March 11, 2003 at 5:23 pm
Hi Everyone,
I seem to be having issues with running a DTS package on the scheduler. The run just keeps running after 500 hours+. I just noticed this today. I also noticed that for all packages I started getting runaway processes beginning on 11/20/02. I guess my question is why would this happen? has anyone ever encountered this? How do I begin to troubleshoot this?
Thanks
JMC
JMC
March 14, 2003 at 8:00 am
This was removed by the editor as SPAM
March 14, 2003 at 8:31 am
In addition I just created a test package pulling data from Oracle using Microsoft for Oracle driver. Ran the package without the scheduler and the package ran for 3 minutes. I then ran the package from the scheduler, it's still running after 2 hours. I checked all rights and everything is right. What is going on?
Thanks
JMC
JMC
March 14, 2003 at 9:49 am
Try saving the dts package with no schedulle, and then create an schedule job with the DTSRun cmdline utility. See if it works.
March 17, 2003 at 7:04 am
I found this out on Friday.
Test my package through the scheduler. I noticed something interesting. The job ran fine through the scheduler. However the scheduler keeps running even after the job is completed. Could I have a bug on the job scheduler? Has anyone encountered this before.
Thanks
JMC
JMC
March 18, 2003 at 12:31 pm
FYI. I fixed the issue. Since I'm using apartment threading which is not compatible with the Oracle driver. My job scheduler continues running. Fixed this issue by going into the workflow properties of the dts and setting the following properties:
Commit transaction on succesful completion of this step
Rollback transaction on failure
Execute on main package thread
Close connection on completion
Thanks
JMC
JMC
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply