DB2 - Problem description
Problem IT24129 | Status: Closed |
DB2 MAY DEADLATCH DURING AN INSERT INTO AN ITC TABLE WHILE THEREARE 2 OR MORE OTHER CONCURRENT IUD TRANSACTIONS | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
B2 may run into a deadlatch when appending new blocks for an ITC table (during an insert) while there are 2 or more other concurrent transaction. This problem can happen if there is a user index on the ITC table and if one of the other transactions running parallel to the insert has an index fetch. If the error occurs, we should see the following stack: -------Frame------ ------Function + Offset------ 0x0900000000112F14 thread_wait + 0x94 0x090000002C940164 getConflictComplex__17SQLO_SLATCH_CAS64FCUl + 0x6E4 0x090000002C940864 getConflict__17SQLO_SLATCH_CAS64FCUl + 0x84 0x090000002D6677CC IPRA.$sqlbFindPageInBPOrSim__FP11SQLB_FIX_CBiUlP15SQLB_BufferPoo l + 0x1ACC 0x090000002D66355C sqlbfix__FP11SQLB_FIX_CB + 0x55C 0x090000002E713444 sqlifix__FP7SQLI_CBP14SQLI_PAGE_DESCUii + 0x84 0x090000002F3E037C sqlischd__FP7SQLI_CBP11SQLI_SDGLOBUsUi + 0x31FC 0x090000002F3E0588 IPRA.$next_level__FP7SQLI_CBP11SQLI_SDGLOBUsUi + 0x28 0x090000002F3DD6BC sqlischd__FP7SQLI_CBP11SQLI_SDGLOBUsUi + 0x53C 0x09000000302D4040 IPRA.$sqliCleanupEmptyLeaf__FP7SQLI_CBUi + 0xE20 0x09000000302CFEE8 sqliCleanupPages__FP7SQLI_CB + 0x2528 0x090000002F3D97F0 sqlidelk__FP8sqeAgentP9SQLD_IXCBP10SQLI_IXPCRP8SQLD_KEY8SQLZ_RID UlP16SQLB_OBJECT_DESC + 0xF70 0x090000002EF00DC4 sqldVirtualColumnDeleteKey__FP8sqeAgentP13SQLD_DFM_WORK8SQLZ_RID UsUl + 0x104 0x090000002E5B8CE0 sqldbFindAppendOrEmptyBlock__FP8sqeAgentP13SQLD_DFM_WORKP16SQLD_ TABLE_CACHET3PUlP8SQLZ_RID + 0xC40 0x090000002EED7DBC IPRA.$sqldCreateAppendCachePagesForMDCTable__FP13SQLD_DFM_WORKP1 5SQLD_PAGE_CACHEP11SQLB_FIX_CBlPUiP16SQLD_TABLE_CACHET6P16dmsBat chCreateCB + 0x1FC 0x090000002EED1090 sqldCreateNewAppendCache__FP13SQLD_DFM_WORKP15SQLD_PAGE_CACHEUlT 3PUlP16SQLD_TABLE_CACHET6 + 0x3170 0x090000002EEDA338 sqldExtendAppendCache__FP13SQLD_DFM_WORKUlP16SQLD_TABLE_CACHET3 + 0x1398 0x090000002EEDE000 sqldSearchPageCache__FP13SQLD_DFM_WORKP15SQLD_PAGE_CACHEP16SQLD_ TABLE_CACHET3 + 0x2A0 0x090000002E5B5AEC sqldb_insertITCRow__FP13SQLD_DFM_WORKP16SQLD_TABLE_CACHET2 + 0x48C 0x090000002EE60E94 sqldRowInsert__FP8sqeAgentUsT2UcUliPP10SQLD_VALUEP8SQLZ_RIDPPv + 0x2A94 0x090000002ED700B4 sqlrinsr__FP8sqlrr_cbUsT2iT2PP10SQLD_VALUEQ3_10sqlri_iudo11t_iud oFlags17t_iudoFlagsKernelP8SQLZ_RIDPPv + 0xD4 0x09000000331DCBE4 sqlriisr__FP8sqlrr_cb + 0x2C4 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.02.2018 27.11.2018 27.11.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |