Oh great magi of Microsoft and Oracle, please help me!

I'm trying to get SSIS to connect to Oracle on 64-bit, but I'm having
trouble.

It's running Windows Server 2003 R2 (x64), SQL Server 2005 SP2 (x64),
and the full Oracle Client 11g1 (x64).

The Oracle client can connect to the server and the connection tests ok.
I can even pull data from SQL Lite. However, I'm having trouble
configuring SSIS to connect to Oracle so it can load the data in SQL Server.

Below are the error messages, and after them, I'll give you a bunch of
the things I've tried. Please don't overlook the little things. My
actual experience with Oracle is non-existent. I may have easily missed
something simple.

----------------------------------------------------------------------------
ERROR FROM MICROSOFT DRIVER:
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.
----------------------------------------------------------------------------
ERROR FROM ORACLE DRIVER:
Attempt to load Oracle client libraries threw BadImageFormatException.
This problem will occur when running in 64 bit mode with the 32 bit
Oracle client components installed.
----------------------------------------------------------------------------
CAN'T REMEMBER WHICH DRIVER:
The 'OraOLEDB.Oracle.1' provider is not registered on the local machine.
----------------------------------------------------------------------------
CAN'T REMEMBER WHICH DRIVER:
The specified module could not be found. (Exception from HRESULT:
0x8007007E)
----------------------------------------------------------------------------

THINGS I'VE TRIED:
Completely removed all previous Oracle installations and registry settings.

Reinstalled the full Oracle client x64. It's installed to
D:\Oracle\products\11.1\client\ so this directly contains bin. D: is a
local drive, not networked.

Completely uninstalled and reinstalled the Microsoft .NET Framework
versions 2.0 SP1 and 3.0 to ensure that the x64 versions were installed.

Ensured that ORACLE_HOME was set to the above directory in the
Environmental Variables.

Ensured that both ORACLE_HOME\bin and ORACLE_HOME\lib were in the path
ahead of everything else.

Ensured that ORACLE_HOME, ORACLE_HOME_NAME, ORACLE_GROUP_NAME, and
NLS_LANG were set in HKLM\Software\Oracle. Inst_loc is set to
C:\Program Files\Oracle\Inventory.

Set LOCAL in both the Environmental Variables and Registry.

Re-verified connectivity with the Test Connection button in Oracle
configuration and by pulling data through SQL Lite.

The only thing I haven't done that I can think of is use a Connection
String on Microsoft's ODBC drivers. I was planning on trying that tomorrow.

MY ANALSIS/THOUGHTS:
It's as if the Microsoft drivers don't know Oracle is installed, but I
don't know how to tell them it's installed. The only copy of ociw32.dll
is in ORACLE_HOME\bin.

I have no idea how the Oracle drivers are coming up with a 64/32 bit
mismatch considering that I personally removed and reinstalled the x64
client. (I didn't try uninstalling/reinstalling MS XML Parsing
services. Would that make a difference?)

I'm hoping there's somebody out there with a miracle answer for me, but
any help at all would be greatly appreciated.

Thanks in advance.

Joseph D. Wagner

On Jul 3, 10:50 am, "Joseph D. Wagner" <the... (AT) josephdwagner (DOT) info>
wrote:
Hi Joseph,
I don't know if this can help you... i had a similar problem with a
pkg trying to save data to excel: executed in visualstudio it worked,
executed from a job it didn't. Launching from inside the job with
cmdexec it worked.
The problem was with 64 bit sqlserver (apart oracle, i've your same
architecture) that cannot connect to 32bit jet oledb drivers, or with
dtexec utility that used 64bit drivers, or somewhat...

When i was searching for a solution i've read somewhere that pkg with
oracle connections had a similar resolution as well. Check it out!
http://forums.microsoft.com/MSDN/Sho...64293&SiteID=1
http://forums.microsoft.com/MSDN/Sho...59581&SiteID=1

hope this helps!
M.

On Jul 3, 10:50 am, "Joseph D. Wagner" <the... (AT) josephdwagner (DOT) info>
wrote:
Hi Joseph,
I don't know if this can help you... i had a similar problem with a
pkg trying to save data to excel: executed in visualstudio it worked,
executed from a job it didn't. Launching from inside the job with
cmdexec it worked.
The problem was with 64 bit sqlserver (apart oracle, i've your same
architecture) that cannot connect to 32bit jet oledb drivers, or with
dtexec utility that used 64bit drivers, or somewhat...

When i was searching for a solution i've read somewhere that pkg with
oracle connections had a similar resolution as well. Check it out!
http://forums.microsoft.com/MSDN/Sho...64293&SiteID=1
http://forums.microsoft.com/MSDN/Sho...59581&SiteID=1

hope this helps!
M.

On Jul 3, 10:50 am, "Joseph D. Wagner" <the... (AT) josephdwagner (DOT) info>
wrote:
Hi Joseph,
I don't know if this can help you... i had a similar problem with a
pkg trying to save data to excel: executed in visualstudio it worked,
executed from a job it didn't. Launching from inside the job with
cmdexec it worked.
The problem was with 64 bit sqlserver (apart oracle, i've your same
architecture) that cannot connect to 32bit jet oledb drivers, or with
dtexec utility that used 64bit drivers, or somewhat...

When i was searching for a solution i've read somewhere that pkg with
oracle connections had a similar resolution as well. Check it out!
http://forums.microsoft.com/MSDN/Sho...64293&SiteID=1
http://forums.microsoft.com/MSDN/Sho...59581&SiteID=1

hope this helps!
M.

On Jul 3, 10:50 am, "Joseph D. Wagner" <the... (AT) josephdwagner (DOT) info>
wrote:
Hi Joseph,
I don't know if this can help you... i had a similar problem with a
pkg trying to save data to excel: executed in visualstudio it worked,
executed from a job it didn't. Launching from inside the job with
cmdexec it worked.
The problem was with 64 bit sqlserver (apart oracle, i've your same
architecture) that cannot connect to 32bit jet oledb drivers, or with
dtexec utility that used 64bit drivers, or somewhat...

When i was searching for a solution i've read somewhere that pkg with
oracle connections had a similar resolution as well. Check it out!
http://forums.microsoft.com/MSDN/Sho...64293&SiteID=1
http://forums.microsoft.com/MSDN/Sho...59581&SiteID=1

hope this helps!
M.

On Jul 3, 10:50 am, "Joseph D. Wagner" <the... (AT) josephdwagner (DOT) info>
wrote:
Hi Joseph,
I don't know if this can help you... i had a similar problem with a
pkg trying to save data to excel: executed in visualstudio it worked,
executed from a job it didn't. Launching from inside the job with
cmdexec it worked.
The problem was with 64 bit sqlserver (apart oracle, i've your same
architecture) that cannot connect to 32bit jet oledb drivers, or with
dtexec utility that used 64bit drivers, or somewhat...

When i was searching for a solution i've read somewhere that pkg with
oracle connections had a similar resolution as well. Check it out!
http://forums.microsoft.com/MSDN/Sho...64293&SiteID=1
http://forums.microsoft.com/MSDN/Sho...59581&SiteID=1

hope this helps!
M.

On Jul 3, 10:50 am, "Joseph D. Wagner" <the... (AT) josephdwagner (DOT) info>
wrote:
Hi Joseph,
I don't know if this can help you... i had a similar problem with a
pkg trying to save data to excel: executed in visualstudio it worked,
executed from a job it didn't. Launching from inside the job with
cmdexec it worked.
The problem was with 64 bit sqlserver (apart oracle, i've your same
architecture) that cannot connect to 32bit jet oledb drivers, or with
dtexec utility that used 64bit drivers, or somewhat...

When i was searching for a solution i've read somewhere that pkg with
oracle connections had a similar resolution as well. Check it out!
http://forums.microsoft.com/MSDN/Sho...64293&SiteID=1
http://forums.microsoft.com/MSDN/Sho...59581&SiteID=1

hope this helps!
M.

On Jul 3, 10:50 am, "Joseph D. Wagner" <the... (AT) josephdwagner (DOT) info>
wrote:
Hi Joseph,
I don't know if this can help you... i had a similar problem with a
pkg trying to save data to excel: executed in visualstudio it worked,
executed from a job it didn't. Launching from inside the job with
cmdexec it worked.
The problem was with 64 bit sqlserver (apart oracle, i've your same
architecture) that cannot connect to 32bit jet oledb drivers, or with
dtexec utility that used 64bit drivers, or somewhat...

When i was searching for a solution i've read somewhere that pkg with
oracle connections had a similar resolution as well. Check it out!
http://forums.microsoft.com/MSDN/Sho...64293&SiteID=1
http://forums.microsoft.com/MSDN/Sho...59581&SiteID=1

hope this helps!
M.

On Jul 3, 10:50 am, "Joseph D. Wagner" <the... (AT) josephdwagner (DOT) info>
wrote:
Hi Joseph,
I don't know if this can help you... i had a similar problem with a
pkg trying to save data to excel: executed in visualstudio it worked,
executed from a job it didn't. Launching from inside the job with
cmdexec it worked.
The problem was with 64 bit sqlserver (apart oracle, i've your same
architecture) that cannot connect to 32bit jet oledb drivers, or with
dtexec utility that used 64bit drivers, or somewhat...

When i was searching for a solution i've read somewhere that pkg with
oracle connections had a similar resolution as well. Check it out!
http://forums.microsoft.com/MSDN/Sho...64293&SiteID=1
http://forums.microsoft.com/MSDN/Sho...59581&SiteID=1

hope this helps!
M.

On Jul 3, 10:50 am, "Joseph D. Wagner" <the... (AT) josephdwagner (DOT) info>
wrote:
From MsTechnet:
Integration Services Considerations on 64-bit Computers
http://technet.microsoft.com/en-us/l.../ms141766.aspx

let us know
M.