DSNU017I csect-name UTILITY DATA BASE SERVICES MEMORY EXECUTION ABENDED, REASON=X0rrr CAUSE=X0rrr
Explanation
The database services address space has abended. If X'0rrr' is four hexadecimal digits in length (for example, X'00C1'), the abend was an MVS™ X'rrr' abend. If X'0rrr' is eight hexadecimal digits in length, the abend was a Db2 subsystem X'04E' abend, and X'0rrr' is an abend reason code.
If the value of general register 2 is not zero, then cause will contain CAUSE=X'cccccccc' where X'cccccccc' is the value of general register 2. This information is for service purposes only.
For example, one possible reason, among many, for this message is that catalog tables contain invalid data that was updated by the use of SQL statements or by tools. When such updates introduce invalid data, they can cause unpredictable results, including abends for RUNSTATS and other utilities
System action
The utility job is abended. The entry for the job is retained in the SYSIBM.SYSUTIL table.
System programmer response
If an MVS system abend was encountered (4 hexadecimal digits), refer to the appropriate MVS publication. If an abend reason code was encountered (8 hexadecimal digits), look up the reason code. 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.
User response
Consult with the system programmer to obtain information about failure analysis. If the cause of the failure is correctable, the utility job can be restarted. If the error cannot be corrected, the -TERM command should be used to delete the failing job's utility id from SYSIBM.SYSUTIL.
If you suspect that the error is the result of invalid data in the catalog, run the RUNSTATS utility at the table space level to correct the data.