00C90105   

Explanation

An inconsistent page was detected. This has been caused by a DB2® internal error.

System action

A record is written to SYS1.LOGREC, an SVC dump is requested, and the page will be scheduled for automatic recovery. If automatic recovery is successful, message DSNB215I is issued. If automatic recovery fails, message DSNI012I is issued, and an abend '04E' with reason code 00C90102 will occur.

Note: If the resource required for automatic recovery is in use, automatic recovery will be delayed until the resource is available.

System programmer response

Check whether an application issues an ALTER TABLE statement and an INSERT statement in the same commit scope. In such cases, you might resolve the situation by adding a COMMIT statement between the ALTER TABLE and INSERT statements.

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.

Problem determination

SYS1.LOGREC contains information in the variable recording area (VRA) of the system diagnostic work area (SDWA). Significant fields for this code are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and VRARRK9. Exceptions to the table definitions of the VRA fields are:
  • VRARRK5 is the name of the module that called the check page routine that detected the error in the page.
  • VRARRK6 identifies the error in the page.
The following general purpose registers (GPRs) contain the indicated diagnostic information:
GPR
Content
2
Address of the page set block (PB)
3
Address of the log record, if any
8
Address of the buffer block (BB)
9
Address of the page buffer

Also, refer to ABEND codes associated with DSN1COPY misuse for further information on DSN1COPY misuse.

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.
  • Listing of DB2 log output.
  • Dump of the index or table space that failed.
  • 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.