|Default value||There is no default value.|
|Range of values||One or more IP addresses, separated by colons|
CLUSTER_INTERCONNECTS provides Oracle with information about additional cluster interconnects available for use in Real Application Clusters environments.
CLUSTER_INTERCONNECTS parameter can be used to override the default interconnect with a preferred cluster traffic network. This parameter is useful in Data Warehouse systems that have reduced availability requirements and high interconnect bandwidth demands. You can also use
CLUSTER_INTERCONNECTS to override the default interconnect chosen by Oracle.
For example, if you are running two instances of Oracle for two databases on the same machine, then you can load balance the interconnect traffic to different physical interconnects. This does not reduce Oracle availability.
CLUSTER_INTERCONNECTS can be used in Oracle Real Application Clusters environments to indicate cluster interconnects available for use for the database traffic. Use this parameter if you need to override the default interconnect configured for the database traffic, which is stored in the cluster registry. This procedure also may be useful with Data Warehouse systems that have reduced availability requirements and high interconnect bandwidth demands.
CLUSTER_INTERCONNECTS specifically overrides the following:
Network classifications stored by
oifcfg in the OCR.
The default interconnect chosen by Oracle.
If you want to load-balance the interconnect, then Oracle recommends that you use link-bonding at the operating system level, even if you have two databases on the same server, so that multiple interconnects use the same address. Note that multiple private addresses provide load balancing, but do not provide failover unless bonded. If you specify multiple addresses in init.ora using
CLUSTER_INTERCONNECTS, instead of bonding multiple addresses at the operating system level, then typically availability is reduced, because each network interface card failure will take down that instance.
Refer to your vendor documentation for information about bonding interfaces. Some vendor bonding architectures may require the use of this parameter.
If you have multiple database instances on Oracle Real Application Clusters nodes and want to use a specific interface for each instance, then you can set the
CLUSTER_INTERCONNECTS initialization parameter to the IP address for each database instance. For example:
If the Oracle RAC interconnect is configured to run on a different interface than the Oracle Clusterware interconnect, then this configuration can cause reduced availability, as failovers or instance evictions can be delayed if the Oracle RAC interconnect fails while the Oracle Clusterware NIC remains up.
See Also:Oracle Real Application Clusters Administration and Deployment Guide for additional platform-specific information about using