2 Pre-installation Tasks

Checking the Software Requirements on AIX

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

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.

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

X11.motif.lib

mqm.Client.Bnd
mqm.Server.Bnd

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.

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.

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 determine whether a PTF is installed, enter a command similar to the following:

   # lslpp -l -B U489726 U485561 ...
   
   

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

   https://techsupport.services.ibm.com/server/aix.fdc
   
   

3. If you require a CSD for WebSphere MQ, see the following Web site for download and installation information:

   http://www.ibm.com/software/integration/mqfamily/support/summary/aix.html
   
   

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

Checking the Software Requirements on HP-UX

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

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.

X11MotifDevKit

MQSERIES.MQM-CL-HPUX
MQSERIES.MQM-SERVER

C-ANSI-C

ACXX

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

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 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, you must install it. See your operating system or software documentation for information about installing products.

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.

GOLDAPPS11i
GOLDBASE11i

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

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

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

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

3. If you require a CSD for WebSphere MQ, see the following Web site for download and installation information:

   http://www.ibm.com/software/integration/mqfamily/support/summary/hpx.html
   

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 Groups and User" section.

Checking the Software Requirements on Linux

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

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.

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

MQSeriesClient
MQSeriesServer
MQSeriesRuntime

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.

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.

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. If you require a CSD for WebSphere MQ, see the following Web site for download and installation information:

   http://www.ibm.com/software/integration/mqfamily/support/summary/lin.html
   
   

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

Checking the Software Requirements on Solaris

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

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.

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

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

mqm

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.

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.

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. If you require a CSD for WebSphere MQ, see the following Web site for download and installation information:

   http://www.ibm.com/software/integration/mqfamily/support/summary/sun.html
   
   

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

Checking the Software Requirements on Tru64 UNIX

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

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.

OSFCMPLRS
OSFLIBA
OSFPGMR
OSFSER
OSFX11

DCECDS
DECRTS
DCESEC

OSFXDEVX
OSFXINCLUDE
OSFXLIBA

MQS_CLIENT
MQS_SERVER

MQS_MQJAVA

DTCCMPLR

CXXBASE
CXXLIB
CXXOLD

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

   If necessary, install the required software subset. If you require the Compaq C Compiler V6.5-207 (dtk), you can download it from the following Web site:

   http://www.tru64unix.compaq.com/dtk/
   
   

4. If you intend to use Oracle Messaging Gateway and require MQSeries classes for Java and MQSeries classes for Java Message Service (SupportPac MA88), download it from the following Web site:

   http://www.ibm.com/software/integration/support/supportpacs/individual/ma88.html
   

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.

T64V51BB22AS0002-20030415

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

If you require a CSD for MQSeries, see the following Web site for download and installation information:

http://www.ibm.com/software/integration/mqfamily/support/summary/dig.html

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.

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

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
  
  

Creating the OSDBA Group

You must create an OSDBA group in the following circumstances:

• An OSDBA group does not exist, for example, if this is the first installation of Oracle Database software on the system

• An OSBDA group exists, but you want to give a different group of UNIX users database administrative privileges in a new Oracle installation

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

• AIX:

  1. Enter the following command:

     # smit security
     
     

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

  3. Press F10 to exit.

• Other operating systems:

  Enter the following command to create the dba group:

  # /usr/sbin/groupadd dba
  

Creating an OSOPER Group (Optional)

Create an OSOPER group only if you want to identify a group of UNIX users with a limited set of database administrative privileges (SYSOPER operator privileges). For most installations, it is sufficient to create only the OSDBA group. If you want to use an OSOPER group, you must create it in the following circumstances:

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

• If an OSOPER group exists, but you want to give a different group of UNIX users database operator privileges in a new Oracle installation

If you require an new OSOPER group, create it as follows, depending on your operating system. In the following procedure, use the group name oper unless a group with that name already exists.

• AIX:

  1. Enter the following command:

     # smit security
     
     

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

  3. Press F10 to exit.

• Other operating systems:

  Enter the following command to create the oper group:

  # /usr/sbin/groupadd oper
  
  

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, with different group membership, to give database administrative privileges to those groups in a new Oracle Database installation

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 and that it is a member of the appropriate OSDBA and OSOPER groups. See one of the following sections for more information:

• If you want to use the existing Oracle software owner user, and the user’s primary group is the Oracle Inventory group, see one of the following sections:

  • HP-UX Only: Creating an Unprivileged User

  • Verifying That the UNIX User nobody Exists

• To modify an existing user, see the "Modify an Existing Oracle Software Owner User" section.

• To create a new user, see the following section.

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 the OSDBA group and if required, the OSOPER group, for example dba or dba,oper.

     
     

     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[,oper] 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 the secondary groups, which must include the OSDBA group and if required, the OSOPER group, for example dba or dba,oper

  2. Set the password of the oracle user:

     # passwd oracle
     
     

See one of the following sections to continue:

• HP-UX Only: Creating an Unprivileged User

• Verifying That the UNIX User nobody Exists

If the oracle user exists, but its primary group is not oinstall or it is not a member of the appropriate OSDBA or OSOPER groups, 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 the secondary groups, for example dba and oper.

  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[,oper] oracle
  
  

HP-UX Only: Creating an Unprivileged User

You must create an new unprivileged local user to own the extjob executable. You can use any user name for this user, but this document uses the name extjob. To create the extjob user, enter the following command on all cluster nodes:

# /usr/sbin/useradd extjob

To continue, see the "HP-UX Only: Grant Privileges to the OSDBA Group" section.

Verifying That the UNIX User nobody Exists

Before installing the software, verify that the UNIX user nobody exists on the system:

1. To determine whether the user exists, enter the following command:

   # id nobody
   
   

   If this command displays information about the nobody user, you do not have to create that user.

2. If the nobody user does not exist, enter the one of the following commands to create it:

   • AIX:

     # smit security
     
     

     Specify the appropriate options to create an unprivileged nobody user, then press F10 to exit.

   • Other operating systems:

     # /usr/sbin/useradd nobody
     
     

HP-UX Only: Grant Privileges to the OSDBA Group

To enhance the performance of the software on HP-UX systems, you must grant several system privileges to the OSDBA group. Complete the following steps if you are installing the software on HP-UX:

1. Using any text editor, open the /etc/privgroup file, or create it if necessary.

2. Add or edit the following line, which begins with the name of the OSDBA group, specifying the privileges MLOCK, RTPRIO, and RTSCHED, that you want to grant to this group every time the system reboots:

   dba MLOCK RTPRIO RTSCHED
   
   

3. Save the file and exit from the text editor.

4. Enter the following command to grant the privileges to the OSDBA group:

   # /usr/sbin/setprivgrp -f /etc/privgroup
   
   

5. Enter the following command to verify that the privileges are set correctly:

   # /usr/sbin/getprivgrp dba
   
   

Configuring Shell Limits and System Configuration Parameters on AIX

On AIX systems, you do not need to configure kernel parameters. However, Oracle recommends that you set shell limits and system configuration parameters as described in this section.

Verify that the shell limits shown in the following table are set to the values shown. The procedure following the table describes how to verify and set the values.

To view the current value specified for these shell limits, and to change them if necessary, follow these steps:

1. Enter the following command:

   # smit chuser
   
   

2. In the User NAME field, enter the user name of the Oracle software owner, for example oracle.

3. Scroll down the list and verify that the value shown for the soft limits listed in the previous table is -1.

   If necessary, edit the existing value.

4. When you have finished making changes, press F10 to exit.

Verify that the maximum number of processes allowed per user is set to 2048 or greater. The procedure following the table describes how to verify and set the value.

1. Enter the following command:

   # smit chgsys
   
   

2. Verify that the value shown for Maximum number of PROCESSES allowed per user is greater than or equal to 2048.

   If necessary, edit the existing value.

3. When you have finished making changes, press F10 to exit.

Configuring Kernel Parameters on HP-UX

Verify that the kernel parameters shown in the following table are set either to the formula shown, or to values greater than or equal to the recommended value shown. The procedure following the table describes how to verify and set the values.