The Capture appears to be running normally when issuing "show capture detail" EXCEPT that you see "Capture current redo log : 0". Moreover, when running transactions on replicating tables or issuing flush does not generate any message in Capture queue which has 0 messages and 0 backlog as seen in qstatus. The "Capture state" is "Waiting" at all times.
The symptoms appear somewhat similar to the ones where Capture encounters a log wrap, which is not the case in our situation. In case of log wrap the "Capture state" is always "Initializing" and not "Waiting". The Shareplex internal table Shareplex_actid shows that SEQNO contains the latest log sequence # which is same as "Oracle current redo log" from "show capture detail" so there is no log wrap here. The only thing puzzling is that the OFFSET is 0.
Capture MAY be stuck at certain log offset while trying to process the online redo log.
Whatever the cause, it is worth trying a harmless workaround which worked in one scenario. One may want to stop Capture and force a log switch on source database by "alter system switch logfile". This has resolved at least one such occurance of the problem described whereby Capture started processing from the archived log after restart.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center