ASM Instance Management
The Oracle Enterprise Manager (OEM) or the
Database
Configuration Assistant (DBCA)
can be used for a GUI
interface to connect to ASM to configure and alter disk groups
and their metadata. OEM provides an integrated approach for
managing the ASM instance as well as database instances
while DBCA is for database instances only. The footprint for an
ASM instance is around 100MB.
An ASM instance does not have a data
dictionary. Therefore, SYSDBA
and SYSOPER have to be used to connect to an ASM instance. For connecting remotely to an ASM instance, use the password file. No other user
administration is maintained by the ASM instance. Those who
connect to the ASM instance with SYSDBA privilege have complete
administrative access to all disk groups in the system.
The SYSOPER privilege is limited to the
following SQL commands:
-
STARTUP AND SHUTDOWN
-
ALTER DISKGROUP
MOUNT/DISMOUNT/REPAIR
-
ALTER DISKGROUP ONLINE/OFFLINE
DISK
-
ALTER DISKGROUP REBALANCE/CHECK
Access to all v$asm_* views
will be
discussed later in this
chapter.
An
ASM instance
should
always be
up and running on the host.
It should
be brought up automatically whenever the host is rebooted.
It should also
use the auto startup mechanism supported by the
underlying operating system. For example, it should run as a
service under Windows. It is also expected to run under Oracle
Cluster Ready Services (CRS) framework for high availability.
