Does the script sp_eventmon catch capture errors about log wrap detected or can't parse redo log (4242360)

Does the script sp_eventmon catch capture errors about log wrap detected or can't parse redo log

Does the script sp_eventmon located in the proddir/util directory catch errors related to capture not being able to parse the redo log or where a log wrap LOG_WRAP detected

capture can not read a redo log

Yes, the sp_eventmon does catch cases where the capture process is reporting errors like LOG_WRAP detected or "A portion of the redo log could not be parsed'

The following errors were reported in the event_log and sp_eventmon caught the errors and sent an email to the user.
Error 2012-08-20 23:06:56.012709 26421 2 Capture: LOG_WRAP detected 5 37792272 0, ...exiting...(../src/olog/olog.c:2585) (capturing from stock) [module oct]
Notice 2012-08-20 23:06:56.008807 26421 2 Capture: Begin record skip at seqno=5 offset=37792272 rc=6 (capturing from stock) [module oct]
Warning 2012-08-20 23:06:56.005413 26421 2 Capture: A portion of the redo log could not be parsed (capturing from stock) [module oct]
Notice 2012-08-20 23:06:50.292566 26421 2 Capture: Begin record skip at seqno=5 offset=37792272 rc=6 (capturing from stock) [module oct]
Warning 2012-08-20 23:06:50.288121 26421 2 Capture: A portion of the redo log could not be parsed (capturing from stock) [module oct]

The mail sent is as follows

From korcl@fulqasu02 Mon Aug 20 23:09:24 2012
Date: Mon, 20 Aug 2012 23:09:24 -0700 (PDT)
From: kens oracle user <korcl@fulqasu02>
Message-Id: <201208210609.q7L69OK2026453@fulqasu02>
To: korcl@fulqasu02
Subject: Errors found in SharePlex log!
Content-Length: 1543

The following errors were found in the SharePlex event log for instance: sp_cop -u8606 on host fulqasu02
Line# 105: SharePlex Instance:sp_cop -u8606: Error 2012-08-20 23:07:23.894076 26429 2 Capture: LOG_WRAP detected 5 37792272 0, start retry (../src/olog/olog.c:2579) (capturing from stock) [module oct]

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