home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC78648 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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
verfügbare FixPacks:
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

Lösung
First fixed in DB2 Version 9.7, Fixpack 6.
Workaround
n/a
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.09.2011
18.07.2012
18.07.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList