Re: DB jobs wont run for longer periods

nicklas.lundgren_at_triacon.se writes:

> The interval is 1 minute and is set correct. The job runs fine for a
> couple of days and then all of a sudden it just stops to be executed.
> There is nothing in the log for this job that shows anything wrong.
>

In the past I have seen the job scheduler stop executing jobs for the following reasons

1. The database was attempted to be shutdown for a cold backup but timed out after 60 minutes due to some kind of client activity leaving the database up but the job scheduler down requiring the database to be bounced with a shutdown abort. (setting the job processes parameter to 0 and then to 10 did not restart the job scheduler processes)
2. The particular job was still executing in a hung state. This was evident by the job not being further executed and listing the currently running jobs showed the jobs in question. Attempting to kill the associated sessions didn't work and bouncing the database cleared everything up.

--
Dave Newman