2 Installation Issues

2.1.1 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.2 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.3 Oracle Database 10g (10.1.0.4.2) Patch Set

Before you run REPCA 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.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 Harmless Error Message

After you install Oracle Internet Directory middle tier (J2EE and Web Cache, Portal and Wireless, and Business Intelligence and Forms) you will see java.io.FileNotFoundException error message in the inventory_location\logs\oraInstalltimestamp.err log file. (The default inventory_location is C:\Program Files\Oracle\Inventory.)

This error message is harmless and can be ignored.

2.1.6 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.7 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.8 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.9 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 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

• 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.10 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.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.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).