DB2 - Problem description
Problem IT40527 | Status: Closed |
HADR STANDBY FAILS WITH SQLRLC_FIND_LATCH_ANCHOR() PROBE:5 "INVALID ENTRY_TYPE" CALLED BY SQLPRDBREDOROSCATCACHEINV() | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
This problem only affects HADR standby with both DB2_HADR_ROS and DB2_HADR_ROS_AVOID_REPLAY_ONLY_WINDOW register variables enabled. The standby database might encounter abnormal termination, with the following message from db2diag.log: 2021-04-10-19.06.55.283939-240 I4183E487 LEVEL: Severe PID : 29522 TID : 139829425727232 PROC : db2sysc 0 INSTANCE: xxx NODE : 000 DB : xxx APPHDL : 0-8 APPID: *LOCAL.DB2.210408175428 HOSTNAME: xxx EDUID : 77 EDUNAME: db2redom (xxx) 0 FUNCTION: DB2 UDB, catcache support, sqlrlc_find_latch_anchor, probe:5 MESSAGE : invalid entry_type DATA #1 : unsigned integer, 4 bytes 0 2021-04-10-19.06.55.284504-240 I4671E571 LEVEL: Error PID : 29522 TID : 139829425727232 PROC : db2sysc 0 INSTANCE: xxx NODE : 000 DB : xxx APPHDL : 0-8 APPID: *LOCAL.DB2.210408175428 HOSTNAME: xxx EDUID : 77 EDUNAME: db2redom (xxx) 0 FUNCTION: DB2 UDB, catcache support, sqlrlc_sysschemaauth_invalidate_list, probe:1273 MESSAGE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT "SQLCA has already been built" DATA #1 : String, 17 bytes invalidate failed 2021-04-10-19.07.08.664871-240 I85396E463 LEVEL: Error PID : 29522 TID : 139829438310144 PROC : db2sysc 0 INSTANCE: xxx NODE : 000 DB : xxx APPHDL : 0-5985 APPID: *LOCAL.DB2.210410230700 HOSTNAME: xxx EDUID : 74 EDUNAME: db2redom (xxx) 0 FUNCTION: DB2 UDB, catcache support, sqlrlc_execute_event, probe:79 DATA #1 : unsigned integer, 4 bytes 2149187693 2021-04-10-19.07.08.664980-240 I85860E940 LEVEL: Error PID : 29522 TID : 139829438310144 PROC : db2sysc 0 INSTANCE: xxx NODE : 000 DB : xxx APPHDL : 0-5985 APPID: *LOCAL.DB2.210410230700 HOSTNAME: xxx EDUID : 74 EDUNAME: db2redom (xxx) 0 FUNCTION: DB2 UDB, catcache support, sqlrlc_broadcast, probe:0 MESSAGE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT "SQLCA has already been built" DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 18 sqlerrmc: invalid entry_type sqlerrp : SQLRC023 sqlerrd : (1) 0x801A006D (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFFFFB (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 2021-04-10-19.07.08.665099-240 I86801E783 LEVEL: Error PID : 29522 TID : 139829438310144 PROC : db2sysc 0 INSTANCE: xxx NODE : 000 DB : xxx APPHDL : 0-5985 APPID: *LOCAL.DB2.210410230700 HOSTNAME: xxx EDUID : 74 EDUNAME: db2redom (xxx) 0 FUNCTION: DB2 UDB, recovery manager, sqlprDbRedoRosCatCacheInv, probe:390 MESSAGE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT "SQLCA has already been built" DATA #1 : SQLP_LRH, PD_TYPE_SQLP_LRH, 64 bytes recLfs 5504050195 recLsn 00001690CB86B781 lrecsize 2048 lrectype 0069 lrecflags 0000 backlso 0 maps to pso 0000000000000000 thistid 0000C5160C59 DATA #2 : unsigned integer, 1 bytes 18 DATA #3 : unsigned integer, 4 bytes 0 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.8.0 or higher * **************************************************************** | |
Local Fix: | |
On standby server, run: db2set DB2_HADR_ROS_AVOID_REPLAY_ONLY_WINDOW=OFF Note: Changes to this variable will take effect after deactivate and activate of the standby database. | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.8.0 or higher * **************************************************************** | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 06.04.2022 06.04.2022 06.04.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |