To identify the storage requirements for using Oracle Automatic Storage Management, you must determine the number of devices and the amount of free disk space that you require.

1. Determine whether you want to use Oracle ASM for Oracle Database files, recovery files, or both. Oracle Database files include data files, control files, redo log files, the server parameter file, and the password file.

   During the database installation, you have the option to select either a file system or Oracle ASM as the storage mechanism for Oracle Database files. Similarly, you also have the option to select either a file system or Oracle ASM as the storage mechanism for your recovery files.

   Note:

   You do not have to use the same storage mechanism for both Oracle Database files and recovery files. You can use a file system for one file type and Oracle ASM for the other.

   If you select Oracle ASM as your storage option for Oracle Database files, then depending on your choice in the Specify Recovery Options screen, you have the following recovery options:

   • If you select the Oracle ASM option for your recovery files, then Oracle Universal Installer provides you with only the option to use the same disk group for both Oracle Database files and recovery files.

   • If you decide not to enable recovery during the database installation, then, after the database installation, you can modify the DB_RECOVERY_FILE_DEST parameter to enable the fast recovery area.

2. Choose the Oracle ASM redundancy level to use for each Oracle Automatic Storage Management disk group you create.

   The redundancy level that you choose for the Oracle ASM disk group determines how Oracle 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:

   • Normal redundancy

     To optimize performance and reliability in a normal redundancy disk group, Oracle ASM uses two-way mirroring for data files and three-way mirroring for control files, by default. In addition, you can choose the mirroring characteristics for individual files in a disk group. You can use two-way mirroring or no mirroring.

     A normal redundancy disk group requires a minimum of two failure groups (or two disk devices) if you are using two-way mirroring. 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.

   • High redundancy

     The contents of the disk group are three-way mirrored by default. To create a disk group with high redundancy, you must specify at least three failure groups (a minimum of three devices).Although high-redundancy disk groups provide a high level of data protection, you must consider the higher cost of additional storage devices before deciding to use this redundancy level.

   • Flex redundancy

     A flex redundancy disk group is a new disk group type with features such as flexible file redundancy, mirror splitting, and redundancy change. A flex disk group can consolidate files with different redundancy requirements into a single disk group. It also provides the capability for databases to change the redundancy of its files.

     For database data, you can choose no mirroring (unprotected), two-way mirroring (mirrored), or three-way mirroring (high). A flex redundancy disk group requires a minimum of three disk devices (or three failure groups).

3. Determine the total amount of disk space that you require for the data files and recovery files.

   If an Oracle ASM instance is running 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 database installation.

   Use the following tables to determine the minimum number of disks and the minimum disk space requirements for the installation:

   Table 5-1 Oracle ASM Disk Number and Space Requirements for an Oracle database (non-CDB)

   Redundancy Level	Minimum Number of Disks	Data Files	Recovery Files	Both File Types
   External	1	2.7 GB	8.1 GB	10.8 GB
   Normal	2	5.2 GB	15.6 GB	20.8 GB
   High	3	7.8 GB	23.4 GB	31.2 GB
   Flex	3	7.8 GB	23.4 GB	31.2 GB

   Table 5-2 Oracle ASM Disk Number and Space Requirements for a multitenant container database (CDB) with one pluggable database (PDB)

   Redundancy Level	Minimum Number of Disks	Data Files	Recovery Files	Both File Types
   External	1	4.4 GB	13.2 GB	17.6 GB
   Normal	2	8.6 GB	25.8 GB	34.4 GB
   High	3	12.9 GB	38.7 GB	51.6 GB
   Flex	3	12.9 GB	38.7 GB	51.6 GB

   Note:

   • The disk devices must be owned by the user performing the grid installation.

     Check with your system administrator to determine if the disks used by Oracle ASM are mirrored at the storage level. If so, select External for the redundancy. If the disks are not mirrored at the storage level, then select Normal for the redundancy.

   • Every Oracle ASM disk is divided into allocation units (AU). An allocation unit is the fundamental unit of allocation within a disk group. You can select the AU Size value from 1, 2, 4, 8, 16, 32 or 64 MB, depending on the specific disk group compatibility level. The default value is set to 4 MB.

4. (Optional) Identify failure groups for the Oracle ASM disk group devices.

   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. By default, each device comprises its own failure group. However, if two disk devices in a normal redundancy disk group are attached to the same SCSI controller, then the disk group becomes unavailable if the controller fails. The controller in this example is a single point of failure. To protect against failures of this type, you could use two SCSI controllers, each with two disks, and define a failure group for the disks attached to each controller. This configuration enables the disk group to tolerate the failure of one SCSI controller.

   Note:

   Define custom failure groups after installation, using the GUI tool ASMCA, the command line tool asmcmd, or SQL commands.

   If you define custom failure groups, then you must specify a minimum of two failure groups for normal redundancy disk groups and three failure groups for high redundancy disk groups.

   For failure groups containing database files and clusterware files, including voting files, you must specify a minimum of three failure groups for normal redundancy disk groups, and five failure groups for high redundancy disk groups. Disk groups containing voting files must have at least three failure groups for normal redundancy or at least five failure groups for high redundancy. Otherwise, the minimum is two and three respectively. The minimum number of failure groups applies whether or not they are custom failure groups.

5. 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:

   • The disk devices must be owned by the user performing the Oracle Grid Infrastructure installation.

   • All the devices in an Oracle ASM disk group must be the same size and have the same performance characteristics.

   • Do not specify multiple partitions on a single physical disk as a disk group device. Oracle Automatic Storage Management expects each disk group device to be on a separate physical disk.

   • Although you can specify a logical volume as a device in an Oracle ASM disk group, Oracle does not recommend their use because it adds a layer of complexity that is unnecessary with Oracle ASM. Oracle recommends that if you choose to use a logical volume manager, then use the logical volume manager. The logical volume manager represents a single logical unit number (LUN) without striping or mirroring. You can minimize the effect on storage performance of the additional storage layer.

You can select new disk groups during interactive installations, but you must use existing disk groups for noninteractive installations.

Select from the following choices to store either database or recovery files in an existing Oracle ASM disk group, depending on installation method:

• Installation method that runs Database Configuration Assistant in an interactive mode (either during installation or after installation)

  • Select new Disk Group

  • Select existing Disk Group

• Installation method that runs Database Configuration Assistant in a noninteractive mode (either during installation or after installation)

  Select an existing Disk Group only. You cannot create a disk group during noninteractive installations. You can add disk devices to an existing disk group if it has insufficient free space.

• Step 1: Enabling Disk Automounting

• Step 2: Creating the Disk Partitions

DISKPART> select disk 5
DISKPART> create partition primary size=500
DISKPART> ...
DISKPART> create partition extended
DISKPART> create partition logical size=800
DISKPART> ...
DISKPART> create partition logical size=500

To use Oracle Automatic Storage Management with direct attached storage (DAS) or storage area network (SAN), the disks must be stamped with a header.

1. Select the Delete labels option, then click Next.

   The delete option is only available if disks exist with stamps. The delete window shows all stamped Oracle Automatic Storage Management disks.

2. In the Delete Stamps window, select the disks to unstamp.
3. Click Next.
4. Click Finish.

asmtool -add [-force]
\Device\Harddisk1\Partition1 ORCLDISKASM0
\Device\Harddisk2\Partition1 ORCLDISKASM2...

asmtool -addprefix ORCLDISKASM [-force]
\Device\Harddisk1\Partition1
\Device\Harddisk2\Partition1...

asmtool -list [-force]

asmtool -delete ORCLDISKASM0 ORCLDISKASM1...