Errors ORA-00354, ORA-00353, ORA-00312


I' m using Oracle 11G in Windows 2008 Server.
When I try to start up the database, it gives the  following errors  ;

ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 97452 change 11660519  time 08/21/2010 16:04:47
ORA-00312: online log 1 thread 1: 'D:\APP\ADMINISTRATOR\ORADATA\DBO\REDO01.LOG'

It can' t be opened.

When I execute the sql query below  for  observing status of the  redolog group;


It's status  is Active.    

In addition to these, I have no backups.

What can I do to start up  the database?

Who is Participating?
schwertnerConnect With a Mentor Commented:
You start up the DB.
If it was shut down gracefully (without abort, force options) the corrupted online redo is not a problem.
You will be able to open the DB. One way to do this is to use init.ora  parameter file with the parameter:

Another possible way is to mount the database and to to log switch. After that drop the damaged group and create another.

And do not forget: multiplex the online redo log groups. If the group has more then one member you will not experience this.
slightwv (䄆 Netminder) Commented:
check out the following:

You will likely lose some data.  If this database is important, I suggest a solid backup and recovery plan moving forward.
I didn't open the link that slightwv posted but I would also run dbverify on the database. You can do a google search or ask us for additional help but that utility will look to see if there are problems with the database and datafiles.
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

slightwv (䄆 Netminder) Commented:
dbv is for database files.  I don't think you can run it against online redolog files.

Check out:

Which references the following Metalink note:
DBV cannot be used on Redo Logs (and ArchiveLogs) and Controlfiiles.
See Note#35512.1
Dumb me, I didn't read the problem correctly and thought this was a problem with a datafile. My bad, you are 100% correct.
slightwv (䄆 Netminder) Commented:
>>parameter file with the parameter: _allow_reset_logs_corruption

this is a LAST resort if everything else fails.
If you do this you will not be supported and will need to take a full export, re-create the database, then import the data back in.

The main question here is WHY you startup the DB:
1. Because you shutdown the DB
2. Because it fails
In the first case you needn't the online redo logs - everything except the damaged redo log is OK
In the second case you need the online redo log for crash recovery (will be done automatic) but you need also the online redo log. And it is damaged and not multiplexed.

The next question is what kind of DB you monitor - productive or development. If it is not productive then loss of data may be acceptable.

The conclussion for the future - multiplex the online redo logs.
orcun_turkecAuthor Commented:
Thank you...
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.