DB2 - Problem description
Problem IT34023 | Status: Closed |
FODC_PANIC WITH INVALID LATCH FROM SQLOLATCHCAS64.C WHEN ROUTINEEXECUTION LIST MONITORING IS ENABLED. | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
Db2 can trap when routine execution list monitoring is enabled (mon_rtn_execlist db config parameter set to on). The trap is on function rollupMetricsForStmt. Db2diag.log may have the following entries: 2020-08-04-06.23.31.760790-240 E401915A4157 LEVEL: Severe (OS) PID : 7932508 TID : 913548 PROC : db2sysc 0 INSTANCE:db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-19418 APPID: 1234565789 UOWID : 242289 ACTID: 3 AUTHID : db2inst1 HOSTNAME: localhost EDUID : 913548 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, SQO Latch Tracing, SQLO_SLATCH_CAS64::releaseConflict, probe:330 MESSAGE : ZRC=0x870F011E=-2029059810=SQLO_LATCH_ERROR_EXPECTED_HELD "expected latch to be held." CALLED : OS, -, unspecified_system_function DATA #1 : String, 39 bytes Attempting to unlock an invalid latch: DATA #2 : File name, 16 bytes sqloLatchCAS64.C DATA #3 : Source file line number, 8 bytes 1054 DATA #4 : Codepath, 8 bytes 2 DATA #5 : String, 125 bytes 0x0000000000000000: { held X: 0 reserved for X: 0 shared holders: 0 firstSharIndex: 0x0 firstExclIndex: 0x0 } DATA #6 : LatchMode, PD_TYPE_LATCH_MODE, 8 bytes 0x0 (invalid mode) DATA #7 : String, 411 bytes { state = 0x0000000000000000 = { held X: 0 reserved for X: 0 shared holders: 0 firstSharIndex: 0x0 firstExclIndex: 0x0 } starve X mode = true xWaitCount = 0 requestCount = 0 identity = sqmRtnMetricsTable::m_rtnStmtLatch (872) } DATA #8 : Pointer, 8 bytes 0x0a00020347a93fa0 DATA #9 : Hexdump, 16 bytes 0x0A00020347A93FA0 : 0000 0000 0000 0000 0368 0000 0000 0000 .........h...... CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x0900000019B61678 dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3CiT1T 3T7 + 0x2F8 [1] 0x0900000019B62E4C releaseConflict__17SQLO_SLATCH_CAS64Fv + 0x10C [2] 0x090000001A9FF1D0 IPRA.$rollupMetricsForStmt__17sqmRtnMetricsNodeFP19sqlrr_curr_ac tivityb + 0x1330 [3] 0x090000001A9FD380 sqlmTermActivityMetrics__FP19sqlrr_curr_activityP8sqeAgentP5sqlc a + 0x3AC0 [4] 0x090000001D97425C IPRA.$sqlrr_remove_curr_activity__FP8sqlrr_cbiPP19sqlrr_curr_act ivity + 0x8BC [5] 0x090000001D9536A4 sqlrr_activity_exe_stop__FP8sqlrr_cb + 0x924 [6] 0x090000001A8EC0B8 sqlricls_simple__FP8sqlrr_cbil + 0xC18 [7] 0x090000001BD3218C sqlrr_process_execute_request__FP8sqlrr_cbib + 0x29EC [8] 0x090000001BCCCF40 sqlrr_execute__FP14db2UCinterfaceP9UCstpInfo + 0x4A0 [9] 0x090000001E3FB06C executeSection__10pvmPackageFP5sqlcaUib + 0x98C [10] 0x090000001E3F6028 executeQuery__3PVMFUib + 0x208 [11] 0x090000001E402CE0 run__3PVMFv + 0xFE0 [12] 0x090000001E3EE95C pvm_entry + 0x45C [13] 0x0900000019C0BB0C sqloInvokeFnArgs + 0x5D6C [14] 0x090000001D5BB958 IPRA.$sqlriInvokerTrusted__FP10sqlri_ufobP21sqlriRoutineErrorInt fb + 0x2AF8 [15] 0x090000001D5B16A8 sqlriInvokeInvoker__FP10sqlri_ufobb + 0x2008 [16] 0x090000001D5B25B0 sqlricall__FP8sqlrr_cb + 0x670 [17] 0x090000001CCBD138 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x618 [18] 0x090000001BD32DE4 sqlrr_process_execute_request__FP8sqlrr_cbib + 0x3644 [19] 0x090000001BCCCF40 sqlrr_execute__FP14db2UCinterfaceP9UCstpInfo + 0x4A0 [20] 0x09000000210F903C sqljs_ddm_excsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0x5BC [21] 0x0900000021075660 sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC interface + 0x280 [22] 0x09000000210786E4 sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 0x2264 [23] 0x09000000210438BC IPRA.$sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0xE9C [24] 0x090000002104BFD4 sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4 [25] 0x0900000021041970 IPRA.$sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x13F0 [26] 0x090000002103EDB4 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0x334 [27] 0x0900000019D64320 RunEDU__8sqeAgentFv + 0xB60 [28] 0x0900000019D3E540 EDUDriver__9sqzEDUObjFv + 0x300 [29] 0x0900000019C1FA80 sqloEDUEntry + 0x360 [30] 0x0900000000568E10 _pthread_body + 0xF0 [31] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF Setting mon_rtn_execlist to OFF prevents the issue | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.5.0 or higher * **************************************************************** | |
Local Fix: | |
Setting mon_rtn_execlist to OFF prevents the issue | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.5.0 or higher * **************************************************************** | |
Comment | |
Upgrade to Db2 11.5.5.0 or higher | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.08.2020 20.11.2020 20.11.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |