If you do not want to divide the privileges for system access into separate operating system groups, then you can designate one operating system group as the group whose members are granted access as OSDBA, OSOPER, and OSASM for Oracle ASM privileges. The default operating system group name for all of these is usually dba and that group is typically chosen for the default configuration.
Table 3-1 shows an example of a Linux deployment without separated privileges for Oracle ASM users.
Table 3-1 One operating system group and one set of privileges for all Oracle ASM users
| Role/Software Owner | User | Group/Privilege |
|---|---|---|
|
Oracle ASM administrator/Oracle Grid Infrastructure home |
oracle |
dba/SYSASM, SYSDBA, SYSOPER |
|
Database administrator 1/Database home 1 |
oracle |
dba/SYSASM, SYSDBA, SYSOPER |
|
Database administrator 2/Database home 2 |
oracle |
dba/SYSASM, SYSDBA, SYSOPER |
|
Operating system disk device owner |
oracle |
dba |