Residual entries in Shareplex internal tables on source database are causing this.
The Shareplex internal tables SHAREPLEX_JOB_STATS and SHAREPLEX_JOBS on source database have details of the jobs run for Compare. The tables are cleaned up once the compare finishes. At times this may not happen. It could be due to any glitch in OS or the database. This results in the confusing output in “job status”. To resolve the issue, clean up the internal tables on source database as:
SQL> delete from "SHAREPLEX_JOB_STATS" where job_id=<id of the residual job>;
SQL> delete from "SHAREPLEX_JOBS" where job_id=<id of the residual job>;