00D70011
Explanation
The data space manager (DSM) subcomponent of Db2 has been requested to extend a table space or index space, but the table space or index space has already been extended to its maximum size. This situation does not mean that no more is space available in the page set for the requested insert. An additional search will be performed for space in the current table space or index space. If space cannot be found, then the data manager component will issue reason code 00C9009C for a partitioned page set or 00C9009D for a non-partitioned page set.
If this condition is encountered when trying to insert into a traditional sort work file, other table spaces in the work file database are searched for space. If none is available, the job fails with a "resource not available" code.
If this condition is encountered for a table space in a work file database when inserting into a DGTT, the job might fail with resource unavailable because other concurrent jobs are competing for storage in the work file database. If it is encountered for DGTT use when no other jobs are running, it indicates the table space is not big enough to hold all the data.
For the name of the data set from which the name of the table space, index space, and/or partition can be derived, see message DSNP001I or DSNP007I and the SQLCA.
System action
No extension is done.
System programmer response
Notify the database administrator if appropriate. Otherwise, if the table space is partitioned and there is space in other partitions, you may be able to redefine the table space with new partitioning parameters so that the data that has overloaded this partition is directed to others. If the table space is not partitioned, you probably have more than one table residing in this table space. Define another table space, unload this one, then reload the tables into the separate spaces. (Be aware that this is a very large amount of data to move. Careful planning is recommended.)
If a large DGTT cannot be contained in a single existing table space in the work file database, consider altering the MAXPARTITIONS attribute to increase the number of partitions if it is a PBG table space, or create larger table spaces. Because you do not control which table space is used, the recommendation is to create all work file table spaces with sufficient space.
User response
If this condition occurs when inserting into a DGTT or sort work file and other concurrent jobs are competing the for storage space, try rerunning the job when the usage is less. If the same condition is encountered for DGTT use when no other jobs are running the table space is not big enough to hold all the data.
If you are unable to resolve the problem yourself, notify the system programmer or database administrator.
Problem determination
If you believe the table space or index space has not yet reached maximum size, provide listings of the console, integrated catalog facility (ICF) catalog, and VTOC.
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.
- 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).
- IDCAMS LISTCAT output for the ICF (VSAM) catalog that contains the Db2 subsystem catalog that defined the failing index or table.
- VTOC listing of the disk volume on which the failing operation occurred.
- Listing of the results produced by the SQL statements.
- Listing of Db2 catalog tables.
- 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 views and tables involved in the error.