Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Information
Space announcement This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.
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.
