On this activity we are going to rename the scan name on a Oracle 19c RAC environment.
We don’t want to change the IP’s, just the name.
| ORIGINAL NAME: | CLUSTER-ORA-SCAN2 |
| TARGET NAME: | CLUSTER-ORA2-SCAN |
First, you need to make sure new SCAN NAME is pingable from all RAC servers (to avoid name resolution issues)
1:- Check current configuration:
[oragrid@sever-ora21 ~]$ srvctl config scan
SCAN name: CLUSTER-ORA-SCAN2, Network: 1
Subnet IPv4: xx.xx.128.0/255.255.248.0/eth0, static
Subnet IPv6:
SCAN 1 IPv4 VIP: xx.xx.128.137
SCAN VIP is enabled.
SCAN 2 IPv4 VIP: xx.xx.128.138
SCAN VIP is enabled.
SCAN 3 IPv4 VIP: xx.xx.128.139
SCAN VIP is enabled.
[oragrid@sever-ora21 ~]$2:- Stop SCAN:
[oragrid@sever-ora21 ~]$ srvctl stop scan_listener
[oragrid@sever-ora21 ~]$ srvctl stop scan
[oragrid@sever-ora21 ~]$3:- Rename SCAN (as root):
[root@sever-ora21 ~]# srvctl modify scan -n CLUSTER-ORA2-SCAN
[root@sever-ora21 ~]#4:- Start and check:
[oragrid@sever-ora21 ~]$ srvctl start scan
[oragrid@sever-ora21 ~]$ srvctl start scan_listener
[oragrid@sever-ora21 ~]$ srvctl config scan
SCAN name: CLUSTER-ORA2-SCAN, Network: 1
Subnet IPv4: xx.xx.128.0/255.255.248.0/eth0, static
Subnet IPv6:
SCAN 1 IPv4 VIP: xx.xx.128.137
SCAN VIP is enabled.
SCAN 2 IPv4 VIP: xx.xx.128.138
SCAN VIP is enabled.
SCAN 3 IPv4 VIP: xx.xx.128.139
SCAN VIP is enabled.
[oragrid@sever-ora21 ~]$
that’s it!
Comments