I have seen lower sequence logs complete archival after higher sequence logs. Usually coinciding with some sort of I/O bottleneck where multiple archiver processes are competing for limited bandwidth. I have not seen any sort of log corruption as a result of that process though. If the logs are identical on both the primary and standby, (use diff to verify) I would suggest doing another backup. Because if that archived log is corrupt it will put a keebosh on your restore. If you used rman for your backup, I am pretty sure you can verify that your archive logs will restore properly. Of course if you can't recover your standby it will have to be resynched as well.
Steve -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Steve McClure INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
