suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT21726 Status: Closed

Deadlatch caused query on a range partitioned table to hang in aparallel
environment

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
During the execution of a query on a range partitioned table, a
deadlatch occurred that caused the query to hang.  It was
necessary to recycle DB2 to break the deadlatch.

The factors involved here are:
- parallel environment (SMP enabled)
- select on a range partitioned table with partitioned
indexes
- index needs to be rebuilt

The deadlatch occurred between different subagents processing
the query and rebuilding the invalid index.

The stacks will show similar messages:


Waiting on latch type: (SQLO_LT_SQLD_TCB__loadInProgress) -
Address: (0x7ff506509900), Line: 382, File:
/view/db2_v101fp4_linuxamd64_s140509/vbs/engn/sqd/inc/sqldtcb_in
lines.h
Holding Latch type: (SQLO_LT_SQLP_LTRN_CHAIN__transChainLatch) -
Address: (0x7fcace8d4880), Line: 1696, File:
/view/db2_v101fp4_linuxamd64_s140509/vbs/engn/sqp/inc/sqlpLockIn
ternal.h


Waiting on latch type:
(SQLO_LT_SQLP_LTRN_CHAIN__transChainLatch) - Address:
(0x7fcace8d4880), Line: 1696, File:
/view/db2_v101fp4_linuxamd64_s140509/vbs/engn/sqp/inc/sqlpLockIn
ternal.h
Holding Latch type: (SQLO_LT_SQLD_TCB__loadInProgress) -
Address: (0x7ff506509900), Line: 1025, File:
/view/db2_v101fp4_linuxamd64_s140509/vbs/engn/include/sqldtm_inl
ines.h
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 2 Fix Pack 2 or higher               *
****************************************************************
Local Fix:
The problem can be avoided by not scanning a range partitioned
table with invalid indexes; rebuild any invalid indexes before
accessing the table.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT10880 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.08.2017
24.10.2017
24.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)