| Oracle® Application Server Release Notes 10g Release 3 (10.1.3) for Linux on POWER B28546-06 |
|
 Previous |
 Next |
| Oracle® Application Server Release Notes 10g Release 3 (10.1.3) for Linux on POWER B28546-06 |
|
Previous |
Next |
This chapter describes installation and upgrade issues and their workarounds associated with Oracle Application Server. It includes the following topics:
This section describes preinstallation issues of Oracle Application Server. It includes the following topics:
In addition to the software packages documented in Oracle Application Server Installation Guide, use the following to fulfill the software requirements:
For Red Hat Enterprise Linux AS 4.0 Systems:
gdbm-1.8.0-24 db4-4.2.52-7.1 compat-db-4.1.25-9
Perform the following additional step (as root), if /usr/lib/libgdbm.so.3 does not exist in your system:
#ln -s /usr/lib/libgdbm.so.2 /usr/lib/libgdbm.so.3
|
Note: This step is required for Apache2.0 install only |
For SUSE Linux Enterprise Server 9 Systems:
gdbm-1.8.3-228.1 db-4.2.52-86.3 db1-1.85-85.1
These packages are required for apache1.3 and apache2.0.
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.4, "Asian Languages Do Not Display Correctly with Java 5.0"
Section 2.2.5, "Japanese Characters Affected on Red Hat Linux"
Section 2.2.6, "Check gcc Version Before Installing 10.1.3 on a Host with a 9.0.4 Installation"
Section 2.2.7, "Install Software Packages for Red Hat Linux"
Section 2.2.8, "Response Files Created through the Record Mode Are Not Supported"
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".
Prior to installation of Oracle HTTP Server as part of an Oracle Application Server installation on Red Hat Linux 4.0, set the following kernel parameter:
file-max >= 131072
Failure to set the preceding parameter may result in an error in installation of Oracle Application Server.
When you install Oracle Application Server within a ja_JP locale on SUSE Linux, the titles of all Oracle Universal Installer windows, including Help windows, include garbled fonts (for example,'%9%H$'). However, the fonts displayed on the content of the Oracle Universal Installer are displayed correctly.
According to release notes for Java Developer Kit (JDK) 1.4.2 posted on the Sun Microsystems Java Web site (http://java.sun.com), JDK 1.4.2 does not provide support for east-asian languages including Japanese on SUSE Linux.
Asian language characters including Japanese, Korean, Traditional Chinese, and Simplified Chinese are not displayed on SuSE platform due to lack of support of JDK.
To resolve this issue, you can modify the font properties/config files. Refer to the following Sun Microsystems Java website URL for details:
http://java.sun.com/j2se/1.5.0/docs/guide/intl/fontconfig.html
However, both Sun and Oracle do not support these modifications and if you need support, then you will need to reproduce the product functional errors with an unaltered JDK.
On Red Hat Linux Release 4 (Nahant Update 1) and Red Hat Linux Release 3 (version older than Taroon Update 3), Japanese (ja_JP) characters appear as square boxes on the Oracle Universal Installer installation screens for Oracle Application Server 10g Release 3 (10.1.3). This issue is due to the use of the Java Runtime Engine (JRE) version that is shipped with Oracle Application Server; 1.4.2_05 or an earlier version of the JRE.
To work around this issue use version number1.4.2._06 or a newer version of the JRE.
Oracle Application Server 10g Release 3 (10.1.3) requires a version of gcc that depends upon your operating system. See Oracle Application Server Installation Guide 10g Release 3 (10.1.3) for Linux x86 for the version of gcc required for your operating system.
If your host contains an Oracle Application Server 10g (9.0.4) installation, you may have installed gcc-2.95 or gcc-2.96 on your system, as outlined in Oracle Application Server Quick Installation and Upgrade Guide 10g (9.0.4) for Linux x86. The procedure involved creating symbolic links for /usr/bin/gcc and /usr/bin/cc to the appropriate version of the executables.
To check whether these links exist:
ls -l /usr/bin/gcc /usr/bin/cc
Check if the gcc and cc commands are symbolic links, for example:
gcc -> /opt/gcc295/bin/gcc cc -> /opt/gcc295/bin/gcc
If the links exist, remove them and create new links to the version of gcc required for 10.1.3:
Install the version of gcc required for your version of Linux. For example:
/opt/gcc323
Remove the existing symbolic links:
rm /usr/bin/gcc rm /usr/bin/cc
Create links to the new version of gcc:
ln -s /opt/gcc323/bin/gcc /usr/bin/gcc ln -s /opt/gcc323/bin/gcc /usr/bin/cc
Install Oracle Application Server 10g Release 3 (10.1.3).
If you are installing on Red Hat Enterprise Linux AS/ES 4.0, Update 1 or higher, certified on AMD64 and Intel EM64T, the following packages (or higher versions) are required:
glibc-2.3.4-2.9.i686.rpm (32-bit)
glibc-2.3.4-2.9.x86_64.rpm
glibc-common-2.3.4-2.9.x86_64.rpm
glibc-devel-2.3.4-2.9.i386.rpm (32bit)
glibc-devel-2.3.4-2.9.x86_64.rpm
gcc-3.4.3-22.1.x86_64.rpm
gcc-c++-3.4.3-22.1.x86_64.rpm
gnome-libs-1.4.1.2.90-44.1.x86_64.rpm
libstdc++-3.4.3-22.1.i386.rpm (32-bit)
libstdc++-3.4.3-22.1.x86_64.rpm
libstdc++-devel-3.4.3-22.1.i386.rpm (32-bit)
libstdc++-devel-3.4.3-22.1.x86_64.rpm
make-3.80-5.x86_64.rpm
pdksh-5.2.14-30.x86_64.rpm
sysstat-5.0.5-1.x86_64.rpm
binutils-2.15.92.0.2-13.x86_64.rpm
compat-db-4.1.25-9.i386.rpm (32-bit)
compat-db-4.1.25-9.x86_64.rpm
control-center-2.8.0-12.x86_64.rpm
xscreensaver-4.18-5.rhel4.2.x86_64.rpm
setarch-1.6-1.x86_64
openmotif21-2.1.30-11.RHEL4.4.i386.rpm (32-bit)
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.
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.
This section describes issues with upgrade of Oracle Application Server. It includes the following topic:
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"*/>.
This section describes known errors in Oracle Application Server installation and upgrade documentation. It includes the following topic:
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"
The Oracle Application Server Installation Guide and Oracle Application Server Quick Installation Guide refer to multiple installation CDs. However, there is only one installation CD for Oracle Application Server 10g.
Additionally, 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.
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
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
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.
|
 Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|