Error 12514 Oracle
Contents |
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 oracle error 12514 encountered Oracle Protocol Adapter that is being called may not be installed on the local
12154 Oracle Error
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
Oracle Error 12564
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
Oracle Error 12560
CONNECT_DATA 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) oracle error 12541 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
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! Oracle PostersOracle Books Oracle Scripts Ion Excel-DB Don Burleson Blog ora 12514 error in oracle
ORA-12514: TNS: listener could ora 12514 error in oracle 11g not resolve SERVICE_NAME Question: Here's my issue, causing a ORA-12514: TNS: listener could not resolve SERVICE_NAME error: CODE error 12514 received logging on to the standby oracle SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> startup mount ORACLE instance started. ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor I'm using Oracle 10g on Windows https://docs.oracle.com/cd/B19306_01/server.102/b14219/net12500.htm 2000. What's cause of this error and how to resolve it? Answer by Edward Stoever: ORA-12514: TNS:listener does not currently know of service requested 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 service name for a service (usually a database service) that either has not yet dynamically http://www.dba-oracle.com/t_ora_12514_tns_listener_service_name.htm 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 services are currently known by the listener by executing: lsnrctl servicesof service In previous articles I have explored various reasons why a client process might not be able to connect to an Oracle database. In Help! I can’t connect to my database … I http://edstevensdba.com/oracle-tns/ora-12514-tnslistener-does-not-currently-know-of-service/ presented an overview of the process. I followed that with articles going into more depth on the types of problems that can prevent the request from reaching the host server. Now I would like to look at problems that can arise once the request actually arrives at the listener, in particular “ORA-12514: TNS:listener does not currently know of service requested in connect descriptor”. For this demonstration I will oracle error generate the error then go through the standard analysis and solution. After that, I will explore some of the interesting factors that flow from this. The Error - ORA-12514 Before we get into specifics of debugging ORA-12514, let's create a test case and mention some general principles. C:\>sqlplus scott/tiger@tulsa SQL*Plus: Release 11.2.0.1.0 Production on Mon Jan 18 15:28:47 2016 Copyright (c) 1982, 2010, Oracle. All rights reserved. ora 12514 error ERROR: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor Enter user-name: Fig. 1 Of course the very first thing anyone should do when confronted with an Oracle error is to check the official description. There are many sources on the web, but I like to start with ‘oerr’ utility on the server .. [oracle@vmlnx01 admin]$ oerr ora 12514 12514, 00000, "TNS:listener does not currently know of service requested 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 service name for a service (usually a database service) // 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 services are currently known by the listener by executing: // lsnrctl services // - Check that the SERVICE_NAME parameter in the connect descriptor of t