Oracle software owner users and the Oracle Inventory, OSDBA, and OSOPER groups must exist and be identical on all cluster nodes.

1. Log in to the node as root.
2. Enter commands similar to the following to create the asmadmin, asmdba, backupdba, dgdba, kmdba, asmoper, racdba, and oper groups, and if not configured by the Oracle Preinstallation RPM or prior installations, then the oinstall and dba groups.

   Use the id option to specify the correct group ID for each group.

   # mkgroup -A id=54421 oinstall
   # mkgroup -A id=54322 dba
   # mkgroup -A id=54323 oper
   # mkgroup -A id=54324 backupdba
   # mkgroup -A id=54325 dgdba
   # mkgroup -A id=54326 kmdba
   # mkgroup -A id=54327 asmdba
   # mkgroup -A id=54328 asmoper
   # mkgroup -A id=54329 asmadmin
   # mkgroup -A id=54330 racdba

   Note:

   You are not required to use the UIDs and GIDs in this example. If a group already exists, then use the groupmod command to modify it if necessary. If you cannot use the same group ID for a particular group on a node, then view the /etc/group file on all nodes to identify a group ID that is available on every node. You must then change the group ID on all nodes to the same group ID.
3. To create the Oracle Grid Infrastructure (grid) user, enter a command similar to the following:

   # mkuser id=54322 pgrp=oinstall groups=asmadmin,asmdba,racdba grid

   • The id option specifies the user ID, which must be the user ID that you identified in the previous subsection.

   • The pgrp option specifies the primary group for the Grid user, which must be the Oracle Inventory group (OINSTALL), which grants the OINSTALL system privileges. In this example, the OINSTALL group is oinstall.

   • The groups option specifies the secondary groups. The Grid user must be a member of the OSASM group (asmadmin) and the OSDBA for ASM group (asmdba).

   Note:

   If the user already exists, then use the usermod command to modify it if necessary. If you cannot use the same user ID for the user on every node, then view the /etc/passwd file on all nodes to identify a user ID that is available on every node. You must then specify that ID for the user on all of the nodes.
4. Set the password of the user.

   For example:

   # passwd grid

5. Ensure that the Oracle software owner user has the capabilities CAP_NUMA_ATTACH, CAP_BYPASS_RAC_VMM, and CAP_PROPAGATE.
   1. To check existing capabilities, enter the following command as root; in this example, the Oracle Database installation user account is grid:

      # /usr/bin/lsuser -a capabilities grid

   2. To add capabilities, enter a command similar to the following:

      # /usr/bin/chuser 
      capabilities=CAP_NUMA_ATTACH,CAP_BYPASS_RAC_VMM,CAP_PROPAGATE grid

6. Complete user environment configuration tasks for each user.