2 Installation and Upgrade Issues

This chapter describes installation and upgrade issues and their workarounds associated with Oracle Application Server. It includes the following topics:

• Section 2.1, "Preinstallation Issues"

• Section 2.2, "Installation Issues"

• Section 2.3, "Upgrade Issues"

• Section 2.4, "Documentation Errata"

2.1 Preinstallation Issues

This section describes preinstallation issues of Oracle Application Server. It includes the following topic:

• Section 2.1.1, "HP UX Kernel Parameter Incorrect"

2.1.1 HP UX Kernel Parameter Incorrect

In Section 2.4 "Kernel Parameters", of the Oracle Application Server Installation Guide the value for maxfiles_lim is incorrectly stated as 65536. Ensure that the kernel parameters for OracleAS Web Cache is set with maxfiles_lim not exceeding 60000.

2.2 Installation Issues

This section describes issues with installation of Oracle Application Server. It includes the following topics:

• Section 2.2.1, "sl_DlgClusterInfoWebReturn Parameter Does Not Work in Silent Installations"

• Section 2.2.2, "Response Files Created through the Record Mode Are Not Supported"

• Section 2.2.3, "IPv6 Not Supported"

2.2.1 sl_DlgClusterInfoWebReturn Parameter Does Not Work in Silent Installations

Oracle Application Server Installation Guide 10g Release 3 (10.1.3) lists sl_DlgClusterInfoWebReturn as one of the parameters that can be included in the response file for silent installations. This parameter is supposed to allow you add the instance to a cluster; however, it does not work and you will find that the instance is not clustered after the installation has completed.

To work around this problem, you can add the instance to a cluster by manually updating the opmn.xml file with the following tags after you finish the silent installation:

<topology>
    <discover list="*ip_address:port"/>
</topology>

These tags must be nested within the <notification-server> tag.

For more detailed instructions, refer to Oracle Application Server High Availability Guide 10g Release 3 (10.1.3), section 3.2.1.2, "Discovery Server Method".

2.2.2 Response Files Created through the Record Mode Are Not Supported

If you want to run the installer with a response file (to perform a silent or non-interactive installation), you cannot use response files created through the -record command-line option in the installer, as described in the "Creating Response Files by Using the Record Mode in the Installer" section in the Oracle Application Server Installation Guide. Instead, you must use response files that were created from the provided response file templates; you replace the placeholder values in the template files with your own values.

2.2.3 IPv6 Not Supported

This release of Oracle Application Server is not certified to run on machines that are configured with IPv6. You have to install and run this release of Oracle Application Server on machines that are configured with IPv4.

2.3 Upgrade Issues

This section describes issues with upgrade of Oracle Application Server. It includes the following topic:

• Section 2.3.1, "Additional Data Source Requirement for OEMS JMS Database Applications"

2.3.1 Additional Data Source Requirement for OEMS JMS Database Applications

If you are deploying an OEMS JMS Database application on Oracle Application Server 10g Release (10.1.3), note that you must verify that the manage-local-transactions attribute in the data-sources.xml file is set to false.

The following example shows the managed-data-source element in the data-sources.xml file with the required attribute for OEMS JMS Database applications:

<managed-data-source name="OracleDS" connection-pool-name="Example
Connection Pool" jndi-name="jdbc/OracleDS" *manage-local-transactions="false"*/>.

2.4 Documentation Errata

This section describes known errors in Oracle Application Server installation and upgrade documentation. It includes the following topic:

• Section 2.4.1, "Incorrect Reference to Installation Media"

• Section 2.4.2, "Incorrect Ports Listed in the Oracle Application Server Installation Guide"

• Section 2.4.3, "ORACLE_HOSTNAME Environment Variable Does Not Work"

• Section 2.4.4, "PATH, CLASSPATH, and LD_LIBRARY_PATH May be Set or Unset When Running Installer"

2.4.1 Incorrect Reference to Installation Media

In the Oracle Application Server Quick Installation Guide, the second step in section 5 "Starting the Installer" should be:

2. Insert the disk:

CD-ROM: Insert the Oracle Application Server CD-ROM.

DVD-ROM: Insert the Oracle Application Server DVD-ROM.

2.4.2 Incorrect Ports Listed in the Oracle Application Server Installation Guide

In Table B-1, "Default Port Numbers and Ranges (Grouped By Component)", in the Oracle Application Server Installation Guide, the allotted port range is incorrectly listed for the Listen (SSL) and SSL ports. The correct port numbers are as follows:

For the Listen (SSL) port:

• Allotted port range: 4443 - 4543

• Default port number: 4443

For the SSL port:

• Allotted port range: 4443 - 4543

• Default port number: 4443

2.4.3 ORACLE_HOSTNAME Environment Variable Does Not Work

In the section "Installing on Multihomed (Multi-IP) Computers," the Oracle Application Server Installation Guide states:

"By default, Oracle Universal Installer uses the ORACLE_HOSTNAME environment variable setting to find the hostname. If ORACLE_HOSTNAME is not set and you are installing on a computer that has multiple network cards, Oracle Universal Installer determines the hostname by using the first name in the /etc/hosts file."

This is incorrect. There is no default behavior, and the only way to set the hostname is by running Oracle Universal Installer with the OUI_HOSTNAME switch as follows:

> runInstaller OUI_HOSTNAME=hostname

2.4.4 PATH, CLASSPATH, and LD_LIBRARY_PATH May be Set or Unset When Running Installer

The "Environment Variables" section of Oracle Application Server Installation Guide 10g Release 3 (10.1.3) states that the PATH, CLASSPATH, and LD_LIBRARY_PATH environment variables must not contain references to directories in any Oracle home directories.

This is not correct. It does not matter, if the PATH, LD_LIBRARY_PATH , and CLASSPATH variables are set or unset before running the installer, and it does not matter if they contain references to directories in any Oracle home directories.