Use this checklist to plan operating system users, groups, and environments for Oracle Grid Infrastructure installation.
Table 1-5 User Environment Configuration for Oracle Grid Infrastructure
|Review Oracle Inventory (oraInventory) and OINSTALL Group Requirements||
The Oracle Inventory directory is the central inventory of Oracle software installed on your system. It should be the primary group for all Oracle software installation owners. Users who have the Oracle Inventory group as their primary group are granted the OINSTALL privilege to read and write to the central inventory.
Ensure that the group designated as the OINSTALL group is available as the primary group for all planned Oracle software installation owners.
|Create operating system groups and users for standard or role-allocated system privileges||
Create operating system groups and users depending on your security requirements, as described in this installation guide.
Set resource limits settings and other requirements for Oracle software installation owners.
Group and user names must use only ASCII characters.
Note:Do not delete an existing daemon user. If a daemon user has been deleted, then you must add it back.
|Unset Oracle Software Environment Variables||
If you have an existing Oracle software installation, and you are using the same user to install this installation, then unset the following environment variables:
If you have set
|Configure the Oracle Software Owner Environment||
Configure the environment of the oracle or grid user by performing the following tasks:
|Determine root privilege delegation option for installation||
During installation, you are asked to run configuration scripts as the root user. You can either run these scripts manually as root when prompted, or during installation you can provide configuration information and passwords using a root privilege delegation option.
To run root scripts automatically, select Automatically run configuration scripts. during installation. To use the automatic configuration option, the root user credentials for all cluster member nodes must use the same password.