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

I agree with you about DBAs. Most do know the OS pretty well. But the problem is that many of the things that are done with cron jobs, like nightly imports, really should be done in development by developers who, even if they could write a cron job, are forbidden to do so.

And then there is the problem of the error logs. And application error log split between tables in the database and log files outside the database are impossible for end-users to evaluate. And while we all know that DBAs should check the logs every day ... reality dictates that few have the time and do so. Finally, it is impossible to do statistical analysis of errors logged outside the database, or create reports, without going through the additional step of importing them.

Enough of my whining. I'll get back to work.

Daniel Morgan

Knut Talman wrote:

> > 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.
>
> Well, most DBAs know their OS very well. But I won't force anyone to use cron.
> You should use what you know best. If there is no other way you have to learn
> what solves your problems.
>
> > Is there anything cron can do that DBMS_JOB with a bit of C or Java can't do
> > better?
>
> If you use C or even Java your code isn't fully platform independend too.
>
> > 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.
>
> See above.
>
> A customer has a database and they are doing alot w/ DBMS_JOB. Before they did
> it w/ cronjobs, now they switched to DBMS_JOB. They have 10 background processes
> which consume some memory. Now they buy more memory (machine is swapping).
>
> Regards,
>
> Knut
Received on Mon Apr 15 2002 - 14:14:42 CDT