Solved

FSM upgrade issues on App Server

  • 10 December 2021
  • 3 replies
  • 129 views
JitheshP
Rank
Userlevel 2
Badge +7

Hi Team,

 

We have upgraded FSM DB to 6.9 from 6.5 on the Oracle DB server (system: XX) and trying to upgrade FSM App client and mobile on the App server (system: YY) using this DB server name but the DB connection doesnt get established.

When DB connection is tested during Application server installation it always ends up in error 

ORA-12154: TNS:could not resolve the connect identifier specified

 

 

 

DB upgrade was successful on Db server (system name: XX)

 

Present Status of the Upgrade:

FSM Database:prodfsm dbuserVersion: FSM6.9.7746 17-3-2021 10:31:27

FSM Client: FSMVersion: 6.5.7417.14159

 

Please advise how to fix this connection issue.

 

Regards,

Jithesh

 

icon

Best answer by JitheshP 10 December 2021, 10:08

View original

3 replies

H
Rank
Userlevel 5
Badge +13

Hi @JitheshP,

 

We have encounterd the same issue when trying to connect to the oracle database from server (refer the below screenshot).

 

Below is the workaround which worked for us.

Oracle client is installed in locations like below(check environment variables related to this)

C:\app\client\MERIWW\product\19.0.0\client_1\NETWORK\ADMIN\tnsnames.ora

C:\app\oracle\product\19.0.0\client_1\NETWORK\ADMIN\tnsnames.ora

 

In the oracle installed location you can find the tnsnames.ora file

During the installation, it will check whether the tnsnames.ora file is having the correct server name

If not, it will show below error.

‘TNS could not resolve the connect identifier specified’

Could you please check whether the correct server value is set in tnsnames.ora file?

 

Thanks,

Hasara

JitheshP
Rank
Userlevel 2
Badge +7

Hi Hasara,

 

We have the FSM client 6.5 still working without it upgraded to 6.9 even though FSM DB is on 6.9

So  I assume there should be no problem with tnsnames.ora

 

However we are checking that again with the DBAs and will revert.

 

JitheshP
Rank
Userlevel 2
Badge +7

Hi Hasara,

 

TNS_ADMIN entry and TNS configuration not added correctly in the env variables which was the cause of the issue. That is updated and issue is fixed.

 

Thanks for your time and response.

 

Regards,

Jithesh

Reply


Terms & ConditionsCookie settings