Difference between revisions of "Unable to create ARCHIVE database"
m (Updated error severity text) |
m (Added db2diag.log location info.) |
||
| Line 30: | Line 30: | ||
* Check to ensure the directories referred to in ars.cfg exist, and that you (or the database owner) have read, write, and execute permissions. | * Check to ensure the directories referred to in ars.cfg exist, and that you (or the database owner) have read, write, and execute permissions. | ||
* In installations where the database owner and CMOD Admin account are different, ensure that the SRVR_INSTANCE_OWNER in [[ars.ini]] and DB2INSTANCE parameter in [[ars.cfg]] is equal to each other, and are the user id of the database owner account. | * In installations where the database owner and CMOD Admin account are different, ensure that the SRVR_INSTANCE_OWNER in [[ars.ini]] and DB2INSTANCE parameter in [[ars.cfg]] is equal to each other, and are the user id of the database owner account. | ||
=== DB2 Diagnostics === | |||
If the above hints for configuring CMOD don't help, consider checking the db2diag.log file. You can find db2diag.log inside your instance directory, inside the db2dump subdirectory. On a standard install, it should be located here: | |||
/home/archive/sqllib/db2dump/db2diag.log | |||
Revision as of 18:46, 13 April 2016
What was the error?
Message Number: 4067
Message Severity: Error (Corrective action is required to continue)
Message Name: ARS4067E
Message Text: Unable to create the archive database. err=<sqlcode>
Related errors
arsdb: ARS4019E Unable to create the DB2 ARCHIVE database
What were you doing?
Probably trying to create the database while installing Content Manager OnDemand.
Example
ARS4067E Unable to create the archive database. err=<sqlcode>
Troubleshooting
This is a frustratingly generic and non-descript error message generated when the arsdb -cv command can't create the database. There's no single thing to check for, except reviewing all your configuration steps for the correct information.
Here are some of the most basic things to review:
- Check that you have permission to read the configuration files in the 'config' directory.
- Check for typographical errors in the ars.ini and ars.cfg files.
- Check to ensure the directories referred to in ars.cfg exist, and that you (or the database owner) have read, write, and execute permissions.
- In installations where the database owner and CMOD Admin account are different, ensure that the SRVR_INSTANCE_OWNER in ars.ini and DB2INSTANCE parameter in ars.cfg is equal to each other, and are the user id of the database owner account.
DB2 Diagnostics
If the above hints for configuring CMOD don't help, consider checking the db2diag.log file. You can find db2diag.log inside your instance directory, inside the db2dump subdirectory. On a standard install, it should be located here:
/home/archive/sqllib/db2dump/db2diag.log