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

INSTANCE CRASHES DURING ROLLBACK OF DELETE ON A COMPRESSED INDEX

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
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).
Problem Summary:
**************************************************************** 
* 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.
available fix packs:
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

Solution
Fixed in DB2 9.7 Fix Pack 1.  The code in
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.06.2009
02.02.2010
02.02.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList