October 22, 2014 at 9:16 am
Hi all,
We have a series of SSIS packages that pull data from an Oracle DB into a SQL Server DWH. Most of the packages were originally developed on one of our development servers, and there were no issues with the connectors.
I am trying to move the development of new packages to the desktop (and then deploying to our ETL server), instead of developing right on the server. However this means I need the Oracle connectors installed locally.
Sometimes this works, but there are intermittent problems. When I first installed the this, what would happen would be I could create a new connection to the Oracle servers no problem, but when I opened a package first written on the server, the connection would fail to initialize with the error: "Test connection failed because of an error initializing the provider. OCIEnvCreate failed with return code -1 but error message text was not available". At the time, I could work around it by opening a dummy project and initializing the connection, then opening the existing project to edit.
But recently, it has started ALWAYS giving that error. Yesterday I uninstalled and reinstalled the Oracle ODP and everything went fine. However, today it is back to always failing. I have tried googling the error (find mostly pages of web projects trying to use these ado.net connectors), and tried the relevant troubleshooting advice.
Has anyone experienced a similar problem with Oracle connectors from a windows 7 desktop, and how did you address it?
EDIT: Actually, it appears the packages are using the OracleClient data provider, not the ODP.net one. The ODP.net one works, but I would need to set it up on our ETL server to use it.
So lets change the queston to "has anyone had this issue with the OracleClient data provider"?
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply