Linked Server Error 7303 Oracle
Contents |
360 games PC games sql server 2012 linked server oracle Windows games Windows phone games Entertainment All Entertainment microsoft sql server error 7303 linked server Movies & TV Music Business & Education Business Students & educators sql server oracle linked server query syntax Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet cannot initialize the data source object of ole db provider "oraoledb.oracle" for linked server Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All
Oracle Linked Server Equivalent
Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a
Cannot Create An Instance Of Ole Db Provider Oraoledb.oracle For Linked Server
title. You can not post a blank message. Please type your message cannot initialize the data source object of ole db provider "msdaora" for linked server and try again. More discussions in Oracle Provider for OLE DB All PlacesDatabaseDatabase Application DevelopmentWindows and .NETOracle Provider sp_helplinkedsrvlogin for OLE DB This discussion is archived 2 Replies Latest reply on Oct 10, 2012 1:55 AM by 967297 Steps to connect SQL Server to Oracle works but WHY ?? 888236 https://support.microsoft.com/en-us/kb/280106 Sep 21, 2011 6:18 PM The following steps is what I have to do in order to get SQL Server to talk to an Oracle database. These steps, for me, work 100% of the time. Any deviation from the following steps will result in failure. Rebooting the machine didn't make any difference between each of the steps. My question is why I https://community.oracle.com/thread/2289794 have to install the client a second time? All the documentation that I have found at Oracle, Microsoft, or elsewhere state that I only need the InstantClient. ========================================= Some server I don't have access to with Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit installed Windows XP SP3 - 32bit with Microsoft SQL Server 2005 SP3 installed The following steps are done on the Windows XP machine. 1) install win32_11gR2_client Select: InstantClient (174.0MB) Path: C:\Oracle 2) install ODTwithODAC112021 Select: Oracle Data Access Components for Oracle Client Oracle Base: C:\Oracle Name: OraClient11g_home1 Path: C:\Oracle\product\11.2.0\client_1 3) Add entries for tnsnames.ora and sqlnet.ora 4) Ensure environmental variable ORACLE_HOME is set to C:\Oracle\product\11.2.0\client_1 5) SQL Server Management Studio Check "Allow Inprocess" for Oracle Provider OraOLEDB.Oracle Restart SQL Server Try to add link to Oracle - fails to connect "The test connection to the linked server failed." Additional information: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) Cannot initialize the data source object of OLE DB Provider "OraOLEDB.Oracle" for linked server "ORACLEDB". OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLEDB" returned message "". (Microsof
he was facing while creating a Linked Server to an Oracle database. He was trying to create a Linked Server to a Oracle Database from a SQL Server 2005 instance. He http://www.sqldbadiaries.com/2010/12/27/cannot-create-an-instance-of-ole-db-provider-oraoledb-oracle-for-linked-server/ had the Oracle Client components installed on the server hosting the SQL Server instance. After giving all the details in the Linked Server properties when clicking on Ok, he would receive the following error message. Since the linked server is Oracle, the first thing that I tried was to check if the Server hosting the SQL Server instance, was able to connect to the listener on the Oracle Database linked server Server using tnsping. tnsping successfully connected to the Oracle database from the SQL Server box. Then I moved on to check the Provider details while creating the Linked Server. The Linked Server provider was Oracle Provider for OLE DB. This is the driver that gets installed along with the Oracle Client Components. This KB article states that Error 7302 can be a result of MSDAORA.dll not being registered correctly. of ole db In this case it had to be an issue with the dll related to Oracle Provider for OLE DB i.e.OraOleDB.dll. Before checking the dll related issues, I wanted to check if something was missing in the registry. The list of Providers in the Linked Server is populated from the Providers key in the registry. This key is located under the instance name under the below key. The entries in the registry looked like this. I could not find anything unusual here. Now it was confirmed that something must be wrong with the OraOleDB.dll. This dll is located under the bin directory of the folder where Oracle Client Components are installed (usually called oracle_home). When I navigated to that folder, I could not find any such files. To confirm this, I checked that directory on a *working* instance, the OraOleDB.dll was listed there. Now my job was easy. On the server which was having issues with the Linked Server, the Oracle Client Components were either not installed correctly or it was corrupt. I copied the dll from the *working* server and pasted it under