Management of the ASM instance is typically done from the command line prompt.

Starting and stopping the ASM instance

Starting and stopping the ASM instance is much like starting and stopping an Oracle database. Oracle knows that you are starting an ASM instance, so it knows that when you issue the startup command that it needs to do something a bit different than it would with a normal database. Here is the output from an ASM instance startup (without error):

C:\oracle\product\10.2.0\DB01\BIN>set ORACLE_SID=rob10gr2
C:\oracle\product\10.2.0\DB01\BIN>Sqlplus sys/Robert as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jan 26 22:28:57 2007
Copyright (c) 1982, 2005, Oracle.  All rights reserved.
Connected to an idle instance.

SQL> startup
ASM instance started

Total System Global Area   83886080 bytes
Fixed Size                  1247420 bytes
Variable Size              57472836 bytes
ASM Cache                  25165824 bytes
ASM diskgroups mounted

When you first start the ASM instance, you will see this error:

ORA-15110: no diskgroups mounted

This just indicates that no ASM disk groups have yet been allocated to the ASM instance.

Shutting down the ASM instance is just as easy. A shutdown immediate, shutdown abort or just a plain shutdown will do fine. Here is an example of shutting down an ASM instance:

C:\oracle\product\10.2.0\DB01\BIN>set ORACLE_SID=rob10gr2
C:\oracle\product\10.2.0\DB01\BIN>Sqlplus sys/Robert as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jan 26 22:28:57 2007
Copyright (c) 1982, 2005, Oracle.  All rights reserved.
Connected to an idle instance.

SQL> shutdown immediate

If you execute a normal or immediate shutdown command on an ASM instance, that shutdown will fail if there is any database using that ASM instance. An error will be returned and the ASM instance will stay up. As a result, before you shutdown the ASM instance, you will need to shutdown all databases using that ASM instance.

You can perform a shutdown abort on the ASM instance. This will cause the ASM instance to shutdown immediately and all of the associated databases will be shutdown in an inconsistent state. This will require instance recovery when the databases are re-started, which can increase the time it takes to re-open the database. Oracle recommends that you not use the shutdown abort command when stopping an ASM instance.

For additional information on managing ASM disk groups, see the following:

SYSASM Role

A new role was introduced in Oracle 11g, SYSASM. You should use this role when connecting as an administrator to an ASM instance. When logging into an ASM instance start using SYSASM instead of SYSDBA. It is likely that in the future SYSDBA connections to an ASM instance will not be supported. The authentication requirements for connecting as SYSASM are the same as when you connect as SYSDBA.

An example of connecting to an ASM instance using the new SYSASM role is seen here:

[oracle@localhost ~]$ sqlplus / as sysasm
 Copyright (c) 1982, 2006, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.3.0
With the Partitioning, OLAP and Data Mining options
SQL>

You can also use the normal connect commands such as connect sys/dork as SYSASM and the like.