ARS0013E - Revision history

Jderrick: Reformatted the links to the DB2 Message References.

2017-02-10T17:14:01Z

Reformatted the links to the DB2 Message References.

← Older revision		Revision as of 17:14, 10 February 2017
Line 33:		Line 33:
	Refer to your local Database Administrator for assistance in resolving issues with your preferred database engine.		Refer to your local Database Administrator for assistance in resolving issues with your preferred database engine.

			[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.messages.doc/doc/c0052007.html DB2 10.5 Messages Reference]

	~~[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.messages.doc/doc/c0052007.html DB2 10.5 Messages Reference]~~
	[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.messages.doc/doc/c0052007.html DB2 10.1 Messages Reference]		[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.messages.doc/doc/c0052007.html DB2 10.1 Messages Reference]

	[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.8.0/com.ibm.db2.luw.messages.doc/doc/c0052007.html DB2 9.8 Messages Reference]		[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.8.0/com.ibm.db2.luw.messages.doc/doc/c0052007.html DB2 9.8 Messages Reference]

	[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.messages.doc/doc/c0052007.html DB2 9.7 Messages Reference]		[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.messages.doc/doc/c0052007.html DB2 9.7 Messages Reference]

	[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.5.0/com.ibm.db2.luw.messages.doc/doc/c0052007.html DB2 9.5 Messages Reference]		[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.5.0/com.ibm.db2.luw.messages.doc/doc/c0052007.html DB2 9.5 Messages Reference]

Jderrick: Added troubleshooting of CMOD arsmaint errors.

2017-02-10T17:12:34Z

Added troubleshooting of CMOD arsmaint errors.

← Older revision		Revision as of 17:12, 10 February 2017
Line 8:		Line 8:
	Message Text: DB Error: text -- SQLSTATE=state, SQLCODE=code, File=file, Line=line		Message Text: DB Error: text -- SQLSTATE=state, SQLCODE=code, File=file, Line=line

	== ~~Related Errors~~ ==		== Examples ==
	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		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? ==		== 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.		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 occur during database maintenance with the IBM CMOD arsmaint command, if there was an error that occurred during database maintenance.		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? ==		== What happened? ==
Line 22:		Line 24:

	This is a generic database error message -- CMOD passes along what little information it receives from the database engine on the error.		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.		To find more information on what's causing the error, check your database engine diagnostic logs.

Jderrick: /* What were you doing? */

2017-02-10T17:00:13Z

What were you doing?

← Older revision		Revision as of 17:00, 10 February 2017
Line 12:		Line 12:

	== What were you doing? ==		== 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.		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 occur during database maintenance with the IBM CMOD arsmaint command, if there was an error that occurred during database maintenance.

	== What happened? ==		== What happened? ==

Jderrick: Updated error severity text

2015-05-10T01:52:03Z

Updated error severity text

← Older revision		Revision as of 01:52, 10 May 2015
Line 4:		Line 4:
	Message Number: 13		Message Number: 13

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

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

Jderrick: Added an example and 'What happened?'.

2015-05-09T03:07:10Z

Added an example and 'What happened?'.

← Older revision		Revision as of 03:07, 9 May 2015
Line 7:		Line 7:

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

			== Related Errors ==
			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

	== What were you doing? ==		== 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.

	~~Probably trying to start~~ CMOD~~, either after~~ a ~~new installation~~, ~~upgrade~~, ~~load~~, ~~or database change~~.		== 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.

	== Troubleshooting ==		== Troubleshooting ==

Jderrick: /* What were you doing? */

2015-05-09T03:01:36Z

What were you doing?

← Older revision		Revision as of 03:01, 9 May 2015
Line 10:		Line 10:
	== What were you doing? ==		== What were you doing? ==

	Probably trying to start CMOD, either after a new installation, upgrade, or database change.		Probably trying to start CMOD, either after a new installation, upgrade, load, or database change.

	== Troubleshooting ==		== Troubleshooting ==

Jderrick: TOCright

2015-04-29T00:14:39Z

TOCright

← Older revision		Revision as of 00:14, 29 April 2015
Line 1:		Line 1:
			{{TOCright}}

	== What was the error? ==		== What was the error? ==

Jderrick: Reformatting.

2015-04-28T13:45:33Z

Reformatting.

← Older revision		Revision as of 13:45, 28 April 2015
Line 1:		Line 1:

	Message Text: ~~'''~~DB Error: text -- SQLSTATE=state, SQLCODE=code, File=file, Line=line~~'''~~		== What was the error? ==
			Message Number: 13

			Message Name: ARS0013E

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

			== What were you doing? ==

			Probably trying to start CMOD, either after a new installation, upgrade, or database change.

			== Troubleshooting ==

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

Jderrick: Inserted 'Message Text'.

2014-10-26T01:25:32Z

Inserted 'Message Text'.

← Older revision		Revision as of 01:25, 26 October 2014
Line 1:		Line 1:

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

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

Jderrick: Added links to Message Reference Knowledge Centres

2014-10-26T01:24:39Z

Added links to Message Reference Knowledge Centres

← Older revision		Revision as of 01:24, 26 October 2014
Line 1:		Line 1:
	~~== ARS0013E ==~~

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

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

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

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


			[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.messages.doc/doc/c0052007.html DB2 10.5 Messages Reference]
			[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.messages.doc/doc/c0052007.html DB2 10.1 Messages Reference]
			[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.8.0/com.ibm.db2.luw.messages.doc/doc/c0052007.html DB2 9.8 Messages Reference]
			[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.messages.doc/doc/c0052007.html DB2 9.7 Messages Reference]
			[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.5.0/com.ibm.db2.luw.messages.doc/doc/c0052007.html DB2 9.5 Messages Reference]