Can't get Oracle OLE DB provider to work from SSIS on a 64-bit environment



Hi

I posted this question in the .server newsgroup yesterday, but apparently my cross-post to this newsgroup didn't made it, so now I post it once more.

I'm having some troubles setting up an Oracle datasource on a SSIS
installation running 64-bit. We have it setup in our test/dev
environment running 32-bit where it works with Microsoft OLEdb Provider
for Oracle. Since this Provider isn't available in the 64-bit version I
was told to install the Oracle OLE DB provider client.
I did that and from Management Studio on that server, I can set up a
linked server using this provider and that works fine. When I then in
SSIS set up a connection using this Oracle OLE db provider and
specifying the same servername, I get an error when I test the
connection. The error is :

Test connection failed because of an error in initializing provider.
ORA-12154: TNS: kunne ikke fortolke den angivne
forbindelsesidentifikator (The last bit is in Danish and translated it
says something like 'Couldn't understand the actual connection
indicator').

If I look a the providers that are being used, I can see that the linked
server is using a provider called 'OraOLEDB.Oracle' where in SSIS it's
using a provider called 'OraOLEDB.Oracle.1'. This is most likely
because I first installed the regular Oracle client and then later on
when I figured out that I need the Oracle ODAC I installed that. I then
ended up with 2 Oracle "client" installations, so that is most likely
why I see 2 different providers. What then puzzles me, is how I can
choose which one to use. No matter what I do, it seems like the .1 is
chosen in SSIS. I've even tried to uninstall the "old" client but that
doesn't make any difference.
I'd love to uninstall both Oracle clients and then try just to install
the ODAC, but that isn't that simple. First of all, there are no way to
uninstall ODAC and when I uninstall the regular Oracle Client with the
installer, it still leaves a lot of files and registry entires around..:-(.

I've set up Oracle connections many times and feel I'm having a fair
grip of how it should be done, but this 64-bit /SSIS issue is driving me
nuts.....

Does any of you have any good suggestions on how to solve this issue?

--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator


.



Relevant Pages

  • Re: Cant get Oracle OLE DB provider to work from SSIS on a 64-bit environment
    ... The project I'm trying to get running, consists of approx 25 seperate packages where 3-4 of them gets data from different Oracle sources, but I'm not even got to the point where I'm trying to run the whole lot. ... There are two issues in the topic that could be an issue, and that is to switch the whole project to 32-bit mode and then the part that says that the Designer only shows 32-bit versions of the provider. ... What I think I'll try now, it to install the 32-bit version of the Oracle ODAC to see if that makes any difference. ... uninstall ODAC and when I uninstall the regular Oracle Client with the ...
    (microsoft.public.sqlserver.dts)
  • Re: Cant get Oracle OLE DB provider to work from SSIS on a 64-bit environment
    ... If the 32-bit driver worked well for you, you can have your SSIS package run ... I'm having some troubles setting up an Oracle datasource on a SSIS ... Since this Provider isn't available in the 64-bit version I ... I'd love to uninstall both Oracle clients and then try just to install ...
    (microsoft.public.sqlserver.dts)
  • Cannot Install Windows Server 2003 SP1
    ... I have two domain controllers, the issue is with one of the domain ... It will happily install SP1 but when the system reboots after ... I am able to logon to the server but cannot talk to or ping anything else on ... A provider, Rsop Planning Mode Provider, has been registered in the WMI ...
    (microsoft.public.windows.server.general)
  • Re: Oracle Database Access via IIS 6.0 ASP Pages on Windows 2003 S
    ... communicate back through IIS to SQL*NET installed for the Oracle Client. ... Microsoft SQL Server 2000 Standard with SP3a installed on same box. ... Microsoft OLE DB Provider for ODBC Drivers error '80004005' ...
    (microsoft.public.inetserver.iis)
  • Error initializing provider (Microsoft OLE DB provider for oracle)
    ... administrator account in win2k server. ... When Microsoft OLE DB Provider for Oracle is used as new data source ... it gives "An error in initializing provider. ...
    (microsoft.public.sqlserver.olap)