00E40197
Explanation
Db2 detected an error while deleting rows from the catalog history table.
System action
Utilities processing is abended. The abend might be accompanied by message DSNT500I. An SDUMP might be taken.
User response
Correct the 'resource unavailable' condition that is identified by the DSNT500I message, terminate the utility, and start it again from the beginning.
If DSNT500I was not issued, register 2 contains a secondary Db2 reason code that gives more information about the problem. If the secondary reason code is not documented here, it is an internal IBM® code.
Problem determination
If the condition cannot be corrected, determine the failing environment. 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.
- SVC dump (or system dump), taken to SYS1.DUMPxx data set, as result of an operator-initiated dump command or SLIP trap exit.
- SYSABEND, SYSUDUMP, or SYSMDUMP output.
- A listing of the 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.
- UTPRINT output, produced by utility invocation of SORT.