DB2 UDB Logretain

[ssarah]

hi,
I have questions regarding DB2 UDB v8.1 Log management. We have a
database cfg file has recently changed to the following setting:

LOGPRIMARY =20
LOGSECOND =40
LOGRETAIN = RECOVERY
USEREXIT = NO
LOGARCHMETH1= DISK :/db2home/DB/archive

It seems that the old log files stays in the active log directory. Will the log files in the active log directory exceed 20? Does the old log files required manaully removal? How do I know which log file is committed and can be removed? Why DB2 has the same log files writting to active log path and the LOGARCHMETH1 location?

Thanks
Sarah

[Dale McInnis]

Sarah
With this configuration, DB2 will maintain 20 log files (at a minimum) in the active log path. If you have a long running transaction that spans more than the 20 log files, then DB2 will allocate up to an additional 40 log files (for a total of 60 log files) in the active log path.

As soon as a log file is filled (even if there are open transactions in it) the file will be copied to the archive path (/db2home/DB/archive). The file will stay there forever, you must manually purge what is no longer needed based on
your recovery policy. The log file, once archived, will be renamed to a future extent once all active transactions in the log file have completed.

Hope this helps

Dale McInnis

hi,
I have questions regarding DB2 UDB v8.1 Log management. We have a
database cfg file has recently changed to the following setting:

LOGPRIMARY =20
LOGSECOND =40
LOGRETAIN = RECOVERY
USEREXIT = NO
LOGARCHMETH1= DISK :/db2home/DB/archive

It seems that the old log files stays in the active log directory. Will the log files in the active log directory exceed 20? Does the old log files required manaully removal? How do I know which log file is committed and can be removed? Why DB2 has the same log files writting to active log path and the LOGARCHMETH1 location?

Thanks
Sarah