Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS 2008 and Oracle database connectivity Issue in a 64 bit machine Expand / Collapse
Author
Message
Posted Wednesday, February 9, 2011 5:12 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: 2 days ago @ 9:28 AM
Points: 44, Visits: 56
Hi,

I have an SSIS package that retrieves data from an Oracle database. As a common problem for oracle connectivity with a 32 bit BIDS is the program files (x86), I have mitigated this problem by using a batch file and that calls BIDS (PROGRA~2). I can created a new Oracle database connection manager using the "Microsoft OLE DB provider for Oracle" to connect to the Oracle database. We have installed a Oracle client (10.0.2) and set the appropriate connection string in the tnsname file. Whenever i test the connectivity in connection manager the system says test connection succeeded. However, when i run the package in debug mode the BIDS gives me the following error:

***************************************************************
SSIS package "tst.dtsx" starting.
Information: 0x4004300A at Transfer ABC table, SSIS.Pipeline: Validation phase is beginning.
Error: 0xC0202009 at tst, Connection manager "MY_ORACLE": SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for Oracle" Hresult: 0x80004005 Description: "ORA-06413: Connection not open.
".
Error: 0xC020801C at Transfer ABC table, OLE DB Source [51]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "IMT_WEBMETHODS" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
***************************************************************

Is this because my 32 bit DTEXEC is installed in the "Program Files (x86)" folder? I have looked through many posts but then i am not sure what should be the resolution for this. Should i uninstall the client tools on the server and reinstall it on a folder which does not have tany Parenthesis().

My final objective is to save the package on the msdb database and run it from the SQL Server Agent.

Regards,

Srikant
Post #1061009
Posted Wednesday, February 9, 2011 5:21 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, May 30, 2013 1:44 AM
Points: 45, Visits: 852
i have met the same problem. try below steps

* Uninstall oracle client
* restart and delete the existing oracle folder like("app")
and update the server patch then reinstall oracle client.

i want to know sql server is 64 bit or 32 bit version
Post #1061012
Posted Wednesday, February 9, 2011 7:54 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: 2 days ago @ 9:28 AM
Points: 44, Visits: 56
it is a 64 bit W2K8 machine with SQL2k8 installation.
Post #1061151
Posted Wednesday, February 9, 2011 9:51 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, May 30, 2013 1:44 AM
Points: 45, Visits: 852
can you tell me the registry setting for below entry and its values?

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI
Post #1061686
Posted Wednesday, February 9, 2011 10:05 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, December 7, 2012 2:52 AM
Points: 1, Visits: 23
As per my understanding you are using BIDS env for executing your package.
If it is the case then BIDS env 2008 can execute the packages whose Runtime env property set to 32 bit.
Because BIDS for sql 2008 is not compatible with 64 bit.
if you execute executable directly without using BIDS then it may be possible
Post #1061689
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse