DB2 FOR LUW / DB2FORLUW / B50 - DB2

Reorg Table Reclaim Extents on Insert Time Clustering (ITC)
Tables can result in FODC_IndexError with very high number of
concurrent updates or inserts reusing empty blocks

The following messages and stack trace can be reported by REORG
TABLE RECLAIM EXTENTS on Insert Time Clustering (ITC) tables
when a block attempting to be reclaimed by REORG that was reused
by concurrent updates or inserts during early phases of the
REORG TABLE RECLAIM EXTENTS utility.

Blocks will be cached by REORG TABLE RECLAIM EXTENTS as
candidates for reclaim processing. In subsequent phases, REROG
consolidates and reclaims extents back to the table space.

In rare scenarios the reuse of those cached blocks by concurrent
insert and update transactions can lead to the following
messages and error stack trace:

2020-06-09-18.09.28.303939-300 I3411194A613         LEVEL:
Severe
PID     : 38077338             TID : 104188         PROC :
db2sysc 0
INSTANCE: inst                 NODE : 000           DB   :
dbname
APPHDL  : 0-11373              APPID: *LOCAL.db2p11.200609213725
AUTHID  : authid               HOSTNAME: hostname
EDUID   : 104188               EDUNAME: db2agent (P11) 0
FUNCTION: DB2 UDB, sqldb, sqldbOlrDeleteEmptyITCBlock,
probe:1249
DATA #1 : zrid, PD_TYPE_SQLZ_RID, 8 bytes
Page=13172100; Slot=0; Dpid=0
DATA #2 : Page ID, PD_TYPE_SQLZ_PAGE_ID, 4 bytes
13172100
DATA #3 : unsigned integer, 4 bytes
6586050

2020-06-09-18.09.28.313495-300 I3411808A585         LEVEL: Error
PID     : 38077338             TID : 104188         PROC :
db2sysc 0
INSTANCE: inst                 NODE : 000           DB   :
dbname
APPHDL  : 0-11373              APPID: *LOCAL.db2p11.200609213725
AUTHID  : authid               HOSTNAME: hostname
EDUID   : 104188               EDUNAME: db2agent (P11) 0
FUNCTION: DB2 UDB, sqldb, sqldbOlrDeleteEmptyITCBlock,
probe:1259
RETCODE : ZRC=0x8709002C=-2029453268=SQLI_NOKEY "Key not found
within node"
          DIA8541C The index key could not be found, the value
was "".


pthread_kill + 0xD4
sqloDumpEDU + 0x9C
IPRA.$sqlischdDumpData__FP7SQLI_CBP11SQLI_SDGLOBi + 0x730
sqlischd__FP7SQLI_CBP11SQLI_SDGLOBUsUi + 0x2A4C
sqlidelk__FP8sqeAgentP9SQLD_IXCBP10SQLI_IXPCRP8SQLD_KEY8SQLZ_RID
UlP16SQLB_OBJECT_DESC + 0x12BC
sqldVirtualColumnDeleteKey__FP8sqeAgentP13SQLD_DFM_WORK8SQLZ_RID
UsUl + 0x10C
sqldbOlrDeleteEmptyITCBlock__FP8sqeAgentP13SQLD_DFM_WORKP8SQLD_T
CB + 0xC54
sqldOLRCleanup__FP13SQLD_DFM_WORKi + 0x2240
sqldDoCleanupLogEndMovePhase__FP8sqeAgentP13SQLD_DFM_WORKiPv +
0x5E4
sqldbPerformItcOlrRowMovement__FP8sqeAgentP13SQLD_DFM_WORKP18SQL
D_OLR_INTERRUPTP8SQLD_TCB + 0x6B4
sqldOnlineTableReorg__FP8sqeAgentUsT2UcUliN22PcT6T9T6P9SQLP_LSN8
T13_sT6 + 0x4778
sqlrreorg_table__FP8sqlrr_cbUsT2P8sqlrg_idT2iT6UlN26sPUcT6T12_N2
6T11_UcT6 + 0x1B94
sqlrreorg_sendinfo__FP14db2UCinterfacei + 0x2850
sqlrr_reorg__FP14db2UCinterfacei + 0x27C
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5
sqlca + 0x6CC
sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo + 0x1780
sqljs_ddm_excsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0x4C4
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interface + 0x280
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb +
0x2264
IPRA.$sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0xE9C
sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4
IPRA.$sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x13F0
sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0x33C
RunEDU__8sqeAgentFv + 0xB60
EDUDriver__9sqzEDUObjFv + 0x300
sqloEDUEntry + 0x360

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Apply v11.5.7.0 to DB2 server                                *
****************************************************************

Restart Database and re-issue REORG TABLE RECLAIM EXTENTS with
minimal activity. Without high levels of concurrent activity
this timing scenario is very hard to hit

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Apply v11.5.7.0 to DB2 server                                *
****************************************************************

First fixed in DB2 v11.5.7.0

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

22.04.2021
23.08.2021
23.08.2021