2 Pre-Installation Tasks

2.1 Understanding and Using Cluster Verification Utility

Cluster Verification Utility (CVU) is a tool that performs system checks. This guide provides CVU commands to assist you with confirming that your system is properly configured for Oracle Clusterware and Oracle Real Application Clusters installation.

This section describes the following topics:

• Entering Cluster Verification Utility Commands

• Using CVU to Determine if Installation Prerequisites are Complete

• Using the Cluster Verification Utility Help

• Using Cluster Verification Utility with Oracle 10g Release 1

• Verbose Mode and "Unknown" Output

$ /mountpoint/crs/Disk1/cluvfy/
$ ./runcluvfy.sh options

$ /dev/dvdrom/crs/Disk1/cluvfy/
$ ./runcluvfy.sh comp nodereach -n node1,node2 -verbose

/$ ./runcluvfy.sh stage -pre crsinst -n node_list 

$ cd /dev/dvdrom/crs/Disk1/cluvfy/
$ ./runcluvfy.sh stage -pre crsinst -n node1,node2,node3

$ ./runcluvfy.sh stage -pre crsinst -n node1,node2,node3 -r 10gR1

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

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

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

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

     $ xhost + hostname
     
     

     The hostname is the name of the local host.

  3. If you are not installing the software on the local system, then use the ssh, rlogin, or telnet command to connect to the system where you want to install the software:

     $ telnet remote_host
     
     

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

     $ su - root
     password:
     #
     
     

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

  Note:

  If necessary, refer to 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, then enter the following command to switch user to root:

     $ su - root
     password:
     #
     

2.3 Creating Required Operating System Groups 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 several operating system groups and an operating system user account.

The following operating system groups and user are required if you are installing Oracle Database:

• The OSDBA group (typically, dba)

  You must create this group the first time you install Oracle Database software on the system. This group identifies operating system user accounts that have database administrative privileges (the SYSDBA privilege). The default name for this group is dba.

  If you want to specify a group name other than the default dba group, then you must choose the Custom installation type to install the software or start Oracle Universal Installer as a user that is not a member of this group. In this case, Oracle Universal Installer prompts you to specify the name of this group.

• The OSOPER group (typically, oper)

  This is an optional group. Create this group if you want a separate group of operating system users to have a limited set of database administrative privileges (the SYSOPER privilege). By default, members of the OSDBA group also have the SYSOPER privilege.

  If you want to specify a separate OSOPER group, other than the default dba group, then you must choose the Custom installation type to install the software or start Oracle Universal Installer as a user that is not a member of the dba group. In this case, Oracle Universal Installer prompts you to specify the name of this group. The usual name chosen for this group is oper.

• An unprivileged user

  Verify that the unprivileged user nobody exists on the system. The nobody user must own the external jobs (extjob) executable after the installation.

The following operating system group and user are required for all installations:

• The Oracle Inventory group (typically, 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, then the existing Oracle Inventory group must be the primary group of the operating system 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 (typically, 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. It must also have the OSDBA and OSOPER groups as secondary groups. In Oracle documentation, when this user account is referred to, it is called the oracle 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, OSDBA groups, and OSOPER groups (other than oracle, dba, and oper) for separate installations. By using different groups for different installations, members of these different groups have DBA privileges only on the associated databases rather than on all databases on the system.

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

• Creating the Oracle Inventory Group

• Creating the OSDBA Group

• Creating an OSOPER Group (Optional)

• Creating the Oracle Software Owner User

• Verifying that the User nobody Exists

• Creating Identical Users and Groups on Other Cluster Nodes

• Configuring SSH on All Cluster Nodes

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

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

# /usr/sbin/groupadd oinstall

# /usr/sbin/groupadd dba

# /usr/sbin/groupadd oper

# id oracle

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

# /usr/sbin/usermod -g oinstall -G dba[,oper] oracle

$ ps -aef | grep sshd

$ man ssh2

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

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

• Set the DISPLAY, ORACLE_BASE, and ORACLE_HOME environment variables in preparation for the Oracle Clusterware installation

You should also ensure that the PATH variable contains $ORACLE_HOME/bin before /usr/X11R6/bin

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

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

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

   $ xhost + hostname
   
   

   The hostname is the name of the local host.

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:

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

     % vi .bash_profile
     
     

   • 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 text editor.

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

    • Bash shell:

      $ . ./.bash_profile
      
      

    • Bourne, Bash, 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:

    Note:

    You cannot use a shared file system as the location of the temporary file directory (typically /tmp) for RAC installation. If you place /tmp on a shared file system, then the installation fails.

    1. Use the df -h 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 775 /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
         
         

2.5 Checking the Hardware Requirements

Each system must meet the following minimum hardware requirements:

• At least 1 GB of physical RAM

• Swap space equivalent to the multiple of the available RAM, as indicated in the following table:

  Available RAM	Swap Space Required
  Between 1 GB and 2 GB	1.5 times the size of RAM
  More than 2 GB	Equal to the size of RAM

  
  

• 400 MB of disk space in the /tmp directory

• Up to 4 GB of disk space for the Oracle software, depending on the installation type and platform

• 1.2 GB of disk space for a preconfigured database that uses file system storage (optional)

  Additional disk space, either on a file system or in an Automatic Storage Management disk group, is required for the flash recovery area if you choose to configure automated backups.

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

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

   # /bin/vmstat -P | grep "Total Physical Memory"
   
   

   If the size of the physical RAM installed in the system 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:

   # /sbin/swapon -s
   
   

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

   • # df -k /tmp
     
     

   This command displays disk space in 1 kilobyte blocks.

   Alternatively, with HP Tru64 version 5.1 B or later, you can use the df -h command, which displays disk space in gigabyte or megabyte blocks.

   If there is less than 400 MB of disk space available in the /tmp directory (less than 4194304 1-k blocks), then complete one of the following steps:

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

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

   • # df -h
     
     

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

   Installation Type	Requirement for Software Files (GB)
   Enterprise Edition	at least 1.5
   Standard Edition	at least 1.5
   Custom (maximum)	at least 1.5

   
   

2.6 Checking the Network Requirements

Check that you have the networking hardware and internet protocol (IP) addresses required for an Oracle Real Application Clusters installation. This section contains the following:

• Checking IP Address Requirements

• Checking Network Hardware Requirements

• Configuring the Network Requirements

• Checking Node Time Requirements

• Configuring Reliable Datagram (RDG)

http://metalink.oracle.com

2.7 Checking the Network Setup with CVU

As the oracle user, enter a command using the following syntax to verify node connectivity among all of the nodes for which your cluster is configured:

/mountpoint/crs/Disk1/cluvfy/runcluvfy.sh comp nodecon -n node_list [-verbose]

In the preceding syntax example, the variable node_list is a comma-separated list of nodes in your cluster. This command detects all the network interfaces available on the cluster nodes, and verifies the connectivity among all the nodes through the network interfaces it finds.

Select the option -verbose to receive progress updates as the CVU performs its system checks, and detailed reporting of the test results.

For example, to verify node connectivity on a two-node cluster with nodes node1 and node2, with the mountpoint /dev/dvdrom, and with updates and a summary of the verification checks the CVU performs, enter the following command:

/dev/dvdrom/crs/Disk1/cluvfy/runcluvfy.sh comp nodecon -n node1,node2 -verbose

2.8 Verifying Software Requirements

Depending on the products that you intend to install, verify that the following software is installed on the system. To check these requirements refer to the section "Checking the Software Requirements", following this section.

OSFCMPLRS
OSFLIBA
OSFPGMR
OSFSER
OSFX11

TCRBASE
TCRMIGRATE

OSFXDEVX
OSFXINCLUDE
OSFXLIBA

DTCCMPLR

CXXBASE
CXXLIB
CXXOLD

2.9 Verifying 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.

T64V51BB26AS0005-20050502

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

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

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

2.10 Configuring Kernel Subsystem Attributes

To view the current value specified for these kernel subsystem attributes, and to change them if necessary, follow these steps:

1. Log in as root, and make a copy of your existing /etc/sysconfigtab file. For example:

   # cp /etc/sysconfigtab /etc/sysconfigtab.orig
   
   

2. Using a text editor, create a stanza-formatted modification file called sysconfigmod for the /etc/sysconfigtab file, with the following contents:

   vfs:
        fifo_do_adaptive=0 
   
   

3. Using the following command, merge the contents of sysconfigmod with the existing /etc/sysconfigtab file:

   # sysconfigdb -m -f sysconfigmod
   
   

4. Use the following command syntax to confirm this change, and to determine the current values of subsystem attributes:

   # /sbin/sysconfig -q subsystem
   
   

   In the preceding syntax example, replace the variable subsystem with the name of the subsystem whose value you want to check.

   For example, to check the attribute values of the ipc subsystem, enter the following command:

   # /sbin/sysconfig -q ipc
   
   

   To check the attribute values of the proc subsystem, enter the following command:

   # /sbin/sysconfig -q proc 
   
   

   To check the attribute values of the rdg subsystem, enter the following command:

   # /sbin/sysconfig -q rdg
   
   

   Check the kernel subsystems listed in the following table:

   Note:

   Make a note of the current values and identify any values that you must change.

   Table 2-3 Required Values for HP Tru64 Kernel Subsystem Attributes

   Subsystem	Attribute	Recommended Value
   ipc	shm_max	4278190080 (4 GB minus 16 MB)
   	shm_min	1
   	shm_mni	256
   	shm_seg	256
   	ssm_threshold	Set this attribute to 0 only if the rad_gh_regions[n] or gh_chunks attributes are set in the vm subsystem. Otherwise, do not change the value.
   proc	exec_disable_arg_limit	1
   	per_proc_stack_size	8388608 (8 MB)Foot 1
   	max_per_proc_stack_size	33554432 (32 MB)Footref 1
   	per_proc_data_size	335544320 (320MB)
   	max_per_proc_data_size	335544320 (320MB)
   	max_per_proc_address_space	Equal to the size of RAM or 1073741824 (1 GB), whichever is larger.
   	per_proc_address_space	Equal to the size of RAM or 1073741824 (1 GB), whichever is larger.
   rdg	msg_size	32768
   	max_objs	5120
   	max_async_req	256
   	max_sessions	500 (or at least 20 plus the value of the PROCESSES initialization parameter for all databases on the system, if this value is higher.)
   	rdg_max_auto_msg_wires	0
   	rdg_auto_msg_wires	0
   rt	aio_task_max_num	8193
   vfs	fifo_do_adaptive	0

   
   
   ^Footnote 1 The maximum value supported by Oracle for this parameter is 512 MB.
   

   Note:

   The vfs parameter new_wire_method is obsoleted with the current patchset for HP Tru64.

5. If you must change any of the current values, then follow these steps:

   1. Create a backup copy of the /etc/sysconfigtab file. For example:

      # cp /etc/sysconfigtab /etc/sysconfigtab.mod1
      
      

   2. Using any text editor, create a stanza-formatted file similar to the following, specifying the subsystems and attributes that you want to modify:

      ipc:
           shm_max = 4278190080
           shm_min = 1
           shm_mni = 256
           shm_seg = 128
      
      proc:
           exec_disable_arg_limit = 1
           per_proc_stack_size = 8388608
           max_per_proc_stack_size = 33554432
           per_proc_data_size = 335544320
           max_per_proc_data_size = 335544320
           max_per_proc_address_space = 4294967296
           per_proc_address_space = 4294967296
      
      rdg:
        msg_size = 32768
        max_objs = 5120
        max_async_req = 256
        max_sessions = 500
        rdg_max_auto_msg_wires = 0
        rdg_auto_msg_wires = 0
      
      

   3. Enter a command similar to the following to merge the missing or modified subsystem attributes to the /etc/sysconfigtab file:

      # /sbin/sysconfigdb -m -f filename
      
      

      In this example, filename is the name of the file you created in step b.

   4. Enter the following command to restart the system:

      # /sbin/shutdown -r now
      
      

   5. When the system restarts, log in and switch user to root.

6. (Optional) If you have a db_block_size of 16 KB or greater, and you are using UDP IPC implementation, then edit the inet parameter in the /etc/sysconfigtab file to be at least the following:

   inet: udp_recvspace = 65536
   udp_sendspace = 65536
   
   

   Note:

   Default IPC for Oracle Real Application Clusters is RDG

7. Repeat this procedure on all other cluster nodes.

2.11 Checking the Hardware and Operating System Setup with CVU

As the oracle user, use the following command syntax to start Cluster Verification Utility (CVU) stage verification to check hardware and operating system setup:

/mountpoint/crs/Disk1/cluvfy/runcluvfy.sh stage –post hwos –n node_list [-verbose]

In the preceding syntax example, replace the variable node_list with the names of the nodes in your cluster, separated by commas. For example, to check the hardware and operating system of a two-node cluster with nodes node1 and node2, with the mountpoint /dev/dvdrom/ and with the option to limit the output to the test results, enter the following command:

/dev/dvdrom/crs/Disk1/cluvfy/runcluvfy.sh stage –post hwos –n node1,node2

Select the option -verbose to receive detailed reports of the test results, and progress updates about the system checks performed by Cluster Verification Utility.

2.12 Checking the Operating System Requirements Setup with CVU

As the oracle user, use the following command syntax to check if your system meets the operating system requirement pre-installation tasks:

/mountpoint/crs/Disk1/cluvfy/runcluvfy.sh comp sys -n node_list -p {crs|database} -osdba osdba_group -orainv orainv_group -verbose

In the preceding syntax example:

• The variable mountpoint is the mountpoint of the Oracle 10g Release 2 (10.2) installation media

• The variable node_list is the list of nodes in your cluster, separated by commas

• The -p flag identifies either crs or database, and indicates that checks are performed for Oracle Clusterware or Oracle Database system requirements

• The variable osdba_group is the name of your OSDBA group, typically dba

• The variable orainv_group is the name of your Oracle Inventory group, typically oinstall

You can select the option -verbose to receive progress updates as the CVU performs its system checks, and detailed reporting of the test results.

For example, to perform a system check for an Oracle Clusterware installation on a two-node cluster with nodes node1 and node2, with the OSDBA dba and Oracle inventory group oinstall, and with the media mountpoint /dev/dvdrom/, then enter the following command:

/dev/dvdrom/crs/Disk1/cluvfy/runcluvfy.sh comp sys -n node1,node2 -p crs -osdba crs -orainv oinstall

2.13 Identifying Required Software Directories

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

• Oracle Base Directory

• Oracle Inventory Directory

• Oracle Clusterware Home 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. 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 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 might 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 the Oracle base 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, Oracle Universal Installer prompts you to specify the path to this directory. If you are installing the software on a local file system, then Oracle recommends that you choose the following path:

oracle_base/oraInventory

As the Oracle base directory is located on a cluster file system, you must place the Oracle Central Inventory directory on a local file system, privately mounted on each node, so that each node has a separate copy of the central inventory.

If you specify a shared location for the Oracle Central Inventory, then each node attempts to write to the same central inventory. This is not supported.

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.

Oracle Clusterware Home Directory

The Oracle Clusterware home directory is the directory where you choose to install the software for Oracle Clusterware. You must install Oracle Clusterware in a separate home directory. When you run Oracle Universal Installer, it prompts you to specify the path to this directory, as well as a name that identifies it. Oracle recommends that you specify a path similar to the following for the Oracle Clusterware home directory:

/u01/app/oracle/product/crs

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/db_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.14 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:

• Identifying an Existing Oracle Base Directory

• Creating an Oracle Base Directory

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:

• Identifying an existing Oracle Inventory directory

  Enter the following command on all nodes in the cluster 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) on that system. 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 on all nodes in the cluster 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.

Before deciding to use an existing Oracle base directory for this installation, make sure that it satisfies the following conditions:

• It should not be on the same file system as the operating system.

• It must have an identical path on all nodes in the cluster.

• It must have at least 1.5 GB free disk space on all the nodes in the cluster

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

  # df -h oracle_base_path
  
  

  When you are configuring the oracle user's environment in the section "Creating the Oracle Clusterware Home Directory", set the ORACLE_BASE environment variable to specify the directory you choose.

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.

Creating an Oracle Base Directory

Before you create an Oracle base directory, you must identify an appropriate file system. The Oracle base directory requires at least 1.5 GB of free disk space.

To identify an appropriate file system, follow these steps:

1. Use the df -h 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.

   Note:

   The Oracle base directory must be on a cluster file system.

   The path to the Oracle base directory must be the same on all nodes.

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 to 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. If necessary, repeat the commands listed in the previous step to create the same directory on the other nodes in the cluster.

3. When you configure the oracle user's environment later in this chapter, set the ORACLE_BASE environment variable to specify the Oracle base directory you have created in this task.

2.15 Creating the Oracle Clusterware Home Directory

Oracle Universal Installer (OUI) creates the Oracle Clusterware home directory for you. Ensure before you start the installation that you provide sufficient disk space on a file system for the Oracle Clusterware directory, and the parent directory of the Oracle Clusterware directory space is writable by the oracle user.

To identify an appropriate file system, follow these steps:

1. Use the df -h command to determine the free disk space on each mounted file system.

2. From the display, identify a file system that has at least 1.4 GB of free disk space.

   If you are using the same file system for the Oracle base directory, then this 1.4 GB of disk space is additional to the free disk space requirement that you identified previously.

   Note:

   The file system must be a cluster file system.

   The path to the Oracle Clusterware home directory must be the same on all nodes.

3. Note the name of the mount point directory for the file system that you identified.

To create the Oracle Clusterware home 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/crs/oracle_sw_owner/product/10/app
   # chown -R root:oinstall /mount_point/crs
   # chmod -R 775 /mount_point/crs/oracle_sw_owner
   
   

   If the mount point you identified is /u01, then the recommended Oracle Clusterware home directory path is as follows:

   /u01/crs/oracle/product/10/crs
   
   

   Note:

   After installation, you should change permissions so that only the root user can write to the Oracle Clusterware home directory.

2. If necessary, repeat the commands listed in the previous step to create the same directory on the other nodes in the cluster.

3. Enter commands similar to the following to set the ORACLE_BASE and ORACLE_HOME environment variable in preparation for the Oracle Clusterware installation:

   • Bourne, Bash, or Korn shell:

     $ ORACLE_BASE=/u01/app/oracle
     $ ORACLE_HOME=/u01/crs/oracle/product/10/app
     $ export ORACLE_BASE
     $ export ORACLE_HOME
     
     

   • C shell:

     % setenv ORACLE_BASE /u01/app/oracle
     % setenv ORACLE_HOME /u01/crs/oracle/product/10/app
     
     

4. Enter the following commands to ensure that the TNS_ADMIN environment variable is not set:

   • Bourne, Bash, or Korn shell:

     $ unset TNS_ADMIN
     
     

   • C shell:

     % unsetenv TNS_ADMIN
     
     

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

2.16 Overview of the Spike Optimalization Tool

The Spike optimization tool (Spike) is a performance optimization tool that increases the performance of the Tru64 UNIX binary. In a testing environment, Spike, with feedback, increased the performance of Oracle Database by up to 23 percent on an OLTP workload.

For information about Spike, refer to the Tru64 UNIX documentation, or enter one of the following commands:

man spike
spike

2.17 Stopping Existing Oracle Processes for Upgrades or Co-existing Databases

Table 2-5 provides an overview of what you need to do if you have an existing Oracle database on the system where you plan to install Oracle Database 10g Release 2 (10.2). Review the table, and perform tasks as required.

Installing Oracle 10g Release 2 on a System with Oracle 10g Release 1

If your system has an Oracle Database Release 10g Release 10. 1 installation, and you install an Oracle Database 10g Release 2 (10.2) either to coexist with or to upgrade the 10.1, then most installation types configure and start a default Oracle Net listener using TCP/IP port 1521 and the IPC key value EXTPROC. One of the following occurs:

• During a co-existing installation, Database Configuration Assistant (DBCA) automatically migrates the listener and related files from the 10.1 Oracle home to the 10.2 Oracle home.

• During an upgrade, Oracle Database Upgrade Assistant (DBUA) automatically locates the Oracle 10g release 1 (10.1) listener, and migrates it to Oracle 10g release 2.

Proceed to Chapter 3.

Installing Oracle 10g Release 2 on a System with Oracle9i Release 2

This section provides instructions for preparing

Explanation of Tasks If you are installing an Oracle Database 10g Release 2 (10.2) on a system with an existing Oracle9i Release 2 (9.2) database, and the Oracle Net listener process is using the same port or key value as the default used with the Oracle 10g Release 2 (10.2) installation, port 1521, then Oracle Universal Installer can only configure the new listener; it cannot start it. To ensure that the new listener process starts during the installation, you must shut down any existing listeners before starting Oracle Universal Installer. To do this, refer to "Shutting Down the Listener"

You must shut down the Global Services Daemon (GSD), because otherwise, during 10g Release 2 (10.2) installation, the Oracle9i Release 9.2 SRVM shared data is upgraded into an Oracle Cluster Registry that the 9.2 GSD will not be able to use. The 10.2 Oracle Clusterware installation starts a 10g Release 2 (10.2) GSD to serve the Oracle9i 9.2 clients. To do this, refer to "Shutting down the Global Services Daemon"

Shutting Down the Listener To determine whether an existing Oracle9i listener process is running and to shut it down if necessary, follow these steps:

1. Switch user to oracle:

   # su - oracle
   
   

2. Enter the following command to determine whether an Oracle9i listener process is running and to identify its name and the Oracle home directory in which it is installed:

   $ ps -ef | grep tnslsnr
   
   

   This command displays information about the Oracle Net listeners running on the system:

   ... oracle_home1/bin/tnslsnr LISTENER -inherit
   
   

   In this example, oracle_home1 is the Oracle home directory where the listener is installed and LISTENER is the listener name.

   Note:

   If no Oracle Net listeners are running, then proceed to Chapter 3.

3. Set the ORACLE_HOME environment variable to specify the appropriate Oracle home directory for the listener:

   • Bourne, Bash, or Korn shell:

     $ ORACLE_HOME=oracle_home1
     $ export ORACLE_HOME
     
     

   • C or tcsh shell:

     % setenv ORACLE_HOME oracle_home1
     
     

4. Enter the following command to identify the TCP/IP port number and IPC key value that the listener is using:

   $ $ORACLE_HOME/bin/lsnrctl status listenername
   

   Note:

   If the listener uses the default name LISTENER, then you do not have to specify the listener name in this command.

5. Enter a command similar to the following to stop the listener process:

   $ $ORACLE_HOME/bin/lsnrctl stop listenername
   
   

6. Repeat this procedure to stop all listeners running on this system and on all other nodes in the cluster.

Shutting down the Global Services Daemon As the oracle user, on each node of the cluster, use the following syntax to shut down the GSD:

$ cd 92_Oracle_home
$ bin/gsdctl stop

In the preceding syntax example, the variable 92_Oracle_home is the Oracle9i Release 2 (9.2) database home.