Unable to determine the database engine - Revision history

Jderrick: Added section about CMOD directory permissions.

2020-05-24T04:14:28Z

Added section about CMOD directory permissions.

← Older revision		Revision as of 04:14, 24 May 2020
Line 19:		Line 19:

	== Troubleshooting ==		== Troubleshooting ==

			If you're not installing CMOD as the server's 'root' or 'admin' account, ensure that you have the proper permissions to access the configuration files, and any intermediate directories. You may need to change the ownership and permissions of the CMOD installation directory or configuration files to match the ID that you intend to run the Content Manager OnDemand daemon [[arssockd]] as.

			$ ls -l
			drwxr-xr-x. 3 archive archive 4096 May 11 21:41 bin
			drw-r--r--. 2 archive archive 4096 May 23 23:59 config
			drwxr-xr-x. 2 archive archive 25 May 11 21:41 dd
			drwxr-xr-x. 7 archive archive 70 May 11 21:41 exits
			The archive user can't traverse into the 'config' directory -- it's missing the execute privilege!
			$ chmod 755 config
			$ ls -l
			drwxr-xr-x. 3 archive archive 4096 May 11 21:41 bin
			drwxr-xr-x. 2 archive archive 4096 May 23 23:59 config
			drwxr-xr-x. 2 archive archive 25 May 11 21:41 dd
			drwxr-xr-x. 7 archive archive 70 May 11 21:41 exits
			Permissions now allow the 'archive' user to access the contents of the 'config' directory.

	Check to see that your [[ars.ini]] configuration parameters are correct and up to date. On some platforms, the values (especially User ID's) are case-sensitive, so you may need to use "archive" instead of "ARCHIVE".		Check to see that your [[ars.ini]] configuration parameters are correct and up to date. On some platforms, the values (especially User ID's) are case-sensitive, so you may need to use "archive" instead of "ARCHIVE".

Jderrick: Added section on using the instance name in arsdb -uv command.

2019-04-05T18:42:48Z

Added section on using the instance name in arsdb -uv command.

← Older revision		Revision as of 18:42, 5 April 2019
Line 23:		Line 23:

	Ensure that the ARS_DB_ENGINE parameter in the ars.cfg file is one of the three following values: DB2, ORACLE, MSSQL.		Ensure that the ARS_DB_ENGINE parameter in the ars.cfg file is one of the three following values: DB2, ORACLE, MSSQL.

			If you have a non-default CMOD instance name ("archive") then you MUST use the -I parameter with the correct IBM Content Manager OnDemand instance name.

	See the [[ars.cfg]] article for more information on the parameters in the [[ars.cfg\|IBM CMOD Configuration file]] to make sure you're using the appropriate IBM Content Manager OnDemand configuration parameters.		See the [[ars.cfg]] article for more information on the parameters in the [[ars.cfg\|IBM CMOD Configuration file]] to make sure you're using the appropriate IBM Content Manager OnDemand configuration parameters.

Jderrick: Added MANY more IBM CMOD troubleshooting items to the arsdb error Unable to determine the database engine.

2018-10-12T12:47:22Z

Added MANY more IBM CMOD troubleshooting items to the arsdb error Unable to determine the database engine.

← Older revision		Revision as of 12:47, 12 October 2018
Line 19:		Line 19:

	== Troubleshooting ==		== Troubleshooting ==

			Check to see that your [[ars.ini]] configuration parameters are correct and up to date. On some platforms, the values (especially User ID's) are case-sensitive, so you may need to use "archive" instead of "ARCHIVE".

	Ensure that the ARS_DB_ENGINE parameter in the ars.cfg file is one of the three following values: DB2, ORACLE, MSSQL.		Ensure that the ARS_DB_ENGINE parameter in the ars.cfg file is one of the three following values: DB2, ORACLE, MSSQL.

	See the [[ars.cfg]] article for more information on the parameters in the [[ars.cfg\|IBM CMOD Configuration file]].		See the [[ars.cfg]] article for more information on the parameters in the [[ars.cfg\|IBM CMOD Configuration file]] to make sure you're using the appropriate IBM Content Manager OnDemand configuration parameters.

			Check to see that you have DB2 connectivity from the IBM CMOD instance owner account, and permission to access the tables:

			# Can I run db2 and see the database directory?
			$ db2 list database directory
			System Database Directory
			Number of entries in the directory = 1
			Database 1 entry:
			Database alias = ARCHIVE
			Database name = ARCHIVE
			Local database directory = /arsdb/SMS
			Database release level = 10.00
			Comment =

			# Do I have permission to connect to the database?
			$ db2 connect to BNC
			Database Connection Information
			Database server = DB2/LINUXX8664 10.5.8
			SQL authorization ID = ARCHIVE
			Local database alias = ARCHIVE

			If you're not able to see or connect to DB2, make sure you have the correct group membership (sysadm1 if your IBM CMOD installation was by-the-book), and check to make sure that the appropriate db2 links have been created with the <code> db2ln </code> command. You will need administrative or root access to perform this task.

			Also check to see that you have the correct environment variables, with the <code> set</code> or <code> setenv</code> commands, depending on your command shell:

			$ set
			DATABASE=ARCHIVE
			DB2DIR=/opt/ibm/db2/V10.5
			DB2INSTANCE=archive
			DB2LIB=/home/archive/sqllib/lib
			DB2_HOME=/home/archive/sqllib
			DB2_NET_CLIENT_PATH=
			HOSTNAME=OnDemand.example.com
			HOSTTYPE=x86_64
			IBM_DB_DIR=/home/archive/sqllib
			IBM_DB_HOME=/home/archive/sqllib
			IBM_DB_INCLUDE=/home/archive/sqllib/include
			IBM_DB_LIB=/home/archive/sqllib/lib

			If you don't have these values, you will need to find the <code> db2profile</code> script and execute it to set these variables -- it can be found inside the 'sqllib' directory of the database owner's home directory.

			Finally, IBM CMOD updates have been known to have problems co-existing with prior versions of Content Manager OnDemand being installed at the same time. Removing old Content Manager OnDemand versions before configuring your newly-installed instance with the <code> uninstallod</code> command may help eliminate this error. Make sure to back up your configuration files first!

	See the IBM Documentation on ARS0013E: [https://www.ibm.com/support/knowledgecenter/en/SSEPCD_9.5.0/com.ibm.ondemand.messages.doc/dodm4013.htm v9.5]   [https://www.ibm.com/support/knowledgecenter/en/SSEPCD_10.1.0/com.ibm.ondemand.messages.doc/dodm4013.htm v10.1]		If these items didn't help, See the IBM Documentation on ARS0013E: [https://www.ibm.com/support/knowledgecenter/en/SSEPCD_9.5.0/com.ibm.ondemand.messages.doc/dodm4013.htm v9.5]   [https://www.ibm.com/support/knowledgecenter/en/SSEPCD_10.1.0/com.ibm.ondemand.messages.doc/dodm4013.htm v10.1]

Jderrick: Updated ARS_DB_ENGINE, removed references to ars.ini.

2017-11-17T20:20:08Z

Updated ARS_DB_ENGINE, removed references to ars.ini.

← Older revision		Revision as of 20:20, 17 November 2017
Line 20:		Line 20:
	== Troubleshooting ==		== Troubleshooting ==

	~~It's not very clear which of~~ the ~~parameters~~ in the ars.~~ini~~ file ~~are to be used for what purpose.~~		Ensure that the ARS_DB_ENGINE parameter in the ars.cfg file is one of the three following values: DB2, ORACLE, MSSQL.

	~~[@SRV@_ARCHIVE] <=- CMOD Instance Name to be used with arsdb, arsmaint and arssockd.~~
	~~HOST= <=- should be set to the server's fully-qualified domain name (prod.cmod.example.com)~~
	~~PROTOCOL=2 <=- In all modern instances of CMOD, the current version number is 2.~~
	~~PORT=0 <=- If set to 0, IBM CMOD port number~~ is ~~set to 1445.~~
	~~SRVR_INSTANCE=ARCHIVE <=- The name~~ of the DB2~~/Oracle database that CMOD stores index data in.~~
	~~SRVR_INSTANCE_OWNER=odadmin <=- The User name of the UNIX account that runs arssockd & owns database tables~~.

			See the [[ars.cfg]] article for more information on the parameters in the [[ars.cfg\|IBM CMOD Configuration file]].

	See the IBM Documentation on ARS0013E: [https://www.ibm.com/support/knowledgecenter/en/SSEPCD_9.5.0/com.ibm.ondemand.messages.doc/dodm4013.htm v9.5]   [https://www.ibm.com/support/knowledgecenter/en/SSEPCD_10.1.0/com.ibm.ondemand.messages.doc/dodm4013.htm v10.1]		See the IBM Documentation on ARS0013E: [https://www.ibm.com/support/knowledgecenter/en/SSEPCD_9.5.0/com.ibm.ondemand.messages.doc/dodm4013.htm v9.5]   [https://www.ibm.com/support/knowledgecenter/en/SSEPCD_10.1.0/com.ibm.ondemand.messages.doc/dodm4013.htm v10.1]

Jderrick: Added links to IBM CMOD Documentation.

2017-11-17T20:07:17Z

Added links to IBM CMOD Documentation.

← Older revision		Revision as of 20:07, 17 November 2017
Line 28:		Line 28:
	SRVR_INSTANCE=ARCHIVE <=- The name of the DB2/Oracle database that CMOD stores index data in.		SRVR_INSTANCE=ARCHIVE <=- The name of the DB2/Oracle database that CMOD stores index data in.
	SRVR_INSTANCE_OWNER=odadmin <=- The User name of the UNIX account that runs arssockd & owns database tables.		SRVR_INSTANCE_OWNER=odadmin <=- The User name of the UNIX account that runs arssockd & owns database tables.


			See the IBM Documentation on ARS0013E: [https://www.ibm.com/support/knowledgecenter/en/SSEPCD_9.5.0/com.ibm.ondemand.messages.doc/dodm4013.htm v9.5]   [https://www.ibm.com/support/knowledgecenter/en/SSEPCD_10.1.0/com.ibm.ondemand.messages.doc/dodm4013.htm v10.1]

Jderrick: Fixed formatting and added more troubleshooting information for ARS0013E.

2017-11-17T15:05:19Z

Fixed formatting and added more troubleshooting information for ARS0013E.

← Older revision		Revision as of 15:05, 17 November 2017
Line 15:		Line 15:
	== Example ==		== Example ==

	~~<code>~~		$ arsdb -u -I PROD
	$ arsdb -u -I PROD		arsdb: ARS4013E Unable to determine the database engine
	arsdb: ARS4013E Unable to determine the database engine
	~~</code>~~

	== Troubleshooting ==		== Troubleshooting ==
Line 24:		Line 22:
	It's not very clear which of the parameters in the ars.ini file are to be used for what purpose.		It's not very clear which of the parameters in the ars.ini file are to be used for what purpose.

	~~<code>~~		[@SRV@_ARCHIVE] <=- CMOD Instance Name to be used with arsdb, arsmaint and arssockd.
			HOST= <=- should be set to the server's fully-qualified domain name (prod.cmod.example.com)
	[@SRV@_ARCHIVE] <=- CMOD Instance Name to be used with arsdb, arsmaint and arssockd.		PROTOCOL=2 <=- In all modern instances of CMOD, the current version number is 2.
	HOST=		PORT=0 <=- If set to 0, IBM CMOD port number is set to 1445.
	PROTOCOL=2		SRVR_INSTANCE=ARCHIVE <=- The name of the DB2/Oracle database that CMOD stores index data in.
	PORT=0		SRVR_INSTANCE_OWNER=odadmin <=- The User name of the UNIX account that runs arssockd & owns database tables.
	SRVR_INSTANCE=ARCHIVE <=- The name of the DB2/Oracle database that CMOD stores index data in.
	SRVR_INSTANCE_OWNER=odadmin <=- The User name of the UNIX account that runs arssockd & owns database tables.

	~~</code>~~

Jderrick: Updated error severity text

2015-05-10T01:51:14Z

Updated error severity text

← Older revision		Revision as of 01:51, 10 May 2015
Line 5:		Line 5:
	Message Number: 4013		Message Number: 4013

	Message Severity: Error		Message Severity: Error (Corrective action is required to continue)

	Message Name: ARS4013E		Message Name: ARS4013E

Jderrick: Moved the TOC to the right.

2015-04-29T00:13:20Z

Moved the TOC to the right.

← Older revision		Revision as of 00:13, 29 April 2015
Line 1:		Line 1:
			{{TOCright}}

	== What was the error? ==		== What was the error? ==

Jderrick: /* Troubleshooting */

2015-04-29T00:12:31Z

Troubleshooting

← Older revision		Revision as of 00:12, 29 April 2015
Line 29:		Line 29:
	PORT=0		PORT=0
	SRVR_INSTANCE=ARCHIVE <=- The name of the DB2/Oracle database that CMOD stores index data in.		SRVR_INSTANCE=ARCHIVE <=- The name of the DB2/Oracle database that CMOD stores index data in.
	SRVR_INSTANCE_OWNER=~~odadminp~~ <=- The User name of the UNIX account that runs arssockd & owns database tables.		SRVR_INSTANCE_OWNER=odadmin <=- The User name of the UNIX account that runs arssockd & owns database tables.

	</code>		</code>

Jderrick: Added example & Troubleshooting.

2015-04-28T16:19:31Z

Added example & Troubleshooting.

New page

== What was the error? ==

Message Number: 4013

Message Severity: Error

Message Name: ARS4013E

== What were you doing? ==

Probably trying to run [[arsdb]] or [[arssockd]] with the -I parameter.

== Example ==

<code>
$ arsdb -u -I PROD
arsdb: ARS4013E Unable to determine the database engine
</code>

== Troubleshooting ==

It's not very clear which of the parameters in the ars.ini file are to be used for what purpose.

<code>

[@SRV@_ARCHIVE] <=- CMOD Instance Name to be used with arsdb, arsmaint and arssockd.
HOST=
PROTOCOL=2
PORT=0
SRVR_INSTANCE=ARCHIVE <=- The name of the DB2/Oracle database that CMOD stores index data in.
SRVR_INSTANCE_OWNER=odadminp <=- The User name of the UNIX account that runs arssockd & owns database tables.

</code>