HP Enterprise Cluster Master Toolkit User Guide (5900-2131, December 2011)

NOTE: If using this configuration, the 'PFILE' parameter in the haoracle.conf configuration file
should be set to the specific pfile on a given host. For example, the PFILE in haoracle.conf on node1
should be set to /ORACLE_TEST0/dbs/initORACLE_TEST0.ora.node1.
Error Handling
On startup, the Oracle shell script will check for the existence of the init${SID_NAME}.ora or
spfile${SID_NAME}.ora file in the shared ${ORACLE_HOME}/dbs directory. If this file does not
exist, the database cannot be started on any node until the situation is corrected. The action by
the Oracle shell script is to halt the package on that node and try it on the standby node.
Network Configuration
This document does not cover detailed instructions on how to configure the Oracle network products
for a Serviceguard cluster. This section contains a few basic suggestions on how to configure a
TCP/IP listener for a clustered environment. Consult Oracle documentation for a detailed description
on how to set up the networking products.
/etc/hosts
If you want to access your Oracle instance through a 'hostname', you need to add entries for the
relocatable IP-addresses to your /etc/hosts file (or nameserver). This will allow you to connect to
your database using a logical name with a telnet or rlogin. Thus, /etc/hosts would contain names
of services (database servers) in addition to real physical hostnames. From Serviceguard's point
of view, these are relocatable hostnames:
EXAMPLE:
Assume a Serviceguard package for the Oracle instance ORACLE_TEST0, is assigned the IP address
192.10.10.1
Add the following entry to your hosts files:
192.10.10.1 ORACLE_TEST0
The 'ORACLE_TEST0' instance should now be reachable using the name 'ORACLE_TEST0' regardless
of the node on which it is running.
Listener:
Set up a listener process for each Oracle instance that executes on a Serviceguard cluster, making
sure that the listener can move with the instance to another node. Effectively, ensure the listener
configured to a specific Oracle instance is assigned to a unique port.
In the current release you can configure ONE listener to be monitored by the toolkit.
However you can configure multiple listeners for the Oracle instance outside the Serviceguard
environment to provide more HA to the listener.
NOTE: It is recommended to use encrypted passwords for password protected listeners.
The password specified for a listener in the parameter PASSWORDS_<listener_name> in the
file LISTENER.ORA, must be copied to the LISTENER_PASS parameter in the haoracle.conf file.
If there are multiple passwords configured for a single listener, you can use any one of them for
the LISTENER_PASS parameter in the haoracle.conf.
In particular, for Oracle 10g and 11g, there is a new listener feature called "Local OS
Authentication" activated by default, which permits the user who started it to administer the listener
without requiring password authentication. To disable this feature, you need to specify
"LOCAL_OS_AUTHENTICATION_listener_name = OFF" in LISTENER.ORA. Please note, in this
situation, due to a change in Oracle 10g, you will have to specify the plain text password for the
LISTENER_PASS parameter in haoracle.conf (and not the encrypted password found in
LISTENER.ORA).
Error Handling 51