2 Pre-installation Tasks

Log In to the System as root

Before you install the Oracle software, you must complete several tasks as the root user. To log in as the root user, complete one of the following procedures:

• If you are installing the software from an X Window System workstation or X terminal:

  1. Start a local terminal session, for example, an X terminal (xterm).

  2. If you are not installing the software on the local system, enter the following command to enable remote hosts to display X applications on the local X server:

     $ xhost +
     
     

  3. If you want to install the software on a remote system, enter a command similar to the following to connect to that system:

     $ telnet remote_host
     
     

  4. If you are not logged in as the root user, enter the following command to switch user to root:

     $ su - root
     password:
     #
     
     

• If you are installing the software from a PC or other system with X server software installed:

  
  

  Note: If necessary, see your X server documentation for more information about completing this procedure. Depending on the X server software that you are using, you may need to complete the tasks in a different order.

  
  

  1. Start the X server software.

  2. Configure the security settings of the X server software to permit remote hosts to display X applications on the local system.

  3. Connect to the remote system where you want to install the software and start a terminal session on that system, for example, an X terminal (xterm).

  4. If you are not logged in as the root user on the remote system, enter the following command to switch user to root:

     $ su - root
     password:
     #
     
     

Check the Hardware Requirements

The system must meet the following minimum hardware requirements:

• 256 MB of physical RAM

• 512 MB of swap space

• 400 MB of disk space in the /tmp directory

• Between 180 MB and 1.9 GB of disk space for the Oracle software, depending on the installation type and platform

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

1. To determine the physical RAM size, enter one of the following commands:

   Platform	Command
   AIX	# /usr/sbin/lsattr -E -l sys0 -a realmem
   HP-UX	# /usr/sbin/dmesg | grep "Physical:"
   Linux	# grep MemTotal /proc/meminfo
   Solaris	# /usr/sbin/prtconf | grep "Memory size"
   Tru64 UNIX	# /bin/vmstat -P | grep "Total Physical Memory"

   
   

   If the size of the physical RAM installed in the system is less than the required size, you must install more memory before continuing.

2. To determine the size of the configured swap space, enter one of the following commands:

   Platform	Command
   AIX	# /usr/sbin/lsps -a
   HP-UX	# /usr/sbin/swapinfo -a
   Linux	# grep SwapTotal /proc/meminfo
   Solaris	# /usr/sbin/swap -s
   Tru64 UNIX	# /sbin/swapon -s

   
   

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

3. To determine the amount of disk space available in the /tmp directory, enter one of the following commands:

   • HP-UX:

     # bdf /tmp
     
     

   • Other operating systems:

     # df -k /tmp
     
     

   If there is less than 400 MB of disk space available in the /tmp directory, complete one of the following steps:

   • Delete unnecessary files from the /tmp directory to achieve the required disk space.

   • Set the TEMP and TMPDIR environment variables when setting the oracle user’s environment (described later).

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

4. To determine the amount of free disk space on the system, enter one of the following commands:

   • HP-UX:

     # bdf
     
     

   • Other operating systems:

     # df -k
     
     

   The following table shows the approximate disk space requirements for software files for each installation type:

   Platform	Installation Type	Requirement for Software Files (MB)
   AIX	Instant Client	150
   	Administrator	1900
   	Runtime	1000
   	Custom (maximum)	1800
   HP-UX	Instant Client	150
   	Administrator	1500
   	Runtime	1000
   	Custom	1400
   Linux	Instant Client	110
   	Administrator	650
   	Runtime	350
   	Custom (maximum)	650
   Solaris	Instant Client	150
   	Administrator	1000
   	Runtime	600
   	Custom (maximum)	850
   Tru64 UNIX	Instant Client	150
   	Administrator	1900
   	Runtime	1000
   	Custom (maximum)	1800

   
   

5. To determine whether the system architecture can run the software, enter one of the following commands:

   
   

   Note: If you do not see the expected output, you cannot install the software on this system.

   
   

   Platform	Command	Expected Output
   AIX	# /usr/bin/getconf HARDWARE_BITMODE	64
   HP-UX	# /bin/getconf KERNEL_BITS	64
   Linux	# grep "model name" /proc/cpuinfo	This command displays the processor type. Verify that the processor architecture matches the Oracle software release that you want to install.
   Solaris	# /bin/isainfo -kv	64-bit sparcv9 kernel modules

   
   

Check the Software Requirements

Depending on your operating system, see one of the following sections for information about checking the software requirements:

• Checking the Software Requirements on AIX

• Checking the Software Requirements on HP-UX

• Checking the Software Requirements on Linux

• Checking the Software Requirements on Solaris

• Checking the Software Requirements on Tru64 UNIX

bos.adt.base
bos.adt.lib
bos.adt.libm
bos.perf.libperfstat
bos.perf.perfstat
bos.perf.proctools

xlfcmp
xlfrte

C-ANSI-C

ACXX

FORTRAN90

DCE-C-Tools
DCE-CDS-Server
DCE-Core
DCE-CoreAdmin
DCE-CoreTools
DCE-SEC-Server

GOLDAPPS11i
GOLDBASE11i

http://www.hp.com/products1/unix/java/patches/index.html

# cd /usr/lib
# ln -s libX11.3 libX11.sl
# ln -s libXIE.2 libXIE.sl
# ln -s libXext.3 libXext.sl
# ln -s libXhp11.3 libXhp11.sl
# ln -s libXi.3 libXi.sl
# ln -s libXm.4 libXm.sl
# ln -s libXp.2 libXp.sl
# ln -s libXt.3 libXt.sl
# ln -s libXtst.2 libXtst.sl

make-3.79
binutils-2.11.90.0.8-12

gcc-2.96.108.1
openmotif-2.1.30-11

gcc-3.2.3-2
compat-db-4.0.14.5
compat-gcc-7.3-2.96.122
compat-gcc-c++-7.3-2.96.122
compat-libstdc++-7.3-2.96.122
compat-libstdc++-devel-7.3-2.96.122
openmotif-2.2.2-16
setarch-1.3-1 

gcc-3.2.2-38
openmotif-2.2.2-124

SUNWarc
SUNWbtool
SUNWhea
SUNWlibm
SUNWlibms
SUNWsprot
SUNWsprox
SUNWtoo
SUNWi1of
SUNWi1cs
SUNWi15cs
SUNWxwfnt

http://java.sun.com/j2se/1.4.2/font-requirements.html

OSFCMPLRS
OSFLIBA
OSFPGMR
OSFSER
OSFX11

DCECDS
DECRTS
DCESEC

DTCCMPLR

CXXBASE
CXXLIB
CXXOLD

DFABASE
DFACOM
DFARTL

T64V51BB22AS0002-20030415

T64KIT0020879-V51BB22-E-20031125

# /usr/sbin/dupatch -track -type kit

http://itrc.hp.com/service/patch/mainPage.do

Create Required UNIX Group and User

Depending on whether this is the first time Oracle software is being installed on this system and on the products that you are installing, you may need to create the following UNIX group and user:

• The Oracle Inventory group (oinstall)

  You must create this group the first time you install Oracle software on the system. The usual name chosen for this group is oinstall. This group owns the Oracle inventory, which is a catalog of all Oracle software installed on the system.

  
  

  Note: If Oracle software is already installed on the system, the existing Oracle Inventory group must be the primary group of the UNIX user that you use to install new Oracle software. The following sections describe how to identify an existing Oracle Inventory group.

  
  

• The Oracle software owner user (oracle)

  You must create this user the first time you install Oracle software on the system. This user owns all of the software installed during the installation. The usual name chosen for this user is oracle. This user must have the Oracle Inventory group as its primary group.

A single Oracle Inventory group is required for all installations of Oracle software on the system. After the first installation of Oracle software, you must use the same Oracle Inventory group for all subsequent Oracle software installations on that system. However, you can choose to create different Oracle software owner users for separate installations.

The following sections describe how to create the required UNIX user and group.

inventory_loc=/u01/app/oracle/oraInventory
inst_group=oinstall

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

Identify Required Software Directories

You must identify or create three directories for the Oracle software, as follows:

• Oracle base directory

• Oracle Inventory directory

• Oracle home directory

The following subsections describe the requirements for these directories.

The Oracle base directory acts as a top-level directory for Oracle software installations. It is analogous to the C:\Oracle directory used for Oracle software installations on Windows systems. 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/oracle_sw_owner

In this example:

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

  The examples in this guide use /u01 for the mount point directory. However, you could choose another mount point directory, /oracle or /opt/oracle for example.

• oracle_sw_owner is the UNIX user name of the Oracle software owner, for example oracle.

You can use the same Oracle base directory for more than one installation or you can create separate Oracle base directories for different installations. If different UNIX users install Oracle software on the same system, 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
/opt/oracle/app/oracle

The following sections describe how to identify existing Oracle base directories that might be suitable for your installation and how to create a new Oracle base directory if necessary.

Regardless of whether you create a new 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.

The Oracle Inventory directory (oraInventory) stores an inventory of all software installed on the system. It is required by, and shared by, all Oracle software installations on a single system. The first time you install Oracle software on a system, the Installer prompts you to specify the path to this directory. Oracle recommends that you choose the following path:

oracle_base/oraInventory

The Installer creates the directory that you specify and sets the correct owner, group, and permissions on it. You do not need to create it.

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 the Installer, it prompts you to specify the path to this directory, as well as 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/10.1.0/client_1

The 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 need to create this directory.

Identify or Create an Oracle Base Directory

Before starting the installation, you must either identify an existing Oracle base directory or if required, create a new one. This section contains information about the following:

• Identifying an Existing Oracle Base Directory

• Creating a New Oracle Base Directory

Existing Oracle base directories might not have paths that comply with OFA guidelines. However, if you identify an existing Oracle Inventory directory or existing Oracle home directories, you can usually identify the Oracle base directories, as follows:

• Identify an existing Oracle Inventory directory

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

  • AIX and Linux:

    # more /etc/oraInst.loc
    
    

  • Other operating systems:

    # more /var/opt/oracle/oraInst.loc
    
    

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

  inventory_loc=/u01/app/oracle/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.

• Identify existing Oracle home directories

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

  • Solaris:

    # more /var/opt/oracle/oratab
    
    

  • Other operating systems:

    # more /etc/oratab
    
    

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

  *:/u03/app/oracle/product/10.1.0/db_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 that you want to use are valid choices for an Oracle base directory. If you intend to use the oracle user to install the software, 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.

  
  

To continue:

• If an Oracle base directory exists and you want to use it, see the "Configure the oracle User’s Environment" section.

  When you are configuring 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 if you want to create a new Oracle base directory, see the following section.

To identify an appropriate file system, follow these steps:

1. Use the df -k command (or bdf command on HP-UX) to determine the free disk space on each mounted file system.

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, follow these steps:

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
   
   

   If the mount point you identified is /u01 and oracle is the user name of the Oracle software owner, the recommended Oracle base directory path is as follows:

   /u01/app/oracle
   
   

2. When you are configuring the oracle user’s environment later in this chapter, set the ORACLE_BASE environment variable to specify this directory.

Configure the oracle User’s Environment

You run the Installer from the oracle account. However, before you start the Installer you must configure the environment of the oracle user. To configure the environment, you must:

• Set the default file mode creation mask (umask) to 022 in the shell startup file.

• Set the DISPLAY and ORACLE_BASE environment variables.

To set the oracle user’s environment, follow these steps:

1. Start a new terminal session, for example, an X terminal (xterm).

2. Enter the following command to ensure that X Window applications can display on this system:

   $ xhost +
   
   

3. If you are not already logged in to the system where you want to install the software, log in to that system as the oracle user.

4. If you are not logged in as the oracle user, switch user to oracle:

   $ su - oracle
   
   

5. To determine the default shell for the oracle user, enter the following command:

   $ echo $SHELL
   
   

6. Open the oracle user’s shell startup file in any text editor:

   
   

   Note: On Red Hat Linux, .bash_profile is the user startup file for the Bash shell.

   
   

   • Bourne shell (sh), Bash shell (bash), or Korn shell (ksh):

     $ vi .profile
     
     

   • C shell (csh or tcsh):

     % vi .login
     
     

7. Enter or edit the following line, specifying a value of 022 for the default file creation mask:

   umask 022
   
   

8. If the ORACLE_SID, ORACLE_HOME, or ORACLE_BASE environment variables are set in the file, remove the appropriate lines from the file.

9. Save the file and exit from the editor.

10. To run the shell startup script, enter one of the following commands:

    • Bash shell on Red Hat Enterprise Linux:

      $ . ./.bash_profile
      
      

    • Bourne, Bash, or Korn shell:

      $ . ./.profile
      
      

    • C shell:

      % source ./.login
      
      

11. If you are not installing the software on the local system, enter a command similar to the following to direct X applications to display on the local system:

    • Bourne, Bash, or Korn shell:

      $ DISPLAY=local_host:0.0 ; export DISPLAY
      
      

    • C shell:

      % setenv DISPLAY local_host:0.0
      
      

    In this example, local_host is the host name or IP address of the system you want to use to display the Installer (your workstation or PC).

12. If you determined that the /tmp directory has less than 400 MB of free disk space, identify a file system with at least 400 MB of free space and set the TEMP and TMPDIR environment variables to specify a temporary directory on this file system:

    1. Use the df -k command (or bdf command on HP-UX) to identify a suitable file system with sufficient free space.

    2. If necessary, enter commands similar to the following to create a temporary directory on the file system you identified, and set the appropriate permissions on the directory:

       $ su - root
       # mkdir /mount_point/tmp
       # chmod a+wr /mount_point/tmp
       # exit
       
       

    3. Enter commands similar to the following to set the TEMP and TMPDIR environment variables:

       • Bourne, Bash, or Korn shell:

         $ TEMP=/mount_point/tmp
         $ TMPDIR=/mount_point/tmp
         $ export TEMP TMPDIR
         
         

       • C shell:

         % setenv TEMP /mount_point/tmp
         % setenv TMPDIR /mount_point/tmp
         
         

13. Enter commands similar to the following to set the ORACLE_BASE environment variable:

    • Bourne, Bash, or Korn shell:

      $ ORACLE_BASE=/u01/app/oracle
      $ export ORACLE_BASE
      
      

    • C shell:

      % setenv ORACLE_BASE /u01/app/oracle
      
      

    In these examples, /u01/app/oracle is the Oracle base directory that you created or identified earlier.

14. If you intend to use Pro*COBOL, set the following environment variables. If you must specify several values for an environment variable, for example PATH, separate the values with a colon (:).

    Environment Variable	Required By	Sample Setting and Description
    COBDIR	Pro*COBOL	AIX: /opt/lpp/cobol64/cobol HP-UX, Linux, and Solaris: /opt/lib/cobol Tru64 UNIX: /usr/lib/cobol Specifies the directory where COBOL is installed on the system.
    PATH	Pro*COBOL	$COBDIR/bin:$PATH Specifies the directory where the COBOL compiler executable is located.

    
    

15. Enter the following command to ensure that the ORACLE_HOME and TNS_ADMIN environment variables are not set:

    • Bourne, Bash, or Korn shell:

      $ unset ORACLE_HOME
      $ unset TNS_ADMIN
      
      

    • C shell:

      % unsetenv ORACLE_HOME
      % unsetenv TNS_ADMIN
      
      

    
    

    Note: If the ORACLE_HOME environment variable is set, the Installer uses the value it specifies as the default path for the Oracle home directory. However, if you set the ORACLE_BASE environment variable, Oracle recommends that you unset the ORACLE_HOME environment variable and choose the default path suggested by the Installer.

    
    

16. To verify that the environment has been set correctly, enter the following commands:

    $ umask
    $ env | more
    
    

    Verify that the umask command displays a value of 22, 022, or 0022 and the environment variables that you set in this section have the correct values.