DB2 - Problembeschreibung
Problem IC64283 | Status: Geschlossen |
REORG INDEX WITH THE CLEANUP ONLY OPTION OR ASYNCHRONOUS INDEX CLEANUP MAY CAUSE MEMORY CORRUPTION. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
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. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
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. | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 31.10.2009 01.01.2010 01.01.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP1 | |
Problem behoben lt. FixList in der Version | |
9.7.0.1 |