Error Creating Instance using Oracle

[Joe Wolken]

We have successfully installed and tested an identical QA Server (Instance = ondq) and we are now trying to replicate the process (following IBM Installation manual) to install and configure the PROD server (Instance = ondp).   It is:
RHELinux
Oracle v.19.10.0
CMOD v.10.5

The product installs successfully.  We compared these files to match the setting on QA but changing ondq to ondp:
/opt/ibm/ondemand/V10.5/config/ars.cfg
/opt/ibm/ondemand/V10.5/config/ars.ini
/opt/ibm/ondemand/V10.5/config/ars.dbfs

We get the following error when running the command:  arsdb -I ondp -rtv

[ondp@ause2ldaondp001 config]$ /opt/ibm/ondemand/V10.5/bin/arsdb -I ondp -rtv

ARS4054E DB Error: ORA-12154: TNS:could not resolve the connect identifier specified -- SQLSTATE=, SQLCODE=12154
ARS4023E Unable to connect to ORACLE ondp database

Our Oracle administrator seems to think that the Oracle database on ondp is configured the same as ondq...

Does anyone have an idea what is causing this error or what else to check or resolve this?

Thanks,
Joe

[Justin Derrick]

Hey Joe...

Can we see the contents of the ars.ini file?

-JD.

[Joe Wolken]

Sure,  Here are the content of the ars.ini file:  I welcome any suggestions, especially if they help solve the problem.  This is basically identical to the QA server we have operational.  We just replaced ondq with ondp on several rows.

[@SRV@_ONDP]
HOST=ause2ldaondp001.company.net
PROTOCOL=2
PORT=0
SRVR_INSTANCE=ondp
SRVR_INSTANCE_OWNER=ondp
SRVR_OD_CFG=/opt/ibm/ondemand/V10.5/config/ars.cfg
SRVR_DB_CFG=/opt/ibm/ondemand/V10.5/config/ars.dbfs
SRVR_SM_CFG=/opt/ibm/ondemand/V10.5/config/ars.cache
SRVR_OD_STASH=/opt/ibm/ondemand/V10.5/config/ars.stash

[@SRV@_DD]
PROTOCOL=1

[Justin Derrick]

Yeah, everything looks fine with the ini file - I'd have to guess there's still something wrong with the Oracle config. 

-JD.

[Joe Wolken]

Problem resolved.  As we suspected it was an Oracle issue.  Specifically, there was not sufficient permissions granted to the tnsnames.ora file.  The Oracle admin opened up the permissions to the file and the CMDOD arsdb command worked like expected.

Thanks,
Joe

[Justin Derrick]

Awesome.  Thanks for posting the solution.  :)