The -G option specified the secondary group, which in this example is dba.
The secondary groups must include the OSASM group, whose members are
granted the SYSASM privilege to administer the Oracle ASM instance. You
can designate a unique group for the SYSASM system privileges, separate
from database administrator groups, or you can designate one group as
the OSASM and OSDBA group, so that members of that group are granted the
SYSASM and SYSDBA privileges to grant system privileges to administer
both the Oracle ASM instances and Oracle Database instances. In code
examples, this group is asmadmin.
If you are creating this user to own both Oracle Grid Infrastructure
and an Oracle Database installation, then this user must have the OSDBA
for ASM group as a secondary group. In code examples, this group name is
asmdba. Members of the OSDBA for ASM group are granted
access to Oracle ASM storage. You must create an OSDBA for ASM group if
you plan to have multiple databases accessing Oracle ASM storage, or you
must use the same group as the OSDBA for all databases, and for the
OSDBA for ASM group.