Log File Management: Concepts
For an explanation of the importance of log files and background information about the use of log files in database transaction processing and database recovery, refer to the IBM documentation.
This section describes the log file management tasks that can be accessed from the DB2 Control Center (DB2CC).
Within an R/3 environment, a log file can have four different states during its life cycle:
The log file is currently being used to log transactions. The location of the log file is the LOGPATH database.
The log file is no longer used, but contains transactions for which data pages have not yet been written from the buffer pool to disk. The location of the log file is the LOGPATH database and DB2DB6_ARCHIVE_PATH (that is, the log file was archived by the db2 user exit).
The log file is neither being used, nor contains transactions with unwritten data pages. The location of the log file is DB2DB6_ARCHIVE_PATH.
The log file is archived. The location of the log file is ADSM or tape (that is, it has been saved by BRARCHIVE).
The SAP-DB2admin enhancements to the DB2CC support this life cycle.
The Life Cycle of a Log File
For a description of the parameters that affect log file management, see Log File Management Parameters.
For a description of the available log file management protocols, see Log File Management Protocols.