The following Capture error messages are observed in an RDS environment:
Info 2019-01-14 14:54:31.435680 25214 2250745792 Capture exited with code=1, pid = 10563 (capturing from o.SourceSID)
Error 2019-01-14 14:54:30.081303 10563 4262123264 Capture stopped: Internal error encountered; cannot continue (capturing from o.SourceSID)
Error 2019-01-14 14:54:29.935497 10563 4262123264 Capture: Encountered error in Oracle's Query (capturing from o.SourceSID) [module oct]
Notice 2019-01-14 14:54:29.827936 10563 4262123264 Capture: Using archive log /path/db/RTDEPRE_A/arch/redolog-23283-1-990554245.arc (capturing from o.SourceSID) [module oct]
The corresponding entries in Capture log (the *ocap* log) suggest that there is a log parser error with a code of 12 which indicates a problem in Oracle:
ocap 2019-01-14 14:54:29.935198 10563 4262123264 openBfile: failed to open ARCHIVELOG_DIR:redolog-23283-1-990554245.arc, err=22288
ocap 2019-01-14 14:54:29.935269 10563 4262123264 A portion of the redo log could not be parsed
ocap 2019-01-14 14:54:29.935277 10563 4262123264 Begin record skip at seqno=23283 offset=2765840 rc=12
ocap 2019-01-14 14:54:29.935281 10563 4262123264 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
ocap 2019-01-14 14:54:29.935284 10563 4262123264 Log parser error 12
ocap 2019-01-14 14:54:29.935288 10563 4262123264 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
The log parser error 12 indicates some Oracle issue faced by Capture when parsing the logs. In our case the archive logs which the Capture needs to process are not available in the archive destination. Once the logs are made available to Capture and the Capture is restarted, it should be able to process the logs.
