Return
-
Title
How to kill or cancel a compare job? -
Description
When a compare is issued on Source it spawns a process named sp_desvr on Source and a corresponding sp_declt process on Target.At times there is a need to cancel the compare processes due to a number of reasons.A "compare config" that takes a lot of time if the config file has too many and/or large tables and the server does not have the resources available to allow such compares to run.Sometimes the queues may be heavily backlogged and it may be futile to wait for the compare to finish as it will eventually time out.In all these situations it is better to kill the compare processes on Source and Target. -
Resolution
The following methods will cancel or clear the compare processes on Source and Target:1. The simplest way to kill running compare processes is to identify the Unix process ID (PID) of compare on Source and issue the command "compare cancel <PID>" on Source sp_ctrl.One can identify the PID by issuing "show compare" on Source sp_ctrl.The "compare cancel" will also get rid of the compare process on the Target SharePlex instance.2. The compare process on Source can be killed at OS level but has to be done as root.The corresponding process on Target will also get cleared.If, for any reason, the Target process does stop, you may want to issue "kill" on it as well.3. Shutting down and restarting SharePlex on Source and Target also results in the killing of compare processes.