|
Problem IT05940
|
Status: Closed |
POTENTIAL CORRUPTION DURING READAHEAD DATA PREFETCHING WHEN A DECIMAL KEY PART IS USED WITH INDEX COMPRESSION |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of index compression *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1.0.5. *
**************************************************************** |
| Local Fix: |
Rebuild the corrupt index using the REORG INDEX(ES) command. |
| Solution |
The problem is first fixed in DB2 version 10.1.0.5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.12.2014
10.07.2015
10.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
