Unable to create ARCHIVE database - Revision history

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

2024-10-30T18:35:58Z

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.

← Older revision		Revision as of 18:35, 30 October 2024
Line 15:		Line 15:
	== What were you doing? ==		== What were you doing? ==

	Probably trying to create the database ~~while~~ installing Content Manager OnDemand.		Probably trying to create the database after installing Content Manager OnDemand.

	== Example ==		== Example ==
Line 32:		Line 32:
	/usr/lpp/ars/config		/usr/lpp/ars/config
	/opt/ondemand/config		/opt/ondemand/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		/opt/ibm/ondemand/V10.1/config
			/opt/ibm/ondemand/V10.5/config

	* 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.		; Ensure SRVR_INSTANCE OWNER and DB2INSTANCE are the same!
	* 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.		: 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'.
	* 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~~.		: 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, 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, use the DATABASE owner's account (db2inst1, cmoddba, etc.)
	* 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.
			; 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 ===		=== 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.		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:		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:
Line 53:		Line 62:
	At a UNIX shell prompt:		At a UNIX shell prompt:
	$ db2 "? sql-1390"		$ db2 "? sql-1390"

	IBM DB2 v9.5 Messages & Codes Reference [http://public.dhe.ibm.com/ps/products/db2/info/vr95/pdf/en_US/db2m1e950.pdf Volume 1] [http://public.dhe.ibm.com/ps/products/db2/info/vr95/pdf/en_US/db2m2e950.pdf Volume 2]

	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.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 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".		Try searching in the format SQL#### - where #### is the zero-padded return code, like "SQL0326".

Jderrick: Added section about IBM CMOD ars.cfg overrides local environment variables.

2018-02-06T23:58:33Z

Added section about IBM CMOD ars.cfg overrides local environment variables.

← Older revision		Revision as of 23:58, 6 February 2018
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 ===

Jderrick: Added section about DB2 online help for SQLCODE errors.

2018-02-06T18:17:53Z

Added section about DB2 online help for SQLCODE errors.

← Older revision		Revision as of 18:17, 6 February 2018
Line 48:		Line 48:
	/home/archive/sqllib/db2dump/db2diag.log		/home/archive/sqllib/db2dump/db2diag.log

	Try searching for the SQL return code in the Messages & Codes References.		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 [http://public.dhe.ibm.com/ps/products/db2/info/vr95/pdf/en_US/db2m1e950.pdf Volume 1] [http://public.dhe.ibm.com/ps/products/db2/info/vr95/pdf/en_US/db2m2e950.pdf Volume 2]		IBM DB2 v9.5 Messages & Codes Reference [http://public.dhe.ibm.com/ps/products/db2/info/vr95/pdf/en_US/db2m1e950.pdf Volume 1] [http://public.dhe.ibm.com/ps/products/db2/info/vr95/pdf/en_US/db2m2e950.pdf Volume 2]

Jderrick: Formatting changes to IBM CMOD diagnostics.

2018-02-06T18:14:49Z

Formatting changes to IBM CMOD diagnostics.

← Older revision		Revision as of 18:14, 6 February 2018
Line 35:		Line 35:
	/opt/IBM/ondemand/V9.5/config		/opt/IBM/ondemand/V9.5/config
	/opt/ibm/ondemand/V10.1/config		/opt/ibm/ondemand/V10.1/config


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

Jderrick: Added section about deleting contents of database filesystems.

2018-02-06T18:14:20Z

Added section about deleting contents of database filesystems.

← Older revision		Revision as of 18:14, 6 February 2018
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:

Jderrick: 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

2018-02-06T16:52:58Z

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

← Older revision		Revision as of 16:52, 6 February 2018
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 ===

Jderrick: Minor tweaks.

2016-04-13T19:55:55Z

Minor tweaks.

← Older revision		Revision as of 19:55, 13 April 2016
Line 28:		Line 28:
	=== CMOD Configuration Diagnostics ===		=== CMOD Configuration Diagnostics ===

	* Check that you have permission to read the configuration files in the 'config' directory.		* 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.0/config
			/opt/IBM/ondemand/V9.5/config

	* Check for typographical errors in the [[ars.ini]] and [[ars.cfg]] files.		* 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 (or the database owner) have read, write, and execute permissions.		* 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]] is equal to each other, and are the 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]] is equal to each other, and are the user id of the database owner account.

Jderrick: Added Links to DB2 Messages and Codes References for V9.5 & v10.x

2016-04-13T19:16:20Z

Added Links to DB2 Messages and Codes References for V9.5 & v10.x

← Older revision		Revision as of 19:16, 13 April 2016
Line 38:		Line 38:

	/home/archive/sqllib/db2dump/db2diag.log		/home/archive/sqllib/db2dump/db2diag.log

			Try searching for the SQL return code in the Messages & Codes References.

			IBM DB2 v9.5 Messages & Codes Reference [http://public.dhe.ibm.com/ps/products/db2/info/vr95/pdf/en_US/db2m1e950.pdf Volume 1] [http://public.dhe.ibm.com/ps/products/db2/info/vr95/pdf/en_US/db2m2e950.pdf Volume 2]

			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]

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

Jderrick: Added CMOD sub-title.

2016-04-13T18:47:09Z

Added CMOD sub-title.

← Older revision		Revision as of 18:47, 13 April 2016
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...

			=== CMOD Configuration Diagnostics ===

	* Check that you have permission to read the configuration files in the 'config' directory.		* Check that you have permission to read the configuration files in the 'config' directory.

Jderrick: Added db2diag.log location info.

2016-04-13T18:46:23Z

Added db2diag.log location info.

← Older revision		Revision as of 18:46, 13 April 2016
Line 30:		Line 30:
	* Check to ensure the directories referred to in ars.cfg exist, and that you (or the database owner) have read, write, and execute permissions.		* Check to ensure the directories referred to in ars.cfg exist, and that you (or 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]] is equal to each other, and are the 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]] is equal to each other, and are the user id of the database owner account.

			=== DB2 Diagnostics ===

			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