troubleshooting Question
MSDAORA provider stopped working
asked on
All,
My problem is that the MSDAORA provider within my SQL Server has stopped working. When trying to connect I get the following error message:
Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server.
OLE DB provider "MSDAORA" for linked server "WB_PWBRPR" returned message "Oracle client and networking components were not found.
SQL Server 2005 installed on windows server 2003. Oracle 9.2 network client installed.
I have a stored procedure that is using the OPENQUERY method that is pulling data from the linked server connected through the MSDAORA provider. Up until a week ago this procedure was working fine. Now I am getting the error above in the procedure and when I try to test the connection in SSMS.
The same server is also running SSIS packages that pull data on a scheduled basis from the same oracle datasource. In Visual Studio the OLE connection to the same datasource connects without and issue and the SSIS packages run without an issue. That leads me to believe that the oracle network client is not the issue, but the MSDAORA provider in SQL Server has been changed in some way.
I need help on how to fix the MSDAORA provider in this SQL Server. I'm thinking I will have to update something in the registry, but not sure at all what that would be or where to find it.
Thank you for your help.
My problem is that the MSDAORA provider within my SQL Server has stopped working. When trying to connect I get the following error message:
Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server.
OLE DB provider "MSDAORA" for linked server "WB_PWBRPR" returned message "Oracle client and networking components were not found.
SQL Server 2005 installed on windows server 2003. Oracle 9.2 network client installed.
I have a stored procedure that is using the OPENQUERY method that is pulling data from the linked server connected through the MSDAORA provider. Up until a week ago this procedure was working fine. Now I am getting the error above in the procedure and when I try to test the connection in SSMS.
The same server is also running SSIS packages that pull data on a scheduled basis from the same oracle datasource. In Visual Studio the OLE connection to the same datasource connects without and issue and the SSIS packages run without an issue. That leads me to believe that the oracle network client is not the issue, but the MSDAORA provider in SQL Server has been changed in some way.
I need help on how to fix the MSDAORA provider in this SQL Server. I'm thinking I will have to update something in the registry, but not sure at all what that would be or where to find it.
Thank you for your help.
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 7 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
Our community of experts have been thoroughly vetted for their expertise and industry experience.
The Distinguished Expert awards are presented to the top veteran and rookie experts to earn the most points in the top 50 topics.