Dear Gurus,
I have dbms_job in replication environment to push deffered transactions from site A
to B and B to A.
The job which is running at site A is working fine but job which is running at site
B is not pushing the transactions automatically. But if I do it manually (either
dbms_job.run
-L
[EMAIL PROTECTED]
Sent: Fri, 14 Nov 2003 05:29:30
Dear Gurus,
I have dbms_job in replication environment to push
deffered transactions from site A to B and B
to A.
The job which is running at site A is working
fine but job which is running at site B is not
pushing the transactions
(never
remember where it goes).
HTH
SF
- --- Original Message --- -
From: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L
[EMAIL PROTECTED]
Sent: Fri, 14 Nov 2003 05:29:30
Dear Gurus,
I have dbms_job in replication environment to push
deffered transactions
im trying to submit a job that runs every 5 minuts. Only way I can get the submit to
work is as follows...
variable jobno number;
variable instno number;
begin
select instance_number into :instno from v$instance;
dbms_job.submit(:jobno, 'statspack.snap;', trunc(sysdate+1/24,'HH'),
id prefer to handle this in the database.
From: Gene Sais [EMAIL PROTECTED]
Date: 2003/10/23 Thu AM 10:29:33 EDT
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: stupid dbms_job question
It's called cron :). Or you could run a shell script that executes
I had an issue with dmbs_job where the jobs would become broken if I altered them.
Have you checked if the job becomes broken after you change the interval?
Gudmundur
im trying to submit a job that runs every 5 minuts. Only way I can get the
submit to work is as follows...
variable jobno
Just a shot in the dark
Have you set initialization parameters in the init file?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 23, 2003 6:14 PM
To: Multiple recipients of list ORACLE-L
Subject: Re: Re: stupid dbms_job question
id
An interval of
trunc(sysdate)+(trunc(to_char(sysdate,'s')/900)+1)*5/24/60
ought to give you every 5 minutes. Courtesy of Tom...
On Thu, 2003-10-23 at 10:29, Gene Sais wrote:
It's called cron :). Or you could run a shell script that executes
then sleeps for 5 mins.
[EMAIL PROTECTED]
what initialization parameters? job_queue_processes is fine.
From: Gints Plivna [EMAIL PROTECTED]
Date: 2003/10/23 Thu AM 11:49:32 EDT
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: RE: Re: stupid dbms_job question
Just a shot in the dark
Have you set
Ryan,
remove the trunc() from sysdate+1/96 trunc is removing your time part. or you
should be using ROUND(SYSDATE+1/96,'MI') instead.
Raj
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in
What is JOB_QUEUE_INTERVAL set to? If it's more than 5 minutes then what your seeing
is what you get.
Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA
-Original Message-
Sent: Thursday, October 23, 2003 10:09 AM
To: Multiple recipients of list ORACLE-L
im trying to submit a job
JOB_QUEUE_INTERVAL I think
But I found that it is obsolete in Release 9.0.1
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 23, 2003 7:15 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Re: stupid dbms_job question
what
: Gene Sais [EMAIL PROTECTED]
Date: 2003/10/23 Thu AM 10:29:33 EDT
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: stupid dbms_job question
It's called cron :). Or you could run a shell script that executes then
sleeps for 5 mins.
[EMAIL PROTECTED] 10/23/03 10:09AM
to handle this in the database.
From: Gene Sais [EMAIL PROTECTED]
Date: 2003/10/23 Thu AM 10:29:33 EDT
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: stupid dbms_job question
It's called cron :). Or you could run a shell script that executes then
sleeps for 5 mins
ORACLE-L [EMAIL PROTECTED]
Subject: Re: stupid dbms_job question
It's called cron :). Or you could run a shell script that executes then
sleeps for 5 mins.
[EMAIL PROTECTED] 10/23/03 10:09AM
im trying to submit a job that runs every 5 minuts. Only way I can get
the submit to work
that it is obsolete in Release 9.0.1
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 23, 2003 7:15 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Re: stupid dbms_job question
what initialization parameters? job_queue_processes is fine.
From
OK, I know I must be doing something wrong, would somebody please point
out what it is? I would like to set up a job to sync an intermedia text
index. Here is my job:
SQL select what from all_jobs where job = 2;
WHAT
-
bill
this is a bug..infact it was happening in 8i and oracle said they will try to fix in 9i.
u have to call the procedure in the ur job and embed the sync index in ur procedure.
here is a snippet.u can try this way.
create or replace procedure i_doc_sync
is
begin
ctx_ddl.sync_index(
he has, hasn't he? -- Nora
Joyce
-Original Message-From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sai
SelvaganesanSent: Wednesday, October 08, 2003 3:19 PMTo:
Multiple recipients of list ORACLE-LSubject: Re: intermedia text
and dbms_job problem
bill
:30 PM
To: Multiple recipients of list
ORACLE-L
Subject: dbms_job issue.
Hello
List, I am running into weird dbms_job issue. I have a dbms_job to collect
perfstat every 1 hour , job was running fine for last 8-9 months without any
issue. For last 3 days job is stopping every night around 2 AM. I
Hello
List, I am running into weird dbms_job issue. I have a dbms_job to collect
perfstat every 1 hour , job was running fine for last 8-9 months without any
issue. For last 3 days job is stopping every night around 2 AM. I amnot
seeing any trace file, any logs in alert file. Any idea what
Re-submit the jobthat should work
It has a long theory!!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, September 18, 2003
11:00 PM
To: Multiple recipients of list
ORACLE-L
Subject: dbms_job issue.
Hello
recipients of list
ORACLE-L
Subject: dbms_job issue.
Hello List, I am running
into weird dbms_job issue. I have a dbms_job to collect perfstat every 1 hour ,
job was running fine for last 8-9 months without any issue. For last 3 days job
is stopping every night around 2 AM. I amnot seeing any
Already tried to resubmit it twice, everytime its breaking around mid
night.
-Original Message-From: Venu Gopal
[mailto:[EMAIL PROTECTED]Sent: Thursday, September 18, 2003
10:40 AMTo: Multiple recipients of list ORACLE-LSubject:
RE: dbms_job issue.
Re-submit
it to 'really high' number. I
don't remember the bug# right now ...
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]Sent: Thursday, September 18,
2003 2:00 PMTo: Multiple recipients of list
ORACLE-LSubject: RE: dbms_job issue.
Already tried to resubmit
Resubmit it and it runs fine until mid night. So I really dont have any
stats for this week.
-Original Message-From: Igor Neyman
[mailto:[EMAIL PROTECTED]Sent: Thursday, September 18, 2003
10:45 AMTo: Multiple recipients of list ORACLE-LSubject:
RE: dbms_job issue
[EMAIL PROTECTED] wrote:
Hello List, I am running into weird dbms_job issue. I have a dbms_job
to collect perfstat every 1 hour , job was running fine for last 8-9
months without any issue. For last 3 days job is stopping every night
around 2 AM. I am not seeing any trace file, any logs
Hello list,
I am running 9.2.0.1.0 enterprise edition on win32.
Why doesn't the Supplied PLSQL Packages and Types Reference docs mention
dbms_system ?
It doesn't seem to be explained anywhere in the docs although the admin
docs say that it can be used enable sql_trace for another session.
I was
]
[mailto:[EMAIL PROTECTED]
Sent: Friday, July 25, 2003 1:20 PM
To: Multiple recipients of list ORACLE-L
Subject: dbms_job
Hello list,
I am running 9.2.0.1.0 enterprise edition on win32.
Why doesn't the Supplied PLSQL Packages and Types Reference
docs mention
dbms_system ?
It doesn't seem
Hi
The package dbms_system is now private, the body and header are both
created in $ORACLE_HOME/rdbms/admin/prvtutil.plb. The sql file
$ORACLE_HOME/rdbms/admin/dbmsutil.sql has the following in it now:
Rem dbms_system - database system level commands
Title: RE: dbms_job
www.orafaq.com/papers/dbms_sys.doc
Raj
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
QOTD: Any clod can have facts, having an opinion
Thanks pete
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Saturday, July 26, 2003 02:44
Hi
The package dbms_system is now private, the body and header are both
created in $ORACLE_HOME/rdbms/admin/prvtutil.plb. The sql file
Subject: dbms_job
Hello list,
I am running 9.2.0.1.0 enterprise edition on win32.
Why doesn't the Supplied PLSQL Packages and Types Reference
docs mention
dbms_system ?
It doesn't seem to be explained anywhere in the docs although
the admin
docs say that it can be used enable
Package can be obtained from
http://oracledba.pwp.blueyonder.co.uk/cron.html
Use at your own risk.
Garry Gillies
CONFIDENTIAL:
The information contained in this email (including any attachments)
is confidential, subject to copyright and for the use of the
intended recipient only. If you are
Any Interest?
The DBMS_JOB package is supplied by Oracle to allow the running of
procedures at regular
intervals. Unfortunately the INTERVAL parameter is limited to 128
characters, which prevents
you from getting very complex (user defined functions [in the interval
parameter] do not
work well
Title: RE: DBMS_JOB scheduling
Garry,
1. have you tried select to_char(sysdate,'D') from dual ??
This is really nice, but my only gripe with dbms-job is that is isn't reliable ... it wasn't in 9ir1 on aix and we didn't even look at it in 9ir2. in 9ir1 dbms_job used to _forget_ to run jobs
Title: RE: DBMS_JOB scheduling
Raj,
You must be speaking from UNIX
heights -J
Under Windows I find dbms_job much more
reliable than windows at scheduling.
Actually, never had problems with dbms_job
forgetting to run a job.
Igor Neyman, OCP DBA
[EMAIL PROTECTED
reliable ... it wasn't in 9ir1 on aix and we didn't even look at it in
9ir2. in 9ir1 dbms_job used to _forget_ to run jobs after some time and
the workaround was like setting job_processes to a very large number.
I am sorry to hear that. We are on 8.1.7 and have been using since 7.3
with no major
Title: RE: DBMS_JOB scheduling
Igor,
you are right ... as a unwritten policy we don't allow windows databases
... even for crash test dummies ...
Raj
Rajendra dot Jamadagni at nospamespn dot
com All Views
Title: RE: DBMS_JOB scheduling
nope ... at-least not yet.
Raj
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
QOTD: Any clod can have facts, having
of help with the syntax to submit a dbms_stats run via
dbms_jobs
The following syntax works fine to run the procedure interactively
execute
dbms_stats.gather_schema_stats(ownname='RPT_3G_MASTER',estimate_percent
=10,cascade=true);
but trying to get that into an dbms_job is destroying my brain.The
the procedure interactively
execute
dbms_stats.gather_schema_stats(ownname='RPT_3G_MASTER',estimate_percent
=10,cascade=true);
but trying to get that into an dbms_job is destroying my brain.The
syntax I am trying is based around this script
declare
l_job number;
begin
dbms_job.submit
(l_job
via
dbms_jobs
The following syntax works fine to run the procedure interactively
execute
dbms_stats.gather_schema_stats(ownname='RPT_3G_MASTER',estimate_percent
=10,cascade=true);
but trying to get that into an dbms_job is destroying my brain.The
syntax I am trying is based around this script
to submit a dbms_stats run via
dbms_jobs
The following syntax works fine to run the procedure interactively
execute
dbms_stats.gather_schema_stats(ownname='RPT_3G_MASTER',estimate_percent
=10,cascade=true);
but trying to get that into an dbms_job is destroying my brain.The
syntax I am trying is based
interactively
execute
dbms_stats.gather_schema_stats(ownname='RPT_3G_MASTER',estimate_percent
=10,cascade=true);
but trying to get that into an dbms_job is destroying my brain.The
syntax I am trying is based around this script
declare
l_job number;
begin
dbms_job.submit
(l_job
that into an dbms_job is destroying my brain.The syntax I am trying
is based around this script
declare
l_job number;
begin
dbms_job.submit
(l_job,'dbms_stats.gather_schema_stats(''RPT_2G_MASTER'',10,FALSE,''CASCADE=TRUE'');',
trunc(sysdate+1)+01/24,'sysdate+7');
end;
/
The problem area is the cascade keyword. I
Title: RE: dbms_stats via dbms_job - syntax question
you don't need quotes around cascade=true ...
Raj
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
QOTD
dbms_stats.gather_schema_stats(ownname='RPT_3G_MASTER',estimate_percent=10
,cascade=true);
but trying to get that into an dbms_job is destroying my brain.The syntax I
am trying is based around this script
declare
l_job number;
begin
dbms_job.submit
(l_job,'dbms_stats.gather_schema_stats
',estimate_percent
=10,cascade=true);
but trying to get that into an dbms_job is destroying my brain.The
syntax I am trying is based around this script
declare
l_job number;
begin
dbms_job.submit
(l_job,'dbms_stats.gather_schema_stats(''RPT_2G_MASTER'',10,FALSE,''CASC
ADE=TRUE'');',
trunc(sysdate
='RPT_3G_MASTER',estimate_percent=10,cascade=true);
but trying to get that into an dbms_job is destroying my brain.The syntax
I am trying is based around this script
declare
l_job number;
begin
dbms_job.submit
(l_job,'dbms_stats.gather_schema_stats(''RPT_2G_MASTER'',10,FALSE,''CASCADE=TRUE
to submit statspack.snap at 10:00am and 14:00pm through dbms_job, it's friday afternoon and my head is hurting me from a heavy night and the manuals are as clear as mud.
Thanks
Yahoo! Plus - For a better Internet experienceMurali Vallath
"We must be the change we wish to see in the world.&quo
Quick question, I want to submit statspack.snap at 10:00am and 14:00pm through dbms_job, it's friday afternoon and my head is hurting me from a heavy night and the manuals are as clear as mud.
ThanksYahoo! Plus - For a better Internet experience
Title: Re: submitting statspack.snap through dbms_job
var jnr number
exec dbms_job.submit(job=:jnr, what='statspack.snap(5);',
next_date=trunc(sysdate)+10/24, interval='trunc(sysdate)+10/24');
exec dbms_job.submit(job=:jnr, what='statspack.snap(5);',
next_date=trunc(sysdate)+14/24
/86400');
Mike
Kader Ben wrote:
Hi Listers,
I'm simulating the date in future with fixed_date.
I wrote procedure to be called every seconde through
dbms_job to increment the fixed_date.
I did that dbms_job.submit(:job_num, 'myprocedure;',
sysdate, 'sysdate');
the dba_jobs table show me
(:job_num, 'myprocedure;',sysdate,
'sysdate+1/86400');
Mike
Kader Ben wrote:
Hi Listers,
I'm simulating the date in future with
fixed_date.
I wrote procedure to be called every seconde
through
dbms_job to increment the fixed_date.
I did that dbms_job.submit(:job_num,
'myprocedure
-
From: Kader Ben [mailto:[EMAIL PROTECTED]
I'm simulating the date in future with
fixed_date.
I wrote procedure to be called every seconde
through
dbms_job to increment the fixed_date.
I did that dbms_job.submit(:job_num,
'myprocedure;',
sysdate, 'sysdate
-
From: Kader Ben [mailto:[EMAIL PROTECTED]
I'm simulating the date in future with
fixed_date.
I wrote procedure to be called every seconde
through
dbms_job to increment the fixed_date.
I did that dbms_job.submit(:job_num,
'myprocedure;',
sysdate, 'sysdate');
the dba_jobs table
You can't call a job every second via DBMS_JOB.
I believe that at best the resolution is 1 minute.
You could just open another session and run
something like this:
declare
fd varchar2(50) := '01/01/2010 00:00:00';
v_sql varchar2(200);
begin
loop
v_sql := 'alter system set
Many thanks Jared,
Definitely I think this is only one away to resolve
my problem.
Have nice week end,
Ben
--- [EMAIL PROTECTED] wrote:
You can't call a job every second via DBMS_JOB.
I believe that at best the resolution is 1 minute.
You could just open another session and run
the date in future with
fixed_date.
I wrote procedure to be called every seconde
through
dbms_job to increment the fixed_date.
I did that dbms_job.submit(:job_num,
'myprocedure;',
sysdate, 'sysdate');
the dba_jobs table show me the right interval un
next_date
?
-Original Message-
From: Kader Ben [mailto:[EMAIL PROTECTED]
I'm simulating the date in future with
fixed_date.
I wrote procedure to be called every seconde
through
dbms_job to increment the fixed_date.
I did that dbms_job.submit(:job_num,
'myprocedure
Hi Listers,
I'm simulating the date in future with fixed_date.
I wrote procedure to be called every seconde through
dbms_job to increment the fixed_date.
I did that dbms_job.submit(:job_num, 'myprocedure;',
sysdate, 'sysdate');
the dba_jobs table show me the right interval un
next_date
Title: RE: Fixed_date and dbms_job
After calling dbms_job.submit, did you issue a commit?
-Original Message-
From: Kader Ben [mailto:[EMAIL PROTECTED]]
I'm simulating the date in future with fixed_date.
I wrote procedure to be called every seconde through
dbms_job
Hi,
I have a procedure that submits a dbms_job for immediate processing for onetime.I want
to know if the procedure that submits the job will have to wait till the job gets
executed to execute the next piece of code after the dbms_job.submit() in the
procedure or will the procedure submit
It will submit the job and continue. Even nicer is
that if you subsequently do a rollback later, then the
job will be roll'd back as well. In this way, you
could put dbms_job into (say) a trigger and if the
statement later roll's back you don't end up with a
mess
hth
connor
--- Basavaraja
; next_date .
My question is this: Are the recursive cpu/call stats that are accumulating a result
of the procedures scheduled within DBMS_JOB (there are a handful of these procedures),
or is this likely due to DBMS_JOB (and whatever logic it uses to keep itself doing
what it should) itself
: Wednesday, February 19, 2003 8:25 PM
To: [EMAIL PROTECTED]; CHAN Chor Ling Catherine (CSC)
Subject:RE: DBMS_JOB : Can submit but does not execute
Make sure job_queue_processes 0. Also check job_queue_interval.
Jay Hostetter
Title: RE: DBMS_JOB : Can submit but does not execute
In 8i I have had bad luck of submitting it at sysdate and they don't fire ...
Once I got burned, I can afford 5 seconds ... if it is that critical, dbms_job isn't the tool for that job anymore.
Raj
Title: RE: DBMS_JOB : Can submit but does not execute
Maybe
this is stating the obvious, but make sure you do a COMMIT after submitting the
job. - Dave
-Original Message-From: Jamadagni, Rajendra
[mailto:[EMAIL PROTECTED]]Sent: Thursday, February 20,
2003 6:59 AMTo: Multiple
You have to give commit after submit the job.
-Original Message-
Ling Catherine (CSC)
Sent: Tuesday, February 18, 2003 8:14 PM
To: Multiple recipients of list ORACLE-L
Hi Gurus,
I have submitted a job but it does not execute. Why? Does the owner
require any privileges ? However, I can
Have you set the job_queue_processes parameter in you init.ora file?
CHAN Chor Ling Catherine (CSC) wrote:
Hi Gurus,
I have submitted a job but it does not execute. Why? Does the owner require any privileges ? However, I can use DBMS_JOB.CHANGE command to execute immediately. I would like the
You have to run the job after you submit it.
SQL exec dbms_job.run(24);
Also make sure all init.ora parameters are set eg (job_queue_interval ,
job_queue_processes )
HTH,
Rajesh
-Original Message-
Ling Catherine (CSC)
Sent: Tuesday, February 18, 2003 8:14 PM
To: Multiple recipients of
advice ? TIA
Regds,
Catherine
-Original Message-
From: CHAN Chor Ling Catherine (CSC)
Sent: Wednesday, February 19, 2003 9:15 AM
To: '[EMAIL PROTECTED]'
Subject:DBMS_JOB : Can submit but does
Title: RE: DBMS_JOB : Can submit but does not execute
Also as a practice, I always submit sysdate + 5 seconds instead of sysdate.
Raj
-
Rajendra dot Jamadagni at espn dot com
Any views expressed here are strictly personal.
QOTD
That shouldn't matter. Look at DBA_JOBS when you startup an instance after
it's been down for a while (not that it would ever happen!). All pending
jobs (nextdate = SYSDATE) should be firing, at least as many
job_queue_processes as you have in the init.ora.
Rich
Rich Jesse
Hi All,
Does anybody know a way of to get DBMS_JOB to run a job every 15 minutes,
unless the time of day is between X and Y (for example 00:00am 03:00am)?
All help appreciated! Pointers to RTFM more than welcome! ;)
Mark
===
Mark Leith
The PL/SQL packages that we have running as jobs resubmit themselves when the job is
complete. So we can just add logic before calling DBMS_JOB.SUBMIT. Can your PL/SQL
be modified in this way?
Jay
[EMAIL PROTECTED] 02/18/03 09:14AM
Hi All,
Does anybody know a way of to get DBMS_JOB to run
use a function:
check if 15 minutes after current time is in the don't run interval
if it is return the first time after the interval
if not return 15 minutes later
Pat
Hi All,
Does anybody know a way of to get DBMS_JOB to run a job every 15 minutes,
unless
://asktom.oracle.com.
I think there are a few examples that you will find come close to what you
are looking for.
- Kirti
-Original Message-
Sent: Tuesday, February 18, 2003 8:14 AM
To: Multiple recipients of list ORACLE-L
Hi All,
Does anybody know a way of to get DBMS_JOB to run a job
know a way of to get DBMS_JOB to run a job every 15 minutes,
unless the time of day is between X and Y (for example 00:00am 03:00am)?
All help appreciated! Pointers to RTFM more than welcome! ;)
Mark
===
Mark Leith | T: +44 (0)1905 330
Just found an online version (in the spirit of sharing solutions ;D):
http://otn.oracle.com/oramag/oracle/03-jan/o13asktom.html
---snip---
Setting a Complex Interval
I am using DBMS_JOB, and I want to schedule a job that runs every 15 minutes
from Monday to Friday, between 6 a.m. and 6 p.m
, February 19, 2003 9:15 AM
To: '[EMAIL PROTECTED]'
Subject:DBMS_JOB : Can submit but does not execute
Hi Gurus,
I have submitted a job but it does not execute. Why? Does the owner
require any privileges ? However, I can use
Hi Gurus,
I have submitted a job but it does not execute. Why? Does the owner require any
privileges ? However, I can use DBMS_JOB.CHANGE command to execute immediately. I
would like the job to execute on a daily basis. Any advice ? TIA
--
-- Submit a job
--
1 DECLARE
2job
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
1 - 100 of 182 matches
Mail list logo
