How about
dbms_job.submit(:jobno, 'statspack.snap',
sysdate+n/1440, 'sysdate
15/1440');
where n= a number of minutes to the nearest 15
minutes. So if it's 14:25
then it would
be sysdate+5/1440.
since you only need to do this one time, just make
sure that sysdate + n =
0, 15, 30 or 45
after the
Personally, I tend to just submit four jobs: one at the top of hour, one at
15 past, one at 30 past, and the fourth at 45 past. To alter the frequency,
just break or remove one or more of the jobs. Falls into the category of
not elegant, but it works...
- Original Message -
To:
Title: RE: dbms_job - running jobs every 15 minutes
I simplified it by using cron instead ... g
Raj
__
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't reflect
That's exactly what I do. Phew! I thought I was the only one ;)
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Wednesday, January 22, 2003 8:03 AM
Personally, I tend to just submit four jobs: one at the top of hour, one
at
15 past, one at 30
Title: RE: dbms_job - running jobs every 15 minutes
Cron?
How 1980's :-))
RF
Robert G. FreemanTechnical Management
ConsultantTUSC - The Oracle Experts www.tusc.com904.708.5076 Cell (it's
everywhere that I am!)Author of several books you can find on
Amazon.com!
-Original
Title: RE: dbms_job - running jobs every 15 minutes
Robert,
I have solid reasons not to trust dbms_job ... it didn't work reliably in
901x. Call me retro ... but "cron" rocks ...
8:)
Raj
__
Rajendra
Jamadagni
MIS, ESPN Inc.
Ra
;
/
Seems to me that the time specs could be simplified a bit.
Anyone care to give it a go? :)
Jared
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN
HTMLHEAD
META HTTP-EQUIV=Content-Type CONTENT=text/html; charset=iso-8859-1
TITLERE: dbms_job - running jobs every 15 minutes/TITLE
Title: RE: dbms_job - running jobs every 15 minutes
Cron? How RELIABLE !!
-Original Message-From: Freeman Robert - IL
[mailto:[EMAIL PROTECTED]]Sent: Wednesday, January 22, 2003 10:10
AMTo: Multiple recipients of list ORACLE-LSubject: RE:
dbms_job - running jobs every 15
Title: RE: dbms_job - running jobs every 15 minutes
LOL.
Ok, I
confess, my name's Robert and I'm a CRON user
Rf
Robert G. FreemanTechnical Management
ConsultantTUSC - The Oracle Experts www.tusc.com904.708.5076 Cell (it's
everywhere that I am!)Author of several books you can find
One thing I've learned Arup, there are 15,000 ways of doing the same thing,
and a good many of those are as good as the other. Cron, dbms_job, at,
whatever works for you!!
Rf
Robert G. Freeman
Technical Management Consultant
TUSC - The Oracle Experts www.tusc.com
904.708.5076 Cell (it's
Title: RE: dbms_job - running jobs every 15 minutes
LOL. You are right about the job_scheduler in early
9i.
Had
all sorts of problems when I first started moving stuff to
9.0.1
and 9.0.2 and Oracle was no help figuring out what the
problem was.
I use
cron all the time, but I love
[EMAIL PROTECTED] wrote:
One potential problem with DBMS_JOBS as is being discussed here is that Oracle
computes the next_date at the end of the job. They do that so that if a job
-- INTERVAL is a date function, evaluated immediately before the job starts
-- executing...
runs longer than
Vladimir,
I beg to disagree. The reason is that we used a number of jobs where the
interval was defined as sysdate+1 and the job routinely ran for ~30 minutes
every day. The result was that the job migrated over the course of a week by
3.5 hours so that instead of running at 6AM as
Yea... I realized that after I sent the email, so I submitted my second
suggestion...
Thanks though for your thoughts!!
Robert G. Freeman
Technical Management Consultant
TUSC - The Oracle Experts www.tusc.com
904.708.5076 Cell (It's everywhere that I am!)
Author of several books you can find on
]
Sent by: [EMAIL PROTECTED]
01/22/2003 06:54 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:Re: dbms_job - running jobs every 15 minutes
That's exactly what I do. Phew! I thought I was the only one
:RE: dbms_job - running jobs every 15 minutes
How about this... this will start the job at the top of the following hour
and then schedule it every 15 minutes...
dbms_job.submit(:jobno,
'statspack.snap;',to_date(to_char(sysdate+60/1440,'mm/dd/ hh24'),
'mm/dd/ hh24') ,'to_date(to_char
]
cc:
Subject:RE: RE: dbms_job - running jobs every 15 minutes
Yea... I realized that after I sent the email, so I submitted my second
suggestion...
Thanks though for your thoughts!!
Robert G. Freeman
Technical Management Consultant
TUSC - The Oracle Experts www.tusc.com
...
Jared
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
01/22/2003 08:34 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:Re:RE: dbms_job - running jobs every 15 minutes
One potential problem
[EMAIL PROTECTED]
cc:
Subject:RE: dbms_job - running jobs every 15 minutes
How about this... this will start the job at the top of the following hour
and then schedule it every 15 minutes...
dbms_job.submit(:jobno,
'statspack.snap;',to_date(to_char(sysdate+60/1440,'mm/dd
[EMAIL PROTECTED] wrote:
Now as discussed, if the job is scheduled to start at 9:00 AM and
runbs for 5 minutes it's next_date for run #2 will be 9:20, not 9:15,
and it
will creep 5 minutes every time.
No, as written, my jobs start on every quarter hour, regardless of
runtime.
e.g. 09:00,
Administrator
[EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 21, 2003 6:24 PM
To: Multiple recipients of list ORACLE-L
Subject: dbms_job - running jobs every 15 minutes
[EMAIL PROTECTED] [EMAIL PROTECTED]
cc:
Subject: Re:RE: dbms_job - running
jobs every
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 22, 2003 12:35 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: dbms_job - running jobs every 15 minutes
Thanks Robert, I like this.
Simplified and still easy to read.
Jared
Robert
If a job takes longer than the next scheduled time to execute then I see a
problem. Suppose a job runs every 15 mins but runtime is 30 mins, the
number ofjobs will increase andcompete for the same resources.
I always use cron (80's kinda of control), and the 1st thing I do is check if
the
: Wednesday, January 22, 2003 12:35 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: dbms_job - running jobs every 15 minutes
Thanks Robert, I like this.
Simplified and still easy to read.
Jared
Robert Freeman [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
01/21
1980's??? Yes, but it works, ain't broke, reliable, KISS, and is easy
to implement.
I use cron from my Linux box to connect to the production Oracle
database (OpenVMS) and do a RMAN backup with the catalog on a second
Oracle database (OpenVMS) server. Beats the heck out of trying to get
the
Stephane Faroult wrote:
Vladimir (whose formula I am still trying to understand :-))...
TRUNC(SYSDATE) + (CEIL(TO_CHAR(SYSDATE, 'S') / 60 / :interval) / (24
* 60 / :interval));
P.S.: could you please answer my question ('100% CPU utilization,
urgent') thread?
--
Vladimir Begun
The
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:Re: dbms_job - running jobs every 15 minutes
[EMAIL PROTECTED] wrote:
Now as discussed, if the job is scheduled to start at 9:00 AM and
runbs for 5 minutes it's next_date for run #2 will be 9
by: [EMAIL PROTECTED]
01/22/2003 11:39 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:Re:RE: dbms_job - running jobs every 15 minutes
Actually, Interval is evaluated at the beginning of the job
Feeling particularly anal the other day, I used the following
specification to
run statspack at the top of the hour, 15, 30 and 45 minutes after the
hour.
variable jobno number;
variable instno number;
begin
select instance_number into :instno from v$instance;
dbms_job.submit(
Jared
in general it's much more better to use bind variables, here
I do not use them, shame on me! :)
Hope the code below is ok for you at least it does not look
so complicated.
VARIABLE jobno NUMBER;
VARIABLE plsql VARCHAR2(1000);
EXEC :plsql := 'BEGIN statspack.snap; END;';
BEGIN
How about
dbms_job.submit(:jobno, 'statspack.snap', sysdate+n/1440, 'sysdate
15/1440');
where n= a number of minutes to the nearest 15 minutes. So if it's 14:25
then it would
be sysdate+5/1440.
since you only need to do this one time, just make sure that sysdate + n =
0, 15, 30 or 45
after the
How about this... this will start the job at the top of the following hour
and then schedule it every 15 minutes...
dbms_job.submit(:jobno,
'statspack.snap;',to_date(to_char(sysdate+60/1440,'mm/dd/ hh24'),
'mm/dd/ hh24') ,'to_date(to_char(sysdate+60/1440,''mm/dd/ hh24''),
''mm/dd/
33 matches
Mail list logo
