Guenadi N Jilevski's Oracle BLOG

Oracle RAC, DG, EBS, DR and HA DBA BLOG

Virtualization using Oracle VM VirtualBox for building two node Oracle RAC 11gR2 cluster based on Solaris 10 x86-64

Virtualization using Oracle VM VirtualBox for building two node Oracle RAC 11gR2 cluster based on Solaris 10 x86-64

In the article you will have a look at how to use some Oracle VirtualBox features to build two node Oracle 11gR RAC system on Solaris 10 x86-64. An overview to Oracle Virtualization solutions can be seen here. You will configure Solaris VM and install Oracle GI, Oracle RDBMS and will create a database. You will see  how to fix some problems that were encountered.

The following software will be used:

  1. Oracle 11gR2 for Solaris (x86-64). Download from here.
  2. Oracle Solaris (x86-64). Download from here.
  3. Oracle VM VirtualBox 4.0.6. Download from here.

There will be two virtual machines sol1 and sol2, each of them will be configured with

  • 4GB RAM
  • 160GB bootable disk
  • NIC – NAT: for access to Internet
  • NIC – bridged for public interface in RAC with address 192.168.2.21/22 (first IP 192.168.2.21 on sol1 and second IP 192.168.2.22 on node sol2). These are public interface in RAC.
  • NIC – bridged for private interface in RAC with address 10.10.10.21/22 (first IP 10.10.10.21 on sol1 and second IP 10.10.10.22 on node sol2). These are private interface in RAC.
  • NIC – Host Only : for FTP/SSH/telnet/SCP access from the host OS to the guest OS. (first IP 192.168.56.51 on sol1 and second IP 192.168.56.51on node sol2).
  • 5 10GB attached shared disks for the ASM storage.

Note. For access to the Guest OS (Solaris) from the Host (MS Windows Vista 64) via ssh/scp/telnet/ftp.   

                  Continue reading

May 10, 2011 Posted by | oracle | 12 Comments

UDEV rules for device persistency and permissions/ownerships in OEL6/REDHAT 6 for ASM

UDEV rules for device persistency and permissions/ownerships in OEL6/REDHAT 6 for ASM

ASMlib is used to ensure device persistency after a reboot and makes sure that devices retain their access permissions and ownership that are established during ASMib configuration. UDEV is another alternative to ASMlib to achieve device persistency and to set permissions/ownership (OS chown user:group / chmod ) on devices. The article outlines the steps that are required to establish device persistency and setup new device names with desired permissions and ownership in OEL6/REDHAT6 using udev.

Continue reading

May 10, 2011 Posted by | oracle | 16 Comments

   

Follow

Get every new post delivered to your Inbox.

Join 782 other followers