Capture is not processing any changes when earlier the system clock was incorrectly set an hour ahead even though the clock was subsequently reset back to the correct time. (4331062)

During a source server crash and subsequent starting of source server, system clock was inadvertently set an hour ahead of the prevailing time. After realizing the mistake, the clock was reset back to the correct time. After this the SharePlex was showing Capture state as "processing" but in reality it was not processing anything.  As you will note from the output below, the system time (19:41:06) was behind the timestamp of the last redo record processed (20:06:48) due to the clock set wrongly earlier:

sp_ctrl> show capture detail

Host: hostname        System time: 20-Nov-17 19:41:06

                           Operations

Source     Status            Captured Since

---------- --------------- ---------- ------------------

o.YES      Running               1551 20-Nov-17 19:16:04

   Oracle current redo log          : 100509

   Capture current redo log         : 100503

   Capture log offset               : 3761499152

   Last redo record processed:

        Operation on "OWNER"."TABLE_NAME" at 11/20/17 20:06:48

   Capture state                    : Processing

   Activation id                    : 36

   Error count                      : 0

   Operations captured              : 1551

   Transactions captured            : 322

   Concurrent sessions              : 1

   HWM concurrent sessions          : 4

   Checkpoints performed            : 0

   Total operations processed       : 1794

   Total transactions completed     : 329

   Total Kbytes read                : 0

   Redo records in progress         : 281

   Redo records processed           : 36544

   Redo records ignored             : 34699

   Redo records - last HRID         : ABB49CAArAAF434AAu