Error Code 12154 Oracle
Contents |
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 oracle error 12154 received logging on to the standby to Oracle database. Today I will discuss the reason for this error oracle error 12154 encountered and possible resolutions.
Full error message: OLE DB provider "MSDAORA" for linked server "LINKED_ORA" returned message ora 12154 error in oracle "ORA-12154: TNS:could not resolve the connect identifier specified". Msg 7303, Level 16, State 1, Line 1 Cannot initialize the data source object of OLE DB provider "MSDAORA"Oracle Database Error 12154
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 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 ora 12154 could not resolve the connect identifier specified 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 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 intoserver but either failed to contact the server or did not find a matching service name on that server. TNS or 'Transparent Network Substrate' is a transport protocol that allows Oracle ora-12154 tns could not resolve the connect identifier specified windows 7 sessions to communicate across a network. DB Server <=> Listener <=> Network connection <=>
Tns Could Not Resolve The Connect Identifier Specified Oracle 10g
Client (SQL*Net) <=> Application. In the path above, tnsping can be used to test the parts in bold and should
Ora-12154 Sqlplus
be the first troubleshooting step. If tnsping fails, that generally indicates a problem finding the server connection - if TNSNAMES specifies an IP address, is it correct?, if it's a DNS name, is that 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/ resolving correctly? (try switching for an IP address to find out.) If tnsping succeeds, that can indicate a problem with the client configuration but could equally be that the connection is working as far as the listener but the database is down. Try comparing with another PC - if multiple machines are failing that usually points towards a server issue. Ora-12154 can be a tricky problem to nail http://ss64.com/ora/syntax-ora-12154.html down because there are many possible causes, try making a connection directly on the server or completely regenerate the TNSNAMES.ORA file on the client. ORA-12154 description: 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 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: 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 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 can make it unusable. Directory Naming: - Verify that "LDAP" is listed as one of the values of the NAM
Du siehst YouTube auf Deutsch. Du kannst diese Einstellung unten ändern. Learn more You're viewing YouTube in German. You can change this preference below. Schließen Ja, ich möchte sie behalten Rückgängig machen Schließen Dieses Video ist nicht verfügbar. WiedergabelisteWarteschlangeWiedergabelisteWarteschlange Alle entfernenBeenden https://www.youtube.com/watch?v=QVJ1xO2V7Dc Wird geladen... Wiedergabeliste Warteschlange __count__/__total__ How to resolve the ora 12154 error DBA http://www.bluegecko.com/ora-12154-tnscould-not-resolve-the-connect-identifier-specified/ Pro AbonnierenAbonniertAbo beenden1.9571 Tsd. Wird geladen... Wird geladen... Wird verarbeitet... Hinzufügen Möchtest du dieses Video später noch einmal ansehen? Wenn du bei YouTube angemeldet bist, kannst du dieses Video zu einer Playlist hinzufügen. Anmelden Teilen Mehr Melden Möchtest du dieses Video melden? Melde dich an, um unangemessene Inhalte zu melden. Anmelden Statistik 49.361 error 12154 Aufrufe 42 Dieses Video gefällt dir? Melde dich bei YouTube an, damit dein Feedback gezählt wird. Anmelden 43 17 Dieses Video gefällt dir nicht? Melde dich bei YouTube an, damit dein Feedback gezählt wird. Anmelden 18 Wird geladen... Wird geladen... Wird geladen... Die Bewertungsfunktion ist nach Ausleihen des Videos verfügbar. Diese Funktion ist zurzeit nicht verfügbar. Bitte versuche es später erneut. Veröffentlicht am 31.01.2014In this tutorial could not resolve you will learn how to resolve the ora 12145 error. Kategorie Menschen & Blogs Lizenz Standard-YouTube-Lizenz Mehr anzeigen Weniger anzeigen Wird geladen... Autoplay Wenn Autoplay aktiviert ist, wird die Wiedergabe automatisch mit einem der aktuellen Videovorschläge fortgesetzt. Nächstes Video Oracle - Understanding the tnsnames.ora and listener.ora files - Dauer: 12:46 Chris Ostrowski 88.976 Aufrufe 12:46 How to Fix ORACLE 6i Error "ORA-12154: TNS:could not resolve the connect identifier specified". - Dauer: 4:02 SYED AIZAD RAZA KAZMI 3.087 Aufrufe 4:02 ora - 12514 and ora - 12505 tns listener error fixed in 90 seconds - Dauer: 1:30 CBOT 1.346 Aufrufe 1:30 解决 Oracle ora-12514错误 - Dauer: 33:45 Maclean Liu 1.025 Aufrufe 33:45 Listener Basics For DBA - Dauer: 45:23 Satish Lodam 13.746 Aufrufe 45:23 Oracle Forms 10g TNS Configuration - Dauer: 3:39 Ravi shankar kumar 4.903 Aufrufe 3:39 Oracle listener configuration | listener.ora | listener configuration in oracle 11g - Dauer: 5:29 Wysheid Wysheid 10.553 Aufrufe 5:29 Oracle 10g Listener and Database Creation - Dauer: 6:05 Recouner 7.643 Aufrufe 6:05 Oracle - TNS : Protocol Adapter Error Working Solution - Dauer: 0:57 Srijit Banerjee 49.056 Aufrufe 0:57 How to install Oracle 10g on Windows 7 32bit 64
Blog Oracle MySQL News & Events Oracle Applications Amazon Web Services Jeremiah Wilton's Oradeblog OurSQL Community Podcast Remote DBA Team viewer Whitepapers About Us Philosophy The Blue Gecko Teams Employment Opportunities Partners News Press Contact Us March 4, 2009 by jwilton ORA-12154: TNS:could not resolve the connect identifier specified The error also appears in some versions as: "ORA-12154: TNS:could not resolve service name." When a program needs to connect to an Oracle service via Oracle Networking (SQL*Net), it must look up the connect data for that service somewhere. When the lookup fails, the Oracle client code raises ORA-12154. Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link. Note that this error is generated by the Oracle client code on the local host where the program is running, not by the remote Oracle service to which you are attempting to connect. There are a few ways that the Oracle client code can look up connect data: A flat file named tnsnames.ora Oracle Names service LDAP If you see the whole ORA-12154 error with the text, then your program is finding a working Oracle client install, but that the Oracle service as specified is not listed in tnsnames.ora, Oracle Names or LDAP. The most common causes of ORA-12154 are: The entry is missing from tnsnames.ora The entry in tnsnames.ora is malformed The program is using tnsnames.ora from the wrong ORACLE_HOME The program is not using a fully-qualified service name, but no default domain is enabled in sqlnet.ora Most sites use tnsnames.ora, but enough use Oracle Names and LDAP that the first step should be to determine which name resolution method is deployed at your site. If you are not the database administrator, you should get in touch with the people who manage your Oracle systems and find out which method you should be using. Often they will be able to provide guidance for resolving your problem in accordance with your site's standards. The client code decides which mechan