Administering Oracle RAC databases from Oracle Solaris Cluster software involves using Oracle Solaris
Cluster administration tools to modify the states of Oracle Solaris Cluster resources for
Oracle RAC database instances. For information about how to create these resources, see
Configuring Resources for Oracle RAC Database Instances.

In an Oracle Solaris Cluster configuration, with one exception, there are no general
restrictions on the use of the Oracle database software command line interface (CLI)
to manage Oracle Grid Infrastructure or on the Oracle srvctl command to manage
the Oracle database and its services. The exception is that autostart must remain disabled
in an Oracle Solaris Cluster configuration. Otherwise, you can use Oracle database software
commands as you would in a configuration that does not include Oracle
Solaris Cluster. The Oracle Solaris Cluster software detects the changes made by the
Oracle database CLI and reacts appropriately.

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 these different name spaces. You register resource types
independently for each cluster.

You can administer the resource groups and resources belonging to the global cluster
only from the global-cluster voting node. You can administer the resource groups and
resources belonging to a zone cluster from that zone cluster. In the global-cluster
voting node, you can also administer the resource groups and resources in a
zone cluster by using the -Z option to specify the zone cluster. You
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 Oracle Solaris Cluster resources
on Oracle database components are explained in the subsections that follow:

Oracle Grid Infrastructure manages the startup and shutdown of Oracle database instances, listeners,
and other components that are configured in the Oracle Grid Infrastructure. Oracle
Grid Infrastructure is a mandatory component. Oracle Grid Infrastructure also monitors components that
are started by Oracle Grid Infrastructure and, if failures are detected, perform actions
to recover from failures.

Because Oracle Grid Infrastructure manages the startup and shutdown of Oracle database
components, these components cannot be stopped and started exclusively under the control of the
Oracle Solaris Cluster RGM. Instead, Oracle Grid Infrastructure and the RGM interoperate so
that when Oracle RAC database instances are started and stopped by Oracle
Grid Infrastructure, the state of the database instances is propagated to Oracle Solaris
Cluster resources.

The following table describes the state changes that occur between Oracle Solaris
Cluster resources and Oracle Grid Infrastructure resources.

The names of the states of Oracle Solaris Cluster resources and Oracle
Grid Infrastructure resources are identical. However, the meaning of each state name is
different for Oracle Solaris Cluster resources and Oracle Grid Infrastructure resources. For more
information, see the following table.

The resource is available to the Oracle Solaris 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 Grid Infrastructure 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 Oracle Solaris Cluster RGM
for automatic startup, failover, or restart. A resource that is disabled is also
offline.

The resource is unavailable to run under Oracle Grid Infrastructure 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.