12154 Oracle 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. connect identifier ORA-12152: TNS:unable to send break message Cause: Unable to send break message. Connection
Oracle Connection Error Ora-12154
probably disconnected. Action: Reestablish connection. If the error is persistent, turn on tracing and reexecute the operation. ORA-12153: TNS:not connected Cause: error ora-12154 tns could not resolve the connect identifier specified Not currently connected to a remote host. Action: Reestablish connection. ORA-12154: TNS:could not resolve the connect identifier specified Cause: A connection to a database or other service was requested using a connect identifier,
Ora-12154 Tns Could Not Resolve Service Name
and the connect identifier specified could not be resolved into a connect descriptor using one of 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): ora 12154 tns no listener - 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 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 Ne
while creating a linked server to Oracle ★★★★★★★★★★★★★★★ SnehadeepJune 30, 201028 0 0 0 This is one of the most common errors while creating linked server to Oracle database. Today I will discuss the reason for this error and possible
0ra-12154
resolutions.
Full error message: OLE DB provider "MSDAORA" for linked server "LINKED_ORA"Oracle Error 12541
returned message "ORA-12154: TNS:could not resolve the connect identifier specified".
Msg 7303, Level 16, State 1, Line 1 Cannot initialize oracle error 12154 encountered the data source object of OLE DB provider "MSDAORA" for linked server "LINKED_ORA". First of all make sure you have reviewed the following Microsoft KB article that has a lot of good information on troubleshooting https://docs.oracle.com/cd/B19306_01/server.102/b14219/net12150.htm Oracle linked server issues. How to set up and troubleshoot a linked server to an Oracle database in SQL Server http://support.microsoft.com/kb/280106 Also make sure you have installed Oracle Client on the SQL server. If the SQL server is 64 bit then we need to install 64 bit Oracle provider. You can also create linked server using Oracle ODBC driver together with Microsoft OLE DB provider for ODBC. Once again on a https://blogs.msdn.microsoft.com/dataaccesstechnologies/2010/06/30/ora-12154-tns-could-not-resolve-the-connect-identifier-specified-error-while-creating-a-linked-server-to-oracle/ 64 bit SQL server you need to install the 64-Bit OLEDB Provider for ODBC (MSDASQL) and 64 bit Oracle ODBC drivers. However 64-Bit OLEDB Provider for ODBC (MSDASQL) is already there in Windows Vista/Windows Server 2008 and later OS. This particular error message is a very general error message and can happen for quite a number of reasons. For general understanding of the error, you can review oracle documentation like this http://ora-12154.ora-code.com/ In SQL Server Linked Server, it could indicate a few things (not limited to)– 1. SQL Server (and oracle net libraries) is not able to get the TNS alias from tnsnames.ora file. 2. Something is wrong with the way the alias is created in the tnsnames.ora file (incorrect syntax) 3. TNS alias could not be resolved into a connect descriptor Below is a list of things that you can try to resolve this issue. 1. Verify that the tnsnames.ora file has the alias and the service name that the customer is using. TNS entry for the Oracle database =========================== OracleDB_Dev = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = server01.mydomain.com)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = OracleDB) (SERVEresolve the connect identifier specified"? Article: 00951 Last Reviewed: 7th September 2006 Revision: 1 This error indicates that Oracle is unable to http://www.easysoft.com/support/kb/kb00951.html locate the service name specified in your Easysoft ODBC-Oracle Driver ODBC data source. You need to check the Database attribute value in the data source.If you are using the https://www.techonthenet.com/oracle/errors/ora12154.php standard Oracle client, the Database attribute value must specify a valid service name defined in tnsnames.ora. For example, for the following tnsnames.ora entry, the Database attribute value needs oracle error to be my_database: my_database = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = my_host)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = my_database) ) ) If you are using the Instant Client without a tnsnames.ora file, the Database attribute value needs to be a SQL connect URL rather than a service name: //host:port/service_name where host is the ora-12154 tns could host name or IP address of the Oracle database server, port is the Oracle listener port and service_name is the service name. For example: //my_host:1521/my_database If you want to use the Instant Client with a tnsnames.ora file, the Database attribute value must specify a tnsnames.ora service name and you need to set and export the TNS_ADMIN environment variable. Set TNS_ADMIN to specify the location of the tnsnames.ora file. For example: TNS_ADMIN = /home/oracle/network/admin export TNS_ADMIN Applies To Products Easysoft ODBC-Oracle Driver Knowledge Base Feedback * Did this content help you? Yes No Maybe * Please select one option based on your first choice: I'm very satisfied I think it will help, but I haven't tried it yet It is helpful, but I need more information It is helpful, but hard to understand Seemed relevant in search results, but didn't help me The information is incorrect The page contains one or more broken links Suggest new content or let us know how we can improve this content: (* Required Fields) About Easysoft Contact
MySQL MariaDB PostgreSQL SQLite MS Office Excel Access Word Web Development HTML CSS Color Picker Languages C Language More ASCII Table Linux UNIX Java Clipart Techie Humor Advertisement Oracle Basics ALIASES AND AND & OR BETWEEN COMPARISON OPERATORS DELETE DISTINCT EXISTS FROM GROUP BY HAVING IN INSERT INSERT ALL INTERSECT IS NOT NULL IS NULL JOIN LIKE MINUS NOT OR ORDER BY PIVOT REGEXP_LIKE SELECT SUBQUERY TRUNCATE UNION UNION ALL UPDATE WHERE Oracle Advanced Oracle Cursors Oracle Exception Handling Oracle Foreign Keys Oracle Loops/Conditionals Oracle Transactions Oracle Triggers String/Char Functions Numeric/Math Functions Date/Time Functions Conversion Functions Analytic Functions Advanced Functions Oracle / PLSQL: ORA-12154 Learn the cause and how to resolve the ORA-12154 error message in Oracle. Description When you encounter an ORA-12154 error, the following error message will appear: ORA-12154: TNS:could not resolve service name Cause You tried to connect to Oracle, but the service name is either missing from the TNSNAMES.ORA file or is incorrectly defined. Resolution The option(s) to resolve this Oracle error are: Option #1 Make sure that the TNSNAMES.ORA file exists and is in the correct directory. Option #2 Make sure that the service name that you are connecting to is included in the TNSNAMES.ORA file and that it is correctly defined. Option #3 Make sure that there are no syntax errors in the TNSNAMES.ORA file. For example, if there are unmatched parentheses in the file (ie: open bracket without the corresponding close bracket), the file will be rendered unusable. Share this page: Advertisement Back to top Home | About Us | Contact Us | Testimonials | Donate While using this site, you agree to have read and accepted our Terms of Service and Privacy Policy. We use advertisements to support this website and fund the development of new content. Copyright © 2003-2016 TechOnTheNet.com. All rights reserved.