Release 2 (9.0.2) for AIX-Based Systems, Compaq Tru64 UNIX, HP 9000 Series HP-UX, and Linux Intel
Part Number A95258-03
 Home |
 Contents |
 Index |
| Oracle9i Application Server Installation Guide Release 2 (9.0.2) for AIX-Based Systems, Compaq Tru64 UNIX, HP 9000 Series HP-UX, and Linux Intel Part Number A95258-03 |
|
This chapter describes how to start installing Oracle9i Application Server (Oracle9iAS). It contains the following sections:
Table 2-1, Table 2-2, Table 2-3, and Table 2-4 contain the minimum hardware requirements for Oracle9iAS.
| Install Type | Component Configuration | Minimum Memory Requirements |
|---|---|---|
|
J2EE and Web Cache |
|
256 MB |
|
All other Oracle9iAS install types |
Configure up to three additional Oracle9iAS components |
512 MB |
|
All other Oracle9iAS install types |
Configure four or more additional Oracle9iAS components |
512 MB |
| Install Type | Component Configuration | Minimum Memory Requirements |
|---|---|---|
|
Oracle9iAS Infrastructure |
512 MB |
| Install Type | Component Configuration | Minimum Memory Requirements |
|---|---|---|
|
Oracle9iAS Developer Kits |
512 MB |
For the latest information, refer to OracleMetaLink at:
http://metalink.oracle.com
You can view Oracle9iAS documentation online using a Web browser or Portable Data Format (PDF) viewer.
Table 2-9 lists the documentation viewing tools for Oracle9iAS online documentation.
| Requirement | Items |
|---|---|
|
Online Readers |
Requires any one of the following: HTML |
|
Library-wide HTML search and navigation |
Active internet connection |
|
Disk Space |
310 MB |
Installing and operating Oracle9iAS requires a Web browser. Some of the Oracle9iAS installations require an Oracle database. A complete list of certified software, including databases and Web browsers, for Oracle9iAS is located at Oracle MetaLink:
http://metalink.oracle.com
Review and complete the following preinstallation tasks before installing Oracle9iAS:
Oracle Corporation recommends reading the Oracle9i Application Server Release Notes prior to installing Oracle9iAS. Oracle9i Application Server Release Notes are available with Oracle platform-specific documentation and are available at the OTN Web site at:
http://technet.oracle.com/docs/index.htm
The following section describes dependent configuration requirements for Oracle9iAS Unified Messaging.
To store data on a customer database, configure the database before Oracle9iAS Unified Messaging installation. Information about Oracle9iAS Unified Messaging is available in the Oracle9iAS Unified Messaging Administrator's Guide.
The following environment variables must be verified before starting Oracle Universal Installer:
Be sure your
Note:
PATH, CLASSPATH and library path environment variables do not exceed 1,024 characters. Longer values might generate errors such as "Word too long" during installation. Refer to Table 2-10 for the name of the library path environment variable for your platform.
Table 2-10 lists the names of the library path environment variable for each platform.
| Platform | Library Path Environment Variable |
|---|---|
|
Compaq Tru64 UNIX, and Linux Intel |
LD_LIBRARY_PATH |
|
HP 9000 Series HP-UX |
SHLIB_PATH and LD_LIBRARY_PATH |
|
AIX-Based Systems |
LIBPATH |
The Oracle home directory is the root directory in which Oracle software is installed.
Oracle homes are identified by name. The Oracle home name identifies the program group associated with a specific Oracle home and the installed Oracle services associated with the home.
Multiple instances of Oracle9iAS install types (J2EE and Web Cache, Business Intelligence and Forms, Portal and Wireless, and Unified Messaging) must be installed in separate Oracle homes on the same computer. However, a previous Oracle9iAS instance can be extended to a larger install type using Oracle Universal Installer. It is not possible to downgrade a larger install type to a smaller install type.
You must install Oracle9iAS Infrastructure in its own Oracle home directory, preferably on a separate host. The Oracle9iAS installation cannot exist in the same Oracle home directory as the Oracle9iAS Infrastructure installation.
Components from the Oracle9iAS Developer Kits installation are installed as part of the Oracle9iAS installation. Oracle9iAS Developer Kits can be installed on a separate host to set up a development environment.
Oracle9iAS installations require a unique instance name and administrative (ias_admin) password during initial installation on a host. Additional installations of Oracle9iAS on the host in the same Oracle home require the ias_admin password to continue with the installation. Installations in a different Oracle home require an instance name and the ias_admin password before continuing with the installation.
|
See Also:
|
To prevent a conflict between the software in an existing Oracle home and the Oracle9iAS installation, you must remove all references to the existing Oracle home in your environment. Follow these steps to remove these references.
ORACLE_HOME variable using the following command.
| C shell | Bourne/Korn shell |
|---|---|
|
|
PATH, CLASSPATH, and library path environment variables so they do not use the existing Oracle home value. Refer to Table 2-10 for the name of the library path environment variable for your platform.
Be sure your
Note:
PATH, CLASSPATH and library path environment variables do not exceed 1,024 characters. Longer values might generate errors such as "Word too long" during installation. Refer to Table 2-10 for the name of the library path environment variable for your platform.
Set the DISPLAY environment variable to refer to the X Server that will display the installer. The format of the DISPLAY environment variable is:
hostname:display_number.screen_number
Oracle9iAS requires a running X server to properly create graphics for the installer, Web applications, and management tools. The frame buffer X server installed with your operating system requires that you remain logged in and have the frame buffer running at all times. If you do not wish to do this, then you must use a virtual frame buffer, such as X Virtual Frame Buffer (XVFB) or Virtual Network Computing (VNC).
The installer configures this instance to use the same X server from the installation process for applications and management tools. This X server must either always be running or you must reconfigure Oracle9iAS to use another X server that is always running after the installation completes.
|
Note: Oracle Applications users must read article 181244.1 at:
This article contains applications-specific X server requirements and configuration information. |
|
See Also:
|
Setting the DISPLAY environment variable enables you to run the Oracle Universal Installer remotely from another workstation. On the system where you launch the Oracle Universal Installer, set DISPLAY to the system name or IP address of your local workstation.
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 installer, then run the commands on your local workstations as listed in the table below.
During installation, Oracle Universal Installer uses a temporary directory for swap space. This directory must meet the requirements listed in Section 2.1, "Hardware Requirements" before installing Oracle9iAS. The installation may fail if you do not have sufficient space. The installer checks for the TMP and TMPDIR environment variable to locate the temporary directory. If the TMP environment variable is not set, then the installer uses the /tmp directory. If the TMPDIR environment variable is not set, then the installer uses the /var/tmp directory. Set the TMP and TMPDIR environment variable using the following commands.
| C shell | Bourne/Korn shell |
|---|---|
|
|
|
|
TNS_ADMIN points to the directory where Net configuration files are stored.
If TNS_ADMIN is set on your system, you will have conflicts between that directory and the directory where the Oracle9iAS Net configuration files are created. You will also have conflicts if the configuration files are in a common directory outside of the Oracle home for your other Oracle product. For example, your system may use /var/opt/oracle/tnsnames.ora or /etc/tnsnames.ora for database aliases.
To prevent conflicts between the Net configuration files for different Oracle products, copy the configuration files from either TNS_ADMIN or the common directory to ORACLE_HOME/network/admin for the other products and unset TNS_ADMIN using the following command:
| C shell | Bourne/Korn shell |
|---|---|
|
|
Oracle Universal Installer requires that the fully qualified hostname information appear in the configuration files for your computer. A fully qualified hostname includes both the name of the system and its domain.
Verify that /etc/hosts.* has the following format:
IP_ADDRESS FULLY_QUALIFIED_HOSTNAME SHORT_HOSTNAME ALIASES
The following example shows a properly configured /etc/hosts.* file:
148.87.9.44 oasdocs.us.oracle.com oasdocs oracleinstall
The following UNIX account and groups are required for the installation process:
Use the admintool or groupadd utility to create a group name. In the following text the group name is oinstall. The oinstall group will own Oracle Universal Installer's oraInventory directory. The oracle user account that runs the installation must have the oinstall group as its primary group.
For more information on these utilities, refer to your operating system documentation.
The oracle account is the UNIX account that owns Oracle software for your system. You must run Oracle Universal Installer from this account.
Create an oracle account with the properties listed in Table 2-11.
|
Note:
Use the |
Two groups, the database operator group and the database administrator group, are required for Oracle9iAS Infrastructure installation. Oracle documentation refers to these groups as OSOPER and OSDBA, respectively. Databases use these groups for operating system authentication. This is necessary in situations where the database is shut down and database authentication is unavailable.
The privileges of these groups are given to either a single UNIX group or to two corresponding UNIX groups. There are two ways to choose which groups get the privileges:
oracle account is a member of the dba group before starting the installer, then dba is given the privileges of both OSOPER and OSDBA.
oracle account is not a member of the dba group, then the installer will prompt you for the group names that get these privileges.
The following table lists the privileges for the OSOPER and OSDBA groups.
Following installation, Oracle Universal Installer creates a file showing the port assignments during installation of Oracle9iAS components. The installation process automatically detects any port conflicts and selects an alternative port in the range allocated for that component. Appendix F, "Default Port Numbers and Port Ranges" lists the default port ranges. The file named portlist.ini is located at:
$ORACLE_HOME/install/portslist.ini
This file lists component entries as "port name = port value". For example:
Oracle HTTP Server port = 7777Oracle HTTP Server SSL port = 4443Oracle HTTP Server listen port = 7778Oracle HTTP Server SSL listen port = 4444Oracle HTTP Server Jserv port = 8007Enterprise Manager Servlet port = 1810
You can also view the port numbers by pointing your browser to the Oracle9iAS Welcome page and selecting the Ports tab.
|
See Also:
|
Installation of Oracle9iAS Infrastructure requires exclusive use of port 1521 on your computer. If one of your current system applications uses this port, then complete one of the following actions before installing Oracle9iAS Infrastructure:
Then no further network address modification is necessary.
The Oracle Net listener supports the Oracle8i database as well as Oracle9iAS Infrastructure.
The Oracle9iAS Metadata Repository and Oracle Internet Directory, installed as part of the Oracle9iAS Infrastructure installation, require you to configure your system kernel parameters. Review your kernel parameter settings to ensure that they meet Oracle9iAS Metadata Repository and Oracle Internet Directory requirements. You may experience errors during installation or operational errors after installation if this is not completed.
A system restart is necessary if you change the kernel settings for the kernel changes to take effect.
Refer to the appropriate tables for the kernel parameters for your platform:
For HP, you may use the System Administrator's Menu (SAM) to configure the HP kernel as required by your application. The parameters in the following table are those recommended for a general user running a typical Oracle9i Application Server instance on HP. You may need to change the values depending on your application needs and the type of system you are working on. Refer to the following table to determine if your system shared memory and semaphore kernel parameters are set correctly for Oracle9i Application Server. Use the ipcs command to obtain a list of the system's current shared memory and semaphore segments, and their identification numbers and owner.
The parameters in the following table are the recommended values to run Oracle9i Application Server with a single database instance on HP:
For Linux, use the ipcs command to obtain a list of the system's current shared memory and semaphore segments, and their identification numbers and owner.
You can modify the kernel parameters by using the /proc file system. Perform the following steps to modify the kernel parameters by using the /proc file system.
root user.
/proc/sys/kernel directory.
sem file by using the cat or more utility. For example, using the cat utility, enter the following command:
# cat sem
The output lists, in order, the values for the SEMMSL, SEMMNS, SEMOPM, and SEMMNI parameters. The following example shows how the output appears:
250 32000 32 128
# echo SEMMSL_value SEMMNS_value SEMOPM_value SEMMNI_value > sem
Replace the parameter variables with the values for your system in the order that they are entered in the preceding example. For example:
# echo 100 32000 100 100 > sem
cat or more utility. For example, using the cat utility, enter the following command:
# cat shared_memory_parameter
In the preceding example, the variable shared_memory_parameter is either the SHMMAX or SHMMNI parameter. The parameter name must be entered in lowercase letters.
For example, to modify the SHMMAX parameter, enter the following command:
# echo 2147483648 > shmmax
For example, to modify the SHMMNI parameter, enter the following command:
# echo 4096 > shmmni
For example, to modify the SHMALL parameter, enter the following command:
# echo 2097152 > shmall
# echo 65536 > /proc/sys/fs/file-max ulimit -n 65536
/proc/sys/net/ipv4/ip_local_port_range
# echo 1024 65000 > /proc/sys/net/ipv4/ip_local_port_change
ulimit -u. This gives you the number of processes per user.
ulimit -u 16384
The parameters in the following table are the minimum values required to run Oracle9i Application Server with a single-database instance on Linux:
For Tru64, use a text editor such as vi to change the kernel parameter settings in the /etc/sysconfigtab file after making a backup copy. If you have previously changed your kernel for another program to levels equal to or higher than the levels Oracle9i Application Server requires, then do not modify the settings. If the levels are too low, change them to at least as high as those in the table. If you change the settings, save the /etc/sysconfigtab file and restart the system. For example, if you need to change your SHM_MAX, SHM_MNI, SHM_SEG, PER_PROC_STACK_SIZE, and PER_PROC_DATA_SIZE parameter settings, modify the following lines in the /etc/sysconfigtab file:
ipc: shm_max = 4278190080 shm_mni = 256 shm_seg = 128 proc:per_proc_stack_size = 33554432 per_proc_data_size = 201326592
Refer to the following table to determine if your system shared memory and semaphore kernel parameters are set high enough for Oracle9i Application Server.
To determine the current kernel parameter settings, use the following command:
# /sbin/sysconfig -q ipc
The parameters in the following table are the recommended values to run Oracle9i Application Server with a single database instance on Tru64.
This section describes how Oracle9iAS uses Oracle Universal Installer for installation. It includes the following topics:
Oracle9iAS uses Oracle Universal Installer to guide you through each step of the installation process.
The Oracle Universal Installer provides the following features:
The Oracle Universal Installer automatically checks your computer prior to installation to verify that your system meets operational requirements. Table 2-12 lists the prerequisite checks that are performed.
| Prerequisite Checks | See Also |
|---|---|
|
Check for enough disk space for Oracle home installation |
|
|
Check for TMP and TMPDIR variable and sufficient swap space |
|
|
Check that the install host has enough RAM |
|
|
Verify existence of one infrastructure per host installation (All Oracle9iAS instances on one host share the same infrastructure) |
|
|
Check the |
|
|
Prohibit installation of Oracle9iAS into an existing 8.0.x or 8.1.x Oracle home |
|
|
Prohibit installation of Oracle9iAS Infrastructure into an existing Oracle9iAS home |
|
|
Ensure that the value of |
|
|
Verify the monitor has 256 color viewing capability |
|
|
Verify library path and paths of |
Section 2.5.3.1.1, "Preventing Conflicts With Other Oracle Homes" |
The Oracle Universal Installer creates the oraInventory directory the first time it is run on a computer. The oraInventory directory keeps an inventory of products that the Oracle Universal Installer installs on your computer, as well as other installation information. If you have previously installed Oracle products, then you may already have an oraInventory directory.
When a UNIX group name is created and specified, the Oracle Universal Installer grants the specified group the permission to write to the oraInventory directory. If another group attempts to run the installer, then they must have permission to write to the oraInventory directory. If they do not have permission, then the installation will fail.
The location of oraInventory is defined in the oraInst.loc file. See Table 2-13 for the location of the orainst.loc file for your system.
The latest log file is stored in:
/your_base_directory/oraInventory/logs/installActiontodays_date_time.log
The your_base_directory identifier is the location for your installation files and todays_date_time is the date and time of installation. Log file names of previous installation sessions take the form installActionstodays_date_time.log.
A complete listing of log files is included in the Oracle9i Application Server Administrator's Guide.
Do not delete or manually alter the oraInventory directory or its contents. Doing so can prevent the installer from locating products that you have installed on your system.
Follow these steps to start Oracle Universal Installer and install Oracle9iAS:
This launches Oracle Universal Installer, which installs Oracle9iAS.
The following sections provide the sequence and briefly describe the installation screens that you encounter for the three types of Oracle9iAS installation. Oracle Corporation recommends reviewing the installation sequence for a better understanding of the Oracle9iAS installation process.
This section describes the installation sequence for the following Oracle9iAS installations:
The following screens appear while performing an Oracle9i Application Server installation:
The following screens appear while performing an Oracle9iAS Infrastructure installation:
The Oracle Universal Installer configures both Oracle Internet Directory and Oracle9iAS Single Sign-On whether they are deselected or not. This is completed to verify connectivity between Oracle Internet Directory and Oracle9iAS Single Sign-On.
oracle account is not a member of the dba group. Enter the database administrator and operator group name.
The following screens appear while performing an Oracle9iAS Developer Kits installation:
When you are planning a subsequent Oracle9iAS installation, Oracle Corporation recommends that you:
/var/opt/oracle directory for subsequent Oracle9iAS installations.
oraInventory directory for subsequent Oracle9iAS installations.
Refer to appendices or specific guides for the following supplemental components available with Oracle9iAS, version 9.0.2:
This section describes the following restrictions:
This section also describes the following platform-specific information:
Before starting Cache Server and Admin Server in Oracle Web Cache, increase the data segment to 650 MB using the following command:
# ulimit -d 650000
If you are installing Oracle9iAS on Red Hat Linux, make sure to
http://metalink.oracle.com, search for Patch number 2389349.
/usr/bin directory as the first entry of the PATH environment variable.
If either of these requirements above are not satisfied, relinking will fail.
Also, create a link from the /sbin/fuser file to /bin/fuser. This is required to succesfully detect whether Oracle Enterprise Manager is running during second and subsequent installations on the same machine.
On Compaq Tru64 systems, the group ID of a directory is the same as that of the parent directory (if the parent is not root) and is not controlled by the active group of the current user.
Oracle Corporation recommends that you set the active group of the oracle user to be the same as the group ID of the $ORACLE_HOME directory. If you do not set the active group as recommended above, the Web Cache Configuration Assistant might fail.
Oracle Corporation recommends setting the following ulimit parameters before installation:
| Parameter | Recommended Value |
|---|---|
|
time |
unlimited |
|
file |
unlimited |
|
data |
1048576 |
|
stack |
32768 |
|
memory |
2045680 |
|
coredump |
unlimited |
|
nofiles |
4096 |
|
vmemory |
4194304 |
On Linux, Oracle Corporation recommends setting the swap file size to 3 times the size of RAM before installation.
There are limits to the length of the values of the CLASSPATH values with JDK. If the Oracle home path is long and there are many wrapper.classpath entries in the jserv.conf file, it might cause problems with the jserv process. The workaround is to shorten Oracle home path.
Table 2-13 lists the location of the oratab and oraInst.loc file for each platform:
| Platform | oratab and emtab | oraInst.loc |
|---|---|---|
|
AIX-Based Systems |
|
|
|
HP 9000 Series HP-UX |
|
|
|
Linux Intel |
|
|
|
Compaq Tru64 UNIX |
|
|
Refer to these mounting procedures during installation as necessary:
Mount Disk 1 to begin the installation. Mount the subsequent disk or disks when prompted to do so. Follow these steps to mount the Oracle9i Application Server CD-ROM manually:
root user and create a CD-ROM mount point directory, if one does not already exist, by using the following commands:
$ su root # mkdir cdrom_mount_point_directory
# lsdev -Cc cdrom
The output should be similar to the following:
cd0 Available 10-60-00-4, 0 SCSI Multimedia CD-ROM Drive
# mount options device_name cdrom_mount_point_directory
root account:
# exit
Example 2-1 shows how to mount the CD-ROM manually.
$ su root # mkdir /cdrom # mount -rv cdrfs /dev/cd0 /cdrom # exit
In the preceding output, /dev/cd0 is the CD-ROM device and /cdrom is the mount point.
Mount Disk 1 to begin the installation. Mount the subsequent disk or disks when prompted to do so. Follow these steps to mount the Oracle9i Application Server CD-ROM manually:
root user and create a CD-ROM mount point directory, if one does not already exist, by using the following commands:
$ su root # mkdir cdrom_mount_point_directory
$ ioscan -fun -C disk
The output should be similar to the following:
disk 10 10/12/5.2.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM XM-5701TA /dev/dsk/c4t2d0 /dev/rdsk/c4t2d0
/etc/pfs_fstab file for your CD-ROM device, you must add one. As the root user, use a system editor to add a line, in the following format, to the /etc/pfs_fstab file:
device_file mount_point filesystem_type translation_method
In the preceding format, the first entry is the CD-ROM device, the second entry is the mount point, and the third entry indicates that the CD-ROM to be mounted is in ISO9660 format with Rockridge extensions.
The device_file in this example is /dev/dsk/c4t2d0. For a CD-ROM device with the path /dev/dsk/c4t2d0, you would enter the following:
/dev/dsk/c4t2d0 /SD_CDROM pfs-rrip xlat=unix 1 0
root user with the following command:
$ su root
# nohup /usr/sbin/pfs_mountd & # nohup /usr/sbin/pfsd &
# /usr/sbin/pfs_mount /SD_CDROM
# exit
If you run the Installer while the current working directory is the CD-ROM directory, follow these steps to mount the next CD-ROM:
root user:
$ cd / $ su root
# /usr/sbin/pfs_umount /SD_CDROM
# /usr/sbin/pfs_mount /SD_CDROM
Mount Disk 1 to begin the installation. Mount the subsequent disk or disks when prompted to do so.
If you are using auto mounting software, the CD-ROM is mounted automatically to the directory specified in your auto mount configuration when you insert it into the CD-ROM drive.
To check whether you have auto mounting software, enter the following command:
$ ps -aux | grep automount
If you have auto mounting software, the output must be similar to the following:
root 628 0.0 0.2 1148 588 ? S 17:32 0:00 /usr/sbin/automount /misc file /etc/auto.misc
In the preceding output, the /etc/auto.misc section defines the directory under the /misc file where the CD-ROM will be mounted.
Follow these steps to mount subsequent CD-ROMs:
$ cd / $ eject
To mount the Oracle9i Application Server CD-ROM manually, use the following steps:
root user and, if necessary, create a CD-ROM mount point directory by using the following commands:
$ su root # mkdir cdrom_mount_point_directory
# mount options device_name cdrom_mount_point_directory
root account.
# exit
If you are unsure of the correct device name, consult your system administrator. Typically, the device name is /dev/cdrom.
Example 2-2 shows how to mount the CD-ROM manually.
$ su root # mkdir /cdrom # mount -t iso9660 /dev/cdrom /cdrom # exit
If you run the Installer while the current working directory is the CD-ROM directory, follow these steps to mount the next CD-ROM:
root user by using the following commands:
$ cd / $ su root
# umount cdrom_mount_point_directory
Follow these steps to mount the Oracle9i Application Server CD-ROM manually:
root user and create a CD-ROM mount point directory, if one does not already exist, by using the following commands:
$ su root # mkdir cdrom_mount_point_directory
$ ls /dev/disk/cdrom*c
The command should return a line similar to the following:
/dev/disk/cdrom0c
# mount options device_name cdrom_mount_point_directory
root account.
# exit
Example 2-3 shows how to mount the CD-ROM manually.
$ su root # mkdir /cdrom # mount -t cdfs -r -o nodefperm,noversion,rrip /dev/disk/cdrom0c /cdrom # exit
If you run the Installer while the current working directory is the CD-ROM directory, follow these steps to mount the next CD-ROM:
root user by using the following commands:
$ cd / $ su root
# umount cdrom_mount_point_directory
|
 Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|