Skip Headers
Oracle® Content Database Installation Guide
10g Release 1 (10.2.0.0.0) for Solaris Operating System (SPARC 64-Bit)
Part Number B31415-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

4 Preinstallation Requirements for Oracle Content DB Middle Tier


Note:

Prior to installing Oracle Content DB middle tier, you must first install OracleAS Infrastructure (which contains Oracle Identity Management) and Oracle Database. Refer to Chapter 3, "Installing OracleAS Infrastructure and Oracle Database" for more details.

This chapter discusses necessary requirements that must be met prior to installing Oracle Content DB.


See Also:

This chapter includes the following topics:

4.1 Oracle Content DB Hardware Requirements

This section lists the hardware configurations required to install Oracle Content DB.

Oracle Universal Installer checks these requirements at the start of the installation process and warns you if any of these requirements are not met. Therefore, to save time, you can manually check only the remaining requirements.

You can also run the system checks performed by Oracle Universal Installer without doing an installation by running the following command, where the runInstaller executable is on the Oracle Content DB DVD.

$ mount_point/runInstaller -executeSysPrereqs

The results are displayed on the screen as well as written to a log file.


See Also:

"Prerequisite Checks Performed by Oracle Universal Installer" for more information about the subset of checks performed

Table 4-1 Hardware Requirements for Solaris

Item Requirement Checked by Oracle Universal Installer

Operating system

Solaris 8, Solaris 9, or Solaris 10

Yes

Processor type

SPARC Processor. The processor must have a v9 architecture.

No

Processor speed

450 MHz or greater recommended. Oracle recommends a multiple CPU computer.

To determine the processor speed, enter the psrinfo command with the -v option:

# /usr/sbin/psrinfo -v

No

Network

You can install Oracle Content DB on a computer that is connected to a network, or on a "standalone" computer (not connected to the network).

If you are installing Oracle Content DB on a standalone computer, you can connect the computer to a network after installation. You have to perform some configuration tasks when you connect it to the network; see the Oracle Content Database Administrator's Guide for details.

No

IP

The computer's IP address must be static. Oracle Content DB does not support computers using Solaris DHCP.

Oracle Content DB supports DHCP computers on Linux and Microsoft Windows.

No

Hostname

Ensure that your hostnames are not longer than 255 characters.

No

Support for 32-bit and 64-bit applications

The operating system must be configured to support 32-bit and 64-bit applications. To check this, run the isainfo command with the -v option:

prompt> /usr/bin/isainfo -v
64-bit sparcv9 applications
32-bit sparc applications

If the output does not show both lines, you need to reconfigure your computer. Check with your system administrator.

No

Processor Type

The processor must have a SPARC v9 architecture. This is because Oracle Content DB uses the Sun Java 1.4.2 HotSpot Server VM, which no longer supports SPARC v8 and older processors.

To determine the processor type, run the psrinfo command with the -v option. The output must show "sparcv9":

prompt> /usr/sbin/psrinfo -v
Status of processor 0 as of: 02/10/03 13:21:20
  Processor has been on-line since 02/04/03 15:45:07.
  The sparcv9 processor operates at 450 MHz,
        and has a sparcv9 floating point processor.

No

Processor Speed

450 MHz or greater recommended. Oracle recommends a multiple CPU computer.

To determine the processor speed, run the psrinfo command with the -v option:

prompt> /usr/sbin/psrinfo -v
Status of processor 0 as of: 02/10/03 13:21:20
  Processor has been on-line since 02/04/03 15:45:07.
  The sparcv9 processor operates at 450 MHz,
        and has a sparcv9 floating point processor.

No

Memory

The memory requirement for Oracle Content DB is 3 GB

Notes:

The installer checks the amount of memory on your computer and will warn you if your computer does not meet the minimum memory requirements.

To determine the amount of memory, use the prtconf command:

prompt> /usr/sbin/prtconf | grep Memory

Yes

Disk space

The disk space requirement for Oracle Content DB is 10 GB:

To determine the amount of free disk space, use the df command:

prompt> df -k dir

Replace dir with the directory where you plan to install Oracle Content DB or with the parent directory if the directory does not exist yet. For example, if you plan to install Oracle Content DB in /opt/oracle/infra, replace dir with /opt/oracle or /opt/oracle/infra.

No

Space in /tmp directory

256 MB

To determine the amount of free space in the /tmp directory, use the df command:

prompt> df -k /tmp

If the /tmp directory does not have enough free space, you can specify a different directory by setting the TMP environment variable. See TMP for details.

Yes

Swap space

1.5 GB or greater of available swap space

To determine the amount of available swap space, use the swap command:

prompt> /usr/sbin/swap -l

The value in the "free" column indicates the number of free blocks, where a block is 512 bytes. To convert blocks to KB, divide the number by 2. For example, 2,000,000 free blocks is equivalent to 1,000,000 KB.

If you do not have enough swap space, perform the following tasks:

  1. Log in as the root user, and create an empty swap file:

    prompt> su
Password: root_user_password
# mkfile sizem swap_file_name

    Append an "m" to the size to specify the size in megabytes (example: 900m). The minimum size of this file must be greater than the difference between the currently available swap space and required swap space. For example, if you have 100 MB of free swap space, then this swap file must be at least 1400 MB.

  2. Add the file to the swap space using the following command:

    # /usr/sbin/swap -a swap_file_name

  3. Add a line to /etc/vfstab file. If you do not add the line, the new swap space will not persist when you restart the computer.

    /path/to/swap/file   -   -   swap   -   no   -

    Replace /path/to/swap/file with the location of the swap file.

  4. Verify the new swap space size:

    prompt> /usr/sbin/swap -l

Yes

Monitor

256 color display

To determine your monitor's display capabilities:

  1. Check that the DISPLAY environment variable is set properly. See DISPLAY for details. To test, see if you are able to run /usr/openwin/bin/xclock.

  2. Run the xwininfo command.

    prompt> /usr/openwin/bin/xwininfo

    Look for the "Depth" line. You need a depth of at least 8 (bits per pixel).

Yes

4.1.1 Running Multiple Instances of Oracle Content DB on One Computer

If you are running multiple instances of Oracle Content DB on one computer, each corresponding instance of Application Server Control can consume significant memory. To free up memory, configure a single instance of Application Server Control to manage multiple instances of Oracle Content DB.

4.2 Oracle Content DB Software Requirements

Oracle Content DB depends upon Oracle Identity Management (part of OracleAS Infrastructure) and Oracle Database 10g. The Oracle Database must be registered with Oracle Internet Directory.


See Also:

Chapter 3, "Installing OracleAS Infrastructure and Oracle Database"

Oracle Universal Installer checks that your computer includes any required operating system patches. If Oracle Universal Installer determines that some required patches are missing, it displays an error.

The Oracle Content DB middle tier runs in Oracle Application Server 10g Release 2 (10.1.2.0.2). For information about operating system patches and packages for Solaris, refer to Section F, "Operating System Patches and Packages".

4.3 Kernel Parameter Settings

The computers on which you plan to install Oracle Content DB require their kernel parameters to be set to the minimum values shown in Table 4-2.

Kernel parameter values are stored in the /etc/system file. If your /etc/system file does not specify the parameters, you have to add lines to the file to specify them.


Notes:

  • If any kernel parameter values do not meet the requirements, the installer displays an error message. You will not be able to continue the installation until you update the kernel parameters to the required values.

  • If you update kernel parameter values, you need to restart your computer for the new values to take effect.

Table 4-2 Kernel Parameters for Solaris Systems

Parameter Line in /etc/system Showing the Minimum Value Description

rlim_fd_max

set rlim_fd_max=65536

Defines the hard limit on file descriptors that a single process can have open.

semmni

set semsys:seminfo_semmni=100

Defines the maximum number of semaphore sets in the entire system.

semmns

set semsys:seminfo_semmns=1024

Defines the maximum semaphores on the system. The 256 is only a minimum value for computers that will be running a single database.

semmsl

set semsys:seminfo_semmsl=256

Defines the minimum recommended value, for initial installation only.

shmmax

set shmsys:shminfo_shmmax=4294967295

Defines the maximum allowable size of one shared memory segment (4 GB = 4294967295).

shmmin

set shmsys:shminfo_shmmin=1

Defines the minimum allowable size of a single shared memory segment.

Note: This parameter is not used in Solaris 9.

shmmni

set shmsys:shminfo_shmmni=100

Defines the maximum number of shared memory segments in the entire system.

shmseg

set shmsys:shminfo_shmseg=10

Defines the maximum number of shared memory segments one process can attach.

Note: This parameter is not used in Solaris 9.

To add or update kernel parameter values:

  1. Login at the root user on the computer where you need to change the values.

  2. Make a backup copy of the /etc/system file. For example, the following command makes a backup copy called system.back.

    # cp /etc/system /etc/system.back

  3. Using a text editor such as vi or emacs, update the values or add new lines in the /etc/system file as necessary. For example, the following lines show sample values for the parameters:

    set semsys:seminfo_semmni=300
set semsys:seminfo_semmns=1024
set semsys:seminfo_semmsl=256
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=512
set shmsys:shminfo_shmseg=150

    Tip:

    The comment character for the /etc/system file is the asterisk (*), not #.

  4. Restart the computer for the new values to take effect.

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


Note:

On Solaris 10, you are not required to make changes to the /etc/system file to implement the System V TPC. Solaris 10 uses the resource control facility for its implementation.

Table 4-3 Kernel Parameter and Resource Control Settings for Solaris 10 Systems

Parameter Replaced by Resource Control Recommended Value

noexec_user_stack

NA

1

semsys:seminfo_semmni

project.max-sem-ids

100

semsys:seminfo_semmsl

project.max-sem-nsems

256

shmsys:shminfo_shmmax

project.max-shm-memory

4294967295

shmsys:shminfo_shmmni

project.max-shm-ids

100

Determining the Minimum Value for the semmns Parameter

If you are installing the Oracle Content DB on a computer that is not already running an Oracle Database (that is, the Infrastructure will be the only component running on the computer), then set the semmns parameter to a minimum of 256.

If you are installing Oracle Content DB on a computer that is already running an Oracle Database, then set the semmns parameter to the sum of the processes initialization parameter for each Oracle Database (including the Infrastructure), then adding the largest value twice, and then adding an additional 10 for each database.

The default value of the processes parameter for the Oracle Database is 250.

Example: The computer is already running an Oracle Database, and its processes parameter is set at 250. In this case, you must set the semmns parameter to at least 920, which is explained as follows:

To determine the value of the processes parameter for an Oracle Database, enter the following command in SQL*Plus:

# sqlplus "sys/password as sysdba"
SQL> show parameters processes

In the preceding syntax, password specifies the password for the SYS user.

To add or update kernel parameter values for Solaris 10 operating systems:

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

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

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

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

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

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

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

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

    Note:

    On Solaris 10, the changes made by the prctl command are not effective permanently. If you reboot the computer, then the changes you made made by using this command disappear.

    If you want to make the changes permanent, then you must use the projmod command, as follows, and then you must reboot the computer for the chnages to take effect:

    # projmod -s -K "project.max-shm-memory=(privileged,6GB,deny)\
'user.root'
# projmod -s -K "project.max-sem-ids=(privileged,256,deny)" \
'user.root'

4.4 Ports Used by Oracle Content DB

Oracle Content DB and components of Oracle Application Server (such as Oracle HTTP Server, Oracle Application Server Web Cache, and Oracle Enterprise Manager 10g) use ports. Oracle Universal Installer assigns default port numbers or you can specify port numbers, including the port numbers under 1024.


See Also:

Appendix D, "Default Port Numbers for Oracle Content DB" for a complete list of default port numbers

This section includes the following topics:

Why the Default Port for Oracle HTTP Server Is Port 7777 and Not Port 80

By default, Oracle Universal Installer configures Oracle HTTP Server to use port 7777, not port 80. Port 7777 is the default port because on Solaris, components that use port numbers lower than 1024 require additional steps to be done as the root user before the components can run. Because Oracle Universal Installer does not have root access, it must use a port greater than 1024.

4.4.1 Checking If a Port Is in Use

To check if a port is being used, enter the netstat command to show the used port as follows:

$ netstat -an | grep port_number

Replace port_number with the port number you want to check.


Note:

You can also use the /usr/local/bin/lsof -i :port_number command.

4.4.2 Using Default Port Numbers

To use the default port numbers for Oracle Application Server components, such as Oracle HTTP Server, Oracle Application Server Web Cache, and Oracle Enterprise Manager 10g, you do not have to do anything.


Notes:

  • Oracle Universal Installer assigns the default ports only if the ports are not in use by other applications. If a default port is in use, Oracle Universal Installer tries other ports in the port number range for the component. For example, the default, non-SSL port for Oracle HTTP Server is port 7777. If this port is in use by another application, Oracle Universal Installer assigns a port in the 7777 - 7877 range.

  • If you plan to install multiple instances of Oracle products on the same computer, only the first instance that you install on the computer will use the default ports. When you install additional instances, Oracle Universal Installer will detect that the default ports are already in use by the first instance, and it will assign other ports to the additional instances.


See Also:

you can also refer to the Oracle Application Server Installation Guide for more information about ports and port numbers.

4.5 Operating System Groups

Create operating system groups in the following situations:


See Also:

Your operating system documentation or contact your system administrator for more information about creating operating system groups..


See Also:

you can also refer to the Oracle Application Server Installation Guide for more information about creating operating system groups.

4.6 Operating System Users

Create an operating system user to install and upgrade Oracle products. This guide refers to this user as the oracle user. The oracle user running Oracle Universal Installer must have write permission for the following directories:

If the computer contains other Oracle products, you might already have a user for this purpose. Look in the /var/opt/oracle/oraInst.loc file. This file lists the location of the inventory directory and the group who owns it. If the file does not exist, the computer does not have any Oracle products installed.

If you do not already have a user for installing Oracle products, create a user with the properties listed in Table 4-4.

Table 4-4 Properties of the Operating System User Who Runs Oracle Universal Installer

Property Description

Login name

You can use any name for the user. This guide refers to the user as the oracle user.

Group identifier

The primary group of the oracle user must have write permission for the directory.

You can use any name for the group. This guide uses the name oinstall.

Home directory

The home directory for the oracle user can be consistent with the home directories of other users.

Login shell

The default login shell can be the C, Bourne, or Korn shell.


Note:

Use the oracle user only for installing and running Oracle products. Do not use root as the oracle user.


See Also:

Your operating system documentation or contact your system administrator for more information about creating operating system users.


See Also:

you can also refer to the Oracle Application Server Installation Guide for more information about creating operating system users.

4.7 Environment Variables

The operating system user who installs Oracle Content DB must set or unset certain environment variables.

When working with environment variables, here are some things to remember:

This section discusses the following environment variables and whether they must be set or unset:

4.7.1 ORACLE_HOME, and ORACLE_SID

ORACLE_HOME, and ORACLE_SID must not be set.

4.7.2 PATH, CLASSPATH, and Shared Library Path Environment Variables

Edit your PATH, CLASSPATH, and shared library path environment variables so that they do not reference any Oracle home directories.

4.7.3 DISPLAY

Set the DISPLAY environment variable to point to the X server that will display Oracle Universal Installer. The format of the DISPLAY environment variable is:

host_name:display_number.screen_number

Example (C shell):

$ setenv DISPLAY test.domain.com:0.0

Example (Bourne or Korn shell):

$ DISPLAY=test.domain.com:0.0; export DISPLAY

You can test the display by running the xclock program. Make sure you have run the xhost + command first. Then, to test the display, run the xclock & command. For example:

$ /usr/openwin/bin/xclock &

Note:

The location of the xclock and xhost commands may vary, depending on your operating system. Consult your operating system documentation for more information.

Oracle Content DB requires a running X server during installation, only. The frame buffer X server installed with your operating system requires that you remain logged in and have the frame buffer running during installation. If you do not want to do this, then you must use a virtual frame buffer, such as X Virtual Frame Buffer (XVFB) or Virtual Network Computing (VNC).


See Also:

Oracle Technology Network for more information about obtaining and installing XVFB or other virtual frame buffer solutions, at

http://www.oracle.com/technology/index.html

4.7.4 TNS_ADMIN

This section describes the following two requirements:

  • The TNS_ADMIN environment variable must not be set

  • The /etc and the /var/opt/oracle directories must not contain a tnsnames.ora file

These requirements are necessary to prevent conflicts between the Oracle Net Services configuration files for different Oracle products.

To set TNS_ADMIN or if you have the tnsnames.ora file in /etc or /var/opt/oracle, perform the following steps before installing Oracle Content DB.

  1. If the tnsnames.ora file is in the /etc or /var/opt/oracle directory, move the file to a different directory or you can rename the file.

  2. Ensure the TNS_ADMIN environment variable is not set.

    Example (C shell):

    prompt> unsetenv TNS_ADMIN


    % /usr/openwin/bin/xclock &

    Example (Bourne or Korn shell):

    prompt> unset TNS_ADMIN

After installation, you can merge the contents of the newly created tnsnames.ora file with your existing tnsnames.ora file.

4.7.5 TMP

Oracle Universal Installer uses a temporary directory for swap space and checks for the TMP environment variable to locate the temporary directory. By default, Oracle Universal Installer uses the /tmp directory.

If you want Oracle Universal Installer to use a directory other than /tmp, set TMP to the full path of an alternate directory. The directory must meet the requirements listed in Table 4-1.

Example (C shell):

$ setenv TMP /tmp2

Example (Bourne or Korn shell):

# TMP=/tmp2; export TMP

If you do not set this environment variable, and the default directory does not have enough space, Oracle Universal Installer displays an error message that says the environment variable is not set. You can either set the environment variable to point to a different directory or free up enough space in the default directory. In either case, you must restart the installation.

4.7.6 The /etc/hosts File

The contents of the /etc/hosts file affect both the location of the default identity management realm and the host name for Oracle Application Server Single Sign-On.

Oracle Universal Installer provides alternative methods for you to enter the values that you want without editing the hosts file, as explained in the following sections:

4.7.6.1 Location of the Default Identity Management Realm

Oracle Universal Installer reads the hosts file to construct the location of the default identity management realm. It displays this location in the Specify Namespace in Internet Directory screen.

The hosts file uses the following format:

ip_address   fully_qualified_host_name   short_host_name

For example:

123.45.67.89   primaryHost.domain.com   primaryHost

In the preceding example, the location of the default identity management realm would display as "dc=domain,dc=com".

If the file uses a different format, Oracle Universal Installer displays an incorrect value in the screen.

123.45.67.89   primaryHost   primaryHost.domain.com  <--- incorrect format

In this case, Oracle Universal Installer displays "dc=primaryHost,dc=com" as the default identity management realm. Most likely, this is not the value that you want for the default identity management realm.


Note:

If you require that the hosts file use a different format, you can edit the file to use the required format, perform the installation, then revert the file back to its original format after installation.

If you are unable, or unwilling, to edit the hosts file, you can enter the desired value for the default identity management realm in the Custom Namespace field on the Specify Namespace in Internet Directory screen.

4.7.6.2 Host Name for Oracle Application Server Single Sign-On

If you are installing Oracle Application Server Single Sign-On (OracleAS Single Sign-On) and your hosts file contains only the host name of your computer (without the domain name), you will only be able to sign on to the OracleAS Single Sign-On server using the host name by itself (without the domain name).

To require a domain name when connecting to the OracleAS Single Sign-On server, you can edit the hosts file to include the domain name. If you do not want to edit the file, you can use the OUI_HOSTNAME command-line parameter to Oracle Universal Installer to override the value in the hosts file, as in the following example:

prompt> mount_point/runInstaller OUI_HOSTNAME=myserver.domain.com

4.8 Network Topics

Typically, the computer on which you want to install Oracle Content DB is connected to a network, has local storage to contain the Oracle Content DB installation, has a display monitor, and has an appropriate disk drive.

This section describes how to install Oracle Content DB on computers that do not meet the typical requirements and includes the following topics:

4.8.1 Installing Oracle Content DB on Computers with Multiple Network Cards

If you are installing Oracle Content DB on a computer with multiple network cards, Oracle Universal Installer uses the first names in the /etc/hosts file to determine the host name to use for IP address lookup.

If this is not the name you want to use, you can:

  • Start up Oracle Universal Installer with the OUI_HOSTNAME parameter, if you do not want to edit the /etc/hosts file. Specify the host name that you want to use in this parameter, as in the following example:

    $ mount_point/runInstaller OUI_HOSTNAME=myserver.domain.com

4.8.2 Copying the DVD to a Hard Drive and Installing from the Hard Drive

Instead of installing from the Oracle Content DB DVD, you can copy the contents of the DVD to a hard drive and install the product from there. This provides for an easier solution if you plan to install many instances of Oracle Content DB on your network, or if the computers where you want to install Oracle Content DB do not have DVD-ROM drives.

You can also install Oracle Content DB from remote DVD-ROM drives.


See Also:

"Installing Oracle Content DB from a Remote DVD-ROM Drive" for more information

Checking the Space Requirement

Ensure that the hard drive contains enough space to hold the contents of the Oracle Content DB DVD.

4.8.3 Installing Oracle Content DB from a Remote DVD-ROM Drive

If the computer where you want to install Oracle Content DB does not have a DVD-ROM drive, you can perform the installation from a remote drive. You must share the remote DVD-ROM drive through Network File System.

On the remote computer, which has the DVD-ROM drive:

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

  2. Share the DVD-ROM drive, as follows:

    DVD-ROM:

    # su
Password: root_password
# share -F nfs -o ro /dvdrom

    The path /dvdrom specifies the path to the DVD-ROM drive. You can use any path you prefer.

On the local computer, access the DVD-ROM and run Oracle Universal Installer, as follows:

# /net/remote_computer_host_name/dvdrom/runInstaller

Replace remote_computer_hostname with the name of the remote computer.

4.8.4 Installing Oracle Content DB on a Remote Computer

You can run Oracle Universal Installer on a remote computer (remote_computer), but display the Oracle Universal Installer screens on your local computer (local_computer). Oracle Universal Installer will install Oracle Content DB on the remote computer.

  1. Allow remote_computer to appear on local_computer. Use the following command on the console of the local computer:

    local_computer> xhost +remote_computer

    If you do not run xhost, you might get an Xlib error similar to "Failed to connect to server", "Connection refused by server," or "Can't open display" when starting Oracle Universal Installer.

  2. On local_computer, perform a remote login as the oracle user (using ssh, telnet, or rlogin) to remote_computer, as follows:


    See Also:

    		 

    local_computer> ssh -X -l oracle remote_computer.domain.com

    Note:

    Use of ssh is recommended over rlogin or telnet because it is more secure than either. However, if you do not have ssh available, use rlogin or telnet.

    The ssh server must be configured to allow forwarding X11 connections.

    Alternatively, use one of the following commands:

    local_computer> rlogin -l oracle remote_computer.domain.com
local_computer> telnet remote_computer.domain.com

  3. This step is not required if you are using the ssh connection.

    Set the DISPLAY environment variable on remote_computer to point to local_computer.

    Example (C shell):

    remote_computer> setenv DISPLAY local_computer.domain.com:0.0

    Example (Bourne or Korn shell):

    remote_computer> DISPLAY=local_computer.domain.com:0.0; export DISPLAY

  4. Run Oracle Universal Installer, as described in Chapter 5, "Installing the Oracle Content DB Middle Tier".


    Note:

    You can use a PC X emulator to run Oracle Universal Installer if it supports a PseudoColor color model or PseudoColor visual. Set the PC X emulator to use a PseudoColor visual, and then start Oracle Universal Installer. Refer to the X emulator documentation for instructions on how to change the color model or visual settings.

4.8.5 Installing Oracle Content DB on NFS-Mounted Storage

Currently, Oracle Content DB is certified to run only on the Network Appliance filers Network File Storage (NFS)-mounted storage system.

The NFS-mounted system should be exported to at least the remote install user and remote root user. You can do this using exportfs command, as follows:

prompt> exportfs -i /vol/vol1

To check the latest certification list for any updates, visit Oracle Technology Network.

4.8.6 Support for NIS and NIS+

You can install and run Oracle Content DB in Network Information System (NIS) and NIS+ environments.

4.9 Prerequisite Checks Performed by Oracle Universal Installer

Table 4-5 lists prerequisite checks performed by Oracle Universal Installer.

Table 4-5 Prerequisite Checks Performed by Oracle Universal Installer

Item Description

Operating system version

See "Oracle Content DB Software Requirements" for supported versions

Operating system patches

Oracle Universal Installer checks that your computer includes any required operating system patches. If Oracle Universal Installer determines that some required patches are missing, it displays an error. See Appendix F, "Operating System Patches and Packages" for additional information

Operating system packages

See Appendix F, "Operating System Patches and Packages" for additional information.

Operating system kernel parameters

See "Kernel Parameters for Solaris Systems" for a list of required kernel parameter and their settings

Monitor

See Oracle Content DB Hardware Requirements for monitor requirements

Display permission

Oracle Universal Installer checks that the user has permissions to display on the monitor specified by the DISPLAY environment variable.

Memory

See Oracle Content DB Hardware Requirements for memory requirements

Swap space

See Oracle Content DB Hardware Requirements for swap space requirements

TMP space

See Oracle Content DB Hardware Requirements for /tmp directory space requirements

Oracle home directory name

Oracle Universal Installer checks that the Oracle home directory name does not contain any spaces.

Path to the Oracle home directory

Oracle Universal Installer checks that the path to the Oracle home directory is not longer than 127 characters.

Oracle home directory contents

Oracle Universal Installer checks that the Oracle home directory does not contain any files that might interfere with the installation.

Oracle home directory

Always install Oracle Content DB in a new directory. Do not install Oracle Content DB in an existing Oracle home directory. For example, do not install Oracle Content DB into in an existing Oracle Application Server.

DISPLAY environment variable

The installer checks that the DISPLAY environment variable is set.

Display permission

The installer checks that the user has permissions to display on the monitor specified by the DISPLAY environment variable.

Cluster file system

Oracle Universal Installer checks that you are not installing Oracle Content DB in a cluster file system (CFS).

DBCA_RAW_CONFIG environment variable

If you are installing the Oracle Content DB in a Oracle Real Application Clusters environment, you need to set this environment variable to point to a file that describes the locations of your raw partitions.

Port 1521

The installer displays a warning if port 1521 is in use by any application, including database listeners of any version. You need to stop the application that is using port 1521, then click OK in the warning dialog.

If it is a database listener that is using port 1521, you might be able to use it for the metadata repository database.

If it is another application that is using port 1521, you need to stop it or configure it to use a different port. Alternatively, you can change the database listener to use a port other than 1521, but you can do this only after installation..

Static port conflicts

The installer checks the ports listed in the staticports.ini file, if specified. See Ports Used by Oracle Content DB.

Oracle Enterprise Manager 10g directories are writable

The installer runs this check only if you are expanding a middle tier or if you are reinstalling Oracle Content DB in the same Oracle home. The installer checks that these directories are writable by the operating system user running the installer:

  • ORACLE_HOME/sysman/emd

  • ORACLE_HOME/sysman/config

  • ORACLE_HOME/sysman/webapps/emd/WEB-INF/config

Oracle Enterprise Manager 10g files exist

The installer runs this check only if you are expanding a middle tier or if you are reinstalling Oracle Content DB in the same Oracle home. The installer checks that these files exist:

  • ORACLE_HOME/sysman/config/iasadmin.properties

  • ORACLE_HOME/sysman/webapps/emd/WEB-INF/config/consoleConfig.xml

4.10 Running Prerequisite Checks from the Command Line

You can run the prerequisite checks without having to install Oracle Content DB by using the following single command:

./runInstaller -prereqChecker PREREQ_CONFIG_LOCATION=DVD_MountPoint/stage/prereq -entryPoint oracle.contentdb.top_Core
Go to previous page
Previous		 Go to next page
Next
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