00C90210
Explanation
The data manager detected an inconsistent data condition. In this case, the subpage directory of an index leaf page indicates that a given search key does not belong to any of the subpages. Either this leaf page is the index tree or the nonleaf portion of the index tree lead to this leaf page as the one that should contain the given key.
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 is issued to identify the index page. It also identifies the database 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.
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.
- 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.
- DSN1COPY-generated copy of the index space or table space identified in the DSNI013I messages on tape.