Re: Recover Scenario - Solaris 10.2.0.2

After you sort out the mess in the production DB take a backup of only the affected datafile and restore it to the standby. The standby won't need to apply the inconsistent redo and continue on it's merry way.

Harel Safra

On 11/03/2010 02:57, Newman, Christopher wrote:
>
> Hello,
>
> We've had datafile moved in our production box; then moved back. This
> has caused logical errors in the datafiles. These are all index
> tablespace related datafiles, so our plan there is to drop the
> tablespaces, recreate, and recreate the indexes.
>
> My question... is there any way to manipulate this on the physical
> standby's, or is rebuilding the standby's the only logical move?
>
> Errors look like this:
>
> ORA-10564: tablespace GEN_LARGE_INDX
>
> ORA-01110: data file 149: '/u07/oradata/BANPROD/gnli02BANPROD.dbf'
>
> ORA-10561: block type 'TRANSACTION MANAGED INDEX BLOCK', data object#
> 70727
>
> Wed Mar 10 18:15:59 2010
>
> Media Recovery failed with error 600
>
> I'm thinking rebuild is going to be our only option, as the standby's
> won't get past the 'bad' redo to be able to get to the fix.
>
> Chris Newman
>
> Database Specialist
>
> AITS, University of Illinois
>
> 217-333-5429
>

--
http://www.freelists.org/webpage/oracle-l