Author Topic: ARS4013E and ars4014e error on CMOD MP arsdb command  (Read 1877 times)

ssorich

  • Jr. Member
  • **
  • Posts: 14
    • View Profile
ARS4013E and ars4014e error on CMOD MP arsdb command
« on: May 10, 2019, 09:42:14 AM »
We are in the middle of an upgrade to our dev system..... Newly installed version of 10.1 on a newly built server on redhat 7.2
 running arsdb command.
[cmodusr@vcld013757 config]$ arsdb -I d_cmod -efv
ARS4013E Unable to determine the database engine
ARS4014E Unable to load ><
Segmentation fault

We can sqlplus to Oracle DB from the server..... Running as the instance owner..... Looked through all previous articles here, and prior link. There is a new requirements for XLCC version 13.1.3 for CMOD MP 10.1 that was not in CMOD MP 9.5
There is nothing specified for Linux Redhat (which we are running 7.2). Is anybody aware of which version is required on Linux? Would it be same as AIX? If so the G++ -v gives me a much older GCC version of 4.8.5(?)

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2229
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: ARS4013E and ars4014e error on CMOD MP arsdb command
« Reply #1 on: May 11, 2019, 09:01:48 AM »
While this article is AIX and DB2 specific, it has a few good tips:

https://cmod.wiki/index.php?title=Unable_to_determine_the_database_engine

Also, double-check your ars.ini file to make sure it has the correct path to the configuration files in it.

-JD.
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR

ssorich

  • Jr. Member
  • **
  • Posts: 14
    • View Profile
Re: ARS4013E and ars4014e error on CMOD MP arsdb command
« Reply #2 on: May 14, 2019, 01:36:48 PM »
Yeah this was an ars.ini misconfiguration - note to folks who have not used archive as the DB instance - copy your current  ini files to your new server and change any references 10.1 libs etc