Database Reference
In-Depth Information
The SYSDBA privilege provides access to the data stored in ASM diskgroups; the SYSOPER privilege allows
performing instance operations such as startup, shutdown, mount, dismount, and checking diskgroup; and the
SYSASM privilege allows full administration for the Oracle ASM instance, such as creating or altering diskgroup.
Through these three OS groups, the “grid” is granted all three system privileges for the Oracle ASM instance:
SYSDBA, SYSOPER, and SYSASM. This user is the owner of Grid Infrastructure, which is used to install and manage
the Grid Infrastructure including the ASM instance. In your environment, you also can create additional users with
one or two of these system privileges to perform specific operations such as monitoring ASM diskgroups.
Like a database instance, you can manage an ASM instance using the sqlplus command. For example, in Linux or
Unix, you can set the following environment in the bash profile of the grid user:
export ORACLE_SID=+ASM1
export ORACLE_HOME=/u01/app/12.1.0/grid
Through the grid user, you can log in to the ASM instance with the sysasm privilege and perform ASM
administration tasks:
$ sqlplus / as sysasm
SQL*Plus: Release 12.1.0.1.0 Production on Tue Mar 5 13:22:37 2013
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Real Application Clusters and Automatic Storage Management options
SQL> show parameter spfile
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
spfile string +DATA1/knewrac/ASMPARAMETERFILE/registry.253.807834851
Notice that in the preceding example, the spfile of the ASM instance is stored in a diskgroup “DATA.” Another
user is “oracle,” which is granted SYSDBA and SYSOPER privileges through asmdba and asmoper groups.
$ id oracle
uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall), 54322(dba), 54326(asmdba),
54327(asmoper)
Without being granted the SYSASM privilege, the “oracle” user cannot use the sysasm privilege to log in to the
Oracle ASM instance to do operations such as creating and altering ASM diskgroup. SYSASM enables the separation
of SYSDBA database administration from Oracle ASM storage administration. In this case, we log in as the grid user to
do ASM administration and log in as the Oracle user to do database administration.
Listener for ASM Instance
By default, the listener runs from the Grid Infrastructure home and listens for both ASM instance and database
instances on that RAC node. You don't need to run another listener from Oracle RAC home.
