Skip Headers
Oracle® Database Client Installation Guide
10g Release 2 (10.2) for hp-ux PA-RISC (64-Bit)

Part Number B19070-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Feedback

Go to previous page
Previous
Go to next page
Next
View PDF

2 Preinstallation Tasks

This chapter describes the tasks that you must complete before you start Oracle Universal Installer. It includes information about the following tasks:

2.1 Logging 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:


Note:

Unless you intend to complete a silent-mode installation, you must install the software from an X Window System workstation, an X terminal, or a PC or other system with X server software installed.

For more information about silent-mode installations, refer to Appendix A.


2.2 Checking the Hardware Requirements

The system must meet the following minimum hardware requirements:

To ensure that the system meets these requirements:

  1. To determine the physical RAM size, enter the following command:

    # grep "Physical:" /var/adm/syslog/syslog.log
    
    

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

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

    # /usr/sbin/swapinfo -a
    
    

    If necessary, refer to the 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 the following command:

    # bdf /tmp
    
    

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

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

    • 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 the following command:

    # bdf
    
    

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

    Installation Type Requirement for Software Files
    Instant Client 96 MB
    Administrator 1.9 GB
    Runtime 1.5 GB
    Custom (maximum) 2.0 GB


    Note:

    If you want to configure only the Instant Client Light component of Instant Client, you need 34 MB of disk space to store the related files. To configure Instant Client Light, refer to the "Configuring Instant Client Light" section .

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

    # /bin/getconf KERNEL_BITS
    

    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.

2.3 Checking the Software Requirements

Depending on the products that you intend to install, verify that the following software is installed on the system. The procedure following the table describes how to verify whether these requirements are addressed.

Item Requirement
Operating system Operating system version:

HP-UX 11i V1 (11.11) PA-RISC

HP-UX 11i V2 (11.23)

Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, Oracle XML Developer's Kit (XDK), GNU Compiler Collection (GCC) HP C/ANSI C Compiler (B.11.11.12):

HP aCC Compiler (A.03.60):

GCC compiler gcc 3.4.0 (64-Bit) for 11i V1 and 11i V2

Note: The gcc compiler is supported only for PL/SQL native compilation.

Pro*COBOL Micro Focus Server Express 4.0 SP1 or later

AcuCobol 6.1

Pro*FORTRAN HP-UX 11i V1 (11.11):

HP FORTRAN 90 Compiler (B.11.11.90):

FORTRAN90

HP-UX 11i V2 (11.23):

HP FORTRAN 90 Compiler (B.11.23.20):

FORTRAN90
Oracle JDBC/OCI Drivers You can use the following optional Java SDK versions with the Oracle JDBC/OCI drivers, however they are not required for the installation:
  • Java SDK 1.3.1.16 with the JNDI extension

  • Java SDK 1.2.2.09

  • Java SDK 1.4.2.08

  • Java SDK 5.0

Note: Java SDK 1.4.2 is installed with this release.



See Also:

If you plan to use GNU Compiler Collection as the primary compiler, then refer to Oracle Database Installation Guide for hp-ux PA-RISC (64-Bit) for instructions on configuring the primary compiler.

To ensure that the system meets these requirements:

  1. To determine which version of HP-UX is installed, enter the following command:

    # uname -a
    HP-UX hostname B.11.11 U 9000/800 109444686 unlimited-user license
    
    

    In this example, the version of HP-UX 11i is 11.11.

  2. To determine whether a bundle, product, or fileset is installed, enter a command similar to the following, where level is bundle, product, or fileset:

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

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

In addition, you need to verify that the following patches are installed on the system. The procedure following the table describes how to check these requirements.


Note:

There may be more recent versions of the patches listed installed on the system. If a listed patch is not installed, then determine whether a more recent version is installed before installing the version listed.

Installation Type or Product Requirement
All installations Quality Pack bundle:

HP-UX 11i Quality Pack (GOLDQPK11i), Dec 2004 or later:

GOLDQPK11i
All installations Patches for HP-UX 11i V1 (11.11):
  • PHNE_31097: ONC/NFS general release/performance patch

  • PHSS_31221: HP aC++ -AA runtime libraries (aCC A.03.60)

Patches for HP-UX 11i V2 (11.23):

  • PHSS_31849: linker + fdp cumulative patch

  • PHSS_31852: aC++ Runtime (PA A.03.61)

All installations Patches for JDK on HP-UX 11i V1 (11.11):
  • PHSS_30970: ld(1) and linker tools cumulative patch

Note: Refer to the following Web site for information about additional patches that may be required by JDK 1.4.2:

http://www.hp.com/products1/unix/java/patches/index.html
Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, Oracle XML Developer's Kit (XDK) Patches for HP-UX 11i V1 (11.11):
  • PHSS_32508: HP aC++ Compiler (A.03.63)

  • PHSS_32509: ANSI C compiler B.11.11.12 cumulative patch

  • PHSS_32510: +O4/PBO Compiler B.11.11.12 cumulative patch

Patches for HP-UX 11i V2 (11.23):

  • PHSS_32511: HP aC++ Compiler (A.03.63)

  • PHSS_32512: ANSI C compiler B.11.11.12 cumulative patch

  • PHSS_32513: +O4/PBO Compiler B.11.11.12 cumulative patch


To ensure that the system meets these requirements:

  1. On PA-RISC systems only, enter the following command to determine whether the HP-UX 11i Quality Pack is installed:

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

    If the Quality Pack is not installed or if the date is before June 2003, then download the latest Quality Pack from the following Web site and install it:

    http://www.hp.com/go/softwareinfo/SUPPORT_PLUS
    
    
  2. To determine whether a patch is installed, enter a command similar to the following:

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

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

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

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

    http://itresourcecenter.hp.com
    
    

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

Creating Required Symbolic Links


Note:

This task is required only if the Motif 2.1 Development Environment package (X11MotifDevKit.MOTIF21-PRG) is not installed.

To enable you to successfully relink Oracle products after installing this software, enter the following commands to create required X library symbolic links in the /usr/lib directory:

# 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

2.3.1 Instant Client Light Requirements

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

  • Language: US English

  • Territory: Any territory that is supported by Oracle

  • Character sets:

    • Single byte

      • US7ASCII

      • WE8DEC

    • Unicode

      • UTF8

      • AL16UTF16

      • AL32UTF8

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

2.4 Creating Required Operating System 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 operating system group and user:

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.


Note:

The following sections describe how to create local users and groups. As an alternative to creating local users and groups, you could create the appropriate users and groups in a directory service, for example, Network Information Services (NIS). For information about using directory services, contact your system administrator or refer to your operating system documentation.

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

2.4.1 Creating the Oracle Inventory Group

You must create the Oracle Inventory group if it does not already exist. The following subsections 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

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 and the path of the Oracle Inventory directory.

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

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

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

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

The inst_group parameter shows the name of the Oracle Inventory group, oinstall.

Creating the Oracle Inventory Group

If the oraInst.loc file does not exist, then create the Oracle Inventory group by entering the following command:

# /usr/sbin/groupadd oinstall

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

2.4.2.1 Determining Whether an Oracle Software Owner User Exists

To determine whether an Oracle software owner user named oracle exists, enter the following command:

# id oracle

If the oracle user exists, then the output from this command is similar to the following:

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

If the user exists, then determine whether you want to use the existing user or create another oracle user. If you want to use the existing user, then ensure that the user's primary group is the Oracle Inventory group. Refer to one of the following sections for more information:


Note:

If necessary, contact your system administrator before using or modifying an existing user.

2.4.2.2 Creating an Oracle Software Owner User

If the Oracle software owner user does not exist or if you require a new Oracle software owner user, then create it as follows. In the following procedure, use the user name oracle unless a user with that name already exists.

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

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

    In this command:

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

    • The -G option specifies optional secondary groups, For example, dba

  2. Set the password of the oracle user:

    # passwd oracle
    
    

Refer to the "Identifying Required Software Directories" section to continue.

2.4.2.3 Modifying an Oracle Software Owner User

If the oracle user exists, but its primary group is not oinstall, then enter a command similar to the following to modify it. Specify the primary group using the -g option and any required secondary group using the -G option:

# /usr/sbin/usermod -g oinstall -G dba oracle

2.5 Identifying Required Software Directories

You must identify or create the following directories for the Oracle software:

2.5.1 Oracle Base Directory

The Oracle base directory is a top-level directory for Oracle software installations. It is analogous to the C:\Oracle directory used for Oracle software installations on Microsoft Windows systems. On HP-UX 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, such as /oracle or /opt/oracle.

  • oracle_sw_owner is the operating system 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 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
/opt/oracle/app/oracle

The following sections describe how to identify existing Oracle base directories that may be suitable for your 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 by, and shared by, all Oracle software installations on a single system. The first time you install Oracle software on a system, Oracle Universal Installer prompts you to specify the path to this directory. then Oracle recommends that you choose the following path:

oracle_base/oraInventory

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


Note:

All Oracle software installations rely on this directory. Ensure that you back it up regularly.

Do not delete this directory unless you have completely removed all Oracle software from the system.


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

2.6 Identifying or Creating an Oracle Base Directory

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


Note:

You can choose to create an Oracle base directory, even if other Oracle base directories exist on the system.

2.6.1 Identifying an Existing Oracle Base Directory

Existing Oracle base directories may not have paths that comply with 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 /var/opt/oracle/oraInst.loc
    
    

    If the oraInst.loc file exists, then 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.

  • 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/10.2.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, 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.

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 if you want to create an Oracle base directory, then 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. Use the bdf command 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:

  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, if the mount point you identify is /u01 and oracle is the user name of the Oracle software owner, then the recommended Oracle base directory path is as follows:

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

2.7 Configuring the oracle User's Environment

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

To set the oracle user's environment:

  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 fully_qualified_remote_host_name
    
    

    For example:

    $ xhost somehost.us.acme.com
    
    
  3. If you are not already logged in to the system where you want to install the software, then log in to that system as the oracle user.

  4. If you are not logged in as the oracle user, then 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:

    • C shell (csh or tcsh):

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

    umask 022
    
    
  8. If the ORACLE_SID, ORACLE_HOME, or ORACLE_BASE environment variable is set in the file, then 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:

      $ . ./.bash_profile
      
      
    • Bourne or Korn shell:

      $ . ./.profile
      
      
    • C shell:

      % source ./.login
      
      
  11. If you are not installing the software on the local system, then 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 that you want to use to display Oracle Universal Installer (your workstation or PC).

  12. If you determined that the /tmp directory has less than 400 MB of free disk space, then 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 bdf command 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 that 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. Enter the following commands 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, then Oracle Universal Installer uses the value that it specifies as the default path for the Oracle home directory. However, if you set the ORACLE_BASE environment variable, then Oracle recommends that you unset the ORACLE_HOME environment variable and choose the default path suggested by Oracle Universal Installer.

  15. 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.