3 Installation and Upgrade Issues

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

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

3.1.3 Oracle Database10.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.

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

3.1.5 Non-English Welcome Pages URL Link Pages Incorrectly Coded

Non-English Oracle Application Server 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.

3.1.6 Harmless Error Message

After you install Oracle Application Server 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 can be ignored.

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

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

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

3.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 the Oracle Application Server Upgrade and Compatibility Guide.

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

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

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

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

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

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

3.2.1 System Requirements for Oracle Application Server Companion CD 10g

Table 3-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.

3.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).

3.3.1 Login Link Inoperable

After you perform an upgrade of Oracle Application Server 10g from version 9.0.4 to version 10.1.2, the Oracle Enterprise Manager 10g login link on the welcome page no longer works. During installation, the port number specified for Oracle Enterprise Manager 10g for version 9.0.4 installation is not updated in the version 10.1.2 welcome pages.

3.3.2 Remaining OracleAS Infrastructure Instance in Farm

After you complete an upgrade of OracleAS Infrastructure in an OracleAS Farm, the pre-upgrade instance of the infrastructure still remains in the farm. Specifically, the pre-upgrade instance continues to show up on the Farm page in the Application Server Control Console. There is currently no way to remove the pre-upgrade instance. The remaining instance will not cause any operational problems with the upgraded infrastructure.

Note that you can remove middle tier instances from the OracleAS Farm; however, you must remove the middle tiers from the OracleAS Farm before deinstall the middle tiers. For more information, see "Removing the Source Oracle Home from the OracleAS Farm" in Chapter 4, "Upgrading the Middle Tier" in the Oracle Application Server Upgrade and Compatibility Guide.

3.3.3 Problem Running the mod_osso Configuration Assistant When Upgrading an Oracle Internet Directory in a Partial Replication Environment

When you are upgrading Identity Management in an environment in which Oracle Internet Directory partial replication is used, the mod_osso Configuration Assistant may fail at the end of upgrade.

If this problem occurs, do not exit Oracle Universal Installer. Instead, leave the program running and perform the following workaround in a separate window:

1. Using a text editor, open the following file in the Oracle home of the replica you are upgrading:

   ORACLE_HOME\config\infratool_mod_osso.properties
   
   

2. Modify the contents of the file so it reads as follows:

   DCMRESYNC=oracle.ias.configtool.configimpl.DcmResync$0
   JAZN=oracle.security.jazn.util.JAZNConfigTool$0
   HTTPD=oracle.ias.configtool.configimpl.HttpdSsoConfig$0
   MODOSSO=oracle.ias.configtool.configimpl.SsoConfig$0
   
   

3. Save and close the infratool_mod_osso.properties file.

4. Return to Oracle Universal Installer and try to run the configuration assistant again.

3.3.4 Problems or Issues While Upgrading Specific Components

If you experience problems or issues while upgrading a particular application server component, refer to the component chapter in these release notes for more information.

For example, if you experience problems while upgrading Oracle Ultra Search, refer to Chapter 10, "Oracle Ultra Search".

3.3.5 Configuring OracleAS Portal After Upgrade

If OracleAS Portal is not configured in the source oracle home, it remains unconfigured after the upgrade to 10g Release 2 (10.1.2).

Note that you can choose to configure the OracleAS Portal after upgrading the middle tier or at the end of the entire upgrade process, after upgrading the OracleAS Metadata Repository.

To configure the Portal post upgrade, do following:

1. Modify the port entries in the following file:

   DESTINATION_ORACLE_HOME\assistants\opca\ptlem.bat
   
   

   Update the following port values in the ptlem.sh file with the corresponding source port values, as follows:

   • http_port, which is the Oracle HTTP Server port

   • wc_invalid, which is the Web Cache Invalidation port

   • wc_admin, which is the Web Cache Administration port

   • em_port, which is the Application Server Control port

   You can obtain all these port values, except http_port, from Ports page in the Application Server Control Console.

   To obtain the http_port value, check the contents of the following configuration file:

   DESTINATION_ORACLE_HOME\Apache\Apache\conf\httpd.conf
   
   

2. Use the Application Server Control Console to configure the OracleAS Portal component.

   
   

   See Also: " Configuring Additional Components" in the in the Application Server Control online help

   
   

3. Run ptlconfig command to associate the OracleAS Portal repository with the upgraded middle tier, as follows:

   DESTINATION_ORACLE_HOME\portal\conf\ptlconfig -dad portal_dad
   
   

   Refer to the Oracle Application Server Portal Configuration Guide for more information about the iasconfig.xml and the ptlconfig tool.

If you have already configured OracleAS Portal using the Application Server Control Console, without updating the ports in the ptlem.bat file, then you must also perform the following task:

1. Modify the port entries in the ptlem configuration file, as described previously in this section.

2. Backup the following Oracle Enterprise Manager configuration file:

   DESTINATION_ORACLE_HOME\sysman\emd\targets.xml
   
   

3. Remove the entry for the OracleAS Portal target you are about to reconfigure.

   You must review the entire entry that defines the OracleAS Portal target, starting with the <Target TYPE="oracle_portal"> tag and ending with the </Target> tag.

   For example:

    <Target TYPE="oracle_portal"
            .
            .
            .
   </Target>
   
   

   Before removing target entry for this portal, make sure that this target contains property <Property NAME="portal_DAD" VALUE="portal"/> and that its OracleHome property matches the destination middle tier Oracle home.

4. Save the targets.xml file.

5. Set the ORACLE_HOME environment variable to the destination Oracle home.

6. Run the ptlem script as follows:

   DESTINATION_ORACLE_HOME\assistants\opca\ptlem.bat
   
   

7. Check the log file for any errors:

   DESTINATION_ORACLE_HOME\assistants\opca\install.log
   
   

8. Update the following OracleAS Portal configuration file with new port values for the WebCacheComponent and EMComponent elements:

   DESTINATION_ORACLE_HOME\portal\conf\iasconfig.xml
   
   

   You can obtain the required port numbers from the Ports page in the Application Server Control Console.

9. Run the ptlconfig command to associate the OracleAS Portal repository with the upgraded middle tier, as follows:

   DESTINATION_ORACLE_HOME\portal\conf\ptlconfig -dad portal_dad
      [-pw <portal schema password>]
   
   

Refer to the Oracle Application Server Portal Configuration Guide for more information about the iasconfig.xml configuration file and the ptlconfig tool.

3.3.6 Upgrading from Oracle Application Server 9.0.4 to 10g Release 2 (10.1.2) May Overwrite Custom Ordering of Categories in Oracle Delegated Administration Services

Upgrading Oracle Application Server from 9.0.4 to 10g Release 2 (10.1.2) may overwrite any customized ordering of categories that you have configured for Oracle Delegated Administration Services. If this occurs, you must use the Order Category window in the Oracle Internet Directory Self-Service Console to reorder your category list following the upgrade process.

3.3.7 During Upgrade, References to the Source Oracle Home in OracleAS Forms Services Configuration Files are Case-Sensitive

When you run the OracleAS Upgrade Assistant to upgrade your middle tier Oracle homes, be aware that the OracleAS Upgrade Assistant uses information in the OracleAS Forms Services configuration files to locate the files it needs upgrade.

However, note that references to the locations in your source Oracle home are case-sensitive, even on the Windows platform.

For example, if the actual Oracle home is C:\asHome\ and the configuration file references a file located in the C:\AShome directory, the OracleAS Upgrade Assistant will be unable to locate and upgrade that file.

To avoid this problem, check the contents of the following configuration files and make sure that all references to the source Oracle home are in the proper case:

• web.xml

• oc4j_bi_forms.properties

• oc4j.properties

3.3.8 During Upgrade, The Parameters Names Defined in formsweb.cfg are Considered Case-sensitive

If you have specified a user-defined configuration file using the envFile parameter in one of the application sections of formsweb.cfg, you must make sure that the case used to specify the parameter envFile must be the same case as described in the default application section of the file.

Otherwise, the user-defined configuration files will not be found or upgraded by the middle-tier OracleAS Upgrade Assistant.

3.3.9 OracleAS Forms Services Upgrade Fails While Deploying OracleAS Forms Services EAR File

If you are upgrading a Business Intelligence and Forms Oracle home to Oracle Application Server 10g Release 2 (10.1.2) and the OracleAS Forms Services upgrade fails, then check the OracleAS Upgrade Assistant log file:

DESTINATION_ORACLE_HOME/upgrade/log/iasua.log

If you see the following error in the iasua.log file, then run the OracleAS Upgrade Assistant again:

Forms: Caught exception
oracle.ias.sysmgmt.deployment.j2ee.exception.J2eeDeploymentException: Nested
exception
Resolution:
Base Exception:
This DCM Client Session has been invalidated due to DCM Daemon restart. All
unsaved changes will be lost.
Forms: Caught exception oracle.ias.upgrade.config.oc4j.Oc4jUpgradeException:
Caught exception
ERROR:1 Forms: Error deploying Forms ear file for the user application
appliation_name
NOTIFICATION:1 Framework: Finished upgrading Forms with status: Failure.

The OracleAS Forms Services component should upgrade successfully the second time you run the OracleAS Upgrade Assistant.

3.3.10 Identity Management Not Starting Following Upgrade of Seed Database

A seed database is a database that was originally installed and configured automatically by the Oracle Application Server installation procedure. In most cases, there is no need to manually upgrade a seed database, except as part of an overall upgrade of the OracleAS Infrastructure components. The upgrade of the OracleAS Infrastructure components is documented in the Oracle Application Server Upgrade and Compatibility Guide.

However, it is possible to manually upgrade an Oracle Application Server seed database to a newer database version without upgrading your Oracle Application Server environment. When you finish upgrading the database, it is no longer referred a seed database; instead, it is sometimes referred to as a "customer" database. As a result, this manual upgrade procedure is sometimes referred to as the "seed-to-customer" database upgrade procedure.

Note that If you upgrade your seed database to Oracle Database 10g (10.1.0.4.2), the Distributed Configuration Management (DCM) daemon in the Oracle Application Server Identity Management instance may not start. This is due to an Oracle Notification Server (ONS) port conflict between the Identity Management instance and the upgrade 10g customer database. The ONS port of the Identity Management instance is already in use by the upgraded 10g database.

To work around this issue, update the local port file element in the following configuration file to a non-conflicting port value:

DATABASE_HOME\opmn\conf\ons.config

3.3.11 ORACLE_HOME Value Not Replaced In workingDirectory In formsweb.cfg

The OracleAS Upgrade Assistant does not replace any references to the source ORACLE_HOME with the desination ORACLE_HOME in the workingDirectory parameter in formsweb.cfg.

As a workaround, after running the OracleAS Upgrade Assistant, replace the references to the source ORACLE_HOME with the location of the destination ORACLE_HOME for the workingDirectory parameter in formsweb.cfg.

3.3.12 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

3.4.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 Chapter 22, "Oracle Application Server Single Sign-On".

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

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

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

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

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

3.4.7 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