Difference between revisions of "ARS4019E"
(Added more information about CMOD ars.cfg parameters like primarylog and archivelog.) |
(Many updates to CMOD ARS4019E.) |
||
| Line 3: | Line 3: | ||
Message Number: 4019 | Message Number: 4019 | ||
Message Severity: Error | Message Severity: Error (Corrective action is required to continue) | ||
Message Name: ARS4019E | Message Name: ARS4019E | ||
| Line 9: | Line 9: | ||
Message Text: | Message Text: | ||
ARS4019E Unable to create the DB2 ARCHIVE database | |||
== Related errors == | == Related errors == | ||
| Line 22: | Line 22: | ||
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. | ||
== Troubleshooting == | |||
This is is a 'catch-all' error that is produced by [[arsdb]] when one of the tasks it performs while creating and configuring the database has failed. Check the 'Releated Errors' section for error messages that may provide more information. | |||
If you are trying to install CMOD for the first time, ARS4019E is often caused by problems updating the database configuration parameters, such as primarylog and archivelog paths after the database has been created. Ensure the database configuration in [[ars.cfg]] file is correct, especially the paths to the log directories. | |||
$ arsdb -c | |||
ARS4018I Creating the DB2 ARCHIVE database | |||
ARS4119I Specify the type of archive logging to be used: | |||
Do you wish to use DISK(1), TSM(2), or CIRCULAR(3)? | |||
Please specify 1, 2, or 3:1 | |||
ARS4064E The ARCHIVE database already exists | |||
ARS4019E Unable to create the DB2 ARCHIVE database | |||
[[File:Attention.png|70px|left]] '''WARNING''': Only run this command if you are trying to install a CMOD server for the first time, and your previous attempts are running the [[arsdb]] command with the -c ('create') option were not successful. ENSURE that you are using the correct database name, or you could accidentally remove the wrong database! | |||
$ db2 drop database archive | |||
DB20000I The DROP DATABASE command completed successfully. | |||
The database that was created in a previous attempt has been deleted. | |||
Try running the <code>arsdb -c</code> command again. | |||
If this doesn't resolve your issue, you will need to review the configuration of the database, and ensure things like primary and archive logging settings are correct before proceeding. Refer to your local database administrator, or considering obtaining assistance with your Content Manager OnDemand installation with [https://cmod.cloud/professionalservices/ IBM CMOD Professional Services]. | |||
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. | This error can also 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. | ||
Latest revision as of 04:33, 24 May 2020
What was the error?
Message Number: 4019
Message Severity: Error (Corrective action is required to continue)
Message Name: ARS4019E
Message Text:
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 tasks it performs while creating and configuring the database has failed. Check the 'Releated Errors' section for error messages that may provide more information.
If you are trying to install CMOD for the first time, ARS4019E is often caused by problems updating the database configuration parameters, such as primarylog and archivelog paths after the database has been created. Ensure the database configuration in ars.cfg file is correct, especially the paths to the log directories.
$ arsdb -c ARS4018I Creating the DB2 ARCHIVE database ARS4119I Specify the type of archive logging to be used: Do you wish to use DISK(1), TSM(2), or CIRCULAR(3)? Please specify 1, 2, or 3:1 ARS4064E The ARCHIVE database already exists ARS4019E Unable to create the DB2 ARCHIVE database
WARNING: Only run this command if you are trying to install a CMOD server for the first time, and your previous attempts are running the arsdb command with the -c ('create') option were not successful. ENSURE that you are using the correct database name, or you could accidentally remove the wrong database!
$ db2 drop database archive DB20000I The DROP DATABASE command completed successfully.
The database that was created in a previous attempt has been deleted.
Try running the arsdb -c command again.
If this doesn't resolve your issue, you will need to review the configuration of the database, and ensure things like primary and archive logging settings are correct before proceeding. Refer to your local database administrator, or considering obtaining assistance with your Content Manager OnDemand installation with IBM CMOD Professional Services.
This error can also 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.