Capture Process is uses too much memory.
At times the symptoms are slightly different, as the following log wrap errors are seen in event_log followed by a core dump even though the archive logs exist and Capture was earlier able to process previous archive logs without any issues:
Notice 2018-05-16 12:26:00.811000 7948 22096 Capture: Using archive log I:\FLASH_RECOVERY_AREA\PROVDB1\ARCHIVELOG\ARC96442_0800980515.001 (capturing from SID1) [module oct]
Warning 2018-05-16 12:26:08.065000 7948 22096 Capture: A portion of the redo log could not be parsed (capturing from SID1) [module oct]
Error 2018-05-16 12:26:24.508000 7468 10096 Capture killed due to SIGQUIT, core file = e:\Program Files\Quest Software\SharePlex\bin/core.4576 was generated at this time in the SharePlex/bin Directory, pid = 4576 (capturing from SID1)
Notice 2018-05-16 12:26:26.271000 17092 22064 Capture: Replicating according to target compatibility of "7.5.0.0" (capturing from SID1) [module utl]
Info 2018-05-16 12:26:26.287000 17092 22064 Capture launched, pid = 17092 (capturing from SID1)
The latest *ocap* log may show a log parser error with code 1 which is typical of memory issues:
ocap 2018-05-16 12:26:08.065000 7948 22096 Log parser error 1
If that problem archive log is skipped by advancing the SHAREPLEX_ACTID table to point to the next archive log, the error may stop happening for a while until Capture core dumps on another archive log. So the issue does not go away by skipping the archive log.
This is due to the large tranx file in Vardir/state .
Workaround 1:
1. If you are running SharePlex version 7.6.3.26 or above ,
Set SP_OCT_OLP_TRACE to 0.
sp_ctrl> set param SP_OCT_OLP_TRACE 0
2. If on SharePlex version below 7.6.3.26 Upgrade to Version 7.6.3.37
Workaround 2:
The above may not help at times. So you will need to carry out the following:
1. Look for the size of the *tranx* file(s) in /vardir/state directory. If they are of the order of tens of MB or hundreds of MB, rename the file(s) to another name. Prior to doing so, you may want to be aware that renaming this file would result in loss of the first open transaction if tracking userid for CDC or using denied userid feature of Capture that ignores transactions performed by a specific user.
2. Restart Capture
