Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for Oracle Real Application Clusters Guide Oracle Solaris Cluster |
1. Installing Support for Oracle RAC
2. Configuring Storage for Oracle Files
3. Registering and Configuring the Resource Groups
4. Enabling Oracle RAC to Run in a Cluster
5. Administering Support for Oracle RAC
Overview of Administration Tasks for Support for Oracle RAC
Automatically Generated Names for Oracle Solaris Cluster Objects
Administering Oracle RAC Databases From Oracle Solaris Cluster Software
Effects of State Changes to Oracle Solaris Cluster Resources for Oracle 9i RAC Database Instances
Guidelines for Setting Timeouts
SPARC: VxVM Component Reconfiguration Step 4 Timeout
SPARC: Guidelines for Setting the Communications Port Range for the UDLM
How to Modify an Extension Property That Is Tunable Only When a Resource Is Disabled
Tuning the Support for Oracle RAC Fault Monitors
Operation of the Fault Monitor for a Scalable Device Group
Operation of the Fault Monitor for Scalable File-System Mount Points
Operation of the Oracle 9i RAC Server Fault Monitor
Operation of the Main Fault Monitor
Operation of the Database Client Fault Probe
Operations to Monitor the Partition for Archived Redo Logs
Operations to Determine Whether the Database is Operational
Actions by the Server Fault Monitor in Response to a Database Transaction Failure
Scanning of Logged Alerts by the Server Fault Monitor
Operation of the Oracle 9i RAC Listener Fault Monitor
Obtaining Core Files for Troubleshooting DBMS Timeouts
Customizing the Oracle 9i RAC Server Fault Monitor
Defining Custom Behavior for Errors
Changing the Response to a DBMS Error
Responding to an Error Whose Effects Are Major
Ignoring an Error Whose Effects Are Minor
Changing the Response to Logged Alerts
Changing the Maximum Number of Consecutive Timed-Out Probes
Propagating a Custom Action File to All Nodes in a Cluster
Specifying the Custom Action File That a Server Fault Monitor Should Use
How to Specify the Custom Action File That a Server Fault Monitor Should Use
6. Troubleshooting Support for Oracle RAC
7. Modifying an Existing Configuration of Support for Oracle RAC
8. Upgrading Support for Oracle RAC
A. Sample Configurations of This Data Service
B. Preset Actions for DBMS Errors and Logged Alerts
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 Clusterware or on the Oracle srvctl command to manage the Oracle database and its services. The exception is that, with Oracle 11g release 2 or 12c, 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.
The software architectures of Oracle 9i, Oracle 10g release 1, and Oracle 10g release 2, 11g, or 12c are different. As a result of these differences, the resources for Oracle RAC database instances that Oracle Solaris Cluster software requires depend on the version of Oracle that you are using. Consequently, the administration of Oracle RAC databases from Oracle Solaris Cluster software also depends on the version of Oracle that you are using.
Note - If you are using Oracle 10g release 1, you cannot administer Oracle RAC databases from Oracle Solaris Cluster software. Instead, use Oracle Clusterware utilities to start and shut down Oracle RAC database instances.
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:
In Oracle 10g, 11g, or 12c, Oracle Clusterware manages the startup and shutdown of Oracle database instances, listeners, and other components that are configured in the Oracle Clusterware. Oracle Clusterware is a mandatory component of Oracle 10g, 11g, or 12c. Oracle Clusterware also monitors components that are started by Oracle Clusterware and, if failures are detected, perform actions to recover from failures.
Because Oracle Clusterware 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 Clusterware and the RGM interoperate so that when Oracle RAC database instances are started and stopped by Oracle Clusterware, 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 Clusterware resources.
Table 5-2 Propagation of State Changes Between Oracle Solaris Cluster Resources and Oracle Clusterware Resources
|
The names of the states of Oracle Solaris Cluster resources and Oracle Clusterware resources are identical. However, the meaning of each state name is different for Oracle Solaris Cluster resources and Oracle Clusterware resources. For more information, see the following table.
Table 5-3 Comparisons of States for Oracle Solaris Cluster Resources and Oracle Clusterware Resources
|
For detailed information about the state of Oracle Solaris Cluster resources, see Resource and Resource Group States and Settings in Oracle Solaris Cluster Concepts Guide.
For detailed information about the state of Oracle Clusterware resources, see your Oracle documentation.
In Oracle 9i, Oracle database components can be stopped and started exclusively under the control of the Oracle Solaris Cluster RGM. The effects of state changes to Oracle Solaris 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.