Difference between revisions of "Unable to determine the database engine"

Unable to determine the database engine (view source)

Revision as of 12:47, 12 October 2018

2,566 bytes added , 12:47, 12 October 2018

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

Jderrick

Bureaucrats, Administrators

1,126

edits

@@ Line 19: / Line 19: @@
 == 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.
-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] &nbsp; [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] &nbsp; [https://www.ibm.com/support/knowledgecenter/en/SSEPCD_10.1.0/com.ibm.ondemand.messages.doc/dodm4013.htm v10.1]