Configuring the DB2 Log Manager

Edit online

To activate log archival or retrieval with the DB2® Log Manager facility, modify the DB2 database configuration during the installation. The following two changes to the database configuration are the minimum changes necessary to use the DB2 Log Manager with Data Protection for SAP

Procedure

Update one of the LOGARCHMETH database configuration parameters (this example uses LOGARCHMETH1):

(UNIX™ and Linux™):

db2 update db cfg for SID using LOGARCHMETH1 VENDOR:/path/shared library

(Windows™):

db2 update db cfg for SID using LOGARCHMETH1 VENDOR:drive:\path\tdpdb2.dll

Update the Data Protection for SAP environment. A file that contains the environment settings must be made available to DB2 to allow DB2 to provide this environment for Data Protection for SAP archive or retrieve requests. This file is an extra requirement. This example shows the setup that is needed by Data Protection for SAP for LOGARCHMETH1:
- (UNIX and Linux):
```
db2 update db cfg for SID using LOGARCHOPT1 /path/vendor.env 
```
- (Windows):
```
db2 update db cfg for SID using LOGARCHOPT1 drive:\path\vendor.env 
```
The update to LOGARCHMETH takes effect during the next log file archive.

Results

The following database configuration parameters are applicable to DB2 database backup and restore, and log archive and retrieve with Data Protection for SAP:

Table 1. Configuration parameters for DB2 database backup and restore, and log archive and retrieve
Parameter	Description	Default
LOGARCHMETH1	Media type of the primary destination for archived log files	Off
LOGARCHOPT1	Options field for the primary destination for archived log files (if required).	NULL
LOGARCHMETH2	Media type of the secondary destination for archived log files. If this path is specified, log files are archived to both this destination and the destination that is specified by LOGARCHMETH1.	Off
LOGARCHOPT2	Options field for the secondary destination for archived log files (if required).	NULL
FAILARCHPATH	If DB2 is unable to archive log files to both the primary and secondary (if set) archive destinations because of a media problem, then DB2 tries to archive log files to this path. This path must be a disk.	NULL
NUMARCHRETRY	Number of retries to archive a log file to the primary or secondary archive destination before log files are archived to a failover directory. This option is used only if FAILARCHPATH is set. If NUMARCHRETRY is not set, DB2 continuously tries to archive again to the primary or secondary log archive destination.	5
ARCHRETRYDELAY	Number of seconds to wait after a failed archive attempt before it tries to archive the log file again. Subsequent retries take effect only if NUMARCHRETRY is at least set to 1.	2

The database configuration parameters LOGRETAIN and USEREXIT are still available but are mapped to the parameter LOGARCHMETH1. For further description of the DB2 Log Manager, see the DB2 Administration Guide. Configure Data Protection for SAP so that at least one IBM Storage Protect™ session is available for each of these operations. One session is needed for the database backup and one is for the log archives.