February 14, 2013 at 3:24 pm
I had a nightly SSIS package running on Server 2008 R2 that used the Oracle Provider for Ole DB. We have the Oracle Database as a linked server and the package was running fine. One night a couple of weeks ago, we got a error that the SQL server could not initialize the data source object of Ole DB Provider "OraOleDB.Oracle" for linked server "NAME". Microsoft SQL Error 7399.
We had put a patch on the evening before and attributed that to getting the error. We unistalled Oracle and reinstalled it and set up the TNSNames file again. And the package started running again.
Last night, the same thing happened, however, I have been told that no changes were made to the SQL server or to Oracle.
Has anybody else had this issue and knows what causes this? Obviously to fix it, we will uninstall Oracle and reinstall it, however, we need to know how to prevent this from happening in the future.
Thanks for any help.
February 15, 2013 at 2:02 pm
Did the oraclemts service stop running? Do you have the latest oracle client?
February 15, 2013 at 2:35 pm
No, the oraclemts service did not stop running and we have Oracle 11.2.0
Thanks.
February 16, 2013 at 3:30 am
We had a strange cause oracle transactions failing after sometime.
It was fixed with a reboot of the server after an installation of the 11.2 client (for the post reboot file replacements). Without the reboot, the old oracle client (10) somehow lived on.
Another thing might be the non-sqlserver memory pool in ms sql server,
which is used by in-process extensions like the oracle linked server (startup option -g), but that was in the year 2000
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply