1,126
edits
Difference between revisions of "Unable to create ARCHIVE database"
Jump to navigation
Jump to search
m
Unable to create ARCHIVE database (view source)
Revision as of 18:46, 13 April 2016
, 18:46, 13 April 2016Added db2diag.log location info.
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 | |||