SQL Agent skipping job runs?
-
Hello all,
I've got a weird one. It appears that I have had the SQL Agent just skip running a scheduled job task. No failure no job stuck executing just flat skipped it.
I did ask the mighty google but didn't see anything that resembled the problem.
Has anyone else had an issue with SQL 2005 skipping jobs like this?
Thanks,
Wes
-
I've had this once and not figured out why.
Things you might want to check: Job enabled? Job schedule enabled? Job schedule starting time and ending time; windows time service, task scheduler service..
-
Yeah,
I walked through all of it and so did someone else just to make sure I didn't miss something.
I hate writing a monitor for all the jobs on all the servers because they may not execute period.
-
Wesley Brown (1/5/2009)
Hello all,I've got a weird one. It appears that I have had the SQL Agent just skip running a scheduled job task. No failure no job stuck executing just flat skipped it.
I did ask the mighty google but didn't see anything that resembled the problem.
Has anyone else had an issue with SQL 2005 skipping jobs like this?
Thanks,
Wes
Please check SQL job owner has a access on that step code or not?
-
Did you find out what the problem was?
-
No not yet.
This job has run successfully except for the one day it skipped. It ran successfully today at its normal time. We can't find any reason for it to have skipped a run, the previous run was successful and in its normal run time.
-
I think your sql agent cache is not in sync with msdb database. You can check this by running
xp_sqlagent_notify 'D', null, Null, null, null.
This will dump what is there in the sql memory for jobs. if your job is not listed then it will not run. Propably in that case you need to restart the sql agent.
After running the above query please look into agent error log it would have dumped what is there in sql server agent cache.
-
any chance sql agent just wasn't running at the time?
---------------------------------------------------------------------
-
The job hasn't be modified since it was installed.
SQL Agent was running the whole time. We get alerts immediately if the agent is down from our nagios box.
We have had problems on other boxes where the job would hang on sending notification but nothing like this.
Cheers,
Wes
-
If you right-click on the job in SSMS, and hit view history, does it come back with anything at all?
The Redneck DBA
-
There is plenty of job history plus I archive all job history off to another server.
-
If it's showing up in the history, then it sounds like it's running.
Perhaps it's immediatly failing, or starting then immediatly stopping?
If you drill down into the details of one of the history rows, you can perhaps get a little information.
I've found you get a lot more information about failures (or just general troubleshooting information) if you specify an output file in the advanced page in the job step properties window.
Might try that and see if you get any useful information about what its doing.
The Redneck DBA
-
The job didn't fail it simply didn't execute at all. There is no entry for the time it was suppose to execute in the job history at all.
-
What other jobs are running on that server? I had a similar problem a while back and found that another job, scheduled to start 5 minutes before mine, ran long causing the agent to 'skip' my job. I know servers are supposed to be able to multitask, but just for grins and giggles I rescheduled my job for 5 minutes before the other job's scheduled start time. That seemed to work like a charm - never had another 'skip'!
-
This server has about 50 jobs on it some run as frequently as every 10 minutes.
Viewing 15 posts - 1 through 15 (of 19 total)
You must be logged in to reply to this topic. Login to reply