00C9008F   

Explanation

The database descriptor's size (DBD) has reached the limit of 25% of the EDM Pool size.

System action

The request to create/alter a database object is not allowed.

User response

Create the database object in a different database or drop unused database objects from the database. If you drop an object that is an index or a table space, the space becomes available in the DBD as soon as the drop is committed. If you drop an object that is a table, the space in the DBD is made available only after all of the following events:
  • The DROP is committed.
  • The DB2® REORG is run on the table space and there is no point in time recover after the REORG.
  • MODIFY is run to delete all image copies of data that contains rows of the dropped table, that is, copies that were taken before the REORG. Note that MODIFY will reclaim space in the DBD only if there are SYSCOPY rows to delete.

Problem determination

The requested operation is not performed. An SQLCODE -904 is issued, and/or message DSNT500I is issued.

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.
  • 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.
.