Configuring Users Groups and Environments for Oracle Grid Infrastructure and Oracle AI Database

Creating Groups Users and Paths for Oracle Grid Infrastructure

Describes how to prepare Oracle Grid Infrastructure installation accounts, groups, inventory, and directories. It covers locating or creating the Oracle Inventory group, ensuring consistent user and group IDs across cluster nodes, selecting separate Grid and database owners, assigning required privilege groups, configuring non-symlink Oracle base and Grid home paths, and creating directories with appropriate ownership and permissions. It also emphasizes using a shared central inventory, separate Grid homes, local installation of cluster binaries, and avoiding Grid homes beneath Oracle base or owner home directories.

Oracle Installations with Standard and Job Role Separation Groups and Users

Explains standard and job-role-separated operating system authentication for Oracle Grid Infrastructure, ASM, and databases. It defines the Oracle Inventory, OSDBA, OSOPER, OSASM, OSDBA for ASM, OSBACKUPDBA, OSDGDBA, OSKMDBA, and OSRACDBA groups, describing their privileges and recommended separation by installation or database. It also covers the ASMSNMP monitoring account and distinguishes shared administrative configurations from role-specific users and groups designed to limit database and storage administration privileges.

Creating Operating System Privileges Groups

Provides commands and guidance for creating the operating system groups used by Oracle Grid Infrastructure, ASM, RAC, and database installations. It covers the OSASM, OSDBA for ASM, OSOPER for ASM, OSDBA, OSOPER, OSBACKUPDBA, OSDGDBA, OSKMDBA, and OSRACDBA groups, including their typical names, numeric IDs, and associated Oracle privileges such as SYSASM, SYSDBA, SYSOPER, SYSBACKUP, SYSDG, SYSKM, and SYSRAC.

Creating Operating System Oracle Installation User Accounts

Explains how to create and configure Oracle software owners such as grid, oracle, oracle1, and oracle2, ensuring the Oracle Inventory group is their primary group and assigning appropriate secondary privilege groups. It describes modifying existing accounts without changing their primary inventory group, identifying and synchronizing user and group IDs across cluster nodes, setting passwords, and configuring environments. It also provides minimal shared-privilege and fully role-separated examples with corresponding Oracle base and Grid home ownership and permissions.

Configuring Software Owner User Environments

Details the environment preparation required for Oracle installation owners. It instructs administrators to set umask 022, configure resource limits, establish X display access, remove conflicting Oracle variables, set DISPLAY when installing remotely, and provide a private temporary directory with sufficient space when /tmp is inadequate. It also explains how to edit and reload shell startup files, verify settings, and unset variables such as ORACLE_HOME, ORA_NLS10, TNS_ADMIN, and ORA_CRS_HOME to prevent installation conflicts.

Enabling Intelligent Platform Management Interface Ipmi

Explains how IPMI supports Oracle Clusterware failure isolation and node fencing through BMC-managed hardware. It specifies requirements for compatible BMC firmware, IPMI utilities, management networking, and persistent drivers; provides Linux OpenIPMI module configuration and device verification steps; and describes configuring BMC networking, authentication, LAN access, and administrator accounts with ipmitool. Remote validation must be performed from another cluster node, using identical credentials and working IPMI connectivity on every node.

Checking Resource Limits for Oracle Software Installation Users

Describes how to verify and configure resource limits for each Oracle installation owner. Recommended minimums include 1,024 soft and 65,536 hard open files, 2,047 soft and 16,384 hard processes, a 10,240 KB stack soft limit with a maximum hard limit of 32,768 KB, and locked memory equal to at least 90 percent of RAM with HugePages or 3 GB without HugePages. Limits can be checked with ulimit or cluvfy, adjusted in /etc/security/limits.conf, and activated by logging users out and back in.
Read More: Checking Resource Limits for Oracle Software Installation Users