1. Database Client Installation Guide
  2. Oracle Database Client Installation Checklist
  3. Server Configuration Checklist for Oracle Database Client

Server Configuration Checklist for Oracle Database Client

Use this checklist to check minimum server configuration requirements for Oracle Database Client installations.

Table 1-3 Server Configuration Checklist for Oracle Database Client

Check Task
Disk space allocated to the /tmp directory At least 400 MB of space in the temporary disk space (/tmp) directory.
Swap space allocation relative to RAM

256 MB: 3 times the size of RAM
Between 256 MB and 512 MB: 2 times the size of RAM
Between 512 MB and 2 GB: 1.5 times the size of RAM
Between 2 GB and 16 GB: Equal to the size of RAM
More than 16 GB: 16 GB
Note: If you enable HugePages for your Linux servers, then you should deduct the memory allocated to HugePages from the available RAM before calculating swap space.

Oracle Inventory (oraInventory) and OINSTALL Group Requirements

  • For new installs, if you have not configured an oraInventory directory, then the installer creates an Oracle inventory that is one directory level up from the Oracle base for the Oracle Grid Infrastructure install, and designates the installation owner's primary group as the Oracle Inventory group.

  • For upgrades, Oracle Universal Installer (OUI) detects an existing oraInventory directory from the /etc/oraInst.loc file, and uses the existing oraInventory.

The Oracle Inventory directory is the central inventory of Oracle software installed on your system. Users who have the Oracle Inventory group as their primary group are granted the OINSTALL privilege to write to the central inventory.

The OINSTALL group must be the primary group of all Oracle software installation owners on the server. It should be writable by any Oracle installation owner.
Groups and users Oracle recommends that you create groups and user accounts required for your security plans before starting installation. Installation owners have resource limits settings and other requirements. Group and user names must use only ASCII characters.
Mount point paths for the software binaries Oracle recommends that you create an Optimal Flexible Architecture configuration as described in the appendix "Optimal Flexible Architecture" in Oracle Database Installation Guide for your platform.
Ensure that the Oracle home (the Oracle home path you select for Oracle Database) uses only ASCII characters

The ASCII character restriction includes installation owner user names, which are used as a default for some home paths, as well as other directory names you may select for paths.

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 you can provide configuration information and passwords using a root privilege delegation option such as Sudo.

To enable Sudo, have a system administrator with the appropriate privileges configure a user that is a member of the sudoers list, and provide the username and password when prompted during installation.

Set locale (if needed)

Specify the language and the territory, or locale, in which you want to use Oracle components. A locale is a linguistic and cultural environment in which a system or program is running. NLS (National Language Support) parameters determine the locale-specific behavior on both servers and clients. The locale setting of a component determines the language of the user interface of the component, and the globalization behavior, such as date and number formatting.

symlinks

Oracle home or Oracle base cannot be symlinks, nor can any of their parent directories, all the way to up to the root directory.

Related Topics

Parent topic: Oracle Database Client Installation Checklist