Upgrading Sun Cluster Support for Oracle RAC

If you upgrade Sun Cluster foundation software to release 3.2, you must also upgrade the Sun Cluster Support for Oracle RAC software. For more information, see Chapter 8, Upgrading Sun Cluster Software, in Sun Cluster Software Installation Guide for Solaris OS.

Your existing configuration of Sun Cluster Support for Oracle RAC might not include the RAC framework resource group. In this situation, you must register and configure the RAC framework resource group after upgrading to Sun Cluster 3.2. Otherwise, Oracle RAC cannot run with Sun Cluster. For more information, see Registering and Configuring the RAC Framework Resource Group.

Sun Cluster 3.2 introduces several new features for Sun Cluster Support for Oracle RAC. Information about how to upgrade an existing configuration to use these new features is provided in the subsections that follow.

The SUNW.oracle_rac_server resource type and the SUNW.oracle_listener resource type are unchanged in Sun Cluster 3.2. If you choose to continue to use the SUNW.oracle_rac_server resource type and the SUNW.oracle_listener resource type for Oracle 9i RAC database instances, no upgrade of these resource types is required.

Upgrading Resources in the RAC Framework Resource Group

Changes to resource types of resources in the RAC framework for Sun Cluster 3.2 are summarized in the following table.

Upgrade these resource types if you are upgrading to version 3.2 from an earlier version of Sun Cluster Support for Oracle RAC.

For general instructions that explain how to upgrade a resource type, see Upgrading a Resource Type in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

The information that you require to complete the upgrade of the RAC framework resource types is provided in the subsections that follow.

Information for Registering the New Versions of RAC Framework Resource Types

The resource type versions of changed RAC framework resource types are listed in the following table for version 3.1 and version 3.2 of Sun Cluster. This table also lists the name of the Resource Type Registration (RTR) file of each changed resource type.

To determine the version of the resource type that is registered, use the following command:

# clresourcetype show resource-type

resource-type

Specifies the resource type whose version you are determining.

Information for Migrating Existing Instances of RAC Framework Resource Types

The information that you require to edit each instance of RAC framework resource types is listed in the following table.

The following example shows a command for editing an instance of the SUNW.rac_udlm resource type.

The example shows the setting of an extension property that can be set only when the resource is disabled. The step for disabling the resource is not shown in the example.

Example 6–1 Editing an Instance of the SUNW.rac_udlm Resource Type

# clresource set -p type_version=2 \
-p port=100 rac_udlm-rs 

This command edits a SUNW.rac_framework resource as follows:

• The SUNW.rac_udlm resource is named rac_udlm.

• The type_version property of this resource is set to 2.

• The communications port number that the Oracle UDLM uses is set to 100.

How to Preserve a Nondefault Value of the reservation_timeout Extension Property

The reservation_timeout extension property specifies the timeout value in seconds for the reservation step of a reconfiguration of Sun Cluster Support for Oracle RAC.

In Sun Cluster release 3.1, reservation_timeout is an extension property of the following resource types:

• SUNW.rac_cvm

• SUNW.rac_hwraid

• SUNW.rac_svm

In Sun Cluster release 3.2, reservation_timeout is an extension property only of the SUNW.rac_framework resource type. This property is removed from the SUNW.rac_cvm resource type and the SUNW.rac_svm resource type. The SUNW.rac_hwraid resource type is removed from Sun Cluster release 3.2.

A nondefault value of the reservation_timeout extension property might be set for an existing resource of type SUNW.rac_hwraid, SUNW.rac_cvm, or SUNW.rac_svm. If you require this value after you upgrade to Sun Cluster release 3.2, perform this task to preserve the value.

1. Before you migrate or remove the resource for which the reservation_timeout extension property is set, obtain the value of this property.

   # clresource show -p reservation_timeout -t resource-type

   resource-type

   Specifies the resource type of the resource for which the reservation_timeout extension property is set, namely, SUNW.rac_cvm, SUNW.rac_hwraid, or SUNW.rac_svm.

2. When you migrate the existing instance of the SUNW.rac_framework resource type, set the reservation_timeout extension property to the value that you obtained in Step 1.

   # clresource set -p type_version=version \ -p reservation_timeout=timeout rac-framework-rs

   version

   Specifies the value of the type_version property for the version of SUNW.rac_framework to which you are migrating the instance. In Sun Cluster release 3.2, version is 2.

   timeout

   Specifies the value to which you are setting the reservation_timeout extension property. This value is the value that you obtained in Step 1.

   rac-framework-rs

   Specifies the name of the resource of type SUNW.rac_framework on your cluster. If the scsetup utility of Sun Cluster release 3.1 was used to create the RAC framework resource group, this resource is named rac_framework.

Example 6–2 Preserving a Nondefault Value of the reservation_timeout Extension Property

This example shows the commands for preserving a nondefault value of the reservation_timeout extension property that was set for a resource of type SUNW.rac_svm.

Before the migration of the resource of type SUNW.rac_svm, the following command is run to obtain the value of the reservation_timeout extension property:

# clresource show -p reservation_timeout -t SUNW.rac_svm

=== Resources ===                              

Resource:                                       rac-svm-rs

  --- Standard and extension properties ---    

  Reservation_timeout:                          350
    Class:                                         extension
    Description:                                   Timeout (in seconds) for the 
reservation step of Sun Cluster framework for RAC
    Per-node:                                      False
    Type:                                          int

During the migration of the resource of type SUNW.rac_framework, the following command is run to set properties as follows:

• The type_version property is set to 2.

• The reservation_timeout extension property is set to 350 seconds.

# clresource set -p type_version=2 \
-p reservation_timeout=350 rac_framework 

See Also

The following documentation:

• Information for Registering the New Versions of RAC Framework Resource Types

• Information for Migrating Existing Instances of RAC Framework Resource Types

• The clresource(1CL) man page

How to Remove the Resource of Type SUNW.rac_hwraid

In Sun Cluster release 3.2, the SUNW.rac_hwraid resource type is obsolete and is not supplied with this release. Any resource of type SUNW.rac_hwraid is not required after an upgrade to Sun Cluster release 3.2. If a resource of this obsolete type is configured on your cluster, remove the resource.

1. Become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.

2. Delete the instance of SUNW.rac_hwraid, if any.

   # clresource delete -F -t SUNW.rac_hwraid +

   ---

   Note –

   If no resource of type SUNW.rac_hwraid is configured on your cluster, a message to this effect is displayed. Ignore this message.

   ---

Adding Storage Resources for Oracle Files

Sun Cluster 3.2 introduces resource types that provide fault monitoring and automatic fault recovery for global device groups and file systems.

If you are using global device groups or shared file systems for Oracle files, add storage resources to manage the availability of the storage on which the Oracle software depends.

Before adding storage resources for Oracle files, ensure that you have upgraded resources in the RAC framework resource group. For more information, see Upgrading Resources in the RAC Framework Resource Group.

For detailed instructions for adding storage resources for Oracle files, see Registering and Configuring Storage Resources for Oracle Files.

Follow these instructions only if you are adding storage resources to an existing configuration of storage management schemes. If you are extending an existing configuration of Sun Cluster Support for Oracle RAC by supporting additional storage management schemes, see the following sections:

• Chapter 2, Configuring Storage for Oracle Files

• How to Add a Volume Manager Resource to the RAC Framework Resource Group

Adding Resources for Interoperation With Oracle 10g R2 CRS

Sun Cluster 3.2 introduces resource types that enable Sun Cluster and Oracle 10g R2 CRS to interoperate. These resource types also enable Oracle RAC database instances to be administered from Sun Cluster.

Oracle 10g R1 CRS and Sun Cluster cannot interoperate. Instead, Oracle 10g R1 CRS start and shut down Oracle RAC database instances.

Before adding resources for interoperation with Oracle 10g R2 CRS, ensure that you have performed the tasks in the following sections:

• Upgrading Resources in the RAC Framework Resource Group

• Adding Storage Resources for Oracle Files

For detailed instructions for adding resources for interoperation with Oracle 10g R2 CRS, see Configuring Resources for Oracle RAC Database Instances.

Upgrading to Sun Cluster 3.2 Resource Types for Oracle 9i RAC Database Instances

Sun Cluster 3.2 replaces the failover resource types that automate the startup and shutdown of Oracle 9i RAC database instances with multi-master resource types. The multi-master resources simplify the administration and enhance the scalability of Sun Cluster Support for Oracle RAC.

Upgrading to Sun Cluster 3.2 resource types for Oracle 9i RAC database instances involves the tasks that are described in the following sections:

1. How to Take Offline Resource Groups for Oracle RAC Database Components and Restart the Components

2. How to Modify the Configuration of Sun Cluster Resources for Oracle 9i RAC Database Instances

Perform these tasks in the order in which they are listed.

How to Take Offline Resource Groups for Oracle RAC Database Components and Restart the Components

This task involves taking offline resource groups for Oracle RAC database components and restarting the components on each cluster node individually.

This sequence of operations avoids downtime by ensuring that the Oracle RAC database components remain online on other cluster nodes.

Perform this task on each cluster node individually.

Before You Begin

Ensure that you have upgraded resources in the RAC framework resource group. For more information, see Upgrading Resources in the RAC Framework Resource Group.

1. Become superuser on the cluster node.

2. If you configured Oracle listener resources in separate resource groups, take offline the resource groups from the node.

   If you configured Oracle listener resources in the same resource group as the Oracle RAC server resource, omit this step.

   For each resource group that you are taking offline, type the following command:

   # clresourcegroup offline -n node rac-listener-rg

   -n node

   Specifies the node from which you are taking the resource group offline. This node is the node where you are performing this task.

   rac-listener-rg

   Specifies the resource group for Oracle listener resources that you are taking offline.

   When the resource group is taken offline, the Oracle listener is stopped on the node. The Oracle listeners on other nodes are unaffected.

3. Take offline the resource group for the RAC server from the node.

   # clresourcegroup offline -n node rac-server-rg

   -n node

   Specifies the node from which you are taking the resource group offline. This node is the node where you are performing this task.

   rac-server-rg

   Specifies the resource group for the Oracle RAC server resource that you are taking offline.

   When the resource group is taken offline, the Oracle RAC server is stopped on the node. The Oracle RAC servers on other nodes are unaffected.

   If you configured Oracle listener resources in the same resource group as the Oracle RAC server resource, the listeners are also stopped on the node. The Oracle listeners on other nodes are unaffected.

4. Use Oracle utilities to restart the Oracle RAC server and Oracle listener on the node.

Next Steps

Go to How to Modify the Configuration of Sun Cluster Resources for Oracle 9i RAC Database Instances.

How to Modify the Configuration of Sun Cluster Resources for Oracle 9i RAC Database Instances

Perform this task from one cluster node.

Before You Begin

Ensure that the task that is explained in How to Take Offline Resource Groups for Oracle RAC Database Components and Restart the Components has been performed.

1. Become superuser or assume a role that provides solaris.cluster.admin and solaris.cluster.modify RBAC authorizations.

2. If you configured Oracle listener resources in separate resource groups, remove the resource groups.

   If you configured Oracle listener resources in the same resource group as Oracle RAC server resources, omit this step.

   For each resource group that you are removing, type the following command:

   # clresourcegroup delete -F rac-listener-rg

   rac-listener-rg

   Specifies the resource group for Oracle listener resources that you are removing.

3. Remove all resource groups that contain an Oracle RAC server resource.

   For each resource group that you are removing, type the following command:

   # clresourcegroup delete -F rac-server-rg

   rac-server-rg

   Specifies the resource group that contains an Oracle RAC server resource that you are removing.

4. If you are using Sun StorEdge QFS shared file system, remove all resource groups that contain resources for the Sun StorEdge QFS metadata server.

   If you are not using the Sun StorEdge QFS shared file system, omit this step.

   For each resource group that you are removing, type the following command:

   # clresourcegroup delete -F qfs-mds-rg

   qfs-mds-rg

   Specifies the resource group that contains resources for the Sun StorEdge QFS metadata server that you are removing.

5. If you are using global device groups or shared file systems for Oracle files, add storage resources to manage the availability of the storage on which the Oracle software depends.

   If you are not using global device groups or shared file systems for Oracle files, omit this step.

   For instructions for performing this task, see Adding Storage Resources for Oracle Files.

6. Configure new resources for Oracle 9i RAC database instances.

   For instructions for performing this task, see Configuring Resources for Oracle RAC Database Instances.