Skip Headers
Oracle® Content Database Installation Guide
10g Release 1 (10.2.0.0.0) for HP-UX PA-RISC (64-Bit)

Part Number B31416-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

B Basic Installation Information

This appendix discusses necessary installation information associated with installing Oracle Content DB, and includes the following topics:

B.1 Installation Basics

This section discusses some of the basic principles regarding installing Oracle Content DB, including:

B.1.1 Contents of the Oracle Content DB Media Pack

The Oracle Content DB Media pack includes the following disks:

  • Oracle Content DB software and Oracle Content DB documentation

  • Oracle Drive client for Windows

  • OracleAS Infrastructure components, including Oracle Internet Directory and OracleAS Single Sign-On

B.1.2 Oracle Home Directory

The directory in which you install Oracle Content DB is referred to as the Oracle home in this document. During the installation, you must specify the full path and a name for the Oracle home.

For example, you can install Oracle Content DB in the /home/oracle/OraHome_ContentDB directory, and you can name it ContentDBHome.


Note:

Spaces are not allowed in the Oracle home directory path. For example, you cannot install in the /etc/oracle/Content DB directory because of the space character in Content DB.

Oracle Universal Installer does not check for this until several screens after you have entered the path.


B.1.3 Using Symbolic Links

You can create symbolic links before installing Oracle Content DB and use them during installation. For example, you can use the following commands before starting the installation:

mkdir /home/basedir
ln -s /home/basedir /home/linkdir

When you run Oracle Universal Installer, you can specify /home/linkdir as the Oracle home.

After installation, you cannot create symbolic links to the Oracle home. You also cannot move the Oracle home to a different location and create a symbolic link to the original Oracle home.

B.1.4 Installing Any Oracle Product for the First Time

Oracle recommends that you create an operating system user (referred to in this document as the oracle user) to perform all tasks related to installation of Oracle products.

If Oracle Content DB is the first Oracle product to be installed on a computer, Oracle Universal Installer displays a screen where you specify the location of an inventory directory (the oraInventory directory). This inventory directory is used by the installer to keep track of all Oracle products installed on the computer. The inventory directory is different from the Oracle home for Oracle Content DB.

Users in the oinstall group install Oracle products. To ensure that other users in the oinstall group have access to the inventory directory, do not use the home directory of the oracle user because home directories might not have the proper permissions set up for the oinstall group. Instead, create the inventory directory in the /var/opt/oracle directory.

If an Oracle product was installed previously on the computer, then the installer uses the existing inventory directory. To ensure that you have write permissions on that directory, run Oracle Universal Installer as the same oracle user who installed the existing Oracle product.

B.2 Installation of the Oracle Content DB Middle Tier

Installation of the Oracle Content DB middle tier is done through Oracle Universal Installer. Before the Oracle Content DB middle tier can be installed, however, both OracleAS Infrastructure and Oracle Database must both be installed, and the database must be registered with Oracle Internet Directory.

B.3 Mounting DVDs

This section discusses mounting DVDs. It includes the following topics:

B.3.1 Mounting DVD-ROM for HP-UX PA-RISC

Mount the first DVD of the appropriate installation to begin. Mount the subsequent disk or disks, if required. Follow these steps to mount the Oracle DVD-ROM manually:

  1. Place the DVD in the DVD-ROM drive.

  2. Log in as the root user and create a DVD-ROM mount point directory, if one does not already exist, by using the following commands:

    $ su root
    # /usr/bin/mkdir dvdrom_mount_point_directory
    

    Note:

    Use the following command to determine the device name:
    $ ioscan -fun -C disk
    
    

    The output is similar to the following:

    disk     10  10/12/5.2.0   sdisk       CLAIMED   DEVICE    TOSHIBA DVD-ROM XM-5701TA 
    /dev/dsk/c0t6d0   /dev/rdsk/c0t6d0
    
    

    If there is no entry in the /etc/pfs_fstab file for your DVD-ROM device, then you must add one. As the root user, use a system editor to add a line to the /etc/pfs_fstab file following this format:

    device_file mount_point filesystem_type
    
    

    In the preceding format, the first entry is the DVD-ROM device and the second entry indicates the mount point.

    The device_file in this example is /dev/dsk/c0t6d0. For a DVD-ROM device with the path /dev/dsk/c0t6d0, enter the following:

    /dev/dsk/c0t6d0 /DVD pfs-rrip xlat=unix 1 0
    

  3. Mount the DVD by entering the following command:

    # /usr/sbin/mount -F cdfs -o rr /dev/dsk/cxdytz /DVD
    
    

    In the preceding example, /DVD is the disc mount point directory and /dev/dsk/cxdytz is the device name for the disc device, for example /dev/dsk/c0d6t0.

  4. Log out of the root account.

    # exit
    
    

If you run Oracle Universal Installer while the current working directory is on the DVD, then follow these steps to mount the next DVD:

  1. Change to the system root directory and log in as the root user:

    $ cd /
    $ su root
    
    
  2. To unmount the DVD, use the following command:

    # /usr/sbin/umount /DVD
    
    
  3. Remove the DVD from the DVD-ROM drive.

  4. If required, insert the required DVD in to the DVD-ROM drive and mount it using the following command:

    # /usr/sbin/mount /DVD
    

B.4 Understanding Oracle Universal Installer

Oracle Content DB uses Oracle Universal Installer to guide you through each step of the installation process. Oracle Universal Installer provides the following features:

This section describes the following Oracle Universal Installer features:

B.4.1 oraInventory Directory and Installation Session Log Files

Oracle Content DB creates the oraInventory directory the first time it is run on a computer. The oraInventory directory keeps an inventory of products that Oracle Content DB installs on your computer, as well as other installation information. If you have previously installed Oracle products, you might already have an oraInventory directory.

The operating system group that owns Oracle Content DB must have permission to write to the oraInventory directory. Attempts to run Oracle Content DB without this permission fail.

The location of oraInventory is defined in the oraInst.loc file, located in the /var/opt/oracle directory on your operating system.

The log file of the most recent installation is located in the logs directory, under the oraInventory directory, in the following format:

installActionstoday's_date_time.log

In the preceding format, today's_date_time is the date and time of installation.

Do not delete or manually alter the oraInventory directory or its contents. Doing so can prevent Oracle Universal Installer from locating products that you have installed on your system.


Note:

The make.log file in the $ORACLE_HOME/install directory contains a log of every make file action executed during the installation process. The make.log file also records any link errors during installation. Do not delete or alter the make.log file.

B.4.2 Subsequent Installations with Oracle Universal Installer

If you plan to install a subsequent Oracle Content DB or Oracle Application Server instance on the same host, Oracle recommends the following steps:

  1. Review Chapter 4, "Preinstallation Requirements for Oracle Content DB Middle Tier".

  2. Stop Oracle Enterprise Manager 10g.

  3. Ensure that all other previously installed Oracle Content DB instances are running when you begin installation.

  4. Specify a different Oracle home than the first Oracle Content DB installation.

  5. Use the same oraInventory directory for subsequent Oracle Content DB installations.

B.4.3 Starting Oracle Universal Installer

To start Oracle Universal Installer:

  1. If your computer does not mount DVDs automatically, you must mount the DVD manually.

  2. Log in as the oracle user.

  3. Insert the Oracle Content DB DVD-ROM in to the DVD-ROM drive.


    Notes:

    • Ensure that you are not logged in as the root user when you start Oracle Universal Installer. If you perform the installation as the root user, only the root user will have permissions to manage Oracle Content DB.

    • Do not use dvd_mount_point as your working directory when you start Oracle Universal Installer. If you do, you cannot eject the first DVD during the installation step to insert the second DVD, if required.

    • Oracle recommends using the same operating system user account when installing additional instances of Oracle Content DB on the same host.


  4. Insert the first DVD in to the DVD-ROM drive.

  5. Run Oracle Universal Installer, as follows:

    $ cd
    $ /dvdrom/runInstaller
    

B.4.4 Starting Oracle Universal Installer from the Command Line

This section includes information for running Oracle Universal Installer from the command line.

To start Oracle Universal Installer from the command line:

runInstaller [options] [CommandLineVariable=Value]

In the preceding syntax, [options] can have the following values:

  • -help: Displays help topics for using the subsequent command

  • -silent: Used for silent mode operations. The input parameters can include a response file name or list of command-line variable value pairs

  • -responseFile path: Used for specifying the response file name and directory path to the response file

  • -formCluster: Used for installing the Oracle Clusterware to form the cluster

  • -remoteshell path: Used only for installing clusters, this parameter specifies the path to the remote shell program on the local cluster node

  • -remotecp path: Used only for installing clusters, this parameter specifies the path to the remote copy program on the local cluster node

  • -record -destinationFile path: Used for the record mode operation, this parameter specifies the destination file path, where information is recorded

  • -deinstall: Used for deinstallation operations

  • -debug: Used for retrieving debug information from Oracle Universal Installer

  • -ignoreSysPrereqs: Used for ignoring the results of system prerequisite checks

  • -executeSysPrereqs: Used for executing system prerequisite checks and exiting (a subset of the checks described in "Prerequisite Checks Performed by Oracle Universal Installer" is performed by this option)

  • -paramFile: Used for specifying the location of oraparam.ini file used by Oracle Universal Installer

  • -clone: Used for creating an $ORACLE_HOME copy that matches its current environment

  • -force: Used for allowing silent mode installation in to a nonempty directory

  • -noconsole: Used for suppressing the display of messages to console

  • -removeAllPatches: Used for removing all interim patches from the $ORACLE_HOME directory

  • -ignorePatchConflicts: Used for ignoring all conflicts with existing interim patches during an upgrade (the conflicting interim patches are removed from the $ORACLE_HOME directory)

  • -addNode: Used for adding nodes to the installation

  • -removeHome: Used for removing $ORACLE_HOME directories from the Oracle Universal Installer inventory

B.5 Installing Support for Additional Languages

By default, Oracle Universal Installer installs Oracle Content DB with text in English and in the operating system language. However, you should install support for all languages during installation by selecting all of the languages provided in the Available Languages list and adding them to the Selected Languages list on the Language Selection screen.


Note:

You cannot install support for additional languages after Oracle Content DB is installed. You must install support for additional languages during the installation.

If you install and run Oracle Content DB in an environment that uses a language that you did not install, the user interface may display text in that language or in English. It may also display square boxes, caused by missing fonts, instead of text.

To install Oracle Content DB in a language other than English, you must set the LANG variable to the appropriate language.

To set the LANG variable:

B.6 Oracle Content DB Instances and Instance Names

This section includes the following topics:

When you install Oracle Content DB, an instance of Oracle Content DB is created and Oracle Universal Installer prompts you to provide a name for that instance. For example, you can name the instance cdbinstance. This name can be different from the Oracle home name. You cannot change the instance name after installation.

Oracle Content DB appends the host name and domain name to the given instance name to form a complete instance name. For example, if you are installing an instance on a computer named c1, and you name the instance cdb1, the full name of the instance is cdb1.c1.foo.com, assuming the domain name is foo.com.

Valid characters in instance names consist only of the following:

There is no restriction for the length of instance names.

B.6.1 Restrictions on Oracle Content DB Instance Names

Do not use the host name of the computer when naming Oracle Content DB instances.

If you are planning to install Oracle Content DB in a high availability cluster, the instance name cannot contain any of the following:

  • Host name or IP address of any computer in the cluster

  • Oracle home of any Oracle Content DB installation in the cluster

B.6.2 How Oracle Content DB Uses Instance Names

Instance names are important because Oracle Content DB uses them to uniquely identify instances. So, if you install multiple Oracle Content DB instances on the same computer, you must give each instance a different name.

When you administer Oracle Content DB using Oracle Enterprise Manager 10g, the instance name displays on the screens. Click an instance name to see details about the instance, such as whether the instance is running or stopped, and the log files for the instance.

There is also a command-line tool called opmnctl used to administer Oracle Content DB instances, some commands of which require an instance name as a parameter.


See Also:

Oracle Application Server Administrator's Guide for more details about opmnctl

B.7 The ias_admin User and Restrictions On Its Password

During installation of Oracle Content DB, Oracle Universal Installer prompts you to specify the password for the ias_admin user. The ias_admin user is the administrative user for Oracle Content DB instances. To manage Oracle Content DB instances using Oracle Enterprise Manager 10g, you log in as ias_admin.

You can install multiple Oracle Content DB instances on a given computer with a unique name for each instance, but the name of the administrative user is ias_admin for all instances. The password for the ias_admin user can be different for each instance.

The password for the ias_admin user must conform to the password policy of Oracle Internet Directory:

Remember this password because you must enter it in the following cases:

If you forget the ias_admin password, it can be reset.


See Also:

Oracle Application Server Administrator's Guide for more information about resetting the ias_admin password

B.8 Where Does Oracle Universal Installer Write Files?

Oracle Universal Installer writes files to the directories listed in Table B-1.

Table B-1 Directories to Which Oracle Universal Installer Writes Files

Directory Description

Oracle home

This directory contains Oracle Content DB files. You specify this directory during installation.

Inventory

When you install the first Oracle product on a computer, you specify this directory. Oracle Universal Installer uses this directory to keep track of Oracle products that are installed on the computer. In subsequent installations, Oracle Universal Installer uses the same inventory directory.

/var/opt/oracle

This directory contains information about locations of Oracle homes on the computer.

This directory also contains files that provide information for Oracle Enterprise Manager 10g.

/tmp

Oracle Universal Installer writes files needed during installation to a temporary directory. By default, the temporary directory is /tmp. To specify a different directory, set the TMP environment variable.

See Also: TMP and TMPDIR for more information about setting a different temporary directory.


B.9 Logging In as root During Installation of Oracle Content DB

At least once during the installation of Oracle Content DB, the installer prompts you to log in as the root user and run a script. You must be the root user because the script must write to files and directories not owned by the oracle user or any other user installing the product.

When prompted by Oracle Universal Installer, you will run the root.sh script in a separate window. This script creates files in the local bin directory, which is /usr/local/bin, by default.

For noninteractive installation, after the Finished running generic part of the root.sh script and Now product-specific root actions will be performed messages display, exit the root user and return to the current installation screen.

The root.sh script also detects settings of the ORACLE_OWNER, ORACLE_HOME, and ORACLE_SID environment variables.

If the script finds files of the same name, it prompts you to overwrite the existing files. You should first back up these files, which you can do from another window, and then overwrite them.

B.10 Connecting to Oracle Internet Directory Through SSL

Oracle Content DB can communicate with Oracle Internet Directory using Secure Sockets Layer (SSL). The default setting during the installation does not use SSL. On screens where you specify the host name and port for Oracle Internet Directory, you can select Use Only SSL Connections with This Oracle Internet Directory and provide the Oracle Internet Directory SSL port.

B.11 Modifying Other Oracle Content DB Instances During Installation

During the installation of an Oracle Content DB instance, you should not change the configuration or passwords of other Oracle Content DB installations in your environment.

B.12 Understanding the Order of Installation

This section provides an overview of the order in which Oracle Content DB must be installed.

Certain Oracle products must be installed prior to installing Oracle Content DB. The order of installation of the various products, including Oracle Content DB, is as follows:

  1. Install Oracle Application Server infrastructure.


    See Also:

    Oracle Application Server Installation Guide for installation details

  2. Install Oracle Database 10g.

  3. Register the database with Oracle Internet Directory.

  4. Install Oracle Content DB.