DBMS Server Requirements

When using the Ingres High Availability Option, the Ingres DBMS server is installed and configured as a typical installation, provided that the database-related files are installed on the cluster file system.

At the time of installation, the installer checks if the database, checkpoint, journal, dump, work, and transaction log files are on cluster drives. For a clustered DBMS installation, the database, checkpoint, journal, dump, work, and transaction log files must be on a cluster drive. The II_SYSTEM (Ingres home directory) must be installed on a non-cluster local drive. This configuration should be done while at the Ingres DBMS Configuration screen during installation.

Note: An error message is displayed if the installer finds that the database files are not on a cluster drive.

Using a logical hostname simplifies the installation and configuration of the Ingres DBMS Server in the cluster environment. Conversely, each node can be independently configured.

Set Up a Logical Hostname

To set up a logical hostname, follow these steps:

Run the script iisuscha. Answer yes to "configure a logical hostname" and enter the logical hostname to be used in the HA cluster.
This changes the congfig.dat file by replacing the server name with the logical hostname and sets II_HOSTNAME to the logical hostname.
Use this same logical host name when registering the HA option with the Sun cluster.

Configure Independent Node

If the variable II_HOSTNAME is not to be used for a logical hostname, each host configuration must be set up in the config.dat file. The first host on which Ingres is installed does not need additional setup.

To add additional hostnames that can be used in the cluster, run the script iisuscha. Answer no to "configure a logical hostname." Answer yes to "add a HA host" and enter the additional host to be added. This duplicates the entries in config.dat to match the primary server configuration settings.

Each node then has a different DBMS server configuration, which is helpful in an unbalanced cluster. Each time a change is made to the Ingres configuration, the same change must be completed on each individual node.

Sun Cluster Software Installation Verification

The Sun Cluster packages must be installed and configured on the cluster nodes before installing the Ingres High Availability Option. The installation must be verified by a qualified Sun Cluster Engineer using the commands shown in the following table:

Command	Description
scinstall –pv	Displays the Sun cluster release and version information.
scrgadm –p	Displays the Sun cluster configured resource types, resource groups, and resources.
scstat –p	Displays the status of the Sun cluster components.
scconf –p	Displays the cluster configuration.

Where to Install High Availability Option

The Ingres High Availability Option must be installed on all nodes in the cluster where the Ingres DBMS Server can failover.