DB2 - Problem description
Problem IC64283 | Status: Closed |
REORG INDEX WITH THE CLEANUP ONLY OPTION OR ASYNCHRONOUS INDEX CLEANUP MAY CAUSE MEMORY CORRUPTION. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
If sequential detection is enabled in a database, DB2 may enter this code path during the reorg index cleanup or asynchronous index cleanup. If index pages are not sequential, sequential detection prefetching can not be performed. Then readahead prefetching will be used. The corruption may occur only if the index has VARCHAR/VARGRPAPHIC columns and the prefetch request list is full at the time the prefetching request is made. | |
Problem Summary: | |
If sequential detection is enabled in a database, DB2 may enter this code path during the reorg index cleanup or asynchronous index cleanup. If index pages are not sequential, sequential detection prefetching can not be performed. Then readahead prefetching will be used. The corruption may occur only if the index has VARCHAR/VARGRPAPHIC columns and the prefetch request list is full at the time the prefetching request is made. | |
Local Fix: | |
The local fix is to recreate the index, disable sequential detection or alter the index tablespace prefetch size to zero. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 9.7 Fix Pack 1. | |
Workaround | |
The local fix is to recreate the index, disable sequential detection or alter the index tablespace prefetch size to zero. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 31.10.2009 01.01.2010 01.01.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP1 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |