HP Serviceguard Toolkit for Oracle Data Guard manual Node-specific Configuration, Error Handling

$ cmmodpkg -e -n <node1> -n <node2> ORACLE_TEST0 $ cmmodpkg -e ORACLE_TEST0

If necessary, consult the manual Managing ServiceGuard manual available at http://www.hp.com/ go/hpux-serviceguard-docs —>HP Serviceguard for information on managing packages.

Node-specific Configuration

On many clusters, the standby nodes might be lower end systems than the primary node. An SMP machine might be backed up by a uniprocessor, or a machine with a large main memory may be backed up by a node with less memory.

From Oracle's point of view, we must make sure that any packaged instance can run on any specified node in the corresponding package configuration. The Oracle shell script handles this situation in the following way:

If node-specific tuning is required, set up a node-specific 'init.ora' file for each node in

${ORACLE_HOME}/dbs. This file should be named 'init${SID_NAME}.ora', and there should be one such file for each host.

For Example:

/ORACLE_TEST0/dbs/initORACLE_TEST0.ora.host1 /ORACLE_TEST0/dbs/initORACLE_TEST0.ora.host2

When the Oracle shell script executes the Oracle commands, they will check for the existence of such a file before starting the Oracle database. If no host specific init file exists, a 'global' init${SID_NAME}.ora file is assumed.

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

50 Using the Oracle Toolkit in an HP Serviceguard Cluster