|
Problem IC67129
|
Status: Closed |
APPLICATIONS ARE BLOCKED IN A DEADLATCH BETWEEN TCB CHAIN LATCH AND CACHED TABLE LATCH |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Applications are blocked in a deadlatch between
SQLO_LT_SQLD_CHAIN__fullChainLatchNS and
SQLO_LT_SQLD_APP_CB__cachedTableLatch. This can happen during
normal runtime processing.
Executed db2pd -alldbpartitionnums -stack all(twice in 3 minutes
interval).
3395.6873.002.stack.txt:Waiting on latch type:
(SQLO_LT_SQLD_CHAIN__fullChainLatchNS) - Address:
(0x2b494170bb80), Line: 1517, File: sqldtcb.C
.
.
3395.6425.002.stack.txt:Waiting on latch type:
(SQLO_LT_SQLD_APP_CB__cachedTableLatch) - Address:
(0x2b49220301e4), Line: 6869, File: sqldinlines.h
.
.
3395.6425.002.stack.txt:Holding Latch type:
(SQLO_LT_SQLD_CHAIN__fullChainLatchNS) - Address:
(0x2b494170be80), Line: 1576, File: sqldtcb.C
.
.
3395.6873.002.stack.txt:Holding Latch type:
(SQLO_LT_SQLD_APP_CB__cachedTableLatch) - Address:
(0x2b49220301e4), Line: 1147, File: sqldmisr.C
.
.
<StackTrace>
-----FUNC-ADDR---- ------FUNCTION + OFFSET------
0x00002B4907807EEF ossDumpStackTraceEx + 0x01ef
(/home/svtdbm6/sqllib/lib64/libdb2osse.so.1)
0x00002B4907802C6A _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm +
0x00cc
(/home/svtdbm6/sqllib/lib64/libdb2osse.so.1)
0x00002B4904B826F7 sqlo_trce + 0x0365
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B4904BC675A sqloDumpDiagInfoHandler + 0x00e0
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B49023D3C00 address: 0x00002B49023D3C00 ; dladdress:
0x00002B49023C6000 ; offset in lib: 0x000000000000DC00 ;
(/lib64/libpthread.so.0)
0x00002B49081A6C97 semop + 0x0007
(/lib64/libc.so.6)
0x00002B49036BEE27 _ZN17SQLO_SLATCH_CAS6418getConflictComplexEm
+ 0x04a9
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B49036BE93E _ZN17SQLO_SLATCH_CAS6411getConflictEm +
0x0068
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B490586507E _Z10sqldFixTCBP8sqeAgentiiiiPP8SQLD_TCBjj +
0x060e
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B490585188C
_Z19sqldLockTableFixTCBP8sqeAgenttthiiiimmiPciS1_iP14SQLP_LOCK_I
NFOPP8SQLD_TCBjj
+ 0x098a
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B49032826FA
_Z13sqldRowInsertP8sqeAgenttthmiPP10SQLD_VALUEP13SQLD_TDATARECP8
SQLZ_RID
+ 0x1b3e
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B490383AFB3
_Z8sqlrinsrP8sqlrr_cbttitPP10SQLD_VALUEmP8SQLZ_RID + 0x006f
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B4903848E94 _Z8sqlriisrP8sqlrr_cb + 0x0158
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B49058CEBB7 _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm
+ 0x00e5
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B4904D8E9BB _Z16sqlrr_dss_routerP8sqlrr_cb + 0x06d1
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B4904D9087D
_Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0x0d71
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B4903FE67BC _Z20sqleSubRequestRouterP8sqeAgentPjS1_ +
0x0674
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B4903FE7210 _Z21sqleProcessSubRequestP8sqeAgent + 0x00a6
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B49032E5EBB _ZN8sqeAgent6RunEDUEv + 0x063b
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B49039853B0 _ZN9sqzEDUObj9EDUDriverEv + 0x00a6
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B4903985307 _Z10sqlzRunEDUPcj + 0x0009
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B490370A4C3 sqloEDUEntry + 0x02fb
(/home/svtdbm6/sqllib/lib64/libdb2e.so.1)
0x00002B49023CC143 address: 0x00002B49023CC143 ; dladdress:
0x00002B49023C6000 ; offset in lib: 0x0000000000006143 ;
(/lib64/libpthread.so.0)
0x00002B49081A58CD __clone + 0x006d
(/lib64/libc.so.6)
</StackTrace> |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* A deadlatch situation can occur between two applications. *
* The one application holds the TCB chain latch and is *
* requesting the cache table latch. The other application is *
* holding the cache table latch and is requesting the TCB *
* chain latch. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.07.002 *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
This APAR corrects and eliminates the deadlatch possibility.
Fixed in DB2 Version 9.07.002 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC67145
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.03.2010
23.04.2010
23.04.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.7.002
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
