DB2 - Problem description
Problem IC67759 | Status: Closed |
INDEX PAGE CLEANUP INCORRECTLY MARKS DELETED KEY AS NOT DELETED WHEN USING INDEX COMPRESSION | |
product: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problem description: | |
The problem occurs when running inserts, updates and deletes on a table with indexes that use index compression. The index manager temporarily clears the deleted flag from a key before performing clean up on the page for the purpose of keeping that key on the page. There is a scenario in which the index manager fails to reset the deleted flag on the key. This can result in the following symptoms: - extra data being returned when using an index scan - index/data mismatches detected by DB2's INSPECT command | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * The problem occurs when running inserts, updates and deletes * * on a table with indexes that use index compression. The * * index manager temporarily clears the deleted flag from a key * * before performing clean up on the page for the purpose of * * keeping that key on the page. There is a scenario in which * * the index manager fails to reset the deleted flag on the * * key. This can result in the following symptoms: * * * * - extra data being returned when using an index scan * * * * - index/data mismatches detected by DB2's INSPECT command * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 9.8.2. * **************************************************************** | |
Local Fix: | |
Drop and recreate the affected index. | |
Solution | |
The problem was first fixed in DB2 9.8.2. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.04.2010 12.10.2010 12.10.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.8.2 | |
Problem solved according to the fixlist(s) of the following version(s) |