- 浏览: 1001584 次
- 性别:
- 来自: 北京
文章分类
- 全部博客 (529)
- 服务器 (8)
- jsp (1)
- java (6)
- AIX (1)
- solaris (3)
- linux学习 (53)
- javaScript (2)
- hibernate (1)
- 数据库 (74)
- sql语句 (8)
- oracle 学习 (75)
- oracle 案例 (42)
- oracle 管理 (42)
- Oracle RAC (27)
- oracle data guard (12)
- oracle 参数讲解 (14)
- Oracle 字符集 (8)
- oracle性能调优 (24)
- oracle备份与恢复 (12)
- oracle Tablespace (9)
- oracle性能诊断艺术 (1)
- oracle 11g学习 (5)
- oracle streams (1)
- oracle upgrade and downgrade (4)
- db2学习 (13)
- db2命令学习 (2)
- mysql (28)
- sql server (30)
- sql server 2008 (0)
- 工具 (10)
- 操作系统 (3)
- c++ (1)
- stock (1)
- 生活 (5)
- HADOOP (2)
最新评论
-
massjcy:
...
如何将ubuntu文件夹中文名改为英文 -
skypiea:
谢谢。。。
终于解决了。。。
Oracle 10.2.0.4(5)EM不能启动的解决方案(Patch 8350262) -
qwe_rt:
引用vi /etc/sysconfig/network 请问 ...
Linux操作系统下配置静态IP上网 -
liuqiang:
sudo killall -9 apache2
ps 和 kill 命令详解 -
dazuiba:
引用*绝杀 kill -9 PID 当使用此命令时,一定要通过 ...
ps 和 kill 命令详解
How to Change Interconnect/Public Interface IP or Subnet in Oracle Clusterware [
- 博客分类:
- Oracle RAC
Applies to:
Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 11.1.0.8
Information in this document applies to any platform.
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.
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. (For Windows systems, see additional notes below) :
% $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
syntax: oifcfg setif <interface-name>/<subnet>:<cluster_interconnect|public>
Note: 'oifcfg setif' should be run as the same user who did the original CRS installation, because the 'setif' option updates the OCR and sets permissions in the OCR for the interface based on who is running the command. This is true on all platforms, including Windows.
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
The syntax for changing the interfaces on Windows/RAC clusters is the same as on Unix or Linux, but the interface names will be slightly different. On Windows systems, the default names assigned to the interfaces are generally names such as:
Local Area Connection
Local Area Connection 1
Local Area Connection 2
If you are using an interface name that has spaces in it, such as the examples above, you must enclose the name in quotes. Also, be aware that it is case sensitive. So for example, on Windows, you would use syntax such as the following to add the public subnet in:
C:\oracle\product\10.2.0\crs\bin\oifcfg setif –global 'Local Area Connection 1'/10.2.166.0:public
However, it is common practice on Windows to rename the interfaces to use names that are more meaningful, such as renaming them to 'Public' and 'Private'. If interface names are renamed after CRS is installed, then you will need to run 'oifcfg' to delete the old interface and add the new one back in, as described above.
You can view the available interface names on each node by running the command:
oifcfg iflist
This command must be run on each node, as the 'iflist' option is showing the interface names that exist at the operating system level on that particular node. On the other hand, commands such as 'oifcfg getif', 'oifcfg delif' and 'oifcfg setif' are actually reading/updating the OCR, which is a shared resource. So these commands need only be run one time, and should be runnable from any node in the cluster.
Ramifications of Changing Interface Names Using oifcfg
The ramifications of changing the interface names depends on which name you are changing, and whether or not you are also changing the IP address. In cases where only the interface names are being changed, the ramifications are minor. If you change the name for the Public Interface that is stored in the OCR, you will also need to modify the nodeapps for each node. Therefore, the nodeapps will have to be brought down in order for this change to take effect. See Note 276434.1 for more details on changing the nodeapps to use a new public interface name.
For the Private interface, the database will use the interface stored in the OCR and defined as a 'cluster_interconnect' for cache fusion traffic. You will be able to see this at startup in the alert log, after the parameter listing - for example:
Cluster communication is configured to use the following interface(s) for this instance
192.168.1.1
If this is incorrect, then once you have corrected the entries stored in the OCR (by using 'oifcfg' as described in this note) you will have to restart the instance in order for it to re-read the OCR and pick up the correct network. This applies to ASM instances and Database instances alike.
Note 1: If you intend to change the actual IP addresses for the interconnect, this should be done while the CRS stack is down, in order to prevent node evictions. However, the CRS stack must be running in order to run the 'oifcfg' utility. Once the IP addresses are changed, and the CRS stack has been brought back up, you can then use 'oifcfg' to change the information stored in the OCR. At that point, the instances can then be started.
Note 2: On Windows systems, after shutting down the instance, you will also need to stop/restart the OracleService<SID> (or OracleASMService<ASMSID> before the OCR will be re-read.
For additional information on these commands for 10gR1, refer to:
Oracle® Real Application Clusters Administrator's Guide 10g Release 1 (10.1) Part No. B10765-01. Chapter 8, "Administrative Options", Administering System and Network Interfaces with the
OIFCFG (Oracle Interface Configuration) Tool
For 10gR2, refer to:
Oracle® Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide , 10g Release 2 (10.2) , Part Number B14197-03. Chapter 9.
For 11gR1, refer to:
Oracle® Clusterware Administration and Deployment Guide
11g Release 1 (11.1) , Part Number B28255-03, Appendix C
Oifcfg Usage:
oifcfg iflist
oifcfg setif {-node <nodename> | -global} {<if_name>/<subnet>:<if_type>}...
oifcfg getif [-node <nodename> | -global] [ -if <if_name>[/<subnet>] [-type <if_type>] ]
oifcfg delif [-node <nodename> | -global] [<if_name>[/<subnet>]]
oifcfg [-help]
<nodename> - name of the host, as known to a communications network
<if_name> - name by which the interface is configured in the system
<subnet> - subnet address of the interface
<if_type> - type of the interface { cluster_interconnect | public | storage }
发表评论
-
11gR2 RAC dbca无法发现ASM磁盘组
2012-07-30 11:28 1420安装好Grid Infrastructure和Database ... -
RAC dbca无法发现ASM磁盘组
2012-07-30 11:20 0查看( 1501 ) / 评论( 10 ) / 评分( 0 / ... -
RAC优化要点
2011-01-19 23:03 1931RAC环境下,DB CACHE的命中率对系统的性能影响 ... -
11gR2 cluvfy tools usage
2011-01-05 03:01 1252Note that the following only s ... -
配置11gR2 RAC SCAN
2011-01-02 21:11 343011G RAC scan即用DNA解析的I ... -
CRS-0215: Could not start resource 'ora..vip' [ID 356535.1]
2010-12-17 17:34 3338Oracle Server - Enterprise Edit ... -
Oracle RAC选件技术的价值何在?
2010-07-14 11:38 1647随着IT技术的发展,网格计算目前已经成为一个热点,它所带来的低 ... -
怎样修改 SCAN信息(来自于metalink)
2010-06-06 00:34 1543Applies to: Oracle Server ... -
Modifying the VIP or VIP Hostname of a 10g or 11g Oracle Clusterware Node [ID 27
2010-05-14 11:28 2335Applies to: Oracle Server ... -
RAC或OPS环境下重新创建控制文件 引自Metalink
2010-05-13 13:33 1639PURPOSE-------This article desc ... -
10gR2 RAC Install issues on Oracle EL5 or RHEL5 or SLES10 (VIPCA / SRVCTL / OUI
2010-04-30 12:04 1548Applies to: Oracle Server ... -
RAC环境下listener无法启动案例分析
2010-04-26 21:24 2452RAC系统重新配置listener后无法启动: [root@ ... -
CRS-1019: Resource ora.rac02.ons (application) cannot run on rac01 问题解决
2010-04-25 16:15 2638[root@rac01 bin]# ./crs_stat -t ... -
AIX集群修改IP步骤
2010-04-25 01:50 4333集群修改IP步骤 环境: AIX 5L HACMP ... -
关于虚拟 IP
2010-04-23 11:14 1805关于虚拟 IP10g 中为什么使用虚拟 IP (VIP)?为什 ... -
RAC Ocfs2文件系统常见问题解决方法
2010-01-11 14:28 1590现象一:mount -t ocfs2 -o datavolum ... -
启动OCFS2时出错:o2cb_ctl Unable load configuration file
2010-01-11 14:22 2151操作系统版本:RedHat-AS5 ... -
RAC User Equivalence Check Failed
2010-01-11 14:17 1610在使用SSH方式配置RAC时,可能会在检查用户等价时失败。 ... -
ORACLE RAC:监听原理 简介
2010-01-11 14:15 3632RAC1 RAC2 都需需要配置监听,各自监听自己的 实例 ... -
Oracle集群文件系统(OCFS2)用户指南
2010-01-11 14:02 2791http://oss.oracle.com/projects/ ...
相关推荐
Interconnect Noise Optimization in Nanometer Technologies.pdf,springer
This book is intended for working engineers in the field of digital design and signal integrity, with emphasis on interconnect design. The whole point of this book is to enable you to join the ...
Oracle Applications InterConnect User’s Guide Release 3.1.3
FPGA Interconnect Topologies Exploration
- CR#459427 / AR#30323 - Modified PHY Layer to detect a change in the port width override field and reinitialize when updated. - Messaging packets providing incorrect treq_byte_count value - ...
InfiniBand is a powerful new architecture designed to support I/O connectivity for the Internet infrastructure. InfiniBand is supported by all the major OEM server vendors as a means to expand beyond ...
Local area data networks,normally referred to simply as local area networks or LANs,are used to interconnect distributed communities of computer-based DTEs located within a single building or ...
TP2915 can support a variety of video resolution digital video input standards in 422 or 444 formats over 8, 16 or 24-bit interface with the embedded synchronization (EAV/SAV) header or explicit sync...
9.7 High-Density Interconnect/Microvia Materials / 9.13 9.8 CAF Growth / 9.15 9.9 Electrical Performance / 9.22 References / 9.33 Chapter 10. The Impact of Lead-Free Assembly on Base Materials 10.1 ...
With the combination of the centralized and distributed control of the software-defined optical networks, the proposed interconnect can achieve unprecedented flexibility in dealing with both mice and...
OSI(Open System Interconnect)是传统的开放式系统互连参考模型,是一种通信协议的7层抽象的参考模型,其中每一层执行某一特定任务。该模型的目的是使各种硬件在相同的层次上相互通信。这7层是:物理层、数据链路...
XILINX FPGA AXI总线互联IP datasheet, 用该IP可构建高速片上系统。内容包括了IP配置的说明等
We will then move to implementing routing in Angular 2, analyzing how to handle application states, and navigating from one component to another in depth. After this, the book features full coverage ...
Sufficient ports to enable distributed switching or centralized switching The plethora of high-speed interfaces available for tomorrow’s plug-in modules: Network interfaces (Fibre Channel, 10 ...
component interconnect Special Interest Group (PCI SIG) PCI Local Bus Specification, Revision 2.2 – FLEX 10KA devices include pull-up clamping diode, selectable on a pin-by-pin basis for 3.3-V PCI ...
The point is that in order to interconnect systems, as an architect, you’re better off using standard methods that allow for a faster adoption of your technology. In particular, APIs allow for the ...
We will then move to implementing routing in Angular 2, analyzing how to handle application states, and navigating from one component to another in depth. After this, the book features full coverage ...
11gR2 Grid Infrastructure Redundant Interconnect and ora.cluster_interconnect.haip [ID 1210883.1] This document is intended for RAC Database Administrators and Oracle Support engineers.
Typical communication technologies to interconnect Electronic Control Units (ECUs) are Lo- cal Interconnect Network (LIN) [LIN10], Controller Area Network (CAN) [CAN91], FlexRay (FR) [Fle10], Media ...