Skip Headers
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for IBM zSeries Based Linux
B25837-02
  Go To Documentation Library
Home		 Go To Table Of Contents
Contents
Previous
Previous 		 Next
Next		  

2 Installation and Upgrade Issues

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

2.1 Installation Issues

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

2.1.1 Locales zh_TW.EUC and zh_TW in Traditional Chinese Environments Not Supported in the OracleAS Portal Component

If you try to install the OracleAS Portal component on a computer where the locale is set to zh_TW.EUC or zh_TW in Traditional Chinese environments, the installer will pause indefinitely because of the Java encoder behavior for these locales.

The workaround is to use the zh_TW.BIG5 locale in these environments. This requirement applies during installation only. After installation, you can reset the locale to the original locale.

2.1.2 Characters Dropped or Truncated

In locales where the zh_CN.GB18030 character set is used, input and output operations cause some characters to be dropped or truncated due to a problem in the sun.io.CharToByteGB18030 converter of the Java Developer Kit (JDK).

To avoid this problem, do not use zh_CN.GB18030 as the character set for Oracle Internet Directory in your locale. Oracle recommends using the zh_CN.GBK or zh_CN.GB2312 character sets.

2.1.3 Failure of File-Based Farm Repository Configuration Assistant

If you select Stop, and then select Retry during operation of the File-Based Farm Repository Configuration Assistant in the Oracle Universal Installer, the configuration assistant fails and displays the following message:

This instance is already a member of a farm. An Oracle Application Server instance cannot be moved directly from one farm to another.

There is presently no workaround for this issue.

2.1.4 Non-English Welcome Pages URL Link Pages Incorrectly Coded

Non-English Oracle Internet Directory Welcome pages files have some of the URL links coded incorrectly. The incorrectly coded Welcome pages point to .html URL destinations instead of .htm URL destinations. You will receive a Page Not Found error message if you encounter this issue.

If you encounter this issue, change the URL extension in the address bar of your Web browser to .htm instead of .html.

2.1.5 Distributed OracleAS Metadata Repository and Oracle Internet Directory on Separate Computers Throws Error

If you have distributed infrastructure environment with an OracleAS Metadata Repository on computer 1, and an Oracle Internet Directory installation on computer 2, the Oracle Internet Directory will not allow registration of the OracleAS Metadata Repository and will throw an error message similar to the following:

MR Already registered.
The service name is already registered with the specified Oracle Internet Directory by the database containing OracleAS Metadata Repository on computer 2.
To continue with the registration, please remove existing registration in the Oracle Internet Directory.

This problem occurs if both database SIDs are the same.

2.1.6 Welcome Link Coded Incorrectly

In the Forms and Reports Services Welcome pages, the Welcome link at the bottom of the pages is coded incorrectly. Users should use the Welcome tab at the top of the pages for navigation.

2.1.7 OracleAS Metadata Repository Creation Assistant Should Not Allow Loading into Oracle 10.1.0.4 Database

OracleAS Metadata Repository Creation Assistant allows loading into the Oracle 10.1.0.4 database; unfortunately, this should not be allowed by the program. The OracleAS Metadata Repository Creation Assistant program should perform a prerequisite check for this but it does not.

2.1.8 Installing 10.1.2.0.2 Middle Tiers Against an Existing Infrastructure

You can install 10g Release 2 (10.1.2.0.2) middle tiers against an existing Infrastructure. Specifically, during the 10.1.2.0.2 middle-tier installation procedure, specify the connection details for the existing 10g Release 2 (10.1.2.0.0) Identity Management, and 10.1.2.0.0 or 10g (9.0.4) OracleAS Metadata Repository as described in the Oracle Application Server Installation Guide.

The following are supported configurations with the 10.1.2.0.2 middle tier:

  • 10.1.2.0.0 Identity Management and 10g (9.0.4) OracleAS Metadata Repository

  • 10.1.2.0.0 Identity Management and 10.1.2.0.0 OracleAS Metadata Repository

  • 10.1.2.0.2 Identity Management and 10.1.2.0.0 OracleAS Metadata Repository

For more information about compatibility issues between 10g Release 2 (10.1.2.0.2) and 10g Release 2 (10.1.2.0.0), see "Understanding Version Compatibility" in Oracle Application Server Upgrade and Compatibility Guide.

2.1.9 IBM WebSphere Required Patch Version 6.0.2

If you are using IBM WebSphere Application Server, install the following patch: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24009813

Doing so will help you avoid problems when using Oracle Industrial Telnet Server and (potentially) other products.

2.1.10 Disk Space Needed on a Database that Uses Automatic Storage Management

If you are installing OracleAS Metadata Repository on a database that uses Automatic Storage Management (ASM), make sure the disk group has at least 2 GB of disk space for the OracleAS Metadata Repository tablespaces. This is in addition to the space needed for the SYSTEM and UNDO tablespaces.

2.1.11 Oracle Ultra Search Required (Oracle Database 10g Release 2 (10.2.x) only)

If you plan to install the OracleAS Metadata Repository on Oracle Database 10g Release 2 (10.2.x), then you must install Oracle Ultra Search on the database.

OracleAS Metadata Repository Creation Assistant checks if your database contains the WKSYS and WKPROXY schema. If your database does not contain them, OracleAS Metadata Repository Creation Assistant displays the following warning:

"The Database does not contain Ultra Search Schemas WKSYS and/or WKPROXY. Please install them and try again. Refer to the Database Install Guide and Ultra Search User Guide for more information."

If your database does not have Oracle Ultra Search installed, you can install it from the Oracle Database 10g Companion CD-ROM. See the Oracle Database Companion CD Installation Guide for details.

After installing Oracle Ultra Search, you need to load the schemas onto the database using the Database Configuration Assistant (DBCA). Refer to Oracle MetaLink (http://www.metalink.oracle.com) Note 337992.1 for loading Ultra Search schemas.

2.1.12 Patch Required Prior to Running the Metadata Repository Creation Assistant on a 10.2 Real Application Cluster Database

You must install ARU patch 7993184 before running the Metadata Repository Creation Assistant on a 10.2 Real Application Cluster Database. If you do not apply the patch, you will receive an error message during Oracle Ultra Search configuration.

To apply the patch:

  1. Install the 10.2 Real Application Cluster database.

  2. Create the database using the DBCA or during the installation.

  3. Stop all Oracle Processes.

  4. Install Oracle Ultra Search in the same Oracle home from the companion CD.

  5. Apply ARU patch 7993184. Go to Oracle MetaLink (http://www.metalink.oracle.com) to obtain the ARU patch.

  6. Invoke the DBCA to configure Oracle Ultra Search.

  7. Run the Metadata Repository Creation Assistant.

2.1.13 Populate DB_DOMAIN Before Running Oracle Metadata Repository Creation Assistant on an Oracle 10.2 Database

The default installation option for Oracle Database 10g (Release 2) 10.2 does not populate the DB_DOMAIN. The OracleAS Metadata Repository Creation Assistant uses the value of DB_DOMAIN to construct the Oracle Application Server farm name as $SID.$DB_DOMAIN. You should ensure that the DB_DOMAIN is populated in the database with a valid value prior to running OracleAS Metadata Repository Creation Assistant. Failure to do will result in the default farm name of REGRESS.RDBMS.DEV.US.ORACLE.COM.

2.1.14 Installer Displays Incorrect Version Number

The installer for the OracleAS Metadata Repository Creation Assistant displays the incorrect version number for the OracleAS Metadata Repository. The installer displays (10.1.2.0.2); the version number displayed should be (10.1.2.0.3).

This issue can be ignored during installation.

2.1.15 JAccelerator (Ncomp) Is Not Installed with OracleAS Metadata Repository 10.1.2.x

You will receive the following error message when you run the catpatch.sql script after Oracle Database 10.1.0.5 Patch Set application on OracleAS Metadata Repository 10.1.2.x:

"select dbms_java.full_ncomp_enabled from dual
ERROR at line 1: ORA-29558: JAccelerator (NCOMP) not installed. Refer to Install Guide for instructions. ORA-6512: at "SYS.DBMS_JAVA", line 236."

You can ignore this error message. JAccelerator (Ncomp) is not installed with OracleAS Metadata Repository 10.1.2.x.

2.1.16 Error While Setting Kernel Parameters for Oracle AS Web Cache and Setting Shell Limits

After setting kernel parameters for Oracle AS Web Cache and Setting Shell limits, when you run ulimit-hn command, the value does not change. It remains 1024. Also, when you use the su command to change to the oracle user, the following error is displayed:

ksh /etc/profile[291]: ulimit: exceeds allowable limit

To workaround these issues, add the following parameter to the /etc/pam.d/xdm file:

session    required     /lib/security/pam_limits.so

2.1.17 Do Not Use the Underscore Character in Host Name

Do not use the underscore character (_)as part of the host name for your Oracle Application Server installation. For example, yourbusiness_name

2.1.18 Installing Oracle Application Server Middle Tier against a Real Application Clusters Database when Some of the Nodes are Down

If you are installing an Oracle Application Server middle tier against a Metadata Repository located on a Real Application Clusters database and some of the nodes of the database are down, you must remove the nodes that are down from the database. Following installation of Oracle Application Server middle tier, these nodes can be added back to the database.

2.1.19 Additional Step Required When Installing OracleAS Web Cache on Multihomed (Multi-IP) Computers

If you specify the secondary hostname using the OUI_HOSTNAME parameter to start up the installer as outlined in the Oracle Application Server Installation Guide, and you are installing OracleAS Web Cache, the OPMN configuration assistant gives the following error:

The OPMN config assistant fails.

The log files located at ORACLE_HOME/opmn/logs/WebCache~WebCacheAdmin~1 and ORACLE_HOME/opmn/logs/WebCache~WebCache~1 contain the following error:

No matching CACHE element found in webcache.xml for current hostname
(primary_hostname) and ORACLE_HOME (/u00/product/as1012secondary)
webcache/webcache.xml contains:
      <CACHE NAME="secondary_hostname-WebCache" [...]
           HOSTNAME="secondary_hostname" [...]

To correct this error, perform the following steps:

  1. Locate the webcache.xml file and open the file for editing.

  2. Locate the following lines in the webcache.xml file:

    <CACHE NAME="secondary_hostname-WebCache" [...]
    HOSTNAME="secondary_hostname" [...]

  3. Replace the HOSTNAME of the CACHE element with the primary hostname:

    <CACHE NAME="secondary_hostname-WebCache" [...]
    HOSTNAME="primary_hostname" [...]

2.1.20 Configuring OracleAS Web Cache to Work Within an OracleAS Cold Failover Cluster

Additional configuration steps are required to configure OracleAS Web Cache to work with a OracleAS Cold Failover Cluster.

Perform the following steps to configure OracleAS Web Cache. In these steps, host1 is the virtual hostname of the active node and host2 is the virtual hostname of the passive node.

  1. Locate and open the webcache.xml file.

  2. Locate the CACHE element:

    <CACHE NAME="host1-WebCache" ORACLEHOME="/myoraclehome/oracle"
    HOSTNAME="host1" VOTES="1" CAPACITY="30" >
...
...
</CACHE>

  3. Add a second CACHE element below the CACHE element you located. Copy and paste the first CACHE element below the first one:

    <CACHE NAME="host1-WebCache" ORACLEHOME="/myoraclehome/oracle"
    HOSTNAME="host1" VOTES="1" CAPACITY="30" >
...
...
</CACHE>
<CACHE NAME="host1-WebCache" ORACLEHOME="/myoraclehome/oracle"
    HOSTNAME="host1" VOTES="1" CAPACITY="30" >
...
</CACHE>

  4. Replace the hostname of the second CACHE element with the hostname of the passive node of your cluster:

    <CACHE NAME="host1-WebCache" ORACLEHOME="/myoraclehome/oracle"
    HOSTNAME="host1" VOTES="1" CAPACITY="30" >
...
...
</CACHE>
<CACHE NAME="host1-WebCache" ORACLEHOME="/myoraclehome/oracle"
    HOSTNAME="host2" VOTES="1" CAPACITY="30" >
...
</CACHE>

  5. Save the file.

  6. Restart OracleAS Web Cache.

2.1.21 Turkish Locale Does Not Display Correctly

When running the Oracle Universal Installer to install Oracle Application Server using the Turkish locale, the Configuration Assistant page will not display properly.

2.2 Oracle Application Server Companion CD 10g (10.1.2.0.2)

This section describes information pertaining to the Oracle Application Server Companion CD 10g (10.1.2.0.2). It includes the following topics:

2.2.1 System Requirements for Oracle Application Server Companion CD 10g

Table 2-1 lists the system requirements for the products on the Oracle Application Server Companion CD 10g (10.1.2.0.2):

Table 2-1 System Requirements

Product Required Disk Space Required Memory

Oracle Application Server Containers for J2EE

56 MB

512 MB

Oracle Application Server TopLink

220 MB

192 MB

Oracle Sensor Edge Server

180 MB

512 MB

Oracle HTTP Server with Apache 1.3

550 MB

512 MB

Oracle HTTP Server with Apache 2.0

450 MB

512 MB

OracleAS Web Cache

400 MB

512 MB

For operating system and hardware requirements, go to:

http://metalink.oracle.com.

2.2.2 Oracle Sensor Edge Server Administrator's Guide

The Oracle Sensor Edge Server Administrator's Guide (Part No. B14455-02) in the Oracle Application Server 10g Release 2 (10.1.2) documentation library is available on OTN (http://www.oracle.com/technology/products).

2.2.3 Install Button on Companion CD Summary Screen Is Disabled

If Oracle Universal Installer prerequisite check fails with warnings, and you proceed to the Install Products screen from Oracle AS 10g Companion CD, then the Install button is disabled on the Summary page.

2.3 Documentation Errata

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

2.3.1 Additional Steps for OracleAS Single Sign-On HA Configuration

Additional steps are required after OracleAS Infrastructure is installed with the OracleAS Cluster (Identity Management) option for OracleAS Single Sign-On. For more information refer to Section 22.1.1, "Additional High Availability Configuration Instructions".

2.3.2 Incorrect File Extensions in Installed Documentation

Documentation that is installed with Oracle Application Server 10g does not use standard file extensions to indicate the applicable language. For example, Chinese files (along with any other file that has an underscore in the extension) are not picked up.

To workaround this issue, change the following file extensions in the ORACLE_HOME/ohs/htdocs directory and all ORACLE_HOME/ohs/htdocs subdirectories:

  • zh_CN -> zh-CN

  • pt_BR -> pt-BR

  • es_ES -> es-ES

  • fr_CA -> fr-CA

  • zh_TW -> zh-TW

2.3.3 Incorrect Path for OracleAS Upgrade Assistant Log File

Due to a typographical error, the Oracle Application Server Quick Upgrade Guide incorrectly identifies the path to the OracleAS Upgrade Assistant log file. The error occurs in the section on troubleshooting the middle-tier upgrade procedure.

The actual location of the OracleAS Upgrade Assistant log file is:

DESTINATION_ORACLE_HOME/upgrade/log/iasua.log

2.3.4 Incorrect Version Number on Forms and Reports CD-ROM

The upgrade.txt file on the Forms and Reports Services installation CD-ROM summarizes how you can upgrade to the Oracle Application Server 10g Release 2 (10.1.2.0.2) Forms and Reports Services installation type.

However, the version number included in that file is incorrect. All references to version 10.1.2.0.1 in that file should in fact be references to version 10.1.2.0.2.

2.3.5 Incorrect Copyright Information

The copyright date in the Copyright Information help topic incorrectly shows the copyright date range. The date range should be: Copyright © 1996-2005, Oracle. All rights reserved.

The link at the bottom of most of the help topics does indicate the proper trademark date range; it's only the copyright information topic itself that contains the incorrect copyright date range.

2.3.6 Incorrect Media Reference in Oracle Application Server Installation Guide

In the Oracle Application Server Installation Guide there are two incorrect references to installation media.

  • OracleAS Guard can be installed as a standalone install kit located on OracleAS Utility media #2.

    should be:

    OracleAS Guard can be installed as a standalone install kit located on OracleAS Companion CD #2.

  • OracleAS 10g (10.1.2.0.2) standalone install of OracleAS Guard is located on Utilities Disk 2.

    should be:

    OracleAS 10g (10.1.2.0.2) standalone install of OracleAS Guard is located on Companion CD Disk 2.

2.3.7 Invalid Instruction to Apply Database Patch

In Section1.5.2.2, "Oracle9i Release 2 (9.2.0.6) Real Application Clusters Databases" in Oracle Application Server Metadata Repository Creation Assistant User's Guide 10g Release 2 (10.1.2) for UNIX, the following information is displayed:

"If you are running a Release 2 (9.2.0.6) database in a Real Application Clusters environment, you need to apply patch 3047933 (ARU 6662789) before you can load the OracleAS Metadata Repository on your database."

This information is incorrect. There is no patch application required.

2.3.8 Incorrect OID Port for Silent Installations

In Oracle Application Server Installation Guide, the OID port used during a silent installation is mentioned as port 389. However, port 389 is a privileged port and requires root access. In a silent installation, root access is not granted until the installation is over. Therefore, if you use port 389, then the following occurs:

OID not able to startup

To avoid this error, do not use the OID port number mentioned in the silent installation example of the installation guide. A commonly used default non-SSL port selected by OUI for OID is 3060. For SSL, this port is 3131. However, in the response file, you only need to specify the non-SSL port.

2.3.9 Incorrect Environmental Variable Recommendation

Section 4.8.3, "Installing on Computers with Multiple Aliases" of the Oracle Application Server Installation Guide incorrectly recommends to use the ORACLE_HOSTNAME variable. If you use the environment variable ORACLE_HOSTNAME as indicated in the Oracle Application Server Installation Guide, Oracle Universal Installer will exit while copying files. Attempts to use other measures during installation, (for example, loopback adapter) will also fail. Before installing Oracle Application Server on the referenced configuration, set the OUI_HOSTNAME environment variable to the computer whose hostname you want to use.

2.3.10 Invalid Limitation on Installing Oracle Application Server in an OracleAS Disaster Recovery Environment

Section 13.3.1, "Installing the OracleAS Infrastructure" in the Oracle Application Server Installation Guide reads:

"You must install the Oracle Identity Management and the OracleAS Metadata Repository components of OracleAS Infrastructure on the same node. You cannot distribute the components over multiple nodes."

This limitation is not true.

2.3.11 Error While Setting Kernel Parameters for Oracle AS Web Cache and Setting Shell Limits

Section 4.4.1, "Kernel Parameter Settings for OracleAS Web Cache" and section 4.5, "Set Shell Limits for the oracle User" of Oracle Application Server Installation Guide (B19310-03), states the kernal parameter commands and values.

When you run ulimit-hn command after performing the steps listed in the guide, the value does not change. It remains 1024. Also, when you use the su command to change to the oracle user, the following error is displayed:

ksh /etc/profile[291]: ulimit: exceeds allowable limit

To workaround these issues, add the following parameter to the /etc/pam.d/xdm file:

session    required     /lib/security/pam_limits.so

2.3.12 Incorrect Symbolic Link Creation Command

In the section 5.6, "Can I use symbolic links?" the commands for creating the symbolic link is incorrect. They correct command is:

mkdir /home/basedir 
ln -s /home/basedir /home/linkdir
  Previous
Previous 		 Next
Next
  Go To Documentation Library
Home		 Go To Table Of Contents
Contents