Recover Scenario - Solaris 10.2.0.2
From: Newman, Christopher <cjnewman_at_uillinois.edu>
Date: Wed, 10 Mar 2010 18:57:12 -0600
Message-ID: <565F609E6D736D439837F1A1A797F341029BEF3A_at_ADMINMAIL1.ui.uillinois.edu>
Hello,
Wed Mar 10 18:15:59 2010
Media Recovery failed with error 600
Date: Wed, 10 Mar 2010 18:57:12 -0600
Message-ID: <565F609E6D736D439837F1A1A797F341029BEF3A_at_ADMINMAIL1.ui.uillinois.edu>
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-lReceived on Wed Mar 10 2010 - 18:57:12 CST