Re: Job scheduling problem

From: Andy Hardy <Andrew.Hardy_at_BGTechnology.com>
Date: Tue, 3 Oct 2000 08:47:59 +0100
Message-ID: <8rc2tb$k8k$1@sun-cc204.lboro.ac.uk>

Wil,

You need to have another look at the way that you have defined the 'NEXT' parameter. Instead of just having a 'SYSDATE + 1' style of entry, try and define the next to include the time e.g. 'TRUNC(SYSDATE + 1) + 4/24' which would set the next time to tomorrow at 4am.

Andy

--
Opinions are mine and may not reflect those of BG Technology Ltd

W.F. Weterings <weterings_at_schiphol.nl> wrote in message
news:39D97F0D.8B17D81B_at_schiphol.nl...


> Hello, I have a problem with a job that has to run every day at the same

> time.

>

> The problem occurs when the job is stared later then scheduled because

> the database was down during the scheduled time then oracle immediately

> start the job and because of the sysdate+1 in the interval field the

> next run date shifts from the intended time to the current time.

>

> I made procedure that fixes this but the problem is that if you set the

> job scheduled time from within a running job whit this procedure then

> oracle set the next_date and next_sec fields when then job finishes and

> so canceling out the correction.

>

> Is there a workaround for this. I prefer not to use special grants to

> the user. I thought of using a second job that set the first job.

>

> A help much appreciated.

>

> Please respond to E-mail

>

> Weterings_at_schiphol.nl

>

> Regards,

> Wil.

Received on Tue Oct 03 2000 - 02:47:59 CDT