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 IT09366 Status: Geschlossen

HANG DUE TO INPLACE REORG FAILING TO UNLATCH A PAGE

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
When inplace reorg moves an overflow record and the overflow is 
already on the target page, an attempt may be made to create or 
recreate a page dictionary on the target page. If the dictionary 
creation or recreation does not free up any additional space on 
the page, inplace reorg could fail to unlatch the page. Any 
other application attempting to latch the page will wait on the 
page latch indefinitely. The instance will need to be restarted.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Inplace reorg                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the latest fix pack                               * 
****************************************************************
Local-Fix:
Disable adaptive compression before running inplace reorg.
Lösung
Problem was first fixed in DB2 UDB Version 10.5 fix pack 7
Workaround
Disable adaptive compression before running inplace reorg
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.06.2015
19.01.2016
29.04.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList