RAC 11g2: To Change VIP or HOSTNAME in Oracle 11gR2 Clusterware Node:

RAC 11g2: To Change VIP or HOSTNAME in Oracle 11gR2 Clusterware Node:

Posted on October 26, 2013 by Sakthi

Reasons to change the VIP or HOSTNAME in Oracle 11gR2 Clusterware Node:

– Change of location of Data centers
– Change of ip addresses in the Data centers
– VIP or HOSTNAME is mistyped in DNS, which requires correction

Note: In Oracle 11gR2, you no need to bring down the Database or ASM instance for this change.

Prerequiste:
– The Clusterware stack on the nodes should be up and running.
– nodeapps (VIP / LISTENER / ONS / GSD) should not be running. VIP can be changed while nodeapps are up, but still you need
to restart the nodeapps to make new changes to take effect.

Steps to Change VIP or HOSTNAME in Oracle 11gR2 Clusterware Node:

– Step#1: First note down the current configuration (hostname/VIP/subnetMask/interfaceName). Use the below srvctl command.

srvctl config nodeapps -n <nodeName> -a

– Step#2: Write down the new configuration (VIP/Hostname). BE CAUTIOUS to avoid rework.

– Step#3: Stop the nodeapps using the below srvctl command.

srvctl stop nodeapps -n <nodeName>

– Step#4: Optional. If you wish, disable the nodeapps to avoid getting restarted using the below srvctl command.

srvctl disable nodeapps -n <nodeName>

– Step#5: Don’t forget to Change this in the host file.

– Step#6: a) Now, change the VIP address using the below srvctl command.

srvctl modify nodeapps -n [-A ]

option description briefly: -n Node name. -A The node level VIP address
It will look like this samples:

 

– srvctl modify nodeapps -n gridnode1 -A 192.171.2.153/255.255.255.0/ethnt0 (VIP change)
– srvctl modify nodeapps -n gridnode1 -A gridnode1-v/255.255.255.0/ethnt0 (Hostname
change)
Note: You no need to give together the hostname and VIP address. Either one of the former would be sufficient as
both resolve to one another in srvctl. Also make run this command as root user.

– Step#6: Verify your change by running the below command.

srvctl config nodeapps -n <nodeName> -a

– Step#7: Once you verify the change, start the nodeapps using the below command.

srvctl start nodeapps -n <nodeName>

– Step#8: Enable the nodeapps if it is disabled using the below command.

srvctl enable nodeapps -n <nodeName>

– Step#9: Make the VIP and HOSTNAME changes in the concern LISTENER.ORA and TNSNAMES.ORA files.

– Step#10: If required to change the network registered in OCR, please refer the metalink notes 283684.1 .