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 Recovery Management for Db2 13.1.

Full local subsystem recovery with conditional restart avoidance

In the past, full subsystem recoveries have always included a conditional restart, followed by the recovery of both application objects and the Db2 catalog and directory. This type of recovery is very time- and resource-intensive. However, unchanged objects do not need to be recovered and a conditional restart is not required if no alters, drops or creates were performed in the subsystem between the recovery point and the current time. In addition, recovery time can be further reduced if a quiet point can be used as the recovery point.

The BMC Recovery Management for Db2 solution can dramatically shorten the time required to perform a recovery of an entire local subsystem by analyzing the system for unchanged objects, DDL activity, and quiet points and then generating the fastest and most efficient recovery jobs possible.

This section contains the following topics:

Related topic

Solution-only-features


 

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