DB2 - Problem description
Problem IT38024 | Status: Closed |
FODC_PANIC IN LATCH RELEASECONFLICT() WHEN MAXIMUM NUMBER OF SYSTEM TEMPORARY TABLES IN USE FOR COLUMN-ORGANIZED TABLE WORKLOADS | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
When then number of system temporary tables concurrently in use attempts to exceeds the system temporary tablespace limit, an FODC_Panic may occur due to improper error handling. This condition is more probable with column-organized table workloads, versus row-organized table workloads. The db2diag.log will contain an error message from function "SQLO_SLATCH_CAS64::releaseConflict, probe:330" and token "Attempting to unlock an invalid latch", like so: 2021-05-03-11.42.05.780298-420 E20132101E4281 LEVEL: Severe (OS) PID : 3052 TID : 140462266509056 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : DBNAME1 APPHDL : 0-122 APPID: *LOCAL.db2inst1.210503175008 UOWID : 2 ACTID: 1 AUTHID : DB2INST1 HOSTNAME: hostname EDUID : 502 EDUNAME: db2agntcol (DBNAME1) 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 ...etc... CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x00007FDA982DFD0F _ZNK17SQLO_SLATCH_CAS6420dumpDiagInfoAndPanicEPKcjmmlmiS1_mi + 0x22F [1] 0x00007FDA982E0E33 _ZN17SQLO_SLATCH_CAS6415releaseConflictEv + 0x3B3 [2] 0x00007FDA90A1E2DA _Z23sqldInternalCreateTableP8sqeAgentP19SQLD_TABLECREATE_CB + 0x1AAA [3] 0x00007FDA90A21017 _Z19sqldTableCreateTempP8sqeAgentPtS1_hmmiP10SQLD_FIELDP12SQLD_C OLINFOim + 0x177 [4] 0x00007FDA9136BBD3 _ZN7ibm_cde4data17DatabaseTempTable15createTempTableEv + 0x1A3 [5] 0x00007FDA9136E6FA _ZN7ibm_cde4data17DatabaseTempTableC1EP13SQLO_MEM_POOL + 0x9A [6] 0x00007FDA9136E88B _ZN7ibm_cde4data13openTempTableEP13SQLO_MEM_POOL + 0x4B [7] 0x00007FDA9547BA6A _ZN7ibm_cde5query13JoinSpillInfo13initPageSpillEbmmm + 0x32A | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Modpack/Fixpack inclusive of this APAR fix. * **************************************************************** | |
Local Fix: | |
n/a | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Modpack/Fixpack inclusive of this APAR fix. * **************************************************************** | |
Comment | |
Problem was first fixed in DB2 UDB Version 11.5 fix pack 7. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 16.08.2021 15.12.2021 29.03.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |