Opening the database with corrupted redo log can cause a loss of committed transactions, therefore, you need to do it at your own risk
Steps :
SQL> Startup Mount;
SQL> alter system set “_allow_resetlogs_corruption”=true scope=spfile;System altered.
SQL> shutdown immediate;
ORA-01109: database not openDatabase dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.Total System Global Area 281018368 bytes
Fixed Size 779000 bytes
Variable Size 229383432 bytes
Database Buffers 50331648 bytes
Redo Buffers 524288 bytes
Database mounted.
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> recover database until cancel;
ORA-00280: change 101350984923848 for thread 1 is in sequence #2333
Specify log: {=suggested | filename | AUTO | CANCEL}
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: ‘/home/oracle/oradata/rsdb/system01.dbf’
ORA-01112: media recovery not started
SQL> alter database open resetlogs;
SQL>shutdown immediate;
SQL>Startup;
You can Do this Steps When Data Its Not Important , Such As Test Evn , ….
Enjoy
Osama Mustafa
