Recovering from a failure during forward log recovery
If a failure occurs during the forward-log recovery phase of restart, operations management can recover from this situation.
Symptoms
A Db2 abend occurred, indicating that restart had failed. In addition, the last restart message that was received was a DSNR004I message, which indicates that log initialization completed; therefore, the failure occurred during forward log recovery.Environment
Db2 terminates because a portion of the log is inaccessible, and Db2 is therefore unable to guarantee the consistency of the data after restart.Resolving the problem
Operations management response:
To start Db2 successfully,
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 and which units of recovery made modifications to those page sets. The procedure for determining which page sets contain incomplete changes and which units of recovery made the modifications is described in Recovering from BSDS or log failures during restart. Other topics might help you better understand the problem.