Jump to: navigation, search

What was the error?

Message Number: 13

Message Name: ARS0013E (Corrective action is required to continue)

Message Text: DB Error: text -- SQLSTATE=state, SQLCODE=code, File=file, Line=line


arssockd (ARCHIVE): 05/09/15 02:43:30 73629 ARSLOAD  2 13 DB Error: [IBM][CLI Driver] CLI0122E  Program type out of range. SQLSTATE=HY003 -- SQLSTATE=HY003, SQLCODE=-99999, File=arsdoc.c, Line=4217

ARSMAINT 434684 Error No 13 DB Error: RUNSTATS ON TABLE root.SL25 -- SQLSTATE=Not Defined, SQLCODE=1, File=arssys.c, Line=1287 

What were you doing?

Probably trying to start CMOD, after a new installation, upgrade, or database change. This can also happen when loading data into CMOD and the data presented to the database isn't what is expected. In the example above, a Generic Index File that contained a NULL value was being loaded.

This error message can also occur during database maintenance with the IBM CMOD arsmaint command with the -r option, if there was an error that occurred during database maintenance.

What happened?

Whatever you were working on failed, because CMOD received a message from the database that it wasn't expecting. This is a "pass-through" error that CMOD records in the System Log to assist with troubleshooting & debugging. In many situations, even if the message from the database wasn't critical, CMOD interprets any unexpected message as an error, and stops processing.


This is a generic database error message -- CMOD passes along what little information it receives from the database engine on the error.

If you encountered this error during database maintenance with CMOD's arsmaint command, try running the maintenance command again when the server is less busy, or have your database administrator run the table reorganizations or statistics collection while CMOD is offline.

To find more information on what's causing the error, check your database engine diagnostic logs.

In DB2, the database server diagnostic logs can be found in the sqllib/db2dump directory, primarily in the db2diag.log file.

Refer to your local Database Administrator for assistance in resolving issues with your preferred database engine.

DB2 10.5 Messages Reference

DB2 10.1 Messages Reference

DB2 9.8 Messages Reference

DB2 9.7 Messages Reference

DB2 9.5 Messages Reference