Re: disable all RMAN jobs in Grid Contol

From: NetComrade <netcomrade_at_gmail.com>
Date: Wed, 28 Apr 2010 13:39:13 -0700 (PDT)
Message-ID: <6c2cad20-cf25-4f1c-8e9b-d52f49358f79_at_a16g2000vbr.googlegroups.com>



On Apr 28, 2:52 pm, John Hurley <hurleyjo..._at_yahoo.com> wrote:
> NetComrade:
>
> > I have multiple databases writing to NFS for backups, and the NFS will
> > be going down for MW.
> > Is there any way to suspend RMAN jobs w/o downtiming all the
> > databases, or w/o suspending individual backup jobs?
>
> Put em in cron!  Or some kind of external scheduler!
>
> Let's see ... if your datbase is having issues and you have something
> that is supposed to run but depends on the database ... hmmm ...
>
> If you have something outside the database that doesn't depend on the
> database can you put together something that does some checking and
> alerting when needed ... hmmm ...

We do all oracle related jobs through grid control, including custom monitoring scripts, that way we don't have to hunt down outputs from cron.
If my database is having issues, my grid has nothing to do with it, it's on different host and a different database. If my database is not available we fail back to prompt to toubleshoot it, but we ensure our alerting works otherwise. With 20-30 databases to track all over the place, cron is really not a good option. Plus, how is modifying cron on 2-3 dozen hosts easier then clicking through a few jobs in a single interface? Received on Wed Apr 28 2010 - 15:39:13 CDT

Original text of this message