Peer forward-log recovery

Peer forward-log recovery is skipped unless it is necessary to rebuild lock information from information contained in inactive, non-quiesced members' logs.

Peer retained-lock recovery requires that Db2 do a peer initialization, a partial CSR phase to rebuild UR status, and then do the forward-log recovery for the non-started member.

During peer forward-log recovery, you see messages similar to the following messages. (The phrases in parentheses are not part of the output.)

 DSNR025I @DB3ADB2 DSNRRGRH GROUP RESTART INITIATED TO
 RECOVER RETAINED LOCKS FOR GROUP MEMBER DB1A
 DSNR003I @DB3ADB2 RESTART...PRIOR CHECKPOINT RBA=00000201CC4E
 DSNR004I @DB3ADB2 RESTART...UR STATUS COUNTS
 IN COMMIT=0, INDOUBT=0, INFLIGHT=0, IN ABORT=0
 (End of peer partial current status rebuild for DB1A)
 
 DSNR005I @DB3ADB2 RESTART...COUNTS AFTER FORWARD
 RECOVERY
 IN COMMIT=0, INDOUBT=0
 DSNR026I @DB3ADB2 DSNRRGRH GROUP RESTART COMPLETED TO
 RECOVER RETAINED LOCKS FOR GROUP MEMBER DB1A
 (End of peer forward-log recovery for member DB2A)
 
 DSNR025I @DB3ADB2 DSNRRGRH GROUP RESTART INITIATED TO
 RECOVER RETAINED LOCKS FOR GROUP MEMBER DB2A
 DSNR003I @DB3ADB2 RESTART...PRIOR CHECKPOINT RBA=000000009C4E
 DSNR004I @DB3ADB2 RESTART...UR STATUS COUNTS
 IN COMMIT=0, INDOUBT=0, INFLIGHT=0, IN ABORT=0
 (End of partial current status rebuild for member DB2A)
 
 DSNR005I @DB3ADB2 RESTART...COUNTS AFTER FORWARD
 RECOVERY
 IN COMMIT=0, INDOUBT=0
 DSNR026I @DB3ADB2 DSNRRGRH GROUP RESTART COMPLETED TO
 RECOVER RETAINED LOCKS FOR GROUP MEMBER DB2A
 DSNR022I @DB3ADB2 DSNRRGRH DB2 SUBSYSTEM HAS
 COMPLETED GROUP RESTART FOR PEER MEMBERS
 (End of peer forward-log recovery for member DB1A)

When all members have completed forward-log recovery—either by performing it on their own or by having a peer perform it for them—the lock structure has been rebuilt.