Automated drop recovery
The BMC Recovery Management for Db2 solution assists in the recovery of dropped objects.
This type of recovery is generally needed for an error caused by an application program or by user errors.
Drop recovery is handled by the Log Master and
components of the BMC Recovery Management for Db2 solution.
To perform an automated drop recovery, you first specify information about the Db2 objects that were dropped from the catalog, as follows:
- Type of objects to recover (table, table space, or database)
- Name of each object to recover
- Time frame when the objects were dropped from the catalog
Based on your input, Log Master scans the log for information relating to the dropped Db2 objects, then generates several forms of output that enable Log Master (working with
) to recover the dropped objects. The output can include
- DDL statements to create the dropped objects in the Db2 catalog
syntax to recover a table or table space
- SQL statements for populating a recovered table with data
- Db2 commands to rebind any application plans that were invalidated when the objects were dropped
A Drop Recovery report that provides summary information about the Db2 objects that you want to recover
The information includes the specific image copy that should be used for the recovery and OBID translation information.
JCL statements to execute the different types of output in the right order to accomplish the recovery
You can direct Log Master to execute all or part of the generated JCL.
We strongly recommend that you use the Log Master online interface to define your automated drop recovery. Refer to the BMC AMI Log Master for Db2 documentation for step-by-step instructions on recovering dropped objects.
For information about using batch syntax, look for information on the DROPRECOVERY statement in the BMC AMI Log Master for Db2 documentation and in the BMC AMI Recover for Db2 documentation.
Related topics