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

Unable to determine the database engine (view source)

250 bytes added , 15:05, 17 November 2017

Fixed formatting and added more troubleshooting information for ARS0013E.

1,126

edits

@@ Line 15: / Line 15: @@
 == 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 ==
@@ 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.
-<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>