RAC

Go to Home Page

Oracle Rac IP Change 

In this case, we will change virtual, public and scan ip addresses..  Private ip addresses stays the same, as it is not needed in this scenario.
In this operation first of tall, we will change the ip addresses declared in RAC.
Second, we will make the ip address changes on the rac nodes(servers).
Finally, we will reboot the rac nodes, to make the new ip addresses assigned.
--Note actually, we dont need to reboot the server.. Only restarting the network service will do the job.. 
But, I write this post for a server migration operation.. I suppose the servers are moved from one system Root to other.. So a reboot is required anyways..

Action Plan:

1. First we check the rac components names and their status using ;

crsctl stat res -t
srvctl config scan --> for scan

2. We stop rac services using ;

srvctl stop scan_listener
srvctl stop scan
srvctl stop database -d PROD
srvctl stop asm -n oradbsrv1
srvctl stop asm -n oradbsrv2
srvctl stop nodeapps -n oradbsrv1
srvctl stop nodeapps -n oradbsrv2

3. After stopping the rac services we use crsctl stat res -t to see the status again.. All the service component should be offline..

4. We check the existing ip configuration on rac and on OS.. In addition we check the hosts file;

oifcfg getif
ifconfig -a

cat /etc/hosts

5. We delete the existing public ip..

oifcfg  delif -global eth1 (ehternet device name associated with the public ip..)

6. We define the new public ip ...

oifcfg  setif -global eth1/10.10.12.0:public   --> ethernet device name/new ip:public

7. We check the new ip configuration on rac to see that the public ip is actually changed..

oifcfg  getif

8. We modify scan..

First, Modify scan ip's in DNS..
Then,srvctl modify scan -n SCAN-name (for ex: ebs-scan)
We check if the ip's are reflected with srvctl config scan
We update scan listeners anyways, srvctl modify scan_listener -u

9. We modify listener.ora,  tnsnames.ora and LOCAL_LISTENER/REMOTE_LISTENER parameter to reflect the VIP change if necessary.

10. We Stop crs on all nodes..

crsctl stop crs

11. Next, We change ip address on Rac nodes

For the Linux on each server;

vi /etc/sysconfig/network-scripts/ifcfg-eth1

Change public ip on rac node 1

DEVICE=eth1
BOOTPROTO=static
DHCPCLASS=
HWADDR=00:30:48:56:A6:2E
IPADDR=10.10.12.10
NETMASK=255.255.255.0
ONBOOT=yes

vi /etc/sysconfig/network

NETWORKING=yes
HOSTNAME=ordbsrv1.example.com
GATEWAY=10.10.12.1

Change public ip on rac node 2

vi /etc/sysconfig/network-scripts/ifcfg-eth1

DEVICE=eth1
BOOTPROTO=static
DHCPCLASS=
HWADDR=00:30:48:56:A6:2E
IPADDR=10.10.12.11
NETMASK=255.255.255.0
ONBOOT=yes

vi /etc/sysconfig/network

NETWORKING=yes
HOSTNAME=ordbsrv2.example.com
GATEWAY=10.10.12.1

13. If the dns ip is changing, edit  vi /etc/resolv.conf

-- we do not restart network services, they will be restarted in reboot..

14. We change the /etc/hosts file to reflect the new ip addresses..


---------------- REBOOT -------------------------------

After rebooting;

15. We modify the the virtual ip 's..
We first check the current Vip configuration;

as root user > srvctl config nodeapps -a

Then we modify the the vip configuration;

as root user > srvctl modify nodeapps -n oradbsrv1 -A 10.10.12.16/255.255.255.0/eth1
as root user > srvctl modify nodeapps -n oradbsrv2 -A 10.10.12.17/255.255.255.0/eth1

Then we check again;

as root user > srvctl config nodeapps -a

---------------------------------------------------------------------------------------------------------------------

Oracle E-Business Suite R12 on Exadata V2 Sun Oracle Database Machine -- Implemented case study

Scope:

•EBS installation using rapidwiz  11G 11.1.0.7 single database with EBS 12.1.1

•Upgrade 11.1.0.7 to 11.2.0.2 ( scan supported release)

•11.2.0.2 database patches for Ebs

•Asm/Rac conversion single instance to Exadata Asm.

•Ebusiness Suite Patches to support scan.

•Ebusiness Suite config for Rac and scan.

•Paralel Concurrent Processing configuration.

•Technical Testing

•Data Load

•Functional Testing

•Benchmarks

Installation Process

Target Specs

Target Specifications:

Oracle E-Business Suite R12 (12.1) running on Oracle Database 11gR2 2 node ASM/RAC (Exadata) .

Detailed Specification: 

DB servers(x2) : 

Oracle Enterprise Linux 5.5 64 bit96 Gb Physical Ram30 Gb Sga, 10 Gb Pga

Scan configured.

Application Servers(x2) : 

Oracle Enterprise Linux 5.5 64 bit8 Gb Physical Ram 

Node 1: Admin, Concurrent, Web, Forms

Node 2: Concurrent,Web,Forms

EBS Architecture on Exadata

Oracle 11GR2 RAC INSTALLATION SCREENSHOTS for LINUX x86-64 bit

We start with Raid configuration.. We configure Raid 1+0 for our 4xlocal disks on our HP nodes.

Then , we mount our Oracle Linux 6.5 iso using ILOM and start our Linux installations..

Next; we disable selinux, we disable iptables and ip6tables for all init levels and reboot our nodes.
After rebooting; we continue with configuring our bonded networks on our nodes.
After configuring network, we configure sysctl.conf files on our nodes.. Actually OEL 6.5 comes configured .. Anyways..
Next, we create necessary groups and users .
Then, we configure ntpd . we configure /etc/hosts files .
Afterwards, we install libhbaapi , oracleasmlib and netapp hostutils rpms.

Then we use sanlun to list our disks and gather their wwid s using scsi_id command.. We use these wwid s in configuring multipaths in our nodes.
After configuring multipaths we restart our multipathd using service multipathd restart and list our multipath disks using various multipath commands..Note that we take out a disk using blacklist statement in our multipath.conf file, as this disk is local disk and should not be included in multipath configurations.
We check /dev/mapper directory structure to see our multipath device names..
Then we create filesystem on these /dev/mapper/* devices.. We create filesystem by considering the ASM-Netapp Disks alignment.. (we set the needed values using fdisk expert option)
After we finish our works for SAN disks on OS layer, we use oracleasm to create ASM disks on them.
Lastly we check and configure a couple of things(like grants , .bash_profiles and so on) and start our Grid installation..

At this point , we start our Grid Installation using runInstaller.. We use bonded networks in both private and public ips, besides we used external redundancy for ASM disks as our disks are from SAN Raid groups.
Note that: we ignore resolv.conf and ASM warning in prereq check, as we check it from backend and see that storage check was successful on all nodes.
We also see couple of bug records about this issue.
Also, we use only the dba group for our installations, we dont need to have a role seperation in this environment.

Then we use asmca to create our FRA diskgroup using remaining ASM disks, and use runInstaller to install our Oracle Database Software -- software only..
Note that: we install our database software only, because we will migrate our production database in to this rac environment, so we dont need to create a database in this stage.

Okay, that 's it. Our RAC 11gR2 Environment is up & running.. It is ready for migration...