You are on page 1of 3

Installing Oracle RAC 11g On Windows

2008 Service Pack 2 – 64bit

Installing Oracle RAC and Clusterware on a Windows 2008 server is nothing short of an
adventure.  After much time spent (2 full days), I have accumulated several actions to perform in
order to gain a successful install of RAC.

Windows Prerequisites
Installation Prerequisite Discrepancies for Windows 2008

1.  User Equivalence

In order to fulfill the documented prerequisites and in addition to what is outlined in Note
388730.1, it may be necessary to implement the following change in Windows 2008 User
Account Control settings on each node:

Change the elevation prompt behavior for administrators to “Elevate without


prompting” Reference:  http://technet.microsoft.com/en-us/library/cc709691.aspx

a.  Click Start, click Accessories, click Run, type secpol.msc in the Open box, and then click
OK.
b.  From the Local Security Settings console tree, click Local Policies, and then Security
Options.
c.  Scroll down to and double-click User Account Control: Behavior of the elevation prompt
for administrators.
d.  From the drop-down menu, select:
* Elevate without prompting (tasks requesting elevation will automatically run as elevated
without prompting the administrator)
e.  Click OK.
f.  Close the Local Security Settings window.

 Confirm that the ‘Administrators’ group is listed under ‘Manage auditing and security
log’
o Invoke ‘Local Security Settings’ at the prompt by typing:  ‘secpol.msc’
o Click on ‘Local Policies’
o Click on ‘User Rights Assignment’

2. Make sure all servers that will be in the RAC environment are at the same patch level.
3. Turn off the UAL and Firewall
4. Create a local group on each machine.  Create a local user and add the user to the local group. 
The local user needs elevated permissions.
5. Edit the local host file of each machine to include the virtual address as well as the private
address. (The network team should create a private VLan dedicated for RAC.) Below is an
example of a Host file:

10.235.166.10  psb01.domain.com
10.235.166.11  psdb01-virt
192.168.1.10    psdb01-priv

10.235.166.12  psdb02. domain.com


10.235.166.13 psdb02-virt
192.168.1.11    psdb02-priv

10.235.166.14  psdb03. domain.com


10.235.166.15  psdb03-virt
192.168.1.12    psdb03-priv

Verify that the host file is correct on each machine and that the NICs match the host files.  You
will get some kind of service starting error that really has nothing to do with the service but with
the Host file. Ping everything. Make sure that the binding order is set that the public network
interface is listed first.

6. On each server, 5 small partitions are needed for the clusterware.  Using Diskpart create the
partitions and leave them in the RAW state.  Make sure that Windows doesn’t try to map any
drive letters.  If it does, remove all drive letters from each server.

Select part #
Create part log size = 1024
create part log
list part

7. Using Diskpart bring up all the drives online and in a RAW state.  Again make sure there are
no drive letters attached to the drives.  This set of drives will be used for the actual database
storage.

Select part #

create part log


list part

***Make sure that on each node in Diskpart the automount is enabled****

8. If installing the software via Remote Desktop, run as console mode: mstsc -v:server IP /F –
console
Prechecks for RAC
1. When Running the checks, run 11 and 10.2g.  There is a bug in 11g that it doesn’t understand
the operating system is 64bit.

The command is cluvfy stage -pre crsinst -n (node names, node names,) -verbose (11g)

runcluvfy stage -pre crsinst -n (node names separated by a comma) -verbose (10g)

2. If all passes on the checks start the install.  When entering the node information, make sure it
matches what is typed in the host file.  For the private and virtual, make sure the -priv and the
-virt are added.

3. On the voting disks, chose 3 disks that were created in step 5, then the remainder one will
become the OCRPrimary and the other the OCRMirror.  Do not choose the option to format.  Let
the installer take care of that.

4. If it’s going to fail, it will at this part.  This is the part where it tries to start all the services.  If
the prior steps have been followed this should go just fine.

You might also like