| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.1.0) for Linux Itanium Part Number B32207-06 |
|
|
View PDF |
| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.1.0) for Linux Itanium Part Number B32207-06 |
|
|
View PDF |
This chapter describes installation 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:
Section 2.1.1, "Using the Unified Oracle SOA Suite Installer for the mySOACompany Topology"
Section 2.1.3, "Response Files Created through the Record Mode Are Not Supported"
Section 2.1.5, "Asian Languages Do Not Display Correctly with Java 5.0"
Section 2.1.6, "Japanese Characters Affected on Red Hat Linux"
Section 2.1.7, "Check gcc Version Before Installing 10.1.3 on a Host with a 9.0.4 Installation"
Section 2.1.8, "Install Software Packages for Red Hat Linux"
Section 2.1.9, "Error Messages after Setting VIRTUAL_HOST_NAME"
Section 2.1.12, "Middle Tier Installation Failure for Turkish Locale"
Section 2.1.13, "Recommended Locales for Simplified Chinese and Traditional Chinese"
Section 2.1.14, "Icon and URL Link Errors in Spanish and Brazilian Portuguese Language Locales"
Section 2.1.15, "Oracle HTTP Server Welcome Page Displays Only In English"
Section 2.1.17, "Exception in Error Log when Installing MainCD"
Section 2.1.18, "OPMN Configuration Assistant Fails during Installation on NFS Storage"
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.
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.
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.
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.
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.
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.
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:
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.1.0).
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)
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.
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.
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
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.
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
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.
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)
The opmnctl stopall command times out if the BPEL schema in your OracleAS Metadata Repository Database contains old schemas.
To fix this issue, run the production irca.sh to load new schemas in the Oracle database.
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.
While starting up the BPEL process, the Oracle Process Manager and Notification Server (OPMN) Configuraton Assistant fails and the following error message is displayed:
<2006-11-08 03:51:07,096> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://iwin6509.us.oracle.com:8888 <2006-11-08 03:51:22,099> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://iwin6509.us.oracle.com:8888/orabpel <2006-11-08 03:51:37,124> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://144.25.145.91:8888/orabpel <2006-11-08 03:51:52,127> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://iwin6509.us.oracle.com:8888/orabpel <2006-11-08 03:52:07,131> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://localhost:8888/orabpel <2006-11-08 03:52:07,132> <ERROR> <collaxa> <ProcessJob::execute> Attempt (1/15) ... failed to connect ... retrying in 5 seconds ... <2006-11-08 03:52:27,176> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://iwin6509.us.oracle.com:8888 <2006-11-08 03:52:42,179> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://iwin6509.us.oracle.com:8888/orabpel <2006-11-08 03:52:57,182> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://144.25.145.91:8888/orabpel <2006-11-08 03:53:12,185> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://iwin6509.us.oracle.com:8888/orabpel
However, this issue only occurs while installing the SOA suite on NFS/NAS storage.
To workaround this issue, set the timeout value to 1200 or higher in the opmn.xml file. Following steps describe how to set this value:
Start the installation using runInstaller.
Increase the value of start timeout to 1200 for the oc4j instance in the ORACLE_HOME/opmn/bin/opmn.xml file. For example,
<start timeout="1200" retry="2"/>
Run root.sh to continue with the installation.
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.
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.
This section describes issues with Oracle Application Server documentation. It includes the following topics:
Section 2.2.1, "Incorrect Installation Directory Path in Graphic"
Section 2.2.2, "ASG Standalone Kit Runinstaller Location Correction"
Section 2.2.5, "Additional Requirement for /etc/hosts File not Documented"
An incorrect directory path for the Installation directory is specified in Figure 4-1, "Oracle Application Server SOA Suite 10.1.3.1.0 Installation Screen" in the Oracle Application Server Installation Guide.
The installation directory path should be /scratch/oracle/product/10.1.3.1/OracleAS.
The following directory location is referenced in section 6.5.4, Installing the OracleAS 10g (10.1.3.1.0) Standalone Install of OracleAS Guard into Oracle Homes of Oracle Application Server Installation Guide:
/Disk2/asg/install/runInstaller
The correct directory location is:
/Disk2/asg/Disk1/install/runInstaller
In Chapter 2, Section 5.3.2, "Select Installation Type Screen" of the Oracle Application Server Installation Guide, the following incorrect installation requirements were listed in the screenshot of the Select Installation Type page:
J2EE Server, Web Server, and SOA Suite (874 MB)
J2EE Server and Web Server (659 MB)
J2EE Server (622 MB)
Web Server (535 MB)
The correct installation requirements are:
J2EE Server, Web Server, and SOA Suite (1.2 GB)
J2EE Server and Web Server (650 MB)
J2EE Server (750 MB)
Web Server (650 MB)
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.
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
|
 Copyright © 2007, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
