How to Change Interconnect/Public Interface IP or Subnet in Oracle Clusterware
Metalink 283684.1
Purpose:
----------------
The purpose of this note is to describe how to change or update the cluster_interconnect and/or public interface IP information that is stored in the OCR. The interface defined as 'public' will be the interface used to bind the VIP to, whereas the interface defined as 'cluster_interconnect' will be the default interface used by any RDBMS or ASM instances for cache fusion traffic.
This note is not intended as a means to change the Public or Private Hostnames themselves. Public or Private hostnames can only be changed by removing/adding nodes, or reinstalling Oracle Clusterware. VIP Hostnames can be changed, however. To change a VIP Hostname, please refer to Note 276434.1 .
It may be necessary to change or update interface names, or the IP information associated with an interface if there is a network change affecting the servers, or if the original information that was input during the installation was incorrect. It may also be the case that for some reason, the Oracle Interface Configuration Assistant ('oifcfg') did not succeeed during the installation.
In any of these cases, the 'oifcfg' utility can be used to remove incorrect entries that are stored in the OCR, and to add the correct information back into the OCR.
Note the value stored for the cluster_interconnect via oifcfg is meant to be used by RDBMS and ASM instances only. Oracle Clusterware does not use these values for the interconnect. Oracle Clusterware uses the private nodenames that were specified at install time for communications between the clusterware daemons. If you wish to change the network that Oracle Clusterware is using for communications on the interconnect, this can be done by modifying the hosts file of each node, such that the private node name that was specified during the installation would now resolve to a different IP address. This modification of the hosts file should be done while the Oracle Clusterware Stack is down on all nodes. After the Oracle Clusterware stack has restarted, you can then run oifcfg as described in this note, to change the cluster_interconnect used by RDBMS and ASM instances.
Solution:
---------------------------
As noted above, if the IP subnet for either the 'public' or 'cluster_interconnect' interface is incorrect and needs to be changed, you should make the changes using the Oracle Interface Configuration Tool (oifcfg).
Instructions for Changing Interfaces on Linux/Unix systems:
-------------------------------------------------------------------------
You can change the interface information for a cluster using the following as an example:
1. First - Use the getif option to show the currently configured interfaces. This will display the interfaces that are currently stored in the OCR, what their subnets are, and what their role is (i.e. public or cluster_interconnect). This example is from a Linux system, but the syntax is the same for any platform. On Unix/Linux systems, the interface names are generally assigned by the OS, and standard names vary by platform.
% $ORA_CRS_HOME/bin/oifcfg getif
eth0 10.2.156.0 global public
eth1 192.168.0.0 global cluster_interconnect
2. If the public interface IP needs to be changed, there is not a 'modify' option - you will need to delete the interface and add it back with the correct subnet IP. So, in the example here, the subnet is being changed from 10.2.156.0 to 10.2.166.0 via two separate commands - first a 'delif' followed by a 'setif':
% $ORA_CRS_HOME/bin/oifcfg delif -global eth0
% $ORA_CRS_HOME/bin/oifcfg setif –global eth0/10.2.166.0:public
3. The same step could be use for the private interface:
% $ORA_CRS_HOME/bin/oifcfg delif –global eth1
% $ORA_CRS_HOME/bin/oifcfg setif –global eth1/192.168.1.0:cluster_interconnect
4. Verify the correct interface subnet is in use by re-running oifcfg with the 'getif' option:
% $ORA_CRS_HOME/bin/oifcfg getif
eth0 10.2.166.0 global public
eth1 192.168.1.0 global cluster_interconnect
Purpose:
----------------
The purpose of this note is to describe how to change or update the cluster_interconnect and/or public interface IP information that is stored in the OCR. The interface defined as 'public' will be the interface used to bind the VIP to, whereas the interface defined as 'cluster_interconnect' will be the default interface used by any RDBMS or ASM instances for cache fusion traffic.
This note is not intended as a means to change the Public or Private Hostnames themselves. Public or Private hostnames can only be changed by removing/adding nodes, or reinstalling Oracle Clusterware. VIP Hostnames can be changed, however. To change a VIP Hostname, please refer to Note 276434.1 .
It may be necessary to change or update interface names, or the IP information associated with an interface if there is a network change affecting the servers, or if the original information that was input during the installation was incorrect. It may also be the case that for some reason, the Oracle Interface Configuration Assistant ('oifcfg') did not succeeed during the installation.
In any of these cases, the 'oifcfg' utility can be used to remove incorrect entries that are stored in the OCR, and to add the correct information back into the OCR.
Note the value stored for the cluster_interconnect via oifcfg is meant to be used by RDBMS and ASM instances only. Oracle Clusterware does not use these values for the interconnect. Oracle Clusterware uses the private nodenames that were specified at install time for communications between the clusterware daemons. If you wish to change the network that Oracle Clusterware is using for communications on the interconnect, this can be done by modifying the hosts file of each node, such that the private node name that was specified during the installation would now resolve to a different IP address. This modification of the hosts file should be done while the Oracle Clusterware Stack is down on all nodes. After the Oracle Clusterware stack has restarted, you can then run oifcfg as described in this note, to change the cluster_interconnect used by RDBMS and ASM instances.
Solution:
---------------------------
As noted above, if the IP subnet for either the 'public' or 'cluster_interconnect' interface is incorrect and needs to be changed, you should make the changes using the Oracle Interface Configuration Tool (oifcfg).
Instructions for Changing Interfaces on Linux/Unix systems:
-------------------------------------------------------------------------
You can change the interface information for a cluster using the following as an example:
1. First - Use the getif option to show the currently configured interfaces. This will display the interfaces that are currently stored in the OCR, what their subnets are, and what their role is (i.e. public or cluster_interconnect). This example is from a Linux system, but the syntax is the same for any platform. On Unix/Linux systems, the interface names are generally assigned by the OS, and standard names vary by platform.
% $ORA_CRS_HOME/bin/oifcfg getif
eth0 10.2.156.0 global public
eth1 192.168.0.0 global cluster_interconnect
2. If the public interface IP needs to be changed, there is not a 'modify' option - you will need to delete the interface and add it back with the correct subnet IP. So, in the example here, the subnet is being changed from 10.2.156.0 to 10.2.166.0 via two separate commands - first a 'delif' followed by a 'setif':
% $ORA_CRS_HOME/bin/oifcfg delif -global eth0
% $ORA_CRS_HOME/bin/oifcfg setif –global eth0/10.2.166.0:public
3. The same step could be use for the private interface:
% $ORA_CRS_HOME/bin/oifcfg delif –global eth1
% $ORA_CRS_HOME/bin/oifcfg setif –global eth1/192.168.1.0:cluster_interconnect
4. Verify the correct interface subnet is in use by re-running oifcfg with the 'getif' option:
% $ORA_CRS_HOME/bin/oifcfg getif
eth0 10.2.166.0 global public
eth1 192.168.1.0 global cluster_interconnect
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/12361284/viewspace-616744/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- How to Change IP and VIP in Oracle Clusterware(一)-概念篇Oracle
- Oracle 12.2 RAC修改public ip address或public ip(subnet (netmask) or interface)Oracle
- How to Change IP and VIP in Oracle Clusterware(二)-實操篇Oracle
- 修改Public/Interconnect IP
- SCAN , virtual IP , and public IP must all be on the same subnet
- ORACLE SQL DEVELOPER User Interface ChangeOracleSQLDeveloper
- How to change Public VIP Address in 11gR2 RAC
- The Basics of IPv4 Subnet and Oracle Clusterware(Doc ID 1386709.1)Oracle
- Change AUTO_START in ASM Resource Oracle ClusterwareASMOracle
- How to Deinstall Oracle Clusterware Home ManuallyOracle
- public interface View介面和public interface ViewResolver介面介紹View
- How to modify Public ip and vip In 11gr2 Rac
- How to Change hostname in Oracle Linux 7OracleLinux
- 轉載一個step by step change public-ip and vip on RAC
- Oracle RAC修改Scan IP,Public IP的方法Oracle
- How to Clean Up After a Failed Oracle Clusterware (CRS) InstallationAIOracle
- Oracle RAC修改public, VIP, SCAN IPOracle
- How to change the APPS db password in Oracle EBSAPPOracle
- Oracle RAC修改public,private,vip scan IPOracle
- Oracle RAC中的Public IP, VIP和Internal IP,SCANOracle
- How to change the background color for PyCharmPyCharm
- oracle 11gR2 如何修改public ipOracle
- How To Change The Asm Rebalancing PowerASM
- How to Change RabbitMQ Queue Parameters in Production?MQ
- How To Change UNIX Process Resource LimitsMIT
- Oracle RAC RDS interconnectOracle
- Metlink:How to clean up a failed CRS/ClusterwareAI
- How To Change The Oracle Hidden Parameters In Oracle 10g [ID 315631.1]Oracle 10g
- How to change the implementation (detour) of an externally declared functionFunction
- oracle clusterwareOracle
- Azure Public IP DNS域名DNS
- win rac public ip 修改
- oracle 10g rac modify public ip,private ip,vip實驗步驟Oracle 10g
- How to change VIP and VIP/Hostname in 10g
- Oracle 12. 2 RAC public IP與vip 互換方法Oracle
- Oracle RAC環境下vip/public/private IP的區別Oracle
- RAC 11.2.0.3 修改 Public IP
- ORACLE RAC clusterwareOracle