Skip Headers
Oracle® Application Server Release Notes
10g Release 3 (10.1.3.1.0) for Linux x86

Part Number B31014-11
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

3 Installation Issues

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

3.1 Installation Issues

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

3.1.1 Using the Unified Oracle SOA Suite Installer for the mySOACompany Topology

Oracle Application Server Enterprise Deployment Guide 10g Release 3 (10.1.3.1.0) describes how to install the mySOACompany topology in a distributed environment, i.e., the various SOA components are installed in separate containers. Oracle recommends this environment for availability and performance isolation reasons. If these issues are not important to you, you may install all of the SOA components in a single container. To do this, launch Oracle Application Server SOA Suite 10.1.3.1.0 installer and select the J2EE Server, Web Server, and SOA Suite installation type.

3.1.2 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.

3.1.3 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.

3.1.4 Set Kernel Parameter Prior to Installation of Oracle HTTP Server on Red Hat Linux 4.0

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.

3.1.5 Asian Languages Do Not Display Correctly with Java 5.0

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.

3.1.6 Japanese Characters Affected on Red Hat Linux

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 appears as square boxes on the Oracle Universal Installer installation screens for Oracle Application Server 10g Release 3 (10.1.3.1.0). 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.

3.1.7 Check gcc Version Before Installing 10.1.3 on a Host with a 9.0.4 Installation

Oracle Application Server 10g Release 3 (10.1.3.1.0) requires a version of gcc that depends upon your operating system. See Oracle Application Server Installation Guide 10g Release 3 (10.1.3.1.0) 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:

  1. Install the version of gcc required for your version of Linux. For example:

    /opt/gcc323
    
  2. Remove the existing symbolic links:

    rm /usr/bin/gcc 
    rm /usr/bin/cc
    
  3. 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
    
  4. Install Oracle Application Server 10g Release 3 (10.1.3.1.0).

3.1.8 Install Software Packages for Red Hat Linux

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)

3.1.9 Error Messages after Setting VIRTUAL_HOST_NAME

After successfully completing the Basic Installation with the VIRTUAL_HOST_NAME environment variable set, you may find the following error messages in ORACLE_HOME\opmn\logs\default_group~home~default_group~1:

Warning: Unable to set up connection factory for a resource adapter in esb-dt:
Error creating a ResourceAdapter implementation class. 
Error creating a JavaBean of class
'oracle.tip.esb.server.bootstrap.DesignTimeResourceAdapter: 
java.lang.RuntimeException: failed to get ESB_HOME: 
java.lang.NullPointerException 
Warning: Unable to set up connection factory for a resource adapter in esb-rt:
Error creating a ResourceAdapter implementation class. 
Error creating a JavaBean of class
'oracle.tip.esb.server.bootstrap.RuntimeResourceAdapter: 
java.lang.RuntimeException: failed to get ESB_HOME: java.lang.NullPointerException
log4j:WARN No appenders could be found for logger
(org.quartz.simpl.SimpleThreadPool).
log4j:WARN Please initialize the log4j system properly. 

These error messages are benign and can be safely ignored.

3.1.10 Error Message in application.log File

After successful installation of Oracle Application Server, you may find the following error message in the application.log file:

javax.servlet.ServletException: 
ORABPEL START-UP ERROR!!!!!!!! 
OraBPEL run-time expected system environment property "orabpel.home". 

This error message is benign and can be safely ignored.

3.1.11 Tool and Script Failure

Multiple Oracle Application Server tools and scripts will fail during Oracle Application Server installation due to the incorrect setting of the ANT_HOME environmental variable.

To workaround this issue, unset the ANT_HOME environmental variable prior to installing Oracle Application Server.

After you have unset the ANT_HOME environmental variable, you can either:

  • remove the /etc/ant.conf file

  • comment out the line in the /etc/ant.conf file that incorrectly sets the ANT_HOME environmental variable

3.1.12 Middle Tier Installation Failure for Turkish Locale

Installation of an Oracle Application Server middle-tier fails for Turkish locale.

Oracle recommends that you avoid running the Oracle Universal Installer to install Oracle Application Server using the Turkish locale because some of the installation screens will not be displayed properly and will not be usable.

Oracle Application Server components such as OWSM and BPEL are not functional for the Turkish locale.

3.1.13 Recommended Locales for Simplified Chinese and Traditional Chinese

To avoid issues with installation of Oracle Application Server in locales using simplified Chinese and Traditional Chinese, Oracle recommends using:

  • zh_CN.gbk instead of zh_CN.gb18030 for Simplified Chinese

  • zh_TW.big5 instead of zh_TW.eucTW for Traditional Chinese

3.1.14 Icon and URL Link Errors in Spanish and Brazilian Portuguese Language Locales

In advanced Oracle Application Server installations in Spanish and Brazilian Portuguese Language locales, the Rules Control icon is not displayed.

Additionally the URL link to Oracle Application Server is not placed correctly.

There is no Rules control link in Brazilian Portuguese locale installations.

3.1.15 Oracle HTTP Server Welcome Page Displays Only In English

Oracle HTTP Server Welcome page displays in English only following installation of Oracle Application Server.

In order to view the translated Oracle HTTP Server Welcome page, you need to enter you installation information in the following format where <lang> is the language you would like to use to view the Welcome page:

http://<host>.<port>/index.html.<lang> 

For example,

http://<host>.<port>/index.html.ja (Japanese)

http://<host>.<port>/index.html.ko (Korean)

http://<host>.<port>/index.html.zh_TW (Traditional Chinese)

http://<host>.<port>/index.html.zh_CN (Simplified Chinese)

http://<host>.<port>/index.html.de (German)

http://<host>.<port>/index.html.fr (French)

http://<host>.<port>/index.html.it (Italian)

http://<host>.<port>/index.html.es (Spanish)

http://<host>.<port>/index.html.pt_BR (Brazilian Portuguese)

3.1.16 opmnctl Command Time Out with Old Data

The opmnctl stopall command times out if the BPEL schema in your OracleAS Metadata Repository Database contains old schemas.

To workaround this issue, run the production IRCA to load new schemas in the OracleAS Metadata Repository.

3.1.17 Exception in Error Log when Installing MainCD

After successful installation of Oracle Application Server SOA MainCD, you may find the following Exception message in the oraInstallyyyy-mm-dd_hh-mm-ssAM/PM.err file:

java.lang.NumberFormatException: For input string: ""80""at java.lang.NumberFormatException.forInputString(Unknown Source)
......
Returning 0 instead

This exception message is benign and can be safely ignored.

3.1.18 ONS Port Conflict When Oracle Database is Installed After Oracle Application Server

When you install Oracle Application Server, the ONS localport is set to 6101 by default. If you then install Oracle Database on the same host, the database ONS port may also be set to 6101. This results in a port conflict. The workaround is to manually change one of the ONS ports to a different port number after installation. Refer to Oracle Application Server Administrator's Guide for instructions for changing the ONS port number.

3.1.19 Manual Step Required Before Installing on Oracle Enterprise Linux

Before installing Oracle Application Server 10g Release 3 (10.1.3.1.0) on an Oracle Enterprise Linux system, you must perform the following steps:

  1. View the following file:

    /etc/redhat-release
    

    It will contain the following string of text:

    Enterprise Linux Enterprise Linux AS release 4 (October Update 4)
    
  2. Add the string of text to the end of <INSTALL_DIRECTORY>/install/oraparam.ini, preceded by redhat-. For example, change oraparam.ini from:

    [Certified Versions]Linux=redhat-Red Hat Enterprise Linux AS release 3,redhat-Red Hat Enterprise Linux AS release 4,redhat-Red Hat Enterprise Linux ES release 3,redhat-Red Hat Enterprise Linux ES release 4,SuSE-9
    

    to:

    [Certified Versions]
    Linux=redhat-Red Hat Enterprise Linux AS release 3,redhat-Red Hat Enterprise Linux AS release 4,redhat-Red Hat Enterprise Linux ES release 3,redhat-Red Hat Enterprise Linux ES release 4,SuSE-9,redhat-Enterprise Linux Enterprise Linux AS release 4 (October Update 4)
    
  3. Run Oracle Universal Installer.

3.1.20 OPMJA.MSG Message Format is Invalid

Using the Japanese_Japan locale for user opmn startup causes opmn to become unstable because of a logging function problem. instead of using Japanese_Japan, use another language locale, such as American_America.

3.2 Documentation Errata

The section describes documentation errata in installation documentation. It includes the following topics:

3.2.1 Additional Requirement for /etc/hosts File not Documented

In Chapter 2, "Requirements," of the Oracle Application Server Installation Guide, some additional information regarding the /etc/hosts file is missing.

The following entry must be present in the /etc/hosts file in order for the installation to start oc4j:home:

127.0.0.1 localhost

3.2.2 ASG Standalone Kit Runinstaller Location Correction

Oracle Application Server Installation Guide for Linux x86, section 6.5.4, Installing the OracleAS 10g (10.1.3.1.0) Standalone Install of OracleAS Guard into Oracle Homes, the following directory location is reference:

/Disk2/asg/install/runInstaller

The correct directory location is:

/Disk2/asg/Disk1/install/runInstaller

3.2.3 Incorrect URL

After installation is complete, the readme.txt is displayed and it contains a typo in the URL in the following section:

Online documentation for Oracle Application Server is available at: http://download.oracle.com/docs/cd/B31017-01/index.htm

The correct URL should be:

http://download.oracle.com/docs/cd/B31017_01/index.htm

The dash (-) in the URL should be an underscore (_) character.

3.2.4 Additional Requirement for Installed X11 Fonts

Bug 7416377

Installing Oracle Application Server 10.1.3 on Linux, you might see the following warnings:

Warning: translation table syntax error: Unknown keysym name: osfSelect
Warning: ... found while parsing ':<Key>osfSelect: ManagerGadgetSelect()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfSelect
Warning: ... found while parsing ':<Key>osfSelect: MenuBarGadgetSelect()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfActivate
Warning: ... found while parsing ':<Key>osfActivate: ManagerParentActivate()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfHelp
Warning: ... found while parsing ':<Key>osfHelp: MenuHelp()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfPrimaryPaste
Warning: ... found while parsing ':m <Key>osfPrimaryPaste:cut-primary()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfActivate
Warning: ... found while parsing ':<Key>osfActivate:
PrimitiveParentActivate()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfHelp
Warning: ... found while parsing ':<Key>osfHelp: ManagerGadgetHelp()'
Warning: String to TranslationTable conversion encountered errors

These warnings indicate that some X11 fonts are not installed. When Oracle Universal Installer cannot find them, it defaults to other available system fonts, and the installation can continue.

These warning can be avoided by installing the XFree86-4.3.99.902-43.71 RPM.

3.2.5 Incorrect Information About Cluster Topology Configuration

In the Oracle Application Server Installation Guide 10g Release 3 (10.1.3.1.0), this information about configuring a cluster topology is incorrect:

"If you do not select this option, the OC4J instance will listen for requests from browser clients using its own HTTP listener. The OC4J instance will be configured so that its default web site is running in HTTP protocol mode and can be directly accessed from browser clients."

By disabling the "Access this OC4J Instance from a separate Oracle HTTP Server" option for this installation type, the OC4J default-web-site will not be configured with HTTP, but as a regular OC4J instance.