Difference between revisions of "ARS4019E"

Revision as of 02:23, 24 March 2018

What was the error?

Message Number: 4019

Message Severity: Error

Message Name: ARS4019E

Message Text:

arsdb: ARS4019E Unable to create the DB2 ARCHIVE database

Related errors

ARS4067E Unable to create the archive database.  err=<sqlcode>

What were you doing?

Probably trying to create the database with arsdb -c while installing Content Manager OnDemand.

What happened?

The database creation step failed. You may need to drop the database if it was created, but arsdb wasn't able to finish configuring it.

Troubleshooting

This is is a 'catch-all' error that is produced by arsdb when one of the functions it relies upon has failed. Check the 'Releated Errors' section for error messages that may provide more information.

This error can occur when installing an unsupported version of IBM CMOD with a version of DB2 that is more modern. Specifically, the options related to database transaction logging have changed several times between DB2 v9.0 and v11.1 -- check the db2diag.log file, and see the Troubleshooting Content Manager OnDemand page for more insight.

Revision as of 00:38, 29 April 2015 (view source) Jderrick (talk \| contribs) m (Standardized the layout.) ← Older edit		Revision as of 02:23, 24 March 2018 (view source) Jderrick (talk \| contribs) (IBM CMOD DB2 newer version than originally released.) Newer edit →
Line 25:		Line 25:

	This is is a 'catch-all' error that is produced by [[arsdb]] when one of the functions it relies upon has failed. Check the 'Releated Errors' section for error messages that may provide more information.		This is is a 'catch-all' error that is produced by [[arsdb]] when one of the functions it relies upon has failed. Check the 'Releated Errors' section for error messages that may provide more information.

			This error can occur when installing an unsupported version of IBM CMOD with a version of DB2 that is more modern. Specifically, the options related to database transaction logging have changed several times between DB2 v9.0 and v11.1 -- check the db2diag.log file, and see the [[Troubleshooting Content Manager OnDemand]] page for more insight.