I'm happy to report that the author of the script recently replied and
has updated the source at the web site shown, in case anyone downloaded
this. Thanks.
-Mark Bole
Thank You very much, probably this is the solution that i am looking for.
Great day, Madhu
On Tue, 2005-06-14 at 08:42 -0700, Mark Bole wrote:
Perhaps best to use DBMS_SCHEDULER if you are on 10g.
A very good solution specifically for your situation (VCS) is here:
http://www.vxideas.org/cron-edit
This shell script is designed to be a resource in your VCS group. I used it for several years in a production cluster -- both a primary and a logical standby database, each with its own set of associated cron jobs, and this tool handled them both, whether running together on one node or separately on different nodes -- the correct cron jobs always ran exactly where they were supposed to, nowhere else. No need to clutter up your crontab entries themselves with some ugly if-then logic.
Unfortunately there was one small bug in the script, which is fixed by commenting out one line in the script as shown here. I sent the fix to the author but never got a response. :-(
add_entry() { # this next line was a bug, un-doing what remove_entry did # cp $before $after
-- //www.freelists.org/webpage/oracle-l
