Title: RE: RE : RMAN Repository
I do have one scenario where you really have to use a recovery catalog...  When attempting to backup a VLDB that uses read only tablespaces and extremely infrequent backups for most of the data (i.e. a large datawarehouse), a recovery catalog is very important...  You just may not have the time to perform full backups of your multi terabyte database...  In this case, you better hope that the backup of your read only tablespace from 15 months ago is still around...  Since the CONTROL_FILE_RECORD_KEEP parameter only goes to 1 year, you may be stuck unless you have that data in a recovery catalog...
 
Tim
-----Original Message-----
From: Freeman Robert - IL [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 09, 2003 12:35 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: RE : RMAN Repository

The only things you can't do with controlfile RMAN/database metadata is:

1) use previous "incarnations" of the database for recovery;

Actually, you can, it's just a manual process. This is documented in the RMAN book. Also, in 9i you can do automated backup/restore of control files of your database in RMAN without the recovery catalog, and you can manually recover a control file if that is required using dbms_backup_restore.

 

Robert

Robert G. Freeman
Technical Management Consultant
TUSC - The Oracle Experts www.tusc.com
904.708.5076 Cell (it's everywhere that I am!)
Author of several books you can find on Amazon.com!

-----Original Message-----
From: Orr, Steve [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 09, 2003 10:46 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: RE : RMAN Repository

If you aren't using a repository all you have to do is make sure control file backups are part of the routine. There are 2 ways to backup the backup metadata: 1) the RMAN repository database; 2) backup controlfiles.

Functionally and operationally they're pretty much the same. The only things you can't do with controlfile RMAN/database metadata is: 1) use previous "incarnations" of the database for recovery; 2) use database stored scripts. No big deal as far as I'm concerned.

When RMAN first came out a separate repository database was a requirement. Subsequent releases added some functionality for using controlfiles. The vulnerability of losing the repository or losing the backup controlfile is about equivalent. The overhead of the repository database is more. With the initial releases of RMAN (EBU) Oracle was rightly criticized for the fact that you had to backup the database that holds information about the database you want to backup. Getting rid of this silliness seems reasonable to me.


Steve Orr-man for RMAN,
Bozeman, Montana


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 08, 2003 2:14 PM
To: Multiple recipients of list ORACLE-L
Subject: RE : RMAN Repository
Importance: High


And how does one go about restoring a database when all control files
are lost, and the only recovery data is stored in the control file?

This doesn't sound very reasonable.

Jared


"Deshpande, Kirti" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
 01/08/2003 11:44 AM
 Please respond to ORACLE-L
 
        To:     Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
        cc:
        Subject:        RE : RMAN Repository

Joe,
 That's what I have heard (from 2 Oracle University
Professors/Lecturers/Demonstrators). But no one would tell me when it may
happen. We do not use RMAN (yet) so I did not pursue it further.

- Kirti

-----Original Message-----
Sent: Wednesday, January 08, 2003 1:08 PM
To: Multiple recipients of list ORACLE-L

<snip>

Obilgatory oracle statement/question:  rumor has it by some instructors
that RMAN repository is going away and only control file recoveries
will be possible, truth or fiction?

joe

Reply via email to