1. Stop the SCAN
[grid@rac1 ~]$ srvctl stop scan_listener
[grid@rac1 ~]$ srvctl stop scan
2.Configure the new SCAN in your DNS, or /etc/hosts, or GNS and make sure that lookups are working for the new name.
[root@rac2 ~]# nslookup newscan.domain.com
3. Configure the Cluster to take the new VIPs
As root user on one of the cluster nodes:
[root@rac1 ~]# /u01/product/11.2.0/grid/bin/srvctl modify scan -n newscan.domain.com
4.As grid user on one of the cluster nodes:
[grid@rac1 ~]$ srvctl modify scan_listener -u
[grid@rac1 ~]$ srvctl start scan_listener
5.Verify that configuration:
[grid@rac1 ~]$ srvctl config scan
[grid@rac1 ~]$ srvctl stop scan_listener
[grid@rac1 ~]$ srvctl stop scan
2.Configure the new SCAN in your DNS, or /etc/hosts, or GNS and make sure that lookups are working for the new name.
[root@rac2 ~]# nslookup newscan.domain.com
3. Configure the Cluster to take the new VIPs
As root user on one of the cluster nodes:
[root@rac1 ~]# /u01/product/11.2.0/grid/bin/srvctl modify scan -n newscan.domain.com
4.As grid user on one of the cluster nodes:
[grid@rac1 ~]$ srvctl modify scan_listener -u
[grid@rac1 ~]$ srvctl start scan_listener
5.Verify that configuration:
[grid@rac1 ~]$ srvctl config scan
No comments:
Post a Comment