Oracle Error Vendor Code 12505
Contents |
here for a quick overview listener refused the connection with the following error ora-12505 in oracle sql developer of the site Help Center Detailed answers to any ora-12505 tns listener does not currently know of sid questions you might have Meta Discuss the workings and policies of this site ora 12505 error in sql developer About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack
Ora-12505 Oracle 11g
Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up ORA-12505, TNS:listener does not listener refused the connection with the following error ora-12514 currently know of SID given in connect descriptor up vote 81 down vote favorite 22 I have installed Oracle 11g Express Edition Release 2 in my windows 7 64 bit OS and tried to execute JDBC program, then I got the following error: 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 at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:412) at oracle.jdbc.driver.PhysicalConnection.
connect to the appropriate Oracle database, we'll need to expound a bit on how Oracle behaves and, therefore, what is causing this issue in the first place. ora 12505 error in oracle 12c SIDs vs SERVICE_NAMES It is important to understand the (slight) difference between what
Ora-12505 Jdbc Thin Client
Oracle defines as a SID compared to a SERVICE_NAME, as we'll use this information to create a proper
Tns Listener Does Not Know Of Service Requested In Connect Descriptor
connection string later on. In Oracle, the system identifier (or SID) is a local identifier of up to eight characters in length that is used to identify a particular database and http://stackoverflow.com/questions/18192521/ora-12505-tnslistener-does-not-currently-know-of-sid-given-in-connect-descript differentiate it from other databases on the system. Often the SID is the prefix word or DB_UNIQUE_NAME that precedes the DB_DOMAIN. For example, the SID of our bookstore database, as seen in in the full global database name of bookstore.company.com. SERVICE_NAMES, on the other hand, represent the names by which database instances can be connected to. A SERVICE_NAME will typically follow https://chartio.com/resources/tutorials/how-to-fix-ora-12505-tns-listener-does-not-currently-know-of-sid-given-in-connect-descriptor the format of the SID followed by the database domain, like so: DB_UNIQUE_NAME.DB_DOMAIN The TNS Listener When a client is attempting to connect to an Oracle database, rather than connecting to the database directly, there is a broker service that intervenes and handles the connection request for the client. This broker application is known as the listener and it performs the task of listening for incoming client requests. When a request is received, the listener processes and forwards that request onto the appropriate Oracle database server using a service handler, which just acts as the connection between the listener and the database server. TNS Names and Configuration When connecting to an Oracle database, typically your database server will have tnsnames.ora, which is a configuration file that informs the server about NET_SERVICE_NAMES which are valid database connections. By default, this file is located at ORACLE_HOME/network/admin. For example, a NET_SERVICE_NAME descriptor in tnsnames.ora may be formatted like this: myDatabaseNetService = (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST = localhost)(PORT = 1521)(QUEUESIZE = 100)) (CONNECT_DATA = (SERVICE_NAME = bookstore.company.com) ) ) This would define a NET_SE
incorrectly. Action: Turn on tracing at the ADMIN level and reexecute the operation. Verify that the ORACLE Server executable is present and has execute permissions enabled. Ensure that the ORACLE environment is specified correctly in LISTENER.ORA. The https://docs.oracle.com/cd/B19306_01/server.102/b14219/net12500.htm Oracle Protocol Adapter that is being called may not be installed on the local hard drive. Please check that the correct Protocol Adapter are successfully linked. If error persists, contact Oracle Customer Support. ORA-12502: TNS:listener received no CONNECT_DATA from client Cause: No CONNECT_DATA was passed to the listener. Action: Check that the service name resolved from TNSNAMES.ORA has the CONNECT_DATA component of the connect descriptor. ORA-12504: TNS:listener was not given the SID in CONNECT_DATA listener refused Cause: The SID was missing from the CONNECT_DATA. Action: Check that the connect descriptor corresponding to the service name in TNSNAMES.ORA has an SID component in the CONNECT_DATA. 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 listener refused the 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