If you cannot recover data by yourself, ask Parnassusdata, the professional ORACLE database recovery team for help.
Parnassusdata Software Database Recovery Team
Service Hotline: +86 13764045638 E-mail: [email protected]
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
There many possible reasons why a redo log file becomes corrupted.
Clear the logfile having the problem:
alter database clear <unarchived> logfile ‘<filename>’;
eg: alter database clear logfile group 1;
alter database clear unarchived logfile group 1;
An online redo log file with status=CURRENT or status=ACTIVE in v$log may not be cleared and the error ORA-1624 will be produced. In this case, the database will have to be restored and recovered to a point in time to last available archivelog file.
If an online redo log file has been corrupted while the database is open, the ‘alter database clear logfile’ command can be used to clear the files without the database having to be shutdown.
The command erases all data in the specified logfile group.