Oracle Database Oracle Clusterware Installation Guide for HP-UX

Creating Custom Configuration Groups and Users for Job Roles
3.2.2.5.3 Modifying an Existing Oracle Software Owner User If the oracle user exists, but
its primary group is not oinstall, or it is not a member of the appropriate OSDBA or
OSOPER groups, then enter a command similar to the following to modify it. Specify
the primary group using the -g option and any required secondary group using the
-G option:
# /usr/sbin/usermod -g oinstall -G dba[,oper] oracle
Repeat this procedure on all of the other nodes in the cluster.
3.2.2.6 Creating a Separate ASM Owner
1. To create asm, enter a command similar to the following:
# /usr/sbin/useradd -u 504 -g oinstall -G asm asm
In the preceding command:
■ The -u option specifies the user ID. Using this command flag is optional, as
you can allow the system to provide you with an automatically generated user
ID number. However, you must make note of the asm ID number, as you
require it later during preinstallation.
■ The -g option specifies the primary group, which must be the Oracle
Inventory group--for example, oinstall
■ The -G option specifies the secondary groups, which must include the OSASM
group. For example: asm.
2. Set the password for asm:
# passwd asm
3.2.2.7 Verifying That the User nobody Exists
Before installing the software, complete the following procedure to verify that the user
nobody exists on the system:
1. To determine if the user exists, enter the following command:
# id nobody
If this command displays information about the nobody user, then you do not
have to create that user.
2. If the nobody user does not exist, then enter the following command syntax to
create it:
# /usr/sbin/useradd -u number nobody
for example:
# /usr/sbin/useradd -u 65555 nobody
3. Repeat this procedure on all the other nodes in the cluster.
Oracle Real Application Clusters Preinstallation Tasks 3-9