DB2 - Problembeschreibung
Problem IT00425 | Status: Geschlossen |
POTENTIAL INDEX CORRUPTION WHEN USING INDEX COMPRESSION AND UNIC ODE DATABASES WHICH USE UCA COLLATION WITH S(STRENGTH) = 1 OR 2 | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
The follow criteria must be met for the potential of index corruption: - Must be an index using index compression and defined with a varying length data type in the index key (excluding binary strings and character strings of the FOR BIT DATA subtype) - Must be a Unicode databases which use UCA collation with S(strength) = 1 or 2 - Must acquire an exclusive lock on the table within the same unit of work as deleting some data from the index (for example, the lock could be the result of escalation or the LOCK TABLE command), followed by rollback of the unit of work. 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 a message like 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 seeing this 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 9.7.0.10. * **************************************************************** | |
Local-Fix: | |
Rebuild the corrupt index using the REORG INDEX(ES) command. | |
Lösung | |
The problem is first fixed in DB2 version 9.7.0.10. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 20.03.2014 07.11.2014 07.04.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.0.10 | |
Problem behoben lt. FixList in der Version | |
9.7.0.10 |