Using Serviceguard Extension for RAC, 10th Edition, April 2013

(DLPI) and supported over Serviceguard heartbeat subnet networks, including primary and
standby links.
• Highly available virtual IP () (only when using Oracle Grid Infrastructure 11.2.0.2) — IP
addresses, which Oracle Database and Oracle ASM instances use to ensure highly available
and load balanced across the provided set of cluster interconnect interfaces.
The most common network configuration is to have all interconnect traffic for cluster
communications to go on a single heartbeat network that is redundant so that Serviceguard
monitors the network and resolves interconnect failures by cluster reconfiguration.
The following are situations when it is not possible to place all interconnect traffic on a single
network:
• RAC GCS (cache fusion) traffic may be very high, so an additional dedicated heartbeat
network for Serviceguard needs to be configured.
• Some networks, such as Infiniband, are not supported by CFS/CVM, so the CSS-HB/RAC-IC
traffic may need to be on a separate network that is different from SG-HB network.
• Certain configurations for fast re-configurations requires a dual Serviceguard heartbeat network,
and CSS-HB/RAC-IC does not support multiple networks for HA purposes.
• In a multiple database configuration, RAC-IC traffic of one database may interfere with RAC-IC
traffic of another database; therefore, the RAC-IC traffic of databases may need to be
separated.
In the above cases, you will see a longer time to recover some network failures beyond those
protected by primary and standby, unless Serviceguard is configured to monitor the network.
A failure of CSS-HB/RAC-IC network in such configuration does not force Serviceguard to reform
the cluster. If Serviceguard is not configured to monitor the network, Oracle will take at least CSS
misscount time interval to resolve the network failure. The default value of CSS misscount in SGeRAC
configurations is 600 seconds.
To avoid longer recovery times, manage Oracle Clusterware and RAC-DB instances using
Serviceguard multi-node packages. In addition, configure the CLUSTER_INTERCONNECT_SUBNET
package configuration parameter (as done with a standard SUBNET package configuration
parameter) in the respective multi-node packages to monitor the CSS-HB/RAC-IC networks.
Planning Storage for Oracle Cluster Software
Oracle Cluster Software requires shared storage for the Oracle Cluster Registry (OCR) and a vote
device. Automatic Storage Management cannot be used for the OCR and vote device in prior
Oracle 11gR2 versions because these files must be accessible before Oracle Cluster Software
starts.
For Oracle 10gR2, the minimum required size for each copy of the OCR is 100 MB and for each
vote disk it is 20 MB. For Oracle 11gR1, the minimum required size for each copy of the OCR is
300 MB, and for each vote disk it is also 300 MB.
The Oracle OCR and vote device can be created on supported shared storage, including SLVM
logical volumes, CVM raw volumes, and CFS file systems (on HP-UX releases that support Veritas
CFS and CVM). See “About Veritas CFS and CVM from Symantec” (page 16). Oracle 11gR2
supports OCR and vote device on ASM over SLVM, ASM over raw device files, and Cluster File
System (CFS).
Planning Storage for Oracle 10gR2/11gR1/11gR2 RAC
NOTE: The Oracle 11gR2 OUI allows only ASM over SLVM, ASM over raw device files, Cluster
File System for Clusterware files, and Database files.
Planning Storage for Oracle Cluster Software 31