2 Oracle Database Preinstallation Requirements

2.1.1 Completing a Minimal Linux Installation

To complete a minimal Linux installation, select one of the minimal installation options (either a custom installation where you select the Minimal option from Package Group Selection, or where you deselect all packages except for the Base pack). This installation lacks many RPMs required for installation, so you must use an RPM package for your Oracle Linux release to install the required packages. The package you use depends on your Linux release, and your support status with Unbreakable Linux Network (ULN).

Refer to the following URL for documentation regarding installation of a reduced set of packages:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=728346.1

SSH is required for an Oracle Grid Infrastructure installation. OpenSSH should be included in the Linux distribution minimal installation. To confirm that SSH packages are installed, enter the following command:

# rpm -qa |grep ssh

If you do not see a list of SSH packages, then install those packages for your Linux distribution.

2.1.2 Completing a Default Linux Installation

If you do not install the Oracle Pre-Install RPM, then Oracle recommends that you install your Linux operating system with the default software packages (RPMs). This installation includes most of the required packages and helps you limit manual verification of package dependencies. Oracle recommends that you do not customize the RPMs during installation.

For information about a default installation, log on to My Oracle Support:

https://support.oracle.com

Search for "default rpms linux installation," and look for your Linux distribution. For example:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=ID 401167.1

After installation, review system requirements for your distribution to ensure that you have all required kernel packages installed, and complete all other configuration tasks required for your distribution and system configuration.

2.1.3 About Oracle Linux and the Unbreakable Enterprise Kernel

Oracle's Unbreakable Enterprise Kernel delivers the latest innovations from upstream development to customers who run Red Hat Enterprise Linux (RHEL) 5 or Oracle Linux 5 in the data center. The Unbreakable Enterprise Kernel is included and enabled by default starting with Oracle Linux 5 Update 6.

The Unbreakable Enterprise Kernel is based on a recent stable mainline development Linux kernel, and also includes optimizations developed in collaboration with Oracle Database, Oracle middleware, and Oracle hardware engineering teams to ensure stability and optimal performance for the most demanding enterprise workloads.

Oracle highly recommends deploying the Oracle Unbreakable Enterprise Kernel in your Linux environment, especially if you run enterprise applications. However, using Oracle Unbreakable Enterprise Kernel is optional. If you require strict RHEL kernel compatibility, then Oracle Linux also includes a kernel compatible with the RHEL Linux kernel, compiled directly from the RHEL source code.

You can obtain more information about the Oracle Unbreakable Enterprise Kernel for Linux at the following URL:

http://www.oracle.com/us/technologies/linux

The Oracle Unbreakable Enterprise Kernel for Linux is the standard kernel used with Oracle products. The build and QA systems for Oracle Database and other Oracle products use the Oracle Unbreakable Enterprise Kernel for Linux exclusively. The Oracle Unbreakable Enterprise Kernel for Linux is also the kernel used in Oracle Exadata and Oracle Exalogic systems. Oracle Unbreakable Enterprise Kernel for Linux is used in all benchmark tests on Linux in which Oracle participates, as well as in the Oracle RDBMS preinstall RPM program for x86-64.

Ksplice, which is part of Oracle Linux, updates the Linux operating system (OS) kernel, while it is running, without requiring restarts or any interruption. Ksplice is available only with Oracle Linux.

2.1.4 About the Oracle RDBMS Pre-Install and Oracle Validated RPMs

If your Linux distribution is Oracle Linux, or Red Hat Enterprise Linux, and you are an Oracle Linux customer, then you can complete most preinstallation configuration tasks by using the Oracle RDBMS Server Pre-Install RPM or Oracle Validated RPM for your release, which is available from the Oracle Linux Network, or available on the Oracle Linux DVDs. Using the Oracle Pre-Install RPM is not required, but Oracle recommends you use it to save time in setting up your cluster servers.

When it is installed, the Oracle Pre-Install RPM or Oracle Validated RPM does the following:

• Automatically downloads and installs any additional RPM packages needed for installing Oracle Grid Infrastructure and Oracle Database, and resolves any dependencies

• Creates an oracle user, and creates the oraInventory (oinstall) and OSDBA (dba) groups for that user

• As needed, sets sysctl.conf settings, system startup parameters, and driver parameters to values based on recommendations from the Oracle RDBMS Pre-Install program

• Sets hard and soft resource limits

• Sets other recommended parameters, depending on your kernel version

To become an Oracle Linux Network customer, contact your sales representative, or purchase a license from the Oracle Linux store:

https://shop.oracle.com/product/oraclelinux

To register your server on the Unbreakable Linux Network, or to find out more information, see the following URL:

https://linux.oracle.com

If you are using Oracle Linux 5.2 and higher, then the Oracle Pre-Install RPM is included on the install media.

You can obtain Linux kernels from the Oracle Linux public Yum repository. The public Yum repository for Oracle Linux 4, Oracle Linux 5 and Oracle Linux 6 is available at the following URL:

http://public-yum.oracle.com/

To become an Unbreakable Linux Network customer, contact your sales representative, or purchase a license from the Unbreakable Linux store:

https://shop.oracle.com/product/oraclelinux

To register your server on the Unbreakable Linux Network, or to find out more information, refer to the following URL:

https://linux.oracle.com

If you are using Oracle Linux 4.7 and higher, or Oracle Linux 5.2 and higher, then the Oracle RDBSM Pre-Install or Oracle Validated RPM is included on the install media.

2.1.5 Installing the Oracle Pre-Install or Oracle Validated RPM with ULN Support

Use the following procedure to subscribe to Unbreakable Linux Network (ULN) Oracle Linux channels, and to add the Oracle Linux channel that distributes the Oracle RDBMS Server Pre-Install RPM or Oracle Validated RPM for your release:

1. Register your server with Unbreakable Linux Network (ULN). By default, you are registered for the Oracle Linux Latest channel for your operating system and hardware.

2. Log in to Unbreakable Linux Network:

   https://linux.oracle.com

3. Click the Systems tab, and in the System Profiles list, select a registered server. The System Details window opens and displays the subscriptions for the server.

4. Click Manage Subscriptions. The System Summary window opens.

5. From the Available Channels list, select the Linux installation media copy and update patch channels corresponding to your Oracle Linux distribution. For example, if your distribution is Oracle Linux 5 Update 6 for x86_64, then select the following:

   • Oracle Linux 5 Update 6 installation media copy (x86_64)

   • Oracle Linux 5 Update 6 Patch (x86_64)

6. Click Subscribe.

7. Start a terminal session and enter the following command as root, depending on your platform.

   Oracle Linux 6:

   # yum install oracle-rdbms-server-12cR1-preinstall
   

   Oracle Linux 5 or Oracle Linux 4:

   # yum install oracle-validated
   

   You should see output indicating that you have subscribed to the Oracle Linux channel, and that packages are being installed. For example:

   el5_u6_i386_base
   el5_u6_x86_64_patch
   

   Oracle Linux automatically creates a standard (not role-allocated) Oracle installation owner and groups, and sets up other kernel configuration settings as required for Oracle installations.

8. Repeat steps 1 through 8 on all other servers in your cluster.

   Note:

   Check the RPM log file to review the system configuration changes. For example:

   Oracle Linux 6:

   /var/log/oracle-rdbms-server-12cR1-preinstall/results/orakernel.log
   

   Oracle Linux 5 and Oracle Linux 4:

   /var/log/oracle-validated/results/orakernel.log
   

2.1.6 Installing the Oracle RDBMS Pre-Install RPM from DVD Disks or Images

Use the following procedure to install the Oracle RDBMS Pre-Install RPM or Oracle Validated Configuration RPM from the Oracle Linux distribution:

1. Get Oracle Linux disks either by ordering the Oracle Linux media pack from Oracle Store, or downloading disk images from the Oracle Software Delivery Cloud portal for Oracle Linux and Oracle Virtual Machine (Oracle VM).

   Oracle Store:

   https://shop.oracle.com/store/enterpriselinux
   

   Oracle Software Delivery Cloud:

   https://edelivery.oracle.com/linux
   

2. Start the Oracle Linux installation.

3. At the first software selection screen, which lists task-specific software options, there is an option at the bottom of the screen to customize now or customize later. Select Customize now, and click Next.

4. On the Customize selection page, select Base System on the list on the left side of the screen, and then select System Tools on the right side of the screen. Then, click Optional Packages.

5. The Packages in System Tools window opens. Select the Oracle RDBMS Pre-Install RPM package box from the package list, and click Next.

6. Complete the other screens to finish the Oracle Linux installation.

   Oracle Linux automatically creates a standard (not role-allocated) Oracle installation owner and groups, and sets up other kernel configuration settings as required for Oracle installations.

2.1.7 Using Ksplice to Perform a Zero Downtime Update

Ksplice Uptrack updates provide Linux security and bug fix updates, repackaged in a form that allows these updates to be applied without restarting the kernel.

To use Ksplice Uptrack:

1. Obtain or verify your Oracle Linux premium support subscription from Unbreakable Linux Network:

   https://linux.oracle.com

2. Log in as root.

3. Ensure that you have access to the Internet on the server where you want to use Ksplice. For example, if you are using a proxy server, then set the proxy server and port values in the shell with commands similar to the following:

   # export http_proxy=http://proxy.example.com:port
   # export https_proxy=http://proxy.example.com:port
   

4. Download the Ksplice Uptrack repository RPM package:

   https://www.ksplice.com/yum/uptrack/ol/ksplice-uptrack-release.noarch.rpm

5. Run the following commands:

   rpm -i ksplice-uptrack-release.noarch.rpm
   yum -y install uptrack
   

6. Open /etc/uptrack/uptrack.conf with a text editor, enter your premium support access key, and save the file. You must use the same access key for all of your systems.

7. Run the following command to carry out a zero downtime update of your kernel:

   uptrack-upgrade -y
   

   See Also:

   • The Oracle Ksplice Uptrack website for more information:

     http://www.ksplice.com

   • Oracle Ksplice for Oracle Linux:

     http://oss.oracle.com/ksplice/docs/ksplice-quickstart.pdf

2.3.1 Memory Requirements

The following are the memory requirements for installing Oracle Database 11g Release 2 (11.2):

Minimum: 1 GB of RAM

Recommended: 2 GB of RAM or more

• To determine the RAM size, enter the following command:

  # grep MemTotal /proc/meminfo
  

  If the size of the RAM is less than the required size, then you must install more memory before continuing.

• The following table describes the relationship between the installed RAM and the configured swap space recommendation:

  Note:

  On Linux, the HugePages feature allocates non-swappable memory for large page tables using memory-mapped files. If you enable HugePages, then you should deduct the memory allocated to HugePages from the available RAM before calculating swap space.

  RAM	Swap Space
  Between 1 GB and 2 GB	1.5 times the size of the RAM
  Between 2 GB and 16 GB	Equal to the size of the RAM
  More than 16 GB	16 GB

  
  

If the size of the RAM is less than the required size, then you must install more memory before continuing.

To determine the size of the configured swap space, enter the following command:

# grep SwapTotal /proc/meminfo

If necessary, see the operating system documentation for information about how to configure additional swap space.

To determine the available RAM and swap space, enter the following command:

# free

Automatic Memory Management

Starting with Oracle Database 11g, the Automatic Memory Management feature requires more shared memory (/dev/shm)and file descriptors. The size of the shared memory must be at least the greater of the MEMORY_MAX_TARGET and MEMORY_TARGET parameters for each Oracle instance on the computer. If the MEMORY_MAX_TARGET parameter or the MEMORY_TARGET parameter is set to a nonzero value, and an incorrect size is assigned to the shared memory, it results in an ORA-00845 error at startup. On Linux systems, if the operating system /dev/shm mount size is too small for the Oracle system global area (SGA) and program global area (PGA), it results in an ORA-00845 error.

The number of file descriptors for each Oracle instance must be at least 512*PROCESSES. The limit of descriptors for each process must be at least 512. If file descriptors are not sized correctly, you see an ORA-27123 error from various Oracle processes and potentially Linux Error EMFILE (Too many open files)in non-Oracle processes.

To determine the amount of shared memory available, enter the following command:

# df -h /dev/shm/

On the Initialization Parameters page, note the Memory Size (SGA and PGA), which sets the initialization parameter MEMORY_TARGET or MEMORY_MAX_TARGET. The initialization parameters cannot be greater than the shared memory file system on the operating system. For example, if the shared memory file system allocation on your system is 1 GB, but you set Memory Size (MEMORY_TARGET) to 2 GB, then the following error messages are displayed during database startup:

ORA-00845: MEMORY_TARGET not supported on this system
ORA-01078: Failure in processing system parameters

In addition, if you click All Initialization Parameters and the global database name is longer than eight characters, then the database name value (in the DB_NAME parameter) is truncated to the first eight characters, and the DB_UNIQUE_NAME parameter value is set to the global name.

The workaround, if you encounter the ORA-00845 error, is to increase the /dev/shm mountpoint size.

For example:

# mount -t tmpfs shmfs -o size=7g /dev/shm

To make this change persistent across system restarts, add an entry in /etc/fstab similar to the following:

shmfs /dev/shm tmpfs size=7g 0

2.3.2 System Architecture

To determine if the system architecture can run the software, enter the following command:

# uname -m

Verify that the processor architecture matches the Oracle software release to install. If you do not see the expected output, then you cannot install the software on this system.

2.3.3 Disk Space Requirements

The following are the disk space requirements for installing Oracle Database 11g Release 2 (11.2):

• 1 GB of space in the /tmp directory

  To determine the amount of space available in the /tmp directory, enter the following command:

  # df -h /tmp
  

  If the free space available in the /tmp directory is less than what is required, then complete one of the following steps:

  • Delete unnecessary files from the /tmp directory to meet the disk space requirement.

  • Set the TMP and TMPDIR environment variables when setting the oracle user's environment.

    See Also:

    "Configuring the oracle User's Environment" for more information about setting TMP and TMPDIR

  • Extend the file system that contains the /tmp directory. If necessary, contact the system administrator for information about extending file systems.

• The following tables describe the disk space requirements for software files and data files for each installation type on Linux x86:

  Installation Type	Requirement for Software Files (GB)
  Enterprise Edition	3.95
  Standard Edition	3.88

  
  

  Installation Type	Disk Space for Data Files (GB)
  Enterprise Edition	1.7
  Standard Edition	1.5

  
  

• The following tables describe the disk space requirements for software files and data files for each installation type on Linux x86-64:

  Installation Type	Requirement for Software Files (GB)
  Enterprise Edition	4.35
  Standard Edition	4.22

  
  

  Installation Type	Disk Space for Data Files (GB)
  Enterprise Edition	1.7
  Standard Edition	1.5

  
  

• The following tables describe the disk space requirements for software files and data files for each installation type on IBM: Linux on System z:

  Installation Type	Requirement for Software Files (GB)
  Enterprise Edition	4.9
  Standard Edition	4.5

  
  

  Installation Type	Disk Space for Data Files (GB)
  Enterprise Edition	2.0
  Standard Edition	1.5

  
  

To determine the amount of free disk space on the system, enter the following command:

# df -h

Additional disk space, either on a file system or on an Oracle ASM disk group is required for the fast recovery area if you configure automated backups.

2.3.4 Display Requirements

The minimum resolution for Oracle Database 11g Release 2 (11.2) is 1024 x 768 or higher.

2.4.1 Operating System Requirements

The following operating system versions (or later) are required for Oracle Database 11g Release 2 (11.2):

• On Linux x86

  • Asianux Server 3 SP2

  • Oracle Linux 4 Update 7

  • Oracle Linux 5 Update 2

  • Oracle Linux 6

  • Red Hat Enterprise Linux 4 Update 7

  • Red Hat Enterprise Linux 5 Update 2

  • Red Hat Enterprise Linux 6

  • SUSE Linux Enterprise Server 10 SP2

  • SUSE Linux Enterprise Server 11

• On Linux x86-64

  • Asianux Server 3 SP2

  • Oracle Linux 4 Update 7

  • Oracle Linux 5 Update 2 (with Red Hat Compatible Kernel)

  • Oracle Linux 5 Update 5

  • Oracle Linux 6

  • Oracle Linux 6 (with Red Hat Compatible Kernel)

  • Red Hat Enterprise Linux 4 Update 7

  • Red Hat Enterprise Linux 5 Update 2

  • Red Hat Enterprise Linux 5 Update 5 (with the Oracle Unbreakable Enterprise Kernel for Linux)

  • Red Hat Enterprise Linux 6

  • Red Hat Enterprise Linux 6 (with the Oracle Unbreakable Enterprise Kernel for Linux)

  • SUSE Linux Enterprise Server 10 SP2

  • SUSE Linux Enterprise Server 11

• On IBM: Linux on System z

  • Red Hat Enterprise Linux 4 Update 8

  • Red Hat Enterprise Linux 5 Update 4

  • SUSE Linux Enterprise Server 10 SP3

  • SUSE Linux Enterprise Server 11 SP1

Starting with Oracle Database 11g Release 2 (11.2), the Security Enhanced Linux (SELinux) feature is supported for Oracle Linux 4, Oracle Linux 5, Oracle Linux 6, Red Hat Enterprise Linux 4, Red Hat Enterprise Linux 5, and Red Hat Enterprise Linux 6.

To determine the distribution and version of Linux installed, enter the following command:

# cat /proc/version

You can also enter the following command on some distributions of Linux:

# lsb_release -id

2.4.2 Kernel Requirements

The following are the kernel requirements for Oracle Database 11g Release 2 (11.2):

For Linux x86 

• On Oracle Linux 4 and Red Hat Enterprise Linux 4

  2.6.9 or later

• On Asianux Server 3, Oracle Linux 5, and Red Hat Enterprise Linux 5

  2.6.18 or later

• On Oracle Linux 6

  2.6.32.100 or later

• On Red Hat Enterprise Linux 6

  2.6.32-71 or later

• On SUSE Linux Enterprise Server 10

  2.6.16.21 or later

• On SUSE Linux Enterprise Server 11:

  2.6.27.19 or later

For Linux x86-64 

• On Oracle Linux 4 and Red Hat Enterprise Linux 4

  2.6.9 or later

• On Oracle Linux 5 Update 5

  2.6.32-100.0.19 or later

• On Oracle Linux 5 Update 2

  2.6.18 or later (with Red Hat Compatible Kernel)

• On Oracle Linux 6

  2.6.32-100.28.5.el6.x86_64 or later

• On Oracle Linux 6

  2.6.32-71.el6.x86_64 or later (with Red Hat Compatible Kernel)

• On Red Hat Enterprise Linux 5 Update 5 with the Oracle Unbreakable Enterprise Kernel for Linux

  2.6.32 or later

• On Red Hat Enterprise Linux 6 with the Oracle Unbreakable Enterprise Kernel for Linux

  2.6.32-100.28.5.el6.x86_64 or later

• On Red Hat Enterprise Linux 6

  2.6.32-71.el6.x86_64 or later

• On Asianux Server 3, Oracle Linux 5 Update 2, and Red Hat Enterprise Linux 5 Update 2

  2.6.18 or later

• On SUSE Linux Enterprise Server 10

  2.6.16.21 or later

• On SUSE Linux Enterprise Server 11

  2.6.27.19 or later

For IBM: Linux on System z 

• On Red Hat Enterprise Linux 4

  2.6.9 or later

• On Red Hat Enterprise Linux 5

  2.6.18 or later

• On SUSE Linux Enterprise Server 10

  2.6.16.60 or later

• On SUSE Linux Enterprise Server 11

  2.6.32.12 or later

To determine if the required kernel is installed, enter the following command:

# uname -r

The following is a sample output displayed by running this command on an Oracle Linux 5 system:

2.6.18-128.el5PAE

In this example, the output shows the kernel version (2.6.18) and errata level (-128.el5PAE) on the system.

If the kernel version does not meet the requirement, then contact the operating system vendor for information about obtaining and installing kernel updates.

2.4.3 Package Requirements

The following are the list of packages required for Oracle Database 11g Release 2 (11.2):

• Oracle Database Package Requirements for Linux x86

• Oracle Database Package Requirements for Linux x86-64

• Oracle Database Package Requirements for IBM: Linux on System z

Oracle Database Package Requirements for Linux x86

binutils-2.15.92.0.2
compat-libstdc++-33-3.2.3
elfutils-libelf-0.97
elfutils-libelf-devel-0.97
gcc-3.4.6
gcc-c++-3.4.6
glibc-2.3.4-2.41
glibc-common-2.3.4
glibc-devel-2.3.4
glibc-headers-2.3.4
libaio-devel-0.3.105
libaio-0.3.105
libgcc-3.4.6
libstdc++-3.4.6
libstdc++-devel-3.4.6
make-3.80
numactl-0.6.4.i386
pdksh-5.2.14
sysstat-5.0.5

binutils-2.17.50.0.6
compat-libstdc++-33-3.2.3
elfutils-libelf-0.125
elfutils-libelf-devel-0.125
elfutils-libelf-devel-static-0.125
gcc-4.1.2
gcc-c++-4.1.2
glibc-2.5-24
glibc-common-2.5
glibc-devel-2.5
glibc-headers-2.5
kernel-headers-2.6.18
ksh-20060214
libaio-0.3.106
libaio-devel-0.3.106 
libgcc-4.1.2
libgomp-4.1.2
libstdc++-4.1.2 
libstdc++-devel-4.1.2
make-3.81
sysstat-7.0.2

binutils-2.20.51.0.2-5.11.el6.i686
compat-libcap1-1.10-1.i686
compat-libstdc++-33-3.2.3-69.el6.i686
gcc-4.4.4-13.el6.i686
gcc-c++-4.4.4-13.el6.i686
glibc-2.12-1.7.el6.i686
glibc-devel-2.12-1.7.el6.i686
ksh
libgcc-4.4.4-13.el6.i686
libstdc++-4.4.4-13.el6.i686
libstdc++-devel-4.4.4-13.el6.i686
libaio-0.3.107-10.el6.i686
libaio-devel-0.3.107-10.el6.i686
make-3.81-19.el6.i686
sysstat-9.0.4-11.el6.i686

binutils-2.16.91.0.5
compat-libstdc++-5.0.7
gcc-4.1.2
gcc-c++-4.1.2
glibc-2.4-31.63
glibc-devel-2.4-31.63
ksh-93r-12.9
libaio-0.3.104
libaio-devel-0.3.104
libelf-0.8.5
libgcc-4.1.2
libstdc++-4.1.2
libstdc++-devel-4.1.2
make-3.80
sysstat-8.0.4

binutils-2.19
gcc-4.3
gcc-c++-4.3
glibc-2.9
glibc-devel-2.9
ksh-93t
libstdc++33-3.3.3
libstdc++43-4.3.3_20081022
libstdc++43-devel-4.3.3_20081022
libaio-0.3.104
libaio-devel-0.3.104
libgcc43-4.3.3_20081022
libstdc++-devel-4.3
make-3.81
sysstat-8.1.5

Oracle Database Package Requirements for Linux x86-64

binutils-2.15.92.0.2
compat-libstdc++-33-3.2.3
compat-libstdc++-33-3.2.3 (32 bit)
elfutils-libelf-0.97
elfutils-libelf-devel-0.97
expat-1.95.7
gcc-3.4.6
gcc-c++-3.4.6
glibc-2.3.4-2.41
glibc-2.3.4-2.41 (32 bit)
glibc-common-2.3.4
glibc-devel-2.3.4
glibc-headers-2.3.4
libaio-0.3.105
libaio-0.3.105 (32 bit)
libaio-devel-0.3.105
libaio-devel-0.3.105 (32 bit)
libgcc-3.4.6
libgcc-3.4.6 (32-bit)
libstdc++-3.4.6
libstdc++-3.4.6 (32 bit)
libstdc++-devel 3.4.6
make-3.80
numactl-0.6.4.x86_64
pdksh-5.2.14
sysstat-5.0.5

binutils-2.17.50.0.6
compat-libstdc++-33-3.2.3
compat-libstdc++-33-3.2.3 (32 bit)
elfutils-libelf-0.125
elfutils-libelf-devel-0.125
gcc-4.1.2
gcc-c++-4.1.2
glibc-2.5-24
glibc-2.5-24 (32 bit)
glibc-common-2.5
glibc-devel-2.5
glibc-devel-2.5 (32 bit)
glibc-headers-2.5
ksh-20060214
libaio-0.3.106
libaio-0.3.106 (32 bit)
libaio-devel-0.3.106
libaio-devel-0.3.106 (32 bit)
libgcc-4.1.2
libgcc-4.1.2 (32 bit)
libstdc++-4.1.2
libstdc++-4.1.2 (32 bit)
libstdc++-devel 4.1.2
make-3.81
sysstat-7.0.2

binutils-2.20.51.0.2-5.11.el6 (x86_64)
compat-libcap1-1.10-1 (x86_64)
compat-libstdc++-33-3.2.3-69.el6 (x86_64)
compat-libstdc++-33-3.2.3-69.el6.i686
gcc-4.4.4-13.el6 (x86_64)
gcc-c++-4.4.4-13.el6 (x86_64)
glibc-2.12-1.7.el6 (i686)
glibc-2.12-1.7.el6 (x86_64)
glibc-devel-2.12-1.7.el6 (x86_64)
glibc-devel-2.12-1.7.el6.i686
ksh
libgcc-4.4.4-13.el6 (i686)
libgcc-4.4.4-13.el6 (x86_64)
libstdc++-4.4.4-13.el6 (x86_64)
libstdc++-4.4.4-13.el6.i686
libstdc++-devel-4.4.4-13.el6 (x86_64)
libstdc++-devel-4.4.4-13.el6.i686
libaio-0.3.107-10.el6 (x86_64)
libaio-0.3.107-10.el6.i686
libaio-devel-0.3.107-10.el6 (x86_64)
libaio-devel-0.3.107-10.el6.i686
make-3.81-19.el6
sysstat-9.0.4-11.el6 (x86_64)

binutils-2.16.91.0.5
compat-libstdc++-5.0.7
gcc-4.1.0
gcc-c++-4.1.2
glibc-2.4-31.63
glibc-devel-2.4-31.63
glibc-devel-32bit-2.4-31.63
ksh-93r-12.9
libaio-0.3.104
libaio-32bit-0.3.104
libaio-devel-0.3.104
libaio-devel-32bit-0.3.104
libelf-0.8.5
libgcc-4.1.2
libstdc++-4.1.2
libstdc++-devel-4.1.2
make-3.80
numactl-0.9.6.x86_64
sysstat-8.0.4

binutils-2.19
gcc-4.3
gcc-32bit-4.3
gcc-c++-4.3
glibc-2.9
glibc-32bit-2.9
glibc-devel-2.9
glibc-devel-32bit-2.9
ksh-93t
libaio-0.3.104
libaio-32bit-0.3.104
libaio-devel-0.3.104
libaio-devel-32bit-0.3.104
libstdc++33-3.3.3
libstdc++33-32bit-3.3.3
libstdc++43-4.3.3_20081022
libstdc++43-32bit-4.3.3_20081022
libstdc++43-devel-4.3.3_20081022
libstdc++43-devel-32bit-4.3.3_20081022
libgcc43-4.3.3_20081022
libstdc++-devel-4.3
make-3.81
sysstat-8.1.5

Oracle Database Package Requirements for IBM: Linux on System z

binutils-2.15.92.0.2-25 (s390x)
compat-libstdc++-33-3.2.3-47.3 (s390)
compat-libstdc++-33-3.2.3-47.3 (s390x)
gcc-3.4.6-11 (s390x)
gcc-c++-3.4.6-11 (s390x)
glibc-2.3.4-2.43 (s390)
glibc-2.3.4-2.43 (s390x)
glibc-devel-2.3.4-2.43 (s390)
glibc-devel-2.3.4-2.43 (s390x)
libaio-0.3.105-2 (s390)
libaio-0.3.105-2 (s390x)
libaio-devel-0.3.105-2 (s390)
libaio-devel-0.3.105-2 (s390x)
libgcc-3.4.6-11 (s390)
libgcc-3.4.6-11 (s390x)
libstdc++-3.4.6-10.0.1
libstdc++-3.4.6-10.0.1 (32-bit)
libstdc++-devel-3.4.6-10.0.1
libstdc++-devel-3.4.6-10.0.1 (x86_64)
make-3.80
pdksh
sysstat-5.0.5-25.el4 (s390x)

binutils-2.17.50.0.6-12.el5 (s390x)
compat-libstdc++-33-3.2.3-61 (s390)
compat-libstdc++-33-3.2.3-61 (s390x)
gcc-4.1.2-46.el5 (s390x)
gcc-c++-4.1.2-46.el5 (s390x)
glibc-2.5-42(s390)
glibc-2.5-42 (s390x)
glibc-devel-2.5-42 (s390)
glibc-devel-2.5-42 (s390x)
ksh
libaio-0.3.106-3.2 (s390)
libaio-0.3.106-3.2 (s390x)
libaio-devel-0.3.106-3.2 (s390)
libaio-devel-0.3.106-3.2 (s390x)
libgcc-4.1.2-46.el5 (s390)
libgcc-4.1.2-46.el5 (s390x)
libstdc++-4.1.2-46.el5 (s390)
libstdc++-4.1.2-46.el5 (s390x)
libstdc++-devel-4.1.2-46.el5 (s390x)
make-3.81
sysstat-7.0.2-3.el5 (s390x)

binutils-32bit-2.16.91.0.5-23.34.33 (s390x)
gcc-4.1.2_20070115-0.29.6 (s390x)
gcc-c++-4.1.2_20070115-0.29.6 (s390x)
glibc-2.4-31.74.1 (s390x)
glibc-32bit-2.4-31.74.1 (s390x)
glibc-devel-2.4-31.74.1 (s390x)
glibc-devel-32bit-2.4-31.74.1 (s390x)
ksh
libaio-0.3.104-14.2 (s390x)
libaio-32bit-0.3.104-14.2 (s390x)
libaio-devel-0.3.104-14.2 (s390x)
libaio-devel-32bit-0.3.104-14.2 (s390x)
libstdc++-4.1.2_20070115-0.29.6 (s390x)
libstdc++-devel-4.1.2_20070115-0.29.6 (s390x)
make-3.80-202.2 (s390x)
sysstat-8.0.4-1.7.27 (s390x)

binutils-2.20.0-0.7.9 (s390x)
gcc-4.3-62.198 (s390x)
gcc-c++-4.3-62.198 (s390x)
glibc-2.11.1-0.17.4 (s390x)
glibc-32bit-2.11.1-0.17.4 (s390x)
glibc-devel-2.11.1-0.17.4 (s390x)
glibc-devel-32bit-2.11.1-0.17.4 (s390x)
ksh
libaio-0.3.109-0.1.46 (s390x)
libaio-32bit-0.3.109-0.1.46 (s390x)
libaio-devel-0.3.109-0.1.46 (s390x)
libaio-devel-32bit-0.3.109-0.1.46 (s390x)
libstdc++43-4.3.4_20091019-0.7.35 (s390x)
libstdc++43-32bit-4.3.4_20091019-0.7.35 (s390x)
libstdc++43-devel-4.3.4_20091019-0.7.35 (s390x)
libstdc++43-devel-32bit-4.3.4_20091019-0.7.35 (s390x)
libgcc43-4.3.4_20091019-0.7.35 (s390x)
make-3.81
sysstat-8.1.5-7.9.56 (s390x)

See "Oracle ODBC Drivers" for information on ODBC packages.

To determine if the required packages are installed, enter commands similar to the following:

# rpm -q package_name

If a package is not installed, then install it from the Linux distribution media or download the required package version from the Linux vendor's Web site.

2.4.4 Compiler Requirements

For Linux x86 and Linux x86-64, Intel C++ Compiler 10.1 or later and the version of GNU C and C++ compilers listed under "Package Requirements" are supported with Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, and Oracle XML Developer's Kit (XDK) for Oracle Database 11g Release 2.

For IBM: Linux on System z the version of GNU C and C++ compilers listed under "Package Requirements" are supported for Oracle Database 11g Release 2.

2.4.5 Additional Software Requirements

Depending on the components you want to use, you must ensure that the following software is installed:

• Oracle ODBC Drivers

• Oracle JDBC/OCI Drivers

• Linux-PAM Library

• Oracle Messaging Gateway

• Programming Languages

• Browser Requirements

• Oracle Database Vault Preinstallation Requirement

2.9.1 Installing on DHCP Computers

Dynamic Host Configuration Protocol (DHCP) assigns dynamic IP addresses on a network. Dynamic addressing enables a computer to have a different IP address each time it connects to the network. In some cases, the IP address can change while the computer is still connected. You can have a mixture of static and dynamic IP addressing in a DHCP system.

In a DHCP setup, the software tracks IP addresses, which simplifies network administration. This lets you add a new computer to the network without having to manually assign a unique IP address to the newly added computer.

2.9.2 Installing on Multihomed Computers

You can install Oracle Database 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 host name. In addition, you can set up aliases for the host name. By default, Oracle Universal Installer uses the ORACLE_HOSTNAME environment variable setting to find the host name. If ORACLE_HOSTNAME is not set and you are installing on a computer that has multiple network cards, then Oracle Universal Installer determines the host name from the /etc/hosts file.

Clients must be able to access the computer either by using this host name or by using aliases for this host name. To verify, ping the host name from the client computers using the short name (host name only) and the full name (host name and domain name). Both tests must be successful.

Setting the ORACLE_HOSTNAME Environment Variable

Use the following procedure to set the ORACLE_HOSTNAME environment variable. For example, if the fully qualified host name is somehost.us.example.com, then enter one of the following commands:

In Bourne, Bash, or Korn shell:

$ ORACLE_HOSTNAME=somehost.us.example.com
$ export ORACLE_HOSTNAME

In C shell:

% setenv ORACLE_HOSTNAME somehost.us.example.com

2.9.3 Installing on Computers with Multiple Aliases

A computer with multiple aliases is registered with the naming service under a single IP but with multiple aliases. The naming service resolves any of those aliases to the same computer. Before installing Oracle Database on such a computer, set the ORACLE_HOSTNAME environment variable to the computer whose host name you want to use.

2.9.4 Installing on Non-Networked Computers

You can install Oracle Database on a non-networked computer. If the computer, such as a laptop, is configured for DHCP and you plan to connect the computer to the network after the Oracle Database installation, then use the ping command on the computer on which you want to install the database to check if the computer can connect to itself. Perform this step by first using only the host name and then using the fully qualified name, which should be in the /etc/hosts file.

If the ping command fails, then contact the system administrator.

Connecting the Computer to the Network after Installation

If you connect the computer to a network after installation, then the Oracle Database instance on the computer can work with other instances on the network. The computer can use a static IP or DHCP, depending on the network to which you are connected.

2.10.1 Creating Custom Configuration Groups and Users for Job Roles

This section provides an overview of how to create users and groups to divide access privileges by job roles. Log in as root to create these groups and users.

• Understanding Restrictions for Oracle Installations with Job Role Separation

• Database Groups for Job Role Installations

• Oracle Grid Infrastructure Groups for Job Role Installations

2.10.2 Creating Database Operating System Groups and Users with Job Role Separation

The following sections describe how to create the required operating system user and groups:

• Creating the Oracle Inventory Group

• Creating the OSDBA Group for Database Installations

• Creating an OSOPER Group for Database Installations

• Creating the OSASM Group for Oracle Automatic Storage Management

• Creating the OSDBA Group for Oracle Automatic Storage Management

• Creating the OSOPER Group for Oracle Automatic Storage Management

• Creating the Oracle Software Owner User

inventory_loc=central_inventory_location
inst_group=group

# grep oinstall /etc/group

# more /etc/oraInst.loc

inventory_loc=/u01/app/oraInventory
inst_group=oinstall

# /usr/sbin/groupadd oinstall

# /usr/sbin/groupadd -g 502 dba

# /usr/sbin/groupadd -g 503 oper

# /usr/sbin/groupadd -g 504 asmadmin

# /usr/sbin/groupadd -g 506 asmdba

# /usr/sbin/groupadd -g 505 asmoper

# id oracle
# id grid

uid=501(oracle) gid=501(oinstall) groups=502(dba),503(oper)

uid=8001(grid) gid=8001(oinstall) groups=8001(oinstall),8002(asmadmin),8003(asmdba),8006(dba)

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

2.12.1 Displaying and Changing Kernel Parameter Values

Enter the commands shown in the following table to display the current values of the kernel parameters. Note these values and identify any values that you must change:

If the value of any kernel parameter is different from the minimum value, then perform the following:

1. Using any text editor, create or edit the /etc/sysctl.conf file, and add or edit lines similar to the following:

   Note:

   Include lines only for the kernel parameter values to change. For the semaphore parameters (kernel.sem), you must specify all four values. If any of the current values are larger than the minimum value, then specify the larger value.

   fs.aio-max-nr = 1048576
   fs.file-max = 6815744
   kernel.shmall = 2097152
   kernel.shmmax = 4294967295
   kernel.shmmni = 4096
   kernel.sem = 250 32000 100 128
   net.ipv4.ip_local_port_range = 9000 65500
   net.core.rmem_default = 262144
   net.core.rmem_max = 4194304
   net.core.wmem_default = 262144
   net.core.wmem_max = 1048576
   

   By specifying the values in the /etc/sysctl.conf file, they persist when you restart the system. On SUSE Linux Enterprise Server systems, enter the following command to ensure that the system reads the /etc/sysctl.conf file when it restarts:

   # /sbin/chkconfig boot.sysctl on
   

2. Enter the following command to change the current values of the kernel parameters:

   # /sbin/sysctl -p
   

   Review the output from this command to verify that the values are correct. If the values are incorrect, edit the /etc/sysctl.conf file, then enter this command again.

3. Enter the command /sbin/sysctl -a to confirm that the values are set correctly.

4. On SUSE Linux Enterprise Server systems only, enter the following command for the system to read the /etc/sysctl.conf file when it restarts:

   # /sbin/chkconfig boot.sysctl on
   

5. On SUSE Linux Enterprise Server systems only, you must enter the GID of the oinstall group as the value for the parameter /proc/sys/vm/hugetlb_shm_group. Doing this grants members of oinstall a group permission to create shared memory segments.

   For example, where the oinstall group GID is 501:

   # echo 501 > /proc/sys/vm/hugetlb_shm_group
   

   After running this command, use vi to add the following text to /etc/sysctl.conf, and enable the boot.sysctl script to run when the system restarts:

   vm.hugetlb_shm_group=501
   

   Note:

   Only one group can be defined as the vm.hugetlb_shm_group.

6. After updating the values of the kernel parameters in the /etc/sysctl.conf file, either restart the computer, or run the command sysctl -p to make the changes in the /etc/sysctl.conf file available in the active kernel memory.

2.13.1 Oracle Base Directory

The Oracle base directory is a top-level directory for Oracle software installations. The Optimal Flexible Architecture (OFA) guidelines recommend that you use a path similar to the following for the Oracle base directory:

/mount_point/app/software_owner

In this example:

• mount_point is the mount point directory for the file system that contains the Oracle software.

  The examples in this guide use /u01 for the mount point directory.

• software_owner is the operating system user name of the software owner installing the Oracle software, for example oracle or grid.

You must specify the Oracle base directory that contains all Oracle products.

You can use the same Oracle base directory for multiple installations or you can create separate Oracle base directories for different installations. If different operating system users install Oracle software on the same system, then each user must create a separate Oracle base directory. The following are examples of Oracle base directories that can exist on the same system:

/u01/app/oracle
/u01/app/orauser

See "Creating an Oracle Base Directory".

2.13.2 Oracle Inventory Directory

The Oracle Inventory directory (oraInventory) stores an inventory of all software installed on the system. It is required and shared by all Oracle software installations on a single system. If you have an existing Oracle Inventory path, then Oracle Universal Installer continues to use that Oracle Inventory.

The first time you install Oracle software on a system, Oracle Universal Installer provides an Optimal Flexible Architecture-compliant path in the format /u[01-09]/app, such as /u01/app. The user running the installation has permissions to write to that path. If this is true, then Oracle Universal Installer creates the Oracle Inventory directory in the path /u[01-09]/app/oraInventory. For example:

/u01/app/oraInventory

If you have set ORACLE_BASE for the oracle user during installation, then Oracle Universal Installer creates the Oracle Inventory directory in the path ORACLE_BASE/../oraInventory. For example, if ORACLE_BASE is set to /u01/app/oracle, then the Oracle Inventory directory is created in the path /u01/app/oracle/oraInventory.

If you have neither created an OFA-compliant path nor set ORACLE_BASE, then the Oracle Inventory directory is placed in the home directory of the user that is performing the installation. For example:

/home/oracle/oraInventory

Oracle Universal Installer creates the directory that you specify and sets the correct owner, group, and permissions for it. You do not have to create it.

2.13.3 Oracle Home Directory

The Oracle home directory is the directory where you install the software for a particular Oracle product. You must install different Oracle products or different releases of the same Oracle product in separate Oracle home directories. When you run Oracle Universal Installer, it prompts you to specify the path to this directory and a name that identifies it. The directory that you specify must be a subdirectory of the Oracle base directory. Oracle recommends that you specify a path similar to the following for the Oracle home directory:

oracle_base/product/11.1.0/dbhome_1
oracle_base/product/11.2.0/dbhome_1
oracle_base/product/11.2.0/grid

Oracle Universal Installer creates the directory path that you specify under the Oracle base directory. It also sets the correct owner, group, and permissions on it. You do not have to create this directory.

2.14.1 Identifying an Existing Oracle Base Directory

Existing Oracle base directories may not have paths that follow the Optimal Flexible Architecture (OFA) guidelines. However, if you identify an existing Oracle Inventory directory or existing Oracle home directories, then you can usually identify the Oracle base directories, as follows:

• Identifying an existing Oracle Inventory directory. See "Creating the Oracle Inventory Group" for more information.

  Note:

  Oracle recommends that you do not put the oraInventory directory under the Oracle base directory for a new installation. If you have an existing installation, then follow the steps in this section.

• Identifying an existing Oracle home directory

  Enter the following command to display the contents of the oratab file:

  # more /etc/oratab
  

  If the oratab file exists, then it contains lines of code similar to the following:

  *:/u03/app/oracle/product/11.2.0/dbhome_1:N
  *:/opt/orauser/infra_904:N
  *:/oracle/9.2.0:N
  

  The directory paths specified on each line identify Oracle home directories. Directory paths that end with the user name of the Oracle software owner to use are valid choices for an Oracle base directory. If you intend to use the oracle user to install the software, then you can choose one of the following directories listed in the previous example:

  /u03/app/oracle
  /oracle
  

  Note:

  If possible, choose a directory path similar to the first one (/u03/app/oracle). This path complies with the OFA guidelines.

• Identifying an existing Oracle base directory

  After you locate the Oracle home directory, run a similar command to confirm the location of Oracle base:

  cat /u01/app/oraInventory/ContentsXML/inventory.xml
  

Before deciding to use an existing Oracle base directory for this installation, ensure that it meets the following conditions:

• It is not on the same file system as the operating system.

• It has sufficient free disk space, as follows:

  Requirement	Free Disk Space
  The Oracle base directory contains only software files.	Up to 4 GB
  The Oracle base directory contains both software and database files (not recommended for production databases).	Up to 6 GB

  
  

  To determine the free disk space on the file system where the Oracle base directory is located, enter the following command:

  # df -h oracle_base_path
  

See the following sections for more information:

• If an Oracle base directory exists and you want to use it, then see "Choosing a Storage Option for Oracle Database and Recovery Files" section.

  When you configure the oracle user's environment later in this chapter, set the ORACLE_BASE environment variable to specify the directory you chose.

• If an Oracle base directory does not exist on the system or to create an Oracle base directory, see "Creating an Oracle Base Directory".

2.14.2 Creating an Oracle Base Directory

Before you create an Oracle base directory, you must identify an appropriate file system with sufficient free disk space.

To identify an appropriate file system:

1. To determine the free disk space on each mounted file system, use the following command:

   # df -h
   

2. From the display, identify a file system that has the appropriate amount of free space.

   The file system that you identify can be a local file system, a cluster file system, or an NFS file system on a certified NAS device.

3. Note the name of the mount point directory for the file system that you identified.

To create the Oracle base directory and specify the correct owner, group, and permissions for it:

1. Enter commands similar to the following to create the recommended subdirectories in the mount point directory that you identified and set the appropriate owner, group, and permissions on them:

   # mkdir -p /mount_point/app/oracle_sw_owner
   # chown -R oracle:oinstall /mount_point/app/oracle_sw_owner
   # chmod -R 775 /mount_point/app/oracle_sw_owner
   

   For example:

   # mkdir -p /u01/app/oracle
   # chown -R oracle:oinstall /u01/app/oracle
   # chmod -R 775 /u01/app/oracle
   

2. When you configure the oracle user's environment later in this chapter, set the ORACLE_BASE environment variable to specify the Oracle base directory that you created.

2.16.1 Guidelines for Placing Oracle Database Files on a File System

If you choose to place the Oracle Database files on a file system, then use the following guidelines when deciding where to place them:

• The default path suggested by Oracle Universal Installer for the database file directory is a subdirectory of the Oracle base directory.

• You can choose either a single file system or more than one file system to store the database files:

  • If you want to use a single file system, then choose a file system on a physical device that is dedicated to the database.

    For best performance and reliability, choose a RAID device or a logical volume on more than one physical device and implement the stripe-and-mirror-everything (SAME) methodology.

  • If you want to use more than one file system, then choose file systems on separate physical devices that are dedicated to the database.

    This method enables you to distribute physical input-output operations and create separate control files on different devices for increased reliability. It also enables you to fully implement the OFA guidelines. You can choose the Advanced database creation option to implement this method.

• If you intend to create a preconfigured database during the installation, then the file system (or file systems) that you choose must have at least 2 GB of free disk space.

  For production databases, you must estimate the disk space requirement depending on the use of the database.

• For optimum performance, the file systems that you choose must be on physical devices that are used only by the database.

• The oracle user must have write permissions to create the files in the path that you specify.

2.16.2 Creating Required Directories

To create directories for the Oracle database or recovery files on separate file systems from the Oracle base directory:

1. Use the following to determine the free disk space on each mounted file system:

   # df -h
   

2. From the display, identify the file systems to use:

   File Type	File System Requirements
   Database files	Choose either: A single file system with at least 2 GB of free disk space Two or more file systems with at least 2 GB of free disk space in total
   Recovery files	Choose a file system with at least 2.4 GB of free disk space

   
   

   If you are using the same file system for many file types, then add the disk space requirements for each type to determine the total disk space requirement.

3. Note the names of the mount point directories for the file systems that you identified.

4. Enter commands similar to the following to create the recommended subdirectories in each of the mount point directories and set the appropriate owner, group, and permissions on them:

   • Database file directory:

     # mkdir /mount_point/oradata
     # chown oracle:oinstall /mount_point/oradata
     # chmod 775 /mount_point/oradata
     

     The default location for the database file directory is $ORACLE_BASE/oradata.

   • Recovery file directory (fast recovery area):

     # mkdir /mount_point/fast_recovery_area
     # chown oracle:oinstall /mount_point/fast_recovery_area
     # chmod 775 /mount_point/fast_recovery_area
     

     The default fast recovery area is $ORACLE_BASE/fast_recovery_area. Oracle recommends that you keep the fast recovery area on a separate physical disk than that of the database file directory. This enables you to use the fast recovery area to retrieve data if the disk containing oradata is unusable for any reason.

5. If you also want to use Oracle ASM for storage, then see "Preparing Disks for an Oracle Automatic Storage Management Installation" and "Stopping Existing Oracle Processes" section.

2.18.1 Example of Creating a Udev Permissions File for Oracle Database

See the examples mentioned in "Configuring Storage for Oracle Database Files Using Block Devices" for more information about creating a permissions file.

2.18.2 Example of Configuring Block Device Storage for Oracle Database

The following procedure creates partitions for Oracle Database files on block devices:

1. Log in as root

2. Enter the fdisk command to format a specific storage disk. For example, /sbin/fdisk /dev/sdb

3. Create a partition. For example, create a 280 MB partition for data files.

4. Use the command similar to the following to update the kernel partition table for the shared storage device:

   /sbin/partprobe diskpath
   

The following is an example of how to use the fdisk command to create one partition on a shared storage block disk device for a data file:

$ sudo sh
Password:
# /sbin/fdisk /dev/sdb
The number of cylinders for this disk is set to 1024.
Command (m for help): n
Command action
  e   extended
  P   primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-1024, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-4462, default 1)
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-1024, default 4462): using default value 4462

Command (m for help):w

The partition table has been altered!
Calling ioctl () to re-read partition table.
Synching disks.
# exit
Last login Wed Feb 21 20:23:01 from localnode
$ sudo sh
Password:
# /sbin/partprobe /dev/sdb1