NEXT_RUN_DATE before current date

Question

Hello,
I'm wondering whether having an entry in the ALL_SCHEDULER_JOBS with the field NEXT_RUN_DATE filled with a date that's before the current date would trigger the launch of the job on Oracle instance startup?
The problem I'm having: I'm making backups of an Oracle instance. Some of my scheduled jobs would run daily. If I take a backup today, the backupset will include the ALL_SCHEDULER_JOBS. If I recover the backupset, say, a week from now, when I re-open my instance, the table will include some jobs that have the next running date at some moment in the past. What will happen at the startup of Oracle? Will it launch all the jobs that are scheduled and should have been ran in the past?
Thank you,
Adrian

Answer 1

hello,
I got a problem with my jobs too, I do daily a job that calls a program that runs a datapump export.
But if database was offline during the time the job should run, and database restarts, then jobs runs immediately after instance startup.
I thought there was some of other parameter you could use to let it run only on that fixed time?
Then I read something about the schedule_limit, but I think this does not work correctly on Oracle 10.2.0.3 (Windows platform)?
I've a job:
begin
dbms_scheduler.create_job (
job_name => 'DATAPUMP_RUN',
program_name => 'C_DATAPUMP',
start_date => '&date',
repeat_interval => 'FREQ=DAILY',
enabled => TRUE,
comments => 'Daily datapump');
end;
So, I fill in the date on which it has to start and run daily from that date/hour.
But sometilmes, database is offline, and the whole thing runs after database startup, not necessary and so not good for me.
then I did this:
begin
dbms_scheduler.set_attribute(
name => 'SYS.DATAPUMP_RUN',
attribute => 'schedule_limit',
value => numtodsinterval(5, 'minute'));
end;
(because value => 5 does not work?)
But when shutdowning my database before the job would run and start it back after 6 minutes, the job still gets activated and runs ...
what am I doing wrong?
Is it better to work with a window to avoid this?
thx
by the way, this was oracle's resolution about it:
Constraining Job Start Time
A really nice feature of the new scheduler is the ability to constrain a job's start time to a specific period following the nominal start time. For example, suppose you have a job scheduled to run every evening at 6:00 pm. Due to system load or other reasons, the job might not actually get the chance to start until 6:12 p.m. Do you still want the job to start, even though it's 12 minutes late?
With the scheduler, you can answer the question of how long past its time you're willing to let a job start. You do this by setting the job's schedule_limit attribute value (in minutes). The following specifies that my LOADNEWCUSTOMERS job must begin within 10 minutes of its scheduled start time:
sys.dbms_scheduler.set_attribute(
name =>'GENNICK.LOADNEWCUSTOMERS',
attribute => 'schedule_limit',
value => 10);
If ever this job is delayed for more than 10 minutes past its start time, that run of the job will be skipped. The default schedule_limit attribute is null, which imposes no limit. When using Database Control, you can set this attribute from the Options tab of the Edit Job page.