1,126
edits
Difference between revisions of "Unable to create ARCHIVE database"
Jump to navigation
Jump to search
Unable to create ARCHIVE database (view source)
Revision as of 18:14, 6 February 2018
, 18:14, 6 February 2018Added section about deleting contents of database filesystems.
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) |
(Added section about deleting contents of database filesystems.) |
||
| Line 43: | Line 43: | ||
=== DB2 Diagnostics === | === DB2 Diagnostics === | ||
Also, before running the <code>arsdb -crtv</code> command, ensure that the database filesystems (listed in [[ars.dbfs]]) and log filesystems (listed in [[ars.cfg]]) are empty -- delete any remnants of previous databases if you're rebuilding a new IBM Content Manager OnDemand database. | |||
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: | 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: | ||