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

INDEX PAGE CLEANUP INCORRECTLY MARKS DELETED KEY AS NOT DELETED WHEN USING
INDEX COMPRESSION

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The problem occurs when running inserts, updates and deletes on 
a table with indexes that use index compression.  The index 
manager temporarily clears the deleted flag from a key before 
performing clean up on the page for the purpose of keeping that 
key on the page.  There is a scenario in which the index manager 
fails to reset the deleted flag on the key.  This can result in 
the following symptoms: 
- extra data being returned when using an index scan 
- index/data mismatches detected by DB2's INSPECT command
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of index compression.                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The problem occurs when running inserts, updates and deletes * 
* on a table with indexes that use index compression.  The     * 
* index manager temporarily clears the deleted flag from a key * 
* before performing clean up on the page for the purpose of    * 
* keeping that key on the page.  There is a scenario in which  * 
* the index manager fails to reset the deleted flag on the     * 
* key.  This can result in the following symptoms:             * 
* - extra data being returned when using an index scan         * 
* - index/data mismatches detected by DB2's INSPECT command    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7.2.                                * 
****************************************************************
Local-Fix:
Drop and recreate the affected index.
verfügbare FixPacks:
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 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 9a 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
The fix is contained in DB2 version 9.7.2.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC67759 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.04.2010
23.04.2010
23.04.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList