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

UNDER A RARE TIMING SCENARIO, ALTER TABLESPACE WITH LOWER HIGH WATER MARK
MIGHT HANG DUE TO A DEADLATCH IN EXTENTLATCH.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Under a rare timing scenario, ALTER TABLESPACE with LOWER HIGH 
WATER MARK command might hang due to a deadlatch in extentLatch. 
 
Here's the summary of the deadlatch scenario in extentLatch - 
 
o page cleaner A holding an S latch 
o extent mover B trying to latch in X, waiting for A 
o page cleaner A asking to latch again in S, yielding to B 
o Now, A is waiting for B who is waiting for A who is waiting 
  for B. 
 
Here's a stack dump example for the Page Cleaner i.e. 
 
Page Cleaner 
------------ 
getConflict + 0x74 
sqlbFindAndLatchExtent + 0x3F8 
sqlbFindAndLatchExtent + 0x74 
sqlbCommonWriteSetup 
sqlbClnrAsyncWriteSetup 
 
Here's a stack dump example for the Extent Mover i.e. 
 
Extent Mover 
------------ 
getConflict + 0x74 
sqlbMoveHighestExtent + 0x580 
sqlbLockAndMoveExtents + 0x2440 
sqlbExtentMovementEntryPoint + 0x56C 
sqleIndCoordProcessRequest + 0x41C
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Without this APAR, customer is exposed to the issue as       * 
* described in the "ERROR DESCRIPTION" section.                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7, Fixpack 6.                       * 
****************************************************************
Local Fix:
n/a
available fix packs:
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.7, Fixpack 6.
Workaround
n/a
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.09.2011
18.07.2012
18.07.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList