I on the Internet to find some solutions such as questions, my way is
First shutdown immediate
Then the startup mount
Then input the alter system set "_allow_resetlogs_corruption"=true scope=spfile;
Then enter the shutdown immediate
To enter the startup mount
Then input recover database until cancel;
Then choose cancel
So wrong
SQL> Recover database until cancel
ORA - 00279:19002809 change generated at 11/13/2017 15:00:28 men for thread 1
ORA - 00289: the suggestion:
/opt/oradata/flash_recovery_area/ICDTEST/archivelog/2017 _11_14/o1_mf_1_409_ % u_. The a
Rc
ORA - 00280:19002809 for change thread 1 is in the sequence # 409


Specify the log: {& lt; RET>=suggested | filename | AUTO | CANCEL}
Cancel
ORA - 01547: warning: RECOVER succeeded but OPEN RESETLOGS order to get the error below
ORA - 01194: the file 1 needs more recovery to be consistent
ORA - 01110: data file 1:
'/opt/oradata/oradata/ICDTEST/datafile/o1_mf_system_d849qjpd_ DBF'


ORA - 01112: media recovery not started


Then input the alter database open resetlogs;
Then becomes, like in the screenshot

CodePudding user response:

What kind of type of damage that this wants to see you online redo, if it is INACTIVE log is damaged, directly clear logfile, data is not lost, but if it is ACTIVE or CURRENT, that is complex, may refer to:
http://blog.csdn.net/liaocongyuan1314/article/details/50847529

In addition, when you are behind the most open less final semicolon,

CodePudding user response:

Database recovery, make uncertain, can find us, 7 * 24 technical support service

CodePudding user response:

refer to the second floor xifenfei response:

database recovery, make uncertain, you can find us, 7 * 24 technical support services

Bad,