Start of change

00C90089   

Explanation

The environmental descriptor manager (EDM) function of the data manager subcomponent did not have enough storage in its pool or data space to retrieve the object. The object can be either a database descriptor (DBD), a skeleton cursor table (SKCT), or a skeleton package table (SKPT). The object is identified by a DBD ID, SKCT plan name, or SKPT package name.

System action

The requested operation is not performed.

User response

Invoke the application again. If, after several attempts, EDM still reports that not enough space is available, take the following actions to reduce EDM storage requirements:
  • Reduce the number of concurrent users that are using DB2®.
  • Try reducing the number of SQL statements in the plan or package and rebind.
  • Try to simplify the database design. For example, reduce the number of partitions in the database.

If EDM storage shortage is a recurring problem, change the relevant subsystem parameters on installation panel DSNTIPC to increase the EDM pool size definition. Increase the number of concurrent users and the number of currently active databases. Then, restart DB2.

If a utility that uses a LISTDEF list was run and that list includes a large number of databases, the EDM DBD pool might be full. To see the size of each database DBD, use the DISPLAY DATABASE command. If the EDM DBD pool is full, decrease the size of your LISTDEF contents to eliminate this condition. If this condition occurs frequently, increase the size of your EDM DBD pool. For guidance, see Calculating EDM pool sizes.

Problem determination

The requested operation is not performed. One ore more of the following messages are also issued:
  • SQLCODE -904
  • SQLCODE -923
  • DSNT500I

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.
End of change