Db2 archive logs
You can use
BMC AMI Recovery Manager
to generate JCL to recover a failed archive log from a second copy of the log.
Although Db2 does automatically use the alternate copy if it is available when the first one fails, it is good practice to make another copy to protect against the loss of both copies. If this loss occurs, the log may be unrecoverable.
The log may also be unrecoverable when there is only a single archive log and it fails. As a safeguard, make a second copy of the log while it is still in good condition.
If Db2 is active, BMC AMI Recovery Manager obtains the following information from Db2:
- Whether single or dual archive logs are used
- The archive log data set prefixes
- The block size, allocation type, and allocation quantities
- The archive log retention period
If Db2 is not active, the information for the first two items comes from the BMC AMI Recovery Manager option set (ARM$OPTS). The device type is always obtained from the option set. The information for the last two items is shown as defaults on the data entry panel that appears when you select Archive Logs in the System Resource Recovery and Maintenance panel. Verify that this information is current if Db2 is not active.
If the archive log is not cataloged, a second procedure must be performed. When this procedure is necessary, BMC AMI Recovery Manager adds JCL that calls the DSNJU004 (Print Log Map) utility. You can use the output from the utility as input to BSDS maintenance procedures that delete information about the failed data set and add the information about the newly recovered data set. See BSDS-maintenance for more information.
This section contains the following topics: