If the archive exit fails, it returns a 28 return code (when full) The db2
instance will stay up and it will try the exit again when all the
applications
disconnect. If the primary log area fills up, the instance will hang.

Dan Callahan IT Specialist
603-472-4121 t/l 525-4121
[Email address protected]
[Email address protected]




"Matt Devlin "
<db2udbdba-ezmlms
hield-x41158390.x To
[Email address protected] "LazyDBA Discussion"
a.com> [Email address protected]
cc
05/19/2004 02:32
PM Subject
RE: newbie: Backing up archived
logs










The rm you issuing... That is in the log archive directory I presume? As
a
rule of thumb I try to avoid rm * on the off chance you have a script
error,
or for some reason there is an unexpected file in that directory. By
removing all the logs in your archive directory you also run the risk of
not
having logs on hand if a rollforward or crash recovery is required. I
would
recommend only deleting logs that are older than your most recent backup.
Using the 'find' with the -exec to a rm command would be a good option
here.

If the log archive dir fills, I believe that userexit will return an error
but not hang the instance. The logs will start to que up in the active
log
directory untill userexit begins functioning properly again.

-----Original Message-----
From: Chuck Hamilton
[Email address protected]
Sent: Wednesday, May 19, 2004 12:56 PM
To: LazyDBA Discussion
Subject: newbie: Backing up archived logs


GlacierI am new to this list so please forgive me if this has already been
answered. I searched the archives but did not find it.

We have a procedure to backup archived logs and then purge them. The backup
product we use is Syncsort's Backup Express version 2.1.5. We use a user
exit (db2uext2) to copy logs to the archive directory. The platform is AIX
5.2. The backup procedure is essentially this...

1. force current log to be archived
2. backup the archive directory to tape
3. run "rm *" to purge the logs

I have concern that there is the possibility of a log being generated after
step 2 begins, not being backed up, and then being deleted by step 3. Is my
convern valid?

One other question while I'm at it. What happens if the disk where the
archive directory fills up and db2 needs to archive another file? Will the
db hang?




---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe, e-mail: [Email address protected]
For additional commands, e-mail: [Email address protected]



---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe, e-mail: [Email address protected]
For additional commands, e-mail: [Email address protected]



DB2 & UDB email list listserv db2-l LazyDBA home page