Re: RMAN Restore Scenario: all copies of control files are lost
Date: Mon, 23 Nov 2009 07:26:02 +0000 (GMT)
You can simply do
1) copy /oradata/controlfile.bak to the control_files location specified in the SPFILE (or PFILE); 2) startup mount; 3)recover database 5) alter database open resetlogs;
if you configure controlfile auto backups then
restore controlfile from autobackup
- On Fri, 20/11/09, Roger Xu <wellmetus_at_gmail.com> wrote:
From: Roger Xu <wellmetus_at_gmail.com>
Subject: RMAN Restore Scenario: all copies of control files are lost To: oracle-l_at_freelists.org
Date: Friday, 20 November, 2009, 16:53
Hi RMAN gurus,
Say one backs up a database using the following RMAN block daily:
backup database archive log all;
SQL 'alter database backup controlfile to '/oradata/controlfile.bak';
All copies of the current control files were in the same disk and the disk crashed. Assuming other parts of the database are fine, will the following steps work to restore the database to the minute when the disk crashed?
1) copy /oradata/controlfile.bak to the control_files location specified in the SPFILE (or PFILE); 2) startup mount; 3) find out the most recent archived redo log sequence number (12345) in log_archive_dest_1; 4) restore database until sequence 12346; 5) alter database open resetlogs;
The reason this may work is that RMAN automatically searches for archived and online redo logs that are not recorded in the RMAN repository (in this case the backup controlfile).
Do you think this is one of the many advantages using RMAN vs user-managed backup?
Received on Mon Nov 23 2009 - 01:26:02 CST