DB2 - Problembeschreibung
Problem IT05068 | Status: Geschlossen |
POTENTIAL CORRUPTION DURING READAHEAD DATA PREFETCHING WHEN A DECIMAL KEY PART IS USED WITH INDEX COMPRESSION | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
The symptoms that a customer would most likely see are incorrect results from an index only scan, a keydata mismatch error from an iscan fetch, a key not found during an update or delete operation, or duplicates allowed to be inserted into the table. The corruption that could cause these symptoms could occur while doing read ahead prefetching of data pages from an index scan and prefix compression is in affect for the index and index has a decimal key part. The corrupted byte will originally have a value of 0x00 and incorrectly have be changed to 0x0C. The INSPECT command, when run with the INDEXDATA option, will detect such corruption. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users of index compression * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade DB2 version 10.5.0.5. * **************************************************************** | |
Local-Fix: | |
Rebuild the corrupt index using the REORG INDEX(ES) command. | |
Lösung | |
The problem was first fixed in DB2 version 10.5.0.5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 21.10.2014 15.12.2014 09.04.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.5 |