Return
-
Title
Some jobs do not start when they are supposed to start -
Description
I have various jobs scheduled to run at different times within Toad (Jobs tab in Schema Browser). I've noticed that some of my jobs do not start exactly when they are supposed to start. For example, a job scheduled to run at 7:00am (trunc(sysdate+1) + 7/24) are kicking off at 7:20 or later. Do you know what might be causing this and/or how I could resolve it?
-
Resolution
When it comes to the jobs in the Jobs tab, Toad does not really have anything to do with running them. Basically, Toad gives you a GUI to assist in the managing of them and displays information about the jobs. The information it displays is queried from the sys.user_jobs view, using the following query.
Select job, what, log_user, priv_user, schema_user,
last_date, this_date, this_sec, next_date,
next_sec, total_time, broken, interval,
failures, nls_env
, instance
from sys.user_jobs
where schema_user = <schema_name>
and job = <job_name>The execution of the jobs is done on the database side and is controlled by the database. Contact your DBA or Oracle to help you troubleshoot this issue and find out why the jobs are not being executed at the correct time.