|Oracle Database 11g Release 2 (126.96.36.199) RAC On Oracle Linux 6.3 Using VirtualBox - This article describes the installation of Oracle Database 11g Release 2 (188.8.131.52) RAC on Oracle Linux 6.3 using VirtualBox with no additional shared disk devices.|
Arif Imam said...Excellent Article Tim! I followed your article and was able to install 184.108.40.206.0 RAC On OEL 6.1. I wanted to install Grid agent 220.127.116.11.0. I created a separate account “gridagent”, The setup and link was successful, however it failed to start the agent on Linux 6.1. Any thought on this?
The agent must work with 6.1, since it is running on 12c Cloud Control if you installed that on 6.1 also.
I've not tried installing the agent on RAC yet, but if I did, I would probably install it under the "oracle" account. I'm guessing your issue is with permissions, possibly the group assignments.
If this is not the case, please post any follow up messages to the forum.
lesio said...It's great :)
Do you sleep from time to time ?
Tim... said...Occasionally. :)
Sangla-Hill said...Thank you for helping people like me!
Bryan said...Thank you for good article!!
Tony said...Hello Tim,
I followed the steps of your tutorial but I am getting stuck in OUI when installing grid infrastructure: The step "Perform remote operations" hangs for a lot of hours and I have to cancel the install.
I notice that nothing is being exchanged over the network between the two VMs and the directory ol6-112-rac2:/u01/app/11.2.0/grid is never filled with any content.
Progressing question on forum:
Venky said...Nice Article. After doing vboxmanage steps and starting vbox, I only see /dev/sda, /dev/sda1, /dev/sda2 but not /dev/sdb. What am I missing?
PS: I use windows7 as the host and Linux as the guest os.
Questions in the forum please!
Make sure you are adding them to the correct SATA Controller. On my VMs they are called "SATA Controller". On Windows they may be called something else.
Bradd Piontek said...Tim,
Great article. Working well for me on Windows 7. One small modification for those who just copy-n-paste. "Use the "fdisk" command to partition the disks sdb to sdf. The following output shows the expected fdisk output for the sdb disk.".
I think you meant to write "sdb to sde". Not a big deal. Just a consistency thing
Well spotted. Darn that copy/paste. :) I've corrected it now.
Thiago said...Hi Tim,
I got stuck using dd if=/dev/zero of=/dev/asm*
Without that command the grid installation can't go on.
Do you faced that issue?
My OS is Mac Lion and my Vbox is updated (4.1.18).
PS: Thanks for the article and posts.
I've never had to do that on a clean installation. If you had a failure, you would need to clean up your shared disks before retrying. I'm guessing that is what happened to you.
yurib said...excellent site, thanks Tim. I used this article succesfully as well as some previous versions.
I just used it to install Rac One Node too.
The installer complained about DNS access but it did not affect the installation. It all seems to work, including failover. Top marks to Tim.
André said...Thank you Tim...
Congratulation for this article...
I used Windows 7 to guest OS and... it's works, amazing!!!
Thank you so much.
Glad you liked it. :)
Terry said...The download link for oracle requires a support account not just an OTN account, how do I download Oracle 11g Release 2 (18.104.22.168) Software (64 bit)
without the support account, can you please send me the link.
OL6 requires 22.214.171.124. Version 126.96.36.199 can only be downloaded from MOS, so you can't do this installation without MOS access.
OL5 still works with 188.8.131.52, so you can do that install.
If you need a 1:1 Clone of RHEL 6 please visit
In opposite to CENTOS it is really up to date.
SL63 x86-64 full install works perfect with Oracle 184.108.40.206
during Grid Installation I tried to use for VIP Nic the same subnet (192.168.135.0) then for public network - that doesnt work.
You can place PUB, PRIV and SCAN for example into 192.168.135.0 (255.255.255.0) - but VIP needs for example 192.168.135.0 (255.255.0.0) otherwise you cannot proceed with install - does not mentioned in config guide - Hint would be good
Frank said...If you have problems that the Voting disk (DATA) during ASM Config in Grid install cannot be selected then you need to shutdown the VM's, remove the ASMx.vdi files from EACH VM and repeat "Create Shared Disks" - since VM is allready cloned, you need to repeat step "The SCSI ID of my disks are displayed below....." until "Clone VM..."
No. PUB, VIP and SCAN all on the same network. PRIV on a different network. This is shown in the /etc/hosts definition.
Simon said...A quick note on the udev rules in "/etc/udev/rules.d/99-oracle-asmdevices.rules" - you need a backslash at the end of each line that begins "KERNEL==" to indicate line continuation. Without that udev rendered my vm unbootable.
The entries is wrapped for convenience of display. That's why the text says, "All parameters for a single entry must be on the same line." :)
Jacco H. Landlust said...Hi Tim,
The cloning of the VM caused me some troubles. The eth0 and eth1 devices were renamed to eth2 and eth3. This was caused by the hwaddr being present in /etc/udev/rules.d/70-persistent-net.rules. After changing the hwaddr-es in that file all went like expected.
Dave said...I had the same problem as Jacco with /etc/udev/rules.d/70-persistent-net.rules. Couldn't get eth0 and eth1 to do the right thing at all - very frustrating. Fixing the udev network rules solved that.
DO NOT ask technical questions here! They will be deleted!
These comments should relate to the contents of a specific article. Constructive criticism is good. Advertising and offensive comments are bad and will be deleted!