Oraoledb Error 7399
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Problems with OraOLEDB.Oracle SQL Server > SQL Server Data Access Question 0 cannot initialize the data source object of ole db provider oraoledb.oracle for linked server 7303 Sign in to vote Good day everyone.... I have installed the OraOLEDB.Oracle Provider cannot get the column information from ole db provider "oraoledb.oracle" for linked server on 3 different servers, and have made a link server on all three. On two of the machines, I
Ole Db Provider Oraoledb.oracle For Linked Server Returned Message Ora-12154
am successful in retrieving data from the Oracle database. But, on the third machine, I receive this error: Server: Msg 7399, Level 16, State 1, Line 1The OLE DB provider "OraOLEDB.Oracle" for
Allow Inprocess
linked server "employee_prod" reported an error. The provider did not give any information about the error.Server: Msg 7303, Level 16, State 1, Line 1Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server "tims2_prod". On the machine which is generating the error, I can use SQL*Plus to connect to the remote database. I can also connect to the database microsoft sql server error 7303 linked server oracle using the "ODBC Data Source Administrator" when I create a system DSN. It would appear that the driver is installed and working correctly, but SQL Server can not access it. I have also uninstalled/installed serveral times. All of our servers are running W2003 Standard X64 with SQL Server 2005 Standard 64-bit Edition. Does anyone have any suggestions? Wednesday, June 07, 2006 12:34 PM Reply | Quote Answers 12 Sign in to vote Found the solution.... "Allow inprocess" has to be checked in the provider options. Wednesday, June 07, 2006 12:58 PM Reply | Quote All replies 12 Sign in to vote Found the solution.... "Allow inprocess" has to be checked in the provider options. Wednesday, June 07, 2006 12:58 PM Reply | Quote 0 Sign in to vote hi can you please send me the steps on how to stepup a connection to Oracle Database throught SQL Database. I have created a linked server, but i keep getting an error message OLE DB provider "OraOLEDB.Oracle" for linked server "DBCONN" returned message "ORA-12154: TNS:could not resolve the connect identifier specified". Msg 7303, Level 16, State 1, Line 1 Cannot ini
New? Advanced Search Forum Database Discussions Oracle Error 7399: OLE DB provider 'MSDAORA' reported an error. OLE DB error If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you
Cannot Initialize The Datasource Object Of Ole Db Provider For Linked Server
can post: click the register link above to proceed. To start viewing messages, select the forum that cannot create an instance of ole db provider oraoledb.oracle for linked server you want to visit from the selection below. Results 1 to 8 of 8 Thread: Error 7399: OLE DB provider 'MSDAORA' reported an error. OLE tns could not resolve the connect identifier specified sql server linked server DB error Tweet Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 02-18-2007,05:01 PM #1 indyandumi View Profile View Forum Posts Registered User Join Date Jan 2007 https://social.msdn.microsoft.com/Forums/sqlserver/en-US/a1a8dcbc-027c-4794-b13a-8bd4d7d4d682/problems-with-oraoledboracle?forum=sqldataaccess Posts 36 Error 7399: OLE DB provider 'MSDAORA' reported an error. OLE DB error My link server was working just fine until friday evening. It stopped worked over the week end. with and error Error 7399: OLE DB provider 'MSDAORA' reported an error. OLE DB error . ---my oracle 10g client is working just fine --TNS names looks fine ---i recreated the link but i am still getting the same error. I need your help because a lot of jobs are using that link http://forums.databasejournal.com/showthread.php?44887-Error-7399-OLE-DB-provider-MSDAORA-reported-an-error-OLE-DB-error on Monday it is going to be crazzzy. Reply With Quote 02-18-2007,07:11 PM #2 rmiao View Profile View Forum Posts Moderator Join Date Sep 2002 Posts 5,938 Reboot sql server if possible or try odbc provider for linked server. Reply With Quote 02-18-2007,07:43 PM #3 indyandumi View Profile View Forum Posts Registered User Join Date Jan 2007 Posts 36 rmaio, is to stop sql server the same as to reboot? What i did i stopt sql server and restarted, and then i used ODBC Connection but i keep getting the same error. ---I went to ODBC and setup oracle connection . Any new ideas Reply With Quote 02-18-2007,09:36 PM #4 rmiao View Profile View Forum Posts Moderator Join Date Sep 2002 Posts 5,938 Stopping sql is different from rebooting server since it can't recover os or network issues. Reply With Quote 02-18-2007,09:49 PM #5 indyandumi View Profile View Forum Posts Registered User Join Date Jan 2007 Posts 36 Thanks, i am gonna have to wait until tmwrw to restart the server. Reply With Quote 02-19-2007,09:46 AM #6 indyandumi View Profile View Forum Posts Registered User Join Date Jan 2007 Posts 36 rmaio, We restarted SQL server and we still had the same problem,the problem was on Linux server which runs oracle, so we stoped all oracle services and when we restarted the server BINGO, i am back in business. Thanks man Reply With Quote 02-28-2007,08:53 AM #7 skhanal View Profile View Forum Posts Experts Join Date Nov 2
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 about hiring developers or http://stackoverflow.com/questions/14499977/cannot-create-an-instance-of-ole-db-provider-error-as-windows-authentication-u 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, helping each other. Join them; it only takes a minute: Sign up “Cannot create an instance of OLE DB provider” error as Windows Authentication user up vote 12 down vote favorite 7 I am trying to run openrowset from MS SQL Server on an Oracle server. When linked server i execute the following command: select * from OPENROWSET('OraOLEDB.Oracle','srv';'user';'pass', 'select * from table') the following error occurs Msg 7302, Level 16, State 1, Line 1 Cannot create an instance of OLE DB provider "OraOLEDB.Oracle" for linked server "(null)". Can anyone tell me how I can use openrowset with OraOLEDB.Oracle? I am using 64 bit version of MS SQL Server and Oracle OLEDB driver. Edit I have tried this on two machines running Windows 7 x64 & Windows Server 2008 x64 with ole db provider MS SQL Server 2008 x64. Both showed the same error message. sql-server oracle oledb windows-authentication linked-server share|improve this question edited Nov 21 '13 at 14:10 patrickmdnet 2,3381627 asked Jan 24 '13 at 11:14 th1rdey3 2,05941544 I am trying to run OpenQuery against my linked server and getting same error. My linked server is using OraOLEDB.Oracle provider and I have already enabled the allow In Process option. The funny part is I have been using this linked server without any issue since last week, I did sql server reboot and it suddenly started to give error. –Amit Patel Jan 24 '13 at 17:22 add a comment| 4 Answers 4 active oldest votes up vote 28 down vote In SQL Server Enterprise Manager, open \Server Objects\Linked Servers\Providers, right click on the OraOLEDB.Oracle provider, select properties and check the "Allow inprocess" option. Recreate your linked server and test again. share|improve this answer edited Oct 1 '15 at 19:52 answered Jan 24 '13 at 12:28 David Brabant 18.1k64167 2 Brabank, I already tried that, but it still shows the same error. –th1rdey3 Jan 24 '13 at 12:47 Did you recreate your linked server? –David Brabant Jan 24 '13 at 12:48 yes, I have even restarted the sql service before recreating the linked server. but still no luck. –th1rdey3 Jan 24 '13 at 12:56 2 Thanks for this answer, it saved my day. –binu Jul 30 '