Oracle Database Connection Error
Contents |
TNS:received bad packet type from network layer Cause: Internal error. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. ORA-12152: TNS:unable to send break message Cause: Unable error ora-12154 tns could not resolve the connect identifier specified to send break message. Connection probably disconnected. Action: Reestablish connection. If the error is persistent,
Ora-12154 Tns Could Not Resolve The Connect Identifier Specified Windows 7
turn on tracing and reexecute the operation. ORA-12153: TNS:not connected Cause: Not currently connected to a remote host. Action: Reestablish connection. ORA-12154: TNS:could tns could not resolve the connect identifier specified odbc not resolve the connect identifier specified Cause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of
Tns Could Not Resolve The Connect Identifier Specified Sqlplus
the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached. Action: - If you are using local naming (TNSNAMES.ORA file): - Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA) - Verify ora-12154 tns could not resolve service name that a TNSNAMES.ORA file exists and is in the proper directory and is accessible. - Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file. - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable. - If you are using directory naming: - Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). - Verify that the LDAP directory server is up and that it is accessible. - Verify that the net service name or database name used as the connect identifier is configured in the directory. - Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier - If you are using easy connect naming: - Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). - Make sure the host, port and service name specified are correct. - Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming. ORA-12155: TNS:received bad datatype in NSWMAR
a unique format. Though the TNSNames.ora file may not always be required. For instance, if you have installed only the Tableau-provided Oracle files and do not have a
Asp.net Ora-12154: Tns:could Not Resolve The Connect Identifier Specified
stand-alone Oracle client. The Oracle error messages refer to the TNSNames.ora file.
Tns Could Not Resolve The Connect Identifier Specified Oracle 10g
Typically, correcting route or naming syntax in the Advanced Oracle Connection dialog box or using your full .WORLD ora-12154 tns could not resolve service name oracle 11g database name resolves most Oracle connection issues. If your connection error requires more troubleshooting, refer to the four common connection errors listed below. ORA-03113: end-of-file on communication channelORA-12154: TNS: could https://docs.oracle.com/cd/B19306_01/server.102/b14219/net12150.htm not resolve the connect identifier specified HOST value incorrect or Global name incorrect or unknownORA-12514: TNS listener does not currently know of service requested in connect descriptorSERVICE value incorrectORA-12541: TNS: no listenerPORT value incorrectORA-00932: inconsistent data types ORA-03113: end-of-file on communication channel ORA-03113 is a catch-all type error for any problem interrupting an Oracle session. There can be numerous causes for this http://kb.tableau.com/articles/knowledgebase/oracle-connection-errors error. Please refer to the list below for some troubleshooting guidance. Refer to Oracle documentation specific to this error: My Oracle Support.Refer to Oracle's B Troubleshooting Common Errors page.Oracle recommends that you check for network problems and review the SQL*Net setup.If you're connecting to Oracle 9.2.0.5, in many cases the primary cause of this error is Oracle bug 3010227. Ask your Oracle database administrator to apply Oracle patch 9.2.0.6 or another patch appropriate for your server. Set the Oracle initialization parameter 'STAR_TRANSFORMATION_ENABLED' to FALSE.Alternatively, if you would like to test this issue further follow the optional procedure listed below. Step 1 From the Tableau Desktop start page, select Connect to Data. Step 2 For Tableau Desktop 8.2 and later, on the Connect page, click Oracle. For Tableau Desktop 8.1 and earlier, on the Connect to Data page, click Oracle. Step 3 For Tableau Desktop 8.2 and later, connect to the Oracle server, and then click OK. For Tableau Desktop 8.1 and earlier, follow the steps in the Oracle Connection dialog box to complete the connection. For more information about completing the
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta http://stackoverflow.com/questions/25623153/jdbc-connection-error-to-oracle-database Discuss the workings and policies of this site About Us Learn http://www.dadbm.com/how-to-troubleshoot-oracle-remote-database-connection/ 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, could not helping each other. Join them; it only takes a minute: Sign up JDBC Connection Error to Oracle Database up vote 1 down vote favorite 1 I'm trying to establish a connection from Java to Oracle DB. (My DB is in another machine) The form of URL as i know is like : String url = "jdbc:oracle:thin:@hostname:portnumber:sid"; And could not resolve here is my Java code to establish a connection: package net.metric.action; import java.io.IOException; import java.io.PrintWriter; import java.sql.Connection; import java.sql.DriverManager; import java.sql.ResultSet; import java.sql.Statement; import javax.servlet.ServletException; import javax.servlet.http.HttpServlet; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpServletResponse; public class DemoServlet extends HttpServlet { private static final long serialVersionUID = 1L; protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { response.setContentType("text"); PrintWriter out = response.getWriter(); System.out.println("-------- Oracle JDBC Connection Testing ------"); try { Class.forName("oracle.jdbc.driver.OracleDriver"); } catch (ClassNotFoundException e) { System.out.println("Where is your Oracle JDBC Driver?"); e.printStackTrace(); return; } try{ DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver()); //CONNECT TO DB String url = "jdbc:oracle:thin:@252.112.60.47:1521:XE"; System.out.println(url); Connection conn = DriverManager.getConnection(url,"EXT02501231","Tellcom30"); conn.setAutoCommit(false); Statement stmt = conn.createStatement(); System.out.println("OK"); /* ResultSet rset = stmt.executeQuery("select * from SBO_AUDIT_NEW.AUDIT_EVENT"); while (rset.next()) { System.out.println (rset.getString(1)); } stmt.close(); System.out.println ("Ok.");*/ }catch(Exception e){ System.out.println(e.getMessage()); } } protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { // TODO Auto-generated method stub } } I'm getting this error : -------- Oracle JDBC Connection Testing ------ Io exception: The Network Adapter could not establish the connection What am I doing wrong? A
Share: ← Previous article Next article→ How to troubleshoot Oracle remote database connection June 7, 2013 by Kirill Loifman 22 Comments Many Oracle DBAs, developers and just end-users often encounter an issue when they can not connect remotely to an Oracle database. There can be different reasons of the connection problems. I give below a short cookbook on resolving those database connection issues. But first let’s explore a bit Oracle connectivity concepts and terminology. Oracle NET Client Server configuration An Oracle database is represented to clients as a service; that is, the database performs work on behalf of clients. The service name is included in the connect data part of the connect descriptor. To connect to a database service, clients use a connect descriptor that provides the location of the database and the name of the database service. The address portion of the connect descriptor is actually the protocol address of the listener. To connect to a database service, clients first contact a listener process that typically resides on the database server. The listener receives incoming client connection requests and hands these requests to the database server. Once the connection is established, the client and database server communicate directly. Ping database host IP ping 11.222.333.44 If it works, go to the next step; If not, check the server availability Ping database hostname ping orcl.dadbm.com if it works, go to the next step; if not, something wrong with DNS /ACTIVE directory => try using hosts file Test if listener port is reachable/opened for your remote connection For that use telnet utility which is available on Unix and can be enabled on Windows. 1. Linux example: $ telnet orcl1.dadbm.com 1522
Trying 10.126.247.11...
Connected to orcl.dadbm.com (12.222.333.44).
Escape character is '^]'.
get
Connection closed by foreign host. 2. Windows example 1) First enable telnet on Windows 7 if it’s not there: pkgmgr /iu:"TelnetClient" 2) Check the database port telnet orcl1.dadbm.com 1523
=> no output in case of a port opened; in case of a failure – see below Oracle error:
Could not open connection to the host, on port 1523: Connect failed In case the database listener port is not reachable you face potentially a firewall issue. There are at least two solutions of this problems. Both described in one of my presentations on SlideShare and in Demos on DaDBm YouTube channel. Test Oracl