Difference between revisions of "Unable to create ARCHIVE database"
Jump to navigation
Jump to search
m (Updated error severity text) |
(Major overhaul - consolidated troubleshooting tasks, plus reformatting to make the individual steps more distinct. Added DB2 reference links for v11.1 and v11.5, removed v9.5.) |
||
| (9 intermediate revisions by the same user not shown) | |||
| Line 15: | Line 15: | ||
== What were you doing? == | == What were you doing? == | ||
Probably trying to create the database | Probably trying to create the database after installing Content Manager OnDemand. | ||
== Example == | == Example == | ||
| Line 24: | Line 24: | ||
This is a frustratingly generic and non-descript error message generated when the <code> [[arsdb]] -cv </code> command can't create the database. There's no single thing to check for, except reviewing all your configuration steps for the correct information. | This is a frustratingly generic and non-descript error message generated when the <code> [[arsdb]] -cv </code> 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 | Here are some of the most basic things to review... | ||
* Check that you have permission to read the configuration files in the 'config' directory. | === CMOD Configuration Diagnostics === | ||
* Check that you have permission to read the configuration files in the 'config' directory | |||
/usr/lpp/ars/config | |||
/opt/ondemand/config | |||
/opt/IBM/ondemand/V9.5/config | |||
/opt/ibm/ondemand/V10.1/config | |||
/opt/ibm/ondemand/V10.5/config | |||
; Ensure SRVR_INSTANCE OWNER and DB2INSTANCE are the same! | |||
: Inside [[ars.ini]] the SRVR_INSTANCE_OWNER needs to be the local user name defined to the operating system, usually 'archive' but often 'odadmin' or 'cmodadm' or 'arsadm' or 'cmodprod'. | |||
: Inside [[ars.cfg]] the DB2INSTANCE parameter needs to be the SAME as what you used in the prior step! | |||
: In installations where the database owner and CMOD Admin account are different, use the DATABASE owner's account (db2inst1, cmoddba, etc.) | |||
; 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. | |||
; Check <code>ars.dbfs</code> configuration | |||
: Ensure this filesystem file exists, and have the correct permissions -- your database engine may not create these directories for you! | |||
: Check the filesystem itself -- if there are leftover directories and files in /arsdb, or your primary and archive log filesystems, database creation will fail. | |||
; Don't trust your environment variables! | |||
: If you run <code>echo $DB2INSTANCE</code> in your login shell, this is NOT the variable that gets used -- the DB2INSTANCE parameter in [[ars.cfg]] will take precedence. | |||
=== DB2 Diagnostics === | |||
This is a repeat, but it's important! 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: | |||
/home/archive/sqllib/db2dump/db2diag.log | |||
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 v10.1 Messages & Codes Reference [http://public.dhe.ibm.com/ps/products/db2/info/vr101/pdf/en_US/DB2MessageRefVol1-db2m1e1010.pdf Volume 1] [http://public.dhe.ibm.com/ps/products/db2/info/vr101/pdf/en_US/DB2MessageRefVol2-db2m2e1010.pdf Volume 2] | |||
IBM DB2 v10.5 Messages & Codes Reference [http://public.dhe.ibm.com/ps/products/db2/info/vr105/pdf/en_US/DB2MessageRefVol1-db2m1e1050.pdf Volume 1] [http://public.dhe.ibm.com/ps/products/db2/info/vr105/pdf/en_US/DB2MessageRefVol2-db2m2e1050.pdf Volume 2] | |||
IBM DB2 v11.1 Messages Reference [https://www.ibm.com/docs/en/db2/11.1?topic=reference-messages Messages Reference] | |||
IBM DB2 v11.5 Messages Reference [https://www.ibm.com/docs/en/db2/11.5?topic=content-messages Messages Reference] | |||
Try searching in the format SQL#### - where #### is the zero-padded return code, like "SQL0326". | |||
Latest revision as of 18:35, 30 October 2024
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 after installing Content Manager OnDemand.
Example
ARS4067E Unable to create the archive database. err=<sqlcode>
Troubleshooting
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
/usr/lpp/ars/config /opt/ondemand/config /opt/IBM/ondemand/V9.5/config /opt/ibm/ondemand/V10.1/config /opt/ibm/ondemand/V10.5/config
- Ensure SRVR_INSTANCE OWNER and DB2INSTANCE are the same!
- Inside ars.ini the SRVR_INSTANCE_OWNER needs to be the local user name defined to the operating system, usually 'archive' but often 'odadmin' or 'cmodadm' or 'arsadm' or 'cmodprod'.
- Inside ars.cfg the DB2INSTANCE parameter needs to be the SAME as what you used in the prior step!
- In installations where the database owner and CMOD Admin account are different, use the DATABASE owner's account (db2inst1, cmoddba, etc.)
- Check for typographical errors in the ars.ini and ars.cfg files
- Specifically, check the spelling of
/arsdb,/arsdb_primarylog, and/arsdb_archivelogor equivalent directories.
- Check
ars.dbfsconfiguration - Ensure this filesystem file exists, and have the correct permissions -- your database engine may not create these directories for you!
- Check the filesystem itself -- if there are leftover directories and files in /arsdb, or your primary and archive log filesystems, database creation will fail.
- Don't trust your environment variables!
- If you run
echo $DB2INSTANCEin your login shell, this is NOT the variable that gets used -- the DB2INSTANCE parameter in ars.cfg will take precedence.
DB2 Diagnostics
This is a repeat, but it's important! 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:
/home/archive/sqllib/db2dump/db2diag.log
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 v10.1 Messages & Codes Reference Volume 1 Volume 2
IBM DB2 v10.5 Messages & Codes Reference Volume 1 Volume 2
IBM DB2 v11.1 Messages Reference Messages Reference
IBM DB2 v11.5 Messages Reference Messages Reference
Try searching in the format SQL#### - where #### is the zero-padded return code, like "SQL0326".