Re: disable all RMAN jobs in Grid Contol
Date: Wed, 28 Apr 2010 16:30:04 -0700 (PDT)
Message-ID: <8b267e80-5849-4b33-8f33-3d0bf35a243b_at_a2g2000prd.googlegroups.com>
On Apr 28, 1:39 pm, NetComrade <netcomr..._at_gmail.com> wrote:
> 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?
Well obviously, in the situation you have here, you can write a spider script to modify everything everywhere a lot easier with shells, assuming one could have tight control over the crons. It's common (er, ought to be common) in cron based backups to have a marker file tested to see if the backup should run, just like it is common in unix startup scripts for everything in the rc's.
I don't know anything about grid, but I have seen with dbconsole the same problem as http://technology.amis.nl/blog/2892/how-to-stop-running-rman-jobs-in-oem-grid-control which kind of suggests to me there might be something about mgmt_job_engine that could handle your issue. Searching for that on MOS finds some interesting things, maybe a support call would be worthwhile, even if just to give a wishlist item. It might be a hindsight forehead-slapper for them, or there may be an answer. Or they may not care, DBA 2.0 have already had everything thought out for them!
jg
-- _at_home.com is bogus. http://news.slashdot.org/story/10/04/27/2113224/Arizona-Papers-Please-Law-May-Hit-Tech-Workers?art_pos=26Received on Wed Apr 28 2010 - 18:30:04 CDT