Shulou(Shulou.com)05/31 Report--

This article mainly explains "Oracle RAC how to modify Scan IP,Public IP", the content of the article is simple and clear, easy to learn and understand, the following please follow the editor's ideas slowly in depth, together to study and learn "Oracle RAC how to modify Scan IP,Public IP" bar!

1. Modify public ip

1. Close all instances ahead of time

Srvctl stop database-d XXX

2. Update the configuration of ocr network information, which is executed by root users.

Oifcfg getif

Oifcfg delif-global eth0/127.0.0.1

Oifcfg setif-global eth0/192.168.20.0:public

Srvctl config nodeapps-a

# # #

[root@stuaapp01 ~] # oifcfg getif

Eth2 192.168.10.0 global cluster_interconnect

Eth0 127.0.0.1 global public

[root@stuaapp01 ~] # oifcfg delif-global eth0/127.0.0.1

[root@stuaapp01 ~] # oifcfg setif-global eth0/192.168.20.0:public

[root@stuaapp01 ~] #

[root@stuaapp01 ~] # oifcfg getif

Eth2 192.168.10.0 global cluster_interconnect

Eth0 192.168.20.0 global public

3. Modify the configuration of system-level network files, / etc/hosts and / etc/sysconfig/network-scripts/ifcfg-eth0

You can modify it according to the actual IP. No details are given here.

4. Restart RAC

Crsctl stop crs

Crsctl start crs

Oifcfg getif

Oifcfg delif-global eth0/192.168.20.0

Oifcfg setif-global eth0/127.0.0.1:public

Srvctl config nodeapps-a

2. Modify VIP

1. Collect current VIP configuration information

# / u01/app/11.2.0/grid/bin/srvctl config nodeapps

Status of VIP

# / u01/app/11.2.0/grid/bin/crs_stat-t

2. Stop all resources

# / u01/app/11.2.0/grid/bin/srvctl stop instance-d oggsrc-n stuaapp01

# / u01/app/11.2.0/grid/bin/srvctl stop vip-n stuaapp01-f

3. Verify that VIP is now offline and the interface is no longer bound to the public network interface.

# / u01/app/11.2.0/grid/bin/crs_stat-t (or $crsctl stat res t for 11gR2)

4. Modify VIP in / etc/hosts file

Crsctl stat res ora.stuaapp01.vip-p

5. Root users, modify VIP resources

# / u01/app/11.2.0/grid/bin/srvctl modify nodeapps-n stuaapp01- A stuaapp01-vip/255.255.255.0/eth0

6. Verify the change

# / u01/app/11.2.0/grid/bin/srvctl config nodeapps-a

7. Start resources

$srvctl start vip-n stuaapp01

$srvctl start listener-n stuaapp01

$srvctl start instance-d oggsrc-n stuaapp01

3. Modify SCAN ip

1. Check the current scan ip configuration information and run it with root users.

Srvctl config scan

2. Stop SCAN listeners and SCAN and run them with grid users

Srvctl stop scan_listener

Srvctl stop scan

3. Modify the scan ip configuration information in the / etc/hosts file. Both nodes need to be changed.

Modify according to specific requirements, no details will be given here

4. Refresh the configuration information and run it with root users

Srvctl modify scan-n rac-scan

5. Verify the change information and run it with the root user

Srvctl config scan

6. Restart SCAN & SCAN listener and run it with grid users

Srvctl start scan

Srvctl start scan_listener

7. If the number of SCAN VIPs changes, the following information needs to be updated (optional)

Srvctl modify scan_listener-u

Thank you for your reading, the above is the content of "how Oracle RAC modifies Scan IP,Public IP". After the study of this article, I believe you have a deeper understanding of how Oracle RAC modifies Scan IP,Public IP, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

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.