Re: -- scheduled timer process if power is off?

"Romeo Olympia" <rolympia_at_hotmail.com> wrote in message
news:42fc55dc.0406150204.6570b4d0_at_posting.google.com...
> I assume you're referring to the dbms_job facility.>> If so, then for your case, your jobs will be submitted when your> database is turned on. dbms_job checks for all jobs that should have> run during the downtime and executes them after startup.>>> Take care that the job's next_date doesn't "slide" away from the 1st> day of the month at 17:00 hrs. Maybe a parameter of>> INTERVAL => 'ADD_MONTHS(TRUNC(SYSDATE, 'MM'), 1) + 17/24'>> Cheers.>> avanrossem_at_hotmail.com (Andre) wrote in message
news:<4d32d1be.0406142141.63cde585_at_posting.google.com>...
> > Hello all,> >> > I have a scheduled job which starts at 17:00 hours on the first day of> > the month. Now it is possible that on this day (if it's in the> > weekend) the server is not on. What is going to happen if the server> > is switched on one day later. Does the job run afters startup??> > Is the job ignored and will the job run on the first day of the next> > month?> >> > Thanks for all answers!> >> > Regards,> > Anneke> > The Netherlands

I note in Oracle 9.2.0.1 with JOB_QUEUE_PROCESSES > 1 that the order that
past due jobs are run is undefined. If jobs are scheduled for 15:00, 16:00
and 17:00 hours, and the server is stopped at 14:00 and restarted at 18:00,
the 3 jobs will be run, but not necessarily in chronological order. I've
not tested the behaviour with only one job queue process.

I mention this because I had a design which required strict serialization of
some jobs, and had to redesign it due this restart behaviour. I could find
no discussion of the issue in the Oracle docs, but in hindsight it make
sense to have maximum parallelization on startup. Still, if there is a way
to guarantee that the jobs are run chronologically on restart I would be
interested to know about it.