00C90214   

Explanation

The data manager detected a condition of inconsistent data. The description of the index in the index OBD does not match the attributes of an index page. The problems consists of one of the following conditions:

  • IPPNUNI does not equal OBDKNUNI,
  • IPPTLTH does not equal OBDKLEN,
  • IPPOLTH does not equal OBDLENO, or
  • If the page is a leaf page, the segmentation flag or number of subpages conflict (IPPNLPG does not equal OBDINLPG or IPPSEGM conflicts with OBDINLPG).

The index space may have been improperly restored by using DSN1COPY or the wrong data set may have been copied for the given index.

System action

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

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 will be issued for each index page. It identifies the database, and the index 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.

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.

Refer to ABEND codes associated with DSN1COPY misuse for further information on DSN1COPY misuse.

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.
  • DB2 REPAIR dump of the pages identified in DSNI013I messages.
  • DB2 REPAIR dump of the header page (page 0) for each index identified in the DSNI013I messages.
  • DSN1COPY-generated copy, on tape, of the page set that contains the DB2 directory. Alternatively, request a dump (produced by the REPAIR utility, DSN1COPY, or DSN1PRNT) of the DBD for each database identified in the DSNI013I messages.
.