William,
Agreed about the timing getting funky, but I didn't see that OP was concerned
with when they were running, as long as each database wasn't running two
instances at once, and that it did not run within 30 minutes of the prior job's
completion.
If there needs to be coordination between the databases, meaning no two jobs
across database can run at the same time, or no job can start in any database
within 30 minutes of the completion of a job on any given database, then that
is a different story.
If OP was concerned about start time, he could always just start it either on
the hour, or 30 minutes past the hour, based on the completion time of the job,
and that way he'd have some rough idea of when it's starting.
Thanks,
Scott
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On ;
Behalf Of William Blanchard
Sent: Wednesday, October 26, 2016 8:30 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: Scheduler
While a good solution that would cover the OP problem, it could be a
maintenance nightmare. If you've got multiple servers running this script,
they would all be running at different times and you wouldn't be sure if/when
the last run was for a particular server without actually looking.
Just my $0.02.
William
On 10/25/2016 08:41 PM, Deas, Scott wrote:
Couldn't you just create a non-repeating job, and then at the end of your
process, just schedule it for 30 minutes from now? That way you'd have just
one job - no deleting/recreating necessary.
Scott
On Oct 25, 2016, at 21:39, Jack van Zanen
<jack@xxxxxxxxxxxx<mailto:jack@xxxxxxxxxxxx>> wrote:
not sure if it is possible but create a seperate job that deletes the current
job and schedules a new copy of the job 30 minutes from now and call this job
at the end of your job
Jack van Zanen
-------------------------
This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient. If you are not the intended recipient, please be
aware that any disclosure, copying, distribution or use of this e-mail or any
attachment is prohibited. If you have received this e-mail in error, please
contact the sender and delete all copies.
Thank you for your cooperation
On Wed, Oct 26, 2016 at 12:04 PM, Andrew Kerber
<andrew.kerber@xxxxxxxxx<mailto:andrew.kerber@xxxxxxxxx>> wrote:
The easiest would be to embed the logic in an sp and call the sp every 30
minutes or so. if the 30 minute interval is crucial, embed the code to
schedule the next run within the sp.
Sent from my iPhone
On Oct 25, 2016, at 5:07 PM, Lange, Kevin G
<kevin.lange@xxxxxxxxx<mailto:kevin.lange@xxxxxxxxx>> wrote:
Database: Oracle 12.1.0.2
OS: Linux
I have a condition on multiple databases where a job runs for different lengths
of time depending on the size of the particular database. What I need is to
be able to schedule a job to run multiple times during the day but ONLY if two
conditions are met:
1. IF it has not ran in the last 30 minutes.
2. IF it is not currently running.
So basically, I need to be able to code the Oracle Scheduler correctly with a
varying start time on the job that looks to see if its not running now and if
there is at least 30 minutes since it last ran.
Anyone have any GOOD Oracle Scheduler resources that can help me set up those
kind of dependencies without having to rely on any kind of flag or storage
history ? (Just a link to a location that I can study up on would be fine).
I do have ways to do this, but I was hoping for a nice elegant solution using
just the scheduler itself.
Thanks in advance
Kevin Lange
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
Notice of Confidentiality: **This E-mail and any of its attachments may contain
Lincoln National Corporation proprietary information, which is privileged,
confidential,
or subject to copyright belonging to the Lincoln National Corporation family of
companies. This E-mail is intended solely for the use of the individual or
entity to
which it is addressed. If you are not the intended recipient of this E-mail,
you are
hereby notified that any dissemination, distribution, copying, or action taken
in
relation to the contents of and attachments to this E-mail is strictly
prohibited
and may be unlawful. If you have received this E-mail in error, please notify
the
sender immediately and permanently delete the original and any copy of this
E-mail
and any printout. Thank You.**
Notice of Confidentiality: **This E-mail and any of its attachments may contain
Lincoln National Corporation proprietary information, which is privileged,
confidential,
or subject to copyright belonging to the Lincoln National Corporation family of
companies. This E-mail is intended solely for the use of the individual or
entity to
which it is addressed. If you are not the intended recipient of this E-mail,
you are
hereby notified that any dissemination, distribution, copying, or action taken
in
relation to the contents of and attachments to this E-mail is strictly
prohibited
and may be unlawful. If you have received this E-mail in error, please notify
the
sender immediately and permanently delete the original and any copy of this
E-mail
and any printout. Thank You.**
