Sounds like a case where a dummy recovery + _allow_resetlogs_corruption
could help ya.
Needless to say, try this at home but not at work in production ;)
Stefan
On 26 Aug 2016 4:05 a.m., "Andrew Kerber" <andrew.kerber@xxxxxxxxx> wrote:
Good idea, but no joy... I tried until sequence because the database wasnt
open, and I couldnt get an scn:
SQL> select CURRENT_SCN from v$database;
CURRENT_SCN
-----------
0
I expect I will just have to re-create it.
RMAN> recover database until sequence 411;
Starting recover at 25-AUG-16
using channel ORA_DISK_1
starting media recovery
RMAN-08187: WARNING: media recovery until SCN 22735814 complete
Finished recover at 25-AUG-16
RMAN> alter database open resetlogs;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of sql statement command at 08/25/2016 15:54:36
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '+DATA/OEM13C/DATAFILE/system.265.916168391'
On Thu, Aug 25, 2016 at 3:45 PM, Jonathan Lewis <
jonathan@xxxxxxxxxxxxxxxxxx> wrote:
Could you do an rman recovery to SCN prior to the lost write ?
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
@jloracle
------------------------------
*From:* oracle-l-bounce@xxxxxxxxxxxxx [oracle-l-bounce@xxxxxxxxxxxxx] on
behalf of Andrew Kerber [andrew.kerber@xxxxxxxxx]
*Sent:* 25 August 2016 21:46
*To:* ORACLE-L
*Subject:* ORA-00742: Log read detects lost write in thread 1 sequence
409 block 128535 ORA-00312: online log 1 thread 1:
'+RECO/OEM13C/ONLINELOG/group_1.261.916169151' ORA-00312: online log 1
thread 1: '+DATA/OEM13C/ONLINELOG/group_1.263.916169099'
This is on a system running in a vm on my desktop, thoroughly
non-critical. But its a little annoying that my desktop rebooted when I
lost power, and corrupted these redo log files. I can always rebuild the
database, but I am curious if anyone can think of a way to recover from the
error below on the current redo log. I tried to clear it, but no joy, and
alter database open resetlogs doesnt work either.
Any other thoughts before I give up and start over?
ORA-00742: Log read detects lost write in thread 1 sequence 409 block
128535
ORA-00312: online log 1 thread 1:
'+RECO/OEM13C/ONLINELOG/group_1.261.916169151'
ORA-00312: online log 1 thread 1:
'+DATA/OEM13C/ONLINELOG/group_1.263.916169099'
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
