We have logarchmeth1 set. Also, we have a monitoring script that
checks the gap between any log files in the active log directory. We
have just recently activated logarchmeth1 and what we have found is
that we have a large occurrance of gaps. IBM has told us this is
because the secondary logs are hanging out and will not leave the
active log directory until the database is inactive. Our application
is 24/7 so the databases do not become inactive much.
We have been manually going out and removing the offending log file.
The log file is in the logarchmeth1 directory and the active
directory.
We went to logarchmeth1 to have the whole process controlled by db2
udb. Does anyone have a solution for our issue. We can code (ksh) to
delete the file, but this sorta defeats the purpose.
Thank you for any thoughts,
Kermit Lowry
S1 Corp