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 IT09121 Status: Closed

"DB2 REORGCHK UPDATE STATISTICS ON TABLE ALL" MAY HANG

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
"db2 reorgchk update statistics on table all" may hang 
accidentally. 
If run db2pd -stacks when hang, may find a similar below stack 
at one of xxx.stack.txt file under db2dump directory. 
---------------------------------------------- 
<ossSleep> 
<sqlorest> 
<sqloSpinLockConflict> 
<SQLO_MEM_POOL::captureLatch> 
<sqlogmblkEx> 
<sqlofindf2> 
<pdRLogFilePick> 
<pdRLogGetFilePath> 
<PDLogFacility::open> 
<pdLogInternal> 
<pdLog> 
<SqloMemController::requestMemory> 
<SMemSet::increaseUseableMemory> 
<SMemSet::getChunksFromTree> 
<SMemSet::getContiguousChunks> 
<SQLO_MEM_POOL::getNewChunkSubgroup> 
<SQLO_MEM_POOL::allocateMemoryBlock> 
<sqlogmblkEx> 
   : 
---------------------------------------------- 
 
There is a timing issue and no work around.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 10.5                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.5 FixPack 7.                           * 
****************************************************************
Local Fix:
Solution
Problem was first fixed in DB2 UDB Version 10.5 FixPack 7.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.05.2015
28.01.2016
28.04.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList