Search results

ORA-00354 – (Oracle Hidden Parameter : _allow_resetlogs_corruption)

NOTE: This is One of the Hidden Oracle ParametersDO NOT use it until and unless instructed by Oracle Support. You are trying to start your DATABASE, you found the aforementioned error i.e. ORA-00354.

.Required Action: Perform recovery with a good version of the redo log file or perform cancel-based recovery up to, but not including, the corrupted redo log file.
What will happen, if you don’t have Valid Backup? There is a Workaround via which you can at least recover your Database to some extent:
SQL> select * from v$log;
SQL> alter system set “_allow_resetlogs_corruption”=true scope=spfile;
SQL> shutdown immediate;
SQL> startup mount;
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 897612315 generated at 10/19/2005 16:54:18 needed for thread 1 ORA-00289:
suggestion : /opt/oracle/oradata/conner/archive/1_160.dbf
ORA-00280: change 897612315 for thread 1 is in sequence #160
Specify log: {=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:’/opt/oracle/oradata/conner/system01.dbf’
ORA-01112: media recovery not started
SQL> alter database open resetlogs;
SQL> shutdown immediate;
SQL> startup
Fri Jun 10 16:30:25 2005
alter database open resetlogs
Fri Jun 10 16:30:25 2005
RESETLOGS is being done without consistency checks. This may result in a corrupted database.
The database should be recreated.
RESETLOGS after incomplete recovery UNTIL CHANGE 240677200 Resetting resetlogs
activation ID 3171937922 (0xbd0fee82)
NOTE : I would strongly recommend to immediately take Logical Backup (either Using Data Pump , the conventional one) and Create New Database)

No comments:

Post a Comment