Installation guide
To congure shared disks, do the following:
1. On the rst node only, log in to windows as the Local Administrator.
2. Navigate to Start -> Administrave Tools -> Computer Management.
3. Expand the Storage folder to Disk management.
4. Right-click the unallocated region of a basic disk and choose Create Paron (dynamic disks are not supported).
5. In the Create Paron wizard, choose Next -> Extended Paron (Primary parons are not supported for Logical Drives).
6. Choose Extended Paron. Choose Next.
7. Choose the maximum amount of available space and choose Next.
8. Choose Finish in the summary screen.
9. The Extended Paron should appear green. Right click on the Extended Paron, and choose Create Logical Drive.
10. Proceed through the Wizard instrucons, making sure you choose the enre paron for the Logical Drive. Make sure
that you do not assign a drive leer, and do not format the drive. Choose Finish to exit.
11. Reboot the rst node. Re-enter Disk Management, and check that no drive leer has been assigned. If a drive leer was
assigned, you will have to remove it here (you may also use the Oracle “leerdelete” command from the command line).
12. Reboot each of the other nodes, and check that the drive is visible. Make sure that
no drive leer is assigned on any node. Delete the drive leer, if necessary.
You will need a minimum of three logical drives of 5 GB each for OCFS. If you choose to install Oracle binaries on a shared ORACLE_
HOME, you will need an addional logical drive of at least 5 GB size. For Oracle10g using ASM, you will need one paron of at least
20 MB for the vong disk and one paron of at least 100 MB for the OCR. In addion, for Oracle10g, you may wish to add at least
two more logical drives; one for shared executables (ASM or OCFS) and one for a Recovery Area. Please note that with Oracle10g
using ASM you may place Oracle executables on a shared drive. The Recovery Area should be sized at least as big as 3 GB.
For both Oracle9i and Oracle10g, you have the opon of installing Oracle binaries into a shared ORACLE_HOME. For Oracle9i, you
may use OCFS for shared ORACLE_HOME storage. For Oracle10g, either OCFS or ASM may be used for shared ORACLE_HOME
storage. (Note that the CRS_HOME for Oracle10g cannot be placed on an OCFS volume. It may be placed on local directories that are
replicated to each node.) Using a shared ORACLE_HOME eases administraon by requiring upgrades or patches in only one locaon.
Disk space is also saved. In addion, using a shared ORACLE_HOME removes the possibility of Oracle binaries falling out of synch
between nodes. However, there is an advantage to maintaining per-node copies of the Oracle binaries. This pracce allows oine
maintenance of Oracle binaries on each individual node while the other nodes remain online, without interrupng users. Even if you
elect to use local ORACLE_HOME directories, you have the opon of using the Oracle Universal Installer to replicate binaries to all
cluster nodes, again reducing the chance of binaries being out of synch between nodes.
If you elect to use a Recovery Area for Oracle10g (this is an opon, not a requirement), you should be fully aware of the storage
requirements. The purpose of the Recovery Area is to oer a fast disk-based mechanism for recovery. The Recovery Area ulizes a
combinaon of an RMAN backup to disk and Flash Recovery logs. The inial full RMAN backup and at least one days worth of Flash
Recovery logs guarantees that you will need a Recovery Area at least as large as the sum of the sizes of all the database les. If you
use the default retenon period for Flash Recovery logs of seven days, you will need at least 2X the size of the database les. 3X the
size of the database les is not an uncommon scenario. Use of the Recovery Area oers unprecedented recovery speed and
exibility, but the price you should be prepared to pay is increased disk storage requirements.