Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect

SOLVED
Go to solution
Highlighted
veronique fergu
Occasional Contributor

ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect

I am receiving a TNS listener error now that I have upgraded to 7.1.

I have other 7.1 PPM instances on the same server without any issues but this one instance is giving me this error when I run reports and when sql execution steps are ran in the workflows.

Does anyone have any suggestions?

Thanks,
-veronique
10 REPLIES
Erik Cole_1
Esteemed Contributor

Re: ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect

Hi Veronique,

No typos in the database section of your environment settings in the workbench?
veronique fergu
Occasional Contributor

Re: ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect

Hi Erik,

The enviornment settings haven't changed in the workbench during the upgrade, but I have check them just in case. No resolution there. Thanks for the suggestion.

regards,
-veronique
Darshan Bavisi
Occasional Visitor

Re: ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect

Hi Veronique,

Can you post the screenshots of the entire error message you are getting for both when you run reports and when you try to connect from the Environment tab in Workbench?

Can you also send the error details in serverLog.txt file for this error? That may give more idea on where the problem might me.
veronique fergu
Occasional Contributor

Re: ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect

Hi Darshan,

I have provided the following screenshots and log files.

Thanks for your reply.

-veronique
Erik Cole_1
Esteemed Contributor

Re: ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect

Veronique can you post the values for these two server.conf entries?

com.kintana.core.server.DB_CONNECTION_STRING

com.kintana.core.server.JDBC_URL
veronique fergu
Occasional Contributor

Re: ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect

Hi Erik,

I don't have a db connection string in the server config file . . . . i do have the jdbc in the server config file com.kintana.core.server.JDBC_URL=jdbc:oracle:thin:@HO-ACCE-WDB01:1521:ACCTECD1

i can get the db connection string if i run the report from the workbench . . . .it is

(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=HO-ACCE-WDB01)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ACCTECD1)

Thanks,

-veronique
Erik Cole_1
Esteemed Contributor
Solution

Re: ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect

Try adding

com.kintana.core.server.DB_CONNECTION_STRING=ACCTECD1

to your server.conf and bounce the server after running kUpdateHtml
veronique fergu
Occasional Contributor

Re: ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect

Hi Erik,

That worked! Thanks for your help, I really appreciate it. It seems I changed everything but I did not add that into the server config file, how funny . . . . Have a great one :)

Regards,
-veronique
veronique fergu
Occasional Contributor

Re: ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect

Close case
veronique fergu
Occasional Contributor

Re: ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect

added com.kintana.core.server.DB_CONNECTION_STRING into the server config file and this solved the issue.
//Add this to "OnDomLoad" event