0

I have developed an SSIS package and it is running fine from visual studio. I have deployed this package to SQL server and created a job for its execution. Now the job is failing throwing an error at Data flow task which contains Oracle source.

Please find the below error that I received:

Error: The requested OLE DB provider OraOLEDB.Oracle.1 is not registered. If the 64 bit driver is not installed run the package in 32 bit mode.Error code: 0x00000000 An OLE DB record is available. Source: "Microsoft OLE DB Servoce Components" Hresult: 0x80040154. Description: "Class not registered".

Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Oracle_Source_DWH" failed with error code 0xC0209303. there may be error messages posted before this with more information on why the AcquireConnection method call failed.

Please help me how to resolve this error.

I tried uninstalling the Oracle client but didn't work.

Thanks in Advance, Chandu

chandu
  • 1
  • 1
  • You can try the suggestions in this link - https://stackoverflow.com/questions/12903366/oraoledb-oracle-provider-is-not-registered-on-the-local-machine – Subbu Jul 15 '17 at 16:37
  • Try following this link - https://blogs.msdn.microsoft.com/dataaccesstechnologies/2010/06/30/ora-12154-tns-could-not-resolve-the-connect-identifier-specified-error-while-creating-a-linked-server-to-oracle/ . I know the error message may be different but there are so many other checks to do, that may give you some indication. – VKarthik Jul 17 '17 at 01:39

1 Answers1

0

I suppose that you have Oracle client installed on your SQL Server machine, not only on your developer machine. In that case the most frequent reason of packages executing successfully in VS and fails on SQL Server is that VS using x86 provider, but SQL Server is using x64 version. You have 2 ways to fix that issue:

  1. Install x64 (or both x86 and x64 if you develop on server machine) Oracle clients on SQL Server machine.
  2. In theory (I've never used this) - on the "Execution options" tab of the job step set checkbox "Use 32 bit runtime".
Pavel Botygin
  • 187
  • 7