Question : Trying to connect SSIS packages to Oracle database

Hi I need some urgent  expert assistance please!
I have been doing research around and haven't come up with much...

Story: We are currently migrating a reporting server for a client which runs SQL 2005 on a Windows 2003 STD Server to SQL 2008 on Windows 2008 R2.
This has been all successful and we are in the middle of our testing phase.... But we do have a problem

The reporting server extracts it data from an Oracle 10 database
On the reporting server we have had to install the Oracle 11 Client
      - This is the only client we could find which supports being installed on
      - Our team believes that there should not be a problem with backwards compatibility (Oracle 11 Client accessing Oracle 10 DB)

The problem we are experiencing is when trying to connect SSIS packages to Oracle database.
It appears that the SSIS being a 32 bit application is not able to communicate with Oracle 11g (64 Bit) through Oracle Provider for OLE DB.

Through so browsing through the internet i came across this article - but not sure if this would be the best approach or suitable to our situation
http://blogs.msdn.com/b/jorgepc/archive/2008/02/12/ssis-error-dts-e-cannotacquireconnectionfromconnectionmanager-when-connecting-to-oracle-data-source.aspx

So simply  The "Oracle OLE DB provider" is  not listed on the Native OLE DB on the Connection Manager.

ODB.Issue.1.0.PNG (26 KB) (File Type Details) 

Screen Shot

Are there any Hot Fixes available ?
Any Ideas or thoughts - would be much appreciated it!!

Thank you in advance I leave it in your Expert Hands!!










 

Answer : Trying to connect SSIS packages to Oracle database

You can install and run the SSIS Designer in 32 and/or 64bit on the same 64bit OS. I guess it will depend in your case on what type of OLEDB you have available. Oracle has both 32bit and 64bit available. You need to choose as required by your environment/application needs. See bottom for link with complete MS article; I've pasted what I thought was relevant:

"When you run a package in 64-bit mode, you might not be able to connect to as many data sources as you can when you run a package in 32-bit mode. Some .NET Framework Data Providers and native OLE DB providers might not be available in 64-bit versions. For example, the Microsoft OLE DB Provider for Jet, which connects to Access databases and Excel spreadsheets, is not available in a 64-bit version. Also, the SQL Server Compact Provider, which connects to SQL Server Compact data sources, is not available in a 64-bit version."

"Running Integration Services Packages on 64-bit Computers
--------------------------------------------------------------------------------

Sometimes you might want to run packages in 32-bit mode on a 64-bit computer. You might want to run packages in 32-bit mode for the following reasons:

•To run SQL Server 2000 DTS packages.

•To use a managed .NET Framework Data Provider or native OLE DB provider that is not available in a 64-bit version.

•To use a Script task or Script component that references other assemblies or COM components for which a 64-bit version is not available or not installed.

Selecting 32-bit or 64-bit Package Execution in SSIS Designer
In the Project Properties of an Integration Services package, you can select 32-bit or 64-bit execution by setting the value of the Run64BitRuntime property on the Debugging page. By default, the value of this property is True. When the 64-bit version of the Integration Services runtime is not installed, this setting is ignored."


From: http://msdn.microsoft.com/en-us/library/ms141766.aspx