DB2 - Problem description
Problem IT29730 | Status: Closed |
DB2 TRIES TO ROLLFORWARD A TABLESPACE TO PIT BEFORE MRT | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Once a tablespace is put into rollforward pending state during crash recovery (for example, due to disk error accessing the tablespace), the minimum recovery time for the subsequent tablespace rollforward is the last log record that crash recovery will reach. This defect corrects the problem where Db2 attempts to rollforward a tablespace to a point-in-time (PIT) that is earlier than the minimum recovery time without flagging that it is an improper PIT. Instead of Db2 replaying to the PIT and performing UNDO processing before failing, Db2 will now fail right away if the tablespace rollforward to a PIT is before the minimum recovery time so the user is not forced to perform a full database restore and rollforward. This defect is seen in the db2diag.log when the tablespace rollforward starts the UNDO phase, then attempts to do completion phase without success: 2019-06-11-05.52.51.155247-240 I113929A1283 LEVEL: Info PID : 9175432 TID : 2572 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-128 APPID: *LOCAL.db2inst1.190611095221 AUTHID : db2inst1 HOSTNAME: serverA EDUID : 2572 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, recovery manager, sqlprUndoPhaseTblSpace, probe:1000 DATA #1 : Start of tablespace undo phase Tablespace recovery status for log stream 0 tsLowTranLSN: 000000066AFDF6BF tsMinBuffLSN: 000000066AFDF6BF recoveryStartingLFSLSN: 0/0000000000000000 tsInitialRecoveryStartingLFSLSN: 0/0000000000000000 tsRfwdExtNum: 240010 tsRfwdExtPID: 4294967295 tsRfwdExtCID: 4294967295 tsRestartLSO: 16131044102849 tsRestartExt: 240024 tsLastCommit: 0 tsNextArcFile: 4294967295 tsInitialExtNum: 240010 tsRedoPass1EndExtNum: 240010 tsRedoPass1LastRecLfsLsn: 3858437580/000000066AFDF6BF tsUndoExtNum: 240010 minPseudoLsn: FFFFFFFFFFFFFFFF 2019-06-11-05.52.51.307894-240 E116764A521 LEVEL: Warning PID : 9175432 TID : 2572 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-128 APPID: *LOCAL.db2inst1.190611095221 AUTHID : db2inst1 HOSTNAME: serverA EDUID : 2572 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, data protection services, sqlufrol, probe:8180 MESSAGE : ADM1611W The rollforward recovery phase has been completed. 2019-06-11-05.52.51.609223-240 I122825A555 LEVEL: Info PID : 9175432 TID : 2572 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-128 APPID: *LOCAL.db2inst1.190611095221 AUTHID : db2inst1 HOSTNAME: serverA EDUID : 2572 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, data protection services, sqlufrol, probe:780 MESSAGE : ADM1608I DB2 is invoking the completion phase of the table space rollforward recovery. 2019-06-11-05.52.51.645047-240 I123924A692 LEVEL: Warning PID : 9175432 TID : 2572 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-128 APPID: *LOCAL.db2inst1.190611095221 AUTHID : db2inst1 HOSTNAME: serverA EDUID : 2572 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, recovery manager, sqlprCalcNewTsState, probe:200 DATA #1 : Rollforward has stopped before reaching the backup endpoint for tablespace USERSPACE1. Rollforward log position: 3858437580/000000066AFDF6BF/0/0 Backup end log position: 3858437580/000000066B15291E/1471051190/3943 2019-06-11-05.52.51.645571-240 I124617A1129 LEVEL: Error PID : 9175432 TID : 2572 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-128 APPID: *LOCAL.db2inst1.190611095221 AUTHID : db2inst1 HOSTNAME: serverA EDUID : 2572 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, recovery manager, sqlprCalcNewTsState, probe:15 MESSAGE : ZRC=0x801000BB=-2146434885=SQLPR_RFWD_COULD_NOT_REACH_VALID_STOP PING_POINT "The rollforward operation could not reach a valid stopping point" DATA #1 : String, 308 bytes Rollforward did not reach far enough for pool id. If the proper log files cannot be found to fully recover this tablespace, then issuing the ROLLFORWARD command with the STOP option can be used to force the database to come online at this point in the logs. The tablespace will then need to be recovered. DATA #2 : Pool ID, PD_TYPE_SQLB_POOL_ID, 2 bytes 2 DATA #3 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes 000000066AFDF6C0 DATA #4 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes 000000066AFDF6BF | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher * **************************************************************** | |
Local Fix: | |
N/A | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.07.2019 16.01.2020 16.01.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |