home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IT00986 Status: Closed

CONCURRENT REORGS ON DIFFERENT DATA PARTITIONS OF THE SAME PARTI TIONED
TABLE MIGHT EXECUTE SEQUENTIALLY DURING IDXRECREAT PHASE.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Once you execute concurrent REORG operations like: 
db2 "reorg table T1 allow no access on data partition PART0" 
db2 "reorg table T1 allow no access on data partition PART1" 
 
on table T1 meting criteria required for parallel reorg, you may 
notice that IdxRecreat phase is being sequential. 
The problem is caused by latching during the processing what 
prevents parallel execution. 
 
The problem can only be hit when INTRA_PARALLEL is turned on or 
when using database partitioning feature. 
 
Observable symptoms: 
1. You might notice unexpected difference between REORG finish 
times for partitions similar in size by observing REORG command 
finish time or db2pd -reorg output. 
2. You might notice in db2top output that only one REORG at the 
time utilizes IO, while REORG for other partitions are idle. 
3. In stacks collected during the issue occurrence, you can 
notice that one REORG thread is holding 
SQLO_LT_SQLD_TCB__loadInProgress latch, while other parallel 
threads are waiting for the latch in subject.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* INTRA_PARALLEL ON or when using DPF                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.5.                             * 
****************************************************************
Local Fix:
Solution
The problem is first fixed in DB2 version 10.1.0.5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.04.2014
14.07.2015
14.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList