-
Title
OlogparGetNextRecord: OlogReadRec return BAD_LOG...retry -
Description
The following errors are seen in the event log
10/17/06 14:18 Warning: A portion of the redo log could not be parsed [sp_ocap/80652]
10/17/06 14:18 Notice: Begin record skip at seqno=39259 offset=0 rc=5 [sp_ocap/80652]
10/17/06 14:18 Notice: OlogparGetNextRecord: OlogReadRec return BAD_LOG...retry (0 of 5). [sp_ocap/80652] -
Cause
Redo logs were on raw file system
-
Resolution
sp_ctrl>stop capture
sp_ctrl>set param SP_OCT_REDO_RAW_OFFSET 0
sp_ctrl>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.
Setting the parameter to 0 for AIX means that the default value used is not true and that no offset should be used when reading the redo logs. The parameter below is a workaround in case the offset has changed. -
Additional Information
In later versions like SharePlex 9.1 and up, the event log messages are modified as shown below: Info 2018-03-27 16:51:44.604251 29813 643084816 Capture exited with code=1, pid = 29814 (capturing from o.ORA11GR2) Error 2018-03-27 16:51:44.601373 29814 1114429760 Capture: [SP-OCT01001] Unable to find archivelog with sequence#: 77041 (thread: 1).SharePlex was unable to locate the redo/archive log for sequence 77041 in the database location or under the directory defined by SP_OCT_ARCH_LOC parameter. Restore this archivelog to archive location if missing or set the file's location using SP_OCT_ARCH_LOC. Make sure it is not compressed then restart capture. See 'http://advice.shareplex.com/SP-OCT01001' for additional advice and support. (capturing from o.ORA11GR2) [module oct] Likewise, the output of “status” issued from source sp_ctrl gives out a clearer hint (reason) for Capture error by printing the message “Stopped: missing archive log” as below: sp_ctrl (alvsupl14:9111)> status Brief Status for alvsupl14 Process State PID Running Since --------------- ------------------------------ -------- -------------------- Cop Running 29813 27-Mar-18 16:51:30 Capture Stopped: missing archive log Read Running 29816 27-Mar-18 16:51:30 Export Running 29815 27-Mar-18 16:51:30 Cmd & Ctrl Running 29861 27-Mar-18 16:51:34