Modify IP addresses (public ip, private ip, and virtual ip) under oracle RAC)

It is a good atmosphere to share the technology of modifying IP addresses (public ip, private ip, and virtual ip) under oracle RAC. oracle Group colleagues share the idea of modifying IP addresses under oracle rac, oracle started in 10 years (also passed the ocp certification in 11 years). Even though I have been dedicated to mysql, oracle cannot be spared. Take 3-node rac as An Example 1. preparation (1 ). SELECT INSTANCE_NUMBER, INSTANCE_NAME, HOST_NAME, VERSION, status from gv $ INSTANCE; INSTANCE_NUMBER INSTANCE_NAME HOST_NAME version status certificate -------------- certificate ------------ 1 testrac1 racnode1 10.2.0.4.0 OPEN 3 testrac3 racnode3 10.2.0.4.0 OPEN 2 testrac2 racnode2 10.2.0.4.0 OPEN * 3 node RAC environment (2 ). you need to modify the public ip, private ip, and vitual ip corresponding to node 3.. 2. step 1 ). shut down the database and CLUSTERWARE on instance 3 #/etc/init. d/init. crs stop (2 ). modify the/etc/hosts file on the three hosts and change the node 3 configuration to the target IP address (3 ). after you manually modify the IP address # ifconfig to modify the public ip address, you need to reconnect to node 3 with the new IP address to confirm that the public ip address and PRIVATEIP address are normal. (4) Check the network configuration and check the tnsnames. ora on each node and the remote_listener parameters in the database. If these configurations are configured through the host name, no modification is required. If the IP address is configured directly, modify it based on the new address of Node 3. (5) VIPCA starts VIPCA graphically on node 1 or node 2 using root to configure node 3VIP. If the changes in/etc/hosts are correct, no changes are required. Oracle will automatically find the corresponding new address. After you click "OK", Oracle will report an error during VIP reconfiguration because CLUSTERWARE on node 3 is not started. Ignore this error. (6) start CLUSTERWARE and database #/etc/init. d/init. crs start on node 3