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

TABLE MAY BE INCONSISTENT AFTER INPLACE TABLE REORG IN PURESCALE WITH
EXPLICIT HIERARCHICAL LOCKING ENABLED

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
The problem occurs when explicit hierarchical locking (EHL) is 
enabled in a DB2 pureScale instance and REORG TABLE is run with 
the INPLACE option.  If a crash occurs after the reorg completes 
but before the table exits EHL mode, the subsequent member crash 
recovery will fail to replay the reorg log records. This will 
result in lost updates and the table will be left in an 
inconsistent state. 
 
To recover, a restore and roll forward through the reorg 
operation will be required to bring the table back to a 
consistent state. 
 
Different symptoms are possible as a result, and it may not be 
possible to detect that this has occurred. One example of a 
possible symptom is a failure during the crash recovery due to 
free space on a page not matching what was expected.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of explicit hierarchical locking in pureScale      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the latest fix pack.                              * 
****************************************************************
Local-Fix:
To prevent the problem from occurring, ensure that EHL mode is 
not enabled (database configuration parameter OPT_DIRECT_WRKLD 
is OFF, which is the default). To recovery from the problem once 
hit, it is necessary to restore a backup image that was taken 
before the REORG operation that crashed and roll forward through 
the REORG operation.
Lösung
Problem was first fixed in DB2 UDB version 10.5 fix pack 5.
Workaround
None.  Recovery requires a restore and roll forward.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.10.2014
15.12.2014
09.04.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.5 FixList