Compare fails with "Warning 79 calling connect (de_sock_connectToServerWithIP,LNNN) (IP: <valu (4298242)

When running compare on a very large table, the following errors appear in sp_declt log:

.
.
.
000: DEBUG: using abc.efg.com host name from env. variable, SP_SYS_HOST_NAME (de_sock_create_client_socket,LNNN:de_sock_getHostNameIp,LNNNN)
000: Warning 79 calling connect (de_sock_connectToServerWithIP,LNNN) (IP: <value>, Port: 1234) failed.
000: Warning 79: Connection refused
000: eintr_count = 0, eisconn_count = 0, ealready_count = 0
000: The warnings may due to either "compare cancel"command or network errors.
000: IP mapping failed (de_sock_connectToServerUseIpMapping,LNNN)

(where NNNN denotes any integer)

It could be a number of reasons.

1. There is a lot of activity on the system or the queues are backlogged.

2. The table to be compared is very large.

3. The port used by compare is in use by another application.

4. The port used by compare is closed by a firewall.

5. The site may be experiencing network issues.

6. There is another issue with the port that was selected by compare.

1. Make sure to run compare when there is a least amount of activity on the source system and/or the queues are not unduly backlogged.

2. Try running compare by limiting the # of rows to be compared by using the "where" clause if feasible.

3. See if the random port selected by compare is used by any other application or is hung (see SOL41015 for details), and if so, use another port by specifying the port option in compare. See SOL6834 for further details.

4. See if the firewall is indeed the cause of this issue. This can be done by determining if Shareplex is operating within firewall environment. If so, one may want to open a port (also termed as punching a hole through firewall) and run compare with "port" option. See SOL6834 for further details. By default Shareplex picks up a port at random when running compare and this port is listed in the *desvr* and *declt* logs (the source and target compare logs respectively).

5. If there is any other network issue that may be causing the error, one can run socket test on the port randomly selected by Shareplex to see if it is successful. If not, then some network issue is causing compare to report the error. For running socket_test, see SOL12333 for details. If there is a network error, then the issue needs to be referred to network administrators.

6. Find out if there is another Shareplex instance running on same source/target server combination, shut it down and run compare with port option by specifying the port # used by this second Shareplex instance.  Since the second Shareplex instance was running fine, compare should be able to run on its port #.  If so, then there is a problem with the random port selected by compare when it was run earlier and it needs to be addressed.