The 'OraOLEDB.Oracle.1' provider is not registered on the local machine

Question

The 'OraOLEDB.Oracle.1' provider is not registered on the local machine

Arcturus

Mr or Mrs. 500

Points: 563
More actions
July 25, 2013 at 2:26 pm

#277946

I have a SSIS (2005) package which was developed on a 32 bit machine. The Package connects to the oracle database and have 2 connections (1 using the MS provider for Oracle and other being Oracle Provider for Oracle).
This works fine on my machine but when deployed on Production server which is a 64-bit machine and executed through a SQL server agent job it gives an error "The 'OraOLEDB.Oracle.1' provider is not registered on the local machine".
I have also installed 32 bit oracle client on this machine.
Inputs needed...

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 1

Is the provider name the same for 64 and 32 bit?

You likely will need to run the package with the 32-bit runtime, this is harder in SQL 2005, they made it easier in 2008 with a little checkbox.. But 2005 you usually have to build the command yourself. There are some lovely tutorials on it online.

CEWII

Arcturus Mr or Mrs. 500 Points: 563 More actions · Answer 2

Yes. The provider names are the same and I am running the package using CmdExec which uses the 32-bit runtime.

Koen Verbeeck SSC Guru Points: 259105 More actions · Answer 3

Arcturus (7/25/2013)
Yes. The provider names are the same and I am running the package using CmdExec which uses the 32-bit runtime.

Can you show us the command line?

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

Arcturus Mr or Mrs. 500 Points: 563 More actions · Answer 4

C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTExec.exe /FILE "C:\Package.dtsx" /CONFIGFILE "<C:\PackageConfig.dtsconfig>" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E

Koen Verbeeck SSC Guru Points: 259105 More actions · Answer 5

The command line seems to be fine.

You installed the Oracle client, but did you also install the 32-bit provider?

Why not try to run the package in 64-bit by the way?

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

rswilliams 94513 SSC Enthusiast Points: 171 More actions · Answer 6

I am having a similar problem. I am using SQL Server 2012 and and running the package via SSDT debugging. I have read several other entries on this error and subsequently have (1) Reinstalled the Oracle client, (2) registered the Oracle provider, and (3) made sure that my user id had read/execute rights to the Oracle home directory. I am still getting this error.

I am using the 64-bit Developers Edition running the 32-bit Oracle client. I also have two environments, one older one that works fine (calling this one the 'Test' environment) and a new one (calling this one the 'Dvlp' environment) where I am getting this error. The only obvious difference between the two is that I have both the 32-bit and the 64-bit Oracle clients installed in the Test environment that works. Our Oracle DBAs have told me that even though we have installed both versions of the Oracle Client, we're actually using the 32-bit version on that server.

When trying to create a connection in the new Dvlp environment, I can successfully test the connection the Oracle server, but when I use the saem connection string in my program, I get the "'OraOLEDB.Oracle.1' provider is not registered on the local machine." error. I have doubled checked that the connection strings used are the same, but the program(SSIS Visual Basic Script Component) is not working.

I'd appreciate any help on this one.

Thanks,

Randy

Koen Verbeeck SSC Guru Points: 259105 More actions · Answer 7

If you have only installed the 32-bit client on the new server, try setting Run64BitRuntime on the project to false.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

rswilliams 94513 SSC Enthusiast Points: 171 More actions · Answer 8

Setting the project property Run64BitRuntime to False fixed the problem.

Thanks,

Randy

Koen Verbeeck SSC Guru Points: 259105 More actions · Answer 9

rswilliams 94513 (8/14/2013)
Setting the project property Run64BitRuntime to False fixed the problem.
Thanks,
Randy

Great, glad that you got it solved.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP