You should not expect 10 files always. The number of primary specifies the number of pre-allocated log files required at db activayion or first connect. Once allocated and they get used, DB2 will track which is the first active (has a transaction in flight and/or a committed trans. not externalized from the buffer pool) and which is the next active. Now, you're using TSM to archive via the userexit. You must have modified that exit to archive to TSM AND to erase the log files from their log directory. DB2 does not do that by itself. If tell me you did not modify it, either review the code of the exit to see that it does not erase the files or look for a script that would do that and is run by somebody else than you. Also understand that as you are using the exit, DB2 will rename archived files that are not active (see above) whenever it needs to assign a new log file. So it would be possible for log file S0000000.log to get archived, go inactive, get renamed to S0000010.log. In this fashion, as your db is always active, it is possible to have this scenario. Activate: S0000000.log to S0000009.log get allocated. Activity goes on as db is up: Log files get filled to S0000009.log Your DB2 cfg would show First Active or Loghead as: S0000009.log and Next Active as S0000010.log If S0000009.log is the only active log, that's the only one you would see. Deactivate the db and reactivate the db, you will now see: Log Dircetory: S0000010.log thru to S0000019.log Activity happens, log files fill, they get archived, as they become inactive they get either renamed and/or deleted as your exit behaves.
HTH, Pierre. --- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 05, 2004 9:43 AM Subject: [DB2EUG] DB2 logging > Hi, > > We use DB2 v7.2 fixpack 10a on AIX 5.1 with the following database > settings: > > Number of primary log files (LOGPRIMARY) = 10 > Number of secondary log files (LOGSECOND) = 20 > Log retain for recovery enabled (LOGRETAIN) = RECOVERY > User exit for logging enabled (USEREXIT) = ON > > > When starting the first database connection we see that DB2 creates 10 log > files. > > We only make online backups to TSM, there are some sessions in the database > that are always connected. So there is never a point in time without a > active database connection. After some days we see that there is only one > logfile remaining in the log directory. When a new logfile is needed it > will be created by DB2 and the previous logfile will be archived by the > userexit function to TSM. > > Why is there only one file in the log directory? > We expect that there sould be always ten files in the directory. > > Regards > Raoul > > > > ***************************************************************** > This e-mail and any attachment may contain confidential > and privileged material intended for the addressee only. > If you are not the addressee, you are notified that no part of > the e-mail or any attachment may be disclosed, copied or > distributed, and that any other action related to this e-mail > or attachment is strictly prohibited, and may be unlawful. > If you have received this e-mail by error, please notify the > sender immediately by return e-mail, and delete this message. > Martinair Holland N.V., its subsidiaries and/or its employees > shall not be liable for the incorrect or incomplete transmission > of this e-mail or any attachments, nor responsible for any > delay in receipt. > ***************************************************************** > > - > ::: When replying to the list, please use 'Reply-All' and make sure > ::: a copy goes to the list ([EMAIL PROTECTED]). > *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] > *** For more information, check http://www.db2eug.uni.cc > - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
