DB2 - Problem description
Problem IT21737 | Status: Closed |
INSTANCE MIGHT CRASH WHEN WHEN THE RID WAS DELETED FROM INDEX AND MDC TABLE | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
The rid exists at some point in the index and MDC table - the rid was deleted from index and MDC table - since this is MDC table if the extent was emptied, it can be reused and particular slot will no longer be there - for the rid index scan part, it scans the deleted rid and returned it if there is no need for row locking, this can happen for a partitioned table; the scan sees the rid and returned it - row fetch tries to fetch the deleted rid to validate it is not deleted but didn't expect the slot count has been reduced and panic'd | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * upgrade to Db2 v111m1fp2 * **************************************************************** | |
Local Fix: | |
N/A | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT16369 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.08.2017 11.10.2017 11.10.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |