Checking and Configuring the Server for Oracle Database

Verify that servers where you install Oracle Database meet the minimum requirements for installation.

This section provides minimum server requirements to complete installation of Oracle Database. It does not provide system resource guidelines, or other tuning guidelines for particular workloads.

Logging In to a Remote System Using X Window System

This procedure enables Oracle Universal Installer (OUI) to run on a remote server while displaying its graphical interface on a local X Window System client. Start an X session, permit the remote host with xhost + RemoteHost, connect to the installation server using ssh -Y, and switch to root when required; repeat the process for each installation owner account, such as oracle or grid, and consult the X server documentation if command order or security settings differ.

Setting Remote Display and X11 Forwarding Configuration

Configure the remote display by setting DISPLAY to the local host and display number, using export DISPLAY=hostname:0 for Bourne, Korn, or Bash shells or setenv DISPLAY hostname:0 for C shell. To prevent installation failures caused by X11 forwarding, create or edit each Oracle installation owner’s ~/.ssh/config, set ForwardX11 no for all hosts, and secure the .ssh directory and its contents so they are accessible only to the installation owner.

Checking Server Hardware and Memory Configuration

Verify that the server meets installation requirements by checking physical memory with /proc/meminfo, configured swap, available /tmp space, free memory and swap with free, processor architecture with uname -m, and shared memory sizing and mounting with df -h /dev/shm. Add memory or swap, clean /tmp without removing Oracle temporary directories, or configure TMP and TMPDIR when necessary, and confirm that the architecture matches the Oracle software release.

Preventing Installation Errors Caused by Terminal Output Commands

Because OUI uses SSH to execute commands and transfer files across Grid Infrastructure nodes, remove or conditionally suppress terminal-output commands in hidden shell startup files such as .bashrc and .cshrc for every Oracle installation owner. Commands such as stty must run only in interactive terminals, using appropriate Bourne-style or C-shell conditionals, because output from remotely loaded startup files can cause OUI to report errors and stop the installation.
Read More: Preventing Installation Errors Caused by Terminal Output Commands