Difference between revisions of "Unable to create ARCHIVE database"

Jump to navigation Jump to search
m
More diagnostics for IBM CMOD arsdb unable to create database error, added section on IBM CMOD ars.dbfs, added IBM CMOD V10.1 config directory and formatting changes
m (Minor tweaks.)
m (More diagnostics for IBM CMOD arsdb unable to create database error, added section on IBM CMOD ars.dbfs, added IBM CMOD V10.1 config directory and formatting changes)
Line 34: Line 34:
     /opt/IBM/ondemand/V9.0/config
     /opt/IBM/ondemand/V9.0/config
     /opt/IBM/ondemand/V9.5/config
     /opt/IBM/ondemand/V9.5/config
    /opt/ibm/ondemand/V10.1/config


* 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 (the database owner) have read, write, and execute permissions.
* Check for typographical errors in the [[ars.ini]] and [[ars.cfg]] files -- specifically, check the spelling of <code>/arsdb</code>, <code>/arsdb_primarylog</code>, and <code>/arsdb_archivelog</code> or equivalent directories.
* 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.
* 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.
* 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.


=== DB2 Diagnostics ===
=== DB2 Diagnostics ===

Navigation menu