The example in this section shows how you might set up the resource types, resources, and resource groups for an Oracle application that has been instrumented to be a highly available failover data service.
The main difference between this example and an example of a scalable data service is that, in addition to the failover resource group that contains the network resources, a scalable data service requires a separate resource group (called a scalable resource group) for the application resources.
The Oracle application has two components, a server and a listener. Sun supplies the Sun Cluster HA for Oracle data service, and therefore these components have already been mapped into Sun Cluster resource types. Both of these resource types are associated with resources and resource groups.
Because this example is a failover data service, the example uses logical hostname network resources, which are the IP addresses that fail over from a primary node to a secondary node. Place the logical hostname resources into a failover resource group, and then place the Oracle server resources and listener resources into the same resource group. This ordering enables all of the resources to fail over as a group.
For Sun Cluster HA for Oracle run to on the cluster, you must define the following objects.
LogicalHostname resource type – This resource type is built in, and therefore you do not need to explicitly register the resource type.
Oracle resource types – Sun Cluster HA for Oracle defines two Oracle resource types—a database server and a listener.
Logical hostname resources – These resources host the IP addresses that fail over in a node failure.
Oracle resources – You must specify two resource instances for Sun Cluster HA for Oracle—a server and a listener.
Failover resource group – This container is composed of the Oracle server and listener and logical hostname resources that will fail over as a group.