February 1, 2013 at 11:05 am
Hi All,
I have an SSIS package that connects to an Oracle source using the OLEDB Source connector. I'm attempting to extract a large table by using multiple dataflows to query the Oracle data by partition and export it to a flat file destination. When I run the package via the command line using DTEXEC it runs fine. When I try to execute it from a Windows Service it hangs. The Windows service starts a process and issues the DTEXEC command. When I run DTEXEC via the command line I log on as the same user that is running the windows service. I turned logging on and found that its hanging in the pre-execute phase.
Any thoughts as to why it's hanging when called from the service but it works when executed via a command line?
I'm using SQL Server 2008R2
Thanks
February 5, 2013 at 7:16 am
It could be any number of things but based on what you have stated it sounds like a good place to start would be with the Oracle driver and possibly the bitness of the environment.
Is the server 64-bit? Is your workstation? Is the service running under 32-bit or 64-bit? Are the Oracle drivers installed and configured on the server for the bitness the job is running as?
I know you said this is running via a Windows Service but the principles for running packages under SQL Agent are much the same. Here's a good resource with some usual suspects that you can draw from by ignoring the SQL Agent-specific verbage:
Troubleshooting: SSIS Package Execution Using SQL Server Agent (SQL Server Video)
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply