Overview of Automatic Storage Management (ASM)

Automatic Storage Management (ASM) simplifies administration of Oracle related files by allowing the
administrator to reference disk groups rather than individual disks and files, which are managed by ASM.
The ASM functionality is an extention of the Oracle Managed Files (OMF) functionality that also includes
striping and mirroring to provide balanced and secure storage. The new ASM functionality can be used in
combination with existing raw and cooked file systems, along with OMF and manually managed files.

The ASM functionality is controlled by an ASM instance. This is not a full database instance, just the
memory structures and as such is very small and lightweight.

The main components of ASM are disk groups, each of which comprise of several physical disks that are
controlled as a single unit. The physical disks are known as ASM disks, while the files that reside on the
disks are know as ASM files. The locations and names for the files are controlled by ASM, but user-
friendly aliases and directory structures can be defined for ease of reference.

The level of redundancy and the granularity of the striping can be controlled using templates. Default
templates are provided for each file type stored by ASM, but additional templates can be defined as
needed.

Failure groups are defined within a disk group to support the required level of redundancy. For two-way
mirroring you would expect a disk group to contain two failure groups so individual files are written to two
locations.

In summary ASM provides the following functionality:

 Manages groups of disks, called disk groups.

 Manages disk redundancy within a disk group.
 Provides near-optimal I/O balancing without any manual tuning.
 Enables management of database objects without specifying mount points and filenames.
 Supports large files.

Initialization Parameters and ASM Instance Creation

The initialization parameters that are of specific interest for an ASM instance are:

 INSTANCE_TYPE - Set to ASM or RDBMS depending on the instance type. The default is
RDBMS.
 DB_UNIQUE_NAME - Specifies a globally unique name for the database. This defaults to +ASM
but must be altered if you intend to run multiple ASM instances.
 ASM_POWER_LIMIT -The maximum power for a rebalancing operation on an ASM instance. The
valid values range from 1 to 11, with 1 being the default. The higher the limit the more resources
are allocated resulting in faster rebalancing operations. This value is also used as the default
when the POWER clause is omitted from a rebalance operation.
 ASM_DISKGROUPS - The list of disk groups that should be mounted by an ASM instance during
instance startup, or by the ALTER DISKGROUP ALL MOUNT statement. ASM configuration
changes are automatically reflected in this parameter.
 ASM_DISKSTRING - Specifies a value that can be used to limit the disks considered for
discovery. Altering the default value may improve the speed of disk group mount time and the
speed of adding a disk to a disk group. Changing the parameter to a value which prevents the
discovery of already mounted disks results in an error. The default value is NULL allowing all
suitable disks to be considered.
Incorrect usage of parameters in ASM or RDBMS instances result in ORA-15021 errors.

To create an ASM instance first create a file called "init+ASM.ora" in the "/tmp" directory containing the
following information.

INSTANCE_TYPE=ASM

Next, using SQL*Plus connect to the ide instance.

export ORACLE_SID=+ASM
sqlplus / as sysdba

Create an spfile using the contents of the "init+ASM.ora" file.

SQL> CREATE SPFILE FROM PFILE='/tmp/init+ASM.ora';

File created.

Finally, start the instance with the NOMOUNT option.

SQL> startup nomount

ASM instance started

Total System Global Area 125829120 bytes

Fixed Size 1301456 bytes
Variable Size 124527664 bytes
Database Buffers 0 bytes
Redo Buffers 0 bytes
SQL>

The ASM instance is now ready to use for creating and mounting disk groups. To shutdown the ASM
instance issue the following command.

SQL> shutdown
ASM instance shutdown
SQL>

Once an ASM instance is present disk groups can be used for the following parameters in database
instances (INSTANCE_TYPE=RDBMS) to allow ASM file creation:

 DB_CREATE_FILE_DEST
 DB_CREATE_ONLINE_LOG_DEST_n
 DB_RECOVERY_FILE_DEST
 CONTROL_FILES
 LOG_ARCHIVE_DEST_n
 LOG_ARCHIVE_DEST
  STANDBY_ARCHIVE_DEST

Startup and Shutdown of ASM Instances

ASM instance are started and stopped in a similar way to normal database instances. The options for
the STARTUP command are:

 FORCE - Performs a SHUTDOWN ABORT before restarting the ASM instance.

 MOUNT - Starts the ASM instance and mounts the disk groups specified by
the ASM_DISKGROUPS parameter.
 NOMOUNT - Starts the ASM instance without mounting any disk groups.
 OPEN - This is not a valid option for an ASM instance.

The options for the SHUTDOWN command are:

 NORMAL - The ASM instance waits for all connected ASM instances and SQL sessions to exit
then shuts down.
 IMMEDIATE - The ASM instance waits for any SQL transactions to complete then shuts down. It
doesn't wait for sessions to exit.
 TRANSACTIONAL - Same as IMMEDIATE.
 ABORT - The ASM instance shuts down instantly.

Administering ASM Disk Groups

There are a few basic points to consider when planning to use ASM:

 In most cases you will only need two disk groups (DATA and FRA), where DATA holds all
database related files and FRA holds the fast recovery area, including multiplexed copies on
online redo logs and controlfiles. Typically, the FRA disk group will be twice the size of the DATA
disk group, since it must hold all backups.
 Oracle recommend a minimum of 4 LUNs per disk group, with LUNs using hardware RAID and
external redundancy if possible.
 All LUNs within a disk group should be the same size and have the same performance
characteristics.
 LUNs should be made up from disks dedicated to Oracle, not shared with other applications.

Now let's look at basic administration of disk groups.

Disks

Disk groups are created using the CREATE DISKGROUP statement. This statement allows you to specify
the level of redundancy:

 NORMAL REDUNDANCY - Two-way mirroring, requiring two failure groups.

 HIGH REDUNDANCY - Three-way mirroring, requiring three failure groups.
 EXTERNAL REDUNDANCY - No mirroring for disks that are already protected using hardware
mirroring or RAID. If you have hardware RAID it should be used in preference to ASM
redundancy, so this will be the standard option for most installations.
In addition failure groups and preferred names for disks can be defined. If the NAME clause is omitted the
disks are given a system generated name like "disk_group_1_0001". The FORCE option can be used to
move a disk from another disk group into this one.

CREATE DISKGROUP disk_group_1 NORMAL REDUNDANCY

FAILGROUP failure_group_1 DISK
'/devices/diska1' NAME diska1,
'/devices/diska2' NAME diska2
FAILGROUP failure_group_2 DISK
'/devices/diskb1' NAME diskb1,
'/devices/diskb2' NAME diskb2;

Disk groups can be deleted using the DROP DISKGROUP statement.

DROP DISKGROUP disk_group_1 INCLUDING CONTENTS;

Disks can be added or removed from disk groups using the ALTER DISKGROUP statement. Remember
that the wildcard "*" can be used to reference disks so long as the resulting string does not match a disk
already used by an existing disk group.

-- Add disks.
ALTER DISKGROUP disk_group_1 ADD DISK
'/devices/disk*3',
'/devices/disk*4';

-- Drop a disk.
ALTER DISKGROUP disk_group_1 DROP DISK diska2;

Disks can be resized using the RESIZE clause of the ALTER DISKGROUP statement. The statement can
be used to resize individual disks, all disks in a failure group or all disks in the disk group. If
the SIZE clause is omitted the disks are resized to the size of the disk returned by the OS.

-- Resize a specific disk.

ALTER DISKGROUP disk_group_1
RESIZE DISK diska1 SIZE 100G;

-- Resize all disks in a failure group.

ALTER DISKGROUP disk_group_1
RESIZE DISKS IN FAILGROUP failure_group_1 SIZE 100G;

-- Resize all disks in a disk group.

ALTER DISKGROUP disk_group_1
RESIZE ALL SIZE 100G;

The UNDROP DISKS clause of the ALTER DISKGROUP statement allows pending disk drops to be
undone. It will not revert drops that have completed, or disk drops associated with the dropping of a disk
group.
ALTER DISKGROUP disk_group_1 UNDROP DISKS;

Disk groups can be rebalanced manually using the REBALANCE clause of the ALTER
DISKGROUP statement. If the POWER clause is omitted the ASM_POWER_LIMIT parameter value is used.
Rebalancing is only needed when the speed of the automatic rebalancing is not appropriate.

ALTER DISKGROUP disk_group_1 REBALANCE POWER 5;

Disk groups are mounted at ASM instance startup and unmounted at ASM instance shutdown. Manual
mounting and dismounting can be accomplished using the ALTER DISKGROUP statement as seen below.

ALTER DISKGROUP ALL DISMOUNT;

ALTER DISKGROUP ALL MOUNT;
ALTER DISKGROUP disk_group_1 DISMOUNT;
ALTER DISKGROUP disk_group_1 MOUNT;

Templates

Templates are named groups of attributes that can be applied to the files within a disk group. The
following example show how templates can be created, altered and dropped.

-- Create a new template.

ALTER DISKGROUP disk_group_1 ADD TEMPLATE my_template ATTRIBUTES (MIRROR
FINE);

-- Modify template.
ALTER DISKGROUP disk_group_1 ALTER TEMPLATE my_template ATTRIBUTES (COARSE);

-- Drop template.
ALTER DISKGROUP disk_group_1 DROP TEMPLATE my_template;

Available attributes include:

 UNPROTECTED - No mirroring or striping regardless of the redundancy setting.

 MIRROR - Two-way mirroring for normal redundancy and three-way mirroring for high
redundancy. This attribute cannot be set for external redundancy.
 COARSE - Specifies lower granuality for striping. This attribute cannot be set for external
redundancy.
 FINE - Specifies higher granularity for striping. This attribute cannot be set for external
redundancy.

Directories

A directory heirarchy can be defined using the ALTER DISKGROUP statement to support ASM file
aliasing. The following examples show how ASM directories can be created, modified and deleted.
-- Create a directory.
ALTER DISKGROUP disk_group_1 ADD DIRECTORY '+disk_group_1/my_dir';

-- Rename a directory.
ALTER DISKGROUP disk_group_1 RENAME DIRECTORY '+disk_group_1/my_dir' TO
'+disk_group_1/my_dir_2';

-- Delete a directory and all its contents.

ALTER DISKGROUP disk_group_1 DROP DIRECTORY '+disk_group_1/my_dir_2' FORCE;

Aliases

Aliases allow you to reference ASM files using user-friendly names, rather than the fully qualified ASM
filenames.

-- Create an alias using the fully qualified filename.

ALTER DISKGROUP disk_group_1 ADD ALIAS '+disk_group_1/my_dir/my_file.dbf'
FOR '+disk_group_1/mydb/datafile/my_ts.342.3';

-- Create an alias using the numeric form filename.

ALTER DISKGROUP disk_group_1 ADD ALIAS '+disk_group_1/my_dir/my_file.dbf'
FOR '+disk_group_1.342.3';

-- Rename an alias.
ALTER DISKGROUP disk_group_1 RENAME ALIAS '+disk_group_1/my_dir/my_file.dbf'
TO '+disk_group_1/my_dir/my_file2.dbf';

-- Delete an alias.
ALTER DISKGROUP disk_group_1 DELETE ALIAS '+disk_group_1/my_dir/my_file.dbf';

Attempting to drop a system alias results in an error.

Files

Files are not deleted automatically if they are created using aliases, as they are not Oracle Managed Files
(OMF), or if a recovery is done to a point-in-time before the file was created. For these circumstances it is
necessary to manually delete the files, as shown below.

-- Drop file using an alias.

ALTER DISKGROUP disk_group_1 DROP FILE '+disk_group_1/my_dir/my_file.dbf';

-- Drop file using a numeric form filename.

ALTER DISKGROUP disk_group_1 DROP FILE '+disk_group_1.342.3';

-- Drop file using a fully qualified filename.

ALTER DISKGROUP disk_group_1 DROP FILE
'+disk_group_1/mydb/datafile/my_ts.342.3';

Checking Metadata
The internal consistency of disk group metadata can be checked in a number of ways using
the CHECK clause of the ALTER DISKGROUP statement.

-- Check metadata for a specific file.

ALTER DISKGROUP disk_group_1 CHECK FILE '+disk_group_1/my_dir/my_file.dbf'

-- Check metadata for a specific failure group in the disk group.

ALTER DISKGROUP disk_group_1 CHECK FAILGROUP failure_group_1;

-- Check metadata for a specific disk in the disk group.

ALTER DISKGROUP disk_group_1 CHECK DISK diska1;

-- Check metadata for all disks in the disk group.

ALTER DISKGROUP disk_group_1 CHECK ALL;

ASM Views

The ASM configuration can be viewed using the V$ASM_% views, which often contain different information
depending on whether they are queried from the ASM instance, or a dependant database instance.

View ASM Instance DB Instance

Displays a row for each alias
V$ASM_ALIAS present in every disk group Returns no rows
mounted by the ASM instance.
Displays a row for each database
V$ASM_CLIENT Displays a row for the ASM instance if the
instance using a disk group
database has open ASM files.
managed by the ASM instance.
Displays a row for each disk
V$ASM_DISK discovered by the ASM instance, Displays a row for each disk in disk groups in
including disks which are not part of use by the database instance.
any disk group.
V$ASM_DISKGROUP Displays a row for each disk group Displays a row for each disk group mounted
discovered by the ASM instance. by the local ASM instance.
Displays a row for each file for each
V$ASM_FILE disk group mounted by the ASM Displays no rows.
instance.
Displays a row for each file for each
V$ASM_OPERATION long running operation executing in Displays no rows.
the ASM instance.
Displays a row for each template present in
Displays a row for each template
V$ASM_TEMPLATE each disk group mounted by the ASM
present in each disk group mounted
instance with which the database instance
by the ASM instance.
communicates.

ASM Filenames

There are several ways to reference ASM file. Some forms are used during creation and some for
referencing ASM files. The forms for file creation are incomplete, relying on ASM to create the fully
qualified name, which can be retrieved from the supporting views. The forms of the ASM filenames are
summarised below.
 Filename Type Format
Fully Qualified ASM Filename +dgroup/dbname/file_type/file_type_tag.file.incarnation
Numeric ASM Filename +dgroup.file.incarnation
Alias ASM Filenames +dgroup/directory/filename
Alias ASM Filename with Template +dgroup(template)/alias
Incomplete ASM Filename +dgroup
Incomplete ASM Filename with Template +dgroup(template)

SQL and ASM

ASM filenames can be used in place of conventional filenames for most Oracle file types, including
controlfiles, datafiles, logfiles etc. For example, the following command creates a new tablespace with a
datafile in the disk_group_1 disk group.

CREATE TABLESPACE my_ts DATAFILE '+disk_group_1' SIZE 100M AUTOEXTEND ON;

ASM Background Process

asm_pmon_+ASM =Process Monitor

Monitors the other background processes and performs process recovery when a
server or dispatcher process terminates abnormally

PMON periodically performs cleanup of all the following:

 Processes that died abnormally
 Sessions that were killed
 Detached transactions that have exceeded their idle timeout
 Detached network connections which have exceeded their idle timeout

asm_vktm_+ASM=Virtual Keeper of Time Process

Provides a wall clock time and reference time for time interval measurements

VKTM acts as a time publisher for an Oracle instance. VKTM publishes two sets of
time: a wall clock time using a seconds interval and a higher resolution time (which
is not wall clock time) for interval measurements. The VKTM timer service
centralizes time tracking and offloads multiple timer calls from other clients.

asm_gen0_+ASM=General Task Execution Process

Performs required tasks including SQL and DML

asm_diag_+ASM=Diagnostic Capture Process

DIAG performs diagnostic dumps requested by other processes and dumps

triggered by process or instance termination. In Oracle RAC, DIAG performs global
diagnostic dumps requested by remote instances

asm_psp0_+ASM=Process Spawner Process

Spawns Oracle background processes after initial instance startup

asm_dia0_+ASM=Diagnostic Process

Detects and resolves hangs and deadlocks

asm_mman_+ASM=Memory Manager Process

Serves as the instance memory manager

This process performs the resizing of memory components on the instance.

asm_dbw0_+ASM=Database Writer Process

The primary responsibility of DBWn is to write data blocks to disk. DBWn also
handles checkpoints, file open synchronization, and logging of Block Written
records.
In many cases the blocks that DBWn writes are scattered throughout the
disk. Thus, the writes tend to be slower than the sequential writes performed
by LGWR. DBWn performs multiblock writes when possible to improve
efficiency. The number of blocks written in a multiblock write varies by
operating system.
The DB_WRITER_PROCESSES initialization parameter specifies the number of
DBWn processes (DBW0-DBW9 and DBWa-DBWz). The database selects an
appropriate default setting for this parameter or adjusts a user-specified
setting based on the number of CPUs and processor groups.

asm_lgwr_+ASM=Log Writer Process

Redo log entries are generated in the redo log buffer of the system global area
(SGA). LGWR writes the redo log entries sequentially into a redo log file. If the
database has a multiplexed redo log, then LGWR writes the redo log entries to a
group of redo log files.

asm_ckpt_+ASM=Checkpoint Process

At specific times CKPT starts a checkpoint request by messaging DBWnto begin

writing dirty buffers. On completion of individual checkpoint requests, CKPT updates
data file headers and control files to record most recent checkpoint.
asm_smon_+ASM=System Monitor Process

Performs critical tasks such as instance recovery and dead transaction recovery,
and maintenance tasks such as temporary space reclamation, data dictionary
cleanup, and undo tablespace management

SMON performs many database maintenance tasks, including the following:

 Creates and manages the temporary tablespace metadata
 Reclaims space used by orphaned temporary segments
 Maintains the undo tablespace by onlining, offlining, and shrinking the
undo segments based on undo space usage statistics
 Cleans up the data dictionary when it is in a transient and inconsistent
state
 Maintains the SCN to time mapping table used to support Oracle
Flashback features
In an Oracle RAC database, the SMON process of one instance can perform
instance recovery for other instances that have failed.
SMON is resilient to internal and external errors raised during background
activities.

asm_rbal_+ASM=ASM Rebalance Master Process

In an ASM instance, it coordinates rebalance activity for disk groups. In a database

instances, it manages ASM disk groups.

asm_gmon_+ASM=ASM Disk Group Monitor Process

Monitors all mounted ASM disk groups

GMON monitors all the disk groups mounted in an ASM instance and is responsible
for maintaining consistent disk membership and status information. Membership
changes result from adding and dropping disks, whereas disk status changes result
from taking disks offline or bringing them online.

asm_mmon_+ASM=Manageability Monitor Process

MMON performs many tasks related to manageability, including taking Automatic

Workload Repository snapshots and performing Automatic Database Diagnostic
Monitor analysis.

asm_mmnl_+ASM=Manageability Monitor Lite Process

MMNL performs many tasks relating to manageability, including session history

capture and metrics computation.
asm_asmb_+ASM=ASM Background Process

Communicates with the ASM instance, managing storage and providing statistics

ASMB runs in ASM instances when the ASMCMD cp command runs or when the
database instance first starts if the server parameter file is stored in ASM. ASMB
also runs with Oracle Cluster Registry on ASM.
ASM_DISKGROUPS
The ASM_DISKGROUPS initialization parameter specifies a list of the names of disk groups
that an Oracle ASM instance mounts at startup. Oracle ignores the value that you set for
ASM_DISKGROUPS when you specify the NOMOUNT option at startup or when you run the
ALTER DISKGROUP ALL MOUNT statement. The default value of the ASM_DISKGROUPS
parameter is a NULL string. For information about disk groups that are mounted at startup
time, see "About Mounting Disk Groups at Startup" on page 3-16.
The ASM_DISKGROUPS parameter is dynamic. If you are using a server parameter file
(SPFILE), then you do not have to manually alter the value of ASM_DISKGROUPS. Oracle ASM
automatically adds a disk group to this parameter when the disk group is successfully
created or mounted. Oracle ASM also automatically removes a disk group from this
parameter when the disk group is dropped or dismounted.
The following is an example of setting the ASM_DISKGROUPS parameter dynamically:
SQL> ALTER SYSTEM SET ASM_DISKGROUPS = DATA, FRA;
When using a text initialization parameter file (PFILE), you may edit the initialization
parameter file to add the name of any disk group so that it is mounted automatically at
instance startup. You must remove the name of any disk group that you no longer want
automatically mounted.
The following is an example of the ASM_DISKGROUPS parameter in the initialization file:
ASM_DISKGROUPS = DATA, FRA

ASM_DISKSTRING

The ASM_DISKSTRING initialization parameter specifies a comma-delimited list of strings

that limits the set of disks that an Oracle ASM instance discovers. The discovery strings
can include wildcard characters. Only disks that match one of the strings are discovered.
The same disk cannot be discovered twice.
The discovery string format depends on the Oracle ASM library and the operating system
that are in use. Pattern matching is supported. Refer to your operating system-specific
installation guide for information about the default pattern matching.

For example, on a Linux server that does not use ASMLib, to limit the discovery process to
only include disks that are in the /dev/rdsk/mydisks directory, set the ASM_DISKSTRING
initialization parameter to: /dev/rdsk/mydisks/*

The asterisk is required. To limit the discovery process to only include disks that have a
name that ends in disk3 or disk4, set ASM_DISKSTRING to:
/dev/rdsk/*disk3, /dev/rdsk/*disk4
The ? character, when used as the first character of a path, expands to the Oracle home
directory. Depending on the operating system, when you use the ? character elsewhere in
the path, it is a wildcard for one character.
The default value of the ASM_DISKSTRING parameter is a NULL string. A NULL value causes
Oracle ASM to search a default path for all disks in the system to which the Oracle ASM
instance has read and write access. The default search path is platform-specific. Refer to
your operating system specific installation guide for more information about the default
search path.

Oracle ASM cannot use a disk unless all of the Oracle ASM instances in the cluster can
discover the disk through one of their own discovery strings. The names do not have to be
the same on every node, but all disks must be discoverable by all of the nodes in the
cluster. This may require dynamically changing the initialization parameter to enable
adding new storage.

ASM_POWER_LIMIT
The ASM_POWER_LIMIT initialization parameter specifies the default power for disk
rebalancing in a disk group. The range of values is 0 to 1024. The default value is 1. A
value of 0 disables rebalancing. Higher numeric values enable the rebalancing operation to
complete more quickly, but might result in higher I/O overhead and more rebalancing
processes.
■For disk groups that have the disk group ASM compatibility set to 11.2.0.2 or greater
(for example, COMPATIBLE.ASM = 11.2.0.2), the operational range of values is 0 to 1024
for the rebalance power.
■For disk groups that have the disk group ASM compatibility set to less than 11.2.0.2, the
operational range of values is 0 to 11 inclusive. If the value for ASM_POWER_LIMIT is larger
than 11, a value of 11 is used for these disk groups.

You can also specify the power of the rebalancing operation in a disk group with the POWER
clause of the SQL ALTER DISKGROUP ... REBALANCE statement. The range of allowable
values for the POWER clause is the same for the ASM_POWER_LIMIT initialization parameter.
If the value of the POWER clause is specified larger than 11 for a disk group with ASM
compatibility set to less than 11.2.0.2, then a warning is displayed and a POWER value
equal to 11 is used for rebalancing.

ASM_PREFERRED_READ_FAILURE_GROUPS
The ASM_PREFERRED_READ_FAILURE_GROUPS initialization parameter value is a comma-
delimited list of strings that specifies the failure groups that should be preferentially read
by the given instance. The ASM_PREFERRED_READ_FAILURE_GROUPS parameter setting is
instance specific. The default value is NULL. This parameter is generally used for clustered
Oracle ASM instances and its value can be different on different nodes.
For example: diskgroup_name1.failure_group_name1, ...

DB_CACHE_SIZE

You do not have to set a value for the DB_CACHE_SIZE initialization parameter if you use
automatic memory management. The setting for the DB_CACHE_SIZE parameter determines
the size of the buffer cache. This buffer cache is used to store metadata blocks. The default
value for this parameter is suitable for most environments.

DIAGNOSTIC_DEST

The DIAGNOSTIC_DEST initialization parameter specifies the directory where diagnostics for
an instance are located. The default value for an Oracle ASM instance is the $ORACLE_BASE
directory for the Oracle Grid Infrastructure installation.

$ ls $ORACLE_BASE/diag/asm/+asm/+ASM

alert cdump hm incident incpkg ir lck metadata stage sweep trace

INSTANCE_TYPE
The INSTANCE_TYPE initialization parameter is optional for an Oracle ASM instance in an
Oracle Grid Infrastructure home.
The following is an example of the INSTANCE_TYPE parameter in the initialization file:
INSTANCE_TYPE = ASM

LARGE_POOL_SIZE
You do not have to set a value for the LARGE_POOL_SIZE initialization parameter if you use
automatic memory management.

The setting for the LARGE_POOL_SIZE parameter is used for large allocations. The default
value for this parameter is suitable for most environments.

PROCESSES
The PROCESSES initialization parameter affects Oracle ASM, but the default value is usually
suitable. However, if multiple database instances are connected to an Oracle ASM instance,
you can use the following formula:
PROCESSES = 50 + 50*n

where n is the number database instances connecting to the Oracle ASM instance.

REMOTE_LOGIN_PASSWORDFILE
The REMOTE_LOGIN_PASSWORDFILE initialization parameter specifies whether the Oracle
ASM instance checks for a password file. This parameter operates the same for Oracle
ASM and database instances.

SHARED_POOL_SIZE

You do not have to set a value for the SHARED_POOL_SIZE initialization parameter if you use
automatic memory management. The setting for the SHARED_POOL_SIZE parameter
determines the amount of memory required to manage the instance. The setting for this
parameter is also used to determine the amount of space that is allocated for extent
storage. The default value for this parameter is suitable for most environments.
ASM DISK group status

Candidate :- A fresh disk is available to be added to to ASM Disk group

Member- Given disk is already part of ASM Disk Group

Former:- Given disk was earlier part of some ASM Disk Group but now its available

Foreign:- Given disk is being used by some other software other than ASM

Provisioned:- Given disk is stamped on Linux Platform using ASMLib

---------------------------------

In Normal redundancy Failure Group must filled

In External redundancy Failure Group not required.

--------------------------------------------

Enable XDB feature

run script from rdbms/admin/catxdbdbca.sql

after check listener

enable http and ftp

login through system user after http

-----------------------------------------------

QUORUM | REGULAR

Use these keywords to qualify either failure group or disk specifications.

 REGULAR disks, or disks in non-quorum failure groups, can contain any

files.

 QUORUMdisks, or disks in quorum failure groups, cannot contain any

database files, the Oracle Cluster Registry (OCR), or dynamic volumes.
However,QUORUM disks can contain the voting file for Cluster
Synchronization Services (CSS). Oracle ASM uses quorum disks or disks
in quorum failure groups for voting files whenever possible.
 Disks in quorum failure groups are not considered when determining
redundancy requirements.

If you specify neither keyword, then REGULAR is the default.

Specify either QUORUM or REGULAR before the keyword FAILGROUP if you are
explicitly specifying the failure group. If you are creating a disk group with
implicitly created failure groups, then specify these keywords before the
keyword DISK.