DB2 FOR LUW / DB2FORLUW / A10 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of index compression                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.5.                             * 
****************************************************************

Rebuild the corrupt index using the REORG INDEX(ES) command.

The problem is first fixed in DB2 version 10.1.0.5.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

04.12.2014
10.07.2015
10.07.2015