Skip Headers
Oracle® Application Server Release Notes
10g (10.1.4.0.1) for Linux on POWER

Part Number B32083-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

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 Workaround if HTTP Server Configuration Assistant Fails

If the HTTP Server Configuration Assistant fails during installation, try the following workaround:

  1. Keep the installer open.

  2. Open a shell and log in as root.

  3. Change permissions for the ORACLE_HOME/Apache/Apache/bin/.apachectl file:

    1. Change to the directory containing the .apachectl file.

      > cd ORACLE_HOME/Apache/Apache/bin
      

      ORACLE_HOME is the directory where you are installing Oracle Application Server.

    2. Change the owner to root.

      > chown root .apachectl
      
    3. Change the permissions.

      > chmod 6750 .apachectl
      
  4. In the installer, select the HTTP Server Configuration Assistant and click the Retry button.

    The HTTP Server Configuration Assistant should complete successfully now.

2.1.2 IPv6 Not Supported

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.

2.1.3 Create Symbolic Links Before Installing Oracle Metadata Repository Creation Assistant on Red Hat Enterprise Linux AS/ES 4.0

If you are installing Oracle Metadata Repository Creation Assistant on Red Hat Enterprise Linux AS/ES 4.0, you must perform the following commands prior to installation:

prompt> mkdir /usr/ccs 
prompt> mkdir /usr/ccs/bin 
prompt> ln -s /usr/bin/ar /usr/ccs/bin/ar 
prompt> ln -s /bin/grep /usr/bin/grep 
prompt> ln -s /bin/touch /usr/bin/touch 

If you do not perform these steps, you will get the following errors in the oraInstall<timestamp>.err log file:

ORACLE_HOME/bin/bndlchk: line 62: /usr/ccs/bin/ar: No such file or directory 
ORACLE_HOME/bin/bndlchk: line 62: /usr/bin/grep: No such file or directory 
ORACLE_HOME/bin/bndlchk: line 68: /usr/bin/touch: No such file or directory 

2.1.4 Unique Global Database Name Required During Installation

During installation of either of the install types, Oracle Identity Management and OracleAS Metadata Repository, or OracleAS Metadata Repository, you must enter a unique Global Database Name on the Specify Database Information screen.

If there are 2 databases present on the same host, then each database should have a unique SID and Global Database Name.

Currently, the Oracle Universal Installer only checks if a unique SID is entered by user; it does not check if a Global Database Name is entered by the user. Both the SID and Global Database Name values are entered on the Specify Database Information screen. The installation proceeds with a potential Oracle Internet Directory Configuration Assistant failure. You may see an error message such as the following:

"The Network Adapter could not establish the connection" 

2.1.5 Do Not Use Turkish Locale During Installation

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.

2.1.6 Oracle Application Server Repository Creation Assistant Fails During Loading When the Database Uses Certain Chinese Character Sets

During loading of OracleAS Metadata Repository into an existing database, OracleAS RepCA fails if the database uses the ZHT16MSWIN950, ZHT16HKSCS, or ZHT16HKSCS31 character set.

To check the character set of your database, query the NLS_DATABASE_PARAMETERS view:

sqlplus "sys/password as sysdba"
SQL> select VALUE from NLS_DATABASE_PARAMETERS where PARAMETER='NLS_CHARACTERSET';

where password specifies the password for the SYS user.

2.1.7 OracleAS Cold Failover Cluster: Additional Configuration Steps for Oracle Delegated Administration Services

Additional configuration steps are required to configure Oracle Delegated Administration Services to work with an OracleAS Cold Failover Cluster.

Open the ORACLE_HOME/sysman/emd/targets.xml file and locate the oracle_das_server target and the HTTPMachine, DasURL, and DASMonitorURL properties:

<Target TYPE="oracle_das_server" NAME="instance.domain.com_DAS" DISPLAY_NAME="instance.domain.com_DAS">
   <Property NAME="HTTPMachine" VALUE="LocalHost"/>
   ...
   <Property NAME="DasURL" VALUE="http://LocalHost:7777/oiddas"/>
   <Property NAME="DasMonitorURL" VALUE="http://LocalHost:7777/oiddas/dasmetrics"/>
   ...
</Target>

Change the HTTPMachine, DasURL, and DASMonitorURL property values to the virtual Apache host:

<Target TYPE="oracle_das_server" NAME="instance.domain.com_DAS" DISPLAY_NAME="instance.domain.com_DAS">
   <Property NAME="HTTPMachine" VALUE="VirtualApacheHost"/>
   ...
   <Property NAME="DasURL" VALUE="http://VirtualApacheHost:7777/oiddas"/>
   <Property NAME="DasMonitorURL" VALUE="http://VirtualApacheHost:7777/oiddas/dasmetrics"/>
   ...
</Target> 

2.1.8 Oracle Internet Directory SSL Connection Fail Intermittently

The Oracle Internet Directory SSL connection may fail intermittently during an Oracle Application Server installation. Specifically, this failure may occur during an Identity Management and High Availability collocated installation.

To workaround this issue, retry the failed configuration assistant from the installation.

2.1.9 Incorrect Location for Debug Message

If you encounter Oracle Internet Directory SSL connection failure, the log file (ORACLE_HOME/sso/log/ssoca.log) contains the message of connection failure to LDAP URL, but the correct debug message is ldaps url.

2.1.10 Illegible or Garbage Characters Output in a Russian Locale

When you install Oracle Application Server in Russian locale and some of the configuration assistants fail, you may receive exception message output to Oracle Universal Installer which contain illegible or garbage characters.

If you encounter this type of error message, you can safely ignore the message and continue with the installation and rerun the configuration assistants.

2.1.11 Application Server Control Console Link Not Operational in non-English Installations

In some non-English locale Oracle Application Server installations the Oracle Enterprise Manager 10g Application Server Control Console (Application Server Control Console) hyperlink is not operational on the Welcome page. If the hyperlink is not working in your installation, do the following:

  1. Open the ORACLE_HOME/Apache/Apache/htdocs/index.html file.

  2. Locate the line <a href="http://%s_hostName%:%s_oemConsolePort%" > in the index.html file.

  3. Replace %s_hostName% with your local hostname.

  4. Replace %s_oemConsolePort% with the value of the Application Server Control Console port from the ORACLE_HOME/install/portlist.ini file,

2.1.12 Set the NLS Parameter Before Installing

If you set the following NLS parameters before installation of Oracle Identity Federation through Oracle Application Server:

LANG=zh_CN.GB18030 
LC_ALL=zh_CN.GB18030 

and then check the ORACLE_HOME/dv/OraHome/inventory/Contents/comp.xml file at line 172 you will see the following:

<DEP NAME="oracle.iappserver.charts"VER="10.1.2.0.0" DEP_GRP_NAME="group2" HOME_IDX="5"/> 
Column 43 refers to the beginning of attribute VER, just after the XML attribute value of parameter NAME. 
A whitespace between the double quote and the parameter name is missing. 

If you then install an additional Oracle Identity Federation instance on the same computer, you will receive an error message during the installation.

To workaround this problem, set the NLS parameter as follows:

LANG=zh_CN.GBK 
LC_ALL=zh_CN.GBK 

In Oracle Application Server 10g (10.1.4.0.1), the Java Developer Kit does not support GB18030 encoding.

2.1.13 Excessive Privileges for OracleAS Metadata Repository Installations

This topic is applicable to installations of OracleAS Metadata Repository created with the Oracle Application Server Repository Creation Assistant or installed as part of an OracleAS Infrastructure installation.

The EXECUTE privilege is given to PUBLIC for the following packages:

  • UTL_FILE

  • DBMS_RANDOM

  • UTL_HTTP

  • UTL_SMTP

  • UTL_TCP

These privileges may be excessive, and not necessary for your enterprise.

Oracle recommends that you complete the following steps to determine if the EXECUTE privilege has been applied correctly in your enterprise:

  1. Analyze your application and determine which account / applications require the above packages. If any accounts do require these privileges they will typically be accounts which own applications such as HR or CRM type applications.

  2. Grant execute on the corresponding package to the account / application identified in Step 1. If you were not able to complete the analysis in Step 1, you can optionally grant execute on these packages to the existing application type accounts.

  3. Revoke the EXECUTE privilege for the above packages from the group PUBLIC and verify your application continues to work properly. Completing this step will ensure that new accounts created in the future will not have execute on these packages by default.

2.1.14 Incorrect Guidelines for Online Help

The online help for the Specify Database Configuration Options screen lists the following two guidelines for specifying the global database name:

  • The following characters are valid in the database domain: alphanumeric characters, the underscore (_) character, the minus (-) character, and the pound sign (#) character.

  • The database name can contain only alphanumeric characters (A-Z and 0-9).

These guidelines are incorrect and should be replaced with the following guideline:

  • The following characters are valid in the database domain and domain name: alphanumeric characters, the underscore (_) character, and the pound sign (#) character.

2.1.15 OIDCA Fails Due to Misconfiguration in /etc/hosts

If the virtual hostname specified during a DR/CFC OID installation is an alias hostname instead of valid virtual hostname or IP address, and does not have the domain name configured the system, OUI (OIDCA) may fail. If so, a gethostbyname failed message appears in the $ORACLE_HOME/ldap/log/oidldapd01.log

To resolve this issue, add the domain name to the alias name in the /etc/hosts file, click the Retry button on OUI, and OUI continues to install.

2.1.16 DB Console of Infrastructure IM+MR Cannot be Started

If you install AS 10.1.4IM Infrastructure IM+MR, and try to open the Enterprise Manager using the $ORACLE_HOME/emctl start dbconsole command, you may receive the following error message:

OC4J Configuration Issue.
<ORACLE_HOME>/oc4j/j2ee/OC4J_DBConsole_jphp4d54.jp.oracle.com_infd4 not
found.

To work around this issue, run emca post install as:

.
emca -r

2.1.17 Error While Running RepCA Using runRepCA Command

While running RepCA using runRepCA command against the DB 10.2.0.2 instance, a warning is displayed stating Knowledge Base not found. The following error message is also displayed:

OracleAS RepCA was not able to find the Oracle Text Supplied Knowledge Base 
in the database specified. 
If you are planning to use this repository for installing OracleAS Portal, 
you have to install Oracle Text Supplied Knowledge Base. Oracle Text Supplied 
 
Knowledge Base can be installed in the database using Oracle Database 10g 
Companion CD. 
If you are not planning to use this repository for installing OracleAS 
Portal, 
you may continue further.

Additionally, in the repca_*.log file, the following error message is displayed:

DatabaseSchemaConflict Passed.
Starting validation KNOWLEDGE_BASE_VALIDATION
Starting Knowledge Base validation... 
Repository Creation Assistant was not able to find the Knowledge Base 
install. OracleAS Metadata Repository needs the Knowledge Base to work 
properly. 
Knowledge Base validation completed

These errors messages are generated because Verity filters are not supported on the Linux on POWER platform. You can ignore these error messages, as doing so will not impact the functionality of Portal except for a few PDF search related functionalities.

2.2 Upgrade Issues

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

2.2.1 Clarification of When to Run the Metadata Repository Upgrade Assistant

When you are upgrading to 10g Release 2 (10.1.4.0.1), the Oracle Universal Installer upgrades the OracleAS Identity Management schemas in your database to 10g Release 2 (10.1.4.0.1). This procedure is documented in Chapter 7 of the 10g Release 2 (10.1.4.0.1) Oracle Application Server Upgrade and Compatibility Guide.

However, Oracle Universal Installer does not upgrade the other component schemas in the OracleAS Metadata Repository, such as the OracleAS Portal and OracleAS Wireless schemas.

To determine whether or not you need to run the Metadata Repository Upgrade Assistant (MRUA) to upgrade the component schemas, consider the following:

  • If all the Oracle Application Server middle tiers in your Oracle Application Server environment are currently 10g Release 2 (10.1.2) middle tiers, then it is not necessary to run MRUA, because the component schemas should already be 10g Release 2 (10.1.2) schemas.

    However, you can use the 10g Release 2 (10.1.4.0.1) MRUA to do the following:

    • Verify that the proper component schemas are installed and valid

    • Verify that the database that hosts the OracleAS Metadata Repository has been upgraded to a supported version.

  • If you are currently running Oracle Application Server 10g (9.0.4) middle tiers, then refer to Chapter 5 of the Oracle Application Server Upgrade and Compatibility Guide to determine whether or not you need to upgrade your middle tiers to 10g Release 2 (10.1.2). If you must upgrade your middle tiers to 10g Release 2 (10.1.2), then you must first run MRUA to upgrade the component schemas to 10g Release 2 (10.1.2).

2.2.2 Upgrade of Identity Management Installation to 10.1.4.0.1

If you have the following upgrade:

  • Upgrade your Identity Management installation to 10.1.4.0.1

  • Install Oracle Enterprise Manager 10g Grid Control Plug-in and Oracle Identity Management Grid Control Plug-in Agent

  • Each Identity Management component will display two targets in Oracle Enterprise Manager Grid Control. One target is for the pre-upgrade Identity Management installation, and the other is for the upgraded Identity Management installation.

This is expected behavior because the pre-upgrade Oracle home is still registered with oraInventory. The Oracle Enterprise Manager Grid Control Plug-in Agent discovers all of the Oracle homes on a host and collects information from the respective targets.xml files.

To avoid this problem:

  1. Upgrade your Identity Management installation to 10.1.4.0.1.

  2. Install Oracle Enterprise Manager 10g Grid Control Agent and Oracle Identity Management Grid Control Plug-in Agent.

  3. Remove the pre-upgrade Oracle Application Server Single Sign-On and Oracle Internet Directory targets as follows:

    1. Open the Oracle Enterprise Manager Grid Control.

    2. Select and click Targets.

    3. Select and click All Targets

    4. For each pre-upgrade Oracle Application Server Single Sign-On and Oracle Internet Directory target:

      - Select the target instance

      - Click Remove

For the Oracle Enterprise Manager 10g Grid Control Agent to collect proper monitoring data, you will need to reset the password of the database user dbsnmp of the upgraded Identity Management installation.

To reset the database user password, run the following command (sqlplus "/as sysdba") from the Identity Management database ORACLE_HOME:

> alter user dbsnmp identified by "/dbsnmp_passwd/"; 
> commit; 

2.2.3 Additional Step Required When Upgrading OracleAS Metadata Repository Release 9.0.4.3 to 10.1.4.0.1

If you have applied Oracle Application Server 10g (9.0.4) Patchset 3 (9.0.4.3) to your release 9.0.4 instance, and now want to upgrade the OracleAS Metadata Repository to release 10.1.4.0.1 by running 10.1.4.0.1 MRUA, you must first apply patch 5365207 to your 10.1.4.0.1 MRUA. For this, you must copy the contents of the 10.1.4.0.1 MRUA and Utilities CD–ROM to a location where you have write permission. Then apply patch 5365207 on your 10.1.4.0.1 MRUA staged directory. You can find this patch on My Oracle Support at https://support.oracle.com/.

Use the patched version of 10.1.4.0.1 MRUA to upgrade a release 9.0.4.3 instance to release 10.1.4.0.1. For details about running MRUA, refer to the Oracle Application Server Upgrade and Compatibility Guide.

If you do not apply patch 5365207, then the portal component upgrade will fail with the following error when running 10.1.4.0.1 MRUA:

Calling upgrade plugin for PORTAL
Error: Component upgrade failed PORTAL
Error: PORTAL component version is: 9.0.4.3.0 INVALID

This error message is displayed on screen and is also recorded in the MRUA log file, ORACLE_HOME\upgrade\logs\mrua.log. For the detailed error message, review the portal upgrade precheck log file, ORACLE_HOME\upgrade\temp\portal\precheck.log. Refer to the Oracle Application Server Upgrade and Compatibility Guide for further information on reviewing the upgrade log files.

The detailed error message from the precheck.log file reads as follows:

### Install Schema Validation Utility
>>> Running upg/common/prechk/svuver.sql .
Portal SQL script started at Thu Jun  1 08:55:22 2006
Connected.
# Beginning outer script: common/prechk/svuver
# Portal Schema Version = 9.0.4.3.0
# Version of schema validation utility being installed =
Connected.
###
### ERROR: Exception Executing upg/common/prechk/svuver.sql
###
### Check Failed at Thu Jun  1 08:55:24 2006 Continuing as PreCheck mode is
specified

### Invoke Schema Validation Utility in Report Mode
>>> Running upg/common/prechk/../svurun.sql .
Portal SQL script started at Thu Jun  1 08:55:24 2006
Connected.
# Beginning outer script: common/prechk/svurun
#-- Beginning inner script: common/common/svurun

l_mode := wwutl_schema_validation.MODE_REPORT;

                  *

ERROR at line 5:
ORA-06550: line 5, column 19:
PLS-00201: identifier 'WWUTL_SCHEMA_VALIDATION.MODE_REPORT' must be declared
ORA-06550: line 5, column 9:
PL/SQL: Statement ignored
ORA-06550: line 8, column 19:
PLS-00201: identifier 'WWUTL_SCHEMA_VALIDATION.MODE_CLEANUP' must be declared

ORA-06550: line 8, column 9:
PL/SQL: Statement ignored
ORA-06550: line 15, column 5:
PLS-00201: identifier 'WWUTL_SCHEMA_VALIDATION.VALIDATE_ALL' must be declared

ORA-06550: line 15, column 5:
PL/SQL: Statement ignored
Connected.
###
### ERROR: Exception Executing upg/common/prechk/../svurun.sql REPORT
###
### Check Failed at Thu Jun  1 08:55:25 2006 Continuing as PreCheck mode is
specified

Note:

In the case where you have already encountered this error, apply patch 5365207 and rerun the upgrade. There is no need to restore the OracleAS Metadata Repository from backup before rerunning the upgrade. This is because the upgrade failed during the precheck phase and the portal schema in the OracleAS Metadata Repository has not been altered in the precheck phase.

If the portal upgrade fails in the precheck phase even after applying patch 5365207, then review the precheck log file for details about the new error. Based on the description of the error, resolve the problem and perform the upgrade again, or contact Oracle Support Services for help.

2.2.4 Configuring Port Values for the Load Balancer and Oracle Internet Directory When Upgrading Oracle Application Server Cluster (Identity Management)

The procedure for upgrading to 10g (10.1.4.0.1) Oracle Application Server Cluster (Identity Management) (OracleAS Cluster (Identity Management)) is documented in Appendix B of the Oracle Application Server Upgrade and Compatibility Guide. However, if you are upgrading this type of environment, there is an additional task you must perform if all of the following is true:

  • You are upgrading an OracleAS Cluster (Identity Management) environment to 10g (10.1.4.0.1).

  • Your load balancer and Oracle Internet Directory are using different ports.

  • Your Oracle Internet Directory ports are set to a value less than 1024 and your load balancer ports are set to a value higher than 1024.

In this specific scenario, perform the following steps when you are prompted by Oracle Universal Installer to run the root.sh script:

  1. Use a text editor to open the root.sh file in the Oracle home of the Identity Management instance you are upgrading.

  2. Edit the following two entries in the root.sh file so they point to the SSL and non-SSL port of the Oracle Internet Directory.

    For example:

    SSLPORT=636
    NONSSLPORT=389
    

    Make sure these entries do not point to the load balancer ports.

  3. Save and close the root.sh file.

  4. Run the root.sh file as the root user, as directed by the Oracle Universal Installer instructions.

If you do not perform these steps during the upgrade procedure, the Oracle Internet Directory configuration assistant will fail during the configuration phase of the upgrade procedure.

To fix this problem after the Oracle Internet Directory configuration assistant fails:

  1. Leave Oracle Universal Installer running (with the configuration screen displayed) and open a new terminal window.

  2. From the new terminal window, execute the following commands as the root user in the destination Oracle home:

    chown root <DESTINATION_ORACLE_HOME>/bin/oidldapd 
    chmod 4710 <DESTINATION_ORACLE_HOME>/bin/oidldapd 
    
  3. Return to the Oracle Universal Installer window and retry the Oracle Internet Directory configuration assistant.

2.2.5 Harmless Error Messages During OracleAS Metadata Repository Upgrade

When you upgrade your OracleAS Metadata Repository ORACLE_HOME to 10g (10.1.4.0.1) you may see the following message in the installActions.log file, or the XTERM terminal or DOS command shell window if you are performing a non-interactive installation:

getXMLUserManager:Exception /ORACLE_HOME/in1014MR/sysman/j2ee/config/jazn-data.xml (No such file or directory) 
getRealmUser: XMLUserManager is null 
getXMLUserManager:Exception 
/ORACLE_HOME/in1014MR/sysman/j2ee/config/jazn-data.xml (No such file or directory) 

There is no adverse effects to the installed OracleAS Metadata Repository. The observed messages are only debug messages.

You can ignore the observed messages, there is no adverse effect to the upgrade process.

2.2.6 Metadata Repository Container Version

The Metadata Repository Container (MRC) version in app_registry is 10g (10.1.2.0.2).

There were no schema changes to any OracleAS Metadata Repository components in the 10g (10.1.4.0.1) release. Upgrades from the 10g (10.1.4.0.1) release to the OracleAS Portal (10.1.4.0.0) release is therefore supported.

2.2.7 Issues When Using the ldifwrite Command to Back Up the Oracle Internet Directory

When using the data migration method of upgrading the OracleAS Identity Management, the instructions in Section C.2 of the Oracle Application Server Upgrade and Compatibility Guide instruct you to use the ldifwrite command to backup the Oracle Internet Directory.

When you use the ldifwrite command, you might be prompted to enter the OID password. In response to this prompt, enter the password for the ODS schema in the Oracle Internet Directory database.

If you do not know the ODS schema password, refer to section 6.3, "Viewing OracleAS Metadata Repository Schema Passwords," in the Oracle Application Server Administrator's Guide.

In addition, if you receive an error stating that you cannot connect to the database while attempting to use the ldifwrite command, then try creating a wallet for the Oracle Internet Directory ODS schema password. Use the following command to create a wallet for the password:

oidpasswd connect=<conn_string>           create_wallet=true           current_password=<ods_schema_ password> 

For more information, see the information on the oidpasswd command in Chapter 3, "Oracle Internet Directory Database Administration Tools," in the Oracle Identity Management User Reference.

2.2.8 Upgrade of OracleAS Cold Failover Clusters Fails While Running Configuration Assistant

You can upgrade your OracleAS Cold Failover Clusters environment to Oracle Application Server Release 3 (10.1.4.0.1) using the instructions in Appendix B of the Oracle Application Server Upgrade and Compatibility Guide.

However, for the upgrade to be successful, it is important that the active node in the cluster is associated with the correct virtual hostname and virtual IP address. This allows clients to access the OracleAS Cold Failover Cluster using the virtual hostname.

If you have reconfigured your environment since installing OracleAS Failover Clusters--then the upgrade to Release 3 (10.1.4.0.1) will fail while running the DBMS_IAS_VERSION package Configuration Assistant in Oracle Universal Installer. The installer log files will include the following message:

"DBMS_IAS_VERSION package Configuration Assistant" failed java.sql.SQLException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor 

To remedy this problem, refer the instructions for mapping the Virtual Hostname and Virtual IP address, which are included in the section, "Preinstallation Steps for OracleAS Cold Failover Clusters," in the Oracle Application Server Installation Guide for your platform. Then, run the configuration assistant again. For more information, see the "Configuration Assistants" appendix of the Installation Guide for your platform.

2.3 Documentation Errata

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

2.3.1 Possible Error Message When Decommissioning a 10.1.4.0.1 Oracle Home After Upgrade

Section 10.2, "Task 2: Decommission the OracleAS Identity Management Source Oracle Home," in the Oracle Application Server Upgrade and Compatibility Guide includes instructions for removing the source OracleAS Identity Management instance from the OracleAS Farm. The goal of this procedure is to remove the 10g (10.1.2) instance from the list of Oracle Application Server instances in the farm after you have completed the upgrade to 10g (10.1.4.0.1).

However, in some cases, when you run the dcmctl leavefarm command, as documented in that section, the command fails with the following error:

ADMN-705002

This error can be safely ignored; proceed to the next step in the procedure. There is no harm in leaving the 10g (10.1.2) Oracle home in the list of instances for the farm and in most cases the instance will be removed when you deinstall the instance with Oracle Universal Installer, as described in the next step of the procedure.

2.3.2 Incorrect Line Breaks in MRUA Sample Output

Example 8-1, "Sample Output from an MRUA Session" in the Oracle Application Server Upgrade and Compatibility Guide, shows the output from a typical session with the Metadata Repository Upgrade Assistant. However, in the HTML version of the guide, the line breaks are shown incorrectly. The following lines in the sample output should appear as follows:

Upgrading the OracleAS Metadata Repository to release 10.1.4.0.1. 

Calling upgrade plugin for MRUA
Component upgraded successfully MRUA

2.3.3 Incorrect Global Database Naming Standard

In Table 4-14, "Database Screens", in the Specify Database Identification screen description in the Oracle Application Server Installation Guide, the section incorrectly states that the database name portion of the global database name must contain alphanumeric characters only. This is incorrect. The database name can contain alphanumeric, underscore (_), and pound (#) characters.

2.3.4 Incorrect Table Title in the Installation Guide

In the Oracle Application Server Installation Guide, on Page 2-9, table 2-4 is titled "Software Requirements for Red Hat Enterprise Linux AS/ES 3.0 Systems." This table should be titled "Software Requirements for Red Hat Enterprise Linux AS 4.0 Systems."