I assume you are trying to connect to Oracle RAC.

did you check the tnsnames.ora file? after upgrade you need to manually restore it....

Hi Asaf,

Thanks for the reply.

Yes we restored the tnsnames.ora file also we restored jdbc.properties file as well.

Regards,

Pranav R N

then please submit support case for further investigation.

Hi Pravan,

as you never posted that the issue has been resolved I thought I'll give it a shot:

there was a change from APM 9.51 to APM 9.60

9.5x
====
<HPBSM>\conf\jdbc.drivers.properties

ddoracle.class=com.mercury.jdbc.oracle.OracleDriver
ddoracle.url=jdbc:mercury:oracle:TNSNamesFile=E:\\HPBSM\\conf\\bsm-tnsnames.ora;TNSServerName=${sid}

<HPBSM>\conf\\bsm-tnsnames.ora
TOPAZI =(DESCRIPTION =(ADDRESS =(PROTOCOL = TCP)(Host = myhost.mydomain.mycom)(Port = 1234))
(CONNECT_DATA =(SERVICE_NAME = APM)(SERVER = DEDICATED)))

<HPBSM>\odb\conf\jdbc.properties

Oracle = ddoracle
cmdb.url =jdbc:mercury:oracle:TNSNamesFile=E:\\HPBSM\\conf\\bsm-tnsnames.ora;TNSServerName=APM

9.60
====
- mcoracle.jar no longer exists in folder <HPBSM>\lib
thus the path has to be changed
from for example
ddoracle.class=com.mercury.jdbc.oracle.OracleDriver
to for example
ddoracle.class=oracle.jdbc.driver.OracleDriver

Also the file TNSNamesFile is no longer being used, the data is now passed directly via ddoracle.url

OOTB
<HPBSM>\conf\jdbc.drivers.properties

old
ddoracle.url=jdbc:oracle:thin:@${host}:${port}:${sid}

new
ddoracle.url=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=myhost.mydomain.mycom)(PORT=1234))(LOAD_BALANCE=off)(FAILOVER=off))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=APM)))

also you need to perform the similar steps for ODB / RTSM:

<HPBSM>\odb\conf\jdbc.properties
doesn't exist on a new APM 9.60 installation, you hopefully can copy if it from your still around 9.51 installation and then modify it:

old

Oracle = ddoracle
cmdb.url =jdbc:mercury:oracle:TNSNamesFile=E:\\HPBSM\\conf\\bsm-tnsnames.ora;TNSServerName=APM

new
Oracle = ddoracle
cmdb.url=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=myhost.mydomain.mycom)(PORT=1234))(LOAD_BALANCE=off)(FAILOVER=off))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=APM)))

Greetings
Siggi

P.S. The kudos go to ChristianD who disovered this ;-)-

Hi Siggi,

Sorry for the delay in the response as I was on vacation.

Thanks a lot for the steps and It worked.

But unfortunately after moved the database section steps and when we are in the password section step if I provide the correct admin, JMX and RTSM password it's not updating and giving the below error. Do you have any Idea

Hi Pranav R N,

good that the connection to the database now works.

Regarding the follow-up error, and only looking at the JMX password,

the only ideas coming into my mind are:

- try again

- to start with use a really simple password, for a test just letters for example

- use the defaults and try to change the password(s) after the installation completed using the Configuration and Connection Wizard, you might wanna check KM000002862 for details

- check out
RE: (BSM) Support Tip: Config wizard gives the error "Failed to change the password for admin user"

- enable debug logging in the hope to find something useful in the logfiles

Finally ... a support case might be needed ...

Greetings
Siggi

Hi Siggi,

Thanks for the reply and help.

I was able to resolve the issue. The issue is with the Mangement Database USERS table (management schema) the password for admin user is in plain text. 

(BSM) Support Tip: Config wizard gives the error "Failed to change the password for admin user" - Operations Bridge User Discussions - OpenText Operations Bridge (microfocus.com)

I will close this thread.

Regards,

Pranav R N

Hi Pravan,

cool that you got it working.

Greetings

Siggi

Hello, We faced the same issue and it was resolved after modifying the jdbc files as mentioned above, however now when we run the upgrade wizard_9.51.sh script, post entering the values in the wizard, we are not able to connect to the management DB. Log says - Invalid username/password: logon denied.

We have checked with the DB team and confirmed that username and password which we are using is correct and valid and also they are able to connect from the DPS sevrer using sudo su - oracle with the same username and password.

Working if anyone has faced this same issue and can assist...thanks in advance..

FYI - Upgrading distributed env. from APM 9.51 IP2 to 9.60 In-place. Oracle RAC 19 C DB.