Listener configuration with service guard

Question

Hello
We plan to work here with HP service guard on a cluster (oracle version 7.3 and hp UX 11). We want to distribute databases accross the nodes of the cluster and let them protected by service guard.
Here's my main question.
I have a cluster with two nodes (A and B) and service guard but without OPS. Instance InstA is running on A protected by service guard. Instance InstB is running on B protected by service guard. I I use TNSNAMES.ora with the adresses of the packages guarding my instances.
If, after a problem, service guard switches for example instA from A to B, what will happen with the listener ?
Will we have now two listeners running on node B ?
Or
will we have just one listener ?
In this later case, the listener running on B should be ready to accept connexions to instB but also to instA when instA is moved to B.
Any hint is welcome.

Answer 1

If anyone else comes across this problem and they are trying to get SSL connections to the oracle database working but it is failing with ‘cannot hand off connection’, then in my experience the problem is most likely to be because of a firewall configuration.
It turns out that in a non-SSL environment, Oracle can seamlessly hand off the connection to another port without dropping the connection on it’s own side, and therefore the ports open on the the firewall can remain constrained to the initial connection port (usually 1521). However, in an SSL environment Oracle needs to hand off the connection to a different port number, and because of the SSL handshake required, that port not only needs to be open on the firewall, Oracle needs to be told to use that port number explicitly which is done using the DISPATCHERS setting.
For example, for one dispatcher, that could be run on 24841 while the listener is run on 2484. In this case, set up the firewall with ports 2484 and 24841 open. Set up the listener for TCPS on port 2484. Then to set up the dispatcher, connect as sys (sysdba) to oracle and run
alter system set dispatchers=‘(ADDRESS=(PROTOCOL=TCPS)(HOST=myhost.domain.tld)(PORT=24841))(INDEX=1)’ scope=both;
The index=1 makes sure that you add this dispatcher in a new slot without clobbering your existing TCP listener (which will be in index=0). You will obviously
Good luck. TCPS is a pain in the posterior to get working.