2 Preinstallation Requirements

2.2.1 Memory Requirements

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

• At least 256 MB of RAM.

  To determine the RAM size, enter the following command:

  # /usr/sbin/lsattr -E -l sys0 -a realmem
  

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

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

  Note:

  On AIX systems, with 1 GB or more of memory, Oracle recommends that you set the paging space to an initial setting of half the size of RAM plus 4 GB, with an upper limit of 32 GB. During installation, to optimize paging, monitor the paging space use in a separate window. Use the command chps to increase or decrease the paging space size. The output of chps should indicate paging space use of less than 25 percent on a healthy system. Refer to Oracle Database Administrator's Reference for Linux and UNIX-Based Operating Systems for more information about configuring paging space.

  RAM	Swap Space
  Between 0 MB and 256 MB	3 times the size of RAM
  Between 256 MB and 512 MB	2 times the size of RAM
  Between 512 MB and 2 GB	1.5 times the size of RAM
  Between 2 GB and 16 GB	Equal to the size of RAM
  More than 16 GB	16 GB

  
  

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

# /usr/sbin/lsps -a

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

2.2.2 System Architecture

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

# /usr/bin/getconf HARDWARE_BITMODE

The expected output of this command is 64. If you do not see the expected output, then you cannot install the software on this system.

To determine if the system is started in 64-bit mode, enter the following command:

# bootinfo -K

The result of this command must be 64, indicating that the 64-bit kernel is enabled.

2.2.3 Disk Space Requirements

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

• The minimum disk space requirement for a client install in the /tmp directory is 130 MB

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

  # df -k /tmp
  

  If free disk 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.

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

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

  # df -k
  

• The following table describes the disk space requirements for software files for each installation type on AIX Based Systems

  Installation Type	Requirement for Software Files
  Instant Client	370 MB
  Administrator	3.64 GB
  Runtime	1.91 GB
  Custom (maximum)	3.86 GB

  
  

2.2.4 Display Requirements

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

2.3.1 Operating System Requirements

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

• AIX 5L V5.3 TL 09 SP1 ("5300-09-01"), 64 bit kernel

• AIX 6.1 TL 02 SP1 ("6100-02-01), 64-bit kernel

• AIX 7.1 TL 0 SP1 ("7100-00-01"), 64-bit kernel

The following operating system filesets are required for AIX 5L:

• bos.adt.base

• bos.adt.lib

• bos.adt.libm

• bos.perf.libperfstat 5.3.9.0 or later

• bos.perf.perfstat

• bos.perf.proctools

• xlC.aix50.rte.10.1.0.0 or later

• gpfs.base 3.2.1.8 or later

The following operating system filesets are required for AIX 6.1:

• bos.adt.base

• bos.adt.lib

• bos.adt.libm

• bos.perf.libperfstat 6.1.2.1 or later

• bos.perf.perfstat

• bos.perf.proctools

• xlC.aix61.rte.10.1.0.0 or later

• xlC.rte.10.1.0.0 or later

• gpfs.base 3.2.1.8 or later

The following operating system filesets are required for AIX 7.1:

• bos.adt.base

• bos.adt.lib

• bos.adt.libm

• bos.perf.libperfstat

• bos.perf.perfstat

• bos.perf.proctools

• xlC.aix61.rte.10.1.0.0 or later

• xlC.rte.10.1.0.0 or later

• gpfs.base 3.3.0.11 or later

1. To determine the distribution and version of AIX installed, enter the following command:

   # oslevel -s
   

   For AIX 5L: If the operating system version is lower than AIX 5.3 Technology Level 9 SP 1, then upgrade your operating system to this, or a later, level.

   For AIX 6.1: If the operating system version is lower than AIX 6.1 Technology Level 2 SP 1, then upgrade your operating system to this, or a later, level.

   For AIX 7.1: If the operating system version is lower than AIX 7.1 Technology Level 0 SP 1, then upgrade your operating system to this, or a later, level.

   AIX maintenance packages are available from the following Web site:

   http://www-933.ibm.com/support/fixcentral/

2. To determine whether the required filesets are installed and committed, enter a command similar to the following:

   # lslpp -l bos.adt.base bos.adt.lib bos.adt.libm bos.perf.perfstat \
   bos.perf.libperfstat bos.perf.proctools
   

3. To determine the supported kernel mode, enter a command similar to the following:

   # getconf KERNEL_BITMODE
   

   Note:

   • The expected output of this command is 64. If you do not see the expected output, then you cannot install the software on this system.

   • Oracle Database 11g supports 64-bit kernel and does not provide support for 32-bit kernel applications.

2.3.2 Compiler Requirements

The following is the minimum compiler requirement for Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, and Oracle XML Developer's Kit (XDK) with Oracle Database 11g Release 2:

IBM XL C/C++ Enterprise Edition for AIX, V9.0 April 2008 PTF:

You can download this software from the following link:

http://www-01.ibm.com/support/docview.wss?uid=swg24015075

2.3.3 Additional Software Requirements

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

• Oracle JDBC/OCI Drivers

• ODBC Drivers

• Separate 32-Bit Client Software for 64-Bit Platforms

• Browser Requirements

• Programming Languages

2.3.4 Patch Requirements

The following, or later, patches are required for Oracle Database 11g Release 2 (11.2) for AIX Based Systems:

The following procedure describes how to check these requirements:

• To determine whether an APAR is installed, enter a command similar to the following:

  # /usr/sbin/instfix -i -k "IZ42940 IZ49516 IZ52331 IZ41855 IZ52319"
  

  If an APAR is not installed, then download it from the following Web site and install it:

  http://www-933.ibm.com/support/fixcentral/

• If you require a CSD for WebSphere MQ, then refer to the following Web site for download and installation information:

  http://www-947.ibm.com/support/entry/portal/Downloads/Software/WebSphere/WebSphere_MQ

2.3.5 Instant Client Light Requirements

In addition to the requirements described in the preceding section, if you plan to use Instant Client Light, then the applications must use the following languages and character sets:

• Language: Any language that is supported by Oracle

• Territory: Any territory that is supported by Oracle

• Character sets:

  • Single byte

    • US7ASCII

    • WE8DEC

    • WE8MSWIN1252

    • WE8ISO8859P1

  • Unicode

    • UTF8

    • AL16UTF16

    • AL32UTF8

    Instant Client Light can connect to databases having one of the following database character sets:

    • US7ASCII

    • WE8DEC

    • WE8MSWIN1252

    • WE8ISO8859P1

    • WE8EBCDIC37C

    • WE8EBCDIC1047

    • UTF8

    • AL32UTF8

The language, territory, and character sets are determined by the NLS_LANG environment variable.

2.4.1 Creating the Oracle Inventory Group

You must create the Oracle Inventory group if it does not exist. The following sections describe how to determine the Oracle Inventory group name, if it exists, and how to create it if necessary:

• Determining Whether the Oracle Inventory Group Exists

• Creating the Oracle Inventory Group

Determining Whether the Oracle Inventory Group Exists

When you install Oracle software on the system for the first time, Oracle Universal Installer creates the oraInst.loc file. This file identifies the name of the Oracle Inventory group (typically, oinstall), and the path of the Oracle Inventory directory.

An oraInst.loc file has content similar to the following:

inventory_loc=central_inventory_location
inst_group=group

In the preceding example, central_inventory_location is the location of the Oracle Central Inventory, and group is the name of the group that has permissions to write to the central inventory.

If you have an existing Oracle Inventory, then ensure that you use the same Oracle Inventory for all Oracle software installations, and ensure that all Oracle software users you intend to use for installation have permissions to write to this directory.

To determine whether the Oracle Inventory group exists, enter the following command:

# more /etc/oraInst.loc

If the oraInst.loc file exists, then the output from this command is similar to the following:

inventory_loc=/u01/app/oraInventory
inst_group=oinstall

In the previous output example:

• The inventory_loc parameter shows the location of the Oracle Inventory

• The inst_group parameter shows the name of the Oracle Inventory group (in this example, oinstall).

Creating the Oracle Inventory Group

If the oraInst.loc file does not exist, then create the Oracle Inventory group as follows:

1. Enter the following command:

   # smit security
   

2. Choose the appropriate menu items to create the oinstall group.

3. Press F10 to exit.

2.4.2 Creating the Oracle Software Owner User

You must create an Oracle software owner user in the following circumstances:

• If an Oracle software owner user does not exist, for example, if this is the first installation of Oracle software on the system

• If an Oracle software owner user exists, but you want to use a different operating system user

# id oracle

uid=440(oracle) gid=200(oinstall) groups=201(dba),202(oper)

2.5.1 Oracle Base Directory

The Oracle base directory is a top-level directory for Oracle software installations. On UNIX systems, 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.

You must specify the ORACLE_BASE folder 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 example Oracle base directories could all exist on the same system:

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

The following sections describe how to identify existing Oracle base directories that may be suitable for the installation and how to create an Oracle base directory if necessary.

Regardless of whether you create an Oracle base directory or decide to use an existing one, you must set the ORACLE_BASE environment variable to specify the full path to this directory.

2.5.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 OFA-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/oraInventory.

If you have created neither 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.5.3 Oracle Home Directory

The Oracle home directory is the directory where you choose to 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.2.0/client_1

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.6.1 Identifying an Existing Oracle Base Directory

Existing Oracle base directories may not have paths that follow 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

  Enter the following command to view the contents of the oraInst.loc file:

  # more /etc/oraInst.loc
  

  If the oraInst.loc file exists, then the output from this command is similar to the following:

  inventory_loc=/u01/app/oraInventory
  inst_group=oinstall
  

  The inventory_loc parameter identifies the Oracle Inventory directory (oraInventory). The parent directory of the oraInventory directory is typically an Oracle base directory. In the previous example, /u01/app/oracle is an Oracle base directory.

• Identifying existing Oracle home directories

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

  # more /etc/oratab
  

  If the oratab file exists, then it contains lines 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 could choose one of the following directories from the previous example:

  /u03/app/oracle
  /oracle
  

  Note:

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

• Identifying existing Oracle base directories

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

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

To continue:

• If an Oracle base directory exists and you want to use it, then refer to the "Configuring the oracle User's Environment" 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, refer to the following section.

2.6.2 Creating an Oracle Base Directory

Before you create an Oracle base directory, you must identify an appropriate file system with 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 -k
   

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

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
   # chown -R oracle:oinstall /mount_point/app
   # chmod -R 775 /mount_point/app/
   

   For example:

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

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 have created.