 |
|
ORA-12505: TNS:listener does not currently know of SID
given in connect descriptor tips
Oracle Error Tips by Burleson Consulting
|
Oracle docs note this about ORA-12505:
- ORA-12505: TNS:listener does not currently know of SID given in connect descriptor
-
Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a SID for an instance (usually a database instance) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.
-
Action:
- Wait a moment and try to connect a second time.
- Check which instances are currently known by the listener by executing: lsnrctl services <listener name>
- Check that the SID parameter in the connect descriptor specifies an instance known by the listener.
- Check for an event in the listener.log file.
Searching MOSC, you can find various information docs regarding ORA-12505 in congruence with other errors.
A widely seen situation with ORA-12505 concerns "JDBC Thin Connection Confusion between Service and SID Results in ORA-12505" T
his issue is seen in version 11.5.10 on all platforms, and occurs when the JDBC thin connector tries to connect between the RAC with the Service name instead of SID. This mix-up throws the ORA-12505 error. Though some try to set the TWO_TASK variable to reflect the SID, this workaround will also fail along with ORA-12505.
The problem here is that the jdbc connect
string des not have the appropriate SID name, causing ORA-12505 to interfere.
MOSC offers this solution to resolve ORA-12505:
This issue is resolved by setting the
TWO_TASK variable to the <Service>_806_BALANCE alias in the tnsnames.ora
file.
The difference between the default Service name entry and the
<Service>_806_BALANCE entry is that the second alias points to the 2 SID's
as opposed to the just the Service name in the first alias.
Because ORA-12505 is often an issue within the
listener.ora file, you might find
this link helpful.
|
