| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IT39298 | Status: Closed |
HADR STANDBY ENTERS AN INFINITE LOOP BETWEEN READ FROM MEMORY AND READ FROM DISK | |
| product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
| Problem description: | |
The HADR standby database might enter into a condition where its log replay position is not moving up, and the following messages are repeatedly printed to db2diag.log: 2017-07-30-14.12.36.251331+480 I169146717A633 LEVEL: Info PID : 18481666 TID : 107807 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : MYDB1 HOSTNAME: MYHOST1 EDUID : 107807 EDUNAME: db2lfr.0 (MYDB1) 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: db2inst1 NODE : 000 DB : MYDB1 HOSTNAME: MYHOST1 EDUID : 107807 EDUNAME: db2lfr.0 (MYDB1) 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 The repeating messages have the same data value, indicating that the standby database is not making any progress. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade Db2 to v11.5.8.0 or latest version * **************************************************************** | |
| Local Fix: | |
Deactivate and reactivate the standby database. | |
| Solution | |
| Workaround | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade Db2 to v11.5.8.0 or latest version * **************************************************************** | |
| Comment | |
Upgrade Db2 to v11.5.8.0 or latest version | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 02.12.2021 21.04.2022 22.04.2022 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
