1,126
edits
Difference between revisions of "Unable to create ARCHIVE database"
Unable to create ARCHIVE database (view source)
Revision as of 23:58, 6 February 2018
, 23:58, 6 February 2018Added section about IBM CMOD ars.cfg overrides local environment variables.
m (Added section about DB2 online help for SQLCODE errors.) |
m (Added section about IBM CMOD ars.cfg overrides local environment variables.) |
||
| Line 39: | Line 39: | ||
* Check that the full directory paths in the OnDemand <code>ars.dbfs</code> configuration file exist, and have the correct permissions -- your database engine may not create these directories for you. | * Check that the full directory paths in the OnDemand <code>ars.dbfs</code> configuration file exist, and have the correct permissions -- your database engine may not create these directories for you. | ||
* Check to ensure the directories referred to in <code>ars.cfg</code> exist, and that you (the database owner) have read, write, and execute permissions. | * Check to ensure the directories referred to in <code>ars.cfg</code> exist, and that you (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]] are identical, and are the same 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]] are identical, and are the same user id of the database owner account. | ||
* Don't trust your environment variables! <code>echo $DB2INSTANCE</code> is NOT the variable that gets used -- the DB2INSTANCE parameter in [[ars.cfg]] will take precedence. | |||
=== DB2 Diagnostics === | === DB2 Diagnostics === | ||