Re: rman block recovery

From: <zigzagdna_at_yahoo.com>
Date: Wed, 11 Apr 2012 16:37:40 -0700 (PDT)
Message-ID: <17663418.254.1334187460565.JavaMail.geo-discussion-forums_at_ynjn4>



On Wednesday, April 11, 2012 5:52:01 PM UTC-4, ddf wrote:
> On Apr 11, 10:07 am, zigzag..._at_yahoo.com wrote:
> > On Wednesday, April 11, 2012 11:44:13 AM UTC-4, zigz..._at_yahoo.com wrote:
> > > I have a database which has database block corruption. I had a successful rman backup of Sunday.
> > > Monday and Tuesday rman backup failed saying
> > > ORA-19566: exceeded limit of 0 corrupt blocks for file F:\EM…….
> >
> > > Then I modified rman script to skip  up to 5 corrupt blocks..
> > > set maxcorrupt for datafile 'F:\......' to 5;
> >
> > > Now my rman backup is successful on Wednesday…
> >
> > > Now, I want to repair blocks using rman’s block recover command:
> > > recover datafile 19 block  321, 322, 385, 513, 577 restore
> > > My questions are:
> > > a. Will rman automatically start with Sunday’s successful back and then apply archived logs.. or
> > > Will it start with Wednesday’s backups and then it won’t be able to recover corrupted blocks…
> > > b. How to force rman block recover to start from Sunday’s backup … (Do I have to mark Wedensday's backup as invalid in rman catalog ...
> >
> > My version of database is 10.2.0.4 on Windows 2003 R2.- Hide quoted text -
> >
> > - Show quoted text -
>
> What level backups are these? RMAN will take the most recent level 0
> backup, recover the blocks from that then apply changes to those
> blocks from the most recent cumulative level 1 backup until the blocks
> are considered recovered.
>
>
> David Fitzjarrell

David:
Thanks. I found by trial and error that it picks up the latest backup even though it skipped the corrupt blocks instead of one on Sunday which does not have any corrupted blocks. I have to use rman’s change backup.. Unavailable command to make most recent backup unavailable, then it goes back to Sunday’s backup. Received on Wed Apr 11 2012 - 18:37:40 CDT

Original text of this message