Redo Log Corruption - Dropping Redo Log Is Not Possible - CLEAR LOGFILE
(Doc ID 1078456.6)
Last updated on JUNE 04, 2021
Applies to:Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A 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-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 log is not possible because 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
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!