You control when and how often a job repeats by setting the repeat_interval attribute of the job itself or of the named schedule that the job references. You can set repeat_interval with DBMS_SCHEDULER package procedures or with Enterprise Manager.
The question I had was what will be the next execution date of a job ? Will it be based on start time of one instance of job or completion time of one instance of job ?
According to Oracle Documentation http://download.oracle.com/docs/cd/B28359_01/server.111/b28310/scheduse004.htm#i1023312
The result of evaluating the repeat_interval is a set of timestamps.The Scheduler runs the job at each timestamp. Note that the start date from the job or schedule also helps determine the resulting set of timestamps. (See Oracle Database PL/SQL Packages and Types Reference for more information about repeat_interval evaluation.) If no value for repeat_interval is specified, the job runs only once at the specified start date.
Immediately after a job is started, the repeat_interval is evaluated to determine the next scheduled execution time of the job. It is possible that the next scheduled execution time arrives while the job is still running. A new instance of the job, however, will not be started until the current one completes.
This is something that I took sometime to figure out !
The question I had was what will be the next execution date of a job ? Will it be based on start time of one instance of job or completion time of one instance of job ?
According to Oracle Documentation http://download.oracle.com/docs/cd/B28359_01/server.111/b28310/scheduse004.htm#i1023312
The result of evaluating the repeat_interval is a set of timestamps.The Scheduler runs the job at each timestamp. Note that the start date from the job or schedule also helps determine the resulting set of timestamps. (See Oracle Database PL/SQL Packages and Types Reference for more information about repeat_interval evaluation.) If no value for repeat_interval is specified, the job runs only once at the specified start date.
Immediately after a job is started, the repeat_interval is evaluated to determine the next scheduled execution time of the job. It is possible that the next scheduled execution time arrives while the job is still running. A new instance of the job, however, will not be started until the current one completes.
This is something that I took sometime to figure out !
0 comments:
Post a Comment