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

INSTANCE CRASHES DURING ROLLBACK OF DELETE ON A COMPRESSED INDEX

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
During the rollback (undo) of a delete operation on a compressed 
index, an index page may get corrupted, resulting in an instance 
crash. 
 
The problem occurs when some decimal values are deleted from the 
compressed index, and the operation is rolled back thereafter. 
Index manager incorrectly processes the prefix for decimal type 
as fixed-length prefix causing a page corruption. A similar 
problem is possible for string types, as well when a case 
insensitive database is being used. 
 
The user will see a severe error in db2diag.log from the 
function "procLeaf2Del, probe:2" stating that the index key 
could not be found (e.g. SQLI_NOKEY).
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users that use index compression with case insensitive or    * 
* locale-aware Unicode databases.                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* During the rollback (undo) of a delete operation on a        * 
* compressed                                                   * 
* index, an index page may get corrupted, resulting in an      * 
* instance                                                     * 
* crash.                                                       * 
*                                                              * 
*                                                              * 
*                                                              * 
* The problem occurs when some decimal values are deleted from * 
* the                                                          * 
* compressed index, and the operation is rolled back           * 
* thereafter.                                                  * 
* Index manager incorrectly processes the prefix for decimal   * 
* type                                                         * 
* as fixed-length prefix causing a page corruption. A similar  * 
*                                                              * 
* problem is possible for string types, as well when a case    * 
*                                                              * 
* insensitive database is being used.                          * 
*                                                              * 
*                                                              * 
*                                                              * 
* The user will see a severe error in db2diag.log from the     * 
*                                                              * 
* function "procLeaf2Del, probe:2" stating that the index key  * 
*                                                              * 
* could not be found (e.g. SQLI_NOKEY).                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 Fix Pack 1.                       * 
****************************************************************
Local-Fix:
Turn off index compression (via ALTER INDEX and then index 
reorg) for indexes on decimal types in all databases and string 
types in case insensitive databases.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows

Lösung
Fixed in DB2 9.7 Fix Pack 1.  The code in
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
23.06.2009
02.02.2010
02.02.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP1
Problem behoben lt. FixList in der Version
9.7.0.1 FixList