Skip Headers

Oracle® Database Companion CD Installation Guide
10g Release 1 (10.1) for UNIX Systems: AIX-Based Systems, hp HP-UX PA-RISC (64-bit), hp Tru64 UNIX, Linux x86, and Solaris Operating System (SPARC)
Part No. B10886-02
  Go To Table Of Contents
Contents
Go To Index
Index

Previous Next  

3 Pre-installation Tasks for Installations in a New Oracle Home

This chapter describes the tasks that you must complete before you start the Oracle Universal Installer and install Oracle products in a new Oracle home. It includes information about the following tasks:

3.1 Installation Considerations

Review the following sections before starting the installation.


Hardware and Software Certification

The platform-specific hardware and software requirements included in this installation guide were current at the time this guide was published. However, because new platforms and operating system software versions might be certified after this guide is published, review the certification matrix on the OracleMetaLink Web site for the most up-to-date list of certified hardware platforms and operating system versions. The OracleMetaLink Web site is available at the following URL:

http://metalink.oracle.com

If you do not have a current Oracle Support Services contract, you can access the same information from the following Web site:

http://otn.oracle.com/support/metalink/content.html

Installing Oracle Database 10g Companion Products

The tasks that you must complete when installing Oracle Database 10g Companion Products in a new Oracle home depend on products that you want to install. Before installing the products available through the Oracle Database 10g Companion Products installation type, make sure that your system meets the requirements described in the following sections, depending on the products that you want to install:


Note:

If you install Oracle HTML DB in a new Oracle home, you must install Oracle HTTP Server at the same time.


See Also:

To install Oracle HTML DB in an existing Oracle HTTP Server Oracle home, see Chapter 2, " Pre-installation Tasks for Installations in an Existing Oracle Home".

3.2 Pre-installation Tasks for Oracle HTTP Server

Perform the tasks in the following sections before installing Oracle HTTP Server.

3.2.1 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:


Note:

Unless you intend to complete a silent 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.

  • 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:
      
      

3.2.2 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 free disk space in the /tmp directory

  • The amount of free disk space shown in the following table, depending on your platform and the products that you want to install:

    Products for Installation Platform Disk Space Required
    Oracle HTTP Server AIX, HP-UX, Tru64 UNIX 700 MB
    Linux, Solaris 400 MB
    Oracle HTTP Server and Oracle HTML DB AIX, HP-UX, Tru64 UNIX 1050 MB
    Linux, Solaris 700 MB

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

3.2.3 Check the Software Requirements

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

3.2.3.1 Checking the Software Requirements on AIX

Check that the required software and patches are installed on the system.


Check for Required Software

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 check these requirements.

Installation Type or Product Requirement
All installations Operating system version and maintenance level:

AIX 5L version 5.2, Maintenance Level 1 or higher

Operating system filesets:
bos.adt.base
bos.adt.lib
bos.adt.libm
bos.perf.libperfstat
bos.perf.perfstat
bos.perf.proctools

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

  1. To determine which version of AIX is installed, enter the following command:

    # oslevel -r
    
    

    If the operating system version is lower than AIX 5.2.0.0 Maintenance Level 1 (5200-01), upgrade your operating system to this level. AIX 5L version 5.2 maintenance packages are available from the following Web site:

    https://techsupport.services.ibm.com/server/aix.fdc
    
    
  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
    
    

    If a fileset is not installed and committed, then install it. See your operating system or software documentation for information about installing filesets.


Check for Required Patches

Depending on the products that you intend to install, verify that the following patches are installed on the system. The procedure following the table describes how to check these requirements.

Installation Type or Product Requirement
All installations Authorized Problem Analysis Reports (APARs):
  • IY43980: libperfstat.h not ANSI-compliant

  • IY44810: DSI IN BMRECYCLE

  • IY45462: Definition of isnan() in math.h incorrect

  • IY45707: J2 READAAHEAD/CIO INTERACTION

  • IY46214: dropping partial connections leaves them on so_q0

  • IY46605: exec of 32 bit application can fail on 64 bit kernel

  • IY48525: SDK 1.4.1 32-BIT SR1: CA141-20030930

  • IY51801: race condition in aio_nwait_timeout


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

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

    # /usr/sbin/instfix -i -k "IY22854 IY26778 ..."
    
    

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

    https://techsupport.services.ibm.com/server/aix.fdc
    
    
  2. To continue completing pre-installation tasks, go to the "Create Required UNIX Group and User" section.

3.2.3.2 Checking the Software Requirements on HP-UX

Check that the required software and patches are installed on the system.


Check for Required Software

Verify that the following software is installed on the system. The procedure following the table describes how to check these requirements.

Installation Type or Product Requirement
All installations Operating system version:

HP-UX 11i (11.11) PA-RISC

Quality Pack bundle:

HP-UX 11i Quality Pack (GOLDQPK11i), June 2003 or later:

GOLDAPPS11i
GOLDBASE11i

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

  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 the HP-UX 11i Quality Pack is installed, enter the following command:

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

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

    http://www.software.hp.com/SUPPORT_PLUS/qpk.html
    
    

Check for Required Patches

Depending on the products that you intend to install, verify that the following patches are installed on the system. The procedure following the table describes how to check these requirements.

Installation Type or Product Requirement
All installations Patches for HP-UX 11i (11.11):
  • PHCO_28123: cumulative SAM patch

  • PHKL_29198: Psets Enablement Patch; top(1)

  • PHNE_28476: Cumulative STREAMS Patch

  • PHNE_28923: LAN product cumulative patch

  • PHSS_28871: ld(1) and linker tools cumulative patch

  • PHSS_28880: HP aC++ -AA runtime libraries (aCC A.03.50)

All installations Patches for JDK on HP-UX 11i (11.11):
  • PHCO_26331: mountall cumulative patch, Dev IDs enabler

  • PHCO_29109: Pthread enhancement and fixes

  • PHKL_25468: eventport (/dev/poll) pseudo driver

  • PHKL_25842: Thread Abort

  • PHKL_25993: thread nostop for NFS, rlimit, Ufalloc fix

  • PHKL_25994: Thread NOSTOP, Psets Enablement, Ufalloc

  • PHKL_25995: ufalloc;VxFS3.5;SPP fragmentation

  • PHKL_26468: Shared synchronization performance support

  • PHKL_28489: copyin EFAULT, LDCD access type

Note: See the following Web site for information about additional patches that might be required by JDK 1.4.2:

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

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, 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, download and install that version.


Create Required Symbolic Links

Note:

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

To allow 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

To continue completing pre-installation tasks, go to the "Create Required UNIX Group and User" section.

3.2.3.3 Checking the Software Requirements on Linux

Check that the required software and patches are installed on the system.


Check for Required Software

Verify that the following software is installed on the system. The procedure following the table describes how to check these requirements.

Installation Type or Product Requirement
All installations One of the following operating system versions:
  • Red Hat Enterprise Linux AS/ES 2.1 or 3 (x86)

  • UnitedLinux 1.0, service pack 3 or higher (x86)

The following packages (or higher versions) must be installed:

All distributions:

make-3.79
binutils-2.11.90.0.8-12

Red Hat Enterprise Linux 2.1 (x86):

gcc-2.96.108.1
openmotif-2.1.30-11

Red Hat Enterprise Linux 3:

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 

UnitedLinux 1.0 (x86):

gcc-3.2.2-38
openmotif-2.2.2-124

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

  1. To determine which distribution and version of Linux is installed, enter the following command:

    # cat /etc/issue
    
    

    Note:

    Only the distributions and versions listed in the previous table are supported. Do not install the software on other versions of Linux.

  2. On UnitedLinux 1.0 systems only, enter the following command to determine whether Service Pack 3 is installed:

    # uname -r
    2.4.21-138-default
    
    

    This command shows the kernel version (2.4.21-138) and type (default). If the kernel version is less than 2.4.21-138, contact your UnitedLinux vendor for information about obtaining and installing Service Pack 3.

  3. To determine whether the required packages are installed, enter a command similar to the following:

    # rpm -q package_name
    
    

    If a package is not installed, install it from your Linux distribution media.


Check for Required Patches

Depending on the products that you intend to install, verify that the following patches are installed on the system. The procedure following the table describes how to check these requirements.

Installation Type or Product Requirement
All installations Red Hat Enterprise Linux 2.1 (x86) errata:
  • RHSA-2003:195-06
    Updated kernel addresses security vulnerabilities

  • RHSA-2003:022-09
    Updated glibc packages fix vulnerabilities in resolver


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

  1. On Red Hat Enterprise Linux 2.1 systems only, follow these steps:

    1. To determine whether kernel update RHSA-2003:195-06 or later is installed, enter the following command:

      # uname -r
      2.4.9-e.25
      
      

      This command shows the kernel version (2.4.9) and errata level (e.25). If the errata level is less than 25, install the latest kernel update. See the following Web site for information about kernel update RHSA-2003:195-06:

      https://rhn.redhat.com/errata/RHSA-2003-195.html
      
      
    2. To determine whether fix RHSA-2003:022-09 is installed, enter the following command:

      # rpm -q glibc
      glibc-2.2.4-31
      
      

      If the version shown is less than 2.2.4-31, see the following Web site for information about fix RHSA-2003:022-09:

      https://rhn.redhat.com/errata/RHSA-2003-022.html
      
      
  2. To continue completing pre-installation tasks, go to the "Create Required UNIX Group and User" section.

3.2.3.4 Checking the Software Requirements on Solaris

Check that the required software and patches are installed on the system.


Check for Required Software

Verify that the following software is installed on the system. The procedure following the table describes how to check these requirements.

Installation Type or Product Requirement
All installations Operating system versions:

Solaris 8 or Solaris 9, 64-bit

Operating system packages:
SUNWarc
SUNWbtool
SUNWhea
SUNWlibm
SUNWlibms
SUNWsprot
SUNWsprox
SUNWtoo
SUNWi1of
SUNWi1cs
SUNWi15cs
SUNWxwfnt

Note: You might also require additional font packages for Java, depending on your locale. See the following Web site for more information:

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

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

  1. To determine which version of Solaris is installed, enter the following command:

    # uname -r
    
    

    If the operating system version is lower than Solaris 8 (5.8), upgrade your operating system to this level.

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

    # pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprot \ SUNWsprox SUNWtoo SUNWi1of SUNWi1cs SUNWi15cs SUNWxwfnt
    
    

    If a package is not installed, then install it. See your operating system or software documentation for information about installing packages.


Check for Required Patches

Depending on the products that you intend to install, verify that the following patches are installed on the system. The procedure following the table describes how to check these requirements.


Note:

The patch versions shown in the following table are minimum versions. Higher versions of the same patches are also supported.

Installation Type or Product Requirement
All installations Patches for Solaris 8:

All of the patches included in the J2SE Patch Cluster for Solaris 8:

  • 108528-23, SunOS 5.8: kernel update patch

  • 108652-66, X11 6.4.1: Xsun patch

  • 108773-18, SunOS 5.8: IIIM and X I/O Method patch

  • 108921-16, CDE 1.4: dtwm patch

  • 108940-53, Motif 1.2.7 and 2.1.1: Runtime lib. patch for Solaris 8

  • 108987-13, SunOS 5.8: Patch for patchadd and patchrm

  • 108989-02, /usr/kernel/sys/acctctl & /.../exacctsys patch

  • 108993-18, SunOS 5.8: LDAP2 client, libc, ... lib. patch

  • 109147-24, SunOS 5.8: linker patch

  • 110386-03, SunOS 5.8: RBAC Feature Patch

  • 111023-02, SunOS 5.8: /kernel/fs/mntfs and ... sparcv9/mntfs

  • 111111-03, SunOS 5.8: /usr/bin/nawk patch

  • 111308-03, SunOS 5.8: /usr/lib/libmtmalloc.so.1 patch

  • 111310-01, SunOS 5.8: /usr/lib/libdhcpagent.so.1 patch

  • 112396-02, SunOS 5.8: /usr/bin/fgrep patch

The following additional patches:

  • 111721-04, SunOS 5.8: Math Library (libm) patch

  • 112003-03, SunOS 5.8: Unable to load fontset ... iso-1 or iso-15

  • 112138-01, SunOS 5.8: usr/bin/domainname patch

All installations Patches for Solaris 9:
  • 112233-11: SunOS 5.9: Kernel Patch

  • 111722-04: SunOS 5.9: Math Library (libm) patch


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

  1. To determine whether an operating system patch is installed, enter a command similar to the following:

    # /usr/sbin/patchadd -p | grep patch_number
    
    

    If an operating system patch is not installed, download it from the following Web site and install it:

    http://sunsolve.sun.com
    
    
  2. To continue completing pre-installation tasks, go to the "Create Required UNIX Group and User" section.

3.2.3.5 Checking the Software Requirements on Tru64 UNIX

Check that the required software and patches are installed on the system.


Check for Required Software

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 check these requirements.

Installation Type or Product Requirement
All installations Operating system version:

HP Tru64 UNIX V5.1B

Software Development Kit (SDK) v 1.4.2 for the Tru64 UNIX Operating System for the Java Platform (JDK 1.4.2)
Operating system subsets:
OSFCMPLRS
OSFLIBA
OSFPGMR
OSFSER
OSFX11

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

  1. To determine which version of Tru64 UNIX is installed, enter the following command:

    # /usr/sbin/sizer -v
    Compaq Tru64 UNIX V5.1B (Rev. 2650); Mon Nov  3 10:13:28 PST 200 
    
    

    In this example, the version shown is V5.1B. If necessary, see your operating system documentation for information about upgrading the operating system.

  2. To determine whether Java SDK 1.4.2 is installed, enter the following command:

    # /usr/sbin/setld -i JAVA142 | more
    
    

    If Java SDK 1.4.2 is installed, this command displays the paths to all of the installed files. Note the path of the Java home directory. You must specify this value during the installation. The default path is:

    /usr/opt/java142
    
    

    If this command returns the message Unknown subset, Java SDK 1.4.2 is not installed. Download the Java SDK 1.4.2.01 or higher from the following Web site and install it:

    http://www.compaq.com/java/download/index.html
    
    
  3. To determine whether the required software subsets are installed, enter one of the following commands:

    • To view the list of all software subsets installed on the system, enter the following command:

      # /usr/sbin/setld -i | more
      
      
    • To determine whether a particular software subset is installed, enter a command similar to the following:

      # /usr/sbin/setld -i | grep subsetname
      
      

Check for Required Patches

Depending on the products that you intend to install, verify that the following patches are installed on the system. The procedure following the table describes how to check these requirements.

Installation Type or Product Requirement
All installations Tru64 UNIX V5.1B Patch Kit 2 or higher:
T64V51BB22AS0002-20030415

HP Tru64 UNIX 5.1B PK2 BL22 Fixes for AdvFS Panic in _OtsMove; and Possible Memory Corruption:

T64KIT0020879-V51BB22-E-20031125

To determine whether the required patch kits are installed, enter the following command:

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

If this command does not display the identifiers shown in the previous table for the required patch kits (or the identifier for a higher patch kit level), download the latest patch kit from the following Web site and install it (registration is required to access this Web site):

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

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


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 see your operating system documentation.

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


Determine Whether the Oracle Inventory Group Exists

When you install Oracle software on the system for the first time, the 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:

  • AIX or 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 inst_group parameter shows the name of the Oracle Inventory group (oinstall).


Create the Oracle Inventory Group

If the oraInst.loc file does not exist, create the Oracle Inventory group as follows, depending on your operating system:

  • AIX:

    1. Enter the following command:

      # smit security
      
      
    2. Choose the appropriate menu items to create the oinstall group.

    3. Press F10 to exit.

  • Other operating systems:

    Enter the following command to create the oinstall group:

    # /usr/sbin/groupadd oinstall
    
    

3.2.6 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 UNIX user


Determine Whether an Existing Oracle Software Owner User Exists

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

  • Solaris:

    # id -a oracle
    
    
  • Other operating systems:

    # id oracle
    
    

If the oracle user exists, 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, determine whether you want to use the existing user or create a new user. If you want to use the existing user, ensure that the user’s primary group is the Oracle Inventory group.

See one of the following sections for more information:


Note:

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


Create a New Oracle Software Owner User

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

  • AIX:

    1. Enter the following command:

      # smit security
      
      
    2. Choose the appropriate menu items to create the oracle user, specifying the following information:

      • In the Primary GROUP field, specify the Oracle Inventory group, for example oinstall.

      • In the Group SET field, specify any required secondary groups.


      Note:

      The UID for the oracle user must be less than 65536.

    3. Press F10 to exit.

    4. Set the password of the oracle user:

      # passwd oracle
      
      
  • Other operating systems:

    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

    2. Set the password of the oracle user:

      # passwd oracle
      
      

See the "Identify Required Software Directories" section to continue.


Modify an Existing Oracle Software Owner User

If the oracle user exists, but its primary group is not oinstall, you can modify it as follows depending on your operating system:

  • AIX:

    1. Enter the following command:

      # smit security
      
      
    2. Choose the appropriate menu items to modify the oracle user.

    3. In the Primary GROUP field, specify the Oracle Inventory group, for example oinstall.

    4. In the Group SET field, specify any required secondary groups.

    5. Press F10 to exit.

  • Other operating systems:

    Enter a command similar to the following, specifying the primary group using the -g option and any required secondary groups using the -G option:

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

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


Oracle Base Directory

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.


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


Note:

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

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



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 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/companion_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.

3.2.8 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:


Note:

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


Identifying an Existing 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.


Creating a New Oracle Base Directory

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.

3.2.9 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 and ORACLE_HOME specifies the directory where you want to install the software. If you already have a companion_1 directory, you can specify a higher number.

  14. Enter the following command to ensure that the TNS_ADMIN environment variable is not set:

    • Bourne, Bash, or Korn shell:

      $ unset TNS_ADMIN
      
      
    • C shell:

      % unsetenv TNS_ADMIN
      
      
  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.

3.3 Pre-installation Tasks for Oracle HTML DB

Perform the tasks in the following sections before installing Oracle HTML DB.

3.3.1 Check the Oracle Database Installation

Before installing Oracle HTML DB, identify the Oracle database that you want to use with Oracle HTML DB. The database must be Oracle9i release 9.2.0.3 or higher. The database can be on a different system from the system where you are installing Oracle HTML DB.

3.3.2 Check for Oracle XML DB

Oracle XML DB must be installed in the database that you want to use.

If you are using a preconfigured database created either during an installation or by the Database Configuration Assistant (DBCA), Oracle XML DB is already installed and configured. For information about manually adding Oracle XML DB to an existing database, see the Oracle XML DB Developer’s Guide.

3.3.3 Identify Database Information

During the installation, you must specify the following information about the database:

  • The host name of the database system

  • The port number of the Oracle Net listener

  • The service name of the database

  • The password of the SYS user

Make sure that you have this information before starting the installation.