This content has been marked as final. Show 7 replies
bcm@bcm-laptop:~$ oerr ora 353 00353, 00000, "log corruption near block %s change %s time %s" // *Cause: Some type of redo log corruption has been discovered. This error // describes the location of the corruption. Accompanying errors // describe the type of corruption. // *Action: Do recovery with a good version of the log or do incomplete // recovery up to the indicated change or time. bcm@bcm-laptop:~$ oerr ora 354 00354, 00000, "corrupt redo log block header" // *Cause: The block header on the redo block indicated by the accompanying // error, is not reasonable. // *Action: Do recovery with a good version of the log or do time based // recovery up to the indicated time. If this happens when archiving, // archiving of the problem log can be skipped by clearing the log // with the UNARCHIVED option. This must be followed by a backup of // every datafile to insure recoverability of the database.
Is this archivelog from 04/23/2012 ?
Have preceding logs been applied successfully ?1 person found this helpful
block 32768A nice, round, figure ! What is the actual size of the archivelog file, in bytes ? How does it compare to other archivelogs ? Was it transferred/restored to/from tape / via alternate disk / ftp ? Is it likely that it got corrupted during such transfer ?
Hemant K Chitale
1). Yes, the previous logs were applied succesfully.
2). Yes, this is the log from 4/23/2012.
Was the archivelog restored from tape to disk ? If so, can you try restoring it again ?1 person found this helpful
If the file is corrupt, you have no options. You CANNOT recover beyond the corruption.
You should be logging an SR with Oracle Support for advice.
Hemant K Chitale
Yes I know what you mean.
I will probably just offline the file and see how the app performs.
thanks for your help.
Dev team just re-coded to bypass the unrecoverable datafile...