Launching sp_cop results in the following error:
# ./sp_cop -usha60 &
[1] 8099
#
********************************************
* SharePlex for Oracle Startup
* Version: 6.1.1.10
* VarDir : /u01/sha60/var
* Port : 500
********************************************
udp server bind - exiting
[1] + Done(1) ./sp_cop -usha60 &
#
The env | sort output shows that the port # specified is 500:
# env|sort
.
.
SP_COP_TPORT=500
SP_COP_UPORT=500
Moreover, it is also determined by "netstat -an" command that no other Shareplex instance or application is using the designated port:
# netstat -an | grep -i listen | grep 500
#
There are restrictions on what port numbers can be used by user applications.
Though port numbers can range from 0 to 65535, from 0 to 1023 they are meant to be used by privileged services and are identified as well-known ports. This reservation is made as per the guidelines of Internet Assigned Numbers Authority. So it is not possible for ordinary applications to use such ports (in the above example Shareplex was started on port number 500). Applications like Shareplex need to use port numbers from 1024 and up (the upper limit is 65535). To enable the Shareplex to start, just change the port number to a valid value by changing the environment and restart sp_cop. Make sure to correct the port number on the corresponding target as well if using another server for target.
