Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Log Master for Db2 13.1.

Overview of automated drop recovery

Log Master

 helps to automate the recovery of objects that have been dropped from the Db2 catalog. Using information in the Db2 log, 

Log Master

 can create several types of output, depending on the type of recovery that you request. You also have the option of creating Job Control Language (JCL) statements that run the different forms of output in the correct order to accomplish the recovery.

Best practice
We strongly recommend that you use the Log Master online interface to define your automated drop recovery work ID. This work ID creates the forms of output that enable Log Master, working with a recover utility, to recover dropped objects.

Log Master works with the following recover utilities:

  • BMC AMI Recover to recover table spaces and tables
  • DSN1COPY to recover a single dropped table space

Important

The Db2 Recover utilities that Log Master works with do not support the recovery of “versioned” dropped objects that were altered but not reorganized. For information about limitations and special handling for recovery of versioned objects, see the documentation for your Recover utility.

This section contains the following topics:

Related topics

Recovering-dropped-objects

Automated drop recovery step

Troubleshooting-automated-drop-recovery

Adding-an-automated-drop-recovery-step-to-a-work-ID

Example-1-Automated-drop-recovery-of-a-single-table

Example-2-Automated-drop-recovery-of-a-partitioned-table-space

Overview

 

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