Pre-Installation Requirements

Oracle Pre-Installation Requirements

Product-Specific Requirements

Use the release notes for your platform provided with the CD-ROM to verify that your system meets hardware, disk space, operating system, kernel parameter settings, and other requirements for Oracle9i.
In order to provide you with the latest information on products, new patches, and software, Oracle Corporation now provides ongoing updates of the release notes for your platform. These updated release notes are posted on the Oracle Documentation Center. Access them at docs.oracle.com

Oracle9i Options

Product Name Platform Restrictions and Requirements

Oracle Real Application Clusters, version 9.0.1

AIX HACMP/ES Version 4.4, or higher, which requires patches IY03478, IY04109, and IY06749. PSSP 3.2 which requires patches IY04109, IY04149, and IY04767. (For IBM RS/6000 SP).

HP MC/ServiceGuard 11.09 OPS Edition.

Linux Can be installed through custom installation only. The Cluster Management Software is available in the Oracle9i package, and will be installed on the specified nodes.

Solaris For 32-bit: Sun Enterprise Cluster 2.2 or later.
For 64-bit: Sun Enterprise Cluster 3.0.

Oracle HTTP Server Powered By Apache
AIX JDK 1.2.2.04 or JDK 1.2.2 on AIX Version 4.3.3.

HP JDK 1.2.2.07. The JDK install home location is prompted during Oracle9i installation. Refer to the Hewlett-Packard company support websites for OS patches for JDK 1.1.8.05.

Linux Blackdown JDK 1.1.8_3

Solaris JDK 1.2.2_07. Refer to the Oracle9i Release Notes for Sun SPARC Solaris to determine required JRE patches.

Oracle Spatial, 9.0.1
AIX Not applicable

HP Not applicable

Linux The following software packages are required to build Spatial's sample programs only:
XFree86-devel

Solaris The following software packages are required to build Spatial's sample programs only:
Window Motif

Precompilers and Tools

Product Name Platform Restrictions and Requirements

Pro*C/C++, 9.0.1
AIX VAC 5.0 (5.0.1.1) or newer
Gcc 2.95.2 19991024

HP HP ANSI C compiler release A.11.01.20 or later
Gcc 2.9-hppa-000310
HP C++ A.03.27

Linux Gnu gcc 2.95.2

Solaris Sun Forte Workshop 6.1 109513-03
109505-02

Pro*COBOL, 1.8.75
AIX Merant Server Express 2.0.10

HP Merant Server Express 2.0.10

Linux Not applicable

Solaris Merant Server Express 2.0.10

Pro*COBOL, 9.0.1
AIX Merant Server Express 2.0.10

HP Merant Server Express 2.0.10

Linux Not applicable

Solaris Merant Server Express 2.0.10

Pro*FORTRAN, 1.8.75
AIX XL FORTRAN 6.1

HP HP FORTRAN/9000 B.11.00

Linux Not applicable

Solaris Sun WorkShop 6 update 1 Fortran 77

SQL*Module Ada, 9.0.1
AIX OCS Power ADA 3.1

HP Not applicable

Linux Not applicable

Solaris SPARC Compiler ADA 3.0

Oracle Data Migration Assistant, 9.0.1 All platforms An Oracle7 database must be at least release 7.3.4 to be migrated; an Oracle8 database must be at least release 8.0.6 to be migrated or upgraded; and an Oracle8i database must be at least version 8.1.5 to be migrated or upgraded to Oracle9i.

Network and System Management Products

All network products require the underlying software and operating system libraries for the supported network. The network software must be installed and running prior to installing the Oracle Net products.

Product Name Restrictions and Requirements
Legato Storage Manager For information on Legato requirements, see Appendix B, "Legato Storage Manager".
Oracle Advanced Security: Export Edition, 9.0.1 For information about Oracle Advanced Security authentication support requirements.
Oracle Enterprise Manager, 9.0.1 No additional system configuration is necessary for Oracle Enterprise Manager and its components.
Oracle TCP/IP with SSL Protocol Support, 9.0.1 SSL 3.0 or later.
LU6.2 protocol LU6.2 protocol support is obsolete in this release. Install and configure support for one of the following protocols:

TCP/IP

TCP/IP with SSL

Named Pipes

VI

Oracle Advanced Security

Oracle Advanced Security is an add-on product to the standard Oracle Net Server or Oracle Net Client that is available for purchase. It must be installed on both the server and the client systems. Oracle Advanced Security release 9.0.1 requires Oracle Net release 9.0.1 and supports Oracle9i Database.

Supported Authentication Methods and Requirements

Authentication Method Requirements
Kerberos MIT Kerberos Version 5, release 1.1.
The Kerberos authentication server must be installed on a physically secure machine.
RADIUS A RADIUS server that is compliant with the standards in the Internet Engineering Task Force (IETF) RFC #2138, Remote Authentication Dial In User Service (RADIUS) and RFC #2139, RADIUS Accounting.
To enable challenge-response authentication, run RADIUS on a platform that supports the Java Native Interface as specified in release 1.1 of the Java Development Kit from JavaSoft.
Oracle does not provide the RADIUS authentication server. To use it, install and configure it separately.
Secure Sockets Layer (SSL) A wallet that is compatible with the Oracle Wallet Manager version 2.1. Wallets created in earlier releases of the Oracle Wallet Manager are not forward-compatible.
Oracle Advanced Security provides and installs Secure Sockets Layer.

Installation Recommendations

Oracle Corporation recommends the following installation configuration step.

Using Optimal Flexible Architecture

Oracle Corporation recommends that the Optimal Flexible Architecture (OFA) standard be implemented when installing and configuring Oracle9i databases. The OFA standard is a set of configuration guidelines for creating fast, highly available, reliable Oracle databases that require little maintenance. Following are some of the characteristics of an OFA-compliant database:

Organizes file systems to allow for easy administration

Accommodates scalability, such as adding data into existing databases, or adding users to the system

Distributes I/O loads across disk drives to prevent performance bottlenecks caused by multiple read/write commands issued simultaneously to a single drive

Distributes applications across more than one drive to safeguard against disk failure

Ensures integrity of login home directories when home directories are added, moved, or deleted by the DBA

Allows multiple versions of the application software for concurrent execution of application software tasks
The Oracle Universal Installer supports, but does not require, OFA. The seed database included with the Database installation type of Oracle9i Database is created under a single mount point and is, therefore, not OFA-compliant.

Setup Tasks to Perform as root User

The following pre-installation setup tasks configure your system and set up accounts, groups, variables and permissions needed to run the Oracle9i database. If you choose not to perform these tasks prior to installation, then you will be given the option during the installation process to log in as root user and run the orainstRoot.sh script. The orainstRoot.sh script performs many of these setup tasks for you but might not provide a satisfactory environment for your system. Oracle Corporation recommends that you perform these steps manually.
Log in as the root user and perform the following tasks:

Configure Kernel Parameters

Review your kernel parameter settings to ensure that they meet Oracle9i requirements. If you do not do this, you might experience errors during installation, or operational errors after installation.
Review the Oracle9i release notes for your platform for information on how to check your existing parameter settings, and how to change them to the settings required for Oracle9i.

Create Mount Points

The Oracle9i installation requires at least two mount points:

one for the software

at least one for the database files

An Optimal Flexible Architecture (OFA)-compliant installation requires at least four mount points:

one for the software

at least three for the database files

All software and database mount point names use the syntax /pm, where p is a string constant and m is a unique fixed-length key (typically a two-digit number) used to distinguish each mount point. For example: /u01 and /u02, or /disk01 and /disk02.

Create UNIX Groups for Database Administrators

Oracle requires database administration groups to complete installation and to control database operations that are executed when a database is not mounted. Database administration groups enable operating system user authentication for Oracle administrative privileges, both for internal database accounts and for users to whom you may choose to grant privileges. These privileges are similar to those granted to INTERNAL in previous Oracle versions. Granting these privileges through operating system authentication allows convenience while providing greater security.
Oracle documentation refers to these administrative UNIX groups as OSDBA, typically named dba, and OSOPER, typically named oper.

You must create the OSDBA group. By default, the Oracle Universal Installer searches for a group called dba. If you choose to assign the OSDBA group privilege to a group with a name other than dba, you are prompted for the group name during installation.

Users that belong to the OSDBA group are granted SYSDBA privileges which comprise all database system privileges. These privileges include the right to grant or revoke system privileges, as well as all other administrative privileges. Grant OSDBA group membership only to database administrators.
For HP users, the OSDBA group must be granted RTSCHED, RTPRIO and MLOCK privileges. Refer to the Oracle9i Release Notes for HP for further information.
You can choose to create the OSOPER group.

Users that belong to the OSOPER group are granted SYSOPER privileges which comprise privileges required for basic system maintenance. SYSOPER privileges are a subset of those granted to SYSDBA. These include database startup and shutdown, and other privileges required for database operation. Users granted access to OSOPER group privileges may include application developers, application administrators, database users, and network administrators.

Utility to Add a Group

Platform Utility
AIX smit
HP System Administrator's Menu (SAM)
Linux groupadd
Solaris admintool or groupadd

If you perform a Custom installation of Oracle9i, or if the oracle account is not a member of a group called dba, then the Oracle Universal Installer prompts you to enter the group(s) you have created for these system privileges.

Create a UNIX Group for the Oracle Universal Installer Inventory

The ORAINVENTORY group is the group that will own the Oracle Universal Installer's oraInventory directory. The oraInventory is a repository of all installed Oracle products. The oraInventory is usually located in a directory named oraInventory, and its contents may only be modified by the Oracle Universal Installer. Any user who will be installing, removing, or patching Oracle products must be a member of the ORAINVENTORY group.
If you plan to have only one OSDBA group on a single system, then you can set the ORAINVENTORY group to the same name as the OSDBA group, which typically is dba. In this case, skip ahead to "Create a UNIX Account to Own Oracle Software.
If you plan to have multiple installations on a single system and plan on having a unique OSDBA group for each install, then you will need a separate ORAINVENTORY group. The software owner, typically oracle, must have the ORAINVENTORY group as the primary group.
You are prompted for the ORAINVENTORY group only for the first Oracle product installed on the system. Subsequent installs on the system will reuse the group name you entered the first time.

Scenario for Creating an ORAINVENTORY Group

The following is a typical business scenario for which a separate ORAINVENTORY group is needed:

You have an operating system user named oracle1 with an OSDBA group of dba1.

The oracle1 user works with a database named db11.

You have another operating system user named oracle2 with an OSDBA group of dba2.

The oracle2 user works with a database named db22.

The db11 and db22 databases are installed in different ORACLE_HOME directories.

The oracle1 user should have SYSDBA privileges in the db11 database, but should not have SYSDBA privileges in the db22 database.

The oracle2 user should have SYSDBA privileges in the db22 database, but should not have SYSDBA privileges in the db11 database.

In this situation, it is important to remember that the oraInventory can only be updated by a single operating system group. In order to maintain this central repository of installed Oracle products, the oracle1 and oracle2 users must share a common group, which Oracle Corporation refers to as the ORAINVENTORY group. The ORAINVENTORY group can be named anything, but it is usually named oinstall. In this scenario, by creating the ORAINVENTORY group and making it the primary group for both the oracle1 and oracle2 users, any new entries created by the Oracle Universal Installer for the oracle1 user can be read or updated by the Oracle Universal Installer for the oracle2 user.
Even though both oracle1 and oracle2 share Oracle software information in the ORAINVENTORY group, their different OSDBA group memberships preserve a separate database administrative access. oracle1 has dba1 as its secondary group. oracle2 has dba2 as its secondary group. The ORAINVENTORY group keeps the oraInventory repository of all Oracle executables and datafiles, but none of these files, except the oraInventory, are group writable. Only the owner of the executables or datafiles can modify them. oracle1 owns all files installed by oracle1. oracle2 owns all files installed by oracle2.

Create a UNIX Account to Own Oracle Software

The oracle account is the UNIX user account that owns Oracle9i software after installation. You must run the Oracle Universal Installer with this user account.

oracle Account Properties

Property Description
Login Name Any name, but this guide refers to it as the oracle account.
Primary GID The ORAINVENTORY group.
Secondary GID The OSDBA group.
Home Directory Choose a home directory consistent with other user home directories. The home directory of the oracle account does not have to be the same as the Oracle home directory.
Login Shell The default shell can be /usr/bin/sh, /usr/bin/csh, or /usr/bin/ksh, but the examples in this guide assume that the Bourne shell (/usr/bin/sh).

Utility to Add the oracle Account

Platform Utility
AIX smit
HP System Administrator's Menu (SAM)
Linux useradd
Solaris admintool or useradd

Use the oracle account only for installing and maintaining Oracle software. Never use it for purposes unrelated to the Oracle9i Server. Do not use the root account as the oracle account.
Sites with multiple Oracle home directories on one system may install Oracle software with the same oracle account or different ones. Each oracle account must have the ORAINVENTORY group as its primary group.

Additional Steps for Creating Multiple oracle Accounts

If you will have multiple oracle accounts that must access the same ORAINVENTORY group.

Command to Ensure oracle Account Access to ORAINVENTORY

Platform Command
AIX $ id
HP $ id
Linux $ id
Solaris $ id -a

You should see the ORAINVENTORY group after gid=. You should see the OSDBA group in the groups= list. If this is not so, ensure that both oracle1 and oracle2 accounts are listed in the /etc/groups file for the ORAINVENTORY group, that oracle1 is listed for the OSDBA1 group, and that oracle2 is listed for the OSDBA2 group.

Create a UNIX Account to Own the Apache Server

The APACHE account is a UNIX user account that owns the Apache server after installation. If you use a default configuration (one that listens to ports lower than 1024, which are reserved to root), Oracle Corporation recommends that you set up a separate account to own Apache processes after installation for security reasons. This may affect the performance of other Oracle products. Setting up the Apache Server for Installation
During installation, the user account that owns the Apache server software must be a member of the ORAINVENTORY group in order to complete installation. The Apache server also must be started by root user in order for ports reserved to root to be made available to the database and applications. However, for security reasons, Oracle Corporation recommends that provisions are made to change the Apache server group membership to a low-privileged group, and to transfer ownership of Apache server processes from root to a low-privileged account.
Improving Apache Server Security After Installation

To improve security for database and application processes, create the Apache user. Configure the Apache server to transfer ownership of its processes from root to the Apache user by using the Apache configuration parameter user, which resets user ownership of processes spawned by Apache once the server starts. Assign ownership of listener and module actions for the Apache server to this user. This post-installation process is described in Changing Group Membership of the Apache User .
Assign required access privileges to all Apache related module components to this user so as to allow apache and its modules to function as expected while minimizing security risks.
The Apache user should have minimal user privileges, and should not be a member of any groups whose files are not intended to be visible to the public. The nobody user account that many UNIX systems have may serve as a model for the Apache user. Be aware that all web servers open to the public are at risk of being compromised, and take measures accordingly to minimize exposure to that risk
Configuring the Apache user with OSDBA group or oracle user privileges compromises database security. If the Apache user needs additional rights to run programs, use the Apache suEXEC feature to obtain additional rights for the Apache user.
If a user other than root starts the Apache server, any scripts, servlets, or programs that the Apache server spawns will have the same privileges as that user.

Properties of the Apache User for Installation

Property Description
Login Name The Apache user may be given any name, but this guide refers to it as the Apache user.
Primary GID The primary group must be the same group that owns the oraInventory directory. The location of the oraInventory directory is defined in the /etc/oraInst.loc file for AIX. The location of the oraInventory directory is defined in the /var/opt/oracle/oraInst.loc file for HP, Linux, and Solaris. The default group name that has ownership of the oraInventory directory is the ORAINVENTORY group. For security reasons, this group ownership must be changed after installation. See "Changing Group Membership of the Apache User for more information.
Secondary GID The secondary group should be one in which only the Apache user is a member.
Home Directory Choose a home directory consistent with other user home directories.

Platform Utility
AIX smit
HP System Administrator's Menu (SAM)
Linux useradd
Solaris admintool or useradd

Oracle Corporation recommends caution when adding servlet classes, modifying or upgrading to Apache modules not certified with this version of Oracle9i, or upgrading the Apache server to later versions than the one certified with this version of Oracle9i. Oracle-provided patches for Apache and configurations of Apache will be supported, but it is possible for users to change Apache in ways that are difficult or impossible for Oracle Corporation to support.

Set Permissions for File Creation

It is necessary to set the umask parameter to 022 for the oracle user to ensure group and others have read and execute permissions, but not write permission, on the installed files.
Check the current setting by entering the following command:
$ umask
If the umask command does not return the value 022, then set it for the oracle user by adding the following line to the .profile or .login file:
umask 022
Execute the following command:
$ umask 022
Setup Tasks to Perform as the oracle User

Log in as the oracle account and perform the following tasks as necessary:

Set Environment Variables

Update the Environment for Current Session

Set Environment Variables

It is necessary to set the DISPLAY and PATH environment variables before running the Oracle Universal Installer. Other environmental variables such as the documentation directory or executables path may also be set before running the Oracle Universal Installer.
If an Oracle Server already exists on your system, then its settings may affect the settings that you choose for the new environment.

Variable Description Required?
DISPLAY The name, server number, and screen number of the system where the Oracle Universal Installer displays. Yes
PATH Shell's search path for executables. Yes
ORA_NLS33 Location of Global Technology character set data. No
ORACLE_BASE Directory at the top of the Oracle software and administrative file structure. No
ORACLE_DOC Directory where documentation is installed. No
ORACLE_HOME Directory containing Oracle software for a given release. No
ORACLE_SID The Oracle server instance identifier to use during installation. No

DISPLAY

The DISPLAY variable specifies the name, server number, and screen number of the system where the Oracle Universal Installer displays. On the system where you will run Oracle Universal Installer, set the DISPLAY variable to include the system name or IP address, the X server value, and the screen value used by your workstation. If you are unsure of the value to which you should set the X server and screen, use 0 (zero) for both. Do not use the hostname or IP address of the system where the software is being installed unless you are performing the installation from that system's X Window console.
If you get an Xlib error similar to "Failed to connect to server," "Connection refused by server," or "Can't open display" when starting the Oracle Universal Installer, run the following Bourne or Korn shell, or C shell commands on your X workstation.
In the session on your workstation, enter the following:
$ xhost +server_name
From your workstation where you will run the installation, connect to the server to which you intend to install Oracle9i and enter the following:
$ DISPLAY=workstation_name:0.0
$ export DISPLAY
The PATH variable specifies the shell's search path for executables. Set the shell's search path to include the information in the table below.

Shell Search Paths

Platform Paths
AIX $ORACLE_HOME/bin, /usr/bin, /etc, /usr/lbin, /usr/bin/X11, and /usr/local/bin, if it exists
HP $ORACLE_HOME/bin, /usr/ccs/bin, /usr/bin, /etc, /usr/bin/X11, and /usr/local/bin, if it exists
Linux $ORACLE_HOME/bin, /usr/bin, /bin, /usr/bin/X11/, and /usr/local/bin, if it exists
Solaris $ORACLE_HOME/bin, /usr/ccs/bin, /usr/bin, /etc, /usr/openwin/bin, and /usr/local/bin, if it exists

The ORA_NLS33 variable specifies the directory location of the *.nlb files. The *.nlb files define languages, territories, character sets, and linguistic sorting orders. Set this variable only if the *.nlb files are in a non-default location, which is $ORACLE_HOME/ocommon/nls/admin/data.
The ORACLE_BASE variable specifies the directory at the top of the Oracle software and administrative file structure. The recommended value for an OFA-compliant configuration is /software_mount_point/app/oracle. For example:
/u01/app/oracle

Set the ORACLE_BASE variable even if you are not using an OFA-compliant configuration.
The ORACLE_DOC variable specifies the directory to install the online documentation.
The ORACLE_HOME variable specifies the directory containing the Oracle software for a given release. Ensure that the value of ORACLE_HOME points to a directory that does not contain any Oracle software prior to the Oracle9i software.
The Optimal Flexible Architecture recommended value is $ORACLE_BASE/product/release. For example:
/u01/app/oracle/product/9.0.1

The ORACLE_SID variable specifies the system identifier (sid) for the Oracle server instance to use during installation. If you plan on creating a database during installation, then you have the option of setting ORACLE_SID to the value of the sid. The Oracle Universal Installer will prompt you to confirm this value.

Update the Environment for Current Session

Use a text editor to set the environment variables in the.profile or.login file of the oracle account. You can update the environment in the current shell session before beginning installation by using the appropriate shell command.
On the server where the Oracle database will be installed, enter the following commands:
$ cd
$ . $HOME/.profile

Configure Apache Server

Create the Apache user if you have not done so yet.

Additional Step for AIX

The Apache module requires JDK to be pre-installed for AIX. The installed JDK home will be prompted at the time of installation. For AIX version 4.3.3, install JDK 1.1.8 or 1.2.2.

Oracle Real Application Clusters

Perform the following pre-installation steps to install Real Application Clusters.

Steps to Perform as the root User for Real Application Clusters Installation
Log in as the root user.

Make sure you have the OSDBA group defined in the /etc/group file on all nodes in the cluster. The OSDBA group name and number, and OSOPER group if you plan to designate one, must be identical for all nodes of a UNIX cluster accessing a single database. The default UNIX group name for the OSDBA group is dba.

Create the oracle account on each node of the cluster so that:

the account has the ORAINVENTORY group as the primary group

the account has the dba group as the secondary group

the account is used only to install and update Oracle software

the account has write permissions on remote directories

Create a mount point directory on each node to serve as the top of the Oracle software directory structure so that:

the name of the mount point on each node is identical to that on the initial node

the oracle account has read, write, and execute privileges
Set up user equivalence by adding entries for all nodes in the cluster on the node from which you will run Oracle Universal Installer, including the local node, to either the .rhosts file of the oracle account or the /etc/hosts.equiv file.

To check RSH equivalence, execute a command on every node as the oracle user. For example, enter:
$ rsh another_host pwd
To check RCP equivalence, copy a small file from every node to every node. For example, enter:
$ rcp /tmp/dummy_file another_host:/tmp/dummy file
This is required for Oracle Universal Installer to know on which nodes to install Oracle Real Application Clusters.
Additional root user information for HP

Start MC/ServiceGuard by entering the following command:
$ /usr/sbin/cmruncl
Additional root user information for Solaris
Apply the Sun Cluster software patch that is provided on the Oracle9i CD-ROM. To install the patch, follow the directions provided in the opspatch directory on your CD-ROM. This patch provides the Cluster Membership Monitor (CMM) that is required before you install Oracle Real Application Clusters.
Restart the cluster management software.
For the first node, enter the following commands:
# cd /opt/SUNWcluster/bin 
# scadmin startcluster cluster_name
Run the following commands on each of the other nodes in the cluster:
# cd /opt/SUNWcluster/bin
# scadmin startnode cluster_name
Steps to Perform as the oracle user for Oracle Real Application Clusters
Log in as the oracle account.

If you are performing the pre-installation steps on HP, then verify that the MC/ServiceGuard is running by entering the following command:
$ /usr/sbin/cmviewcl
Command to Verify Cluster Membership Monitor is Running

Platform Command
AIX HACMP
$ /usr/bin/lssrc -ls grpsvcs
Verify that the CLSTRMGR_<cluster_id> has number of providers equal to the number of nodes.
PSSP 3.2
$ /usr/bin/lssrc - ls hags
Verify that css has the correct number of nodes. There should also be a local provider.
HP $ /usr/sbin/cmvicwcl
Linux $ ps -efl | egrep `watchdogd|oranm|oracm'

if all of watchdogd, oranm, and oracm program appears in the process list, Oracle cluster management software is running.

if all of watchdogd, oranm, and oracm program does not appear in the process list, restart the Oracle cluster management software.

Solaris $ ps -ef | grep clustd

if the clustd program appears in the process list, clustd is running.

if the clustd program does not appear in the process list, restart the Cluster Membership Monitor.
Check for user equivalence of the oracle account by performing a remote login (rlogin) to each node in the cluster.

If you are prompted for a password, the oracle account does not have user equivalence. Ensure that you gave the same attributes to all the nodes in the cluster. The Oracle Universal Installer cannot use the rcp command to copy Oracle products to the remote directories without user equivalence.
If you have not set up user equivalence, perform Step 5 in "Setup Tasks to Perform as root User.
Precompilers and Tools

Complete pre-installation tasks for the precompilers and tools required for your platform.

Parameters for the Pro*C/C++ Precompiler

Verify that the C compiler executable is in the PATH setting.

Pro*C/C++ Precompiler Directory

Platform Path Command
AIX /usr/bin $ which cc
HP /usr/ccs/bin $ which cc
Linux /usr/bin $ which gcc
Solaris /opt/SUNWspro/bin $ which cc

Parameters and Environment Variables for the Pro*COBOL Precompiler

Set the COBDIR environment variable to the directory where the COBOL compiler is installed.

Verify that the PATH setting includes the COBOL compiler executable.

Verify that the LD_LIBRARY_PATH setting includes the $COBDIR/lib directory.

If you do not set the COBDIR environment variable prior to starting the installation session, then Pro*COBOL precompiler linking fails.

Pro*COBOL Restriction

The use of incorrectly aligned binary data (such as COMP-1) in Pro*COBOL applications will generate unaligned access warnings that will prevent optimum compiler performance, but not affect the application's results. The warnings may appear as follows:
Unaligned access pid=12227

<unaligned> va=11ffffb84

pc=1200010e0 ra=120001060 type=ldq
Parameters for Pro*FORTRAN Precompiler

Verify that the PATH setting includes the FORTRAN compiler executable.

Pro*FORTRAN Precompiler Directory

Platform Path Command
AIX /usr/bin $ which xlf
HP /opt/Fortran/bin $ which f77
Linux Not applicable Not applicable
Solaris Not applicable $ which f77

Parameters for SQL*Module Ada

Verify that the PATH setting includes the Ada executable.

SQL*Module Ada Precompiler Directory

Platform Path Command
AIX /usr/lpp/powerada $ which ada95
HP Not applicable Not applicable
Linux Not applicable Not applicable
Solaris Not applicable $ which ada

Additional SQL*Module Ada Step for AIX

Verify that the OC Systems PowerAda 3.1 compiler configuration file has been set up. The file is located in the same directory where you have installed PowerAda. The file name will be as follows:

setup for the Korn shell

setup.csh for the C shell

Network and System Management Products

This section describes tasks that need to be completed prior to installation if you have existing network and system management products.

Setup Tasks for Oracle Net Services

If you have an existing installation of Oracle Net8 Server, then shut down all listeners before installing Oracle Net. To determine if any listeners are running, enter the following command:
$ lsnrctl status listener_name
The listener_name field is required if the listener has a name other than the default name listener.
To shut down a running listener, enter the following command:
$ lsnrctl stop listener_name
Verify Oracle Supported Protocols

Oracle Universal Installer automatically installs the TCP/IP protocol with all Oracle9i Database installations. Before installing any protocol, verify that the underlying network is functioning and configured properly.
To verify that the network is functioning properly, transfer and retrieve a test file using the ftp utility by entering the following command:
$ ftp remote_server_name
ftp> put test_filename
ftp> get test_filename
ftp> bye
Setup Tasks for Oracle Enterprise Manager

Before you install Oracle Management Server, you need to determine if you will use an existing Enterprise Manager repository or create a new Enterprise Manager repository.

IMPORTANT:
All Oracle Enterprise Manager products must be of the same release. Do not migrate the Management Server and repository until all Oracle Enterprise Manager users have upgraded their software to release 1 (9.0.1). If you migrate your Management Server and repository to release 1 (9.0.1), and do not upgrade the Enterprise Manager users' software, then the users will not be able to use their version of Enterprise Manager with the new version.

To Use an Existing Repository:

If you plan to migrate an existing Oracle Enterprise Manager repository to the current version, then backup or export the repository so that it can be recovered in the event of a unexpected error.
If you choose to use an existing Oracle Enterprise Manager repository version earlier than release 1 (9.0.1), then migrate the existing repository to release 1 (9.0.1). Review the following information to upgrade your repository.

Release 2.2 or 2.1:

Migrate the older repository to the current release by running Enterprise Manager Configuration Assistant release 1 (9.0.1).

To Create a New Repository:

If you decide to create a new release 1 (9.0.1) repository, then first install and start the database. The Enterprise Manager Configuration Assistant is automatically launched during the configuration phase of the Oracle9i Database Custom installation, the Management and Integration Management Server installation, and the Management and Integration Custom installation.

Product Name	Platform	Restrictions and Requirements
Oracle Real Application Clusters, version 9.0.1	AIX	HACMP/ES Version 4.4, or higher, which requires patches IY03478, IY04109, and IY06749. PSSP 3.2 which requires patches IY04109, IY04149, and IY04767. (For IBM RS/6000 SP).
	HP	MC/ServiceGuard 11.09 OPS Edition.
	Linux	Can be installed through custom installation only. The Cluster Management Software is available in the Oracle9i package, and will be installed on the specified nodes.
	Solaris	For 32-bit: Sun Enterprise Cluster 2.2 or later. For 64-bit: Sun Enterprise Cluster 3.0.
Oracle HTTP Server Powered By Apache	AIX	JDK 1.2.2.04 or JDK 1.2.2 on AIX Version 4.3.3.
	HP	JDK 1.2.2.07. The JDK install home location is prompted during Oracle9i installation. Refer to the Hewlett-Packard company support websites for OS patches for JDK 1.1.8.05.
	Linux	Blackdown JDK 1.1.8_3
	Solaris	JDK 1.2.2_07. Refer to the Oracle9i Release Notes for Sun SPARC Solaris to determine required JRE patches.
Oracle Spatial, 9.0.1	AIX	Not applicable
	HP	Not applicable
	Linux	The following software packages are required to build Spatial's sample programs only: XFree86-devel
	Solaris	The following software packages are required to build Spatial's sample programs only: Window Motif

Product Name	Platform	Restrictions and Requirements
Pro*C/C++, 9.0.1	AIX	VAC 5.0 (5.0.1.1) or newer Gcc 2.95.2 19991024
	HP	HP ANSI C compiler release A.11.01.20 or later Gcc 2.9-hppa-000310 HP C++ A.03.27
	Linux	Gnu gcc 2.95.2
	Solaris	Sun Forte Workshop 6.1 109513-03 109505-02
Pro*COBOL, 1.8.75	AIX	Merant Server Express 2.0.10
	HP	Merant Server Express 2.0.10
	Linux	Not applicable
	Solaris	Merant Server Express 2.0.10
Pro*COBOL, 9.0.1	AIX	Merant Server Express 2.0.10
	HP	Merant Server Express 2.0.10
	Linux	Not applicable
	Solaris	Merant Server Express 2.0.10
Pro*FORTRAN, 1.8.75	AIX	XL FORTRAN 6.1
	HP	HP FORTRAN/9000 B.11.00
	Linux	Not applicable
	Solaris	Sun WorkShop 6 update 1 Fortran 77
SQL*Module Ada, 9.0.1	AIX	OCS Power ADA 3.1
	HP	Not applicable
	Linux	Not applicable
	Solaris	SPARC Compiler ADA 3.0
	Oracle Data Migration Assistant, 9.0.1	All platforms	An Oracle7 database must be at least release 7.3.4 to be migrated; an Oracle8 database must be at least release 8.0.6 to be migrated or upgraded; and an Oracle8i database must be at least version 8.1.5 to be migrated or upgraded to Oracle9i.

Product Name	Restrictions and Requirements
Legato Storage Manager	For information on Legato requirements, see Appendix B, "Legato Storage Manager".
Oracle Advanced Security: Export Edition, 9.0.1	For information about Oracle Advanced Security authentication support requirements.
Oracle Enterprise Manager, 9.0.1	No additional system configuration is necessary for Oracle Enterprise Manager and its components.
Oracle TCP/IP with SSL Protocol Support, 9.0.1	SSL 3.0 or later.
LU6.2 protocol	LU6.2 protocol support is obsolete in this release. Install and configure support for one of the following protocols: TCP/IP TCP/IP with SSL Named Pipes VI

Platform	Utility
AIX	smit
HP	System Administrator's Menu (SAM)
Linux	groupadd
Solaris	admintool or groupadd

Property	Description
Login Name	Any name, but this guide refers to it as the oracle account.
Primary GID	The ORAINVENTORY group.
Secondary GID	The OSDBA group.
Home Directory	Choose a home directory consistent with other user home directories. The home directory of the oracle account does not have to be the same as the Oracle home directory.
Login Shell	The default shell can be /usr/bin/sh, /usr/bin/csh, or /usr/bin/ksh, but the examples in this guide assume that the Bourne shell (/usr/bin/sh).

Property	Description
Login Name	The Apache user may be given any name, but this guide refers to it as the Apache user.
Primary GID	The primary group must be the same group that owns the oraInventory directory. The location of the oraInventory directory is defined in the /etc/oraInst.loc file for AIX. The location of the oraInventory directory is defined in the /var/opt/oracle/oraInst.loc file for HP, Linux, and Solaris. The default group name that has ownership of the oraInventory directory is the ORAINVENTORY group. For security reasons, this group ownership must be changed after installation. See "Changing Group Membership of the Apache User for more information.
Secondary GID	The secondary group should be one in which only the Apache user is a member.
Home Directory	Choose a home directory consistent with other user home directories.

Variable	Description	Required?
DISPLAY	The name, server number, and screen number of the system where the Oracle Universal Installer displays.	Yes
PATH	Shell's search path for executables.	Yes
ORA_NLS33	Location of Global Technology character set data.	No
ORACLE_BASE	Directory at the top of the Oracle software and administrative file structure.	No
ORACLE_DOC	Directory where documentation is installed.	No
ORACLE_HOME	Directory containing Oracle software for a given release.	No
ORACLE_SID	The Oracle server instance identifier to use during installation.	No

Platform	Paths
AIX	$ORACLE_HOME/bin, /usr/bin, /etc, /usr/lbin, /usr/bin/X11, and /usr/local/bin, if it exists
HP	$ORACLE_HOME/bin, /usr/ccs/bin, /usr/bin, /etc, /usr/bin/X11, and /usr/local/bin, if it exists
Linux	$ORACLE_HOME/bin, /usr/bin, /bin, /usr/bin/X11/, and /usr/local/bin, if it exists
Solaris	$ORACLE_HOME/bin, /usr/ccs/bin, /usr/bin, /etc, /usr/openwin/bin, and /usr/local/bin, if it exists

Platform	Command
AIX	HACMP $ /usr/bin/lssrc -ls grpsvcs Verify that the CLSTRMGR_<cluster_id> has number of providers equal to the number of nodes. PSSP 3.2 $ /usr/bin/lssrc - ls hags Verify that css has the correct number of nodes. There should also be a local provider.
HP	$ /usr/sbin/cmvicwcl
Linux	$ ps -efl \| egrep `watchdogd\|oranm\|oracm' if all of watchdogd, oranm, and oracm program appears in the process list, Oracle cluster management software is running. if all of watchdogd, oranm, and oracm program does not appear in the process list, restart the Oracle cluster management software.
Solaris	$ ps -ef \| grep clustd if the clustd program appears in the process list, clustd is running. if the clustd program does not appear in the process list, restart the Cluster Membership Monitor.

Platform	Path	Command
AIX	/usr/bin	$ which cc
HP	/usr/ccs/bin	$ which cc
Linux	/usr/bin	$ which gcc
Solaris	/opt/SUNWspro/bin	$ which cc

Platform	Path	Command
AIX	/usr/bin	$ which xlf
HP	/opt/Fortran/bin	$ which f77
Linux	Not applicable	Not applicable
Solaris	Not applicable	$ which f77

Platform	Path	Command
AIX	/usr/lpp/powerada	$ which ada95
HP	Not applicable	Not applicable
Linux	Not applicable	Not applicable
Solaris	Not applicable	$ which ada