November 21, 2007 at 3:28 pm
I created a SSIS (SQL 2005 of course) and it executes successfully both in BIDS and manually. However when I create a SQL job to run the package it does not finish and I have to stop the job eventually. No errors whatsoever.
November 25, 2007 at 5:35 pm
Chris,
Where does it execute successfully in BIDS and manually? On the server or your workstation?
I've had this issue before, but I doubt it is the same. The package used an Oracle OLEDB connection manager. The package just would run and run and do nothing as a job. Turns out the PATH variable did not have the path to the Oracle bin directory. It could not find the Oracle OLEDB driver and the whole thing just hung up. No errors, no log file.
This may be very difficult to find. Luckily we had a clue when the DBA that installed the Oracle client mentioned that he could not run SQLPlus. That pointed use to try and create a UDL file and then to the Path variable.
Norman
DTS Package Search
November 26, 2007 at 7:18 am
Nite_Eagle,
I am running this from a Remote Desktop Connection to the server, my login has admin rights. When I say manually I mean I open up Integration Services on the server and execute the package manually on it. The package pulls info from SQL and sticks it in an Oracle DB. It works flawlessly execept when I call it from a job. This has also been a recently migrated package (coming from SQL 2000 going to SQL 2005).
The only time the job works is when I select "validate package withou executing".
Thanks for the help.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply