Oracle 10g rac modifies public ip and vip 10/06 Update SLTechnology News&Howtos

Oracle 10g rac modifies public ip and vip

2024-10-06 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

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

Oracle 10g rac modifies public ip, vip and private ip

[TOC]

1.IP address planning

Hostname current IP modified IPPublic IPnode1192.168.56.20192.168.100.20Public IPnode2192.168.56.21192.168.100.21VIPnode1-vip192.168.56.98192.168.100.98VIPnode2-vip192.168.56.99192.168.100.99Private IPnode1-priv10.1.1.110.10.10.1Private IPnode1-priv10.1.1.210.10.10.22. Implementation step planning

Close all crs resources and keep the crs process

Backup OCR

Modify Public IP

Modify VIP

Modify tnsnames.ora and listener.ora

Modify / etc/hosts

Modify the operating system IP

Restart crs and crs resources

Modify local_listener

3. Detailed operation example 3.1 close all crs resources

Because the commands to modify Public IP and vip depend on crs, you need to close all crs resources and retain the crs process before modifying Public IP and vip.

First check the cluster status

[root@node1] # crs_stat-tName Type Target State Host-ora.iesdb.db application ONLINE ONLINE node1 ora....b1.inst application ONLINE ONLINE node1 ora....b2.inst application ONLINE ONLINE node2 ora....srac.cs application ONLINE ONLINE node2 ora....db1.srv application ONLINE ONLINE node1 ora....db2.srv application ONLINE ONLINE node2 ora....SM1.asm application ONLINE ONLINE node1 ora....E1.lsnr application ONLINE ONLINE node1 ora.node1.gsd Application ONLINE ONLINE node1 ora.node1.ons application ONLINE ONLINE node1 ora.node1.vip application ONLINE ONLINE node1 ora....SM2.asm application ONLINE ONLINE node2 ora....E2.lsnr application ONLINE ONLINE node2 ora.node2.gsd application ONLINE ONLINE node2 ora.node2.ons application ONLINE ONLINE node2 ora.node2.vip application ONLINE ONLINE node2

Close all crs resources

The oracle user logs in to node 1 and executes the following command in turn:

[oracle@node1 ~] $srvctl stop database-d iesdb [oracle@node1 ~] $srvctl stop asm-n node1 [oracle@node1 ~] $srvctl stop asm-n node2 [oracle@node1 ~] $srvctl stop nodeapps-n node1 [oracle@node1 ~] $srvctl stop nodeapps-n node2

Now check that the crs resources are all closed:

[oracle@node1] $crs_stat-tName Type Target State Host-ora.iesdb.db application OFFLINE OFFLINE ora....b1.inst application OFFLINE OFFLINE ora....b2.inst application OFFLINE OFFLINE ora....srac.cs application OFFLINE OFFLINE ora....db1.srv application OFFLINE OFFLINE ora....db2.srv application OFFLINE OFFLINE ora....SM1.asm application OFFLINE OFFLINE ora....E1.lsnr application OFFLINE OFFLINE ora.node1.gsd application OFFLINE OFFLINE ora.node1.ons application OFFLINE OFFLINE ora.node1.vip application OFFLINE OFFLINE ora....SM2.asm application OFFLINE OFFLINE ora....E2.lsnr application OFFLINE OFFLINE ora.node2.gsd application OFFLINE OFFLINE ora .node2.ons application OFFLINE OFFLINE ora.node2.vip application OFFLINE OFFLINE3.2 backup OCR

OCR is equivalent to the registry of Windows. For Windows, all software information, users, configuration, security, etc., are placed in the registry. As for the cluster, the same is true. All the resources, configurations, nodes, and RAC databases related to the cluster are placed in this warehouse. If the OCR is destroyed, it will cause the cluster service to start abnormally, and the OCR needs to be repaired. Therefore, the management and maintenance of OCR is very important for the whole cluster.

OCR usually contains the following

Node member information

Database instances, nodes, and other mapping relationships

ASM

Resource allocation information (vip,services, etc.)

Service characteristics (Service characteristics)

Information about related processes in the Oracle cluster

Third-party application information controlled by CRS

OCR backup is done here, mainly in order to recover through OCR backup in the event of an error in the configuration of oracle cluster.

For root users to log in, you only need to make an OCR backup on one node:

# first create a backup folder [root@node1 ~] # mkdir / ocr_backup# ocr backup. Any suffix name of the backup file can be [root@node1 ~] # ocrconfig-export / ocr_backup/ocr201706.bak3.3 to modify Public IP.

If the Public IP to be modified is the same as the original network segment, skip this step.

Oracle user login:

# View current status [oracle@node1 ~] $oifcfg getifeth0 192.168.56.0 global publiceth2 10.1.1.0 global cluster_interconnect# Delete Public IP configuration Information [oracle@node1 ~] $oifcfg delif-global eth0 [oracle@node1 ~] $oifcfg getifeth2 10.1.1.0 global cluster_interconnect# configuration New Public IP Segment [oracle@node1 ~] $oifcfg setif-global eth0/192.168.100.0:public [oracle@node1 ~] $oifcfg getifeth0 192.168.100.0 global publiceth2 10.1.1.0 global cluster_interconnect# Public IP configuration successfully 3.4 modified VIP

Root user login:

# first, set the ORACLE_HOME variable [root@node1 ~] # export ORACLE_HOME= "/ oracle/product/10.2.0/db" # to view the current VIP information [root@node1 ~] # srvctl config nodeapps-n node1-aVIP already exists according to the configuration of the oracle user. : / node1-vip/192.168.56.98/255.255.255.0/eth0 [root@node1 ~] # srvctl config nodeapps-n node2-aVIP already exists. : / node2-vip/192.168.56.99/255.255.255.0/eth0# modify VIP [root@node1 ~] # srvctl modify nodeapps-h usage: srvctl modify nodeapps-n [- o] [- A]-n node name-A node level virtual IP address-o ORACLE_HOME path-h printing usage [root@node1 ~ ] # srvctl modify nodeapps-n node1-A 192.168.100.98/255.255.255.0/eth0 [root@node1 ~] # srvctl modify nodeapps-n node2-A 192.168.100.99/255.255.255.0/eth0# View the modified VIP [root@node1 ~] # srvctl config nodeapps-n node1-aVIP already exists. : / 192.168.100.98/192.168.100.98/255.255.255.0/eth0 [root@node1 ~] # srvctl config nodeapps-n node2-aVIP already exists. : / 192.168.100.99/192.168.100.99/255.255.255.0/eth0# VIP modified successfully 3.5 modify tnsnames.ora and listener.ora

The oracle user logs in and all nodes are modified:

[oracle@node1 db] $cd $ORACLE_HOME/network/admin# backup files before modification [oracle@node1 admin] $cp-a tnsnames.ora tnsnames.ora.bak [oracle@node1 admin] $cp-a listener.ora listener.ora.bak

Then the examiner has two files, in which Public IP and VIP are not modified for hostname, and Public IP and VIP for IP address are modified to the new Public IP and VIP.

Example:

# modify 192.168.56.20 in the file to a new Public IP:192.168.100.20 # the node1-vip in the file remains the same [oracle@node1 admin] $cat listener.ora# listener.ora.node1 Network Configuration File: / oracle/product/10.2.0/db/network/admin/listener.ora.node1# Generated by Oracle configuration tools.SID_LIST_LISTENER_NODE1 = (SID_LIST = (SID_DESC = (SID_NAME = PLSExtProc) (ORACLE_HOME = / oracle/product/10.2.0/db) PROGRAM = extproc)) LISTENER_NODE1 = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = node1-vip) (PORT = 1521) (IP = FIRST)) (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.100.20) (PORT = 1521) (IP = FIRST)) 3.6 modified / etc/hosts

The root user logs in and all nodes are modified:

# first back up the hosts file [root@node1 admin] # cp-a / etc/hosts / etc/hosts.bak# to view the current hosts configuration file [root@node1 admin] # cat / etc/hosts# Do not remove the following line Or various programs# that require network functionality will fail.127.0.0.1 localhost.localdomain localhost::1 localhost6.localdomain6 localhost6192.168.56.20 node1192.168.56.21 node2192.168.56.98 node1-vip192.168.56.99 node2-vip10.1.1.1 node1-priv10.1.1.2 node2-priv

Modify both Public IP and VIP to the new IP address:

# modified hosts file [root@node1 admin] # cat / etc/hosts# Do not remove the following line, or various programs# that require network functionality will fail.127.0.0.1 localhost.localdomain localhost::1 localhost6.localdomain6 localhost6192.168.100.20 node1192.168.100.21 node2192.168.100.98 node1-vip192.168.100.99 node2-vip10.1.1.1 node1-priv10.1.1.2 node2-priv3.7 modified operating system IP

The root user logs in, changes the Public IP of all nodes to the new address, and then restarts the network service:

[root@node1 ~] # cd / etc/sysconfig/network-scripts/ [root@node1 network-scripts] # vim ifcfg-eth0 # Intel Corporation 82540EM Gigabit Ethernet ControllerDEVICE=eth0BOOTPROTO=noneONBOOT=yesHWADDR=08:00:27:b2:d1:1bNETMASK=255.255.255.0IPADDR=192.168.100.20TYPE=EthernetUSERCTL=noIPV6INIT=noPEERDNS=yes# restart the network service [root@node1 network-scripts] # service network restart

After the modification is successful, the root user logs in to ensure that the Public IP and Private IP of all nodes can communicate with each other through ping.

3.8 restart crs and crs resources

The root user logs in, and all nodes do the following:

# first close CRS, (all nodes execute this command before continuing to the next step) [root@node1 ~] # crsctl stop crsStopping resources. This could take several minutes.Successfully stopped CRS resources.Stopping CSSD.Shutting down CSS daemon.Shutdown request successfully issued.# enables CRS (all nodes) [root@node1 ~] # crsctl start crsAttempting to start CRS stack The CRS stack will be started shortly

Wait a moment, and the crs resources of all nodes will start normally:

The network information is as follows:

[root@node1 ~] # ifconfig eth0 Link encap:Ethernet HWaddr 08:00:27:B2:D1:1B inet addr:192.168.100.20 Bcast:192.168.100.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8697 errors:0 dropped:0 overruns:0 frame:0 TX packets:28955 errors:0 dropped:0 overruns:0 carrier:0 collisions: 0 txqueuelen:1000 RX bytes:788771 (770.2 KiB) TX bytes:35854996 (34.1MiB) eth0:1 Link encap:Ethernet HWaddr 08:00:27:B2:D1:1B inet addr:192.168.100.98 Bcast:192.168.100.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1eth2 Link encap:Ethernet HWaddr 08:00:27:CB:6A:BB Inet addr:10.1.1.1 Bcast:10.1.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:322721 errors:0 dropped:0 overruns:0 frame:0 TX packets:283490 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:198377998 (189.1 MiB) TX bytes:145057008 (138.3 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:110006 errors:0 dropped:0 overruns:0 frame:0 TX packets:110006 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:55092250 (52.5 MiB) TX bytes:55092250 (52.5 MiB) 3.9 modify local_listener

Finally, you need to modify the local_listener of oracle.

Note: the IP address in the sql statement is the new VIP, as follows:

ALTER SYSTEM SET LOCAL_LISTENER ='(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.100.98) (PORT = 1521) 'scope=both SID =' iesdb1'

[root@node1] # su-oracle [oracle@node1 ~] $sqlplus / as sysdbaSQL*Plus: Release 10.2.0.5.0-Production on Fri Jun 16 18:31:50 2017Copyright (c) 1982, 2010, Oracle. All Rights Reserved.Connected to:Oracle Database 10g Enterprise Edition Release 10.2.0.5.0-64bit ProductionWith the Partitioning, Real Application Clusters, OLAP, Data Miningand Real Application Testing optionsSQL > show parameter local_listener NAME TYPE VALUE---local_listener string (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.56.98) (PORT = 1521) SQL > ALTER SYSTEM SET LOCAL_LISTENER ='(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.100.98) (PORT = 1521)) 'scope=both SID =' iesdb1' System altered.SQL > ALTER SYSTEM SET LOCAL_LISTENER ='(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.100.99) (PORT = 1521)) 'scope=both SID =' iesdb2';System altered.SQL > show parameter local_listener NAME TYPE VALUE---local_listener string (ADDRESS = (PROTOCOL = TCP) (HO ST = 192.168.100.98) (PORT = 1521)) SQL > SQL > conn system/inspur@iesdb2Connected.SQL > show parameter local_listener NAME TYPE VALUE---local_listener string (ADDRESS = (PROTOCOL = TCP) (HO ST = 192.168.100.99) (PORT = 1521)) SQL >

At this point, the Public IP and VIP of oracle rac have been modified.

4. Fallback process

If there is an error in our middle modification, which causes the cluster to fail to start, we can use OCR to roll back to the initial state.

First turn off crs on all nodes

The root user logs in and executes on all nodes:

[root@node1] # crsctl stop crs Stopping resources. This could take several minutes. Successfully stopped CRS resources. Stopping CSSD. Shutting down CSS daemon. Shutdown request successfully issued.

Restore the configuration files for all nodes

[root@node2 etc] # cp-a / etc/hosts.bak / etc/hosts cp: overwrite "/ etc/hosts"? Y # 2. Restore tnsnames.ora and listener.ora [root@node2 admin] # cp-a tnsnames.ora.bak tnsnames.ora cp: overwrite "tnsnames.ora"? Y [root@node2 admin] # cp-a listener.ora.bak listener.ora cp: overwrite "listener.ora"? Y # Note whether the file permissions are correct [root@node2 admin] # ll tnsnames.ora-rw-r--r-- 1 oracle oinstall 1878 06-16 10:21 tnsnames.ora [root@node2 admin] # ll listener.ora-rw-r--r-- 1 oracle oinstall 552 06-19 14:35 listener.or

Restore OCR

To log in to root users, you only need to restore it on one node:

# the original backup OCR file is: [root@node1 /] # ll / ocr_backup/ocr201706.bak-rw-r--r-- 1 root root 107241 06-16 16:53 / ocr_backup/ocr201706.bak # restore OCR [root@node1 /] # ocrconfig-import / ocr_backup/ocr201706.bak # OCR has no output after successful restore

Restore operating system IP

Edit the Nic file in the / etc/sysconfig/network-scripts/ directory, restore the previously modified Nic IP address, and then restart the network service.

Start CRS to check the cluster status

Root users log in, and all nodes execute:

[root@node1] # crs_stat-t Name Type Target State Host-ora.iesdb.db application ONLINE ONLINE node1 ora....b1. Inst application ONLINE ONLINE node1 ora....b2.inst application ONLINE ONLINE node2 ora....srac.cs application ONLINE ONLINE node2 ora....db1.srv application ONLINE ONLINE node1 ora....db2.srv application ONLINE ONLINE node2 ora....SM1.asm application ONLINE ONLINE node1 ora....E1.lsnr application ONLINE ONLINE Node1 ora.node1.gsd application ONLINE ONLINE node1 ora.node1.ons application ONLINE ONLINE node1 ora.node1.vip application ONLINE ONLINE node1 ora....SM2.asm application ONLINE ONLINE node2 ora....E2.lsnr application ONLINE ONLINE node2 ora.node2.gsd application ONLINE ONLINE node2 ora.node2.ons application ONLINE ONLINE node2 Ora.node2.vip application ONLINE ONLINE node2

At this point, you can see that all the resources in CRS are in the state of ONLINE. Finally, change the IP of local_listener to oracle VIP.

Modify local_listener

Orale users can only operate on one node:

[oracle@node1] $sqlplus / as sysdba SQL*Plus: Release 10.2.0.5.0-Production on Mon Jul 3 15:17:25 2017 Copyright (c) 1982, 2010, Oracle. All Rights Reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.5.0-64bit Production With the Partitioning, Real Application Clusters, OLAP, Data Mining and Real Application Testing options SQL > alter system set local_listener=' (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.56.98) (PORT = 1521)) 'sid='iesdb1'; System altered. SQL > alter system set local_listener=' (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.56.99) (PORT = 1521)) 'sid='iesdb2'; System altered. After SQL > modification

Check the IP address of local_listener as follows:

[oracle@node2] $sqlplus / nolog SQL*Plus: Release 10.2.0.5.0-Production on Mon Jul 3 15:19:10 2017 Copyright (c) 1982, 2010, Oracle. All Rights Reserved. SQL > conn sys@iesdb1 as sysdba Enter password: Connected. SQL > show parameter local_listener NAME TYPE VALUE-local_listener String (ADDRESS = (PROTOCOL = TCP) (HO ST = 192.168.56.98) (PORT = 1521)) SQL > conn sys/inspur@iesdb2 as sysdba Connected. SQL > show parameter local_listener NAME TYPE VALUE-local_listener String (ADDRESS = (PROTOCOL = TCP) (HO ST = 192.168.56.99) (PORT = 1521))

At this point, the oracle cluster is restored.

5. Modify private ip

Here is a supplement to the method of modifying private ip.

You can use the oracle user to modify the private ip as follows:

Modify the heartbeat network segment to 10.10.10.0

# View current IP information [oracle@node1 ~] $oifcfg getif eth0 192.168.56.0 global public eth2 10.1.1.0 global cluster_interconnect # add 10.10.10.0 network segment to heartbeat segment [oracle@node1 ~] $oifcfg setif-global eth2/10.10.10.0:cluster_interconnect [oracle@node1 ~] $oifcfg getif eth0 192.168.56.0 global public eth2 10.1.1.0 global cluster_interconnect eth2 10 .10.10.0 global cluster_interconnect # Delete the original heartbeat segment [oracle@node1 ~] $oifcfg delif-global eth2/10.1.1.0 [oracle@node1 ~] $oifcfg getif eth0 192.168.56.0 global public eth2 10.10.10.0 global cluster_interconnect # oifcfg help [oracle@node1 ~] $oifcfg-help Name: oifcfg-Oracle Interface Configuration Tool. Usage: oifcfg iflist [- p [- n]] oifcfg setif {- node |-global} {/:}. Oifcfg getif [- node |-global] [- if [/] [- type]] oifcfg delif [- node |-global] [[/]] oifcfg [- help]-name of the host, as known to a communications network-name by which the interface is configured in the system-subnet address of the interface-type of the interface {cluster_interconnect | public | storage}

Close CRS

Root users, all nodes operate:

[root@node1] # crsctl stop crs Stopping resources. This could take several minutes. Successfully stopped CRS resources. Stopping CSSD. Shutting down CSS daemon. Shutdown request successfully issued.

Modify the private ip content in the / etc/hosts file

Root users, all nodes operate:

# hosts file [root@node1 ~] # cat / etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost:: 1 localhost6.localdomain6 localhost6 192.168.56.20 node1 192.168.56.21 node2 192.168.56.98 node1-vip 192.168.56.99 node2-vip 10.1.1.1 node1-priv 10.1.1.2 node2-priv # modified hosts file [root@node1 ~] # cat / etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost:: 1 localhost6.localdomain6 localhost6 192.168.56.20 node1 192.168.56.21 node2 192.168.56.98 node1-vip 192.168.56.99 node2-vip 10.10.10.1 node1-priv 10.10.10.2 node2-priv

Modify the operating system IP

Root user, all nodes operate:

[root@node1 ~] # cat / etc/sysconfig/network-scripts/ifcfg-eth2 # Intel Corporation 82540EM Gigabit Ethernet Controller DEVICE=eth2 BOOTPROTO=none ONBOOT=yes HWADDR=08:00:27:cb:6a:bb TYPE=Ethernet NETMASK=255.255.255.0 IPADDR=10.10.10.1 USERCTL=no IPV6INIT=no PEERDNS=yes # restart the network service [root@node1 ~] # service network restart [root@node1 ~] # ifconfig eth2 eth2 Link encap:Ethernet HWaddr 08:00:27:CB:6A:BB inet addr:10.10 .10.1 Bcast:10.10.10.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:135852 errors:0 dropped:0 overruns:0 frame:0 TX packets:112129 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:84007109 (80.1 MiB) TX bytes:52783613 (50.3 MiB) [root @ node2 network-scripts] # ifconfig eth2 eth2 Link encap:Ethernet HWaddr 08:00:27:F6:DB:67 inet addr:10.10.10.2 Bcast:10.10.10.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:112136 errors:0 dropped:0 overruns:0 frame:0 TX packets:135677 errors:0 dropped:0 overruns:0 carrier:0 Collisions:0 txqueuelen:1000 RX bytes:52778410 (50.3 MiB) TX bytes:83970669 (80.0 MiB) # ensures that the heartbeats of all nodes can ping each other [root@node1] # ping 10.10.10.2 PING 10.10.10.2 (10.10.10.2) 56 (84) bytes of data. 64 bytes from 10.10.10.2: icmp_seq=1 ttl=64 time=0.884 ms 64 bytes from 10.10.10.2: icmp_seq=2 ttl=64 time=0.206 ms

Start CRS

Root user, all nodes operate:

[root@node1 ~] # crsctl start crs Attempting to start CRS stack The CRS stack will be started shortly [root@node1 ~] # crs_stat-t Name Type Target State Host- Ora.iesdb.db application ONLINE ONLINE node2 ora....b1.inst application ONLINE ONLINE node1 ora....b2.inst application ONLINE ONLINE node2 ora....srac.cs application ONLINE ONLINE node2 ora....db1.srv application ONLINE ONLINE node1 ora....db2.srv application ONLINE ONLINE node2 ora....SM1.asm Application ONLINE ONLINE node1 ora....E1.lsnr application ONLINE ONLINE node1 ora.node1.gsd application ONLINE ONLINE node1 ora.node1.ons application ONLINE ONLINE node1 ora.node1.vip application ONLINE ONLINE node1 ora....SM2.asm application ONLINE ONLINE node2 ora....E2.lsnr application ONLINE ONLINE node2 ora.node2. Gsd application ONLINE ONLINE node2 ora.node2.ons application ONLINE ONLINE node2 ora.node2.vip application ONLINE ONLINE node2 [oracle@node1 ~] $oifcfg getif eth0 192.168.56.0 global public eth2 10.10.10.0 global cluster_interconnect

At this point, the private ip modification is complete. If you want to roll back, please refer to "4. Fallback process".

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.

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.