在這裡編輯新頁面「Désert/Oracle/Force-Startup」
shutdown immediate
startup mount
ALTER SYSTEM SET "_allow_resetlogs_corruption"= TRUE SCOPE = SPFILE;
shutdown immediate
startup mount
alter database open resetlogs;
recover database until cancel;
Why you need to run this command after resetlogs after setting parameter _allow_resetlogs_corruption
Try below step:
SQL> alter system set "_allow_resetlogs_corruption"=true scope=spile;
System altered.
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 605030496 bytes
Fixed Size 731232 bytes
Variable Size 301989888 bytes
Database Buffers 301989888 bytes
Redo Buffers 319488 bytes
Database mounted.
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 43461065888 generated at 09/01/2010 09:06:15 needed for thread 1
ORA-00289: suggestion : /u202/arch/SPERST/log1_0000000001.arc
ORA-00280: change 43461065888 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
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: '/sperdev2/sperst/data/system01.dbf'
ORA-01112: media recovery not started
SQL> alter database open resetlogs;
Database altered.
Your CURRENT redo log file is corrupted. That's why Oracle recommends to multiplex redo log files to different folders or mount points. I would strongly suggest you to contact Oracle Support to solve this issue. "_allow_resetlogs_corruption" parameter should be used only with Oracle Support's suggestion. Sometimes it works, sometimes not. If it is a test database, drop it and recreate it from scratch. If it is a production database, contact Oracle Support. Most probably they will suggest you to restore the database from backup And please, mutliplex your controlfiles and redo log files in the future BR, Kamran Aghayev A. (OCM)
https://community.oracle.com/tech/developers/discussion/3824617/trouble-to-startup-db