MSDAORA provider stopped working
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.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Can't remember, but it might be that Ora 9.2 did not install the OLE DB provider.
Can we exclude x64 / x86 as an issue?
Can we exclude x64 / x86 as an issue?
BTW, TNS home and TNSNames.ORA do not need to use the same location. TNS_ADMIN will tell where to find the TNSNames.ora, but not necessarily where to find the drivers.
Check the defaults in HKLM\Software\Oracle. You should have a subkey with your ORACLE_HOME name, like HOME0, and a value for ORACLE_HOME which points to the correct client path (without the bin and stuff). (That is what I mistakenly called "TNS Home" - sorry for that!)
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Qlemo's input help me to find a solution to the problem I was having. However the primary issue was to understand what would have caused the MSDAORA provider which was previously working properly to have stopped working, and how to correct that issue to restore the MSDAORA provider to properly function again.
ASKER
TNS is not the issue. As stated above the same TNSnames.ora is being used in the SSIS package which is successfully connecting to the Oracle DB. I created another linked server to a different Oracle DB, which again connects successfully in VisualStudio but also fails due to the MSDAORA issue I noted above.
I would try the Oracle provider, but it isn't listed as provider option in SSMS. I'm not sure why that provider isn't listed since the oracle network componants are installed and I'm not sure how to get it added.