Skip Headers
Oracle® Application Server Release Notes
10g Release 3 (10.1.3.1.0) for Linux x86
B31014-02
  Go To Documentation Library
Home		 Go To Table Of Contents
Contents
Previous
Previous 		 Next
Next		  

3 Installation Issues

This chapter describes installation and their workarounds associated with Oracle Application Server. 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 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.2 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.3 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.4 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.5 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.6 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.7 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.8 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.9 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.10 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.big instead of zh_TW.eucTW for Traditional Chinese

3.1.11 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.12 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.13 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.14 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.

  Previous
Previous 		 Next
Next
  Go To Documentation Library
Home		 Go To Table Of Contents
Contents