Initial config file activation with "live" option results in double posting on target.
Running initial activation with "live" option can result in double posting on target because no reconcile is run on target.
At times the default activation does not succeed due to no downtime available on source database as the activation may fail with ORA-00054. As a workaround if activation is run with "live" option when there is no downtime on source database and there is no reconcile on the target, then it is imperative that the following is done to ensure that there are no consequent out of sync.
Issue "show sync" on target sp_ctrl from time to time, and for any tables appearing as out of sync, either sync such tables using compare or other means, or make sure that the tables have unique constraint enabled on target.
In general the "live" option is used with activation when activating for the first time AND synchronizing the target at the same time. When doing an initial activation with "live" option, it is recommended to run a reconcile on the Post queue on the corresponding target to remove all messages from queue up to a certain log sequence # that have otherwise been applied to the target via hotbackup so as to avoid double posting since users were allowed on source system while the activation was in progress and Shareplex gathered some of those transactions in its queues.