Solved

not able to connect oracle data source

Posted on 2011-09-09
6
2,212 Views
Last Modified: 2013-11-10
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
Comment
Question by:parpaa
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 16

Expert Comment

by:carsRST
ID: 36509794
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
 

Author Comment

by:parpaa
ID: 36510338
I am running this package in 32 bit only
0
 
LVL 16

Expert Comment

by:carsRST
ID: 36510405
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
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 

Author Comment

by:parpaa
ID: 36511827
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
 
LVL 16

Accepted Solution

by:
carsRST earned 500 total points
ID: 36511852
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
 

Author Comment

by:parpaa
ID: 36537137
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

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction In my previous article (http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SSIS/A_9150-Loading-XML-Using-SSIS.html) I showed you how the XML Source component can be used to load XML files into a SQL Server database, us…
In the first part of this tutorial we will cover the prerequisites for installing SQL Server vNext on Linux.
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed
Using examples as well as descriptions, and references to Books Online, show the documentation available for datatypes, explain the available data types and show how data can be passed into and out of variables.

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question