I also agree, cron WORKS well ! The only thing I would add to cron jobs (shell scripts) is to use a semaphore file.
e..g. —--------------------------------------- semfile=/tmp/$0.RUNNING if [ -f $semfile ] ; then exit ; fi touch $semfile DO SOME SHELL STUFF rm $semfile exit —--------------------------------------- This way no matter how frequent you run the job or how long it takes the job to run, it still works. I had a developer run a job every 5 mins but the job took 15 mins to run, so you can guess what begins to happen after a few days :-) Gene >>> [EMAIL PROTECTED] 03/15/02 08:18AM >>> While I agree that dbms_job is the right way, we had lots of problems with dbms_job suddenly failing (i.e. it just stops working) in 9011 and 9012 versions of database. Finally it was something to do with job queue processes, with the help of OWS we fixed it. BUT, I still don't trust dbms_job on our 9i production db and hence all critical jobs are run by our close friend 'cron', it works!. Raj ______________________________________________________ Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni at ESPN dot com Any opinion expressed here is personal and doesn't reflect that of ESPN Inc. QOTD: Any clod can have facts, but having an opinion is an art! -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Gene Sais INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
