[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2328
  • Last Modified:

not able to connect oracle data source

Error: 2011-09-09 06:13:37.80
   Code: 0xC0209303
   Source: DW_EMEA_Import Connection manager "Source"
   Description: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR.  The requested OLE DB provider MSDAORA.1 is not registered -- perhaps no 64-bit provider is available.  Error code: 0x00000000.
An OLE DB record is available.  Source: "Microsoft OLE DB Service Components"  Hresult: 0x80040154  Description: "Class not registered".
0
parpaa
Asked:
parpaa
  • 3
  • 3
1 Solution
 
carsRSTCommented:
You'll need to run it as 32 bit as opposed to 64 bit.

See link below for quick reference on how to do.

http://sqlblog.com/blogs/john_paul_cook/archive/2010/03/24/running-32-bit-ssis-in-a-64-bit-environment.aspx
0
 
parpaaAuthor Commented:
I am running this package in 32 bit only
0
 
carsRSTCommented:
Two possibilities for this error.   Either you don't have the driver or you're not in fact running as 32 bit.

If you run under SQL Agent, you have to check the box to run as 32 bit, regardless of how you ran under BIDS.



 image-thumb-50B7E098.png
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
parpaaAuthor Commented:
i am running  this package trow batch file
  the batch file is calling trow tidal

this is my batch file script


echo =====================EXECUTE  PACKAGE =====================
PATH=%PATH%;G:/TIDAL/Agent/Bin;E:/Program Files (x86)/Microsoft SQL Server/100/DTS/Binn/dtexec

/F "g:/rmt_dev/TMR_dev/jobs/SSIS_Packages/viterra.dtsx" /DE ABTABLES


IF %errorlevel% NEQ 0 GOTO DTSRUN_ERR_EXIT
GOTO SUCCESS_EXIT
:DTSRUN_ERR_EXIT
echo.
echo ABENDED: ERROR running SSIS package
OCSEXIT.exe 10
GOTO EXIT
:SUCCESS_EXIT
echo.
echo COMPLETED SUCCESSFULLY
OCSEXIT.exe 0
GOTO EXIT
:EXIT
echo.
echo FINISHED: %date% %time%
echo on
0
 
carsRSTCommented:
See link.  If you're running from the command line, you'll need to make sure you're running the 32 bit command line version of the dtexec utility.


http://msdn.microsoft.com/en-us/library/ms162810.aspx
"If you have to run certain packages in 32-bit mode, you will have to install the 32-bit version of the dtexec utility.  To install the 32-bit version of the dtexec utility, you must select either Client Tools or Business Intelligence Development Studio during setup."
0
 
parpaaAuthor Commented:
Hi

by doing so many triles, now able to connect the oracle server

now i am running the ssis package in 64 bit
and i used the oledprovider is Native  OLED DB\ Oracle provider for OLED DB

now i am able to connect the server, but when i am trying run this i am getting below validation errors


Error: 2011-09-14 14:48:45.29
   Code: 0xC02020F6
   Source: Import Operators OLE DB Source [1]
   Description: Column "NAME" cannot convert between unicode and non-unicode string data types.
End Error
Error: 2011-09-14 14:48:45.29
   Code: 0xC02020F6
   Source: Import Operators OLE DB Source [1]
   Description: Column "FULL_NAME" cannot convert between unicode and non-unicode string data types.
End Error
Error: 2011-09-14 14:48:45.29
   Code: 0xC02020F6
   Source: Import Operators OLE DB Source [1]
   Description: Column "EDS_CONTACT_NAME" cannot convert between unicode and non-unicode string data types
.
.
.
.
.

Error code 0xC0024107
Error: 2011-09-14 14:48:45.32
   Code: 0xC004706B
   Source: Import Operators SSIS.Pipeline
   Description: "component "OLE DB Source" (1)" failed validation and returned validation status "VS_ISBROKEN".
The Execution method succeeded, but the number of errors raised (14) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number
specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.


please help me in this
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now