Migrating To Exadata Database. JCAPS Sre/513/62 Connection String Is Not Working (Doc ID 1360282.1)

Last updated on APRIL 05, 2017

Applies to:

Oracle Java CAPS - Version 5.1.3 and later
Information in this document applies to any platform.
*** Checked for relevance on 28-MAR-2012 ***
***Checked for relevance on 21-July-2014***

Symptoms


On : JavaCAPS 5.1.3U4

Migrating to EXADATA server, all JDBC connection in JCAPS is failing with the following error:

com.sun.enterprise.resource.PoolingException: Connection could not be allocated Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

 because it only allows to configure using the database server, port and SID (jdbc:oracle:thin:dbServer:port:SID) while the the new EXADATA requires (jdbc:oracle:thin:dbServer:port:SERVICE_NAME)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms