SQL>
ORACLE instance started.startup
Total System Global Area ***** bytes
Fixed Size ***** bytes
Variable Size ***** bytes
Database Buffers ***** bytes
Redo Buffers ***** bytes
Database mounted.
ORA-00333: redo log read error block *Number* count *Number*
And from alert log:
Wed Jun 03 04:56:10 2015
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
parallel recovery started with 23 processes
Started redo scan
Incomplete read from log member '/d1/oracle/redo01/testdb/redo07a.log'. Trying next member.
Aborting crash recovery due to error 333
Errors in file /opt/oracle/base01/diag/rdbms/testdb/testdb/trace/testdb_ora_4512.trc:
ORA-00333: redo log read error block 704089 count 8192
Errors in file /opt/oracle/base01/diag/rdbms/testdb/testdb/trace/testdb_ora_4512.trc:
ORA-00333: redo log read error block 704089 count 8192
ORA-333 signalled during: ALTER DATABASE OPEN...
Resolution:
- Startup DB in mount stage:
SQL>
- Query the status and location of the redo logsstartup mount;
SQL>
STATUS MEMBERselect l.status, member from v$logfile inner join v$log l using (group#);
---------------- ----------------------------------------
INACTIVE /d1/oracle/redo01/testdb/redo01a.log
INACTIVE /d1/oracle/redo01/testdb/redo02a.log
INACTIVE /d1/oracle/redo01/testdb/redo03a.log
INACTIVE /d1/oracle/redo01/testdb/redo04a.log
INACTIVE /d1/oracle/redo01/testdb/redo05a.log
INACTIVE /d1/oracle/redo01/testdb/redo06a.log
CURRENT /d1/oracle/redo01/testdb/redo07a.log
INACTIVE /d1/oracle/redo01/testdb/redo08a.log
8 rows selected.
- Recover the database using backup controlfile and then specify the redo log member tagged as 'CURRENT' from the above query
SQL>
ORA-00279: change 971358405007 generated at 06/01/2015 21:47:20 needed for thread 1recover database using backup controlfile;
ORA-00289: suggestion : /d1/oracle/archivelogs01/testdb/1_167_862932830.dbf
ORA-00280: change 971358405007 for thread 1 is in sequence #167
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/d1/oracle/redo01/testdb/redo07a.log
Log applied.
Media recovery complete.
- Open the database with reset logfile
SQL>
alter database open resetlogs;