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.
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 ?