本站中文解释
Oracle参数CLUSTER_INTERCONNECTS一般用于RAC环境，它是指定系统之间网络传输速度，也就是CRS组件要求使用网络间传输消息的速度，取值必须介于10（最低）和1000（最高）之间。正确设置方法：首先根据RAC节点间网络传输带宽、丢包率等数据分配一个适当的值（如30~50），随后按照以下示例设置参数：
alter system set cluster_interconnects=’tcp:192.168.3.150:3050,tcp:192.168.3.149:3050′ scop=spfile;
以上方法可以保证集群之间的消息正常传输，正确设置Oracle参数CLUSTER_INTERCONNECTS还可有效缩短hang低、注册低等异常日志信息出现的时间，使RAC集群环境达到卓越运行状态。
官方英文解释
CLUSTER_INTERCONNECTS can be used in Oracle Real Application Clusters environments to indicate cluster interconnects available for use for the database traffic.
| Property | Description |
|---|---|
|
Parameter type |
String |
|
Syntax |
|
|
Default value |
There is no default value. |
|
Modifiable |
No |
|
Modifiable in a PDB |
No |
|
Range of values |
One or more IP addresses, separated by colons |
|
Basic |
No |
Use this parameter 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
oifcfgin 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:
hr1.init.ora.cluster_interconnects="192.0.2.111" oltp3.init.ora.cluster_interconnects="192.0.2.112"
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 information about using CLUSTER_INTERCONNECTS
