Forward-log recovery failure
When a failure occurs during the forward-log recovery phase of Db2 restart, certain characteristics of the situation are evident.
The following figure illustrates the events surrounding a failure during the forward-log recovery phase of Db2 restart.

The portion of the log between log RBA X and Y is inaccessible. The log initialization and current status rebuild phases of restart completed successfully. Restart processing was reading the log in a forward direction, beginning at some point prior to X and continuing to the end of the log. Because of the inaccessibility of log data (between points X and Y), restart processing cannot guarantee the completion of any work that was outstanding at restart prior to point Y.
Assume that the following work was outstanding at restart:
- The unit of recovery that is identified as URID1 was in-commit.
- The unit of recovery that is identified as URID2 was inflight.
- The unit of recovery that is identified as URID3 was in-commit.
- The unit of recovery that is identified as URID4 was inflight.
- Page set A had writes that were pending prior to the error on the log, continuing to the end of the log.
- Page set B had writes that were pending after the error on the log, continuing to the end of the log.
The earliest log record for each unit of recovery is identified on the log line in Figure 1. In order for Db2 to complete each unit of recovery, Db2 requires access to all log records from the beginning point for each unit of recovery to the end of the log.
The error on the log prevents Db2 from guaranteeing the completion of any outstanding work that began prior to point Y on the log. Consequently, database changes that are made by URID1 and URID2 might not be fully committed or backed out. Writes that were pending for page set A (from points in the log prior to Y) are lost.