It is recommended to use different ports when running more than one sp_cop on a physical host.
In one particular consolidated environment, source and target shareplex instances are configured using separate logical hostnames on the same physical host. Each SharePlex instance binds to a distinct $SP_SYS_HOST_NAME IP address within the same host rather than using different ports. This solution outlines a workaround to not bind UDP to the localhost.
netstat -an |grep -i <port NUMBER>
udp 0 0 10.10.10.10:2100 0.0.0.0:*
tcp 0 0 10.10.10.10:2100 0.0.0.0:* LISTEN
Starting with version 9.1.3, SharePlex includes improvements in security around UDP communication.
Shareplex now meets a stricter security standard by binding the UDP port to localhost.
WORKAROUND
If you do not want UDP to bind to localhost, apply the following workaround.
1. The recommendation is to set SP_COP_UPORT to a different port on source or target.
2. Use a unique UDP port for each shareplex instance running on a physical server.
EXAMPLE.
Source:
SP_SYS_HOST_NAME=source.
SP_COPT_TPORT=2100.
SP_COP_UPORT=2100.
Target:
SP_SYS_HOST_NAME=target.
SP_COPT_TPORT=2100.
SP_COP_UPORT=2200.
STATUS
Waiting for fix in a future release of SharePlex for Oracle.
