ultegra
19th March 2008, 09:38
Hi experts! I have a problem in job data(ttaad5500m000). I created a job to dump the sequential file every night. However, after a job is done, the status will not release. It just stays as Running. When this happen, I have to manually cancel the job and release it.

Is there a way or script to free the status everytime the job is finished? Many thanks!

David Eagar
19th March 2008, 20:02
Also interested in this problem. Have similar experiences with a number of jobs, some quite long, while others are very quick ones. My problems are intermittent, but seem to only occur on the same jobs.

Only similarity I have with ultegra is SQL2005 and Windows 2003

sukesh75
20th March 2008, 11:09
David,
Do all the jobs share the same settings? I am referring to the jobs that work and close properly and the ones that keep showing status as "Running" even after executing.

sk

David Eagar
20th March 2008, 14:43
David,
Do all the jobs share the same settings? I am referring to the jobs that work and close properly and the ones that keep showing status as "Running" even after executing.

sk

How do you mean "same settings"? The same job can run successfully many times & then go into limbo every so often.

sukesh75
20th March 2008, 15:11
Sorry about that David. Thought you had some jobs working well and others just stalling after execution. Have you tried monitoring it by running a harmless session inside a job over and over to see if it fails to close properly in any of the runs?

sk

David Eagar
20th March 2008, 15:22
No, haven't done too much troubleshooting as yet. Trying to figure out what could be going on to hone in on where to to troubleshoot.

This problem only started occuring with SQL2005 / Windows 2003 mix

ultegra
21st March 2008, 09:28
I only have one job running at the moment.

David Eagar
21st March 2008, 11:01
I only have one job running at the moment.

and running and running and running.........