2 Pre-installation Tasks

This chapter describes the tasks that you must complete before you start the Oracle Universal Installer. It includes information about the following tasks:

Log In to the System as root
Check the Hardware Requirements
Check the Software Requirements
Create Required UNIX Group and User
Identify Required Software Directories
Identify or Create an Oracle Base Directory
Configure the oracle User's Environment

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, follow these steps:

Log in to the system as a user that is a member of the admin group.
Start a local terminal session (/Applications/Utilities/Terminal).
If you are not logged in as the root user, enter the following command to start a shell session with root privileges:
```
$ sudo sh
```
When prompted, enter your password.

Note:

Alternatively, if you are logged in as a user who is a member of the admin group, you can use the sudo command to run commands as the root user, as follows:

$ sudo /usr/sbin/sysctl -a

Check the Hardware Requirements

The system must meet the following minimum hardware requirements:

256 MB of physical RAM (268435456 bytes)
512 MB of swap space
400 MB of disk space in the /tmp directory
Between 75 MB and 420 MB of disk space for the Oracle software, depending on the installation type

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

To determine the physical RAM size, use System Profiler (/Applications/Utilities/System Profiler) or enter the following command:
```
# /usr/sbin/system_profiler SPHardwareDataType | grep Memory
```
If the size of the physical RAM installed in the system is less than the required size, you must install more memory before continuing.

To ensure that the system has enough swap space, enter the following command:

# df -h /

Note:

Mac OS X dynamically creates swap files as required in the /private/var/vm directory. Make sure that you have at least 512 MB of available disk space on the root (/) file system to accommodate newly created swap files.

To determine the amount of disk space available in the /tmp directory, enter the following command:
```
# df -h /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.
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 (MB)

Instant Client 75

Administrator 420

Runtime 200

Custom (maximum) 350

Installation Type	Requirement for Software Files (MB)
Instant Client	75
Administrator	420
Runtime	200
Custom (maximum)	350

Check the Software Requirements

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

Check for Required Software

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

Installation Type or Product	Requirement
All installations	The following operating system version: Apple Mac OS X Server 10.3.6
All Installations	The following software (or a higher version) must be installed: Xcode Tools 1.1 or higher GNU C compiler (`gcc`) version 3.3 20030304 (Apple Computer, Inc. build 1635) This version of `gcc` is included in Xcode Tools 1.2 or higher or in the Dec 2003 gccLongBranch Tools update.
Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, Oracle XML Developer's Kit (XDK)	The version of the GNU C and C++ compiler listed previously is supported for use with these products.

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

To determine the version of the operating system, enter the following command:
```
# sw_vers
```
Note:
Only Mac OS X Server is supported.
To determine whether the required version of gcc is installed, enter the following command:
```
# gcc -v
```
This command returns output similar to the following:
```
Reading specs from /usr/libexec/gcc/darwin/ppc/3.3/specs
Thread model: posix
gcc version 3.3 20030304 (Apple Computer, Inc. build 1635) (-mlongcall)
```
If the required version (including the date and build number) or a later version is not installed, download and install either of the following:
- The Dec 2003 gccLongBranch Tools update
- Xcode Tools 1.2 or higher, which includes the correct version of gcc
You can download this software from the Apple Developer Connection Web site:
```
http://connect.apple.com
```
After you log in, choose Download Software, then Developer Tools to display the download page.

Create Required UNIX Group and User

Depending on whether this is the first time Oracle software is being installed on this system and on the products that you are installing, you may need to create the following UNIX group and user:

The Oracle Inventory group (oinstall)

You must create this group the first time you install Oracle software on the system. The usual name chosen for this group is oinstall. This group owns the Oracle inventory, which is a catalog of all Oracle software installed on the system.

Note:

If Oracle software is already installed on the system, the existing Oracle Inventory group must be the primary group of the UNIX user that you use to install new Oracle software. The following sections describe how to identify an existing Oracle Inventory group.

The Oracle software owner user (oracle)

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

A single Oracle Inventory group is required for all installations of Oracle software on the system. After the first installation of Oracle software, you must use the same Oracle Inventory group for all subsequent Oracle software installations on that system. However, you can choose to create different Oracle software owner users for separate installations.

The following sections describe how to create the required UNIX user and group.

Note:

The following sections describe how to create local users and groups. As an alternative to creating local users and groups, you could create the appropriate users and groups in a directory service, for example, lightweight directory access protocol (LDAP) or Network Information Services (NIS). For information about using directory services, contact your system administrator or see your operating system documentation.

Creating the Oracle Inventory Group

You must create the Oracle Inventory group if it does not already exist. The following subsections describe how to determine the Oracle Inventory group name, if it exists, and how to create it if necessary.

Determine Whether the Oracle Inventory Group Exists

When you install Oracle software on the system for the first time, the Installer creates the oraInst.loc file. This file identifies the name of the Oracle Inventory group and the path of the Oracle Inventory directory. To determine whether the Oracle Inventory group exists, enter the following command:

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

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

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

The inst_group parameter shows the name of the Oracle Inventory group (oinstall).

Create the Oracle Inventory Group

If the oraInst.loc file does not exist, use one of the following methods to create the Oracle Inventory group:

Note:

Oracle recommends that you use the group name oinstall for the Oracle Inventory group.

Use Workgroup Manager (/Applications/Server/Workgroup Manager) to create a group called oinstall.
Use command-line utilities to create the Oracle Inventory group:
1. Enter the following command to list existing groups and group IDs (GIDs):
```
# nireport . /groups gid name | more
```
2. Identify an unused GID for the new Oracle Inventory group.
3. Enter commands similar to the following to create the oinstall group:
```
# nicl . -create /groups/oinstall
# nicl . -append /groups/oinstall gid gid_number
# nicl . -append /groups/oinstall passwd "*"
```

Creating the Oracle Software Owner User

You must create an Oracle software owner user in the following circumstances:

If an Oracle software owner user does not exist, for example, if this is the first installation of Oracle software on the system
If an Oracle software owner user exists, but you want to use a different UNIX user

Determine Whether an Existing Oracle Software Owner User Exists

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

# id oracle

If the oracle user exists, the output from this command is similar to the following:

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

If the user exists, determine whether you want to use the existing user or create a new user. If you want to use the existing user, ensure that the user's primary group (gid) is the Oracle Inventory group. See one of the following sections for more information:

Note:

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

If you want to use the existing Oracle software owner user, and the user's primary group is the Oracle Inventory group, see the "Identify Required Software Directories" section.
To modify an existing user, see the "Modify an Existing Oracle Software Owner User" section.
To create a new user, see the following section.

Create a New Oracle Software Owner User

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

Use Workgroup Manager to create a user with the following properties:

Property	Recommended Value
Name	Oracle Software Owner
Short name	`oracle`
Password	Specify and verify a password for the `oracle` user
Primary group	`oinstall`
Default shell	Any supported shell, for example `/bin/tcsh` or `/bin/bash`
Home directory	A home directory consistent with other user home directories, for example `/Users/oracle`

Use command-line utilities to create the Oracle software owner user:

Enter the following command to list existing users and user IDs (UIDs):
```
# nireport . /users uid name | more
```
Identify an unused UID for the new Oracle software owner user.

Enter commands similar to the following to create the oracle user:

# nicl . -create /users/oracle
# nicl . -append /users/oracle uid uid_number
# nicl . -append /users/oracle gid oinstall_gid
# nicl . -append /users/oracle shell /bin/bash
# nicl . -append /users/oracle home /Users/oracle
# nicl . -append /users/oracle realname "Oracle software owner"

Create the home directory for the oracle user and change the owner and group on that directory:
```
# mkdir /Users/oracle
# chown oracle:oinstall /Users/oracle
```
Set the password for the oracle user:
```
# passwd oracle
```

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

Modify an Existing Oracle Software Owner User

If the oracle user exists, but its primary group is not oinstall, you can use one of the following methods to modify it:

Use Workgroup Manager to modify the oracle user, specifying oinstall as the Primary group.
Use command-line utilities to modify the oracle user:
1. Enter the following command to determine the GID of the oinstall group:
```
# nireport . /groups/oinstall gid name
```
2. Enter the following command to change the GID of the oracle user to the GID of the oinstall group:
```
# nicl . -delete /users/oracle gid
# nicl . -append /users/oracle gid oinstall_gid
```

Identify Required Software Directories

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

Oracle base directory
Oracle Inventory directory
Oracle home directory

The following subsections describe the requirements for these directories.

Oracle Base Directory

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

/mount_point/app/oracle_sw_owner

In this example:

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

The examples in this guide use /Volumes/u01 for the mount point directory. However, you could choose another mount point directory, /Volumes/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:

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

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

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

Oracle Inventory Directory

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

oracle_base/oraInventory

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

Note:

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

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

Oracle Home Directory

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

oracle_base/product/10.1.0/client_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

Note:

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

Identifying an Existing Oracle Base Directory

Existing Oracle base directories might not have paths that comply with OFA guidelines. However, if you identify an existing Oracle Inventory directory or existing Oracle home directories, you can usually identify the Oracle base directories, as follows:

Identify an existing Oracle Inventory directory

Enter the following command to view the contents of the oraInst.loc file:
```
# more /var/opt/oracle/oraInst.loc
```
If the oraInst.loc file exists, the output from this command is similar to the following:
```
inventory_loc=/Volumes/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, /Volumes/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:
```
*:/Volumes/u03/app/oracle/product/10.1.0/db_1:N
*:/opt/orauser/infra_904:N
*:/Volumes/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:
```
/Volumes/u03/app/oracle
/Volumes/oracle
```
Note:
If possible, choose a directory path similar to the first (/Volumes/u03/app/oracle). This path complies with the OFA guidelines.

To continue:

If an Oracle base directory exists and you want to use it, see the "Configure the oracle User's Environment" section.

When you are configuring the oracle user's environment later in this chapter, set the ORACLE_BASE environment variable to specify the directory you chose.
If an Oracle base directory does not exist on the system or if you want to create a new Oracle base directory, see the following section.

Creating a New Oracle Base Directory

To identify an appropriate file system, follow these steps:

Use the df -h command to determine the free disk space on each mounted file system.
From the display, identify a file system that has appropriate free space.
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:

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 /Volumes/u01 and oracle is the user name of the Oracle software owner, the recommended Oracle base directory path is as follows:
```
/Volumes/u01/app/oracle
```
When you are configuring the oracle user's environment later in this chapter, set the ORACLE_BASE environment variable to specify this directory.

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

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

Start a new terminal session.
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.
If you are not logged in as the oracle user, switch user to oracle:
```
$ su - oracle
```
To determine the default shell for the oracle user, enter the following command:
```
$ echo $SHELL
```
Open the oracle user's shell startup file in any text editor:
- Bourne shell (sh), Bash shell (bash), or Korn shell (ksh):
```
$ vi .profile
```
  Note:
  If the oracle user's shell is the Bash shell, open the .bash_profile file, if it exists.
- C shell (csh or tcsh):
```
% vi .login
```
Enter or edit the following line, specifying a value of 022 for the default file mode creation mask:
```
umask 022
```
If the ORACLE_SID, ORACLE_HOME, or ORACLE_BASE environment variables are set in the file, remove the appropriate lines from the file.
Save the file and exit from the editor.
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
```
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 -h command to identify a suitable file system with sufficient free space.
2. If necessary, as a user that is a member of the admin group, 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:
```
$ sudo mkdir /mount_point/tmp
$ sudo chmod a+wr /mount_point/tmp
```
3. As the oracle user, 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
```
Enter commands similar to the following to set the ORACLE_BASE environment variable:
- Bourne, Bash, or Korn shell:
```
$ ORACLE_BASE=/Volumes/u01/app/oracle
$ export ORACLE_BASE
```
- C shell:
```
% setenv ORACLE_BASE /Volumes/u01/app/oracle
```
In these examples, /Volumes/u01/app/oracle is the Oracle base directory that you created or identified earlier.

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.

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 that the environment variables you set in this section have the correct values.