Re: dbms_job question

"Daniel Morgan" <damorgan_at_x.washington.edu> schrieb im Newsbeitrag news:1067001227.901176_at_yasure...
> Volker Hetzer wrote:
>
> >"Daniel Morgan" <damorgan_at_x.washington.edu> schrieb im Newsbeitrag news:1066940302.848416_at_yasure...
> >
> >
> >>Ryan Gaffuri wrote:
> >>
> >>
> >>
> >>>Is it possible to have a job run every 15 minutes between 7PM and 7AM
> >>>every day accept sundays?
> >>>
> >>>
> >>>
> >>>
> >>You but my feeling is that you should probably just run it every 15
> >>minutes and make the
> >>first statement in the procedure an IF statement that checks the clock
> >>to see when it is
> >>appropriate to proceed.
> >>
> >>With respect to Paddy's suggestion ... I'd avoid cron unless there was
> >>no other choice. Cron has
> >>numerous problems as compared with DBMS_JOB. The least of which is that
> >>it requires involving
> >>SysAdmins in everything you do.
> >>
> >>
> >
> >Personally I'd like the fact that the sysadmin is responsible to make sure the
> >cronjobs properly send their email. Much easier than using utl_smtp for it,
> >especially if something goes wrong.
> >
> >If I don't need notification and don't care if it fails occasionally (taking regular
> >statspack snapshots for instance) I use dbms_jobs and check the log files
> >and job views.
> >
> >Lots of Greetings!
> >Volker
> >
> >
> I'd like to agree but I can't. Too many times I have developed on
> Windows and deployed on UNIX. Or developed
> on Sun and deployed on HP/UX or AIX. UTL_SMTP is operating system
> neutral. And as much as I enjoy working
> with a good UNIX SA ... they have other work to do and rarely do they
> like what they do run through a QA
> department before implementation.
>
> In almost every production environment in which I have ever worked ...
> SA's operate outside of QA and that is
> not a good place for important functionality in a deployed
> line-of-business application.

All right, depends on the job you want to do. If the job is part of the "purpose" of the db, like emailing notifications when some rows change it should go into the database.

Another distinction is, do I want the job to be run if there's trouble with the database? If the db is down, dbms_job's won't run, cron jobs will. For instance I run gather_database_stats as a dbms_job because it doesn't make sense to run it without a database.

OTOH I'm using cron for the rman backups. This has nothing to do with the CAD library running on the db and when the db is down or there's trouble I still want the email at least that one time when the trouble surfaces. Of course, I'm assuming here that in case of trouble the OS is more likely to survive than the db.

SA's outside QA? I see a picture in my mind of a business app running on a mailordered PC where "some" linux has been installed by a student and no one checks for faulty disks and then that same company employs a highly paid dba for twiddling with the init.ora parameters and balancing load and stuff. <Shudder> Fortunately I live in a different world.

Lots of Greetings!
Volker Received on Fri Oct 24 2003 - 09:31:58 CDT