Last modified on 5 April 2013, at 05:10

RAC Attack - Oracle Cluster Database at Home/Configure Node 2


  1. In the VMware console, go to the Virtual Machine menu and choose Add Virtual Machine to Inventory.
    RA-vmweb-addmachine.png
  2. Browse to RAC11g/collabn2 and open collabn1.vmx. Make sure you browse to the right folder!

    RA-vmweb-addmachine-browse.png
  3. In the Inventory tab at the left, select the new VM – collabn2. Choose the Console tab and click the play button to start the VM.

    RA-vmweb-console.png
  4. The VMware console should ask you whether you copied or moved the VM. Answer that you copied the files and click OK.

    RA-vmweb-startup-prompt-move.png
  5. When you see the square boxes, click anywhere to open a console window.

    RA-vmweb-console-only.png
  6. Login as the oracle user with the password racattack.

    RA-oel-login-oracle.png
  7. Open a terminal ( Applications >> Accessories >> Terminal ) and switch to the root user.


    RA-oel-console-collabn2-first.png
  8. CONFIRM that the IP address of eth1 starts with 172.16.100.

    [root@collabn1 ~]# ifconfig|grep net
    eth1      Link encap:Ethernet  HWaddr 00:0C:29:C9:3E:C8
              inet addr:172.16.100.129  Bcast:172.16.100.255  Mask:255.255.255.0
              inet addr:127.0.0.1  Mask:255.0.0.0
    
  9. Update the IP addresses by directly editing the linux network configuration files. Update the BOOTPROTO line and add the remaining lines.

    COMMENT or DELETE the line which begins with HWADDR.

    [root@collabn1 ~]# cd /etc/sysconfig/network-scripts
    [root@collabn1 network-scripts]# gedit ifcfg-eth0
    BOOTPROTO=none
    #HWADDR=...
    IPADDR=192.168.78.52
    NETMASK=255.255.255.0
    GATEWAY=192.168.78.2
     
    [root@collabn1 network-scripts]# gedit ifcfg-eth1
    BOOTPROTO=none
    #HWADDR=...
    IPADDR=172.16.100.52
    NETMASK=255.255.255.0
    
  10. Update the DNS search domain

    [root@collabn1 network-scripts]# gedit /etc/resolv.conf
    search vm.ardentperf.com
    nameserver 192.168.78.2
    
  11. Update the HOSTNAME by editing the linux system configuration files. Set it to collabn2.vm.ardentperf.com. Then change the active system hostname with the hostname command.

    [root@collabn1 network-scripts]# gedit /etc/sysconfig/network
    HOSTNAME=collabn2.vm.ardentperf.com
    [root@collabn1 network-scripts]# hostname collabn2.vm.ardentperf.com
    
  12. As root, restart the network services by typing service network restart. Then confirm the new ip addresses with ifconfig. Confirm that search domain by inspecting /etc/resolv.conf – if the file has reverted then edit it again. (The change stuck after the second time I edited the file while walking through this lab.) Also confirm the new hostname with hostname.


    RA-oel-network-restart-collabn2.png
  13. Exit your terminal session and start a new one so that you can see the updated hostname in the prompt.

  14. Edit /etc/hosts. EDIT the line with 127.0.0.1 and then ADD all of the other lines below:

    [root@collabn2 etc]# vi /etc/hosts
    192.168.78.51   collabn1 collabn1.vm.ardentperf.com
    192.168.78.61   collabn1-vip collabn1-vip.vm.ardentperf.com
    172.16.100.51   collabn1-priv collabn1-priv.vm.ardentperf.com
    192.168.78.52   collabn2 collabn2.vm.ardentperf.com
    192.168.78.62   collabn2-vip collabn2-vip.vm.ardentperf.com
    172.16.100.52   collabn2-priv collabn2-priv.vm.ardentperf.com
    192.168.78.250  collab-scan collab-scan.vm.ardentperf.com
    192.168.78.251  collab-gns collab-gns.vm.ardentperf.com
    127.0.0.1       localhost.localdomain localhost
    ::1             localhost6.localdomain6 localhost6