Sorry - I should have been more specific with earlier
versions - I was referring to 8.0 and (if memory
serves) one of the 8.1.x's. I was pondering whether
this had crept into 9 (although I would doubt it)
Keep us posted on what happens :-)
Cheers
Connor
--- Freeman, Robert [EMAIL PROTECTED]
Some comments...
- some earlier versions of the db had job bugs where
the next date was not correctly calculated and thus
stopped running - typically threw an ora-600 or at
least a trace file in bdump (as opposed to udump)
- we're running about 50 jobs at various frequencies
on 9013 and not
Connor,
In our case the intervals were 5AM, 6AM and 12PM ... and it still didn't
work. Perfstat was the biggest problem, I used to run it at 15 min
intervals, and it would work for an hour or two and die unexpectedly without
any message or trace file.
Raj
See inline...
Robert G. Freeman - Oracle8i OCP
Oracle DBA Technical Lead
CSX Midtier Database Administration
Author: Oracle9i New Features
Mastering Oracle8i
Clark Griswold: Eddie, has anyone ever told you that you're bad luck?
Cousin Eddie: Those were my mother's dying
Nope, they never show up there, so it appears the scheduler, for some
reason, just decides
to stop running them.
RF
Robert G. Freeman - Oracle8i OCP
Oracle DBA Technical Lead
CSX Midtier Database Administration
Author: Oracle9i New Features
Mastering Oracle8i
Clark
I've got a TAR open on it now, but slow movement.
RF
Robert G. Freeman - Oracle8i OCP
Oracle DBA Technical Lead
CSX Midtier Database Administration
Author: Oracle9i New Features
Mastering Oracle8i
Clark Griswold: Eddie, has anyone ever told you that you're bad luck?
We had the same situation and then we use cron that never fails. Now, we
don't trust dbms_job ... I had a TAR open on that, but can't access it now.
Raj
__
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Dick,
Thanks, and yes I understand both, but we had really bad luck with dbms_job
which would stop working without any errors. OWS was unable to give a quick
fix, and eventually it turned out that one of the parameters (I think
job_queue_processes) was getting reset or something like that. We
Just out of curiosity, are the jobs showing up in dba_jobs_running? I'm
wondering if they ever report back as having completed.
Brian
-Original Message-
Robert
Sent: Monday, June 10, 2002 1:13 PM
To: Multiple recipients of list ORACLE-L
Anyone run into any problems with the job
Hi Saroj,
As per my knowledge you cannot specify interval in at command .
but you can add multiple entries in at command like
at \\machinename 8:00 /interactive /every:M,T,W,Th,F,S
at \\machinename 9:00 /interactive /every:M,T,W,Th,F,S
hope it will solve ur prblm.
Kranti
Saroj,
The only way that I can do this is using NT's GUI Task Scheduler. There is
an advanced option there that lets you repeat tasks at every specified
interval and the duration.
Regards,
George
-Original Message-
Sent: Tuesday, October 30, 2001 12:20 AM
To: Multiple recipients of
Hi,
You could use the soon command (in the resource kit) to schedule it to run
in 3600 seconds.
The batch file could also have logic to check the current time to work out
when to schedule it next.
You could also use at and have your batch calculate the next time to run at
- using either batch
'soon' command can run at any time interval. it doesn't have to be 3600
sec, could be any number of seconds.
-Original Message-
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 30, 2001 4:56 PM
To: Multiple recipients of list ORACLE-L
Hi,
You could use the soon command (in the
Hi,
You could use the soon command (in the resource kit) to schedule it to run
in 3600 seconds.
The batch file could also have logic to check the current time to work out
when to schedule it next.
You could also use at and have your batch calculate the next time to run at
- using either batch
Hi,
You could use the soon command (in the resource kit) to schedule it to run
in 3600 seconds.
The batch file could also have logic to check the current time to work out
when to schedule it next.
You could also use at and have your batch calculate the next time to run at
- using either batch
Message-
From: David Messer [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, April 03, 2001 5:36 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: "AT" scheduler
I've gotten similarly odd performance from AT. I find that it, among
other
issues, doesn't do well if ther
echo "0,5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/local/bin/myjob"
/tmp/crontab
crontab /tmp/crontab
-Original Message-
Sent: Tuesday, April 03, 2001 12:30 PM
To: Multiple recipients of list ORACLE-L
Can anyone tell me how to schedule a batch job to run every 5 minutes using
the
My Computer/Scheduled Task might fit your needs better, since it has got a
Windows GUI. It's easier to handle than the AT command. The GUI in some
places is illogial, but still it might be usefull for you.
Tamas Szecsy
-Original Message-
Sent: 2001.04.03. 8:22 PM
To: Multiple
Even more, if you are running crontab on NT, I strongly suggest
to take a look at www.SuSe.com or alike.
-Original Message-
Sent: Tuesday, April 03, 2001 2:22 PM
To: Multiple recipients of list ORACLE-L
If you are running on NT, I strongly recommend you obtain crontab for
Windows.
AT
19 matches
Mail list logo