Error In Initializing Provider Ora-12154
Contents |
while creating a linked server to Oracle ★★★★★★★★★★★★★★★ SnehadeepJune 30, 201028 0 0 0 This is one of the most common errors while ora 12154 tns could not resolve the connect identifier specified 10g creating linked server to Oracle database. Today I will discuss the
Ora-12154 Tns Could Not Resolve The Connect Identifier Specified Windows 7
reason for this error and possible resolutions.
Full error message: OLE DB provider "MSDAORA" for ora-12154 tns could not resolve service name linked server "LINKED_ORA" returned message "ORA-12154: TNS:could not resolve the connect identifier specified". Msg 7303, Level 16, State 1, Line 1 Cannot initialize the data ora-12154 tns could not resolve service name oracle 11g 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 Oracle linked server issues. How to set up and troubleshoot a linked server to an Oracle database in SQL ServerTns Could Not Resolve The Connect Identifier Specified Oracle 10g
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 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 wresolve the connect identifier specified” ★★★★★★★★★★★★★★★ SnehadeepJanuary 26, 201010 0 0 0 When you try to develop an ora-06413 SSIS package in x64 Environment in BIDS that connects to test connection failed because of an error in initializing provider. ora-12170 a Oracle Database, you will invariably run into connectivity issues if the installed Oracle Client
Tns-03505 Failed To Resolve Name
tools version is 10.2.0.1 (x86). You will obviously need to install the 32-BIT version of Oracle Client to communicate with BIDS which is a 32-BIT 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/ application!
Subject: ORA-12154 or ORA-6413 Running 32-bit Oracle Software on 64-bit Windows OS. Applies to: Oracle Net Services - Version: 8.1.7.0 to 10.2.0.1 Oracle Data Provider for .NET - Version: 8.1.7.0 to 10.2.0.1 Oracle Objects for OLE - Version: 8.1.7.0 to 10.2.0.1 https://blogs.msdn.microsoft.com/dataaccesstechnologies/2010/01/26/connectivity-issue-with-oracle-in-x64-environment-ora-12154-tnscould-not-resolve-the-connect-identifier-specified/ Oracle Provider for OLE DB - Version: 8.1.7.0 to 10.2.0.1 Oracle ODBC Driver - Version: 8.1.7.0 to 10.2.0.1 Microsoft Windows XP (64-bit Itanium) Microsoft Windows Server 2003 (64-bit Itanium) Microsoft Windows XP (64-bit AMD64 and Intel EM64T) Microsoft Windows Server 2003 (64-bit AMD64 and Intel EM64T) Symptoms: You are attempting to connect to the Oracle database from a Windows platform using one of the following programmatic interfaces · ODBC · OLEDB · OO4O · ODP.NET After installing 32-bit Oracle client software on a 64-bit Windows operating system (OS) you receive one of the following errors: ORA-12154: TNS:could not resolve the connect identifier specified or ORA-6413: Connection not open. Cause: 64-bit Microsoft OS's install 32-bit applications into the following location "C:\Program Files (x86)\…"here 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 http://stackoverflow.com/questions/4457160/test-connection-failed-because-of-an-error-in-initializing-provider 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 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Test connection failed because of an error in initializing provider up vote 0 down vote favorite I get this error when trying to connect to a database server tns could remotely using udl file: Test connection failed because of an error in initializing provider. ORA-12545: Connect failed because target host or object does not exist I believe it is not a connectivity problem, because I can do these checklists successfully: ping IP address ping DNS name tnsping service name connect to the database using sqlplus, do select and other commands to the table reconfigure service using Oracle Net Configuration Assistant I also tried changing the host name tns could not in tnsnames.ora into its IP address, or put IP address and its alias name in etc\hosts, but it is still not working. I guess it is the problem in udl file. I use the same exact udl file with the one's in another PC that's working fine. Do you have any idea? windows oracle ora-12545 share|improve this question edited Apr 10 '11 at 17:20 OMG Ponies 198k36356415 asked Dec 16 '10 at 3:21 oliverwood 1232410 Are you using the 32 or 64bit client and what Oracle versions (server/client) are you using? –sbeskur Dec 16 '10 at 3:42 The client is 32 bit. Both server and client use Oracle version 10.2.0 –oliverwood Dec 16 '10 at 8:24 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote First guess, wrong IP or wrong oracle home is being used (and thus different tnsnames.ora). The other guess, I assume the UDL file is being used in a Windows-based PC : the error might be because the COM objects that being used as provider is not installed correctly. Maybe there is a problem with MDAC (Microsoft Data Access Components), you might also need to reinstall Oracle Client with Windows Interfaces enabled in custom options. share|improve this answer answered Dec 16 '10 at 3:41 YudhiWidyatama 1,1991014 I tried to reinstall Oracle Client but it i