Backward log recovery failure

If a failure occurs during the backward-log recovery phase of restart, operations management can recover from this situation.

When a failure occurs during the backward log recovery phase, certain characteristics of the situation are evident, as the following figure shows.

Figure 1. Illustration of failure during backward log recovery
Begin figure description. This figure is a time line that depicts events that occur during a failure of backward log recovery. End figure description.

The portion of the log between log RBA X and Y is inaccessible. The restart process was reading the log in a backward direction, beginning at the end of the log and continuing backward to the point marked by Begin URID5 in order to back out the changes that were made by URID5, URID6, and URID7. You can assume that Db2 determined that these units of recovery were inflight or in-abort. The portion of the log from point Y to the end of the log has been processed. However, the portion of the log from Begin URID5 to point Y has not been processed and cannot be processed by restart. Consequently, database changes that were made by URID5 and URID6 might not be fully backed out. All database changes made by URID7 have been fully backed out, but these database changes might not have been written to disk. A subsequent restart of Db2 causes these changes to be written to disk during forward recovery.