IBM Support

Logical index corruption

Troubleshooting


Problem

Two scenarios for index corruption.
A) Logical index corruption trying to delete record which does not exist. db2dart will not detect this
B) FODC_Indexerror. SQLI_NOKEY "Key not found within node"

Symptom


Scenario A: Logical index corruption on delete
Attempting to delete record that has already been deleted from index. db2dart will not detect this type of corruption

FUNCTION: DB2 UDB, data management, sqldDeleteRow, probe:2389
RETCODE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data Page"
          DIA8500C A data file error has occurred, record id is "".
2021-01-01-10.41.00.569000+060 I3992F643            LEVEL: Severe
PID     : 4196                 TID : 4544           PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000           DB   : SAMPLE
APPHDL  : 0-1302               APPID: XX.XX.XX.XX.57877.201229025148
UOWID   : 22268                ACTID: 1
AUTHID  : db2inst1              HOSTNAME: test
EDUID   : 4544                 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary logging function), probe:30
MESSAGE : PAGE OBJECT IDENTIFIERS:
DATA #1 : String, 52 bytes
Tablespace ID = 4, Object ID = 589, Object Type = 0
2021-01-01-14.00.16.672000+060 I6669841F601         LEVEL: Severe
PID     : 4148                 TID : 4688           PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000           DB   : SAMPLE
APPHDL  : 0-146                APPID: XX.XX.XX.XX.64726.201230120030
UOWID   : 736                  ACTID: 1
AUTHID  : db2inst1              HOSTNAME: test
EDUID   : 4688                 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary logging function), probe:30
MESSAGE : SLOT DIRECTORY:
DATA #1 : String, 19 bytes
Record Offset = -1
2021-01-01-10.41.00.647000+060 I22351F597           LEVEL: Severe
PID     : 4196                 TID : 4544           PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000           DB   : SAMPLE
APPHDL  : 0-1302               APPID: XX.XX.XX.XX.57877.201229025148
UOWID   : 22268                ACTID: 1
AUTHID  : db2inst1              HOSTNAME: test
EDUID   : 4544                 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary logging function), probe:30
MESSAGE : SLOT DIRECTORY:
DATA #1 : String, 15 bytes
Record Deleted /* Attempt to delete a row which has already been deleted */
2021-01-01-10.41.00.678000+060 I27650F635           LEVEL: Severe
PID     : 4196                 TID : 4544           PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000           DB   : SAMPLE
APPHDL  : 0-1302               APPID: XX.XX.XX.XX.183.57877.201229025148
UOWID   : 22268                ACTID: 1
AUTHID  : db2inst1              HOSTNAME: test
EDUID   : 4544                 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary logging function), probe:30
MESSAGE : SQLD_CCB:
DATA #1 : String, 57 bytes
pool(TID)=65530, obj(FID)=32829, indexid(IID)=1, class=48
2021-01-01-10.41.00.772000+060 I42107F623           LEVEL: Severe
PID     : 4196                 TID : 4544           PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000           DB   : SAMPLE
APPHDL  : 0-1302               APPID: XX.XX.XX.XX.57877.201229025148
UOWID   : 22268                ACTID: 1
AUTHID  : db2inst1              HOSTNAME: test
EDUID   : 4544                 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary logging function), probe:30
MESSAGE : SQLD_TCB:
DATA #1 : String, 44 bytes
Perm Table(4:589)=TPC     .T_PRF_SWITCH_PORT /* This is the table the index belongs to */
Due to errors above, database is marked bad by DB2.

MESSAGE : ADM7518C  The database manager has shut down the following database
          because a severe error has occurred: "SAMPLE   ".
MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
          DIA8414C Logging can not continue due to an error.
Scenario B: FODC_IndexError, SQLI_NOKEY
MESSAGE : ADM14005E  The following error occurred: "IndexError".  First
          Occurrence Data Capture (FODC) has been invoked in the following
          mode: "Automatic".  Diagnostic information has been recorded in the
          directory named
          "C:\PROGRAMDATA\IBM\DB2\DB2COPY1\DB2\DIAG0000\FODC_IndexError_2021-01
          -01-12.56.20.955000_4148_5016_000\".
2021-01-01-12.56.20.986000+060 I6500676F1667        LEVEL: Severe
PID     : 4148                 TID : 5016           PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000           DB   : SAMPLE
APPHDL  : 0-42                 APPID: XX.XX.XX.XX.64549.201230115625
UOWID   : 2                    ACTID: 2
AUTHID  : db2inst1              HOSTNAME: test
EDUID   : 5016                 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, index manager, sqlischd, probe:875
RETCODE : ZRC=0x8709002C=-2029453268=SQLI_NOKEY "Key not found within node"
          DIA8541C The index key could not be found, the value was "".
2021-01-01-12.56.20.986000+060 I6503232F607         LEVEL: Severe
PID     : 4148                 TID : 5016           PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000           DB   : SAMPLE
APPHDL  : 0-42                 APPID: XX.XX.XX.XX.64549.201230115625
UOWID   : 2                    ACTID: 2
AUTHID  : db2inst1              HOSTNAME: test
EDUID   : 5016                 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, index manager, sqlischd, probe:99
MESSAGE : Index object = {TBSPACEID=<7>; OBJECTID=<3081>}
Parent object = {TBSPACEID=<7>; OBJECTID=<3081>}

Document Location

Worldwide

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"ARM Category":[{"code":"a8m500000008PlAAAU","label":"Corruption-\u003EIndex Corruption"}],"ARM Case Number":"TS004660168","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
01 May 2025

UID

ibm16402527