"Howard J. Rogers" <howardjr2000_at_yahoo.com.au> wrote in message
news:3f7c8ba8$0$2484$afc38c87_at_news.optusnet.com.au...
> Ryan Gaffuri wrote:
>
> > When deciding whether to use a database catalog to store your RMAN
> > processes or using the control file, what should be taken into
> > account?
> >
> > When is it better to use just a control file to backup your catalog? I
> > would assume you would do this because its simpler, but are there any
> > other reasons for it?
>
> Hi Ryan,
>
> Pay attention to what Volker is saying elsewhere. He's got it just about
> spot on.
>
> There is no functional reason why (in 9i) you need to run with a catalog.
>
> You don't lose out on any functionality whatsoever if you run without a
> catalog, except that you can't store scripts. But the 9i syntax means that
> scripts are less needed than they might have been. And in any case, you
can
> store scripts as text files and execute them within RMAN with the '@'
> syntax you probably know about from SQL*Plus.
>
> If your backup needs are complex (eg, many databases, each with different
> recovery strategies; a need to store backups for 7 years for audit
purposes
> and that sort of thing) then the catalog is indeed your friend. But for
> most practical purposes, you don't need one. It's another database to
> maintain and to backup. Possibly another license, too.
>
> Regards
> HJR
you have to pay license fees on RMAN? I thought you only pay for
'production' systems. RMAN counts?
Received on Thu Oct 02 2003 - 15:46:32 CDT
