This mainly avoids the overlap/conflict role between the DBAs and SAN administrator by using the SYSASM role to manage ASM instance. SYSASM privileges are restricted in ASM instances.
SQL> connect / as sysasm
Connected.
SQL> create user sanadmin identified by passwd;
User created.
SQL> grant sysasm to sanadmin;
Grant succeeded.
SQL> connect sanadmin/passwd as sysasm;
Connected.
SQL> select * from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS
------------------------------ ----- ----- -----
SYS TRUE TRUE FALSE
SANADMIN FALSE FALSE TRUE
SQL> alter diskgroup DG_DBA_DD501 check;
Diskgroup altered.
The CHECK command verifying the internal consistency of the ASM diskgroup metadata
No comments:
Post a Comment