SSIS 2008 and Oracle database connectivity Issue in a 64 bit machine
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 clear on the resolution for this. Should i uninstall the SQL 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. Thanks, Srikant
February 9th, 2011 10:36am

Is your environment all 64 bit? It might be that you only need to set the 64 bit setting ( Run64BitRuntime ) to false in BIDS to run the package in 32 bit mode.Arthur My Blog
Free Windows Admin Tool Kit Click here and download it now
February 9th, 2011 10:58am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics