2 Preinstallation Tasks

2.1 Logging In to the System as root

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

• 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 the remote host to display X applications on the local X server:

     $ xhost fully_qualified_remote_host_name
     
     

     For example:

     $ xhost somehost.us.acme.com
     
     

  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 fully_qualified_remote_host_name
     
     

  4. If you are not logged in as the root user, then 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, 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.2 Checking the Hardware Requirements

The system must meet the following minimum hardware requirements:

• At least 1024 MB of physical RAM

• The following table describes the relationship between installed RAM and the configured swap space requirement.

  RAM	Swap Space
  Between 1024 MB and 2048 MB	1.5 times the size of RAM
  Between 2049 MB and 8192 MB	Equal to the size of RAM
  More than 8192 MB	0.75 times the size of RAM

  
  

• 400 MB of disk space in the /tmp directory

• Between 1.5 GB and 3.5 GB of disk space for the Oracle software, depending on the installation type

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

  
  

  Note: The disk space requirement for databases that use Automatic Storage Management or raw device storage is described later in this chapter.

  
  

  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 the system meets these requirements:

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

   # /usr/sbin/prtconf | grep "Memory size"
   
   

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

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

   # /usr/sbin/swap -s
   
   

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

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

   # df -k /tmp
   # df -h /tmp (on Solaris 10)
   
   

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

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

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

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

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

   # df -k
   # df -h (on Solaris 10)
   
   

   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	2.0
   Standard Edition	1.5
   Custom (maximum)	2.5

   
   

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

   # /bin/isainfo -kv
   

   
   

   Note: The following is the expected output of this command: 64-bit sparcv9 kernel modules If you do not see the expected output, then you cannot install the software on this system.

   
   

2.3 Checking the Software Requirements

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

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

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

To ensure that the system meets these requirements:

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

   # uname -r
   5.9
   
   

   In this example, the version shown is Solaris 9 (5.9). If necessary, refer to your operating system documentation for information about upgrading the operating system.

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. Refer to your operating system or software documentation for information about installing packages.

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

To ensure that the system meets these requirements:

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

   # /usr/sbin/patchadd -p | grep patch_number(without version number)
   
   

   For example, to determine if any version of the 111713 patch is istalled, use the follwing command:

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

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

   http://sunsolve.sun.com
   
   

2. If you require a CSD or a SupportPac for WebSphere MQ, then refer to the following Web site for download and installation information:

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

2.4 Checking the Network Setup

Typically, the computer on which you want to install Oracle Database is connected to the network, has local storage to contain the Oracle Database installation, has a display monitor, and has a CD-ROM or DVD drive.

This section describes how to install Oracle Database on computers that do not meet the typical scenario. It covers the following cases:

• Configuring Name Resolution

• Installing on DHCP Computers

• Installing on Multihomed Computers

• Installing on Computers with Multiple Aliases

• Installing on Non-Networked Computers

$ ORACLE_HOSTNAME=somehost.us.acme.com
$ export ORACLE_HOSTNAME

% setenv ORACLE_HOSTNAME somehost.us.acme.com

2.5 Creating Required Operating System Groups and Users

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

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

• The OSDBA group (dba)

  You must create this group the first time you install Oracle Database software on the system. It 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 (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 (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 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. This user must have the Oracle Inventory group as its primary group. It must also have the OSDBA and OSOPER groups as secondary groups.

  
  

  Note: In Oracle documentation, this user is referred to as 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 users and groups:

• Creating the Oracle Inventory Group

• Creating the OSDBA Group

• Creating an OSOPER Group (Optional)

• Creating the Oracle Software Owner User

# 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 -a oracle

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

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

2.6 Configuring Kernel Parameters

Verify that the kernel parameters shown in the following table are set to values greater than or equal to the recommended value shown on Solaris 8 and Solaris 9 operating systems. The procedure following the table describes how to verify and set the values.

On Solaris 10, verify that the kernel parameters shown in the following table are set to values greater than or equal to the recommended value shown. The table aslo contains the resource controls that replace the /etc/system file for a specific kernel parameter.

On Solaris 8 and Solaris 9 operating systems, use the following procedure to view the current value specified for these kernel parameters, and to change them if necessary:

1. To view the current values of these parameters, enter the following commands:

   # grep noexec_user_stack /etc/system
   # /usr/sbin/sysdef | grep SEM
   # /usr/sbin/sysdef | grep SHM
   
   

2. If you must change any of the current values, then:

   1. Create a backup copy of the /etc/system file, for example:

      # cp /etc/system /etc/system.orig
      
      

   2. Open the /etc/system file in any text editor and, if necessary, add lines similar to the following (edit the lines if the file already contains them):

      set noexec_user_stack=1
      set semsys:seminfo_semmni=100
      set semsys:seminfo_semmns=1024
      set semsys:seminfo_semmsl=256
      set semsys:seminfo_semvmx=32767
      set shmsys:shminfo_shmmax=4294967295
      set shmsys:shminfo_shmmin=1
      set shmsys:shminfo_shmmni=100
      set shmsys:shminfo_shmseg=10
      
      

   3. Enter the following command to restart the system:

      # /usr/sbin/reboot
      
      

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

On Solaris 10, use the following procedure to view the current value specified for resource controls, and to change them if necessary:

1. To view the current values of the resource control, enter the following commands:

   # id -p // to verify the project id
   uid=0(root) gid=0(root) projid=1 (user.root)
   # prctl -n project.max-shm-memory -i project user.root
   # prctl -n project.max-sem-ids -i project user.root
   
   

2. If you must change any of the current values, then:

   1. To modify the value of max-shm-memory to 6 GB:

      # prctl -n project.max-shm-memory -v 6gb -r -i project user.root
      
      

   2. To modify the value of max-sem-ids to 256:

      # prctl -n project.max-sem-ids -v 256 -r -i project user.root
      

2.7 Identifying Required Software Directories

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

• Oracle Base Directory

• Oracle Inventory Directory

• Oracle Home Directory

/mount_point/app/oracle_sw_owner

/u01/app/oracle
/u01/app/orauser
/opt/oracle/app/oracle

oracle_base/oraInventory

oracle_base/product/10.2.0/db_1

2.8 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

2.9 Choosing a Storage Option for Oracle Database and Recovery Files

The following table shows the storage options supported for storing Oracle Database files and Oracle Database recovery files. Oracle Database files include data files, control files, redo log files, the server parameter file, and the password file.

For all installations, you must choose the storage option that you want to use for Oracle Database files. If you want to enable automated backups during the installation, then you must also choose the storage option that you want to use for recovery files (the flash recovery area). You do not have to use the same storage option for each file type.

Use the following guidelines when choosing the storage options that you want to use for each file type:

• You can choose any combination of the supported storage options for each file type.

• Oracle recommends that you choose Automatic Storage Management as the storage option for database and recovery files.

• For more information about these storage options, refer to the "Database Storage Options" section.

For information about how to configure disk storage before you start the installation, refer to one of the following sections depending on your choice:

• To use a file system for database or recovery file storage, refer to the "Creating Directories for Oracle Database or Recovery Files" section.

• To use raw devices for database file storage, refer to the following section:

  "Configuring Raw Partitions or Raw Logical Volumes"

2.10 Creating Directories for Oracle Database or Recovery Files

This section contains the following topics:

• Guidelines for Placing Oracle Database Files on a File System

• Guidelines for Placing Oracle Recovery Files on a File System

• Creating Required Directories

2.11 Preparing Disk Groups for an Automatic Storage Management Installation

This section describes how to configure disks for use with Automatic Storage Management. Before you configure the disks, you must determine the number of disks and the amount of free disk space that you require. The following sections describe how to identify the requirements and configure the disks on each platform:

• General Steps for Configuring Automatic Storage Management

• Step 1: Identifying Storage Requirements for Automatic Storage Management

• Step 2: Using an Existing Automatic Storage Management Disk Group

• Step 3: Creating DAS or SAN Disk Partitions for Automatic Storage Management

• Step 4: Configuring Disks for Automatic Storage Management

2.12 Configuring Raw Partitions or Raw Logical Volumes

The following subsections describe how to configure raw partitions or raw logical volumes.

• "Configuring Raw Partitions for Oracle Database File Storage"

  Follow the procedures described in this section if you want to use raw partitions for Oracle Database file storage. You can use either raw disk slices or Solaris Volume Manager soft partitions to store the required database files.

• "Configuring Raw Logical Volumes for Oracle Database File Storage"

  Follow the procedures described in this section only if you are using VERITAS Volume Manager (VxVM) on SPARC systems.

Configuring Raw Partitions for Oracle Database File Storage

This section describes how to configure raw partitions for Oracle database files.

A partition is a slice defined on a disk or on a disk array volume. It can also be a soft partition created using Solaris Volume Manager.

Table 2-1 lists the number and size of the raw partitions that you must configure for database files.

system

sysaux

undotbs1

temp

example

users

redo1_m

control{1|2}

spfile

pwdfile

To configure raw partitions for database files:

1. Choose a name for the database that you want to create.

   The name that you choose must start with a letter and have no more than four characters, for example, orcl.

2. If necessary, install or configure the disks that you intend to use and restart the system.

3. If you want to use Solaris Volume Manager soft partitions, then refer to the Solaris Volume Manager documentation for information about how to create them.

   The previous table shows the number and size of the partitions that you require.

4. If you want to use disk slices, then follow these steps to create or identify the required disk slices:

   1. To list the disks attached to the system, enter the following command:

      # /usr/sbin/format
      
      

      The output from this command is similar to the following:

      AVAILABLE DISK SELECTIONS:
             0. c0t0d0 <ST34321A cyl 8892 alt 2 hd 15 sec 63>
                /pci@1f,0/pci@1,1/ide@3/dad@0,0
             1. c1t5d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
                /pci@1f,0/pci@1/scsi@1/sd@5,0
      
      

      This command displays information about each disk attached to the system, including the device name (cxtydz).

   2. Enter the number corresponding to the disk that you want to use.

      
      

      Note: Ensure that the disk you choose is not being used for another purpose. For example, ensure that it is not being used as a component for a logical volume manager volume.

      
      

   3. Use the fdisk command to create a Solaris partition on the disk if one does not already exist.

      Solaris fdisk partitions must start at cylinder 1, not cylinder 0. If you create an fdisk partition, then you must label the disk before continuing.

   4. Enter the partition command, followed by the print command to display the partition table for the disk that you want to use.

   5. Identify or create slices for each of the partitions that you require.

      The previous table shows the number and size of the partitions that you require for database files.

      
      

      Note: To prevent the database files from overwriting the partition table, do not use slices that start at cylinder 0 (for example, slice 2).

      
      

   6. Make a note of the number of the slices that you want to use.

   7. If you modified a partition table or created a new one, then enter the label command to write the partition table and label to the disk.

   8. Enter q to return to the format menu.

   9. After you have finished creating slices, enter q to quit from the format utility.

5. If you plan to use existing partitions, then enter the following command to verify that they are not mounted as file systems:

   # df -k
   
   

   This command displays information about the devices that are mounted as file systems. The device name for a slice includes the disk device name followed by the slice number, for example cxtydzsn, where sn is the slice number. The device name for a Solaris Volume Manager partition is similar to /dev/md/dsk/dnnn, where dnnn is the soft partition name.

6. Enter commands similar to the following to change the owner, group, and permissions on the character raw device file for each partition:

   
   

   Note: If you are using a multi-pathing disk driver, then ensure that you set the permissions only on the correct logical device name for the partition.

   
   

   • Solaris Volume Manager soft partitions:

     # chown oracle:dba /dev/md/rdsk/d100
     # chmod 660 /dev/md/rdsk/d100
     
     

   • Disk slices:

     # chown oracle:dba /dev/rdsk/cxtydzsn
     # chmod 660 /dev/rdsk/cxtydzsn
     
     

7. Follow these steps to create the Oracle Database Configuration Assistant raw device mapping file:

   1. Set the ORACLE_BASE environment variable to specify the Oracle base directory that you identified or created previously:

      • Bourne, Bash, or Korn shell:

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

      • C shell:

        % setenv ORACLE_BASE /u01/app/oracle
        
        

   2. Create a database file subdirectory under the Oracle base directory and set the appropriate owner, group, and permissions on it:

      # mkdir -p $ORACLE_BASE/oradata/dbname
      # chown -R oracle:oinstall $ORACLE_BASE/oradata
      # chmod -R 775 $ORACLE_BASE/oradata
      
      

      In this example, dbname is the name of the database that you chose previously.

   3. Change directory to the $ORACLE_BASE/oradata/dbname directory.

   4. Using any text editor, create a text file similar to the following that identifies the device file name associated with each database file.

      Oracle recommends that you use a file name similar to dbname_raw.conf for this file.

      
      

      Note: The following example shows a sample mapping file that specifies Solaris Volume Manager soft partitions. If you are using disk slices, then specify the appropriate device file name for each slice, for example: /dev/rdsk/cxdytzsn

      
      

      system=/dev/md/rdsk/d100
      sysaux=/dev/md/rdsk/d101
      example=/dev/md/rdsk/d102
      users=/dev/md/rdsk/d103
      temp=/dev/md/rdsk/d104
      undotbs1=/dev/md/rdsk/d105
      redo1_1=/dev/md/rdsk/d106
      redo1_2=/dev/md/rdsk/d107
      control1=/dev/md/rdsk/d108
      control2=/dev/md/rdsk/d109
      spfile=/dev/md/rdsk/d110
      pwdfile=/dev/md/rdsk/d111
      
      

      In this example, dbname is the name of the database.

      Use the following guidelines when creating or editing this file:

      • Each line in the file must have the following format:

        database_object_identifier=device_file_name
        
        

      • Specify one automatic undo tablespace data file (undotbs1) and two redo log files (redo1_1, redo1_2).

      • Specify at least two control files (control1, control2).

      • To use manual instead of automatic undo management, specify a single RBS tablespace data file (rbs) instead of the automatic undo management tablespace data files.

   5. Save the file and note the file name that you specified.

   6. When you are configuring the oracle user's environment later in this chapter, set the DBCA_RAW_CONFIG environment variable to specify the full path to this file.

Configuring Raw Logical Volumes for Oracle Database File Storage

This section describes how to configure raw logical volumes using VERITAS Volume Manager (VxVM) on SPARC systems.

Creating a Disk Group

To create a disk group:

1. If necessary, install the disks that you intend to use for the disk group and restart the system.

2. To ensure that the disks are available, enter the following command:

   # /usr/sbin/format
   
   

   The output from this command is similar to the following:

   AVAILABLE DISK SELECTIONS:
          0. c0t0d0 <ST34321A cyl 8892 alt 2 hd 15 sec 63>
             /pci@1f,0/pci@1,1/ide@3/dad@0,0
          1. c1t5d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
             /pci@1f,0/pci@1/scsi@1/sd@5,0
   
   

   This command displays information about each disk attached to the system, including the device name (cxtydz).

3. From the list, identify the device names for the disk devices that you want to add to a disk group, then use Ctrl+D to exit from the format utility.

4. Enter the following command to verify that the devices you identified are not mounted as file systems:

   # df -k
   
   

   This command displays information about the partitions (slices) on disk devices that are mounted as file systems. The device name for a slice includes the disk device name followed by the slice number, for example cxtydzsn, where sn is the slice number. Slice 2 (s2) represents the entire disk. The disk devices that you choose must not be shown as mounted partitions.

5. Enter the following commands to verify that the devices you identified are not already part of a disk group:

   
   

   Note: The following command displays information about VERITAS Volume Manager (VxVM) disks. If you use a different LVM, then refer to the appropriate documentation for information about determining which disk devices it is managing.

   
   

   # /usr/sbin/vxdiskconfig
   # /usr/sbin/vxdisk list
   
   

   The vxdisk list command identifies the disk devices that are already configured in a disk group. The word online in the STATUS column also identifies disks that have been initialized and placed under VxVM control. The word error in the STATUS column identifies disks that are not initialized.

   The disk devices that you choose must not be in an existing disk group.

6. If the disk devices that you want to use are not initialized, then enter a command similar to the following to initialize each disk:

   # /usr/sbin/vxdiskadd cxtydz
   
   

7. To create a disk group, enter a command similar to the following, specifying all of the disks that you want to add to the group:

   # /usr/sbin/vxdg init diskgroup diskname=devicename ...
   
   

   In this example:

   • diskgroup is the name of the disk group that you want to create, for example, oradg

   • diskname is an administrative name that you assign to a disk, for example orad01

   • devicename is the device name, for example, c1t0d0

Creating Raw Logical Volumes in the New Disk Group

To create the required raw logical volumes in the new disk group:

1. Choose a name for the database that you want to create.

   The name that you choose must start with a letter and have no more than four characters, for example, orcl.

2. Identify the logical volumes that you must create.

   Table 2-2 lists the number and size of the logical volumes that you must create for database files.

   Table 2-2 Raw Logical Volumes Required for Database Files on Solaris

   Number	Size (MB)	Purpose and Sample Logical Volume Name
   1	500	SYSTEM tablespace: dbname_system_raw_500m
   1	500	SYSAUX tablespace: dbname_sysaux_raw_500m
   1	500	UNDOTBS1 tablespace: dbname_undotbs1_raw_500m
   1	250	TEMP tablespace: dbname_temp_raw_250m
   1	160	EXAMPLE tablespace: dbname_example_raw_160m
   1	120	USERS tablespace: dbname_users_raw_120m
   2	120	Two online redo log files (where m is the log number, 1 or 2): dbname_redo1_m_raw_120m
   2	110	First and second control files: dbname_control{1|2}_raw_110m
   1	5	Server parameter file (SPFILE): dbname_spfile_raw_5m
   1	5	Password file: dbname_pwdfile_raw_5m

   
   

3. To create the required logical volumes, enter commands similar to the following:

   # /usr/sbin/vxassist -g diskgroup make volume size user=oracle \
    group=dba mode=660
   
   

   In this example:

   • diskgroup is the name of the disk group that you created previously, for example oradg

   • volume is the name of the logical volume that you want to create

     Oracle recommends that you use the sample names shown in the previous table for the logical volumes. Substitute the dbname variable in the sample logical volume name with the name you chose for the database in step 1.

   • size is the size of the logical volume, for example, 500m represents 500 MB

   • user=oracle group=dba mode=660 specifies the owner, group, and permissions on the volume

     Specify the Oracle software owner user and the OSDBA group for the user and group values (typically oracle and dba).

   The following example shows a sample command used to create a 500 MB logical volume in the oradg disk group for the SYSAUX tablespace of a database named test:

   # /usr/sbin/vxassist -g oradb make test_sysaux_500m 500m \
   user=oracle group=dba mode=660
   
   

Creating the Oracle Database Configuration Assistant Raw Device Mapping File

To enable Oracle Database Configuration Assistant to identify the appropriate raw device for each database file, you must create a raw device mapping file, as follows:

1. Set the ORACLE_BASE environment variable to specify the Oracle base directory that you identified or created previously:

   • Bourne, Bash, or Korn shell:

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

   • C shell:

     % setenv ORACLE_BASE /u01/app/oracle
     
     

2. Create a database file subdirectory under the Oracle base directory and set the appropriate owner, group, and permissions on it:

   # mkdir -p $ORACLE_BASE/oradata/dbname
   # chown -R oracle:oinstall $ORACLE_BASE/oradata
   # chmod -R 775 $ORACLE_BASE/oradata
   
   

   In this example, dbname is the name of the database that you chose previously.

3. Change directory to the $ORACLE_BASE/oradata/dbname directory.

4. Enter the following command to create a text file that you can use to create the raw device mapping file:

   # find /dev/vx/rdsk/diskgroup -user oracle -name dbname* \
   -print > dbname_raw.conf
   
   

5. Edit the dbname_raw.conf file in any text editor to create a file similar to the following:

   system=/dev/vx/rdsk/diskgroup/dbname_system_raw_500m
   sysaux=/dev/vx/rdsk/diskgroup/dbname_sysaux_raw_500m
   example=/dev/vx/rdsk/diskgroup/dbname_example_raw_160m
   users=/dev/vx/rdsk/diskgroup/dbname_users_raw_120m
   temp=/dev/vx/rdsk/diskgroup/dbname_temp_raw_250m
   undotbs1=/dev/vx/rdsk/diskgroup/dbname_undotbs1_raw_500m
   redo1_1=/dev/vx/rdsk/diskgroup/dbname_redo1_1_raw_120m
   redo1_2=/dev/vx/rdsk/diskgroup/dbname_redo1_2_raw_120m
   control1=/dev/vx/rdsk/diskgroup/dbname_control1_raw_110m
   control2=/dev/vx/rdsk/diskgroup/dbname_control2_raw_110m
   spfile=/dev/vx/rdsk/diskgroup/dbname_spfile_raw_5m
   pwdfile=/dev/vx/rdsk/diskgroup/dbname_pwdfile_raw_5m
   
   

   In this example:

   • diskgroup is the name of the disk group

   • dbname is the name of the database

   Use the following guidelines when creating or editing this file:

   • Each line in the file must have the following format:

     database_object_identifier=logical_volume
     
     

     The logical volume names suggested in this manual include the database object identifier that you must use in this mapping file. For example, in the following logical volume name, redo1_1 is the database object identifier:

     /dev/vx/rdsk/oradg/rac_redo1_1_raw_120m
     
     

   • For a single-instance database, the file must specify one automatic undo tablespace data file (undotbs1), and at least two redo log files (redo1_1, redo1_2).

   • Specify at least two control files (control1, control2).

   • To use manual instead of automatic undo management, specify a single RBS tablespace data file (rbs) instead of the automatic undo management tablespace data file.

6. Save the file and note the file name that you specified.

7. When you are configuring the oracle user's environment later in this chapter, set the DBCA_RAW_CONFIG environment variable to specify the full path to this file.

8. To continue, refer to the "Stopping Existing Oracle Processes" section.

2.13 Stopping Existing Oracle Processes

If you choose to create a database during the installation, then most installation types configure and start a default Oracle Net listener using TCP/IP port 1521 and the IPC key value EXTPROC. However, if an existing Oracle Net listener process is using the same port or key value, 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 determine whether an existing listener process is running and to shut it down if necessary:

1. Switch user to oracle:

   # su - oracle
   
   

2. Enter the following command to determine whether a 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 refer to the "Configuring the oracle User's Environment" section to continue.

   
   

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.

2.14 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 environment variable.

To set the oracle user's environment:

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

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

   $ xhost fully_qualified_remote_host_name
   
   

   For example:

   $ xhost somehost.us.acme.com
   
   

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

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

   $ su - oracle
   
   

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

   $ echo $SHELL
   
   

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

   • C shell (csh or tcsh):

     % vi .login
     
     

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

   umask 022
   
   

8. If the ORACLE_SID, ORACLE_HOME, or ORACLE_BASE environment variable is set in the file, then remove the appropriate lines from the file.

9. Save the file, and exit from the editor.

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

    • Bash shell:

      $ . ./.bash_profile
      
      

    • Bourne or Korn shell:

      $ . ./.profile
      
      

    • C shell:

      % source ./.login
      
      

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

    • Bourne, Bash, or Korn shell:

      $ DISPLAY=local_host:0.0 ; export DISPLAY
      
      

    • C shell:

      % setenv DISPLAY local_host:0.0
      
      

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

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

    1. Use the df -k command to identify a suitable file system with sufficient free space.

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

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

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

       • Bourne, Bash, or Korn shell:

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

       • C shell:

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

13. Enter commands similar to the following to set the ORACLE_BASE and ORACLE_SID environment variables:

    • Bourne, Bash, or Korn shell:

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

    • C shell:

      % setenv ORACLE_BASE /u01/app/oracle
      % setenv ORACLE_SID sales
      
      

    In these examples, /u01/app/oracle is the Oracle base directory that you created or identified earlier and sales is the name that you want to call the database (typically no more than five characters).

14. If you are using raw devices for database storage, then set the DBCA_RAW_CONFIG environment variable to specify the full path to the raw device mapping file:

    • Bourne, Bash, or Korn shell:

      $ DBCA_RAW_CONFIG=$ORACLE_BASE/oradata/dbname/dbname_raw.conf
      $ export DBCA_RAW_CONFIG
      
      

    • C shell:

      % setenv DBCA_RAW_CONFIG=$ORACLE_BASE/oradata/dbname/dbname_raw.conf
      
      

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

    • Bourne, Bash, or Korn shell:

      $ unset ORACLE_HOME
      $ unset TNS_ADMIN
      
      

    • C shell:

      % unsetenv ORACLE_HOME
      % unsetenv TNS_ADMIN
      

    
    

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

    
    

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

    $ umask
    $ env | more
    
    

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