Installation guide

Page 22 of 59
To install and manage OracleAS, a monitor is recommended, whether locally attached or
networked through a KVM. The monitor should support at last a 256 color display. If
problems are encountered with a monitor, they are more commonly the fault of improper
driver settings at the OS level, rather than an actual hardware restriction. To verify the
performance of a monitor (or more specifically, the monitor driver) in Linux, issue the
following command:
# /usr/X11R6/bin/xdpyinfo (check for a depth of at least 8 bits per pixel)
Oracle Application Server can require a substantial amount of memory, depending on the
modules that are installed on a specific server. The memory required is cumulative, so if
you install all modules on the same server, you may need as much as 3.5 GB of RAM/
Keep in mind that you should reserve approximately 1 GB for the OS. Table 1 shows the
memory required per tier:
OracleAS Tier Memory Required
J2EE and Web Cache 512 MB
Portal and Wireless 1 GB
Business Intelligence and Forms 1 GB
OracleAS Infrastructure 1 GB
Table 1
To verify the RAM available in Linux, use the following command:
# grep MemTotal /proc/meminfo
OracleAS also requires a certain amount of disk space for each component, as well as
disk space for temporary storage and OS swap space. In general, each server in an
OracleAS cluster will have its own copy of data on disk, the contents of which are locally
managed. The disk space may be local to the server or on an external SAN or NAS
device. Only a couple of cases require disks shared between nodes – Oracle Failover
Clusters (not covered here), and the Metadata Repository, if it is stored in a Real
Application Cluster Database. In these two cases, the disk must be on an external SAN
or NAS device. Table 2 shows the disk requirements: