Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Oracle connectivity issue with SSIS Expand / Collapse
Author
Message
Posted Wednesday, January 2, 2013 1:47 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 12:07 AM
Points: 1,183, Visits: 572
Hi All,

I have SQL Server 2008 R2 installed on Windows server 2008 R2. I have a requirement to fetch the data from Oracle using SSIS, so I have installed Oracle client (32-bit and 64-bit) along with ODAC for Oracle client.

Using OraOLEDB.Oracle provider I created a Linkedserver and able to pull the data using OPENQUERY.

But when I tried to pull the data from Oracle using SSIS (Microsoft OLEDB provider for Oracle), it is throwing the following error:

[Connection manager "OracleSourceDB"] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.

An OLE DB record is available. Source: "Microsoft OLE DB Provider for Oracle" Hresult: 0x80004005 Description: "Oracle client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3.3 or later client software installation. Provider is unable to function until these components are installed.".


Please suggest
Post #1401685
Posted Wednesday, January 2, 2013 4:12 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Today @ 6:16 AM
Points: 709, Visits: 1,418
Is the account that you are running the SSIS package from the same one that you installed/configured the Oracle client from? If not it could be a path issue.

Also, are you not able to select the OLE DB provider for Oracle from Oracle instead of the one from Microsoft? The Microsoft provided one was meant for older versions of Oracle and I do not believe is supported any longer.


Joie Andrew
"Since 1982"
Post #1401760
Posted Wednesday, January 2, 2013 4:41 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 12:07 AM
Points: 1,183, Visits: 572
I am not getting this, please put light on this

Is the account that you are running the SSIS package from the same one that you installed/configured the Oracle client from? If not it could be a path issue.
Post #1401770
Posted Wednesday, January 2, 2013 4:46 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 12:07 AM
Points: 1,183, Visits: 572
The accounts are different.
The account (using which sql server/integration services are running) is different from the account which used to install the oracle client on the machine.
Post #1401775
Posted Wednesday, January 2, 2013 4:51 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Today @ 6:16 AM
Points: 709, Visits: 1,418
The accounts are different.
The account (using which sql server/integration services are running) is different from the account which used to install the oracle client on the machine.


Then the problem could be that when you install the Oracle client the path environment variable gets set with the Oracle client path appended to it. It might be that the account you are using SSIS under does not have that in it. You can try appending the Path variable to include the Oracle client location and see if that resolves your issue. Here is an MSDN forum with a person who had a similar problem and their fix:

Running a SSIS package as a job error - with a connection to an Oracle database


Joie Andrew
"Since 1982"
Post #1401779
Posted Wednesday, January 2, 2013 4:53 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Friday, July 11, 2014 12:55 AM
Points: 729, Visits: 340
Check it at MSDN blog...

http://blogs.msdn.com/b/dataaccesstechnologies/archive/2009/11/10/ssis-error-code-dts-e-oledberror-an-ole-db-error-has-occurred-reasons-and-troubleshooting.aspx
Post #1401781
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse