Recovering from a failure during backward log recovery
When a failure occurs during backward log recovery, Db2 terminates because it cannot access a portion of the log that it needs. Operations management can recover from this situation.
Symptoms
An abend is issued to indicate that restart failed because of a log problem. In addition, the last restart message that is received is a DSNR005I message, indicating that forward log recovery completed and that the failure occurred during backward log recovery.Environment
Because a portion of the log is inaccessible, Db2 needs to roll back some database changes during restart.Resolving the problem
Operations management response:
To start Db2, choose
one of the following approaches:
- Read the information about relevant messages and codes that you received to determine if this approach is possible. The explanations of the messages and codes identify any corrective action that you can take to resolve the problem. If it is possible, correct the problem that made the log inaccessible, and start Db2 again.
- Restore the Db2 log and all data to a prior consistent point and start Db2. This procedure is described in Recovering from unresolvable BSDS or log data set problem during restart.
- Start Db2 without completing some database changes. Do this only if the exact changes cannot be identified; all that can be determined is which page sets might have incomplete changes. The procedure for determining which page sets contain incomplete changes is described in Bypassing backout before restarting. Other related topics might help you better understand the problem.