Sun Cluster Geographic Edition software supports Oracle Real Application Clusters with Hitachi TrueCopy software. Observe the following requirements when you configure Oracle Real Application Clusters:
Each CRS OCR and Voting Disk Location must be in its own device group on each cluster and cannot be replicated.
Static data such as CRS and database binaries are not required to be replicated. But this data must be accessible from all nodes of both clusters.
You must create a SUNW.ScalDeviceGroup resource in its own resource group for the device group that holds dynamic database files. This resource group must be separate from the resource group that holds the clusterware SUNW.ScalDeviceGroup resource.
To be able to leave RAC infrastructure resource groups outside of Sun Cluster Geographic Edition control, you must run Sun Cluster Geographic Edition binaries on both cluster partners and set the RAC protection group External_Dependency_Allowed property to true.
Do not add the CRS OCR and Voting Disk device group to the protection group's cluster_dgs property.
Do not add RAC infrastructure resource groups to the protection group. Only add the rac_server_proxy resource group and resource groups for device groups that are replicated to the protection group. Also, you must set to false the auto_start_on_new_cluster resource group property for the rac_server_proxy resource group and resource groups and for device groups that are replicated.
When you use a cluster file system for an Oracle RAC file system, such as a flash recovery area, alert, or trace log files, you must manually create on both clusters a separate resource group that uses the HAStoragePlus resource to bring online these corresponding file systems. You must set a strong resource dependency from nonClusterware SUNW.ScalDeviceGroup resources to this HAStoragePlus resource. Then add this HAStoragePlus resource group to the RAC protection group.