|
Problem IT39792
|
Status: Closed |
CONCURRENT INSERT INTO A COLUMNAR TABLE WITH ENFORCED PRIMARY KEY MAY DEADLOCK
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
When performing concurrent inserts into a columnar table with an
enforced primary key, a deadlock may be encountered where the
following stacks can be observed:
0x0900000000110F94 thread_wait + 0x94
0x090000000D5673E0 sqloWaitEDUWaitPost + 0xA00
0x090000000DC27D74
sqlplWaitOnWP__FCP9sqeBsuEduCP14SQLP_LOCK_INFOCP8SQLP_LRBCP15SQL
P_LTRN_CHAINCbN25 + 0x4E74
0x090000000DF58E5C
sqlplMakeNewRequestNonSD__FP9sqeBsuEduP14SQLP_LOCK_INFOP11SQLP_T
ENTRYP8SQLP_LRBT4P15SQLP_LTRN_CHAINbT7Cb + 0x199C
0x090000000DADB0D4 sqlplrq__FP9sqeBsuEduP14SQLP_LOCK_INFO +
0x1EB4
0x090000000F3EF418
IPRA.$sqliLockInsertRange__FP7SQLI_CBP12SQLI_KEYDATA + 0x78
0x090000000F3EDF84
sqliLockAndVerify__FP7SQLI_CBP12SQLI_KEYDATAUcUliN44P14SQLI_PAGE
_DESCP9SQLI_SLOT + 0x784
0x090000000FA3976C
IPRA.$sqliLockDup__FP7SQLI_CBP11SQLI_SAGLOBP12SQLI_KEYDATAP9SQLI
_SLOTT4Ul + 0x230C
0x090000000FA2CE68
IPRA.$procLeaf2Add__FP7SQLI_CBP11SQLI_SAGLOBP9SQLI_SLOTiP12SQLI_
KEYDATA + 0x868
0x090000000FA2B5AC sqlischa__FP7SQLI_CBP11SQLI_SAGLOBiUi +
0x2B4C
0x090000000FA2C480 IPRA.$next_level__FP7SQLI_CBP11SQLI_SAGLOBiUi
+ 0x60
0x090000000FA292F0 sqlischa__FP7SQLI_CBP11SQLI_SAGLOBiUi + 0x890
0x090000000E0996B0
sqliaddk__FP8sqeAgentP9SQLD_IXCBP8SQLD_KEY12SQLI_KEYDATAP14SQLP_
LOCK_INFOP8SQLP_LRBUlP10SQLI_IXPCRPPv + 0x1030
and
0x0900000000110F94 thread_wait + 0x94
0x090000000D39A664 getConflictComplex__17SQLO_SLATCH_CAS64FCUl +
0x6E4
0x090000000D39AD64 getConflict__17SQLO_SLATCH_CAS64FCUl + 0x84
0x090000000E0B2918
IPRA.$sqlbFindPageInBPOrSim__FP11SQLB_FIX_CBiUlP15SQLB_BufferPoo
l + 0x1678
0x090000000E0AF128 sqlbfix__FP11SQLB_FIX_CB + 0x528
0x090000000F383E44 sqlifix__FP7SQLI_CBP14SQLI_PAGE_DESCUii +
0x84
0x090000000FA28C68 sqlischa__FP7SQLI_CBP11SQLI_SAGLOBiUi + 0x208
0x090000000FA2C480 IPRA.$next_level__FP7SQLI_CBP11SQLI_SAGLOBiUi
+ 0x60
0x090000000FA292F0 sqlischa__FP7SQLI_CBP11SQLI_SAGLOBiUi + 0x890
0x090000000E0996B0
sqliaddk__FP8sqeAgentP9SQLD_IXCBP8SQLD_KEY12SQLI_KEYDATAP14SQLP_
LOCK_INFOP8SQLP_LRBUlP10SQLI_IXPCRPPv + 0x1030
0x0900000020D3BCB8
indexKeyInsert__Q3_7ibm_cde4data21DatabaseTableAccessorFCQ3_7ibm
_cde5types3TSNRCQ2_3std6vectorXTPCQ3_7ibm_cde5types10ValUncodedT
Q3_
7ibm_cde8services9AllocatorXTPCQ3_7ibm_cde5types10ValUncoded__PC
18sqlriCdeColumnListT3 + 0x338
0x0900000020E92734
addKeyToIndexes__Q3_7ibm_cde4data11TableWriterFRCQ2_3std6vectorX
TPCQ3_7ibm_cde5types10ValUncodedTQ3_7ibm_cde8services9AllocatorX
TPC
Q3_7ibm_cde5types10ValUncoded__PC18sqlriCdeColumnListT2 + 0x254
0x0900000020E75290
insertTupleBuffered__Q3_7ibm_cde4data11TableWriterFRCQ2_3std6vec
torXTPCQ3_7ibm_cde5types10ValUncodedTQ3_7ibm_cde8services9Alloca
tor
XTPCQ3_7ibm_cde5types10ValUncoded__PC18sqlriCdeColumnListT2 +
0x370
0x09000000214EE2E0
insertRowInternal__Q3_7ibm_cde4data13TableAccessorFRCQ3_7ibm_cde
4data18UncodedInsertTupleCbPCUlPC18sqlriCdeColumnListT4CUl +
0x120
0x09000000214EBDAC
insertRow__Q3_7ibm_cde4data13TableAccessorFRCQ2_3std6vectorXTQ3_
7ibm_cde5types8DataTypeTQ3_7ibm_cde8services9AllocatorXTQ3_7ibm_
cde
5types8DataType__RCQ2_3std6vectorXTPCQ3_7ibm_cde5types10ValUncod
edTQ3_7ibm_cde8services9AllocatorXTPCQ3_7ibm_cde5types10ValUncod
ed__RQ3_7ibm_cde4data1
8UncodedInsertTuplePCQ3_7ibm_cde5types7IntegerXTlSP0_CbPCUlPC18s
qlriCdeColumnListT7CUl + 0x62C
0x09000000249C4894
insertRow__25cdeTableAccessorInterfaceFPC18sqlriCdeColumnListP26
cdeDirectInsertTupleHandleCl + 0x1B4
0x09000000249F44F4
performInsert__12cdeInterfaceFPC18sqlriCdeColumnListP26cdeDirect
InsertTupleHandleClPl + 0x4F4
0x090000000F4698A4 sqlriCdeFastInsert__FP8sqlrr_cb + 0x5C4
0x090000000F4849F8 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm +
0x5F8
0x0900000010BAAA9C sqlrr_process_execute_request__FP8sqlrr_cbib
+ 0x33FC
0x090000000F1E14A0 sqlrr_execute__FP14db2UCinterfaceP9UCstpInfo
+ 0x5E0 |
| Problem Summary: |
The problem is firstly fixed on Db2 v11.1 Mod1 FP2. |
| Local Fix: |
|
| Solution |
|
| Workaround |
The problem is firstly fixed on Db2 v11.1 Mod1 FP2. |
| Comment |
Upgrade to Db2 v11.1 Mod1 FP2. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.01.2022
29.01.2022
29.01.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
