Shulou(Shulou.com)06/01 Report--

Oracle 11g modify RAC SCAN IP

In 11gR2, the feature of SCAN (Single Client Access Name) is introduced. The advantage of this feature is that a virtual service layer is added between the database and the client, that is, the so-called scan ip and scan ip listener. The client only needs to configure the tns information of scan ip, and connects to the background cluster database through scan ip listener. In this way, no matter whether the cluster database has the operation of adding or deleting nodes, it will not affect the client. When a client application uses SCAN ip to access the database, scan listener forwards the connection to local listener.

Ip information related to SCAN ip is initialized when the SCAN resource is created. Without using GNS: any changes to SCAN in DNS and / etc/hosts are not automatically synchronized to Clusterware but are manually updated. Here are the specific steps for modifying scan ip:

1 View the status information of scan ip:

Grid@rac1:/home/grid > srvctl config scan

SCAN name: scan, Network: 1/10.250.7.0/255.255.255.0/eth0

SCAN VIP name: scan1, IP: / scan/10.250.7.210

Grid@rac1:/home/grid >

2 stop scan_listener and scan applications

Grid@rac1:/home/grid > srvctl stop scan_listener

Grid@rac1:/home/grid > srvctl stop scan

3 confirm the status of scan_listener,scan

Grid@rac1:/home/grid > srvctl status scan_listener

The SCAN listener LISTENER_SCAN1 is enabled

The SCAN listener LISTENER_SCAN1 is not running

Grid@rac1:/home/grid > srvctl status scan

SCAN VIP scan1 enabled

SCAN VIP scan1 is not running

Grid@rac1:/home/grid > crs_stat-t | grep scan

Ora.scan1.vip ora....ip.type OFFLINE OFFLINE

Grid@rac1:/home/grid >

Grid@rac1:/home/grid >

Grid@rac1:/home/grid > crs_stat-t | grep lsnr

Ora....ER.lsnr ora....er.type ONLINE ONLINE rac1

Ora....N1.lsnr ora....er.type OFFLINE OFFLINE

Ora....C1.lsnr application ONLINE ONLINE rac1

Ora....C2.lsnr application ONLINE ONLINE rac2

4 modify the ip corresponding to scan in the / etc/hosts file of all nodes:

10.250.7.141 scan

10.250.7.142 scan

10.250.7.143 scan

Grid@rac1:/home/grid > srvctl modify scan-h

Modify the SCAN name.

Usage: srvctl modify scan-n

-n qualified SCAN name of the domain name

-h output usage

Grid users do not have the right to change scan ip and must use root permissions

[root@rac1] # / opt/11202/11.2.0/grid/bin/srvctl modify scan-n scan

5 after the change, confirm:

[root@rac1 ~] # / opt/11202/11.2.0/grid/bin/srvctl config scan

SCAN name: scan, Network: 1/10.250.7.0/255.255.255.0/eth0

SCAN VIP name: scan1, IP: / scan/10.250.7.141 srvctl start scan

Grid@rac1:/home/grid > srvctl start scan_listener

7 confirm the status of scan and scan_listener.ora:

Grid@rac1:/home/grid > crs_stat-t | grep scan

Ora.scan1.vip ora....ip.type ONLINE ONLINE rac2

Grid@rac1:/home/grid > crs_stat-t | grep lsnr

Ora....ER.lsnr ora....er.type ONLINE ONLINE rac1

Ora....N1.lsnr ora....er.type ONLINE ONLINE rac2

Ora....C1.lsnr application ONLINE ONLINE rac1

Ora....C2.lsnr application ONLINE ONLINE rac2

Conduct a ping test www.2cto.com

Grid@rac1:/home/grid > ping 10.250.7.141

PING 10.250.7.141 (10.250.7.141) 56 (84) bytes of data.

64 bytes from 10.250.7.141: icmp_seq=1 ttl=64 time=1.52 ms

64 bytes from 10.250.7.141: icmp_seq=2 ttl=64 time=0.226 ms

-10.250.7.141 ping statistics-

2 packets transmitted, 2 received, 0% packet loss, time 1000ms

Rtt min/avg/max/mdev = 0.226 ms 0.873 ms 1.520 Universe

Grid@rac1:/home/grid > ping 10.250.7.142

PING 10.250.7.142 (10.250.7.142) 56 (84) bytes of data.

Unlike modifying private ip and vip, modifying scan ip does not need to stop the database instance, asm or restart crs, which is relatively simple!

After changing the IP, you need to restart the listening or cluster.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.