Re: RMAN on Windows Server
Date: Tue, 1 Dec 2009 08:39:00 -0800 (PST)
Message-ID: <838088.85106.qm_at_web113209.mail.gq1.yahoo.com>
Rich you are correct there.... We have had all sorts of issues with Grid control and in fact I have a project to rip it out and completely rebuild it with the latest and greatest in the works. I was actually more thinking from a single windows database point of view and using Oracle Database Control which is pretty solid. Usually when I think windows, I for some reason tend to think small business. Probably a bad bias... :-)
RF
Robert G. Freeman
Oracle ACE
Ask me about on-site Oracle Training! RMAN, DBA, Tuning, you name it!
Author:
Oracle Database 11g RMAN Backup and Recovery (Oracle Press) - ON IT'S WAY SOON!
OCP: Oracle Database 11g Administrator Certified Professional Study Guide (Sybex)
Oracle Database 11g New Features (Oracle Press)
Oracle Database 10g New Features (Oracle Press)
Other various titles
Blog: http://robertgfreeman.blogspot.com
From: Rich Jesse <rjoralist_at_society.servebeer.com> To: "Oracle-L_at_freelists.org" <oracle-l_at_freelists.org> Sent: Tue, December 1, 2009 9:22:19 AM
Subject: Re: RMAN on Windows Server
Hey Robert,
> Are you using Database control or grid control? They will automate this for
> you using the Oracle Scheduler. Of course, if your shutting down your
> database from time to time then the database scheduler would not be able to
> run the backups.
I'd say this option is "USE AT YOUR OWN RISK". I chose it to get RMAN going, but there is a severe issue with Grid Control jobs. Unfortunately all my SR information is now lost since the upgrade to MOS, so I can't give any specifics, although patch 759579 is what I applied to hopefully fix it. The problem is that the scheduled jobs in Grid Control can silently disappear. If I hadn't noticed my archive_dest suspiciously filling up on the weekend, it could have been major trouble.
I'm in the delicate process of replacing all RMAN backups in Grid Control with a POSIX shell script run locally on each server. Much more robust and reliable, IMNSHO. One can't modify *any* aspect of the RMAN script once it's scheduled. The job must be dropped and recreated. How absurd!
Unfortunately I have one Winders XE DB that I'd still like backed up. And since I'm a solo DBA, I can't take the time to rewrite a backup script specific for this ancillary DB, so Grid Control it is for this guy. I've supplemented the job with yet ANOTHER "Check to make sure Grid Control is running" script utilizing the output from a "repvfy verify jobs" command of the EMDiag kit. And even the version of EMDiag somehow broke a few weeks ago, where I needed to upgrade it. Granted, I'm using this diag tool well beyond what it was meant to do, but at this point I don't another viable option.
Really really really (REALLY!) try to avoid Grid Control for production database backups.
Really.
My $.02,
Rich
-- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-lReceived on Tue Dec 01 2009 - 10:39:00 CST