Capture stuck and gets ORA-1403 when oracle is archiving the redo log shareplex is reading or querying dictionary for log information. The dictionary information has not been updated by oracle when shareplex is querying, and capture does not retry and also does not go check the archive location from SP_OCT_ARCH_LOC.
GetLogMemberStatus for /u02/oradata/ida/redom1_13.log returned 1403
Starting from SharePlex Version 7.0, there is new parameter SP_OCT_CK_LOC_FIRST introduced.
By setting SP_OCT_CK_LOC_FIRST to 1 and bounce the capture, capture process will always first search for an archived redo log in the location specified by SP_OCT_ARCH_LOC. If SP_OCT_ARCH_LOC is an empty string, Capture will first search in the Archive Log Destination as configured in Oracle.
Issue fixed in version 5.3.3. The latest version of Shareplex for Oracle can be downloaded at: https://support.quest.com/shareplex/download-new-releases