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 Parallel Server/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.

If you are using the cluster file system, the reservation step timeout is not applicable.

Details of the extension properties of these resource types are available as follows:

• For the SUNW.rac_cvm resource type, see Table A–2.

• For the SUNW.rac_hwraid resource type, see Table A–3.

Example 2–3 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 Parallel Server/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.