OCAP LOG Indicates the message below:
06-07-07 06:38:26.853576 213420 515 Detected bad log file: "/dev/rredo1_5"
06-07-07 06:38:26.853602 213420 515 Block zero has magic number 0xdb67, should be 0x5a5b5c5d or 0x6a6b6c6d
Event log messages :
07/07/06 06:04 Notice: db_block_size 8192. [sp_ocap(osp)/161730]
07/07/06 06:04 Notice: Oracle version 92 [sp_ocap(osp)/161730]
07/07/06 06:04 Warning: A portion of the redo log could not be parsed [sp_ocap/161730]
07/07/06 06:04 Notice: Begin record skip at seqno=625 offset=0 rc=5 [sp_ocap/161730]
07/07/06 06:04 Warning: A portion of the redo log could not be parsed [sp_ocap/161730]
07/07/06 06:04 Notice: Begin record skip at seqno=265 offset=0 rc=5 [sp_ocap/161730]
07/07/06 06:04 Warning: A portion of the redo log could not be parsed [sp_ocap/161730]
Redo logs on RAW devices on certain platforms have hard coded offsets. These values were hard coded into the product. If the redo logs are on RAW DEVICE and when this offset changes it causes this error.
WORKAROUND:
stop capture
set param SP_OCT_REDO_RAW_OFFSET 0
start capture
SP_OCT_REDO_RAW_OFFSET description:
This parameter tells the Capture process how many bytes to skip when it reads a redo
log or data file that is located on a raw device. These bytes need to be skipped on certain
platforms because they are reserved for the operating system's use. This parameter
should be kept to the default setting of -1, which tells Capture to use the default value
that is programmed for the platform.
Default: -1
Range of valid values: any integer
Takes effect: when Capture is restarted
Additional Information:
Setting the parameter to 0 for AIX means that the default value we used is not true in your case and that no offset should be used when reading the redo logs. The parameter below is a workaround in case the offset has changed.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center