| Oracle® Content Database Installation Guide 10g Release 1 (10.2.0.0.0) for Linux x86 Part Number B31199-05 |
|
|
View PDF |
| Oracle® Content Database Installation Guide 10g Release 1 (10.2.0.0.0) for Linux x86 Part Number B31199-05 |
|
|
View PDF |
|
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:
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 Linux Systems
| Item | Minimum Requirement | Checked by Oracle Universal Installer |
|---|---|---|
|
Processor speed |
450 MHz or faster; 2 GHz or faster recommended Note: On some Linux platforms running AMD-based hardware, the Oracle Content DB configuration assistant hangs. To fix this, install the In certain scenarios, however, JDK does not get upgraded resulting in the Oracle Content DB configuration assistant hanging. If you have AMD-based Linux hardware and if your Oracle Content DB configuration assistant appears to be hanging for a long period of time after installing the
|
Yes |
|
Network |
You can install Oracle Content DB on a computer that is not connected to a network. When you later change the network configuration, refer to the Oracle Content Database Administrator's Guide for information on reconfiguring Oracle Content DB. |
No |
|
IP |
The IP address of a computer can be static or allocated using DHCP. Note: It is recommended that you install Oracle Content DB on systems with static IP addresses. If you later change the IP configuration, refer to the Oracle Content Database Administrator's Guide for information on reconfiguring Oracle Content DB. |
No |
|
Memory |
Oracle Universal Installer checks the amount of memory on your computer and will not allow you to proceed if your computer does not meet the minimum memory requirements. Oracle recommends having at least 1 GB RAM. |
Yes |
|
Disk space |
The disk space requirement for Oracle Content DB is 2 GB. To determine the amount of free disk space, enter the following command: $ df -k directory
Replace |
No |
|
Space in |
400 MB To determine the amount of free disk space in the $ df -k /tmp If the See Also: "TMP" for more details |
Yes |
|
Swap space |
2 GB of available swap space To determine the amount of available swap space, enter the following command: $ cat /proc/swaps If necessary, refer to your operating system documentation for information about how to configure additional swap space. |
Yes |
|
Monitor |
256-color display To determine the display capabilities of the monitor, enter the For example: $ /usr/X11R6/bin/xwininfo Look for the Depth line. You need a depth of at least 8 bits for each pixel. |
Yes |
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.
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.
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).
|
See Also: Appendix F, "Software Requirements for Linux Distributions" for more information about software requirements for different distributions of Linux x86, including Red Hat Enterprise Linux AS/ES 4.0 and SUSE Linux Enterprise Server 9 |
Oracle Content DB installation requires you to configure your system kernel parameters. Compliance with this requirement is especially important for production environments. Review your kernel parameter settings to ensure that they meet the minimum requirements listed in Table 4-2.
|
Notes:
|
Table 4-2 Kernel Parameter Settings for Linux Systems
| Kernel | Recommended Values | Definition | File |
|---|---|---|---|
semmni |
142 |
The maximum number of semaphore sets in the entire system. |
/proc/sys/kernel/sem |
semmns |
32000 |
The maximum number of semaphores on the system. This setting is a minimum recommended value for an initial installation only. The |
/proc/sys/kernel/sem |
semopm |
100 |
The maximum number of operations for each |
/proc/sys/kernel/sem |
semmsl |
256 |
The minimum recommended number of semaphores for each ID for an initial installation only. The |
/proc/sys/kernel/sem |
shmmax |
2147483648 |
The maximum allowable size of one shared memory segment. It is 2 GB for SMP kernel. The recommended size is half the RAM size. |
/proc/sys/kernel/shmmax |
shmmni |
4096 |
The maximum number of shared memory segments in the entire system. |
/proc/sys/kernel/shmmni |
shmall |
3279547 |
The total amount of shared memory available. |
/proc/sys/kernel/shmall |
msgmni |
2878 |
The number of message queue identifiers. |
/proc/sys/kernel/msgmni |
msgmax |
8192 |
The maximum message size. |
/proc/sys/kernel/msgmax |
msgmnb |
65535 |
The maximum number of bytes on the message queue. |
/proc/sys/kernel/msgmnb |
file-max |
327679 |
The maximum number of files. |
/proc/sys/fs/file-max |
ip_local_port_range |
10000-65000 |
The range of local IP ports. |
/proc/sys/net/ipv4/ip_local_port_range |
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 Linux, 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.
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/sbin/lsof -i :port_number command. |
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:
|
Create operating system groups in the following situations:
If you plan to install Oracle Content DB on a computer that does not have Oracle products, create a group to own the inventory directory.
If you plan to install Oracle Application Server in a new database (that is, one created by Oracle Universal Installer), create groups for database administrators.
|
See Also: Your operating system documentation or contact your system administrator for more information about creating operating system groups. |
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:
The Oracle home directory, which contains files for the product you are installing
The inventory directory, which is used by the installer for all Oracle products
If the computer contains other Oracle products, you might already have a user for this purpose. Look in the /etc/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-3.
Table 4-3 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 |
|
Group identifier |
The primary group of the You can use any name for the group. This guide uses the name |
|
Home directory |
The home directory for the |
|
Login shell |
The default login shell can be the C, Bourne, or Korn shell. |
|
Note: Use theoracle 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. |
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:
If you set environment variables in the .profile file, they might not be read. To ensure that environment variables are set to the correct values, check their values in the shell where you will be running the installer.
To check the value of environment variables, use the env command to display all the currently defined environment variables and their values, as follows:
$ env
If you use the su command to switch users (for example, switching from the root user to the oracle user), check the environment variables when you are the new user because the environment variables might not be passed to the new user. This can happen even if you enter su with the - parameter (such as su - user).
$ /* root user */ $ su - oracle $ env
This section discusses the following environment variables and whether they must be set or unset:
Edit your PATH, CLASSPATH, and shared library path environment variables so that they do not reference any Oracle home directories.
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/X11R6/bin/xclock &
|
Note: The location of thexclock 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
Search for frame buffer. |
This section describes the following two requirements:
The TNS_ADMIN environment variable must not be set
The /etc directory 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, perform the following steps before installing Oracle Content DB.
If the tnsnames.ora file is in the /etc directory, move the file to a different directory or you can rename the file.
Ensure the TNS_ADMIN environment variable is not set.
Example (C shell):
$ unsetenv TNS_ADMIN
Example (Bourne or Korn shell):
$ unset TNS_ADMIN
After installation, you can merge the contents of the newly created tnsnames.ora file with your existing tnsnames.ora file.
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.
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:
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 thehosts 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 |
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:
$ mount_point/runInstaller OUI_HOSTNAME=myserver.domain.com
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:
Installing Oracle Content DB on Computers with Multiple Network Cards
Copying the DVD to a Hard Drive and Installing from the Hard Drive
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
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.
Checking the Space Requirement
Ensure that the hard drive contains enough space to hold the contents of the Oracle Content DB DVD.
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:
Insert the Oracle Content DB DVD in to the DVD-ROM drive.
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.
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.
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.
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 ofssh 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 |
Alternatively, use one of the following commands:
local_computer> rlogin -l oracle remote_computer.domain.com local_computer> telnet remote_computer.domain.com
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
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. |
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 administrator. You can do this using exportfs command, as follows:
# exportfs -i /vol/vol1
To check the latest certification list for any updates, visit Oracle Technology Network.
Table 4-4 lists prerequisite checks performed by Oracle Universal Installer.
Table 4-4 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. |
|
Operating system packages |
See Appendix F, "Software Requirements for Linux Distributions" for additional information. |
|
Operating system kernel parameters |
See Table 4-2, "Kernel Parameter Settings for Linux Systems" for a list of required kernel parameter and their settings |
|
Monitor |
See Table 4-1, "Hardware Requirements for Linux Systems" for monitor requirements |
|
Display permission |
Oracle Universal Installer checks that the user has permissions to display on the monitor specified by the |
|
Memory |
See Table 4-1, "Hardware Requirements for Linux Systems" for memory requirements |
|
Swap space |
See Table 4-1, "Hardware Requirements for Linux Systems" for swap space requirements |
|
TMP space |
See Table 4-1, "Hardware Requirements for Linux Systems" for |
|
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. |
|
|
The installer checks that the |
|
Cluster file system |
Oracle Universal Installer checks that you are not installing Oracle Content DB in a cluster file system (CFS). |
|
Application Server Control directories are writable |
Oracle Universal Installer runs this check only if you are expanding Oracle Content DB or if you are reinstalling Oracle Content DB. Oracle Universal Installer checks that these directories are writable by the operating system user running the installer:
|
|
Application Server Control files exist |
Oracle Universal Installer runs this check only if you are expanding Oracle Content DB or if you are reinstalling Oracle Content DB. Oracle Universal Installer checks that these files exist:
|
|
Database initialization parameters |
Oracle Universal Installer checks to make sure that the database you want to use with Oracle Content DB has the required minimum values. See "Setting Required Database Initialization Parameters" for additional information. |
|
Database character set |
Oracle Universal Installer checks to make sure that the database character set is AL32UTF8. |
