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 out the compare processes due to a number of reasons. One may have issued a "compare config" that takes a lot of time if the config file has too many and/or too large tables and one does not have the resources available at the server to allow such compare to run. Sometimes the queues may be heavily backlogged and it may be futile to wait for the compare to finish since it will eventually time out. In all these situations one is better off killing or getting rid of the compare processes on source and target
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 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 on its own. If, for any reason the target process does not go away on its own, one may want to issue "kill" on it as well.
3. Shutting down and restarting Shareplex on respective instance also results in the killing of these processes.