Skip Headers

Oracle® Application Server Installation Guide 10g Release 3 (10.1.3) for Linux x86 B25217-01 |
| Home | Contents | Index

Previous | Next |

# 2 Requirements

Before installing Oracle Application Server, ensure that your computer meets the requirements described in this chapter.

Table 2-1 Sections in This Chapter

Section | Highlights
--- | ---
Section 2.1, "Using OracleMetaLink to Obtain the Latest Oracle Application Server Hardware and Software Requirements" | Describes how to find the most current requirements for Oracle Application Server 10g Release 3 (10.1.3).
Section 2.2, "System Requirements" | Lists requirements such as supported processor speed, memory, disk space, and swap space.
Section 2.3, "Software Requirements" | Lists requirements such as supported operating systems, operating system patches, software packages, and Linux x86-64 certification informations.
Section 2.4, "Set Shell Limits for the oracle User" | Lists the shell limits for the `oracle` user.
Section 2.5, "Ports" | Describes how to configure components to use ports other than the default ports.
Section 2.6, "Operating System Groups" | Describes why the operating system user who installs Oracle Application Server should belong to certain operating system groups.
Section 2.7, "Operating System User" | Describes why you should create an operating system user to install Oracle Application Server.
Section 2.8, "Environment Variables" | Describes how to set or unset environment variables required for installation.
Section 2.9, "Network Topics" | Describes network issues such as installing Oracle Application Server on a remote computer, using a remote CD-ROM/DVD-ROM drive, or installing from a hard disk.
Section 2.10, "Prerequisite Checks Performed by the Installer" | Lists the items checked by the installer, such as length of the Oracle home name and whether or not the Oracle home directory already contains another Oracle product.

## 2.1 Using OracleMetaLink to Obtain the Latest Oracle Application Server Hardware and Software Requirements

The Oracle Application Server 10g (10.1.3) hardware and software requirements included in this guide were accurate at the time this manual was released to manufacturing. For the most up-to-date information about hardware and software requirements, refer to OracleMetaLink:

    http://metalink.oracle.com/

After logging into OracleMetaLink, click Certify. From the resulting Web page, you can view the latest certifications by product, platform, and product availability.

## 2.2 System Requirements

Table 2-2 lists the system requirements for running Oracle Application Server. The installer checks many of these requirements at the start of the installation process and warns you if any of them is not met. To save time, you can manually check only the ones that are not checked by the installer. Refer to Table 2-2 to see which requirements are not checked by the installer.

You can also run the system checks performed by the installer without doing an installation, by running the `runInstaller` command as shown. The `runInstaller` command is on the Oracle Application Server CD-ROM (Disk 1) or DVD-ROM (in the `application_server` directory).

CD-ROM:

    prompt> mount_point/runInstaller -executeSysPrereqs

DVD-ROM:

    prompt> mount_point/application_server/runInstaller -executeSysPrereqs

The results are displayed on the screen as well as written to a log file. For more information on the types of checks performed, see Section 2.10, "Prerequisite Checks Performed by the Installer".

Table 2-2 System Requirements

Item | Requirement
--- | ---
Network | You can install Oracle Application Server on a computer that is connected to a network, or on a "standalone" computer (not connected to the network). If you are installing Oracle Application Server on a standalone computer, you can connect the computer to a network after installation. You have to perform some configuration tasks when you connect it to the network; see the Oracle Application Server Administrator's Guide for details. Checked by Installer: No
IP | The computer's IP address can be static or allocated using DHCP. If you later change the IP configuration, see the Oracle Application Server 10g Administrator's Guide for information on reconfiguring Oracle Application Server. See Section 2.9.1, "Installing on a DHCP Host" for additional requirements. Checked by Installer: No
Hostname | Ensure that your hostnames are not longer than 255 characters. Checked by Installer: No
Processor type | Pentium (32-bit) To determine the processor type, run the following command:
    prompt> cat /proc/cpuinfo | grep name
    model name      : Intel(R) Pentium(R) 4 CPU 3.00GHz
Checked by Installer: No
Processor Speed | 300 MHz or faster To determine the processor speed, run the following command:
    prompt> cat /proc/cpuinfo | grep MHz
    cpu MHz         : 2992.553
Checked by Installer: Yes
Memory | 512 MB The memory requirement provided represents enough physical memory to install and run Oracle Application Server. However, for most production sites, you should configure at least 1 GB of physical memory. For sites with substantial traffic, increasing the amount of memory further may improve your performance. For Java applications, you should either increase the maximum heap allocated to the OC4J processes, or configure additional OC4J processes to utilize this memory. See the Oracle Application Server Performance Guide for details. To determine the optimal amount of memory for your installation, the best practice is to load test your site. Resource requirements can vary substantially for different applications and different usage patterns. In addition, some operating system utilities for monitoring memory can overstate memory usage (partially due to the representation of shared memory). The preferred method for determining memory requirements is to monitor the improvement in performance resulting from the addition of physical memory in your load test. Refer to your platform vendor documentation for information on how to configure memory and processor resources for testing purposes. Notes: The installer checks the amount of memory on your computer and will warn you if your computer does not meet the minimum memory requirements. To determine the amount of memory, enter the following command:
    prompt> grep MemTotal /proc/meminfo
Checked by Installer: Yes
Disk space | Integrated Web Server, J2EE Server and Process Management: 678MB J2EE Server and Process Management: 641 MB Web Server and Process Management: 558 MB Oracle TopLink: 154 MB The installer may display inaccurate disk space requirement figures. Refer to the figures listed above for disk space requirements. To determine the amount of free disk space, use the `df` command:
    prompt> df -k dir
Replace dir with the Oracle home directory or with the parent directory if the Oracle home directory does not exist yet. For example, if you plan to install Oracle Application Server in `/opt/oracle/j2ee`, you can replace dir with `/opt/oracle` or `/opt/oracle/j2ee`. Checked by Installer: No
Space in `/tmp` or directory | 400 MB To determine the amount of free disk space in the `/tmp` directory, use the `df` command:
    prompt> df -k /tmp
If the `/tmp` directory does not have enough free space, you can specify a different directory by setting the TMP or TMPDIR environment variable. See Section 2.8.6, "TMP and TMPDIR" for details. Checked by Installer: Yes
Swap space | 512 MB of available swap space To determine the amount of available swap space, enter the following command:
    prompt> grep SwapTotal /proc/meminfo
If necessary, see your operating system documentation for information on how to configure additional swap space. Checked by Installer: Yes
Monitor | 256 color display To determine your monitor's display capabilities, run the following command:
    prompt> /usr/X11R6/bin/xdpyinfo
Look for the "depths" line. You need a depth of at least 8 (bits per pixel). Checked by Installer: Yes
Supported browsers | Oracle Enterprise Manager 10g is supported on the following browsers: Microsoft Internet Explorer 6.0 SP2 (supported on Microsoft Windows only) Netscape 7.2 Mozilla 1.7. You can download Mozilla from `http://www.mozilla.org`. Firefox 1.0.4. You can download Firefox from `http://www.mozilla.org`. Safari 1.2, 2.0 (on Apple Macintosh computers) For the most current list of supported browsers, check the OracleMetaLink site (`http://metalink.oracle.com`). Checked by Installer: No. However, if you access Oracle Enterprise Manager 10g using a non-supported browser, you will get a warning message.

### 2.2.1 Installing from the Console or X Windows

If you are performing the installation from the console or X Windows, then add the following line to the `/etc/pam.d/xdm` file:

    session required pam_limits.so

## 2.3 Software Requirements

Depending on your distribution of Linux, see one of the following sections for information on checking the software requirements:

- Section 2.3.1, "Software Requirements for Red Hat Enterprise Linux AS/ES 3.0 Systems"

- Section 2.3.2, "Software Requirements for Red Hat Enterprise Linux AS/ES 4.0 Systems"

- Section 2.3.3, "Software Requirements for SUSE Linux Enterprise Server 9 Systems"

Oracle does not support customized kernels or modules not supported by the Linux vendor.

You can install Oracle Application Server 10g Release 3 (10.1.3) on a Linux system that is not on a network and you can install Oracle Application Server 10g Release 3 (10.1.3) on a Linux system that is configured to use DHCP. If you want to install Oracle Application Server on a computer that is not on a network you must configure the computer to use either a static IP address or a loopback IP address. Configure the computer to resolve the hostname of the computer to either a static IP address or a loopback IP address.

### 2.3.1 Software Requirements for Red Hat Enterprise Linux AS/ES 3.0 Systems

Table 2-3 lists the software requirements for Red Hat Enterprise Linux AS/ES 3.0 systems and the procedure that follows the table describes how to ensure your system meets these requirements and any additional requirements for installing Oracle Application Server.

Note: Red Hat Enterprise Linux AS/ES 3.0, 4.0 and SUSE Linux Enterprise Server 9 are certified and supported. For the most current list of supported Linux Operating Systems, check OracleMetaLink (`http://metalink.oracle.com`).

Table 2-3 Software Requirements for Red Hat Enterprise Linux AS/ES 3.0 Systems

Item | Requirement
--- | ---
Operating System | Red Hat Enterprise Linux AS/ES 3.0 For more information on Red Hat, see:
    http://www.redhat.com
Red Hat Update | Update 3
Software packages (check that these versions or higher versions are installed) |
    glibc-2.3.2-95.27
    glibc-common-2.3.2-95.27
    binutils-2.14.90.0.4-35
    compat-glibc-7.x-2.2.4.32.6
    compat-libstdc++-7.3-2.96.128
    compat-libstdc++-devel-7.3-2.96.128
    gcc-3.2.3-42
    gcc-c++-3.2.3-42
    libstdc++-3.2.3-42
    libstdc++-devel-3.2.3-42
    openmotif21-2.1.30-8
    pdksh-5.2.14-21
    setarch-1.3-1
    make-3.79.1-17
    gnome-libs-1.4.1.2.90-34.1
    sysstat-4.0.7-4.EL3.3
    compat-db-4.0.14-5
Note: For Red Hat Enterprise Linux AS/ES 3.0, the equivalent version of `openmotif 2.1.30-8` is `openmotif21-2.1.30-8`. The `openmotif21-2.1.30-8` package can be installed from disk number 3 of the Red Hat Enterprise Linux AS/ES 3.0 distribution by entering:
    $ rpm -ivh openmotif21-2.1.30-8
64-bit Certification | Red Hat Enterprise Linux AS/ES 3.0, Update 3 or higher, is certified on AMD64 and Intel EM64T. The following packages (or higher versions) are required:
    glibc-2.3.2-95.27.x86_64.rpm
    glibc-3.2.3-95.27.i686.rpm (32-bit)
    glibc-devel-3.2.3-95.27.x86_64.rpm
    glibc-devel-3.2.3-95.27.i386.rpm (32-bit)
    gcc-3.2.3-20.x86_64.rpm
    libgcc-3.2.3-20.x86_64.rpm
    libgcc-3.2.3-20.i386.rpm (32-bit)
    setarch-1.3-1.x86_64.rpm
    pdksh-5.2.14-21.x86_64.rpm
    openmotif21-2.1.30-8.i386.rpm
    compat-glibc-7.x-2.2.4.32.5.i386.rpm (32-bit)
    compat-gcc-7.3-2.96.122.i386.rpm
    sysstat-4.0.7-4.x86_64.rpm
    gnome-libs-1.4.1.2.90-34.1.i386.rpm (32-bit)
    compat-db-4.0.14-5.1.i386.rpm (32-bit)
- Note the following: To install 32-bit packages on a 64-bit system, you may need to use the `--force` option and the `--nodeps` option of the `rpm` utility. Always use 32-bit shell emulation, use the following command before running the installer and any other Oracle Application Server commands or scripts:
      # linux32 bash

To ensure that the system meets all the requirements, follow these steps:

1. Log in as the `root` user.

2. To determine which distribution and version of Linux is installed, enter the following command:

       # cat /etc/issue
       Red Hat Enterprise Linux AS release 3 (Taroon)

   Note: Red Hat Enterprise Linux AS/ES 3.0, 4.0 and SUSE Linux Enterprise Server 9 are certified and supported. For the most current list of supported Linux Operating Systems, check OracleMetaLink (`http://metalink.oracle.com`).

3. To check that Update 3 is installed:

       # cat /etc/redhat-release
       Red Hat Enterprise Linux AS release 3 (Taroon Update 3)

4. To determine whether any other package is installed, enter a command similar to the following:

       # rpm -q package_name

   If a package is missing, download it and install it using the following command:

       # rpm -i package_name

   When installing a package, make sure you are using the correct architecture and optimization rpm file. To check the architecture of an rpm file, run the following command:

       # rpm -q package_name --queryformat "%{arch}\n"

   In the following example, the glibc rpm file is suitable for an Intel architecture

       # rpm -q glibc --queryformat "%{arch}\n"
       i686

5. If the `hugemem` kernel is used, set the architecture using following command:

       prompt> setarch i386

### 2.3.2 Software Requirements for Red Hat Enterprise Linux AS/ES 4.0 Systems

Table 2-4 lists the software requirements for Red Hat Enterprise Linux AS/ES 4.0 systems and the procedure that follows the table describes how to ensure your system meets these requirements and any additional requirements for installing Oracle Application Server.

Note: Red Hat Enterprise Linux AS/ES 3.0, 4.0 and SUSE Linux Enterprise Server 9 are certified and supported. For the most current list of supported Linux Operating Systems, check OracleMetaLink (`http://metalink.oracle.com`).

Table 2-4 Software Requirements for Red Hat Enterprise Linux AS/ES 4.0 Systems

Item | Requirement
--- | ---
Operating System | Red Hat Enterprise Linux AS/ES 4.0 For more information on Red Hat, see:
    http://www.redhat.com
Red Hat Update | Update 1
Software packages (check that these versions or higher versions are installed) |
    glibc-2.3.4-2.9
    glibc-common-2.3.4-2.9
    binutils-2.15.92.0.2-13
    compat-libstdc++-296-2.96-132.7.2
    gcc-3.4.3-22.1
    gcc-c++-3.4.3-22.1
    libstdc++-3.4.3-22.1
    libstdc++-devel-3.4.3-22.1
    openmotif21-2.1.30-11.RHEL4.4
    pdksh-5.2.14-30
    setarch-1.6-1
    make-3.80-5
    gnome-libs-1.4.1.2.90-44.1
    sysstat-5.0.5-1
    compat-db-4.1.25-9
    control-center-2.8.0-12
    xscreensaver-4.18-5.rhel4.2
64-bit Certification | Red Hat Enterprise Linux AS/ES 4.0, Update 1 or higher, is certified on AMD64 and Intel EM64T. The following packages (or higher versions) are required:
    binutils-2.15.92.0.2-13.x86_64.rpm
    compat-db-4.1.25-9.i386.rpm (32-bit)
    compat-db-4.1.25-9.x86_64.rpm
    control-center-2.8.0-12.x86_64.rpm
    gcc-3.4.3-22.1.x86_64.rpm
    gcc-c++-3.4.3-22.1.x86_64.rpm
    glibc-2.3.4-2.9.i686.rpm (32-bit)
    glibc-2.3.4-2.9.x86_64.rpm
    glibc-common-2.3.4-2.9.x86_64.rpm
    gnome-libs-1.4.1.2.90-44.1.x86_64.rpm
    libstdc++-3.4.3-22.1.i386.rpm (32-bit)
    libstdc++-3.4.3-22.1.x86_64.rpm
    libstdc++-devel-3.4.3-22.1.i386.rpm (32-bit)
    libstdc++-devel-3.4.3-22.1.x86_64.rpm
    make-3.80-5.x86_64.rpm
    pdksh-5.2.14-30.x86_64.rpm
    sysstat-5.0.5-1.x86_64.rpm
    xscreensaver-4.18-5.rhel4.2.x86_64.rpm
    setarch-1.6-1.x86_64
    openmotif21-2.1.30-11.RHEL4.4.i386.rpm (32-bit)
- Note the following: To install 32-bit packages on a 64-bit system, you may need to use the `--force` option and the `--nodeps` option of the `rpm` utility. Always use 32-bit shell emulation, use the following command before running the installer and any other Oracle Application Server commands or scripts:
      # linux32 bash

To ensure that the system meets all the requirements, follow these steps:

1. Log in as the `root` user.

2. To determine which distribution and version of Linux is installed, enter the following command:

       # cat /etc/issue
       Red Hat Enterprise Linux AS release 4 (Nahant Update 1)

   Note: Red Hat Enterprise Linux AS/ES 3.0, 4.0 and SUSE Linux Enterprise Server 9 are certified and supported. For the most current list of supported Linux Operating Systems, check OracleMetaLink (`http://metalink.oracle.com`).

3. To check that Update 1 is installed:

       # cat /etc/redhat-release
       Red Hat Enterprise Linux AS release 4 (Nahant Update 1)

4. To determine whether any other package is installed, enter a command similar to the following:

       # rpm -q package_name

   If a package is missing, download it and install it using the following command:

       # rpm -i package_name

   When installing a package, make sure you are using the correct architecture and optimization rpm file. To check the architecture of an rpm file, run the following command:

       # rpm -q package_name --queryformat "%{arch}\n"

   In the following example, the glibc rpm file is suitable for an Intel architecture

       # rpm -q glibc --queryformat "%{arch}\n"
       i686

5. If the `hugemem` kernel is used, set the architecture using following command:

       prompt> setarch i386

### 2.3.3 Software Requirements for SUSE Linux Enterprise Server 9 Systems

Table 2-5 lists the software requirements for SUSE Linux Enterprise Server 9 systems and the procedure that follows the table describes how to ensure your system meets these requirements and any additional requirements for installing Oracle Application Server.

Note: Oracle Application Server 10g Release 3 (10.1.3) is certified with the following Operating System specific software. For the most current list of supported Operating System specific software, for example JDK version, Operating System version, check OracleMetaLink (`http://metalink.oracle.com`).

Table 2-5 Software Requirements for SUSE Linux Enterprise Server 9 Systems

Item | Requirement
--- | ---
Operating System | SUSE Linux Enterprise Server 9 For more information on SUSE Linux Enterprise Server, see:
    http://www.suse.com
Software packages (check that these versions or higher versions are installed) |
    glibc-2.3.3-98.28
    gcc-3.3.3-43.24
    gcc-c++-3.3.3-43.24
    libstdc++-3.3.3-43.24
    libstdc++-devel-3.3.3-43.24
    openmotif21-libs-2.1.30MLI4-119.1
    pdksh-5.2.14-780.1
    make-3.80-184.1
    gnome-libs-1.4.1.7-671.1
    gnome-libs-devel-1.4.1.7-671.1
    sysstat-5.0.1-35.1
    binutils-2.15.90.0.1.1-32.5
64-bit Certification | SUSE Linux Enterprise Server is certified on AMD64 and Intel EM64T. The following packages (or higher versions) are required:
    glibc-2.3.3-98.28.x86_64.rpm
    glibc-32bit-9-200407011233.x86_64.rpm
    glibc-devel-32bit-9-200407011229.x86_64.rpm
    gcc-3.3.3-43.24.x86_64.rpm
    gcc-3.2.3-20.x86_64.rpm
    gcc-c++-3.3.3-43.24.x86_64.rpm
    libgcc-3.2.3-20.i386.rpm (32-bit)
    libstdc++-3.3.3-43.24.x86_64.rpm
    libstdc++-devel-3.3.3-43.24.x86_64.rpm
    libstdc++-devel-32bit-9-200407011229.x86_64.rpm
    gnome-libs-1.4.1.7-671.1.x86_64.rpm
    gnome-libs-devel-1.4.1.7-671.1.x86_64.rpm
    gnome-libs-32bit-9-200407011229.x86_64.rpm
    binutils-2.15.90.0.1.1-32.5.x86_64.rpm
    binutils-32bit-9-200407011229.x86_64.rpm
    compat-32bit-9-200407011229.x86_64.rpm
    compat-sles8-1.3-93.3.x86_64.rpm
    compat-2004.7.1-1.2.x86_64.rpm
    pdksh-5.2.14-780.1.x86_64.rpm
    make-3.80-184.1.x86_64.rpm
    sysstat-5.0.1-35.1.x86_64.rpm
    perl-32bit-9-200407011229.x86_64.rpm
    libaio-devel-32bit-9-200407011229.x86_64.rpm
    XFree86-devel-32bit-9-200407011229.x86_64.rpm
    linux32-1.0-341.1.x86_64.rpm
    db-32bit-9-200407011229.x86_64.rpm
    db1-32bit-9-200407011229.x86_64.rpm
    compat-32bit-9-200407011229.x86_64.rpm
Always use 32-bit shell emulation, use the following command before running the installer and any other Oracle Application Server commands or scripts:
    # linux32 bash

To ensure that the system meets all the requirements, follow these steps:

1. Log in as the `root` user.

2. To determine which distribution and version of Linux is installed, enter the following command:

       prompt> cat /etc/issue
       Welcome to SuSE Linux 9.0 (i686) - Kernel \r (\l).

   Note: Red Hat Enterprise Linux AS/ES 3.0, 4.0 and SUSE Linux Enterprise Server 9 are certified and supported. For the most current list of supported Linux Operating Systems, check OracleMetaLink (`http://metalink.oracle.com`).

3. To determine whether any other package is installed, enter a command similar to the following:

       prompt> rpm -q package_name

   If a package is missing, download it and install it using the following command:

       prompt> rpm -i package_name

   When installing a package, make sure you are using the correct architecture and optimization rpm file. To check the architecture of an rpm file, run the following command:

       prompt> rpm -q package_name --queryformat "%{arch}\n"

   In the following example, the glibc rpm file is suitable for an Intel architecture

       prompt> rpm -q glibc --queryformat "%{arch}\n"
       i686

4. Create the following symbolic link for the Perl executable if it does not already exist:

       prompt> ln -sf /usr/bin/perl /usr/local/bin/perl

5. Create the following symbolic link for the `fuser` executable if it does not already exist:

       prompt> ln -sf /bin/fuser /sbin/fuser

6. If the `orarun` package was installed on a SUSE Linux Enterprise Server system, complete the following steps as the `oracle` user to reset the environment:

   1. Enter the following commands:

          prompt> cd /etc/profile.d
          prompt> mv oracle.csh oracle.csh.bak
          prompt> mv oracle.sh oracle.sh.bak
          prompt> mv alljava.sh alljava.sh.bak
          prompt> mv alljava.csh alljava.csh.bak

   2. Use any text editor to comment out the following line from the `$HOME/.profile` file:

          . ./.oracle

   3. Log out of the `oracle` user account.

   4. Log into the `oracle` user account for the changes to take effect.

7. If any Java packages are installed on the system, unset the Java environment variables, for example JAVA_HOME.

   Note: Oracle recommends that you do not install any of the Java packages supplied with the SUSE Linux Enterprise Server distribution.

8. If you use Network Information Service (NIS):

   1. Make sure that the following line exists in the `/etc/yp.conf` file:

          hostname.domainname broadcast

   2. Make sure that the following line exists in the`/etc/nsswitch.conf` file:

          hosts: files nis dns

9. Make sure that the `localhost` entry in the `/etc/hosts` file is an IPv4 entry. If the IP entry for `localhost` is IPv6 format, installation cannot succeed. The following example shows an IPv6 entry:

       prompt> special IPv6 addresses
       ::1             localhost ipv6-localhost ipv6-loopback
       ::1             ipv6-localhost ipv6-loopback

   To correct this example `/etc/hosts` file, comment the localhost entry as follows:

       prompt> special IPv6 addresses
       prompt> ::1             localhost ipv6-localhost ipv6-loopback
       ::1             ipv6-localhost ipv6-loopback

   To comment the entries, you can use the perl script included in the `utils/4015045/` directory of CD-ROM Disk 1 and in the `application_server/utils/4015045/` directory on the DVD-ROM. Run the script as the `root` user. This script is also available as patch 4015045. This patch is available from:

       http://metalink.oracle.com

## 2.4 Set Shell Limits for the oracle User

The following table contains the recommended shell limits for the `oracle` user, depending on the user's default shell.

Bourne or Bash Shell Limit | Korn Shell Limit | C or tcsh Shell Limit | Hard Limit
--- | --- | --- | ---
nofile | nofile | descriptors | 65536
noproc | processes | maxproc | 16384

To increase the shell limits:

1. Add the following lines to `/etc/security/limits.conf` file:

       *        soft   nproc         2047
       *        hard   nproc         16384
       *        soft   nofile        2048
       *        hard   nofile        65536

2. Add the following line to the `/etc/pam.d/login` file, if it does not already exist:

       session    required     /lib/security/pam_limits.so

3. Depending on the `oracle` user's default shell, make the following changes to the default shell start-up file:

   - For the Bourne, Bash, or Korn shell, add the following lines to the `/etc/profile` file:

         if [ $USER = "oracle" ]; then
                 if [ $SHELL = "/bin/ksh" ]; then
                       ulimit -p 16384
                       ulimit -n 65536
                 else
                       ulimit -u 16384 -n 65536
                 fi
         fi

   - For the C or tcsh shell, add the following lines to the `/etc/csh.login` file:

         if ( $USER == "oracle" ) then
                 limit maxproc 16384
                 limit descriptors 65536
         endif

## 2.5 Ports

Many Oracle Application Server components, such as Oracle HTTP Server, use ports. You can have the installer assign default port numbers, or use port numbers that you specify.

- Section 2.5.1, "Checking If a Port Is in Use"

- Section 2.5.2, "Using Default Port Numbers"

- Section 2.5.3, "Using Custom Port Numbers (the "Static Ports" Feature)"

Why the Default Port for Oracle HTTP Server Is Port 7777 and Not Port 80

By default, the installer configures Oracle HTTP Server to use port 7777, not port 80. Port 7777 is the default port because on UNIX, components that use port numbers lower than 1024 require additional steps to be done as the root user before the components can run. Because the installer does not have root access, it has to use a port greater than 1024.

If you want Oracle HTTP Server to use a different port, such as port 80, use the "static ports" feature, which enables you to specify port numbers for components. Although you can change the port number after installation, it is easier to set the port number during installation.

### 2.5.1 Checking If a Port Is in Use

To check if a port is being used, you can run the `netstat` command as follows:

    prompt> netstat -an | grep portnum

### 2.5.2 Using Default Port Numbers

If you want to use the default port numbers for components, you do not have to do anything. See Appendix B, "Default Port Numbers" for a list of the default port numbers and ranges. Make sure that at least one port is available in the port range for each component. If the installer is unable to find a free port in the range, the installation will fail.

### 2.5.3 Using Custom Port Numbers (the "Static Ports" Feature)

To instruct the installer to assign custom port numbers for components:

1. Create a file containing the component names and port numbers. Section 2.5.3.1, "Format of the staticports.ini File" describes the file format. This file is typically called the `staticports.ini` file, but you can name it anything you want.

2. In the installer, on the Specify Port Configuration Options screen, select Manual and enter the full path to the `staticports.ini` file.

   If you do not specify the full path to the file, the installer will not be able to find the file. The installer will then assign default ports for all the components, and it will do this without displaying any warning.

#### 2.5.3.1 Format of the staticports.ini File

The `staticports.ini` file has the following format. Replace port_num with the port number that you want to use for the component.

    Oracle HTTP Server port = port_num
    Oracle HTTP Server SSL port = port_num
    Oracle Notification Server Request port = port_num
    Oracle Notification Server Local port = port_num
    Oracle Notification Server Remote port = port_num

The easiest way to create the file is to use the `staticports.ini` file on the CD-ROM (Disk 1) or DVD-ROM as a template:

1. Copy the `staticports.ini` file from the CD-ROM or DVD-ROM to your hard disk.

   Table 2-6 Location of the staticports.ini File on CD-ROM and DVD-ROM

   Media | Location of staticports.ini File
   --- | ---
   CD-ROM | Disk 1: mount_point`/stage/Response/staticports.ini`
   DVD-ROM | mount_point`/application_server/stage/Response/staticports.ini`

2. Edit the local copy (the file on the hard disk) to include the desired port numbers.

   You do not need to specify port numbers for all components in the `staticports.ini` file. If a component is not listed in the file, the installer uses the default port number for that component.

   The following example sets the Oracle HTTP Server ports and some Oracle Process Manager and Notification Server ports. For components not specified, the installer will assign the default port numbers.

       Oracle HTTP Server port = 2000
       Oracle HTTP Server SSL port = 2001
       Oracle Notification Server Request port = 2002
       Oracle Notification Server Local port = 2003

   When installation is complete, you can run the following commands to see the assigned ports:

       prompt> ORACLE_HOME/opmn/bin/opmnctl startall
       prompt> ORACLE_HOME/opmn/bin/opmnctl status -l

Notes on Choosing Port Numbers: Port numbers cannot be greater than 65535. If you use a port number less than 1024 for a component, you must run the component as the root user. If you use a port number less than 1024 for a component, the installer will not be able to start up the component at the end of installation. You may need to configure the component first before you can start it up. See the appropriate component documentation for details. If you plan to set port numbers for Oracle HTTP Server, be sure you read Section 2.5.3.3, "Ports for Oracle HTTP Server".

The installer verifies that the ports specified in the file are available by checking memory. This means that it can only detect ports that are being used by running processes. It does not look in configuration files to determine which ports an application is using.

If the installer detects that a specified port is not available, it displays an alert. The installer will not assign a port that is not available. To fix this:

1. Edit the `staticports.ini` file to specify a different port, or shut down the application that is using the port.

2. Click Retry. The installer re-reads the `staticports.ini` file and verifies the entries in the file again.

#### 2.5.3.2 Error Conditions that Will Cause the Installer to Use Default Ports Instead of Specified Ports

Check your `staticports.ini` file carefully because a mistake can cause the installer to use default ports without displaying any warning. Here are some things that you should check:

- If you specify the same port for more than one component, the installer will use the specified port for the first component, but for the other components, it will use the components' default ports. The installer does not warn you if you have specified the same port for multiple components.

- If you specify different ports for one component on multiple lines, the installer assigns the default port for the component. The installer does not warn you if you have specified different ports for one component.

- If you specify the same port for one component on multiple lines, the installer assigns the default port for the component. The installer does not warn you if you have specified the same port on multiple lines.

- If you have syntax errors in the `staticports.ini` file (for example, if you omitted the `=` character for a line), the installer ignores the line. For the components specified on such lines, the installer assigns the default ports. The installer does not display a warning for lines with syntax errors.

- If you misspell a component name, the installer assigns the default port for the component. Names of components in the file are case sensitive. The installer does not display a warning for lines with unrecognized names.

- If you specify a non-numeric value for the port number, the installer ignores the line and assigns the default port number for the component. It does this without displaying any warning.

- If you specify a relative path to the staticports.ini file (for example, "`./staticports.ini`" or just "`staticports.ini`"), the installer will not find the file. The installer continues without displaying a warning and it will assign default ports to all components. You must specify a full path to the `staticports.ini` file.

#### 2.5.3.3 Ports for Oracle HTTP Server

Be sure you understand the following when setting ports for this component.

In the `httpd.conf` file for Oracle HTTP Server, the `Port` and the `Listen` directives specify the ports used by Oracle HTTP Server (Figure 2-1). You must set both directives to use the same port number.

To set these ports, use the "Oracle HTTP Server port" and "Oracle HTTP Server Listen port" lines in the `staticports.ini` file. For example:

    Oracle HTTP Server port = 8080
    Oracle HTTP Server Listen port = 8080

To set the SSL version of these ports, use the following lines. As in the non-SSL version, the port numbers must be the same.

    Oracle HTTP Server SSL port = 443
    Oracle HTTP Server Listen (SSL) port = 443

Figure 2-1 Configuring Oracle HTTP Server

Description of "Figure 2-1 Configuring Oracle HTTP Server"

##### 2.5.3.3.1 staticports.ini Example

In this scenario, configure Oracle HTTP Server to use ports 80 and 443. Create a `staticports.ini` file that includes the following lines:

    Oracle HTTP Server port = 80
    Oracle HTTP Server Listen port = 80
    Oracle HTTP Server SSL port = 443
    Oracle HTTP Server Listen (SSL) port = 443

Note: Because you are using ports less than 1024, you have to configure Oracle HTTP Server to run as the root user. You can perform the configuration during installation or after installation. You can choose to perform the configuration after installation, but note that the installer will not be able to start up the components (because they are not yet configured). For details, see the Oracle HTTP Server Administrator's Guide.

## 2.6 Operating System Groups

If you plan to install Oracle Application Server on a computer that does not have Oracle products, you need to create an operating system group to own the "inventory" directory. See Section 2.6.1, "Create a Group for the Inventory Directory".

To create a local operating system group:

Enter the following command to create the `oinstall` group:

    # /usr/sbin/groupadd oinstall

For more information about operating system users and groups, see your operating system documentation or contact your system administrator.

### 2.6.1 Create a Group for the Inventory Directory

If you plan to install Oracle Application Server on a computer that does not have Oracle products, create a group to own the inventory directory. The installer writes its files in the inventory directory to keep track of the Oracle products installed on the computer.

This guide uses the name `oinstall` for this operating system group.

By having a separate group for the inventory directory, you allow different users to install Oracle products on the computer. Users need write permission for the inventory directory. They can achieve this by belonging to the `oinstall` group.

For the first time installation of any Oracle product on a computer, the installer displays a screen where you enter a group name for the inventory directory, and a screen where you enter the location of the inventory directory.

The default name of the inventory directory is `oraInventory`.

If you are unsure if there is already an inventory directory on the computer, look in the `/etc/oraInst.loc` file. This file lists the location of the inventory directory and the group who owns it. If the file does not exist, the computer does not have Oracle products installed on it.

## 2.7 Operating System User

Create an operating system user to install and upgrade Oracle products. This guide refers to this user as the `oracle` user. The `oracle` user running the installer must have write permission for these directories:

- the Oracle home directory, which contains files for the product you are installing

- the inventory directory, which is used by the installer for all Oracle products

If the computer contains other Oracle products, you might already have a user for this purpose. Look in the `/etc/oraInst.loc` file. This file lists the location of the inventory directory and the group who owns it. If the file does not exist, the computer does not have Oracle products installed on it.

If you do not already have a user for installing Oracle products, create a user with the following properties:

Table 2-7 Properties of the Operating System User Who Runs the Installer

Item | Description
--- | ---
Login name | You can use any name for the user. This guide refers to the user as the `oracle` user.
Group identifier | The primary group of the `oracle` user must have write permission for the `oraInventory` directory. See Section 2.6.1, "Create a Group for the Inventory Directory" for more information about this group. You can use any name for the group. This guide uses the name `oinstall`.
Home directory | The home directory for the `oracle` user can be consistent with the home directories of other users.
Login shell | The default login shell can be the C, Bourne, or Korn shell.

Note: Use the `oracle` user only for installing and running Oracle products. Do not use root as the `oracle` user.

To create a local operating system user:

1. To create the `oracle` user, enter a command similar to the following:

       # /usr/sbin/useradd -g oinstall -G dba[,oper] oracle

   In this command:

   - The `-g` option specifies the primary group, which must be the Oracle Inventory group, for example `oinstall`

   - The `-G` option specifies the secondary groups, which must include the OSDBA group and if required, the OSOPER group, for example `dba` or `dba,oper`

2. Set the password of the `oracle` user:

       # passwd oracle

To check which groups an operating system user belongs to, run the `groups` command with the name of the user. For example:

    prompt> groups oracle

For more information about operating system users and groups, see your operating system documentation or contact your system administrator.

## 2.8 Environment Variables

The operating system user who will be installing Oracle Application Server needs to set (or unset) the following environment variables.

Table 2-8 summarizes whether you set or unset an environment variable.

Table 2-8 Environment Variable Summary

Environment variable | Set or Unset
--- | ---
ORACLE_HOME and ORACLE_SID | Must not be set.
PATH, CLASSPATH, and LD_LIBRARY_PATH | Must not contain references to directories in any Oracle home directories
DISPLAY | Set it to the monitor where you want to the installer window to appear.
TMP and TMPDIR | Optional. If unset, defaults to `/tmp`.
TNS_ADMIN | Must not be set.
ORA_NLS | Must not be set.
LD_BIND_NOW | Must not be set.

### 2.8.1 Environment Variable Tips

Here are some tips when working with environment variables:

- If you set environment variables in the `.profile` file, they might not be read. To ensure environment variables are set to the correct values, check their values in the shell where you will be running the installer.

- To check the value of environment variables, use the `env` command. This displays all the currently defined environment variables and their values.

      % env

- If you use the `su` command to switch users (for example, switching from the root user to the `oracle` user), check the environment variables when you are the new user because the environment variables might not be passed to the new user. This can happen even if you run `su` with the `-` parameter (`su -` `user`).

      # /* root user */
      # su - oracle
      % env

### 2.8.2 ORACLE_HOME and ORACLE_SID

These environment variables must not be set.

### 2.8.3 PATH, CLASSPATH, and LD_LIBRARY_PATH

Edit your PATH, CLASSPATH, and LD_LIBRARY_PATH environment variables so that they do not reference any Oracle home directories.

### 2.8.4 DISPLAY

Set the DISPLAY environment variable to point to the X server that will display the installer. The format of the DISPLAY environment variable is:

    hostname:display_number.screen_number

Example (C shell):

    % setenv DISPLAY test.mydomain.com:0.0

Example (Bourne or Korn shell):

    $ DISPLAY=test.mydomain.com:0.0; export DISPLAY

You can test the display by running the xclock program:

    $ xclock &

Oracle Application Server requires a running X server during installation only. The frame buffer X server installed with your operating system requires that you remain logged in and have the frame buffer running during installation. If you do not wish to do this, then you must use a virtual frame buffer, such as X Virtual Frame Buffer (XVFB) or Virtual Network Computing (VNC).

Visit Oracle Technology Network (`http://www.oracle.com/technology`) for information about obtaining and installing XVFB or other virtual frame buffer solutions. Search OTN for "frame buffer".

### 2.8.5 TNS_ADMIN

This section describes two requirements:

- The TNS_ADMIN environment variable must not be set. If set, it can cause errors during installation.

- The `/etc` and the `/var/opt/oracle` directories must not contain a `tnsnames.ora` file.

These requirements are necessary to prevent conflicts between the Net configuration files for different Oracle products.

If you need to set TNS_ADMIN or if you have the `tnsnames.ora` file in `/etc` or `/var/opt/oracle`, do the following steps before installing Oracle Application Server.

1. If you have the `tnsnames.ora` file in `/etc` or `/var/opt/oracle`, move the file from these directories to a different directory. Alternatively, you can rename the file.

2. Make sure the TNS_ADMIN environment variable is not set.

   Example (C shell):

       % unsetenv TNS_ADMIN

   Example (Bourne or Korn shell):

       $ unset TNS_ADMIN

After installation, you can merge the contents of the newly created `tnsnames.ora` file with your existing `tnsnames.ora` file.

### 2.8.6 TMP and TMPDIR

The installer uses a temporary directory for swap space. The installer checks for the TMP and TMPDIR environment variables to locate the temporary directory. If this environment variable does not exist, the installer uses the `/tmp` directory.

If you want the installer to use a temporary directory other than `/tmp`, set the TMP and TMPDIR environment variables to the full path of an alternate directory. The `oracle` user must have right permission for this directory and the directory must meet the requirements listed in Table 2-2.

Example (C shell):

    % setenv TMP /tmp2
    % setenv TMPDIR /tmp2

Example (Bourne or Korn shell):

    $ TMP=/tmp2; export TMP
    $ TMPDIR=/tmp2; export TMPDIR

If you do not set this environment variable, and the default directory does not have enough space, then the installer displays an error message that says the environment variable is not set. You can either set the environment variable to point to a different directory or free up enough space in the default directory. In either case, you have to restart the installation.

### 2.8.7 ORA_NLS

To make sure that the Oracle Application Server installation completes successfully, unset this environment variable.

Example:

    $ unset ORA_NLS

### 2.8.8 LD_BIND_NOW

To make sure that the Oracle Application Server installation completes successfully, unset this environment variable.

Example:

    $ unset LD_BIND_NOW

## 2.9 Network Topics

Typically, the computer on which you want to install Oracle Application Server is connected to the network, has local storage to contain the Oracle Application Server installation, has a display monitor, and has a CD-ROM or DVD-ROM drive.

This section describes how to install Oracle Application Server on computers that do not meet the typical scenario. It covers the following cases:

- Section 2.9.1, "Installing on a DHCP Host"

- Section 2.9.2, "Installing on Multihomed (Multi-IP) Computers"

- Section 2.9.3, "Copying CD-ROMs or DVD-ROM to Hard Drive, and Installing from the Hard Drive"

- Section 2.9.4, "Installing from a Remote CD-ROM or DVD-ROM Drive"

- Section 2.9.5, "Installing on Remote Computers"

### 2.9.1 Installing on a DHCP Host

If you are installing Oracle Application Server in a DHCP network you must use a loopback configuration. To access the Oracle Application Server, you need to use a local browser. Perform the following steps to install Oracle Application Server in a DHCP network:

1. Find the IP address allocated from the DHCP server by running the following command:

       $ /sbin/ifconfig -a

   The IP address is associated with the interface configured to use DHCP.

2. Configure the host to resolve hostname to loopback IP address:

   1. Configure the host to resolve hostname to loopback IP address, by modifying the `/etc/hosts` file to contain the following entries:

          127.0.0.1 hostname.domainname hostname
          127.0.0.1 localhost.localdomain localhost

   2. Check that the hostname resolves to the loopback IP address by entering the following command:

          $ /bin/ping hostname.domainname

3. Complete the Oracle Application Server installation as described in this guide using the hostname used in step 2.

### 2.9.2 Installing on Multihomed (Multi-IP) Computers

You can install Oracle Application Server on a multihomed computer. A multihomed computer is associated with multiple IP addresses. This is typically achieved by having multiple network cards on the computer. Each IP address is associated with a hostname; additionally, you can set up aliases for the hostname. By default, Oracle Universal Installer uses the `ORACLE_HOSTNAME` environment variable setting to find the hostname. If `ORACLE_HOSTNAME` is not set and you are installing on a computer that has multiple network cards, Oracle Universal Installer determines the hostname by using the first name in the `/etc/hosts` file.

Clients must be able to access the computer using this hostname (or using aliases for this hostname). To check, ping the hostname from the client computers using the short name (hostname only) and the full name (hostname and domain name). Both must work.

### 2.9.3 Copying CD-ROMs or DVD-ROM to Hard Drive, and Installing from the Hard Drive

Instead of installing from the Oracle Application Server CD-ROMs or DVD-ROM, you can copy the contents of the CD-ROMs or DVD-ROM to a hard drive and install from there. This might be easier if you plan to install many instances of Oracle Application Server on your network, or if the computers where you want to install Oracle Application Server do not have CD-ROM or DVD-ROM drives.

(You can install from remote CD-ROM or DVD-ROM drives; see Section 2.9.4, "Installing from a Remote CD-ROM or DVD-ROM Drive".)

When you install from the hard drive, the installer does not prompt you to swap CD-ROMs. It can find all the files if they are in the proper locations (see Figure 2-2).

Space Requirement

Ensure that the hard drive contains enough space to hold the contents of the CD-ROMs or the `application_server` directory on the DVD-ROM. Each CD-ROM contains approximately 650 MB. This means that if you are copying three CD-ROMs, you need approximately 1.9 GB of disk space.

On the DVD-ROM, the `application_server` directory is approximately 1.6 GB.

This space is in addition to the space required for installing Oracle Application Server (listed in Table 2-2).

To Copy the CD-ROMs:

1. Create a directory structure on your hard drive as shown in Figure 2-2.

   You need to create a parent directory (called `OracleAS_10g` in the example, but you can name it anything you like), and, under the parent directory, create subdirectories called `Disk1`, `Disk2`, and so on. The names of the subdirectories must be `Disk` `N`, where `N` is the CD-ROM number.

   Figure 2-2 Directory Structure for Copying CD-ROMs to Disk

   Description of "Figure 2-2 Directory Structure for Copying CD-ROMs to Disk"

2. Copy the contents of each CD-ROM into the corresponding directory.

       prompt> cp -pr /cdrom_mount_point/10.1.3disk1/* /path/to/hard/drive/Disk1/
       prompt> cp -pr /cdrom_mount_point/10.1.3disk2/* /path/to/hard/drive/Disk2/
       ... Repeat for each CD-ROM.

To run the installer from the copied files, invoke the `runInstaller` executable from the `Disk1` directory. Run it from the computer that will be running Oracle Application Server.

    prompt> /path/to/hard/drive/Disk1/runInstaller

To Copy the application_server Directory from the DVD-ROM

1. (optional) Create a directory to contain the `application_server` directory.

2. Copy the `application_server` directory from the DVD-ROM to your hard disk.

       prompt> cp -pr /dvd_mount_point/application_server /path/to/hard/drive

To run the installer from the copied files, invoke the `runInstaller` executable from the computer that will be running Oracle Application Server:

    prompt> /path/to/hard/drive/application_server/runInstaller

### 2.9.4 Installing from a Remote CD-ROM or DVD-ROM Drive

You can run the installer on a remote computer ("remote_computer"), but have the installer screens display on your local computer ("local_computer"). The installer will install Oracle Application Server on the remote computer.

1. Allow remote_computer to display on local_computer. You need to run this command on the local computer's console.

       local_computer> xhost +remote_computer

   If you do not run `xhost`, you might get an Xlib error similar to "Failed to connect to server", "Connection refused by server," or "Can't open display" when starting the installer.

2. On local_computer, perform a remote login (using `telnet` or `rlogin`) to remote_computer. Log in as the `oracle` user, as described in Section 2.7, "Operating System User". Ensure that the user has set the environment variables correctly, as described in Section 2.8, "Environment Variables".

       local_computer> rlogin -l oracle remote_computer.mydomain.com
       - OR -
       local_computer> telnet remote_computer.mydomain.com

3. Set the DISPLAY environment variable on remote_computer to point to local_computer.

   Example (C shell):

       remote_computer> setenv DISPLAY local_computer.mydomain.com:0.0

   Example (Bourne or Korn shell):

       remote_computer> DISPLAY=local_computer.mydomain.com:0.0; export DISPLAY

4. Run the installer. See Section 3.11, "Starting theOracle Universal Installer".

Note: You can use a PC X emulator to run the installer if it supports a PseudoColor color model or PseudoColor visual. Set the PC X emulator to use a PseudoColor visual, and then start the installer. Refer to the X emulator documentation for instructions on how to change the color model or visual settings.

### 2.9.5 Installing on Remote Computers

You can run the installer on a remote computer ("remote_computer"), but have the installer screens display on your local computer ("local_computer"). The installer will install Oracle Application Server on the remote computer.

1. Allow remote_computer to display on local_computer. You need to run this command on the local computer's console.

       local_computer> xhost +remote_computer

   If you do not run `xhost`, you might get an Xlib error similar to "Failed to connect to server", "Connection refused by server," or "Can't open display" when starting the installer.

2. On local_computer, perform a remote login (using `telnet` or `rlogin`) to remote_computer. Log in as the `oracle` user, as described in Section 2.7, "Operating System User". Ensure that the user has set the environment variables correctly, as described in Section 2.8, "Environment Variables".

       local_computer> rlogin -l oracle remote_computer.mydomain.com
       - OR -
       local_computer> telnet remote_computer.mydomain.com

3. Set the DISPLAY environment variable on remote_computer to point to local_computer.

   Example (C shell):

       remote_computer> setenv DISPLAY local_computer.mydomain.com:0.0

   Example (Bourne or Korn shell):

       remote_computer> DISPLAY=local_computer.mydomain.com:0.0; export DISPLAY

4. Run the installer. See Section 3.11, "Starting theOracle Universal Installer".

Note: You can use a PC X emulator to run the installer if it supports a PseudoColor color model or PseudoColor visual. Set the PC X emulator to use a PseudoColor visual, and then start the installer. Refer to the X emulator documentation for instructions on how to change the color model or visual settings.

### 2.9.6 Installing on NFS-Mounted Storage

To run Oracle Application Server on NFS systems, you have to use a certified NFS-mounted storage system.

Currently Oracle Application Server is certified to run on these NFS systems:

- Network Appliance (NetApp) filers

The NetApp system should be exported to at least the remote install user and remote root user. You can do this using `exportfs` command:

    prompt> exportfs -i /vol/vol1

Before installing, verify that the NFS mount setuid permission is set to `suid`. The `nosuid` option will cause the install to fail.

To check the latest certification list for any updates, visit Oracle Technology Network (`http://www.oracle.com/technology`).

### 2.9.7 Running Multiple Instances from One Installation

Oracle Application Server components are intended to be run only on the computer where they are installed. You cannot run the components on remote computers, even though the computers can access the files through NFS.

Figure 2-3 Run Oracle Application Server Only on the Computer Where It Is Installed

Description of "Figure 2-3 Run Oracle Application Server Only on the Computer Where It Is Installed"

### 2.9.8 Support for NIS and NIS+

You can install and run Oracle Application Server in NIS and NIS+ environments.

## 2.10 Prerequisite Checks Performed by the Installer

Table 2-9 lists the checks performed by the installer:

Table 2-9 Prerequisite Checks Performed by the Installer

Item | Description
--- | ---
Processor | See Table 2-2 for recommended values.
Operating system version | See Section 2.3, "Software Requirements" for supported versions.
Operating system patches | See Section 2.3, "Software Requirements" for a list of required patches.
Software packages | See Section 2.3, "Software Requirements" for a list of required packages.
Memory | See Table 2-2 for recommended values.
Swap space | See Table 2-2 for recommended values.
TMP space | See Table 2-2 for recommended values.
Instance name | The installer checks that the computer on which you are installing Oracle Application Server does not already have an instance of the same name.
Oracle home directory name | The installer checks that the Oracle home directory name does not contain any spaces.
Path to Oracle home directory | The installer checks that the path to the Oracle home directory is not longer than 127 characters.
Oracle home directory contents | The installer checks that the Oracle home directory does not contain any files that might interfere with the installation.
Oracle home directory | You should install Oracle Application Server in a new directory. Here are some examples of installations that are not allowed: Oracle Application Server into an 8.0, 8i, 9.0.1, 9.2, or 10g database Oracle home Oracle Application Server into an Oracle Management Service Oracle home Oracle Application Server into an Oracle Collaboration Suite Oracle home Oracle Application Server into an Oracle HTTP Server standalone Oracle home Oracle Application Server into an OracleAS Web Cache standalone Oracle home Oracle Application Server into an Oracle9i Developer Suite 9.0.2 or Oracle Developer Suite 10g Release 2 (10.1.2) Oracle home Oracle Application Server into an Oracle Containers for J2EE standalone Oracle home Oracle Application Server into an Oracle9iAS 1.0.2.2 Oracle home Oracle Application Server into an infrastructure 9.0.2, 9.0.4, or 10g Release 2 (10.1.2) Oracle home Oracle Application Server into an Oracle9iAS 9.0.2, 9.0.3, 9.0.4, or 10g Release 2 (10.1.2) middle tier Oracle home Oracle Application Server into an Oracle home installed from the Oracle Business Intelligence 10g (10.1.2.0.2) CD-ROM.
Static port conflicts | The installer checks the ports listed in the `staticports.ini` file, if specified. See Section 2.5, "Ports".
Monitor | The installer checks that the monitor is configured to display at least 256 colors.
Display permission | The installer checks that the user has permissions to display on the monitor specified by the DISPLAY environment variable.
DISPLAY environment variable | The installer checks that the DISPLAY environment variable is set.
TNS_ADMIN environment variable | The TNS_ADMIN environment variable must not be set. There must not be a `tnsnames.ora` file in the `/etc` or `/var/opt/oracle` directories.
Cluster file system | The installer checks that you are not installing Oracle Application Server in a cluster file system (CFS).
glibc version check on Linux | The installer runs this check only if you are installing on Linux. The installer makes sure that the glibc version is glibc-2.3.2-95.27 or higher on Red Hat Enterprise Linux AS/ES 3.0, glibc-2.3.4-2.9 or higher on Red Hat Enterprise Linux AS/ES 4.0, and glibc-2.3.3-98.28 or higher on SUSE Linux Enterprise Server 9.
Packages check on Linux | The installer runs this check only if you are installing on Linux.The installer makes sure that the mandatory packages are installed. For example, it checks the gcc, sysstat and openmotif packages as specified in Table 2-3 for Red Hat Enterprise Linux AS/ES 3.0 , Table 2-4 for Red Hat Enterprise Linux AS/ES 4.0, and Table 2-5 for SUSE Linux Enterprise Server 9.