Re: Oracle RMAN Catalog vs. controlfile advantages
Date: Wed, 14 Apr 2010 20:46:00 -0500
Message-ID: <4bc66fd7$0$11024$c3e8da3_at_news.astraweb.com>
"NetComrade" <netcomrade_at_gmail.com> wrote in message news:892a9daf-0f48-4544-b44d-9199540c3ed8_at_r18g2000yqd.googlegroups.com... On Apr 14, 1:35 pm, "Michel Cadot" <micadot{at}altern{dot}org> wrote:
> > The exact list is in the documentation.
>>
> if these are the 'benefits' then there is really only one=potentially
> longer history.
> You can also create a recovery catalog, an external Oracle database in
> which to store this information. The control file has finite space for
> records of backup activities, while a recovery catalog can store a
> much longer history. The added complexity of operating a recovery
> catalog database can be offset by the convenience of having the
> extended backup history available if you have to do a recovery that
> goes further back in time than the history in the control file.
> There are also a few features of RMAN that only function when you use
> a recovery catalog. For example, RMAN stored scripts are stored in the
> recovery catalog, so commands related to them require the use of a
> recovery catalog. Other RMAN commands are specifically related to
> managing the recovery catalog and so are not available (and not
> needed) if RMAN is not connected to a recovery catalog.
You are not losing much. It is a matter of which set of issues you rather deal with, having recovery catalog or not? Often time with Oracle, moving from one thing to another doesn't solve all the problems; it merely replaces old problems with new ones. Received on Wed Apr 14 2010 - 20:46:00 CDT