Unanswered: client hangs when the link to server is down
I have a procedure that connects to 13 different oracle databases one by one on a WAN. It both reads and writes to the remote databases n distributed transactions.
The problem is - if a listener on one of the remote servers is down or if a WAN link is down, the procedure just hangs. Shouldn't SQLNet detect the situation and timeout so that the procedure can move on to the next database server?
I'd appreciate any help. I'm using Oracle 7.3.4 and 7.1.6 on the various servers.