00C90205   

Explanation

The data manager detected an inconsistent data condition. In this case, a row obtained from an index entry does not point to a valid row in a data page. The error is probably caused by an extra index entry, but it could also result from a table update not being redone when it should have been.

System action

A record is written to SYS1.LOGREC, and an SVC dump is requested.

Operator response

Collect the console output from the system on which the job was run for the period of time spanning the failure. Save this output for use in problem determination.

System programmer response

If you suspect an error in DB2®, you might need to report the problem. For information about identifying and reporting the problem, see Collecting diagnostic data.

User response

Notify the system programmer.

Problem determination

Message DSNI013I is issued to identify the index page. It identifies the database name, table space name, and index space name. This message is issued for all pages in use at the time of the abend. Within this group of pages, at least one page is involved in the inconsistency. The other pages were present at the time of the abend.

Run the CHECK utility to determine the extent of index inconsistency if:

  • The page type indicated in message DSNI013I is index
  • The page type indicated in message DSNI013I is data
  • There is an index defined on a table in the indicated page set.

The LOC keyword in the dump title gives the Load-module.CSECT:qualifier of the location where the abend occurred. 'Qualifier' is a unique, 4-digit hexadecimal number that identifies the place within the source module (CSECT) where the abend was issued.

SYS1.LOGREC contains information in the variable recording area (VRA) of the system diagnostic work area (SDWA). Significant fields for this abend code are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and VRARRK9.

The name of the CSECT involved is given in VRARRK5. The full CSECT name given in the dump title.

Collect the following diagnostic items:
  • Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
  • Dynamic dump, taken to SYS1.DUMPxx data set, by DB2 (04E and 04F abends).
  • Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.
  • Detailed description of events immediately prior to and during the abend.
  • SYSPRINT output, including JCL, for the application program or batch job, and system messages that were issued. Make sure that MSGLEVEL=(1,1) on the JOB statement so that all diagnostic information is sent to SYSPRINT.
  • DB2 log output, including any DB2 recovery log archive tapes.
  • CHECK utility output.
  • DB2 REPAIR dump of the pages identified in DSNI013I messages.