Resource Registration

Once the data service is installed on all nodes in the cluster, the resource must be registered. All administration must be done as a super user, normally the "root" user.

During the installation of the Ingres High Availability Option, the resource type (Ingres.ingres_server) for the data service is automatically registered.

Register the Ingres High Availability Option Resource

If the resource type is not registered, use the following command to register it:

# scrgadm –a –t Ingres.ingres_server –f /opt/Ingres/IngresSCAgent/etc/Ingres.ingres_server

where:

• -t

  Specifies the predefined resource type name for the Ingres.ingres_server DBMS High Availability Option

• -f

  Specifies the pathname of the resource type registration file and is required if the file is not in the well-known directory(usually /usr/cluster/lib/rgm/rtreg).

Configure Ingres High Availability Option

After the Ingres High Availability Option package has been installed, perform these steps:

1. Become the super user on a cluster node by using the following command:

   % su

2. Create a failover resource group to hold the network and application resources by using the following command:

   # scrgadm –a –g <resource-group> [-h nodelist]

   where:

   • -a

     Adds the data service resource type.

   • -g

     Specifies the name of the resource group. This name can be of your choice but must be unique for the resource groups within the cluster.

   • -h

     Specifies an optional comma-separated list of physical node names or IDs that identify potential masters. The order here determines the order in which the nodes are considered as primary during failover

3. Create a Logical Hostname resource in the group using the following command:

   # scrgadm –a –L –g <resource-group> -l <logical-hostname>

   where:

   • -a

     Adds the data service resource type.

   • -L

     Adds a logical Hostname resource type.

   • -g

     Specifies the name of the resource group. This name can be your choice but must be unique for the resource groups with the cluster.

   • -I

     Specifies a network resource. The network resource is the logical hostname or shared IP address that clients use to access Ingres for Sun Cluster HA

4. Create an Ingres resource in the group by using the following Sun Cluster administration command:

   # scrgadm –a –j <resource-name> -g <resource-group> \

   -t Ingres.ingres_server \

   -x II_SYSTEM=<$II_SYSTEM> \

   –x II_OWNER=<ingres> \

   –x II_HOSTNAME=<logical_host> \

   [-x User=<user> -x Pword=<password> \

   -x Database=<database>] \

   [-x EnvFile=<environmentfile>] \

   [-x II_SCHA_TRACE=<level> –x II_SCHA_LOG=<filename>]

   where:

   • -a

     Adds the data service resource type.

   • -j

     Specifies the name of the resource to be added.

   • -g

     Specifies the name of the resource group. This name can be your choice but must be unique for resource groups with the cluster.

   • -t

     Specifies the predefined resource type name for the Ingres.ingres_server DBMS High Availability Option.

   • -x II_SYSTEM

     Sets the path for the Ingres system directory.

   • -x II_OWNER

     Sets the Ingres owner.

   • -x II_HOSTNAME

     Sets the logical host name.

   • -x User (Optional)

     Sets the users for secondary monitoring.

   • -x Pword (Optional)

     Sets the password for secondary monitoring.

   • -x Database (Optional)

     Sets the database for secondary monitoring.

   • -x EnvFile (Optional)

     Sets the file used to load additional user specified environment variables.

   • -x II_SCHA_TRACE (Optional)

     Sets the trace level for debugging. Valid levels are 0 for no tracing and 1-9 for debugging information.

   • -x II_SCHA_LOG (Optional)

     Sets the filename for the trace output.

     Notes:

   • When a fault occurs in the Ingres services resource that causes a restart, the whole resource group is restarted. Other resources in the resource group are restarted, even if they did not have a fault. To prevent other resources from being restarted along with the Ingres services, put them in a separate resource group.
   • To override the default values, you can set additional extension properties for the Ingres High Availability Option.
5. Bring the resource group online by using the following command:

   # scrgadm –Z -g <resource-group>

   • -Z

     Enables all resources of the specified resource group.

   • -g

     Specifies the name of the resource group. This name can be your choice but must be unique for resource groups within the cluster

6. Verify that the Ingres High Availability Option resource has come online on one node of the cluster by using the following command:

   # scstat -g