00C90094   

Explanation

A data set is in a different state than DB2® expects, which might occur as a result of the following situations:
  • A data set was deleted and redefined, but DB2 does not recognize the redefined data set.
  • A previous DB2 failure damaged the data set in some way.

System action

The requested action is not performed. If the invoker of this module abends, a record is written to SYS1.LOGREC, and the invoker might initiate a dump. If the invoker does not abend, no record is written, and no dump is requested. If this occurs, an SQL return code is issued, or message DSNT500I is issued, or both. The data set is placed in a stopped status unless the invoker of the module is a utility.

Operator response

Notify the system programmer.

System programmer response

If you do not have the current level of the data set, you must perform DB2 recovery to return the data set to its expected state. See the Problem Determination section of this message to learn how to determine the name of the data set to be corrected. Use the DISPLAY command to check the status of the data set. If the data set is stopped, use the START command before performing recovery.

User response

If the code was received while processing a user table, DB2 determined that the data set is empty. A DROP TABLESPACE statement followed by a CREATE TABLESPACE statement and a CREATE TABLE statement defines the dropped table to DB2. Use the IDCAMS LISTCAT for the failing DB2 data set. Check the HI-USED-RBA for this data set; if HI-USED-RBA = 0, the data set is empty.

Problem determination

This error is detected at a time when DB2 cannot determine the specific name of the data set involved. However, the SQL return code or message DSNT500I provides the name of the table space or index space where the data set resides. When the table or index space consists of a single data set, this is specific. Otherwise, the system programmer must find the particular data set within the table or index space.

SYS1.LOGREC contains information in the variable recording area (VRA) of the system diagnostic work area (SDWA). Significant fields for this code are: VRARRK13, VRARRK14, and VRARRK15. 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.

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.
  • SVC dump (or system dump), taken to SYS1.DUMPxx data set, as result of an operator-initiated dump command or SLIP trap exit.
  • Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.
  • IDCAMS LISTCAT output for the ICF (VSAM) catalog that contains the DB2 subsystem catalog that defined the failing index or table.
  • 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.
  • Definitions of views and tables involved in the error.