Skip Headers
Oracle® Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide
10g Release 2 (10.2) for Microsoft Windows

Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

C Configuring Raw Devices for Oracle Real Application Clusters

This appendix provides additional information about configuring raw devices to deploy Real Application Clusters (Oracle RAC). You must configure raw devices if you do not use automatic storage management or an Oracle Cluster File System. The topic in this appendix is:

Support for Raw Devices on Windows Systems

Oracle Database with Oracle Real Application Clusters supports the use of raw devices for Oracle files on Windows 2000 and Windows 2003.

You can partition a raw device to store data and control files. You can also use the entire raw device to store data.

You can create partitions on Windows 2000 and Windows 2003 by using the Disk Management utility, Diskmgmt.msc. To access this utility:

  1. Click Start.

  2. Select Run... from the program list.

  3. In the Run dialog box, type diskmgmt.msc.

Raw Devices Required by Database Configuration Assistant

If you want to use Database Configuration Assistant to create a database on raw storage, that is, without using automatic storage management or an Oracle Cluster File System, then you must configure raw devices as described in this section. These devices are in addition to the OCR and voting disk required to install Oracle Clusterware. Create these devices before running Oracle Universal Installer to install Oracle Database 10g software. DBCA cannot create an Oracle RAC database unless you have properly configured the following devices:

Planning Your Raw Device Creation Strategy

Before installing Oracle Database 10g software with Oracle RAC, create enough partitions of specific sizes to support your database, and also leave a few spare partitions of the same size for future expansion. For example, if you have space on your shared disk array, then select a limited set of standard partition sizes for your entire database. Partition sizes of 50MB, 100MB, 500MB, and 1GB are suitable for most databases. Also create a few very small and a few very large spare partitions that are, for example, 1MB and perhaps 5GB or greater in size. Based on your plans for using each partition, determine the placement of these spare partitions by combining different sizes on one disk, or by segmenting each disk into same-sized partitions.


Ensuring that there are spare partitions enables you to perform emergency file relocations or additions if a tablespace datafile becomes full.