DB2 - Problem description
Problem IT39916 | Status: Closed |
POSSIBLE MEMORY CORRUPTION WHEN CALLING PD_GET_DIAG_HIST | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
On a multi-member instance it is possible for memory corruption to occur when the PD_GET_DIAG_HIST table function is called. When this occurs the stack looks like this: diagnoseMemoryCorruptionAndCrash SQLO_MEM_POOL::MemTreePut sqlofmblkEx sqlrwGetWLMTableFunctionMergedResult sqlerTrustedRtnCallbackRouter wlmGetNextBuffer pd_get_diag_hist_v10fp3 sqloInvokeFnArgs sqlriInvokerTrusted sqlriInvokeInvoker sqlri_tfftc sqlriFetch sqlrita sqlriSectInvoke sqlrr_process_fetch_request sqlrr_fetch sqljs_ddm_cntqry sqljsParseRdbAccessed sqljsParse sqljsSqlam sqljsDriveRequests sqljsDrdaAsInnerDriver sqljsDrdaAsDriver RunEDU EDUDriver sqloEDUEntry pthread_body And the following probes occur in the db2diag.log: 2022-01-13-13.21.45.425137+060 I295537047A688 LEVEL: Severe PID : 42533144 TID : 403615 PROC : db2sysc 3 INSTANCE: db2inst1 NODE : 003 DB : MYDB1 APPHDL : 3-7123 APPID: *N3.db2inst1.220104145349 UOWID : 1 ACTID: 1 AUTHID : DB2INST1 HOSTNAME: MYHOST1 EDUID : 403615 EDUNAME: db2agent (MYDB1) 3 FUNCTION: DB2 UDB, WLM, sqlrwGetWLMTableFunctionMergedResult, probe:6 CALLED : DB2 UDB, relation data serv, sqlrkrpc_nl RETCODE : ZRC=0x80120003=-2146303997=SQLR_INTRP ?Statement interrupt, detected at RDS? DIA8003C The interrupt has been received. 2022-01-13-13.21.45.428887+060 E295537736A870 LEVEL: Error PID : 42533144 TID : 403615 PROC : db2sysc 3 INSTANCE: db2inst1 NODE : 003 DB : MYDB1 APPHDL : 3-7123 APPID: *N3.db2inst1.220104145349 UOWID : 1 ACTID: 1 AUTHID : DB2INST1 HOSTNAME: MYHOST1 EDUID : 403615 EDUNAME: db2agent (MYDB1) 3 FUNCTION: DB2 UDB, SQO Memory Management, sqloDiagnoseFreeBlockFailure, probe:30 MESSAGE : ADM14005E The following error occurred: ?Panic?. First Occurrenc Data Capture (FODC) has been invoked in the following mode: ?Automatic?. Diagnostic information has been recorded in the directory named ?/db2home/db2inst1/sqllib/db2dump/DIAG0003/FODC_Panic_2022-01-13 -1 3.21. 45.426676_42533144_403615_003/?. 2022-01-13-13.21.45.433275+060 E295538607A2804 LEVEL: Severe PID : 42533144 TID : 403615 PROC : db2sysc 3 INSTANCE: db2inst1 NODE : 003 DB : MYDB1 APPHDL : 3-7123 APPID: *N3.db2inst1.220104145349 UOWID : 1 ACTID: 1 AUTHID : DB2INST1 HOSTNAME: MYHOST1 EDUID : 403615 EDUNAME: db2agent (MYDB1) 3 FUNCTION: DB2 UDB, SQO Memory Management, sqloDiagnoseFreeBlockFailure, probe:999 MESSAGE : Memory validation failure, diagnostic file dumped. DATA #1 : String, 28 bytes Corrupt pool free tree node. DATA #2 : File name, 35 bytes 42533144.403615.mem_diagnostics.txt CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x09000000131B1388 diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCcCb + 0x4E8 [1] 0x09000000131B9C3C MemTreePut__13SQLO_MEM_POOLFP8SMemNodeUlP17SqloChunkSubgroup + 0x6DC [2] 0x09000000131475CC sqlofmblkEx + 0xDEC [3] 0x090000001A656100 sqlrwGetWLMTableFunctionMergedResult__FUiPPv + 0x6A0 [4] 0x0900000013E7A818 sqlerTrustedRtnCallbackRouter__FUiPPv + 0x378 [5] 0x090000002EDE6F88 wlmGetNextBuffer + 0xE8 [6] 0x090000002EE53684 pd_get_diag_hist_v10fp3 + 0x11E4 [7] 0x090000001310A414 sqloInvokeFnArgs + 0x5B94 [8] 0x09000000157F5240 IPRA.$sqlriInvokerTrusted__FP10sqlri_ufobP21sqlriRoutineErrorInt fb + 0xC60 [9] 0x09000000157ECE28 sqlriInvokeInvoker__FP10sqlri_ufobb + 0x2008 [10] 0x090000001A1F4BC4 sqlri_tfftc__FP8sqlrr_cbP9sqlri_tao + 0x324 [11] 0x0900000015AAEBBC sqlriFetch__FP8sqlrr_cbP9sqlri_taol + 0x21C [12] 0x09000000177CA2B8 sqlrita__FP8sqlrr_cb + 0x8F8 [13] 0x0900000015EE1A28 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x688 [14] 0x0900000015347C14 sqlrr_process_fetch_request__FP14db2UCinterface + 0xD14 [15] 0x090000001534376C sqlrr_fetch__FP14db2UCinterfaceP15db2UCCursorInfo + 0x1FCC [16] 0x090000001A6D6E40 sqljs_ddm_cntqry__FP14db2UCinterfaceP13sqljDDMObject + 0x4C0 [17] 0x090000001A66A000 sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC interface + 0x220 [18] 0x090000001A66D134 sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 0x22B4 [19] 0x0900000013DD9E7C IPRA.$sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0xEFC [20] 0x0900000013DE2634 sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4 [21] 0x0900000013DD7D9C IPRA.$sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x141C [22] 0x0900000013DD51BC sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0x33C [23] 0x0900000013265920 RunEDU__8sqeAgentFv + 0xB60 [24] 0x090000001323F840 EDUDriver__9sqzEDUObjFv + 0x300 [25] 0x090000001311E500 sqloEDUEntry + 0x360 [26] 0x09000000005ACFE8 _pthread_body + 0xE8 [27] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 2022-01-13-13.21.45.454486+060 I295541412A570 LEVEL: Severe PID : 42533144 TID : 403615 PROC : db2sysc 3 INSTANCE: db2inst1 NODE : 003 DB : MYDB1 APPHDL : 3-7123 APPID: *N3.db2inst1.220104145349 UOWID : 1 ACTID: 1 AUTHID : DB2INST1 HOSTNAME: MYHOST1 EDUID : 403615 EDUNAME: db2agent (MYDB1) 3 FUNCTION: DB2 UDB, DRDA Application Server, sqljsSignalHandler, probe:10 MESSAGE : DIA0505I Execution of a component signal handling function has begun. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 v11.1.4.6 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to latest fix pack 11.5.7 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * DB2 v11.1.4.6 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to latest fix pack 11.5.7 * **************************************************************** | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.02.2022 22.03.2022 16.04.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |