1,126
edits
Difference between revisions of "Unable to determine the database engine"
Unable to determine the database engine (view source)
Revision as of 18:42, 5 April 2019
, 18:42, 5 April 2019Added section on using the instance name in arsdb -uv command.
(Added MANY more IBM CMOD troubleshooting items to the arsdb error Unable to determine the database engine.) |
(Added section on using the instance name in arsdb -uv command.) |
||
| 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. | ||