My Oracle Support Banner

OID DIP Provisioning Profile Trace File Reporting "ORA-12505, Tns:Listener Does Not Currently Know Of Sid Given In Connect Descriptor" (Doc ID 1448332.1)

Last updated on FEBRUARY 08, 2021

Applies to:

Oracle Internet Directory - Version 10.1.2 and later
Information in this document applies to any platform.

Symptoms

Provisioning profiles from Applications to OID reporting errors in the trace files with SCAN enabled.

Example: (where MYHOST is the SCAN name)
Using Service Name to connect - URL : jdbc:oracle:thin:@<SCAN_HOSTNAME>:<DB_PORT>:<SID>,user : <EBS_APPS_USER>
Exception Connecting to DB :java.sql.SQLException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
The Connection descriptor used by the client was:
<SCAN_HOSTNAME>:<DB_PORT>:<SID>

ODIException: 0:ODIException: Exception Connecting to DB :java.sql.SQLException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
The Connection descriptor used by the client was:
<SCAN_HOSTNAME>:<DB_PORT>:<SID>

Exception connecting : java.sql.SQLException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
The Connection descriptor used by the client was:
<SCAN_HOSTNAME>:<DB_PORT>:<SID>

ODI Exception while Initialising PLSQL Reader
at oracle.ldap.odip.gsi.PLSQLReader.initialise(PLSQLReader.java:181)
at oracle.ldap.odip.prov.ProvAppToOIDSync_2_0.initialise(ProvAppToOIDSync_2_0.java:128)
at oracle.ldap.odip.engine.ProvThread.runOldVersion(ProvThread.java:548)
at oracle.ldap.odip.engine.ProvThread.run(ProvThread.java:182)


Testing the same connection using  a JDBC test the same error "ORA-12505, TNS:listener does not currently know of SID given in connect descriptor" is reported.

However connections are successful outside of OID using sqlplus and tnsnames.ora with SCAN name.

Changes

Changed provisioning profile orclodipprofileinterfaceconnectinformation to use a SCAN name rather than the physical or virtual hostname.
 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.