Oracle Database Oracle Clusterware Installation Guide for HP-UX

■ Creating an OSOPER Group
■ Creating the Oracle Software Owner User
Creating Custom Configuration Groups and Users for Job Roles
■ Creating Identical Database Users and Groups on Other Cluster Nodes
3.2.2.1 Creating the OSDBA Group for Custom Installations
You must create an OSDBA group in the following circumstances:
■ An OSDBA group does not exist, for example, if this is the first installation of
Oracle Database software on the system
■ An OSDBA group exists, but you want to give a different group of operating
system users database administrative privileges for a new Oracle Database
installation
If the OSDBA group does not exist or if you require a new OSDBA group, then create
it as follows. In the following procedure, use the group name dba unless a group with
that name already exists:
# /usr/sbin/groupadd -g 502 dba
3.2.2.2 Creating an OSOPER Group
Create an OSOPER group only if you want to identify a group of operating system
users with a limited set of database administrative privileges (SYSOPER operator
privileges). For most installations, it is sufficient to create only the OSDBA group. If
you want to use an OSOPER group, then you must create it in the following
circumstances:
■ If an OSOPER group does not exist; for example, if this is the first installation of
Oracle Database software on the system
■ If an OSOPER group exists, but you want to give a different group of operating
system users database operator privileges in a new Oracle installation
If you require a new OSOPER group, then create it as follows. In the following, use the
group name oper unless a group with that name already exists.
# /usr/sbin/groupadd -g 505 oper
3.2.2.3 Creating the OSASM Group
If the OSASM group does not exist or if you require a new OSASM group, then create
it as follows. In the following procedure, use the group name asm unless a group with
that name already exists:
# /usr/sbin/groupadd -504 asm
3.2.2.4 Creating the OSDBA Group for ASM
You must create an OSDBA group for ASM to provide access to the ASM instance.
This is necessary if OSASM and OSDBA are different groups.
If the OSDBA group for ASM does not exist or if you require a new OSDBA group for
ASM, then create it as follows. In the following procedure, use the group name
asmdba unless a group with that name already exists:
# /usr/sbin/groupadd -g 506 asmdba
Oracle Real Application Clusters Preinstallation Tasks 3-7