Service Guard with Oracle Question.

[Rpger Tavener]

We have a 2 node Service Guard Cluster. We want to run one Oracle package, pkgA on Server A, and the other package, PkgB on Server B. with the ability to fail over either package to either server. What's the best way to configure the listener and tnsnames for Oracle?

Thank you..

[Janet Abel]

I have a similar setup. Both servers hold the Oracle binaries, including the tnsnames.ora and the listener.ora files. They both point to the package names/IPs and are not part of a package. Oracle is, however, started by the cluster.

Hope that helps,
Janet

[Charles McCary]

In addition, you can create a dbstart_pkg and dbshut_pkg that takes SID as a parameter, so that you can start whatever SID is associated with a package from within the package control script. Example in my package control script:

su - oracle -c "/opt/ORACLE/product/8.1.7/bin/dbshut_pkg SID_1"

[Carsten Krege]

In case you didn't know: There exists a product "Enterprise Cluster Master Toolkit" which contains a package control script for integration of Oracle into SG.
See
http://docs.hp.com/hpux/pdf/B5139-90036.pdf

Carsten

[Bruno DESQUESNE]

A merged tnsnames.ora file should be shared by all hosts within the cluster and probably outside as well.

For listener.ora, there a simple solution.

=> use named listener. Actually, you probably use a default, un-named listener, and you start it with "lsnrctl start".

You can define as many named listener as you need in the same file. for example :

setA = (ADDRESS_LIST = (ADDRESS = (HOST...
SID_LIST_setA =
(SID_LIST = (SID_DESC ...

Then you can start a listener for this set of SIDs with the command "lsnrctl start setA". Of course, you will also define a setB listener in the same listener.ora.

Easy, isn't it ?

Regards