客户端使用 VIP（虚拟 IP）连接 Oracle 数据库的版本为 10g 和 11g 的集群环境。这些虚拟 IP 是和虚拟主机名对应的静态 IP 地址并且通过 DNS 解析（除非您使用了 11gR2 GNS）。

在安装 Oracle 集群管理软件时，用户会被要求为集群中的每一个节点输入一个虚拟 IP 和虚拟主机名。这些信息会被记录在 OCR (Oracle Cluster Registry)中，而且 HA 框架中的不同组件会依赖于这些 VIP。如果出于某种原因，需要修改 VIP、VIP 对应的主机名或者公网的子网、网络掩码等信息，请按照本文介绍的过程。

 
  如果修改涉及到集群私网，请参考  
  Note 283684.1

详细信息

情况1. 修改公网对应的主机名

集群公网对应的主机名是在安装时输入的，并且被记录在 OCR 中。这个主机名在安装之后是不能修改的。唯一的修改方法是删除节点，修改主机名，之后将节点重新添加到集群，或者直接重新安装集群软件，并完成后续的克隆配置。

情况2. 只修改公网 IP或者VIP，但是不修改网卡、子网或网络掩码信息，或者只是修改MAC地址，而不需要修改其他信息

如果只需要修改公网 IP 地址或者VIP，而且新的地址仍然在相同的子网和相同的网络接口上，或者只是修改公网IP的MAC地址，IP/interface/subnet/netmask仍旧保持不变，集群层面不需要做任何修改，所有需要的修改是在 OS 层面反映 IP 地址的变化。

1. 关闭 Oracle 集群管理软件
2. 在网络层面，DNS 和 /etc/hosts 文件中修改 IP 地址，或者直接修改MAC地址
3. 重新启动 Oracle 集群管理软件

以上的修改可以使用滚动的方式完成，例如：每次修改一个节点。

情况3. 修改公网网卡，子网或网络掩码信息

如果修改涉及到了不同的子网（网络掩码）或者网卡，需要将 OCR 中已经存在的网卡信息删除并重新添加新的信息。在以下的示例中子网从 10.2.156.0 被修改为 10.2.166.0，需要执行两个步骤 –首先‘delif’，接下来 ‘setif’：

 
  % $CRS_HOME/bin/oifcfg/oifcfg delif -global [/] 
  
   % $CRS_HOME/bin/oifcfg/oifcfg setif -global /:public 
  
   例如: 
  
   % $CRS_HOME/bin/oifcfg delif -global eth0/10.2.156.0  
  
   % $CRS_HOME/bin/oifcfg setif -global eth0/10.2.166.0:public

然后，在操作系统层面进行修改。除非 OS 层面的修改需要重新启动节点，否则不需要重启 Oracle 集群管理软件。修改可以使用滚动的方式完成。

一旦公网信息被修改，与其相关的 VIP 和 SCAN VIP 也需要修改，请参考情况4和情况5。

 
  注意：对于11gR2，上面命令要求集群在所有节点运行，否则报错PRIF-33 和 PRIF-32，比如： 
  
   [grid@racnode1 bin]$ ./oifcfg delif -global eth0/192.168.1.0 
  
   PRIF-33: Failed to set or delete interface because hosts could not be discovered 
  
   CRS-02307: No GPnP services on requested remote hosts. 
  
   PRIF-32: Error in checking for profile availability for host racnode2 
  
   CRS-02306: GPnP service on host "racnode2" not found.

情况4. 修改 VIP 相关的公网信息

准备修改VIP

一般而言，只有 10.2.0.3 之前的版本需要完全的停机。从 10.2.0.3 开始，ASM 和数据库实例对 VIP 资源的依赖关系已经被删除，所以修改 VIP 不需要停止 ASM 和数据库实例，只有当修改 VIP 时产生的客户端连接会受影响。如果修改只涉及到特定的节点，那么只有连接到对应节点的客户端链接在修改时会受影响。

首先，请参考情况3以确保公网信息被修改。如果在 OS 层面的网络修改后发生了节点或者集群管理软件重启，VIP 将不会被启动，请跳到步骤“修改 VIP 和相关属性”。

获得当前的 VIP 配置

1. 获取当前设置
对于版本 10g 和 11gR1, 使用 Oracle 集群管理软件的拥有者执行下面的命令：

 
  $ srvctl config nodeapps -n -a 
  
   例如： 
  
   $ srvctl config nodeapps -n racnode1 -a 
  
   VIP exists.: /racnode1-vip/101.17.80.184/255.255.254.0/eth1

对于版本 11gR2, 使用 Grid Infrastructure 的拥有者执行下面的命令：

 
  $ srvctl config nodeapps -a 
  
   例如： 
  
   $ srvctl config nodeapps -a 
  
   Network exists: 1/101.17.80.0/255.255.254.0/eth1, type static 
  
   VIP exists: /racnode1-vip/101.17.80.184/101.17.80.0/255.255.254.0/eth1, hosting node racnode1 
  
   VIP exists: /racnode2-vip/101.17.80.186/101.17.80.0/255.255.254.0/eth1, hosting node racnode2

2. 验证 VIP 状态

 
  版本 10.2 和 11.1： 
  
   $ crs_stat -t  
  
   版本 11.2： 
  
   $ crsctl stat res -t 
  
   - 以上命令应该显示 VIPs 状态为 ONLINE 
  
   $ ifconfig -a 
  
   (HP 平台请使用 netstat –in, Windows 平台请使用 ipconfig /all) 
  
   - VIP 逻辑网卡对应公网网卡

停止资源

3. 停止 nodeapps 资源 (如果有必要的话，停止存在依赖关系的 ASM 和数据库资源):

对于版本 10g 和 11gR1, 使用 Oracle 集群管理软件的拥有者执行下面的命令：

 
  $ srvctl stop instance -d -i    (对于 10.2.0.3 及以上版本，可以忽略) 
  
   $ srvctl stop asm -n                      (对于 10.2.0.3 及以上版本，可以忽略) 
  
   $ srvctl stop nodeapps -n  
  
   例如：  
  
   $ srvctl stop instance -d RACDB -i RACDB1 
  
   $ srvctl stop asm -n racnode1 
  
   $ srvctl stop nodeapps -n racnode1

对于版本 11gR2, 使用 Grid Infrastructure 的拥有者执行下面的命令：

 
  $ srvctl stop instance -d -n    (可以忽略) 
  
   $ srvctl stop vip -n -f 
  
   例如： 
  
   $ srvctl stop instance -d RACDB -n racnode1 
  
   $ srvctl stop vip -n racnode1 -f

 
  注意1: 对于版本 11gR2，需要使用 -f 选项停止 listener 资源，否则会报以下错误： 
  
   PRCR-1014 : Failed to stop resource ora.racnode1.vip 
  
   PRCR-1065 : Failed to stop resource ora.racnode1.vip 
  
   CRS-2529: Unable to act on 'ora.racnode1.vip' because that would require stopping or relocating 'ora.LISTENER.lsnr', but the force option was not specified 
  
   ...

4. 验证 VIP 现在处于 OFFLINE 状态，并且 VIP 不再绑定到公网网卡

 
  $ crs_stat -t (对于版本 11gR2，使用命令 $ crsctl stat res –t) 
  
   $ ifconfig -a 
  
   (HP 平台请使用 netstat –in, Windows 平台请使用 ipconfig /all)

修改 VIP 和相关属性

5. 确定新的 VIP 地址/子网/网络掩码或者 VIP 对应的主机名，在 OS 层面修改网络配置信息，确认新的 VIP 地址应经注册到 DNS 或者确认 /etc/hosts 文件（Unix/Linux 平台），\WINDOWS\System32\drivers\etc\hosts 文件（Windows平台）已经被修改。如果网卡信息被修改，确认在修改之前新的网卡在服务器上已经可用。

 
  例如： 
  
   新VIP 地址：110.11.70.11 racnode1-nvip 
  
   新子网信息：110.11.70.0 
  
   新网络掩码：255.255.255.0 
  
   新网卡：eth2

6. 使用 root 用户修改 VIP 资源：

 
  # srvctl modify nodeapps -n -A //<[if1[if2...]]> 
  
   例如： 
  
   # srvctl modify nodeapps -n racnode1 -A racnode1-nvip/255.255.255.0/eth2

 注意 1：从版本 11.2 开始，VIP 依赖于 network 资源(ora.net1.network)，OCR 只记录 VIP 主机名或者 VIP 资源相关的 IP 地址。集群公网的属性（子网/网络掩码）通过网络资源记录。当 nodeapps 资源被修改后，network资源(ora.net1.network)相关的属性也会随之被修改。 
 从 11.2.0.2 开始，如果只修改子网/网络掩码信息，网络资源可以通过以下的 srvctl modify network 命令直接修改。 
 使用 root 用户：
 # srvctl modify network -k ] [-S /[/if1[|if2...]] 
 例如：
 # srvctl modify network -k 1 -S 110.11.70.0/255.255.255.0/eth2 
 如果其他属性没有变化，不需要修改 VIP 或 SCAN VIP。 
 注意 2：在12.1.0.1的版本上由于Bug 16608577 - CANNOT ADD SECOND PUBLIC INTERFACE IN ORACLE 12.1 ,srvctl modify network 的命令会失败并提示： 
 # srvctl modify network -k 1 -S 110.11.70.0/255.255.255.0/eth2
PRCT-1305 : The specified interface name "eth2" does not match the existing network interface name "eth1" 
 需要通过以下workaround来解决： 
 # srvctl modify network -k 1 -S 110.11.70.0/255.255.255.0
 # srvctl modify network -k 1 -S 110.11.70.0/255.255.255.0/eth2 

* 一个 11gR2 修改 VIP 主机名，但是不修改 IP 地址的例子。

 
  例如：只把 VIP 主机名从 racnode1-vip 修改为 racnode1-nvip，IP 地址和其他属性保持不变。 
  
   如果 IP 地址保持不变，以上的命令将不会改变命令‘crsctl stat res ora.racnode1.vip -p’的输出中项目 USR_ORA_VIP 的值。请使用下面的命令： 
  
   # crsctl modify res ora.racnode1.vip -attr USR_ORA_VIP=racnode1-nvip 
  
   验证项目 USR_ORA_VIP 的改变： 
  
   # crsctl stat res ora.racnode1.vip -p |grep USR_ORA_VIP

 
  注意：对于 Windows 平台，如果网卡名中包含了空格，那么网卡名需要包含在双引号(")中。例如： 
  
   使用管理员用户或者软件安装用户： 
  
   > srvctl modify nodeapps -n racnode1 -A 110.11.70.11/255.255.255.0/"Local Area Connection 1"

7. 验证改变

 
  $ srvctl config nodeapps -n -a (10g and 11gR1) 
  
   $ srvctl config nodeapps -a (11gR2) 
  
   例如： 
  
   $ srvctl config nodeapps -n racnode1 -a 
  
   VIP exists.: /racnode1-nvip/110.11.70.11/255.255.255.0/eth2

重新启动资源

8. 启动 nodeapps 和其它资源

对于版本 10g 和 11gR1, 使用 Oracle 集群管理软件的拥有者执行下面的命令：

 
  $ srvctl start nodeapps -n         
  
   $ srvctl start asm -n                (对于 10.2.0.3 及以上版本，可以忽略) 
  
   $ srvctl start instance -d -i    (对于 10.2.0.3 及以上版本，可以忽略) 
  
   例如： 
  
   $ srvctl start nodeapps -n racnode1 
  
   $ srvctl start asm -n racnode1 
  
   $ srvctl start instance -d RACDB -i RACDB1

对于版本 11gR2, 使用 Grid Infrastructure 的拥有者执行下面的命令：

 $ srvctl start vip -n  
 $ srvctl start listener -n 
 $ srvctl start instance -d -n (可以忽略) 
例如：
 $ srvctl start vip -n racnode1 
 $ srvctl start listener -n racnode1
 $ srvctl start instance -d RACDB -n racnode1 

注意:如果网络的属性做了修改，比如netmask 等做了修改，需要重新启动nodeapps

9. 验证新的 VIP 状态为 ONLINE 并且已经绑定到集群公网网卡

 
  $ crs_stat -t (对于版本 11gR2，使用命令 $ crsctl stat res –t) 
  
   $ ifconfig -a 
  
   (HP 平台请使用 netstat –in, Windows 平台请使用 ipconfig /all)

10. 如果集群中的其它节点也需要类似的改变，请重复同样的步骤。

其它

11. 如果需要，修改 listener.ora, tnsnames.ora 和 LOCAL_LISTENER/REMOTE_LISTENER 参数反应 VIP 的改变。

 
  注意： ASM和DB实例的LOCAL_LISTENER参数，是GI自动设置的。VIP的改变，LOCAL_LISTENER会自动识别，并生效。但是由于Bug 22824602，一些特定情况下。 LOCAL_LISTENER参数没有反应 VIP 的改变。workaround解决方法是重启受影响的节点的集群软件。 
 

情况5：修改 SCAN VIP 相关的公网信息

对于 11gR2 Grid Infrastructure，客户端可以通过 SCAN 和 SCAN VIP 连接数据库。请参考下面的 Note 修改 SCAN VIP。

Note 952903.1 How to update the IP address of the SCAN VIP resources (ora.scan.vip)
Note 972500.1 How to Modify SCAN Setting or SCAN Listener Port after Installation

 
  注意：如果需要回退修改，那么用原始值替换新值，然后重新运行命令。 
 

参考

NOTE:283684.1 - How to Modify Private Network Information in Oracle Clusterware
NOTE:952903.1 - How to Update the IP Address of the SCAN VIP Resources (ora.scan{n}.vip)

How to Modify Public Network Information including VIP in Oracle Clusterware (文档 ID 276434.1)

In this Document

Purpose

Scope

Details

Case I. Changing public hostname

Case II. Changing public IP or VIP only without changing interface, subnet or netmask or changing MAC address only without changing anything else

Case III. Changing public network interface, subnet or netmask

Case IV. Changing VIPs associated with public network change

Planning for VIP changes

Gathering Current VIP Configuration

Stopping Resources

Modifying VIP and Its Associated Attributes

Restarting Resources

Others

Case V. Change SCAN VIP associated with public network change

References

APPLIES TO:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 12.2.0.1 [Release 10.1 to 12.2]

Information in this document applies to any platform.

PURPOSE

The purpose of this note is to illustrate how to change a public hostname, public IP, a Virtual IP Address (VIP), VIP hostname or other VIP attributes in an Oracle Clusterware/Grid Infrastructure environment.

SCOPE

Oracle Database 10g and 11g use VIPs (Virtual IP) in clustered environments for clients to connect to the database. These VIPs are static IP addresses associated with (virtual) hostnames and resolved through DNS (except when using 11gR2 GNS).

During the installation of the Oracle Clusterware users are prompted to enter a Virtual IP and Virtual hostname for each of the node in the cluster. These are stored within the OCR (Oracle Cluster Registry) and different components within the HA framework depend on these VIPs. If for some reason the need arises to change either the VIP, the VIP hostname, or the subnet, netmask etc, this procedure should be followed.

For changes associated with private network/cluster interconnect, please refer to Note 283684.1

DETAILS

Case I. Changing public hostname

Public hostname is recorded in OCR, it is entered during installation phase. It can not be modified after the installation. The only way to modify public hostname is by deleting the node, then adding the node back with a new hostname, or reinstalling the clusterware or following the clone procedure to reconfigure the clusterware.

Case II. Changing public IP or VIP only without changing interface, subnet or netmask or changing MAC address only without changing anything else

If the change is only public IP or VIP address and the new ones are still in the same subnet, same interface, or if the change is only for public IP MAC address, IP/interface/subnet/netmask all remain the same, nothing needs to be done at clusterware layer, all changes need to be done at OS layer to reflect the change.

1. Shutdown Oracle Clusterware stack

2. Modify the IP address at network layer, DNS and /etc/hosts file to reflect the change or modify the MAC address at network layer

3. Restart Oracle Clusterware stack

Above change can be done in rolling fashion, eg: one node at a time.

Case III. Changing public network interface, subnet or netmask

If the change involves different subnet(netmask) or interface, delete the existing interface information from OCR and add it back with the correct information is required. In the example here, the subnet is changed from 10.2.156.0 to 10.2.166.0 via two separate commands - first a 'delif' followed by a 'setif':

% $CRS_HOME/bin/oifcfg/oifcfg delif -global [/]

% $CRS_HOME/bin/oifcfg/oifcfg setif -global /:public

For example:

% $CRS_HOME/bin/oifcfg delif -global eth0/10.2.156.0

% $CRS_HOME/bin/oifcfg setif -global eth0/10.2.166.0:public

Then make the change at OS layer. There is no requirement to restart Oracle clusterware unless OS change requires a node reboot. This can be done in rolling fashion.

Once public network is changed, its associated VIP and SCAN VIP are also required to change, refer to CASE IV and CASE V.

Note: for 11gR2, above command requires clusterware RUNNING on ALL nodes, otherwise PRIF-33 and PRIF-32 will be reported, i.e.

[grid@racnode1 bin]$ ./oifcfg delif -global eth0/192.168.1.0

PRIF-33: Failed to set or delete interface because hosts could not be discovered

CRS-02307: No GPnP services on requested remote hosts.

PRIF-32: Error in checking for profile availability for host racnode2

CRS-02306: GPnP service on host "racnode2" not found.

Case IV. Changing VIPs associated with public network change

Planning for VIP changes

In general, a complete outage is only required for pre-10.2.0.3 release. From 10.2.0.3 onwards, the ASM/database instance dependency on the VIP resource is removed, so the VIP could be modified without having to take down the ASM/database instance, only client connections to the database will be affected when VIP is down. If the modification is a node specific, then only connection to that node will be affected during the time of change.

Please follow Case III to ensure public network changes are made first. If there is a node reboot or Clusterware restart after the OS network change, vip will not start, please skip to step "Modifying VIP and its Associated Attributes".

Gathering Current VIP Configuration

1. Gather the existing setup

for 10g and 11gR1, as Oracle Clusterware owner:

$ srvctl config nodeapps -n -a

eg:

$ srvctl config nodeapps -n racnode1 -a

VIP exists.: /racnode1-vip/101.17.80.184/255.255.254.0/eth1

for 11gR2, as Grid Infrastructure owner:

$ srvctl config nodeapps -a

eg:

$ srvctl config nodeapps -a

Network exists: 1/101.17.80.0/255.255.254.0/eth1, type static

VIP exists: /racnode1-vip/101.17.80.184/101.17.80.0/255.255.254.0/eth1, hosting node racnode1

VIP exists: /racnode2-vip/101.17.80.186/101.17.80.0/255.255.254.0/eth1, hosting node racnode2

2. Verify VIP status

10.2 and 11.1:

$ crs_stat -t

11.2:

$ crsctl stat res -t

- it should show VIPs are ONLINE

$ ifconfig -a

(netstat -in for HP and ipconfig /all for Windows)

- VIP logical interface is bound to the public network interface

Stopping Resources

3. Stop the nodeapps resources (and all dependent resources ASM/DB only if required):

10g and 11gR1, as Oracle Clusterware owner:

$ srvctl stop instance -d -i (optional for 10.2.0.3+)

$ srvctl stop asm -n (optional for 10.2.0.3+)

$ srvctl stop nodeapps -n

eg,

$ srvctl stop instance -d RACDB -i RACDB1

$ srvctl stop asm -n racnode1

$ srvctl stop nodeapps -n racnode1

11gR2, as Grid Infrastructure owner:

$ srvctl stop instance -d -n (optional)

$ srvctl stop vip -n -f

eg,

$ srvctl stop instance -d RACDB -n racnode1

$ srvctl stop vip -n racnode1 -f

Note 1: The -f option is required for 11gR2 to stop listener resource, otherwise following error will occur:

PRCR-1014 : Failed to stop resource ora.racnode1.vip

PRCR-1065 : Failed to stop resource ora.racnode1.vip

CRS-2529: Unable to act on 'ora.racnode1.vip' because that would require stopping or relocating 'ora.LISTENER.lsnr', but the force option was not specified

...

4. Verify VIP is now OFFLINE and the interface is no longer bound to the public network interface

$ crs_stat -t (or $ crsctl stat res -t for 11gR2)

$ ifconfig -a

(netstat -in for HP and ipconfig /all for windows)

Modifying VIP and Its Associated Attributes

5. Determine the new VIP IP/subnet/netmask or VIP hostname, make the network change on OS first, ensure the new VIP is registered in DNS or modified in /etc/hosts (for Unix/Linux) and \WINDOWS\System32\drivers\etc\hosts file (for Windows). If the network interface is changed, ensure the new interface is available on the server before proceeding with the modification.

For example:

New VIP is: 110.11.70.11 racnode1-nvip

new subnet is 110.11.70.0

new netmask is 255.255.255.0

new interface is eth2

6. Modify the VIP resource, as root user:

# srvctl modify nodeapps -n -A //<[if1[if2...]]>

eg:

# srvctl modify nodeapps -n racnode1 -A racnode1-nvip/255.255.255.0/eth2

Note 1 : Starting with 11.2, the VIPs depend on the network resource (ora.net1.network), the OCR only records the VIP hostname or the IP address associated with the VIP resource. The network attributes (subnet/netmask/interface) are recorded with the network resource. When the nodeapps resource is modified, the network resoure(ora.net1.network) attributes are also modified implicitly.

From 11.2.0.2 onwards, if only subnet/netmask/interface change is required, network resource can be modified directly via srvctl modify network command.

as root user:

# srvctl modify network -k ] [-S /[/if1[|if2...]]

eg:

# srvctl modify network -k 1 -S 110.11.70.0/255.255.255.0/eth2

There is no need to modify VIP or SCAN if other attributes are not changed.

Note 2: For 12.1.0.1 release, due to unpublished Bug 16608577 - CANNOT ADD SECOND PUBLIC INTERFACE IN ORACLE 12.1, the srvctl modify network command fails with:

# srvctl modify network -k 1 -S 110.11.70.0/255.255.255.0/eth2

PRCT-1305 : The specified interface name "eth2" does not match the existing network interface name "eth1"

Workaround is to modify network resource with an empty interface name, then modify it again with the desired interface name, eg:

# srvctl modify network -k 1 -S 110.11.70.0/255.255.255.0

# srvctl modify network -k 1 -S 110.11.70.0/255.255.255.0/eth2

The bug has been fixed in 12.1.0.2 and above.

* A special case for 11gR2 modifying the VIP hostname only without changing the IP address.

For example: only VIP hostname changes from racnode1-vip to racnode1-nvip, IP and other attributes remain the same.

If IP address is not changed, above modify command will not change the USR_ORA_VIP value in 'crsctl stat res ora.racnode1.vip -p' output. Please use the following command:

# crsctl modify res ora.racnode1.vip -attr USR_ORA_VIP=racnode1-nvip

Verify the changes for USR_ORA_VIP field:

# crsctl stat res ora.racnode1.vip -p |grep USR_ORA_VIP

Note: For Windows platform, the interface name needs to be in quote (") if there is a space in between, eg:

As administrator user or software install user:

> srvctl modify nodeapps -n racnode1 -A 110.11.70.11/255.255.255.0/"Local Area Connection 1"

7. Verify the change

$ srvctl config nodeapps -n -a (10g and 11gR1)

$ srvctl config nodeapps -a (11gR2)

eg:

$ srvctl config nodeapps -n racnode1 -a

VIP exists.: /racnode1-nvip/110.11.70.11/255.255.255.0/eth2

Restarting Resources

8. Start the nodeapps and the other resources

10g and 11gR1, as Oracle Clusterware owner:

$ srvctl start nodeapps -n

$ srvctl start asm -n (optional for 10.2.0.3+)

$ srvctl start instance -d -i (optional for 10.2.0.3+)

eg:

$ srvctl start nodeapps -n racnode1

$ srvctl start asm -n racnode1

$ srvctl start instance -d RACDB -i RACDB1

11gR2, as Grid Infrastructure owner:

$ srvctl start vip -n

$ srvctl start listener -n

$ srvctl start instance -d -n (optional)

eg,

$ srvctl start vip -n racnode1

$ srvctl start listener -n racnode1

$ srvctl start instance -d RACDB -n racnode1

Note: if the network attributes are changed, i.e. netmask changed, restart the nodeapps

9. Verify the new VIP is ONLINE and bind to the public network interface

$ crs_stat -t (or $ crsctl stat res -t for 11gR2)

$ ifconfig -a

(netstat -in for HP or ipconfig /all for windows)

10. Repeat the same steps for the rest nodes in the cluster only if the similar change is required.

Others

11. Modify listener.ora, tnsnames.ora and LOCAL_LISTENER/REMOTE_LISTENER parameter to reflect the VIP change if necessary.

Note , LOCAL_LISTENER for ASM and DB are set automatically by Grid Infrastructure. The VIP change in LOCAL_LISTENER should take effect automatically. Due to Bug 22824602, under some race condition, the LOCAL_LISTENER for ASM instance might not reflect the VIP change. The workaround is to restart the Clusterware on the affected node.

Case V. Change SCAN VIP associated with public network change

With Grid Infrastructure 11gR2, SCAN and SCAN VIP are introduced for client connections. To modify the SCAN VIP, please refer to

Note 952903.1 How to update the IP address of the SCAN VIP resources (ora.scan.vip)

Note 972500.1 How to Modify SCAN Setting or SCAN Listener Port after Installation

Note: if rolling back the change is required, repeat the commands which have been run, replace the new value with original value to restore the original configuration.

REFERENCES

NOTE:952903.1 - How to update the IP address of the SCAN VIP resources (ora.scan{n}.vip)

NOTE:283684.1 - How to Modify Private Network Information in Oracle Clusterware

小麦苗课程

小麦苗课堂开课啦，如下是现有的课程，欢迎咨询小麦苗：

课程名称	课时	上课时间	价格
OCP（从入门到专家）	每年1期，35课时左右/期	20：00-22：00	1588(可优惠)
OCM认证	每年N期，9课时/期	20：00-22：00	22888
高可用课程（rac+dg+ogg）	每年1期，20课时左右/期	20：00-22：00	1888(可优惠)
Oracle初级入门	每年1期，15课时左右/期	20：00-22：00	800
Oracle健康检查脚本	可微信或微店购买。		88
Oracle数据库技能直通车	包含如下3个课程： ①《11g OCP网络课程培训》（面向零基础）价值1600元 ②《11g OCM网络班课程培训》（Oracle技能合集）价值10000+元 ③《RAC + DG + OGG 高可用网络班课程》价值2000元以上3个课程全部打包只要5888，只要5888所有课程带回家，终身指导！所有课程都是在线讲课，不是播放视频，课件全部赠送！注意：以上OCP和OCM课程只包括培训课程，不包括考试费用。OCM提供培训+视频，但是不提供练习环境和资料。报名一次，OCP和高可用的课程可以免费终身循环听课。		5888
OCP+高可用（rac+dg+ogg）	报名OCP+高可用课程，可以优惠300元，优惠后的价格为3188.		3188(可优惠)

注意：

1、每次上课前30分钟答疑。

2、OCM实时答疑，提供和考试一样的练习模拟环境，只要按照老师讲的方式来练习，可以保证100%通过。

3、授课方式：YY语音网络直播讲课（非视频） + QQ互动答疑 + 视频复习。

4、OCP课时可以根据大家学习情况进行增加或缩减。

5、以上所有课程均可循环听课。

6、12c OCM课程私聊。

7、Oracle初级入门课程，只教大家最实用+最常用的Oracle操作维护知识。

8、以上所有课程，可以加小麦苗微信（lhrbestxh）或QQ（646634621）详聊，优惠多多。

培训项目	连接地址
DB笔试面试历史连接	http://mp.weixin.qq.com/s/Vm5PqNcDcITkOr9cQg6T7w
OCP培训说明连接	https://mp.weixin.qq.com/s/2cymJ4xiBPtTaHu16HkiuA
OCM培训说明连接	https://mp.weixin.qq.com/s/7-R6Cz8RcJKduVv6YlAxJA
高可用（RAC+DG+OGG）培训说明连接	https://mp.weixin.qq.com/s/4vf042CnOdAD8zDyjUueiw
OCP最新题库解析历史连接（052）	http://mp.weixin.qq.com/s/bUgn4-uciSndji_pUbLZfA
微店地址	https://weidian.com/s/793741433?wfr=c&ifr=shopdetail

About Me

.............................................................................................................................................

● 本文作者：小麦苗，部分内容整理自网络，若有侵权请联系小麦苗删除

● 本文在itpub（http://blog.itpub.net/26736162/abstract/1/）、博客园（http://www.cnblogs.com/lhrbest）和个人微信公众号（xiaomaimiaolhr）上有同步更新

● 本文itpub地址：http://blog.itpub.net/26736162/abstract/1/

● 本文博客园地址：http://www.cnblogs.com/lhrbest

● 本文pdf版、个人简介及小麦苗云盘地址：http://blog.itpub.net/26736162/viewspace-1624453/

● 数据库笔试面试题库及解答：http://blog.itpub.net/26736162/viewspace-2134706/

● DBA宝典今日头条号地址：http://www.toutiao.com/c/user/6401772890/#mid=1564638659405826

.............................................................................................................................................

● QQ群号：230161599（满）、618766405

● 微信群：可加我微信，我拉大家进群，非诚勿扰

● 联系我请加QQ好友（646634621），注明添加缘由

● 于 2018-07-01 06:00 ~ 2018-07-31 24:00 在魔都完成

● 最新修改时间：2018-07-01 06:00 ~ 2018-07-31 24:00

● 文章内容来源于小麦苗的学习笔记，部分整理自网络，若有侵权或不当之处还请谅解

● 版权所有，欢迎分享本文，转载请保留出处

.............................................................................................................................................

● 小麦苗的微店：https://weidian.com/s/793741433?wfr=c&ifr=shopdetail

● 小麦苗出版的数据库类丛书：http://blog.itpub.net/26736162/viewspace-2142121/

● 小麦苗OCP、OCM、高可用网络班：http://blog.itpub.net/26736162/viewspace-2148098/

.............................................................................................................................................

使用微信客户端扫描下面的二维码来关注小麦苗的微信公众号（xiaomaimiaolhr）及QQ群（DBA宝典）、添加小麦苗微信，学习最实用的数据库技术。

小麦苗的微信公众号小麦苗的DBA宝典QQ群2 小麦苗的微信二维码小麦苗的微店

.............................................................................................................................................

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/26736162/viewspace-2157362/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/26736162/viewspace-2157362/

声明：本文内容由网友自发贡献，不代表【wpsshop博客】立场，版权归原作者所有，本站不承担相应法律责任。如您发现有侵权的内容，请联系我们。转载请注明出处：https://www.wpsshop.cn/w/运维做开发/article/detail/976272

如何修改集群的公网信息（包括 VIP） (文档 ID 1674442.1)