Re: "OK" to loop on DBMS_SLEEP ???

I'm not the one with the issue but I hate cron. Error messaging is not nearly as robust as what is possible with DBMS_JOB and it leaves the application's error messages in multiple places. Also, it requires having one more skill set and more privileges which means more things that can go wrong or be done poorly.

Is there anything cron can do that DBMS_JOB with a bit of C or Java can't do better?

PS: The other thing I don't like about cron is that it is UNIX specific which means it can not be migrated to other platforms without a rewrite.

Daniel Morgan

Knut Talman wrote:

> > I 'm using DBMS_JOB to schedule a function to simply check if an OS file
> > exists, the file may not be there just yet...
> > so Im thinking of putting in a loop around DBMS_SLEEP to keep sniffing for
> > few minutes....
>
> Will DBMS_JOB start the job once and then you'll look for the file, sleep some
> seconds, look for the file and so on? The purpose of DBMS_JOB is to start jobs
> at specified intervals, if you tell it to start the lookup every 5 minutes it
> will do so. You don't need DBMS_SLEEP, it is tautological. Does this job really
> has to run from the database side? Why don't you use cron or at (depending on
> your OS)?
>
> Regards,
>
> Knut
Received on Mon Apr 15 2002 - 13:34:29 CDT