When capture is running on non-ASM RAC, capture may be slow or fall behind Oracle a few online logs, but there are no specific errors in capture log
Or
When capture is running on ASM RAC but archivelog is on non-ASM location, capture may hang on reading archivelogs.
Event_log will show internal query error with ORA-22287 if database is on 12c (but no error on 11g)
Error 2018-10-16 18:19:35.748221 50331942 1286 Capture: Encountered error in Oracle's Query (capturing from o.SPLEXIFDB) [module oct]
Error 2018-10-16 18:19:35.753855 50331942 1286 Capture: Encountered error in Oracle's Query (capturing from o.SPLEXIFDB) [module oct]
Error 2018-10-16 18:19:35.759792 50331942 1286 Capture: Encountered error in Oracle's Query (capturing from o.SPLEXIFDB) [module oct]
Error 2018-10-16 18:19:35.764903 50331942 1286 Capture: Encountered error in Oracle's Query (capturing from o.SPLEXIFDB) [module oct]
And ocap log when turning on SP_OCT_OLOG_DEBUG 0x1ff, SP_OCT_FIO_DEBUG 0x1ff and SP_OCT_BIO_DEBUG 0x1ff, shows below error
ocap 2018-10-16 18:19:35.744803 50331942 1286 readBfile: OCILobRead2 failed: err=22287
ocap 2018-10-16 18:19:35.744843 50331942 1286 FioOciRead:: failed to read data from BFile: rc=12
ocap 2018-10-16 18:19:35.744858 50331942 1286 ReadChunk: readBfile failed: rc=12
ocap 2018-10-16 18:19:35.744873 50331942 1286 A portion of the redo log could not be parsed
ocap 2018-10-16 18:19:35.744888 50331942 1286 Begin record skip at seqno=15299 offset=281931408 rc=12
ocap 2018-10-16 18:19:35.744902 50331942 1286 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
ocap 2018-10-16 18:19:35.744916 50331942 1286 Log parser error 12
ocap 2018-10-16 18:19:35.744930 50331942 1286 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
ocap 2018-10-16 18:19:35.744945 50331942 1286 *************************************
ocap 2018-10-16 18:19:35.744959 50331942 1286 Dump of log parser information
In both scenarios, run query against dba_directories on the source DB to confirm if there are any directory names returned like ‘REDOLOG_DIR%’ which confirms the issue.
select directory_name from dba_directories where directory_name like 'REDOLOG_DIR%';
Product Defect affecting 9.1.x and 9.2.0
STATUS:
The issue is fixed in 9.2.1
