2 Pre-installation Tasks

Log In to the System as root

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

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

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

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

     $ xhost +
     
     

  3. If you are not installing the software on the local system, 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, enter the following command to switch user to root:

     $ su - root
     password:
     #
     
     

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

  
  

  Note: If necessary, see your X server documentation for more information about completing this procedure. Depending on the X server software that you are using, you may need to complete the tasks in a different order.

  
  

  1. Start the X server software.

  2. Configure the security settings of the X server software to permit remote hosts to display X applications on the local system.

  3. Connect to the remote system where you want to install the software and start a terminal session on that system, for example, an X terminal (xterm).

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

     $ su - root
     password:
     #
     

Check the Hardware Requirements

The system must meet the following minimum hardware requirements:

• 512 MB of physical RAM

• 1 GB of swap space (or twice the size of RAM)

  On systems with 2 GB or more of RAM, the swap space can be between one and two times the size of RAM.

• 400 MB of disk space in the /tmp directory

• Between 1.5 GB and 3 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)

  
  

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

  
  

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

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

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

   Platform	Command
   Linux x86-64	# grep MemTotal /proc/meminfo

   
   

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

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

   Platform	Command
   Linux x86-64	# grep SwapTotal /proc/meminfo

   
   

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

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

   • # df -k /tmp
     
     

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

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

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

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

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

   • # df -k
     
     

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

   Platform	Installation Type	Requirement for Software Files (GB)
   Linux x86-64	Enterprise Edition	1.5
   Linux x86-64	Standard Edition	1.5
   Linux x86-64	Custom (maximum)	1.5

   
   

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

   Platform	Installation Type	Requirement for Software Files (MB)
   Linux x86-64	Instant Client	110
   Linux x86-64	Administrator	650
   Linux x86-64	Runtime	350
   Linux x86-64	Custom (maximum)	650

   
   

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

   
   

   Note: If you do not see the expected output, you cannot install the software on this system.

   
   

   Platform	Command	Expected Output
   Linux x86-64	# grep "model name" /proc/cpuinfo	This command displays the processor type. Verify that the processor architecture matches the Oracle software release that you want to install.

   
   

Check the Software Requirements

See the following section for information about checking the software requirements:

• Checking the Software Requirements on Linux x86-64

make-3.79.1
gcc-3.2.3-34
glibc-2.3.2-95.20
glibc-devel-2.3.2-95.20
glibc-devel-2.3.2-95.20 (32 bit)
compat-db-4.0.14-5
compat-gcc-7.3-2.96.128
compat-gcc-c++-7.3-2.96.128
compat-libstdc++-7.3-2.96.128
compat-libstdc++-devel-7.3-2.96.128
gnome-libs-1.4.1.2.90-34.1 (32 bit)
openmotif21-2.1.30-8
setarch-1.3-1
libaio-0.3.96-3
libaio-devel-0.3.96-3

make-3.79.1
gcc-3.3-43
gcc-c++-3.3.3-43
glibc-2.2.5-213
glibc-32bit-8.1-9
glibc-devel-32bit-8.1-9
openmotif-2.2.2-124
libaio-0.3.96-3
libaio-devel-0.3.96-3

gcc-3.3.3-43
gcc-c++-3.3.3-43
glibc-2.3.3-98
libaio-0.3.98-18
libaio-devel-0.3.98-18
make-3.80
openmotif-libs-2.2.2-519.1

Create Required UNIX 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 UNIX groups and a UNIX user.

The following UNIX 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 UNIX users 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, you must choose the Custom installation type to install the software or start the Installer as a user that is not a member of this group. In this case, the 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 UNIX 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, you must choose the Custom installation type to install the software or start the Installer as a user that is not a member of the dba group. In this case, the Installer prompts you to specify the name of this group. The usual name chosen for this group is oper.

• An unprivileged user

  You must 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 UNIX 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, the existing Oracle Inventory group must be the primary group of the UNIX user that you use to install new Oracle software. The following sections describe how to identify an existing Oracle Inventory group.

  
  

• The Oracle software owner user (oracle)

  You must create this user the first time you install Oracle software on the system. This user owns all of the software installed during the installation. The usual name chosen for this user is oracle. This user must have the Oracle Inventory group as its primary group. It must also have the OSDBA and OSOPER groups as a secondary groups.

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 UNIX user and groups.

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

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

Configure Kernel Parameters and Shell Limits

See one of the following section for information about configuring the system kernel parameters and shell limits:

• Configuring Kernel Parameters on Linux x86-64

Identify Required Software Directories

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

• Oracle base directory

• Oracle Inventory directory

• Oracle home directory

The following subsections describe the requirements for these directories.

Oracle Base Directory

The Oracle base directory acts as a top-level directory for Oracle software installations. It is analogous to the C:\Oracle directory used for Oracle software installations on Windows systems. On Linux systems, the Optimal Flexible Architecture (OFA) guidelines recommend that you use a path similar to the following for the Oracle base directory:

/mount_point/app/oracle_sw_owner

In this example:

• mount_point is the mount point directory for the file system that will contain the Oracle software.

  The examples in this guide use /u01 for the mount point directory. However, you could choose another mount point directory, /oracle or /opt/oracle for example.

• oracle_sw_owner is the UNIX user name of the Oracle software owner, for example oracle.

You can use the same Oracle base directory for more than one installation or you can create separate Oracle base directories for different installations. If different UNIX users install Oracle software on the same system, each user must create a separate Oracle base directory. The following example Oracle base directories could all exist on the same system:

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

The following sections describe how to identify existing Oracle base directories that might be suitable for your installation and how to create a new Oracle base directory if necessary.

Regardless of whether you create a new Oracle base directory or decide to use an existing one, you must set the ORACLE_BASE environment variable to specify the full path to this directory.

Oracle Inventory Directory

The Oracle Inventory directory (oraInventory) stores an inventory of all software installed on the system. It is required by, and shared by, all Oracle software installations on a single system. The first time you install Oracle software on a system, the Installer prompts you to specify the path to this directory. Oracle recommends that you choose the following path:

oracle_base/oraInventory

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

Oracle Home Directory

The Oracle home directory is the directory where you choose to install the software for a particular Oracle product. You must install different Oracle products, or different releases of the same Oracle product, in separate Oracle home directories. When you run the Installer, it prompts you to specify the path to this directory, as well as a name that identifies it. The directory that you specify must be a subdirectory of the Oracle base directory. Oracle recommends that you specify a path similar to the following for the Oracle home directory:

oracle_base/product/10.1.0/db_1

The Installer creates the directory path that you specify under the Oracle base directory. It also sets the correct owner, group, and permissions on it. You do not need to create this directory.

Identify or Create an Oracle Base Directory

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

• Identifying an Existing Oracle Base Directory

• Creating a New 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:

• Identify an existing Oracle Inventory directory

  Enter the following command to view the contents of the oraInst.loc file:

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

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

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

  The inventory_loc parameter identifies the Oracle Inventory directory (oraInventory). The parent directory of the oraInventory directory is typically an Oracle base directory. In the previous example, /u01/app/oracle is an Oracle base directory.

• Identify existing Oracle home directories

  Enter the following command to view the contents of the oratab file:

  • # more /etc/oratab
    
    

  If the oratab file exists, it contains lines similar to the following:

  *:/u03/app/oracle/product/10.1.0/db_1:N
  *:/opt/orauser/infra_904:N
  *:/oracle/9.2.0:N
  
  

  The directory paths specified on each line identify Oracle home directories. Directory paths that end with the user name of the Oracle software owner that you want to use are valid choices for an Oracle base directory. If you intend to use the oracle user to install the software, you could choose one of the following directories from the previous example:

  /u03/app/oracle
  /oracle
  

  
  

  Note: If possible, choose a directory path similar to the first (/u03/app/oracle). This path complies with the OFA guidelines.

  
  

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 sufficient free disk space on all cluster nodes, as follows:

  Requirement	Free Disk Space
  The Oracle base directory will contain only software files.	Up to 3 GB, depending on the platform
  The Oracle base directory will contain both software and database files (not recommended for production databases).	Up to 4 GB, depending on the platform

  
  

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

  • # df -k oracle_base_path
    
    

To continue:

• If an Oracle base directory exists and you want to use it, see the following section:

  • Choose a Storage Option for Oracle Database and Recovery Files

  When you are configuring the oracle user's environment later in this chapter, set the ORACLE_BASE environment variable to specify the directory you chose.

• If an Oracle base directory does not exist on the system or if you want to create a new Oracle base directory, see the following section.

Creating a New Oracle Base Directory

Before you create a new Oracle base directory, you must identify an appropriate file system with sufficient free disk space, as follows:

To identify an appropriate file system, follow these steps:

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

2. From the display, identify a file system that has appropriate free space.

   The file system that you identify can be a local file system, a cluster file system, or an NFS file system on a certified NAS device.

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

To create the Oracle base directory and specify the correct owner, group, and permissions for it, follow these steps:

1. Enter commands similar to the following to create the recommended subdirectories in the mount point directory that you identified and set the appropriate owner, group, and permissions on them:

   # mkdir -p /mount_point/app/oracle_sw_owner
   # chown -R oracle:oinstall /mount_point/app/oracle_sw_owner
   # chmod -R 775 /mount_point/app/oracle_sw_owner
   
   

   If the mount point you identified is /u01 and oracle is the user name of the Oracle software owner, the recommended Oracle base directory path is as follows:

   /u01/app/oracle
   
   

2. When you are configuring the oracle user's environment later in this chapter, set the ORACLE_BASE environment variable to specify this directory.

Choose 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 datafiles, 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, 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 ASM as the storage option for database and recovery files.

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

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

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

• To use ASM for database or recovery file storage, see the "Configure Disks for Automatic Storage Management" section.

• To use raw devices (partitions or logical volumes) for database file storage, see the following section:

  Configure Raw Devices

Create Directories for Oracle Database or Recovery Files

If you decide to place the Oracle database or recovery files on a file system, use the following guidelines when deciding where to place them.

Guidelines for Placing Oracle Database Files on a File System

If you choose to place the Oracle database files on a file system, use the following guidelines when deciding where to place them:

• The default path suggested by the Installer for the database file directory is a subdirectory of the Oracle base directory.

  This default location is not recommended for production databases.

• You can choose either a single file system or more than one file system to store the database files:

  • If you want to use a single file system, choose a file system on a physical device that is dedicated to the database.

    For best performance and reliability, choose a RAID device or a logical volume on more than one physical device and implement the stripe-and-mirror-everything (SAME) methodology.

  • If you want to use more than one file system, choose file systems on separate physical devices that are dedicated to the database.

    This method allows you to distribute physical I/O and create separate control files on different devices for increased reliability. It also allows you to fully implement the OFA guidelines described in Appendix D, "Optimal Flexible Architecture". You must choose either the Advanced database creation option or the Custom installation type during the installation to implement this method.

• If you intend to create a preconfigured database during the installation, the file system (or file systems) that you choose must have at least 1.2 GB of free disk space.

  For production databases, you must estimate the disk space requirement depending on the use that you want to make of the database.

• For optimum performance, the file systems that you choose should be on physical devices that are used only by the database.

• The oracle user must have write permissions to create the files in the path that you specify.

Guidelines for Placing Oracle Recovery Files on a File System

If you choose to place the Oracle recovery files on a file system, use the following guidelines when deciding where to place them:

• To prevent disk failure from making both the database files and the recovery files unavailable, place the recovery files in a file system on a different physical disk from the database files.

  
  

  Note: Alternatively use an ASM disk group with a normal or high redundancy level for either or both file types.

  
  

• The file system that you choose should have at least 2 GB of free disk space.

  The disk space requirement is the default disk quota configured for the flash recovery area (specified by the DB_RECOVERY_FILE_DEST_SIZE initialization parameter).

  If you choose the Custom installation type or the Advanced database configuration option, you can specify a different disk quota value. After you create the database, you can also use Oracle Enterprise Manager Grid Control or Database Control to specify a different value.

  For more information about sizing the flash recovery area, see the Oracle Backup and Recovery Basics manual.

• The default path suggested by the Installer for the flash recovery area is a subdirectory of the Oracle base directory. You can choose this path only if you are using an Oracle base directory that is on a shared file system.

  This default location is not recommended for production databases.

• The oracle user must have write permissions to create the files in the path that you specify.

Creating Required Directories

To create directories for the Oracle CRS, database, or recovery files on separate file systems to the Oracle base directory, follow these steps:

1. If necessary, configure the shared file systems that you want to use and mount them on each node.

   
   

   Note: The mount point that you use for the file system must be identical on each node. Make sure that the file systems are configured to mount automatically when a node reboots.

   
   

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

3. From the display, identify the file systems that you want to use:

   File Type	File System Requirements
   Database files	Choose either: A single file system with at least 1.2 GB of free disk space Two or more file systems with at least 1.2 GB of free disk space in total
   Recovery files	Choose a file system with at least 2 GB of free disk space.

   
   

   If you are using the same file system for more than one type of file, add the disk space requirements for each type to determine the total disk space requirement.

4. Note the names of the mount point directories for the file systems that you identified.

5. Enter commands similar to the following to create the recommended subdirectories in each of the mount point directories and set the appropriate owner, group, and permissions on them:

   • Database file directory:

     # mkdir /mount_point/oradata
     # chown oracle:oinstall /mount_point/oradata
     # chmod 775 /mount_point/oradata
     
     

   • Recovery file directory (flash recovery area):

     # mkdir /mount_point/flash_recovery_area
     # chown oracle:oinstall /mount_point/flash_recovery_area
     # chmod 775 /mount_point/flash_recovery_area
     
     

6. If you also want to use ASM or raw devices for storage, see one of the following sections:

   • Configure Disks for Automatic Storage Management

   • Configure Raw Devices

   Otherwise, see the "Stop Existing Oracle Processes" section.

Configure Disks for Automatic Storage Management

This section describes how to configure disks for use with ASM. 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:

• Identifying Storage Requirements for ASM

• Using an Existing ASM Disk Group

• Configuring Disks for ASM

configure

# /etc/init.d/oracleasm configure

enable
disable

# /etc/init.d/oracleasm enable

start
stop
restart

# /etc/init.d/oracleasm restart

createdisk

# /etc/init.d/oracleasm createdisk DISKNAME devicename

deletedisk

# /etc/init.d/oracleasm deletedisk DISKNAME

querydisk

# /etc/init.d/oracleasm querydisk {DISKNAME | devicename}

listdisks

# /etc/init.d/oracleasm listsdisks

scandisks

# /etc/init.d/oracleasm scandisks

Configure Raw Devices

The following sections for contains information about configuring raw devices on Linux x86-64:

Stop Existing Oracle Processes

If you choose to create a database during the installation, 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, the 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 the Installer.

To determine whether an existing 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 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, see the "Configure 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, 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.

Configure the oracle User's Environment

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

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

• Set the DISPLAY,ORACLE_BASE, and ORACLE_SID environment variables.

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

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

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

   $ xhost +
   
   

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

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

   $ su - oracle
   
   

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

   $ echo $SHELL
   
   

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

   
   

   Note: On Red Hat Linux, .bash_profile is the user startup file for the Bash shell.

   
   

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

     $ vi .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 variables are set in the file, remove the appropriate lines from the file.

9. Save the file and exit from the editor.

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

    • Bash shell on Red Hat Enterprise Linux:

      $ . ./.bash_profile
      
      

    • Bourne, Bash, or Korn shell:

      $ . ./.profile
      
      

    • C shell:

      % source ./.login
      
      

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

    • Bourne, Bash, or Korn shell:

      $ DISPLAY=local_host:0.0 ; export DISPLAY
      
      

    • C shell:

      % setenv DISPLAY local_host:0.0
      
      

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

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

    1. Use the df -k command 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, 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 command 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, the 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, Oracle recommends that you unset the ORACLE_HOME environment variable and choose the default path suggested by the 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.