Sun Cluster Data Service for Oracle Real Application Clusters Guide for Solaris OS

Previous: Overview of Administration Tasks for Sun Cluster Support for Oracle Real Application Clusters
Next: Removing Sun Cluster Support for Oracle Real Application Clusters

Tuning Sun Cluster Support for Oracle Real Application Clusters

To tune the Sun Cluster Support for Oracle Real Application Clusters data service, you modify the extension properties of the resources for this data service. For details about these extension properties, see Appendix A, Sun Cluster Support for Oracle Real Application Clusters Extension Properties. Typically, you use the command line scrgadm -x parameter=value to set extension properties when you create the Sun Cluster Support for Oracle Real Application Clusters resources. You can also use the procedures in Chapter 2, Administering Data Service Resources, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS to configure the resources later.

Guidelines for Setting Timeouts

Many of the extension properties for Sun Cluster Support for Oracle Real Application Clusters specify timeouts for steps in reconfiguration processes. The optimum values for most of these timeouts are independent of your cluster configuration. Therefore, you should not need to change the timeouts from their default values.

Timeouts that depend on your cluster configuration are described in the subsections that follow. If timeouts occur during reconfiguration processes, increase the values of these timeout properties to accommodate your cluster configuration.

SPARC: VxVM Component Reconfiguration Step 4 Timeout

The time that is required for step 4 of a reconfiguration of the VxVM component of Sun Cluster Support for Oracle Real Application Clusters is affected by the size and complexity of your VERITAS shared-disk group configuration. If your VERITAS shared-disk group configuration is large or complex and the reconfiguration of the VxVM component times out, increase the timeout for step 4 of a reconfiguration of the VxVM component.

To increase the timeout for step 4 of a reconfiguration of the VxVM component, increase the value of the Cvm_step4_timeout extension property of the SUNW.rac_cvm resource.

For more information, see SPARC: SUNW.rac_cvm Extension Properties.

Example 4–1 Setting the VxVM Component Reconfiguration Step 4 Timeout

# scrgadm -c -j rac_cvm -x cvm_step4_timeout=1200

This example sets the timeout for step 4 of a reconfiguration of the VxVM component to 1200 seconds. This example assumes that the VxVM component is represented by an instance of the SUNW.rac_cvm resource type that is named rac_cvm.

Reservation Step Timeout

The time that is required for reservation commands to run is affected by the following factors:

The number of shared physical disks in the cluster
The load on the cluster

If the number of shared physical disks in the cluster is large, or if your cluster is heavily loaded, the reconfiguration of Sun Cluster Support for Oracle Real Application Clusters might time out. If such a timeout occurs, increase the reservation step timeout.

To increase the reservation step timeout, increase the Reservation_timeout extension property of the appropriate resource for your storage management scheme.

Storage Management Scheme	Resource
Solaris Volume Manager for Sun Cluster	`SUNW.rac_svm`
VxVM with the cluster feature	`SUNW.rac_cvm`
Any combination without a volume manager	`SUNW.rac_hwraid`

Details of the extension properties of these resource types are available in the following sections:

Example 4–2 Setting the Reservation Step Timeout

# scrgadm -c -j rac_hwraid -x reservation_timeout=350

This example sets the timeout for the reservation step of a reconfiguration of Sun Cluster Support for Oracle Real Application Clusters to 350 seconds. In this example, the cluster uses hardware RAID support. This example assumes that the hardware RAID component is represented by an instance of the SUNW.rac_hwraid resource type that is named rac_hwraid.

SPARC: Guidelines for Setting the Communications Port Range for the Oracle UDLM

An application other than the Oracle UDLM on a cluster node might use a range of communications ports that conflicts with the range for the Oracle UDLM. If such a conflict occurs, modify the range of communications ports that the Oracle UDLM uses.

The range of communications ports that the Oracle UDLM uses is determined by the values of the following extension properties of the SUNW.rac_udlm resource type:

Port. Specifies the communications port number that the Oracle UDLM uses. The first number in the range of communications port numbers that the Oracle UDLM uses is the value of Port.
Num_ports. Specifies the number of communications ports that the Oracle UDLM uses. The last number in the range of communications port numbers that the Oracle UDLM uses is the sum of the values of Port and Num_ports.

For more information, see SPARC: SUNW.rac_udlm Extension Properties.

Example 4–3 Setting the Communications Port Number for the Oracle UDLM

# scrgadm -c -j rac_udlm -x port=7000

This example sets the communications port number that the Oracle UDLM uses to 7000. The following assumptions apply to this example:

The Oracle UDLM component is represented by an instance of the SUNW.rac_udlm resource type that is named rac_udlm.
The command in this example is run as part of the procedure for modifying an extension property that is tunable only when disabled. For more information, see How to Modify an Extension Property That Is Tunable Only When a Resource Is Disabled.

How to Modify an Extension Property That Is Tunable Only When a Resource Is Disabled

Restrictions apply to the circumstances in which you can modify an extension property that is tunable only when a resource is disabled. Those circumstances depend on the resource type as follows:

SUNW.rac_udlm – Only when the Oracle UDLM is not running on any cluster node
SUNW.rac_cvm – Only when VxVM is not running in cluster mode on any cluster node

Steps

Disable each resource that the RAC framework resource group contains and bring the RAC framework resource group into the UNMANAGED state.

Disable the instance of the SUNW.rac_framework resource only after you have disabled all other resources that the RAC framework resource group contains. The other resources in the RAC framework resource group depend on the SUNW.rac_framework resource.

For detailed instructions, see Disabling Resources and Moving Their Resource Group Into the UNMANAGED State in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

Reboot all the nodes that are in the node list of the RAC framework resource group.

Use the scrgadm utility to set the property to its new value.
# scrgadm -c -j resource -x property=value
-j resource

Specifies the name of the resource for which you are modifying an extension property. If this resource was created by using the scsetup utility, the name depends on the resource type, as shown in Names Assigned to RAC Framework Resources by scsetup.

property

Specifies the name of the extension property that you are changing.

value

The new value of the extension property.

Bring the RAC framework resource group and its resources online.
# scswitch -Z -g resource-group
-Z

Enables the resource and monitor, moves the resource group to the MANAGED state, and brings the resource group online.

-g resource-group

Specifies the name of the RAC framework resource group that is to be moved to the MANAGED state and brought online. If this resource group was created by using the scsetup utility, the name of the resource group is rac-framework-rg.