REDO LOG CORRUPTION - DROPPING REDO LOGS NOT POSSIBLE - CLEAR LOGFILE
Last updated on OCTOBER 20, 2016
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Information in this document applies to any platform.
Redo log corruption errors in one of the redo log files while the database is open.
The redo log corruption could be any of these errors:
ORA-16038 log %s sequence# %s cannot be archived
ORA-354 corrupt redo log block header
ORA-353 log corruption near block <num> change <str >time <str>
ORA-367 checksum error in log file header
ORA-368 checksum error in redo log block
Dropping the redo logs is not possible as it may be needed for instance recovery.
The online redo logs may not be dropped if:
There are only two log groups
The corrupt redo log file belongs to the current group
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms