Re: rman restore from consistent backup
Date: Thu, 12 Feb 2009 14:27:32 -0800 (PST)
On Feb 12, 9:38 am, Charles Hooper <hooperc2..._at_yahoo.com> wrote:
> Pages 373-374 of the book "RMAN Recipes for Oracle Database 11g"
> offers two other approaches, one using a backed up control file, and
> the other using current control file:
snip ... not familiar with that book
> Using the current control file:
> RMAN> connect target /
> RMAN> startup mount;
> RMAN> restore database;
> RMAN> alter database open resetlogs;
> (the above is expected to return ORA-01139, switch to SQL*Plus)
> SQL> recover database until cancel;
> SQL> cancel
> SQL> alter database open resetlogs;
Starting to lose track probably of the point you are trying to make Charles.
If you are still talking about trying to recover a database that was in noarchivelog that had an rman backup of it taken while it was in MOUNT ... ( I think you are ) ... then I can think of no good reason to not restore the controlfile.
It may work in certain cases using the current one but other ones can be constructed where it won't. The idea if intentionally causing an ORA error via RMAN then bypassing by sqlplus ... more than a little ugly.
Better idea but still probably not a good one in this specific case is to use RMAN for the restore but do all the recover thru sqlplus in the first place.
I think a better recommendation is to just go ahead and restore the controlfile.
Moving outside of that specific focus ( if we were there in the first place ... personally I always follow any RMAN backup with my own backup of the controlfile done in 2 ways. I use the rman copy controlfile command ( in it's own session not associated with any backup commands ) afterwards and also use sqlplus to get a copy of the spfile and backup controlfile to trace. It may be overkill and it is old school but personally I don't want to depend on any autobackup provided "probably can get this stuff back" dependencies. Received on Thu Feb 12 2009 - 16:27:32 CST