2 Installation and Upgrade Issues

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 Oracle Database 10.1.0.4.2 Patch Set Restriction

The Oracle 10.1.0.4.2 Patch Set is intended only for application to Oracle Application Server 10g installations.

2.1.5 Oracle Database 10g (10.1.0.4.2) Patch Set

Before you run OracleAS Metadata Repository Creation Assistant on an Oracle Database 10g (10.1.x) database, you must install the Oracle Database 10g (10.1.0.4.2) Patch Set. This patch is only available on the Oracle Database 10g (10.1.0.4.2) Patch Set CD in the Oracle Application Server 10g Release 2 (10.1.2.0.2) CD pack.

2.1.6 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.7 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.8 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.9 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.10 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.11 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.12 ORA-01031: Insufficient Privileges Error Message

After OracleAS Metadata Repository Creation Assistant is loaded, the log file contains the error ORA-01031: "insufficient privileges".This error occurs during the loading of the OracleAS Syndication product, which is obsolete and is loaded for compatibility purposes. This error can safely be ignored.

2.1.13 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.14 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.15 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.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):

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.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 21.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 Oracle Developer Suite 10.1.2.0.2 Is Not Available with This Release

Although there are references to Oracle Developer Suite 10.1.2.0.2 in the documentation, note that Oracle Developer Suite 10.1.2.0.2 is not available with this release.

2.3.9 Missing Instructions to View the tcp_conn_request_max Parameter

You cannot search for the tcp_conn_request_max parameter through SAM. The commands required to view and change this parameter were not included in Chapter 2, "Requirements" of Oracle Application Server Installation Guide for hp-ux Itanium.

To view this parameter, run the following command:

ndd -get /dev/tcp tcp_conn_request_max

To change the parameter, run the following command:

ndd -set /dev/tcp tcp_conn_request_max value

where value is the value of the tcp_conn_request_max parameter that you need to change.

For example,

ndd -set /dev/tcp tcp_conn_request_max 2048 

2.3.10 Incorrect Response File Parameter Value

In Appendix B, "Silent Installation" of the Oracle Application Server Metadata Repository Creation Assistant User's Guide, section B.2.2.1.1, "Example Response File for Loading OracleAS Metadata Repository in a Database that Uses a File System", under the [ADVANCED] section the following requirement is shown:

SYSTEM_UNDO_TABLESPACE_REQUIREMENT_MET =false

the requirement should be:

SYSTEM_UNDO_TABLESPACE_REQUIREMENT_MET =true

2.3.11 OracleAS Wireless Providers May Not Work After Upgrade

If you have configured geocoding, mapping, or routing providers for Oracle9i Application Server 9.0.2.x, these location-based services for OracleAS Wireless may not work after an upgrade to Oracle Application Server 10g Release 2 (10.1.2).

After the upgrade, you must manually remove all geocoding, mapping, and routing providers using the Application Server Control Console. Specifically, you can manage location-based services by using the Location Services link in the Component Configuration section of the Site Administration page, which is available from the OracleAS Wireless Home page in the Application Server Control Console.

For more information about location-based services for OracleAS Wireless, refer to Location Based Services for OracleAS Wireless on OTN at:

http://www.oracle.com/technology/products

2.3.12 Incorrect Information About the rlim_fd_max Parameter

Section 2.8 "New Kernel Parameter Required by OracleAS Web Cache" of Oracle Application Server Installation Guide for hp-ux Itanium is not applicable to HP-UX Itanium.

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