This article covers the basic management of an ASM instance for database storage.

 

Starting an ASM Instance

1. You must set the ORACLE_SID variable to ASM SID.
2. Default ASM SID is +ASM and for RAC is +ASM{node number}.
3. The ORACLE_HOME variable must be set to Grid infrastructure home where Oracle ASM is installed.
4. Initialization parameter file must contain text: INSTANCE_TYPE = ASM
5. When you run STARTUP command, the ASM instance mounst the ASM disk groups.

 

ASM SQL*plus STARTUP command is options interpreted as:

1. FORCE – Issues SHUTDOWN ABORT to ASM instance before restarting it.
2. MOUNT or OPEN – Mounts the diskgroups in init parameter ASM_DISKGROUPS. This is the default.   An OPEN state for ASM instance really does not exist, if supplied it is treated as MOUNT.
3. NOMOUNT – Starts ASM Instance without mounting diskgroups.
4. RESTRICT – Starts up an instance in restricted mode. Have to have both CREATE SESSION and RESTRICTED SESSION privileges to connect.

 

SYSASM database and OSASM OS privileges gives storage permissions with granting high-level to database itself.  Users can be created in ASM instance and given SYSASM privilege.  OSASM system privilege does same at OS layer.

 

Example of creating a user with SYSASM to new user:

 

$ export ORACLE_SID = + ASM

$ sqlplus / as sysasm

 

CREATE USER asm_admin IDENTIFIED by badpassword_nobiscuit;

User created.

SQL > GRANT SYSASM TO asm_admin;

 

SQLPLUS /NOLOG

SQL > CONNECT asm_admin AS SYSASM

Enter password: badpassword_nobiscuit

Connected to an idle instance.

 

SQL > STARTUP

ASM instance started

Total System Global Area 71303168 bytes

Fixed Size 1069292 bytes

Variable Size 45068052 bytes

ASM Cache 25165824 bytes

ASM disk groups mounted

 

 

Shutting Down an Oracle ASM Instance.

1. ASM instance uses the SQL*Plus shutdown command and you must set the ORACLE_SID variable to ASM SID.
2. Before shutting down an ASM instance you should shutdown all databases using it, if not they will be shutdown with abort option upon ASM shutdown.
3. Before shutting down an ASM instance you should dismount all Dynamic Volume Manager volumes.
4. example of shutdown.

 

SQLPLUS /NOLOG

SQL>  CONNECT asm_user as sysasm

Enter password: *******

Connected.

SQL> SHUTDOWN NORMAL

 

 

SHUTDOWN Options in ASM:

1. NORMAL – instance waits for all in-progress SQL to complete, dismounts disk groups and shuts down. Instance also waits for all currently connected users to disconnect from instance.  Any database instance connected, will cause the command to return an error and will not shutdown.   NORMAL is default shutdown.
2. IMMEDIATE or TRANSACTIONAL – instance waits for all in-progress SQL to complete before dismounting all disk groups and shutting down ASM instance. It does not wait for current users to disconnect.  If any database instances are connected to ASM, will cause the command to return an error and will not shutdown.
3. ABORT – ASM immediately shuts down without dismounting disk groups. This will cause recovery on next ASM startup.  All databases connected to ASM instance will also perform shutdown abort.

 

 

Larry Catt

OCP

An ASM disk group consists of multiple disks and is the base object ASM manages.  Disk Groups contain information for ASM to manage drive space.  Sub-components of a Disk Group are Disks, files, and allocation units.  A disk group can contain files from several different databases and a single database can use files from multiple disk groups.

Disk Group attributes are parameters that belong to disk group and not the ASM instance.  Common ASM disk group attributes are:

• ENABLED – Can be TRUE or FALSE – determines if access control is possible. Default is false and have to use alter disk group to change.
• UMASK – determine the permission mask on created oracle ASM user file. Permission for owner, users in same user group, and users not in users group.  Applies to all files on a disk group.
• AU_SIZE – File extent consists of one or more allocation units. Oracle ASM file consists of one or more file extents.   When creating disk group, you can set the Oracle ASM allocation unit size, value can be 1, 2, 4, 8,16,32,64 MB, depending on the specific disk group compatibility level.
• ASM – The attribute defines the version used. ASM version must be greater or equal to COMPATIBLE.RDBS version to access disks.  If COMPATIBLE.ASM is 11.0 any database instance with version of 10.1 or higher can access, but to manage disk group it must be 11 or higher.
• RDBMS – controls the format of message between ASM instance and database instance. Defines the minimum database client release that can access a disk group.
• TYPE – Id disk group type: data, recovery, or system. Determines the distance to nearest neighbor disk in failure group mirror.   Default is data giving value of 1, recovery – 3, and system – 5 to nearest disk group.
• DISK_REPAIR_TIME – Amount of time a disk can be unavailable to failure before it is dropped from disk group.  To use both COMPATIBLE.ASM and COMPATIBLE.RDBMS must be set to 11.1 or higher.  Cannot set during disk group creation, but use ALTER DISKGROUP… SET ATTRIBUTE.    Default is 3.6 hours.  If either ASM or RDBMS are set to less then 11.1, disk is immediately dropped from disk group.

 

CREATE DISKGROUP SQL command is used to create diskgroups and specifies the following:

1. Unique diskgroup name.
2. Redundancy level:
   1. NORMAL REDUNDANCY – 2 way mirroring is the default
   2. HIGH REDUNDANCY – 3 way mirroring
   3. EXTENAL REDUNDANCY – no mirroring
3. Disks to format for diskgroup.
4. Optional – specify disk to specific failure groups.
5. Optional – specify type of failure group.
6. Optional – specify diskgroup attributes software compatibility or allocation unit size.

 

Example:

CREATE DISKGROUP data NORMAL REDUNDANCY

FAILGROUP fg1

DISK ‘/u01/ diska1’ NAME diska1,

‘/u01/ diska2’ NAME diska2,

‘/u01/ diska3’ NAME diska3

FAILGROUP fg2

DISK ‘/u01/ diskb1’ NAME diskb1,

‘/u01/ diskb2’ NAME diskb2,

‘/u01/ diskb3’ NAME diskb3

ATTRIBUTE ‘au_size’ =’ 2M’, ‘compatible.asm’ = ‘11.2’, ‘compatible.rdbms’ = ‘11.2’;

 

The ALTER DISKGROUP SQL statement enables you to alter a disk group configuration. It is possible to add, resize, or drop disks while the database remains online. Multiple operations in a single ALTER DISKGROUP statement are both possible and recommended. Grouping operations in a single ALTER DISKGROUP statement can reduce rebalancing operations. Oracle ASM automatically rebalances a disk group when its configuration changes. The V$ASM_OPERATION view allows you to monitor the status of rebalance operations. The following command adds two more disks to the data diskgroup.

 

ALTER DISKGROUP data ADD DISK ‘/u01/ diska4’ NAME diska4, ‘/u01/ diska5’ NAME diska5;

 

When rebalancing a disk group, if the POWER clause is not specified in an ALTER DISKGROUP statement, or if a rebalance is executed implicitly because a disk has been added or dropped, the ASM_POWER_LIMIT initialization parameter determines the power used. The value of this parameter can be adjusted dynamically. Higher power values will cause a rebalance operation to complete faster, but consumes more processing and I/ O resources. The default value of 1 minimizes disruption to other applications.

 

 

Larry Catt

OCP