Oracle® Solaris Cluster Data Service for Oracle Real Application Clusters Guide

Exit Print View

Updated: July 2014, E39656–01

Guidelines for Setting Timeouts

Many of the extension properties for Support for Oracle RAC 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.

This section describes the following timeouts:

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 Support for Oracle RAC 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 SUNW.rac_framework resource.

For more information, see SUNW.rac_framework Extension Properties.

Example 5-1  Setting the Reservation Step Timeout
# clresource set -p reservation_timeout=350 rac-framework-rs

This example sets the timeout for the reservation step of a reconfiguration of Support for Oracle RAC to 350 seconds. This example assumes that the Support for Oracle RAC framework component is represented by an instance of the SUNW.rac_framework resource type that is named rac-framework-rs.