Skip to Content

Db2 active logs

You can use BMC AMI Recovery Manager to generate JCL to recover from the more common active log failures, as follows:

  • A read or write error occurs on one active log in a subsystem where dual logs are employed. BMC AMI Recovery Manager generates JCL to recover the failed copy from the good copy.
  • A read or write error occurs on an active log in a subsystem where only a single log is employed. BMC AMI Recovery Manager generates JCL to recover the failed log from the most recent archived log.
  • A read or write error occurs on both active logs in a subsystem where dual logs are employed. BMC AMI Recovery Manager generates JCL to recover both logs from the most recent archived log.

Related topics

Managing-DB2-Subsystem-Toolbox

Db2-system-resource-maintenance-and-recovery

  • A loss of synchronization occurs between logs in a subsystem where dual logs are employed. BMC AMI Recovery Manager generates JCL to reproduce one log from the other. Logs can be out of synchronization if, for example, a volume was recovered outside of Db2 that contained one or more active data sets.

See the IBM Db2 Administration documentation for a discussion of input/output (I/O) and other errors that can occur with Db2 logs.

If Db2 is active, BMC AMI Recovery Manager ascertains from Db2 the archive log data set prefixes and whether single or dual archive logs are in use. If Db2 is not active, the information comes from the BMC AMI Recovery Manager option set (ARM$OPTS). You should, therefore, always verify the information in the option set before starting to generate active log recovery JCL.

Use the procedure described in Generating JCL to recover a Db2 archive log to generate recovery JCL.

Success

Tip

Before using BMC AMI Recovery Manager to recover active logs, you can, if necessary, use the IDCAMS LISTCAT option on the System Resource Recovery and Maintenance panel to get physical information about the active log. If you need to recover the active log from the archive log, you can use the Print Log Map utility to get information about the most recent archive log. To recover active logs, you need to archive log information only if the active log cannot be recovered from a second copy of the active log.

Generating JCL to recover a Db2 active log

This procedure generates recovery JCL for the most common Db2 active log errors.

You select the error type, provide the required data, and then generate recovery JCL. The JCL must be submitted when Db2 is not active.

Warning

Important

We recommend that you put the recovered active log on a volume that is different from the failed log.

Before you begin

To perform this procedure, you need the following authorizations:

  • EXECUTE authority for BMC AMI Recovery Manager
  • Data set authority to run the JCL

To generate JCL to recover a Db2 active log

  1. In the BMC AMI Recovery for Db2 Main Menu, select 3. DB2 Subsystem Toolbox.
  2. In the Db2 Subsystem Toolbox panel, select 2. Active Logs. 
  3. In the Active Log Recovery panel, select the appropriate error condition.
  4. A second panel appears, allowing you to specify options about the error condition. Enter the information as required and press Enter. for more information about the error conditions, see Log error conditions.
  5. When the JCL Specification panel appears, enter a fully qualified output data set name. Be aware of the following information:
    • The output data set is used for saving the JCL and must be cataloged. If not enclosed in quotes, the output data set will be prefixed by your TSO prefix.
    • The job statement must contain a symbolic variable (&#) for the job number. For more information, see Output-data-sets-job-cards-and-symbolic-variables.

  6. Save the JCL data set or submit the job as required.

    Warning

    Important

    Db2 must be inactive when you submit the recovery JCL.

Log error conditions

The following table describes the log error conditions you might need to specify.

Error condition

Options

I/O error with dual logs

  • Failed data set disposition—delete or rename the failed active log
  • Rename VSAM cluster—rename the failed data set, specifying its new VSAM cluster name in 42 characters or less
  • Failed copy number—specify which copy of the active log failed
  • Failed log number—specify the number of the failed active log
  • New volume—specify the name of the volume where the recovered active log data set will reside
Warning

Important

We recommend that you put the recovered active log on a volume that is different from the volume where the good copy of the active log resides.

I/O error with single log

  • Rename VSAM cluster—specify a new VSAM cluster name in 42 characters or less to rename the failed log data set
  • Failed active log number—specify the number of the failed active log
  • Recovery archive log number—specify the number of the archive log to use in the recovery
  • Recovery archive log timestamp—specify the prefix for the archive log to be used in recovery if the archive log data set is named by Db2 using timestamps
  • Recovery archive log volume—specify the volume number of the archive log to be used in recovery if the archive log data set is not cataloged
  • Recovery archive unit—specify the unit name of the device where the archive resides if the archive log data set is not cataloged
  • New active log volume—specify the name of the volume where the new active log will reside (optional)
Warning

Important

If you leave this field blank, the active log will be stored on the volume where it is currently defined.

I/O error with both dual logs

  • Rename VSAM cluster copy 1—specify a new VSAM cluster name in 42 characters or less to rename the first failed log data set
  • Rename VSAM cluster copy 2— specify a new VSAM cluster name in 42 characters or less to rename the second failed log data set
  • Failed active log number— specify the number of the failed active log
  • Recovery archive log number—specify the number of the archive log to use in the recovery
  • Recovery archive log prefix—specify the prefix of the archive log data set to use in recovery if the archive log data set name is created by Db2 using a timestamp
  • Recovery archive log volume—specify the volume number of the archive log to use in recovery if the archive log data set is not cataloged
  • Recovery archive unit—specify the unit name of the device on which the archive log resides if the archive log data set is not cataloged
  • New active log volume copy 1—specify the volume where Copy 1 of the new active log will reside. If you leave this field blank, the recovered active log is put on the volume where it resided before the failure.
  • New active log volume copy 2—specify the volume where copy 2 of the new active log will reside. If you leave this field blank, the recovered active log is put on the volume where it resided before the failure.

Out of synchronization

  • Copy requiring recovery—specify which copy of the active log will be recovered
  • Active log number— specify the number of the active log that will be recovered

Initialize active logs

Initializes all unformatted active logs

Display, Add or Remove

You can display, add, or remove active logs while Db2 is still up and running.

  • Active Log Display—run the Display online or as a batch job.
  • Active Log Add—run the added active log online or as a batch job.
  • Add Active Log name—add an active log by specifying its name.
  • Add Active log number—add the active log by specifying its number.
  • Active Log Remove—run the removed active log online or as a batch job.
  • Remove Active Log name—remove an active log by specifying its name.
  • Remove Active Log number—remove an active log by specifying its number.
Warning

Important

BMC AMI Recovery Manager ignores active logs in Pending Removal status.

For more information about adding and removing active logs, see the IBM documentation.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Recovery Manager for Db2 13.1