Unable to create ARCHIVE database

From CMOD.wiki
Jump to navigation Jump to search

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.


ARS4067E Unable to create the archive database.  err=<sqlcode>


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...

CMOD Configuration Diagnostics

  • 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 -- specifically, check the spelling of /arsdb, /arsdb_primarylog, and /arsdb_archivelog or equivalent directories.
  • Check that the full directory paths in the OnDemand ars.dbfs 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 ars.cfg 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.
  • Don't trust your environment variables! echo $DB2INSTANCE is NOT the variable that gets used -- the DB2INSTANCE parameter in ars.cfg will take precedence.

DB2 Diagnostics

Also, before running the arsdb -crtv 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:


Try searching for the SQL return code in the Messages & Codes References, or use the online help:

At a UNIX shell prompt:

  $ db2 "? sql-1390"

IBM DB2 v9.5 Messages & Codes Reference Volume 1 Volume 2

IBM DB2 v10.1 Messages & Codes Reference Volume 1 Volume 2

IBM DB2 v10.5 Messages & Codes Reference Volume 1 Volume 2

Try searching in the format SQL#### - where #### is the zero-padded return code, like "SQL0326".