08/24/08 22:11 Notice: (Read) Queue write recovery started, sqrw_srcseq= msg.mpseq=<xxxxxxx> [sp_ordr(que)/<pid#>]
08/24/08 22:12 Notice: Queue write recovery complete, <xxxx> duplicate messages skipped , <xxxxxxx> bytes total [sp_ordr(que)/<pid#>]
08/24/08 22:12 Warning: A portion of the redo log could not be parsed [sp_ocap/<pid#>]
08/24/08 22:12 Notice: Begin record skip at seqno=<xxxxxxx> offset=-<xxxxxxx> rc=1<xx> [sp_ocap/<pid#>]
capture log errors:
08-08-24 22:11:59.127653 11462 4 Archive filename=<archive log destination path>/LOGxxxx_x.ARC doesn't exist for file dest_id <x>
08-08-24 22:11:59.127714 11462 4 Archive filename=<archive log destination path>/LOGxxxx_x.ARC doesn't exist and retried with
08-08-24 22:11:59.127714 11462 4 dest_id of 1 through <x>
08-08-24 22:11:59.127783 11462 4 stat(<archive log destination path>/LOGxxxx_x.ARC, sbuf) failed
08-08-24 22:11:59.133165 11462 4 Try to find file contains string "xxxxx" under <
08-08-24 22:11:59.134353 11462 4 about to stat <archive log destination path>/LOGxxxx_x.ARC
08-08-24 22:11:59.141007 11462 4 Found file with seqno=xxxxx "<archive log destination path>/LOGxxxx_x.ARC"
08-08-24 22:11:59.141135 11462 4 Found archive log with seqno=xxxxx, thread=x under <archive log destination path>
08-08-24 22:12:21.658840 11462 4 Invalid block number -xxxxxxx requested, should be [x,xxxxxxx]
08-08-24 22:12:21.665297 11462 4 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
08-08-24 22:12:21.665358 11462 4 Log parser error x
This is generally caused when capture cannot read the archive log for the following reason:
1.A corrupt redo/archive log file .
2.Unable to read the archive logs .
If it is determined that the redo/archive log is corrupted then use the following workaround :
sp_ctrl (<source host>:<port#>)> stop capture
sp_ctrl (<source host>:<port#>)> set param SP_OCT_SKIP_BAD_BLOCK 1
sp_ctrl (<source host>:<port#>)> start capture
If capture is unable to read the archive log then please ensure that the archive log is readable. Check that the archive logs are in archive log destination, uncompressed and readable to the splex user.
These messages in the problem description get repeated in the logs several times, identifying one log file and particular offset.