DB2 - Problem description
Problem IT39532 | Status: Closed |
DB2 PURESCALE: MEMBER MAY FODC_PANIC DUE TO CORRUPTED LATCH WITHIN DB2CFCONNPOOLMGR EDU | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
In a Db2 pureScale environment, a Db2 member may encounter a FODC_Panic condition due to a corrupted latch within the db2CFConnPoolMgr EDU. If this issue is encountered the following db2diag.log messages should be observed on the member: 2020-04-16-17.12.43.797374+120 E2048029A2278 LEVEL: Severe (OS) PID : 26804624 TID : 14680 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 HOSTNAME: EDUID : 14680 EDUNAME: db2CFConnPoolMgr 0 FUNCTION: DB2 UDB, SQO Latch Tracing, SQLO_SLATCH_CAS64::getConflictComplex, probe:210 MESSAGE : ZRC=0x870F0114=-2029059820=SQLO_LATCH_ERROR_UNUSED_BITS_ARE_SET "latch likely corrupted. Reserved bits are unexpectedly non-zero." CALLED : OS, -, unspecified_system_function DATA #1 : String, 13 bytes invalid latch DATA #2 : File name, 16 bytes sqloLatchCAS64.C DATA #3 : Source file line number, 8 bytes 591 DATA #4 : Codepath, 8 bytes 0 DATA #5 : String, 137 bytes 0xCCCCCCCCCCCCCCCC: { held X: 0 reserved for X: 0 shared holders: 52428 firstSharIndex: 0xCCCCC firstExclIndex: 0x66666 } DATA #6 : LatchMode, PD_TYPE_LATCH_MODE, 8 bytes 0x1 (SQLO_LATCH_MODE_SHARED) DATA #7 : String, 402 bytes { state = 0xCCCCCCCCCCCCCCCC = { held X: 0 reserved for X: 0 shared holders: 52428 firstSharIndex: 0xCCCCC firstExclIndex: 0x66666 } starve X mode = false xWaitCount = 52428 requestCount = 0 identity = unknown (3276) } DATA #8 : Pointer, 8 bytes 0x078000000c162508 DATA #9 : Hexdump, 16 bytes 0x078000000C162508 : CCCC CCCC CCCC CCCC CCCC CCCC CCCC CCCC ................ CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x0900000012015678 dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3CiT1T 3T7 + 0x2F8 [1] 0x0900000012015EA0 getConflictComplex__17SQLO_SLATCH_CAS64FCUl + 0x1A0 [2] 0x0900000012016AE4 getConflict__17SQLO_SLATCH_CAS64FCUl + 0x84 [3] 0x09000000129B3118 sqleSingleCaReadLinkResources__21SQLE_SINGLE_CA_HANDLEFCP30SQLHA _CF_MEMBER_LINK_RESOURCESCb + 0x5B8 [4] 0x09000000129C085C SAL_DoAdapterHousekeeping + 0xF1C [5] 0x0900000019B11260 sqleCFConnPoolMgrEntry__FPUcUi + 0x2E0 [6] 0x09000000120D3200 sqloEDUEntry + 0x360 [7] 0x09000000005ABFE8 _pthread_body + 0xE8 [8] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 2020-04-16-17.12.43.834249+120 E2050308A690 LEVEL: Error PID : 26804624 TID : 14680 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 HOSTNAME: EDUID : 14680 EDUNAME: db2CFConnPoolMgr 0 FUNCTION: DB2 UDB, base sys utilities, sqle_panic, probe:30 MESSAGE : ADM14005E The following error occurred: "Panic". First Occurrence Data Capture (FODC) has been invoked in the following mode: "Automatic". Diagnostic information has been recorded in the directory named "/db2home/db2inst1/sqllib/db2dump/DIAG0000/FODC_Panic_2020-04-16 -17.12. 43.823476_26804624_14680_000/". | |
Problem Summary: | |
The problem is firstly fixed on Db2 v11.1.4.5. | |
Local Fix: | |
Solution | |
Workaround | |
The problem is firstly fixed on Db2 v11.1.4.5. | |
Comment | |
Upgrade to Db2 v11.1.4.5 or later versions. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.01.2022 22.01.2022 22.01.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |