If one of our customer machines is restarted the Sybase SA 18.104.22.16813 service doesn't bind to the udp port (no sb option on the command line). We checked this with „netstat –aon | findstr 2638“.
When only the service is restarted it listens on this port.
There is nothing in the server log indicating a problem or cause.
The customer has a backup server with live log and wants to switch to this server if the primary machine fails, so specifying the server tcpip address on the client side requires changing quite a lot of settings back and forth. And using a dns address adds another point of failure.
It seems to be a timing issue, perhaps adding a dependency or setting the service to delayed start could remedy the problem (Testing this is not easy as the system is in use 24/7 and it doesn't happen on the backup system), but is there a way to further diagnose this problem (apart from adding -z)?
30 Jul '13, 04:42