Difference between revisions of "ARS4019E"
(IBM CMOD DB2 newer version than originally released.) |
(Added more information about CMOD ars.cfg parameters like primarylog and archivelog.) |
||
| Line 21: | Line 21: | ||
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. | 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. | ||
This is often caused by problems updating the database configuration parameters, such as primarylog and archivelog paths. Ensure the database configuration in [[ars.cfg]] file is correct, especially the paths to the log directories. | |||
== Troubleshooting == | == Troubleshooting == | ||
Revision as of 04:22, 24 May 2020
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.
This is often caused by problems updating the database configuration parameters, such as primarylog and archivelog paths. Ensure the database configuration in ars.cfg file is correct, especially the paths to the log directories.
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.