Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RMAN limitiations when used with controlfile only

RMAN limitiations when used with controlfile only

From: Jared Still <jkstill_at_gmail.com>
Date: Tue, 17 Apr 2007 16:46:17 -0700
Message-ID: <bf46380704171646u7088d050vbea4fd44a2ae807a@mail.gmail.com>


Dear List:

I have been compiling a list of limitiations that are imposed on RMAN when the catalog database is in the controlfile only.

While Oracle recommends using a repository database, the official proclamation has been that its use is optional.

Lately it has become apparent that a repository database isn't really optional.

The only stated limitation of using the controfile only is that stored scripts cannot be used. There are several documents on MetaLink that seem to contradict that. Limitations with TSPITR, databases that may be missing archive log backups do to being opened with RESETLOGS, and others I'm sure.

The fix for the limitiations I have found is to 'use a recovery catalog in the database.'

If you know of any other limitations imposed on RMAN when the catalog resides only in the controlfile, please post them.

Thanks,

--

Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

--

http://www.freelists.org/webpage/oracle-l Received on Tue Apr 17 2007 - 18:46:17 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US