Re: Newbie RMAN question: recovery catalogue

Niall Litchfield wrote:
> joel garry wrote:
> > Niall Litchfield wrote:
> >> The controlfile views were correct IIRC, but then I'd have to connect to
> >> each database to see them. I'm after one report for backup activity last
> >> night for all our databases so if anyone has any bright suggestions feel
> >> free.
> >>
> >
> > unix shell fans would generally find it simple to loop through all
> > hosts and db's driving a hereis script for the desired info from
> > sqlplus, then paste them all together.
> >
> > My bright suggestion if you are on Windows would be either get a shell
> > that supports such things, or use whatever your favorite tools are that
> > can do that. Though I'm wondering why you can't just hardcode connects
> > into a sql script - remote security settings? Maybe run a batch on
> > each node and mail the results to an aggregator? How much detail do
> > you want and how many databases do you have?
>
> The example given was 5 - we have more than that on a couple of
> different platforms - I'm excluding the solaris db since I intend to
> kill it soon. One premise of using a catalog is that you get a central
> repository which holds information about your backups, so you only have
> one place to look. This seems to me the RightThing(TM) to do, a bit like
> the way network backup software works these days - you don't connect to
> each server to see if the backup worked, you have a central repository.
> Unfortunately if RMAN doesn't correctly record backup status then this
> is rather unfortunate.
>
> --
> Niall Litchfield
> Oracle DBA
> http://www.orawin.info/services

Yes, why reinvent the wheel. I did the script/create link option for about 48 databases.
I used the linked repository when catalog was not viable option. I prefer the catalog option for production. Stored scripts, not having to worry about losing all backup records and faster reports are all catalog advantages. Received on Thu Jan 11 2007 - 10:04:34 CST