Oracle® Application Server Release Notes
10g Release 3 (10.1.3) for Linux x86 and Linux x86-64 B25216-02 |
|
![]() 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 issues with installation of Oracle Application Server. It includes the following topics:
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 Web site 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.
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"*/>.