Oracle Error 12538 Encountered
Contents |
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
Ora-12222 Forms 6i
Excel-DB Don Burleson Blog
ora-12154 ORA-12538: TNS: no such protocol adapter Oracle Database Tips by Burleson Consulting From the Oracle documentation we see this on the ORA-12538 error: ORA-12538: TNS:no such protocol adapter Cause: The protocol adapter requested (by way of the '(PROTOCOL=..)'; keyword-value pair in a TNS address) is unknown. If the supplied address is typographically correct then the protocol adapter is not installed. Action: Install the protocol adapter or correct typographically error, as appropriate. Note: if the supplied address was derived from resolving the service name, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA or SQLNET.ORA). Solutions: If TNS_ADMIN is set then you should be able to use a network alias, not the full "(DESCRIPTION..." connect string. The TNS_ADMIN parm tells Oracle clients where to find the tnsnames.ora file. Setting the ORACLE_HOME environment variable incorrectly on a Windows based system will create this problem. �� Burleson is the American Team Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals. Feel free to ask questions on our Oracle forum. Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications. Errata? Oracle technology is changing and we strive to update our BC Oracle support information. If you find an error or have a suggestion for improving our content, we would appreciate your feedback. Just e-mail: anhere for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack 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 How to resolve this error on oracle? up vote 1 down vote favorite what is this error, I http://www.dba-oracle.com/t_iora_12538_tns_no_protocol_adapter.htm am trying to import some data into oracle and getting this error on a fresh database. UID-12538: operation generated ORACLE error 12538 ora-12538: TNS:no such protocol adapter oracle share|improve this question asked Sep 28 '15 at 11:28 Sanjeev 114 Welcome to SO! This question is lacking a lot of information - please add the exact command you run, the contents of your tnsnames.ora / sqlnet.ora plus any relevant environment variables http://stackoverflow.com/questions/32821887/how-to-resolve-this-error-on-oracle (ORACLE_HOME/TNS_ADMIN) that you have changed (and please add this information by 'edit'ing your question, not as a comment) –Frank Schmitt Sep 28 '15 at 13:05 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote From the Oracle documentation we see this on the ORA-12538 error ORA-12538: TNS:no such protocol adapter Cause: The protocol adapter requested (by way of the '(PROTOCOL=..)'; keyword-value pair in a TNS address) is unknown. If the supplied address is typographically correct then the protocol adapter is not installed. Action: Install the protocol adapter or correct typographically error, as appropriate. Note: if the supplied address was derived from resolving the service name, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA or SQLNET.ORA). Solutions: If TNS_ADMIN is set then you should be able to use a network alias, not the full "(DESCRIPTION..." connect string. The TNS_ADMIN parm tells Oracle clients where to find the tnsnames.ora file. Setting the ORACLE_HOME environment variable incorrectly on a Windows based system will create this problem. share|improve this answer answered Sep 28 '15 at 11:30 Heru-Luin 1,388621 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest
process Cause: The process of starting up a dedicated server process failed. The executable could not be found or the environment may be set up incorrectly. Action: Turn on tracing at the ADMIN level https://docs.oracle.com/cd/B13789_01/server.101/b10744/net12500.htm 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 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 oracle error 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 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 oracle error 12538 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