00C90219
Explanation
The data manager detected an inconsistent data condition in a segmented table space. In this case, an allocated segment was found on a wrong segment chain (that is, a segment chain contains a segment that belongs to a different table).
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 space map page that contains the bad segment entry. The database name and table space name will also be identified.
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.
Refer to ABEND codes associated with DSN1COPY misuse for further information on DSN1COPY misuse.
- 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.
- SVC dump (or system dump), taken to SYS1.DUMPxx data set, as result of an operator-initiated dump command or SLIP trap exit.
- 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.
- Definitions of table spaces, tables, and indexes involved in the error.