DB2 - Problem description
Problem IT34483 | Status: Closed |
HADR STANDBY ENTERS AN INFINITE LOOP BETWEEN READ FROM MEMORY AND READ FROM DISK WHEN ENCOUNTERING A LOG FILE WITH CORRUPTED XHD | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Standby replay position is not moving up. The following messages are repeatedly printed in Standby's db2diag.log, and the data reported do not change at all: 2017-07-30-14.12.36.251331+480 I169146717A633 LEVEL: Info PID : 18481666 TID : 107807 PROC : db2sysc 0 INSTANCE: istp NODE : 000 DB : DBSTP HOSTNAME: STPDB2 EDUID : 107807 EDUNAME: db2lfr.0 (DBSTP) 0 FUNCTION: DB2 UDB, recovery manager, sqlplfrDoScanNext, probe:2400 DATA #1 : SQLPLFR_SCAN_ID, PD_TYPE_SQLPLFR_SCAN_ID, 8 bytes LFR Scan Num = 3 LFR Scan Caller's EDUID = 138870 MESSAGE : HADR: finished disk scan, next pages read from memory DATA #2 : String, 26 bytes lfrReadBeforeAfterXhdrFlag DATA #3 : Hex integer, 8 bytes 0x0000000000000000 2017-07-30-14.12.36.251675+480 I169147351A827 LEVEL: Info PID : 18481666 TID : 107807 PROC : db2sysc 0 INSTANCE: istp NODE : 000 DB : DBSTP HOSTNAME: STPDB2 EDUID : 107807 EDUNAME: db2lfr.0 (DBSTP) 0 FUNCTION: DB2 UDB, recovery manager, sqlplfrDoScanNextForHadrRemoteLogs, probe:4000 DATA #1 : SQLPLFR_SCAN_ID, PD_TYPE_SQLPLFR_SCAN_ID, 8 bytes LFR Scan Num = 3 LFR Scan Caller's EDUID = 138870 MESSAGE : HADR: Received log gap, reading from disk. DATA #2 : unsigned integer, 8 bytes 18174878065345 DATA #3 : unsigned integer, 8 bytes 18174878073496 DATA #4 : unsigned integer, 8 bytes 2 DATA #5 : unsigned integer, 8 bytes 18174878065345 DATA #6 : unsigned integer, 8 bytes 18174878069421 DATA #7 : Hex integer, 8 bytes 0x0000000000031008 This is because the extent header of a log file is corrupted, so the HADR standby keeps alternating from reading from buffer and disk while not progressing, as it mistakenly considers the log file to be truncated. This causes an infinite loop in Standby and makes Standby unable to proceed with replay. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade Db2 to latest version * **************************************************************** | |
Local Fix: | |
Deactivate and reactivate the standby | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade Db2 to latest version * **************************************************************** | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.10.2020 02.12.2021 02.12.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |