DB2 FOR LUW / DB2FORLUW / B10 - DB2

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

****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* upgrade to Db2 v111m1fp2                                     *
****************************************************************

N/A

not known / see Local fix

forerunner  : IT16369 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

03.08.2017
11.10.2017
11.10.2017