Description of failure during current status rebuild

When a failure occurs during current status rebuild, certain characteristics of the situation are evident.

The following figure illustrates the timeline of events that exist when a failure occurs during current status rebuild.
Figure 1. Failure during current status rebuild
Begin figure description. This figure is a time line that depicts events that occur during a failure of current status rebuild. End figure description.

The portion of the log between log RBAs X and Y is inaccessible. For failures that occur during the current status rebuild phase, the following activities occur:

  1. Log initialization completes successfully.
  2. Db2 locates the last checkpoint. (The BSDS contains a record of its location on the log.)
  3. Db2 reads the log, beginning at the checkpoint and continuing to the end of the log.
  4. Db2 reconstructs the status of the subsystem as it existed at the prior termination of Db2.
  5. During this process, a problem with the log is encountered, preventing Db2 from reading all required log information. Db2 terminates and issues an abend reason code. Some of the abend reason codes that might be issued include:
    • 00D10261
    • 00D10262
    • 00D10263
    • 00D10264
    • 00D10265
    • 00D10266
    • 00D10267
    • 00D10268
    • 00D10329
    • 00D1032A
    • 00D1032B
    • 00D1032C
    • 00E80084

Because the end of the log is inaccessible in this case, some information is lost:

  • Units of recovery might have successfully committed or modified additional page sets past point X.
  • Additional data might have been written, including those that are identified with writes that are pending in the accessible portion of the log.
  • New units of recovery might have been created, and these might have modified data.

Because of the log error, Db2 cannot perceive these events.

A restart of Db2 in this situation requires truncation of the log.