ORA-00353 log corruption

[Former Member]

Hello Experts,

I am facing below errors while applying logs to DR system. I am getting archive log corruption at one step. I restore offline backup to bypass this log corruption but same error continue.

I tried to search notes and found note 694155 where ALTER DATABASE CLEAR UNARCHIVED LOGFILE '<log>' command is given. Not able to understand exact format as getting error in this command as well.

Can you please help in below problem:

====

SQL> recover database using backup controlfile until cancel;

ORA-00279: change 672579068 generated at 01/22/2010 01:34:00 needed for thread

1

ORA-00289: suggestion : F:\ORACLE\PRD\ORAARCH\PRDARCHARC15731_0667429501.001

ORA-00280: change 672579068 for thread 1 is in sequence #15731

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

auto

ORA-00283: recovery session canceled due to errors

ORA-00356: inconsistent lengths in change description

ORA-00353: log corruption near block 16269 change 672579068 time 11/17/2117

12:11:51

ORA-00334: archived log: 'F:\ORACLE\PRD\ORAARCH\PRDARCHARC15731_0667429501.001'

ORA-01112: media recovery not started

=====

Thanks,

Regards,

Swapnil Lakhe

[former_member524429]

Hi,

As mentioned in previous message, you can use second consistent offline redo log file from backup copy.

If you are still not able to resume your Recovery process due to corrupted redo log file problem, then only point in time recovery is the final option, but it will nt server the purpose of DR System.

As an alternative, You can again restore ur DR site from latest Online/Offline Backup of your Primary Server Database and refer the follwing sap notes as a preacaution in furute to avoide the same situation again.

[ Note 1016173 - Verifying database and archive log files using RMAN|https://service.sap.com/sap/support/notes/1016173]

[ Note 694155 - Error due to corrupt redo logs|https://service.sap.com/sap/support/notes/694155]

As per the SAP Note[ Note 540463 - FAQ: Consistency Checks + Block Corruptions|https://service.sap.com/sap/support/notes/540463], it is possible to skip corruptions in redologfiles when performing a recovery with the help of SAP Support and their internal SAP Note :825970.

Please contact SAP Support and reference INTERNAL note 825970. 
This note is not public because trying to apply the procedures to continue recovery can cause application inconsistencies that can be fixed only by SAP Support.

Regards,

Bhavik G. Shroff

[sunny_pahuja2]

Hi,

It looks like that archive log that you are applying is corrupt. Try to copy this file again from main server or archive backup. and then try again.

Thanks

Sunny