Select operating system groups whose members will have administrative privileges for the Automatic Storage Management storage. Members of these groups are granted system privileges for administration using operating system group authentication. You can use the same group to grant all system privileges, or you can define separate groups to provide role-based system privileges through membership in operating system groups.
Members of the OSASM group are granted the SYSASM administrative privilege for ASM, which provides full administrator access to configure and manage the storage instance. If the installer finds a group on your system named asmadmin, then that is the default OSASM group.
You can use one group as your administrator group (such as dba), or you can separate system privileges by designating specific groups for each system privilege group. ASM can support multiple databases. If you plan to have more than one database on your system, then you can designate a separate OSASM group, and use a separate user from the database user to own the Oracle Clusterware and ASM installation.
Members of the OSOPER for ASM group are granted access to a subset of the SYSASM privileges, such as starting and stopping the storage tier. If the installer finds a group on your system called asmoper, then that is the default OSOPER for ASM group. If you do not have an asmoper group on your servers, or you want to designate another group whose members are granted the OSOPER for ASM privilege, then you can designate a group on the server. Leave the field blank if you choose not to specify an OSOPER for ASM privileges group.
If you want to have an OSOPER for ASM group, then the group must exist on your operating system, or on a Network Information Service (NIS).
Members of the OSDBA for ASM group are granted read and write access to files managed by ASM. The grid infrastructure installation owner must be a member of this group, and all database installation owners of databases that you want to have access to the files managed by ASM should be members of the OSDBA group for ASM. If the installer finds a group on your system called asmdba, then that is the default OSDBA for ASM group.
After you have selected groups to be designated as administrative privileges operating system groups, click Next.