2 Oracle Database Preinstallation Requirements

2.2.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:

  # /usr/contrib/bin/machinfo  | grep -i Memory
  

  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:

  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:

# /usr/sbin/swapinfo -a

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

2.2.2 Disk Space Requirements

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

• At least 1 GB of space in the /tmp directory

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

  # bdf /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 HP-UX Itanium systems:

  Installation Type	Requirement for Software Files (GB)
  Enterprise Edition	7.10
  Standard Edition	6.10

  
  

  Installation Type	Disk Space for Data Files (GB)
  Enterprise Edition	2.20
  Standard Edition	1.51

  
  

• The following tables describe the disk space requirements for software files and data files for each installation type on HP-UX PA-RISC systems:

  Installation Type	Requirement for Software Files (GB)
  Enterprise Edition	5.0
  Standard Edition	4.7

  
  

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

  
  

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

# bdf

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.2.3 Display Requirements

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

2.2.4 Run Level Requirement

Ensure that the system is started with run level 3.

2.3.1 Operating System Requirements

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

• HP-UX 11i V3 patch Bundle Sep/ 2008 (B.11.31.0809.326a) or higher

To determine the distribution and version of HP-UX installed, enter the following command:

# uname -a

HP-UX hostname B.11.31 U ia64 4156074294 unlimited-user license

In this example, the version of HP-UX 11i is 11.31 and the process is HP-UX Itanium.

Verify that the system meets the minimum patch bundle requirements using the following command:

# /usr/sbin/swlist -l bundle |grep QPK

The QPK (Quality Pack) bundles have version numbers of the form B.11.31.0809.326a (for the September 2008 release), B.11.31.0903.334a (for the March 2009 release), and so on.

If a required bundle, product, or fileset is not installed, then you must install it. See your operating system or software documentation for information about installing products.

2.3.2 Compiler Requirements

The following are the compiler requirements for HP-UX systems Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, and Oracle XML Developer's Kit (XDK) with Oracle Database 11g Release 2 (11.2):

On HP-UX PA RISC

• HP ANSI C B.11.31.04 (Swlist Bundle - C.11.31.04) - September 2008

• aC++ A.03.85 (Swlist Bundle - C.11.31.04) - September 2008

On HP-UX Itanium

• A.06.20 (HP C/aC++ Swlist Bundle - C.11.31.04) - Sep 2008

2.3.3 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

• Oracle Messaging Gateway

• Programming Languages

• Browser Requirements

• Oracle Database Vault Preinstallation Requirement

2.3.4 Patch Requirement

The following, or later, patches and bundles are required for Oracle Database 11g Release 2 (11.2) for HP-UX systems:

• HP-UX Itanium

• HP-UX PA-RISC

HP-UX Itanium

HP-UX PA-RISC

To ensure that the system meets these requirements:

1. To determine if a patch is installed, enter a command similar to the following:

   # /usr/sbin/swlist -l patch | grep PHSS_37959
   

   Alternatively, to list all installed patches, enter the following command:

   # /usr/sbin/swlist -l patch | more
   

2. If a required patch is not installed, then download it from the following Web site and install it:

   http://www.hp.com/go/hpsc

   If the Web site displays a recent version of the patch, then download and install that version.

2.7.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.7.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.7.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.7.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.8.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.8.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

• Creating the External Jobs User Account for HP-UX

inventory_loc=central_inventory_location
inst_group=group

# grep oinstall /etc/group

# more /var/opt/oracle/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.10.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.10.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.10.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.11.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 /var/opt/oracle/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.

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

  # bdf 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.11.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:

   # bdf
   

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.13.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.13.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:

   # bdf
   

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.