|Oracle® Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide
10g Release 2 (10.2) for Microsoft Windows
|PDF · Mobi · ePub|
This chapter describes the storage configuration tasks that you must complete before you start Oracle Universal Installer. It includes information about the following tasks:
Complete the following steps to prepare shared disks for storage:
You must disable write caching on all disks that will be used to share data between nodes in your cluster. To disable write caching, perform these steps:
Click Start, then click Settings, then Control Panel, then Administrative Tools, then Computer Management, then Device Manager, and then Disk drives
Expand the Disk drives and double-click the first drive listed
Under the Disk Properties tab for the selected drive, uncheck the option that enables the write cache
Double-click each of the other drives listed in the Disk drives hive and disable the write cache as described in the previous step
Caution:Any disks that you use to store files, including database files, that will be shared between nodes, must have write caching disabled.
If you are using Windows 2003, then you must enable disk automounting, depending on the Oracle products you are installing and on other conditions.
You must enable automounting when using:
Raw partitions for Oracle Real Application Clusters (Oracle RAC)
Cluster file system for Oracle RAC
Raw partitions for a single-node database installation
Logical drives for Automatic Storage Management (ASM)
To enable automounting:
Enter the following commands at a command prompt:
c:\> diskpart DISKPART> automount enable Automatic mounting of new volumes enabled.
exit to end the
Repeat steps 1 and 2 for each node in the cluster.
When you have prepared all the cluster nodes in your Windows 2003 system as described in the previous steps, restart all of the nodes.
Note:All nodes in the cluster must have automatic mounting enabled in order to correctly install Oracle RAC and Oracle Clusterware. Oracle recommends that you enable automatic mounting before creating any logical partitions for use by the database, ASM, or the Cluster File System.
You must restart each node after enabling disk automounting. After it is enabled and the node is restarted, automatic mounting remains active until it is disabled.
This section describes supported options for storing Oracle Clusterware files, Oracle Database software, and database files. It includes the following sections:
Use the following overview to help you select your storage option:
There are two ways to store Oracle Clusterware files:
Oracle Cluster File System (OCFS): The cluster file system Oracle provides for the Windows and Linux communities. If you intend to store Oracle Clusterware files on OCFS, then you must ensure that OCFS volume sizes are at least 500 MB each.
Raw storage: Raw logical volumes or raw partitions are created and managed by Microsoft Windows disk management tools or by tools provided by third party vendors.
Note that you must provide disk space for one mirrored Oracle Cluster Registry (OCR) file, and two mirrored voting disk files.
There are three ways to store Oracle Database and recovery files on shared disks:
Automatic Storage Management (database files only): Automatic Storage Management (ASM) is an integrated, high-performance database file system and disk manager for Oracle files. Because ASM requires an Oracle Database instance, it cannot contain Oracle software, but you can use ASM to manage database and recovery files.
Oracle Cluster File System (OCFS): Note that if you intend to use OCFS for your database files, then you should create partitions large enough for the database files when you create partitions for Oracle Clusterware
Note:If you want to have a shared Oracle home directory for all nodes, then you must use OCFS.
Raw storage: Note that you cannot use raw storage to store Oracle database recovery files.
The storage option that you choose for recovery files can be the same as or different to the option you choose for the database files.
For all installations, you must choose the storage option that you want to use for Oracle Clusterware files and Oracle Database files. If you want to enable automated backups during the installation, then you must also choose the storage option that you want to use for recovery files (the flash recovery area). You do not have to use the same storage option for each file type.
For voting disk file placement, ensure that each voting disk is configured so that it does not share any hardware device or disk, or other single point of failure. An absolute majority of voting disks configured (more than half) must be available and responsive at all times for Oracle Clusterware to operate.
For single-instance Oracle Database installations using Oracle Clusterware for failover, you must use OCFS, ASM, or shared raw disks if you do not want the failover processing to include dismounting and remounting the disks containing your database files.
The following table shows the storage options supported for storing Oracle Clusterware files, Oracle Database files, and Oracle Database recovery files. Oracle Clusterware files include the Oracle Cluster Registry (OCR) and the Oracle Clusterware voting disk. Oracle Database files include data files, control files, redo log files, the server parameter file, and the password file.
Note:For the most up-to-date information about supported storage options for Oracle RAC installations, refer to the Certify pages on the OracleMetaLink Web site:
|Storage Option||File Types Supported|
|Automatic Storage Management||No||Yes||Yes|
|Cluster file system (OCFS)||Yes||Yes||Yes|
|Shared raw storage||Yes||Yes||No|
Use the following guidelines when choosing the storage options that you want to use for each file type:
If you satisfy all of the requirements listed for the chosen storage options, then you can choose any combination of the supported storage options for each file type.
Oracle recommends that you choose Automatic Storage Management (ASM) as the storage option for database and recovery files.
For Standard Edition cluster installations, ASM is the only supported storage option for database or recovery files.
You cannot use ASM to store Oracle Clusterware files, because these files must be accessible before any Oracle instance starts, which includes the ASM instances required to manage ASM access.
If you intend to use ASM with Oracle RAC, and you are configuring a new ASM instance, then you must ensure that your system meets the following conditions:
All nodes on the cluster have the release 2 (10.2) version of Oracle Clusterware installed
Any existing ASM instance on any node in the cluster is shut down
If you intend to upgrade an existing Oracle RAC database, or an Oracle RAC database with ASM instances, then you must ensure that your system meets the following conditions:
The Oracle RAC database or Oracle RAC database with ASM instance is running on the node from which the Oracle Universal Installer (OUI) and Database Configuration Assistant (DBCA) is run
The Oracle RAC database or Oracle RAC database with ASM instance is running on the same nodes that you intend to make members of the new cluster installation. For example, if you have an existing Oracle RAC database running on a three node cluster, then you must install the upgrade on all three nodes. You cannot attempt to upgrade only 2 nodes of the cluster.
To obtain the benefits of voting disk redundancy, you must provide storage for three copies of the voting disk no matter which storage option you choose.
If you decide to place the Oracle datafiles on OCFS, then use the following guidelines when deciding where to place them:
If you want to use a single cluster file system, then choose a cluster file system on a physical device that is dedicated to the database.
For best performance and reliability, choose a RAID device or a logical volume on more than one physical device and implement the stripe-and-mirror-everything methodology, also known as SAME.
If you want to use more than one cluster file system, then choose cluster file systems on separate physical devices or partitions that are dedicated to the database.
This method enables you to distribute physical I/O and create separate control files on different devices for increased reliability. It also enables you to fully implement Oracle Optimal Flexible Architecture (OFA) guidelines. To implement this method, you must choose either the Advanced database creation option or choose the Custom installation type during installation.
If you intend to create a preconfigured database during the installation, then the cluster file system (or systems) that you choose must have at least 4 GB of free disk space.
For optimum performance, the cluster file systems that you choose should be on physical devices that are used only by the database.
Note:You must not create an NTFS partition on a disk that you are using for OCFS.
The default location suggested by Oracle Universal Installer for the database file directory is a subdirectory of the Oracle base directory. However, this default location is not appropriate for Oracle RAC production databases.
Note:You must choose a location for recovery files only if you intend to enable automated backups during the installation.
If you choose to place the Oracle recovery files on a cluster file system, then use the following guidelines when deciding where to place them:
To prevent disk failure from making the database files as well as the recovery files unavailable, place the recovery files on a cluster file system that is on a different physical disk from the database files.
Note:Alternatively use an ASM disk group with a normal or high redundancy level for either or both file types.
The cluster file system that you choose should have at least 3 GB of free disk space.
The disk space requirement is the default disk quota configured for the flash recovery area (specified by the
DB_RECOVERY_FILE_DEST_SIZE initialization parameter).
If you choose the Custom installation type or the Advanced database configuration option, then you can specify a different disk quota value. After you create the database, you can also use Oracle Enterprise Manager to specify a different value.
See Also:Oracle Backup and Recovery Basics for more information about sizing the flash recovery area.
The default location suggested by Oracle Universal Installer for the recovery area directory is a subdirectory of the Oracle base directory. However, this default location is not appropriate for Oracle RAC production databases.
When you have determined your disk storage options, you must perform the following tasks in the following order:
To use OCFS for Oracle Clusterware files, refer to Configuring Storage for Oracle Clusterware Files on a Shared File System
To use raw devices (partitions) for Oracle Clusterware files, refer to "Configuring Storage for Oracle Clusterware Files on Raw Devices"
To use a file system for database or recovery file storage, refer to Configuring Storage for Oracle Clusterware Files on a Shared File System, and ensure that in addition to the volumes you create for Oracle Clusterware files, you also create additional volumes with sizes sufficient to store database files.
To use Automatic Storage Management for database or recovery file storage, refer to "Configuring Disks for Automatic Storage Management".
To use raw devices (partitions) for database file storage, refer to "Configuring Raw Logical Volumes or Raw Partitions".
To check for all shared file systems available across all nodes on the cluster, use the following CVU command:
cluvfy comp ssa -n node_list
Remember to use the full path name and the
runcluvfy.bat command on the installation media and include the list of nodes in your cluster, separated by commas, for the
node_list. The following example is for a system with two nodes,
node2, and the installation media on drive F:
F:\> clusterware\cluvfy\runcluvfy.bat comp ssa -n node1,node2
If you want to check the shared accessibility of a specific shared storage type to specific nodes in your cluster, then use the following command syntax:
cluvfy comp ssa -n node_list -s storageID_list
In the preceding syntax, the variable
node_list is the list of nodes you want to check, separated by commas, and the variable
storageID_list is the list of storage device IDs for the storage devices managed by the file system type that you want to check.
Log in to Windows with Administrative privileges and perform the following steps depending on whether you use the Oracle Cluster File System (OCFS) or raw devices:
If you plan to use Automatic Storage Management (ASM) for your database files, then you only need to perform the actions related to the Oracle home and the Oracle Cluster Registry (OCR) and voting disk storage.
If you plan to use OCFS for your Oracle home and datafiles, then the following partitions must exist before you run OUI to install Oracle Clusterware:
3 GB, or larger, for the Oracle home
3 GB, or larger, for the datafiles
The OCR and voting disk, required by Oracle Clusterware, are also stored in the OCFS datafile directory (
datafile_disk is the OCFS partition and
clustername is the name of your cluster.
Oracle Universal Installer (OUI) does not suggest a default location for the Oracle Cluster Registry (OCR) or the Oracle Clusterware voting disk. If you choose to create these files on a file system, then perform the steps described in this section to set up the shared disk raw partitions for OCFS. Windows refers to raw partitions as logical drives. If you need more information about creating partitions, then refer to the Windows online help from within the disk administration tools.
Run Windows Disk Management from one node to create an extended partition. Use a basic disk: dynamic disks are not supported.
Create at least two partitions: one for the Oracle home and one for the Oracle database files.
You do not need to create a partition for the voting disk if you plan to use OCFS. OCFS stores the voting device in a file.
The number of partitions used for OCFS affects performance. Therefore, you should create the minimum number of partitions needed for the OCFS option you choose.
To create the required partitions, perform the following steps:
From one of the existing nodes of the cluster, run the Windows disk administration tool as follows:
Click Start, then select Settings, Control Panel, Administrative Tools, and then Computer Management
Expand the Storage folder to Disk Management. Use a basic disk with a Master Boot Record (MBR) partition style as an extended partition for creating partitions.
Right click inside an unallocated part of an extended partition and choose Create Logical Drive. A wizard presents pages for configuring the logical drive. Select the select logical drive radio button and click Next.
Enter the size that you want for the partition and click Next.
If you are preparing drives on a Windows 2003 system, then you should restart all nodes in the cluster after you have created the logical drives.
Check all nodes in the cluster to ensure that the partitions are visible on all the nodes and to ensure that none of the Oracle partitions have drive letters assigned. If any partitions have drive letters assigned, then remove them by performing these steps:
Right-click the partition in the Windows disk administration tool
Select "Change Drive Letters and Paths..." from the menu
Click Remove in the "Change Drive Letter and Paths" window
To use raw devices, create two partitions: One 256MB partition for the voting disk and one 256 MB partition for the OCR. If you are not using OCFS for your datafiles, then you must also create raw partitions for your database files as described in "Configuring Raw Logical Volumes or Raw Partitions".
This section describes how to configure disks for use with ASM. Before you configure the disks, you must determine the number of disks and the amount of free disk space that you require.
The following sections describe how to identify the requirements and configure the disks:
Identify your site's storage requirements.
Optionally, use an existing Automatic Storage Management disk group.
If you are creating a new Automatic Storage Management disk group, then create partitions for DAS or SAN disks.
Use one of the following methods to complete the Automatic Storage Management configuration:
If you plan to install Oracle Database using interactive mode, then Oracle Universal Installer prompts you for the Automatic Storage Management disk configuration information during the installation.
If you plan to install Oracle Database using noninteractive mode, then you must configure the disks manually before performing the installation.
To identify the storage requirements for using Automatic Storage Management, you must determine how many devices and the amount of free disk space that you require. To complete this task, follow these steps:
Determine whether you want to use Automatic Storage Management for Oracle datafiles, recovery files, or both.
Note:You do not have to use the same storage mechanism for datafiles and recovery files. One can use the file system, while the other uses Automatic Storage Management. If you plan to use Automatic Storage Management for both datafiles and recovery files, then you should create separate ASM disk groups for the datafiles and the recovery files.
If you plan to enable automated backups during the installation, then you can choose Automatic Storage Management as the storage mechanism for recovery files by specifying an ASM disk group for the flash recovery area. Depending how you choose to create a database during the installation, you have the following options:
If you select an installation method that runs Database Configuration Assistant in interactive mode (for example, by choosing the Advanced database configuration option), then you can decide whether you want to use the same ASM disk group for datafiles and recovery files. You can also choose to use different disk groups for each file type. Ideally, you should create separate ASM disk groups for datafiles and recovery files.
The same choice is available to you if you use Database Configuration Assistant after the installation to create a database.
If you select an installation type that runs Database Configuration Assistant in non-interactive mode, then you must use the same Automatic Storage Management disk group for datafiles and recovery files.
The redundancy level that you choose for the Automatic Storage Management disk group determines how ASM mirrors files in the disk group, and determines the number of disks and amount of disk space that you require. The redundancy levels are as follows:
An external redundancy disk group requires a minimum of one disk device. The effective disk space in an external redundancy disk group is the sum of the disk space in all of its devices.
Because Automatic Storage Management does not mirror data in an external redundancy disk group, Oracle recommends that you use only RAID or similar devices that provide their own data protection mechanisms as disk devices in this type of disk group.
In a normal redundancy disk group, Automatic Storage Management uses two-way mirroring by default (except for the control file, which is mirrored three ways), to increase performance and reliability. A normal redundancy disk group requires a minimum of two disk devices, or two failure groups. The effective disk space in a normal redundancy disk group is half the sum of the disk space in all of its devices.
For most installations, Oracle recommends that you use normal redundancy disk groups.
In a high redundancy disk group, Automatic Storage Management uses three-way mirroring to increase performance and provide the highest level of reliability. A high redundancy disk group requires a minimum of three disk devices (or three failure groups). The effective disk space in a high redundancy disk group is one-third the sum of the disk space in all of its devices.
While high redundancy disk groups do provide a high level of data protection, you must consider the higher cost of additional storage devices before deciding to use this redundancy level.
|Redundancy Level||Minimum Number of Disks||Datafiles||Recovery FIles||Both File Types|
|External||1||1.15 GB||2.3 GB||3.45 GB|
|Normal||2||2.3 GB||4.6 GB||6.9 GB|
|High||3||3.45 GB||6.9 GB||10.35 GB|
If an ASM instance already exists on the system, then you can use an existing disk group to meet these storage requirements. If necessary, you can add disks to an existing disk group during the installation.
The following section describes how to identify existing disk groups and determine the free disk space that they contain.
Note:You need to complete this step only if you intend to use an installation method that runs Database Configuration Assistant in interactive mode–for example, if you intend to choose the Custom installation type, or the Advanced database configuration option. Other installation types do not enable you to specify failure groups.
If you intend to use a normal or high redundancy disk group, then you can further protect your database against hardware failure by associating a set of disk devices in a custom failure group. Failure groups define ASM disks that share a common potential failure mechanism. For more information about ASM failure groups, refer to Oracle Database Administrator's Guide.
Note:If you define custom failure groups, you must specify a minimum of two failure groups for normal redundancy disk groups and three failure groups for high redundancy disk groups.
If you are sure that a suitable disk group does not exist on the system, then install or identify appropriate disk devices to add to a new disk group. Use the following guidelines when identifying appropriate disk devices:
All of the devices in an Automatic Storage Management disk group should be the same size and have the same performance characteristics.
Do not specify two or more partitions on a single physical disk as ASM disks in the same disk group. Automatic Storage Management expects each device for a disk group to be on a separate physical disk.
Although you can specify a logical volume as a device in an Automatic Storage Management disk group, Oracle does not recommend their use. Logical volume managers can hide the physical disk architecture, preventing Automatic Storage Management from optimizing I/O across the physical devices.
Tip:As you progress through the following steps, make a list of the raw device names you intend to use and have it available during your database or ASM installation.
If you want to use Automatic Storage Management as the storage option for either database or recovery files, and an existing Automatic Storage Management disk group already exists, then you have the following choices, depending on the installation method that you select:
If you select an installation method that runs Database Configuration Assistant in interactive mode (for example, by choosing the Advanced database configuration option for example), then you can decide whether you want to create a new disk group, or use an existing disk group.
The same choice is available to you if you use Database Configuration Assistant after the installation to create a database.
If you select an installation type that runs Database Configuration Assistant in non-interactive mode, then you must choose an existing disk group for the new database; you cannot create a new disk group. However, you can add disk devices to an existing disk group if the existing disk group has insufficient free space for your requirements.
Note:The Automatic Storage Management instance that manages the existing disk group can be running in a different Oracle home directory.
To determine whether an existing ASM disk group exists, or to determine whether there is sufficient disk space in a disk group, you can use Oracle Enterprise Manager, either Grid Control or Database Control. Alternatively, you can use the following procedure:
In the Services Control Panel, make sure that the
n service, where
n is the node number, has started.
Open a Windows command prompt and temporarily set the
ORACLE_SID environment variable to specify the appropriate value for the ASM instance that you want to use.
For example, if the ASM SID is named
+ASM1, then enter a setting similar to the following:
C:\> set ORACLE_SID = +ASM1
Connect to the Automatic Storage Management instance as the
SYS user with
SYSDBA privilege and start the instance if necessary with a command similar to the following:
C:\> sqlplus "SYS/SYS_password as SYSDBA" SQL> STARTUP
Enter the following command to view the existing disk groups, their redundancy level, and the amount of free disk space in each disk group:
SQL> SELECT NAME,TYPE,TOTAL_MB,FREE_MB FROM V$ASM_DISKGROUP;
From the output, identify a disk group with the appropriate redundancy level and note the free space that it contains.
If necessary, install, or identify the additional disk devices required to meet the storage requirements listed in the previous section.
Note:You can use any physical disk for Automatic Storage Management, as long as it is partitioned. However, you cannot use NAS or Microsoft dynamic disks.
Use Microsoft Computer Management or the command line tool
diskpart to create the partitions. Ensure that you create the partitions without drive letters. After you have created the partitions, the disks can be configured.
See Also:"Assigning Logical Names" for more information about using
diskpartto create a partition
To use Automatic Storage Management with direct attached storage (DAS) or storage area network (SAN) storage, the disks must be stamped with a header. If you install Oracle Database in interactive mode, then Oracle Universal Installer configures the disks' headers during the installation process.
However, if you plan to install Oracle Database in noninteractive mode, then you need to configure the disks manually before installation either by using
asmtoolg (GUI version) or using
asmtool (command line version). You can also use these tools to reconfigure the disks after installation. The
asmtool utilities only work on partitioned disks; you cannot use Automatic Storage Management on unpartitioned disks.
The following section describes the
asmtool functions and commands.
asmtool tools associate meaningful, persistent names with disks to facilitate using those disks with Automatic Storage Management. Automatic Storage Management uses disk strings to operate more easily on groups of disks at once. The names that
asmtool create make this easier than using Windows drive letters.
All disk names created by
asmtool begin with the prefix
ORCLDISK followed by a user-defined prefix (the default is
DATA), and by a disk number for identification purposes. You can use them as raw devices in the Automatic Storage Management instance by specifying a name
prefix either can be
DATA, or can be a value you supply, and where
n represents the disk number.
To add or change disk stamps:
In the installation media labeled Oracle Database 10g Release 2 (10.2), navigate to
db\asmtool, and double-click
If Oracle Database is already installed, then go to
bin, and double-click
Select the Add or change label option, and then click Next.
asmtoolg shows the devices available on the system. Unrecognized disks are labeled as a "Candidate device." Raw device files are labeled as "Oracle raw device file." Stamped Automatic Storage Management disks are labeled as "Stamped ASM disk," and unstamped Automatic Storage Management disks are labeled as "Unstamped ASM disks." The tool also shows disks that are recognized by Windows as a file system (such as NTFS). These disks are not available for use as ASM disks, and cannot be selected. In addition, Microsoft Dynamic disks are not available for use as ASM disks.
If necessary, follow the steps under "Creating Partitions for Logical Volumes" to create a disk partition for the ASM instance.
On the Stamp Disks screen, select the disks to stamp.
For ease of use, Automatic Storage Management can generate unique stamps for all of the devices selected for a given prefix. The stamps are generated by concatenating a number with the prefix specified. For example, if the prefix is
DATA, then the first Automatic Storage Management link name is
You can also specify the stamps of individual devices.
Optionally, select a disk to edit the individual stamp (Automatic Storage Management link name).
To delete disk stamps:
Select the Delete labels option, then click Next.
The delete option is only available if disks exist with stamps. The delete screen shows all stamped Automatic Storage Management disks.
On the Delete Stamps screen, select the disks to unstamp.
||Adds or changes stamps. You must specify the hard disk, partition, and new stamp name. If the disk is a raw device or has an existing Automatic Storage Management stamp, then you must specify the
If necessary, follow the steps under "Creating Partitions for Logical Volumes" to create a disk partition for the ASM instance.
asmtool -add [-force] \Device\Harddisk1\Partition1 ORCLDISKASM0 \Device\Harddisk2\Partition1 ORCLDISKASM2...
||Adds or changes stamps using a common prefix to generate stamps automatically. The stamps are generated by concatenating a number with the prefix specified. If the disk is a raw device or has an existing Automatic Storage Management stamp, then you must specify the
asmtool -addprefix ORCLDISKASM [-force] \Device\Harddisk1\Partition1 \Device\Harddisk2\Partition1...
||List available disks. The stamp, windows device name, and disk size in megabytes are shown. Some disks may be file systems, and cannot be stamped. If the disk is a raw device or has an existing ASM stamp, then you must specify the
asmtool -list [-force]
||Removes existing stamps from disks.||
asmtool -delete ORCLDISKASM0 ORCLDISKASM1...
asmtoolwill notify any Automatic Storage Management instances on the local machine and other nodes in the cluster if available, to rescan the available disks.
This section contains the following topics:
Create the logical volumes listed in the following table. You must create these volumes to install an Oracle database.
|Number||Partition Size (MB)||Purpose and Sample Logical Volume Name|
|1 for each instance||500||
|2 for each instance||120||Two online redo log files (where m is the thread number and n is the log number, 1 or 2):
|2||110||First and second control files:
|1||5||Server parameter file (SPFILE):
To create and configure raw volumes or partitions, use the disk administration tools provided by the operating system or third party vendors. The following administration tools are provided by the operating system:
Windows 2000 and Windows Server 2003 provide Disk Management snap-in to manage disks.
To access this tool, type
diskmgmt.msc at the command prompt. Alternatively, from the Start menu, select Programs, then Administrative Tools, then Computer Management. Then select the Disk Management node in the Storage tree.
Windows Server 2003 provides a command line tool to manage disks.
To access this tool, type
diskpart.exe at the command prompt.
Note:If you need to download the
diskmgmt.msctool, consult Microsoft documentation on the Microsoft Web site
See Also:The online help or documentation for the administration tool you are using
You can use the
diskpart tool command
create partition to create primary or extended partitions, or create logical drives.
The following example uses the
diskpart tool to create a 32 MB extended partition on disk 100. In this syntax,
diskpart.exe is the command line tool for managing disks.
c:\> diskpart.exe DISKPART> select disk 100 DISKPART> create partition extended size=32
Note:Be aware of the following restrictions for partitions:
You cannot use partitions defined on disks with primary partitions for storage defined while running the OUI to install Oracle Clusterware as described in Chapter 4, "Installing Oracle Clusterware on Windows-Based Systems".
With 32-bit Windows, you cannot create more than four primary disk partitions for each disk. With 64-bit and x64 Windows, you can create up to 128 primary partitions. However, Oracle recommends that you limit the number of partitions that you create to prevent disk contention.
Because of these restrictions, you may prefer to use extended partitions rather than primary partitions.
After creating volumes, assign logical names for the Oracle Database. You can assign names to partitions by using
importSYMLinks from the command line, or by using Oracle Object Link Manager. To use Oracle Object Link Manager to create persistent symbolic links to the corresponding raw partitions, run the command
Note:For Windows Server 2008, you must have administrator privileges and run commands from an Administrative command prompt to run executables that reside in the Oracle Clusterware home.
Note:You must complete this procedure only if you are using raw devices for database files. You do not specify the raw devices for the Oracle Clusterware files in the DBCA raw device mapping file.
To enable Database Configuration Assistant (DBCA) to identify the appropriate raw partition symbolic links for each database file, you must create a raw device mapping file, as follows:
Set the ORACLE_BASE environment variable to specify the Oracle base directory that you identified or created previously, as in this example:
C:\>set ORACLE_BASE = E:\oracle
Create a database subdirectory under the Oracle base directory as in this example:
dbname is the name of the database that you chose previously.
Change directory to the
Using any text editor, create a file called
conf.txt. The file should have the following characteristics:
Each line in the file must have the following format:
database_object_identifier = symbolic link name
For your Oracle RAC database, the file must specify one automatic undo tablespace datafile (
n) and two redo log files (
_2) for each instance where
n is the instance number.
Specify at least two control files (
Note:In Windows, by default,
\represents the escape key. To enter a backslash as part of a script, you must enter it in as a string literal. This means that when configuring the mapping file, for Windows to read the mapping file with the path
\\.\, you must enter the path as
\\\\.\\. Windows reads this as "escape backslash escape backslash. escape backslash."
The following syntax example is for a mapping file for a two-instance Oracle RAC cluster:
system=\\\\.\\dbname_SYSTEM sysaux=\\\\.\\dbname_SYSAUX spfile=\\\\.\\dbname_SPFILE users=\\\\.\\dbname_USERS temp=\\\\.\\dbname_TEMP undotbs1=\\\\.\\dbname_UNDOTBS1 undotbs2=\\\\.\\dbname_UNDOTBS2 control1=\\\\.\\dbname_CONTROL1 control2=\\\\.\\dbname_CONTROL2 redo1_1=\\\\.\\dbname_REDO1_1 redo1_2=\\\\.\\dbname_REDO1_2 redo2_1=\\\\.\\dbname_REDO2_1 redo2_2=\\\\.\\dbname_REDO2_2 example=\\\\.\\dbname_EXAMPLE pwdfile=\\\\.\\dbname_pwdfile
Save the file and note the file name that you specified.
You may optionally set an environment variable, DBCA_RAW_CONFIG, to specify the full path to this file. For the Oracle base defined in Step 1, you would use the following command:
If you use OCFS or ASM for your database files, then your database will be created by default with files managed by Oracle Database. You may also elect to use files managed by Oracle if you choose the Custom installation type or the Advanced database creation option. If you use this feature, you need only specify the database object name instead of file names when creating or deleting database files.
Configuration procedures are required in order to enable Oracle Managed Files.
See Also:"Using Oracle-Managed Files" in Oracle Database Administrator's Guide