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

MISSING INDEX KEY OR WRONG RESULT WHEN USING EXCLUDE NULL KEYS RANDOM
INDEXES AFTER SOME DATA PARTITION ATTACH OPERATION

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
The following criteria must be met for the potential of index 
corruption: 
- Must be a nonpartitioned index on a range partitioned table 
that was defined using random ordering and the EXCLUDE NULL KEYS 
clause of the CREATE INDEX statement 
- Must have done an attach of a data partition after the 
nonpartitioned index was created 
- Must have executed the SET INTEGRITY statement after the 
attach operation 
 
The corruption will result in a key mismatch between the table 
and index and can manifest in different ways. However, it will 
most commonly show up during a subsequent delete operation with 
messages similar to the following: 
 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command. During SQL 
processing it returned: 
SQL0901N  The SQL statement or command failed because of a 
database system error. (Reason "Key data mismatch encountered 
during key delete".) SQLSTATE=58004 
 
Note that this is a common symptom to other problems so if you 
receive the errors that are mentioned above is not conclusive 
that you hit this problem. 
 
Also, note the corruption might go undetected for some time 
after being introduced. To detect the problem, you can run 
INSPECT with the INDEXDATA option.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.4.                             * 
****************************************************************
Local-Fix:
Rebuild the corrupt index using the REORG INDEX(ES) command.
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
The problem is first fixed in DB2 version 10.5.0.4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
24.06.2014
08.09.2014
09.04.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList