Re: DBMS_JOB
- From: Jared Still <jkstill@xxxxxxxxx>
- To: niall.litchfield@xxxxxxxxx
- Date: Thu, 3 Mar 2005 18:53:42 +0000
You mean like 'at' on Windows?
I mention this as I know you do windows. :)
'at' is anything if not unreliable.
It has broken on a number of machines here, and no one can
ever seem to determine why.
I've been forced ( *forced* mind you) to resort to a Perl version of
cron on Windows boxes where I want to reliable run external jobs.
As for database jobs, DBMS_JOB has served me quite well. Not
as robust as it could be, but it is easy to use, and on Windows
platforms, saves me from setting up an external scheduler.
A working one, that is.
Jared
On Thu, 3 Mar 2005 08:54:31 +0000, Niall Litchfield
<niall.litchfield@xxxxxxxxx> wrote:
> On Wed, 2 Mar 2005 23:32:03 +0000 (GMT), Connor McDonald
> <hamcdc@xxxxxxxxxxx> wrote:
> > I've always been slow at putting together complex interval functions...so
> > some other solutions I
> > typically use are:
> <snip good stuff>
>
> I'm surprised no-one has suggested not using DBMS_JOB, but using some
> other scheduler (cron or the scheduled tasks applet perhaps). In my
> book DBMS_JOB doesn't really cut it (and of course its gone in 10g).
> --
> Niall Litchfield
> Oracle DBA
> http://www.niall.litchfield.dial.pipex.com
> --
> //www.freelists.org/webpage/oracle-l
>
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
--
//www.freelists.org/webpage/oracle-l
Other related posts:
