Administering Oracle RAC databases from Sun Cluster involves using Sun Cluster administration tools to modify the states of Sun Cluster resources for Oracle RAC database instances. For information about how to create these resources, see Configuring Resources for Oracle RAC Database Instances.
The software architectures of Oracle 9i, Oracle 10g R1, and Oracle 10g R2 are different. As a result of these differences, the resources for Oracle RAC database instances that Sun Cluster requires depend on the version of Oracle that you are using. Consequently, the administration of Oracle RAC databases from Sun Cluster also depends on the version of Oracle that you are using.
If you are using Oracle 10g R1, you cannot administer Oracle RAC databases from Sun Cluster. Instead, use Oracle CRS utilities to start and shut down Oracle RAC database instances.
On Solaris 9 systems, there is a single name space for all resource groups and resources. On Solaris 10 systems, each cluster such as the global cluster or a specific zone cluster, constitutes an independent name space for resource groups and resources. Thus, there is no name collision between names in this different name spaces. The administrator registers resource types independently for each cluster.
The administrator can administer the resource groups and resources belonging to the global cluster only from the global-cluster voting node. The administrator can administer the resource groups and resources belonging to a zone cluster from that zone cluster. The administrator in the global-cluster voting node can also administer resource groups and resources in a zone cluster by using the -Z option to specify the zone cluster. The administrator can set up inter-cluster resource dependencies or affinities only from the global-cluster voting node. The examples in the following sections typically explain the situations when the command is issued in the cluster where the resource group or resource resides.
The effects of changes to the states of Sun Cluster resources on Oracle database components are explained in the subsections that follow.
In Oracle 10g, the Oracle CRS manage the startup and shutdown of Oracle database instances, listeners, and other components that are configured in the CRS. Oracle CRS are a mandatory component of Oracle 10g. CRS also monitor components that are started by CRS and, if failures are detected, perform actions to recover from failures.
Because Oracle CRS manage the startup and shutdown of Oracle database components, these components cannot be stopped and started exclusively under the control of the Sun Cluster RGM. Instead, Oracle CRS and the Sun Cluster RGM interoperate so that when Oracle RAC database instances are started and stopped by Oracle CRS, the state of the database instances is propagated to Sun Cluster resources.
Table 4–2 Propagation of State Changes Between Sun Cluster Resources and Oracle CRS Resources
Trigger |
Initial State |
Resulting State |
||
---|---|---|---|---|
Sun Cluster Resource |
Oracle CRS Resource |
Sun Cluster Resource |
Oracle CRS Resource |
|
Sun Cluster command to take offline a resource |
Enabled and online |
Enabled and online |
Enabled and offline |
Enabled and offline |
Oracle CRS command to stop a resource |
Enabled and online |
Enabled and online |
Enabled and offline |
Enabled and offline |
Sun Cluster command to bring online a resource |
Enabled and offline |
Enabled and offline |
Enabled and online |
Enabled and online |
Oracle CRS command to start a resource |
Enabled and offline |
Enabled and offline |
Enabled and online |
Enabled and online |
Sun Cluster command to disable a resource |
Enabled and online |
Enabled and online |
Disabled and offline |
Disabled and offline |
Oracle CRS command to disable a resource |
Enabled and online |
Enabled and online |
Enabled and online |
Disabled and online |
Oracle SQLPLUS command to shut down the database |
Enabled and online |
Enabled and online |
Enabled and offline |
Enabled and offline |
Sun Cluster command to enable a resource |
Disabled and offline |
Disabled and offline |
Enabled and online or offline |
Enabled and online or offline |
Oracle CRS command to enable a resource |
Disabled and offline |
Disabled and offline |
Disabled and offline |
Enabled and offline |
The names of the states of Sun Cluster resources and Oracle CRS resources are identical. However, the meaning of each state name is different for Sun Cluster resources and Oracle CRS resources. For more information, see the following table.
Table 4–3 Comparisons of States for Sun Cluster Resources and Oracle CRS Resources
State |
Meaning for Sun Cluster Resources |
Meaning for Oracle CRS Resources |
---|---|---|
Enabled |
The resource is available to the Sun Cluster RGM for automatic startup, failover, or restart. A resource that is enabled can also be in either the online state or the offline state. |
The resource is available to run under Oracle CRS for automatic startup, failover, or restart. A resource that is enabled can also be in either the online state or the offline state. |
Disabled |
The resource is unavailable to the Sun Cluster RGM for automatic startup, failover, or restart. A resource that is disabled is also offline. |
The resource is unavailable to run under the Oracle CRS for automatic startup, failover, or restart. A resource that is disabled can also be in either the online state or the offline state. |
Online |
The resource is running and providing service. |
The resource is running and providing service. A resource that is online must also be enabled. |
Offline |
The resource is stopped and not providing service. |
The resource is stopped and not providing service. A resource that is offline can also be in either the disabled state or the enabled state. |
For detailed information about the state of Sun Cluster resources, see Resource and Resource Group States and Settings in Sun Cluster Concepts Guide for Solaris OS.
For detailed information about the state of Oracle CRS resources, see your Oracle documentation.
In Oracle 9i, Oracle database components can be stopped and started exclusively under the control of the Sun Cluster RGM. The effects of state changes to Sun Cluster resources for Oracle 9i RAC database instances are as follows:
Bringing online a resource for an Oracle 9i RAC database component starts the component on the nodes where the resource is brought online.
Taking offline a resource for an Oracle 9i RAC database component stops the component on the nodes where the resource is taken offline.