I had a similar problem once a few years back. The answer I got from IBM
was there is no way to get it to recall the archive on older log files.
However there is a solution. We just wrote a small korn shell script that
called the user exit manually passing it the name of the old log files. It
them went about its business of doing the archive as though DB2 had invoked
it.
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, July 31, 2001 7:52 AM
> To: [EMAIL PROTECTED]
> Subject: DB2EUG: UDB and Archive Logging (USEREXIT)
>
> We've been using archive logging and the "db2uext2" user exit for
> archiving
> our log files to TSM for quite some time with pretty good success.
> However, yesterday something stopped working and the db2uext2 exit started
> failing. We stopped and restarted the instance, which seems to have
> cleared up the problem as new archive logs started getting archived to
> TSM.
> But all the older log files for which the userexit failed are still
> residing on disk, and are not being archived to TSM. This is causing us
> space problems for these file systems.
>
> Does anybody know how I can get the exit to be called again in order to
> force these older log files to get archived to TSM so that we can free up
> space?
>
> Thanks,
>
> Bill Gallagher, DBA
> Phoenix Life Insurance
>
>
>
> =====
> To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
> For other info (and scripts), see
> http://people.mn.mediaone.net/scottrmcleod
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
