Oracle® Application Server Release Notes 10g Release 2 (10.1.2) for HP-UX PA-RISC (64-bit) B25187-09 |
|
Previous |
Next |
This chapter describes installation and upgrade issues and their workarounds associated with Oracle Application Server. It includes the following topics:
This section describes issues with installation of Oracle Application Server. It includes the following topics:
Section 2.1.2, "Do Not Use the Underscore Character in Host Name"
Section 2.1.5, "Failure of File-Based Farm Repository Configuration Assistant"
Section 2.1.6, "Response Files Created through the Record Mode Are Not Supported"
Section 2.1.7, "Oracle Database 10.1.0.4.2 Patch Set Restriction"
Section 2.1.9, "Non-English Welcome Pages URL Link Pages Incorrectly Coded"
Section 2.1.13, "Installing 10.1.2.0.2 Middle Tiers Against an Existing Infrastructure"
Section 2.1.14, "IBM WebSphere Required Patch Version 6.0.2"
Section 2.1.15, "ORA-01031: Insufficient Privileges Error Message"
Section 2.1.16, "Oracle Ultra Search Required (Oracle Database 10g Release 2 (10.2.x) only)"
Section 2.1.19, "Installer Displays Incorrect Version Number"
Section 2.1.20, "JAccelerator (Ncomp) Is Not Installed with OracleAS Metadata Repository 10.1.2.x"
Section 2.1.23, "Configuring OracleAS Web Cache to Work Within an OracleAS Cold Failover Cluster"
Section 2.1.26, "TEMP Tablespace Required for Metadata Repository Creation Assistant"
Section 2.1.27, "OPatch Not Supported with OC4J Standalone Installations"
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.
Do not use the underscore character (_)as part of the host name for your Oracle Application Server installation. For example, yourbusiness_name
.
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.
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.
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.
If you want to run the installer with a response file (to perform a silent or non-interactive installation), you cannot use response files created through the -record
command-line option in the installer, as described in the "Creating Response Files by Using the Record Mode in the Installer" section in the Oracle Application Server Installation Guide. Instead, you must use response files that were created from the provided response file templates; you replace the placeholder values in the template files with your own values.
The Oracle 10.1.0.4.2 Patch Set is intended only for application to Oracle Application Server 10g installations.
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.
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
.
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.
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.
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.
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.
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.
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.
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 (https://www.metalink.oracle.com
) Note 337992.1 for loading Ultra Search schemas.
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:
Install the 10.2 Real Application Cluster database.
Create the database using the DBCA or during the installation.
Stop all Oracle Processes.
Install Oracle Ultra Search in the same Oracle home from the companion CD.
Apply ARU patch 7993184. Go to Oracle MetaLink (https://www.metalink.oracle.com
) to obtain the ARU patch.
Invoke the DBCA to configure Oracle Ultra Search.
Run the Metadata Repository Creation Assistant.
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
.
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.
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.
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.
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:
Locate the webcache.xml
file and open the file for editing.
Locate the following lines in the webcache.xml
file:
<CACHE NAME="secondary_hostname-WebCache" [...] HOSTNAME="secondary_hostname" [...]
Replace the HOSTNAME
of the CACHE
element with the primary hostname:
<CACHE NAME="secondary_hostname-WebCache" [...] HOSTNAME="primary_hostname" [...]
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.
Locate and open the webcache.xml
file.
Locate the CACHE
element:
<CACHE NAME="host1-WebCache" ORACLEHOME="/myoraclehome/oracle" HOSTNAME="host1" VOTES="1" CAPACITY="30" > ... ... </CACHE>
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>
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>
Save the file.
Restart OracleAS Web Cache.
Important: Before upgrading the database that hosts your Oracle Application Server Release 2 (10.1.2) Metadata Repository, be sure to verify that the database version is supported. Go to Table 4, "Oracle Application Server Certified Oracle Databases" in the Oracle Application Server Certification Information on OTN:( |
To add support for a new database release to either the 10.1.2.0.2 or 10.1.4.0.0 versions of the OracleAS Metadata Repository Upgrade Assistant, complete the following steps:
Open the $ORACLE_HOME
/mrua/mrua.xml
in a text editor.
If you are using the OracleAS Metadata Repository Upgrade Assistant CD ROM you must copy the contents of the CD to a writable directory to perform the edit.
Add the following entry to the $ORACLE_HOME
/mrua/mrua.xml
file. (In the following example RDBMS 10.2.0.2 is used):
<Version ReleaseNumber="10.2.0.2" DisplayName="OracleAS supported database"> </Version>
Save the edited $ORACLE_HOME
/mrua/mrua.xml
file and run MRUA.
Run the OracleAS Metadata Repository Upgrade Assistant.
When running the Oracle Universal Installer to install Oracle Application Server using the Turkish locale, the Configuration Assistant page will not display properly.
The TEMP tablespace must exist in any database on which you run the Metatdata Repository Creation Assistant. If the TEMP tablespace does not exist, create it before you run the Metadata Repository Creation Assistant.
You cannot apply a patch to an OC4J standalone installation using OPatch. If you attempt to do so, you will get the following error:
None of the patch actions is applicable to the Oracle Home. OPatch will not apply the patch, exiting...
Oracle Application Server Installation Guide 10g Release 2 (10.1.2) contains a section titled "Installing Middle Tiers Against OracleAS Cluster (Identity Management) Configurations." The following is additional information about installing a middle tier against Oracle Identity Management (OID) with Multimaster Replication (MMR).
If you have a geographically distributed MMR OID installation, the middle tiers should be installed in each location pointing to the local OID address.
If MMR is used intrasite with a load balancer, then the middle tiers should be installed against the load balancer front-ending the two OIDs and the customer needs to configure the LDAP load balancer that they are using for OID so that it points to only one OID node. Once the installation is completed, the load balancer can be configured back to the way it was originally.
For more information, refer to OracleMetaLink Note 370433.1 Master Note: How to Setup and Configure MultiMaster Replication (MMR) with Identity Management (IM) Cluster in High Availability Env.
If you are installing OracleAS Infrastructure, and you are installing on a machine that uses a virtual hostname, you can specify the virtual hostname in the installer by selecting the High Availability and Replication option. See the following documentation for detailed installation instructions:
If you are installing Oracle Identity Management and OracleAS Metadata Repository, see the section titled "OracleAS Cold Failover Cluster (Infrastructure): Details of Installation Steps" in Oracle Application Server Installation Guide 10g Release 2 (10.1.2) for your operating system.
If you are installing Oracle Identity Management only, see the section titled "OracleAS Cold Failover Cluster (Oracle Identity Management): Details of Installation Steps" in Oracle Application Server Installation Guide 10g Release 2 (10.1.2) for your operating system.
This section describes information pertaining to the Oracle Application Server Companion CD 10g (10.1.2.0.2). It includes the following topics:
Section 2.2.1, "System Requirements for Oracle Application Server Companion CD 10g"
Section 2.2.2, "Oracle Sensor Edge Server Administrator's Guide"
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 |
72 MB |
512 MB |
Oracle Application Server TopLink |
258 MB |
192 MB |
Oracle Sensor Edge Server |
284 MB |
512 MB |
Oracle HTTP Server with Apache 1.3 |
1.3 GB |
512 MB |
Oracle HTTP Server with Apache 2.0 |
1.29 GB |
512 MB |
OracleAS Web Cache |
1.23 GB |
512 MB |
For operating system and hardware requirements, go to:
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
).
This section describes issues with the upgrade of Oracle Application Server. It includes the following topics:
Section 2.3.1, "WWU-01012 Error During Portal Repository Upgrade"
Section 2.3.3, "Remaining OracleAS Infrastructure Instance in Farm"
Section 2.3.5, "Problems or Issues While Upgrading Specific Components"
Section 2.3.8, "Identity Management Not Starting Following Upgrade of Seed Database"
Section 2.3.9, "ORACLE_HOME Value Not Replaced In workingDirectory In formsweb.cfg"
Section 2.3.10, "OracleAS Wireless Providers May Not Work After Upgrade"
Section 2.3.11, "New ODS Password After Oracle Identity Management Upgrade"
If your OracleAS Portal repository is configured in an Oracle Real Application Clusters (RAC) database, then your Portal repository upgrade to 10g Release 2 (10.1.2) can sometimes fail and the following error message will appear in the upgrade error log:
ERROR: WWU-01012: Upgrade completed with the following errors ### 177 : ERROR at line 1: ### 178 : ORA-38301: can not perform DDL/DML over objects in Recycle Bin
How To Work Around this Problem
If you receive this error, you can workaround the problem, as follows:
Connect to the database from SQL*Plus as the SYS user.
Run the following command:
purge recyclebin;
Perform the upgrade again.
How To Avoid this Problem Before an Upgrade
To avoid this issue before you begin an upgrade of the Portal repository when it is stored in a RAC database:
Connect to the database from SQL*Plus as the SYS users.
Enter the following query:
SELECT object_name, original_name, type, droptime FROM user_recyclebin;
If the query returns 'no rows selected
', then no additional action is required.
If the query returns any rows, then purge the recycle bin by running following SQL statement after connecting to Database from sqlplus as SYS:
purge recyclebin;"
Perform the Portal repository upgrade as directed.
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.
There is presently no workaround for this issue.
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.
When you are upgrading Identity Management in an environment in which Oracle Internet Directory partial replication is used, a problem while running the upgrade with Oracle Universal Installer: 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:
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
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".
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:
Modify the port entries in the following file:
DESTINATION_ORACLE_HOME/assistants/opca/ptlem.sh
DESTINATION_ORACLE_HOME/Apache/Apache/conf/httpd.conf
DESTINATION_ORACLE_HOME/portal/conf/ptlconfig -dad portal_dad
If you have already configured OracleAS Portal using the Application Server Control Console, without updating the ports in the ptlem.sh
file, then you must also perform the following task:
Modify the port entries in the ptlem configuration file, as described previously in this section.
Backup the following Oracle Enterprise Manager configuration file:
DESTINATION_ORACLE_HOME/sysman/emd/targets.xml
DESTINATION_ORACLE_HOME/assistants/opca/ptlem.sh
DESTINATION_ORACLE_HOME/assistants/opca/install.log
DESTINATION_ORACLE_HOME/portal/conf/iasconfig.xml
DESTINATION_ORACLE_HOME/portal/conf/ptlconfig -dad portal_dad
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.
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.
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.
After upgrade of your seed database to a 101042 customer database (rdbms install), the 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 seed 101042 customer database. The ONS port of the Identity Management instance is already in use by the seed 101042 customer database.
To workaround this issue, update the local port file element in the $DATABASE_HOME/opmn/conf/ons.config
file.
Note: The seed database is created when you use the Oracle Application Server installation procedure to create a new database for the OracleAS Metadata Repository. You then use the Oracle Universal Installer to install Oracle Application Server 10g (10.1.2) and upgrade the database automatically. This type of OracleAS Metadata Repository database is referred to as a seed database, because the database was created automatically by the Oracle Application Server installation procedure specifically for hosting the OracleAS Metadata Repository. For more information refer to the Oracle Application Server Upgrade and Compatibility Guide. |
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
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
.
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
The ODS password is required when you perform certain Oracle Internet Directory administration tasks, such as when you have to unlock a user account or configure security for the directory.
After you upgrade Oracle Identity Management to 10g Release 2 (10.1.2), the ODS password in the upgraded, destination Oracle home will no longer be the same as it was in the source Oracle home. Instead, the ODS password in the destination Oracle home is the same as the ias_admin
password you provided for the new Oracle Application Server 10g Release 2 (10.1.2) instance during the upgrade procedure.
The section describes documentation errata in installation and upgrade documentation. It includes the following topics:
Section 2.4.1, "Additional Information About Changing the SYS Password"
Section 2.4.4, "Additional Steps for OracleAS Single Sign-On HA Configuration"
Section 2.4.5, "Incorrect File Extensions in Installed Documentation"
Section 2.4.6, "Incorrect Path for OracleAS Upgrade Assistant Log File"
Section 2.4.7, "Incorrect Version Number on Forms and Reports CD-ROM"
Section 2.4.9, "Incorrect Media Reference in Oracle Application Server Installation Guide"
Section 2.4.10, "Invalid Instruction to Apply Database Patch"
Section 2.4.11, "Oracle Developer Suite 10.1.2.0.2 Is Not Available with This Release"
Section 2.4.12, "Obsolete Kernel Parameters for OracleAS Metadata Repository"
Section 2.4.13, "Missing Instructions to View the tcp_conn_request_max Parameter"
Section 2.4.14, "Incorrect OID Port for Silent Installations"
Section 2.4.16, "Incorrect Environmental Variable Recommendation"
Section 2.4.22, "OracleAS Cluster (Identity Management) Installed Language"
Section 2.4.24, "Information About ADF Configuration Assistant Missing"
The Oracle Application Server Metadata Repository Creation Assistant User's Guide contains the following note:
"The value that you specify for password parameter sets the password for the SYS user. If you specify a different value from the current SYS password, you are changing the SYS password."
This note should be changed to:
"This value that you specify for password parameter sets the password for the SYS user. If you issue the ALTER USER statement to change the password for SYS after connecting to the database, both the password stored in the data dictionary and the password stored in the password file are updated. This parameter is mandatory."
The updated text matches the text in the Oracle Database Administrator's Guide.
In the Oracle Application Server Metadata Repository Creation Assistant User's Guide, Ultra Search is not listed as a prerequisite for Oracle Database 9.2.
This is incorrect; the Ultra Search must be configured in Oracle Database 9.2 before OracleAS Metadata Repository Creation Assistant can be run.
In the Oracle Application Server Metadata Repository Creation Assistant User's Guide, additional clarification is required for the compatible
initialization parameter in (Table 1-7):
The compatible
parameter must be specified using at least 4 decimal places. For example, "9.2.0.0" and "9.2.0.0.0" are both acceptable, but "9.2.0" is not acceptable.
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 25, "Oracle Application Server Single Sign-On".
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
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
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.
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.
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.
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.
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.
In Section 4.4.2 "Kernel Parameter Settings for OracleAS Metadata Repository" of Oracle Application Server Installation Guide for hp-ux PARISC (64-Bit), some of the listed kernel parameters are not required for installing OracleAS Metadata Repository. These parameters are:
maxswapchunks
maxusers
semmap
ncallout
vx_ncsize
In addition, for the ncsize kernel parameter the value has changed as follows:
ncsize = ninode+1024
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.
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
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.
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
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.
Oracle Application Server Installation Guide does not include details about supported browsers.
The following browsers are supported on this operating system:
Microsoft Internet Explorer 6.0 with service pack 2 or later (supported on Microsoft Windows only)
Netscape 7.2
Mozilla 1.7. You can download Mozilla from http://www.mozilla.org
.
Firefox 1.0.4. You can download Firefox from http://www.mozilla.org
.
Safari 1.2 (on Apple Macintosh computers)
For the most current list of supported browsers, check the OracleMetaLink site at
Section 4.2.2, "Installing from the Console or X Windows" of Oracle Application Server Installation Guide incorrectly specifies the file directory path as
/etc/pamd.d/xdm
It should be /etc/pam.d/xdm
.
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.
In the section 5.6, "Can I use symbolic links?" the commands for creating the symbolic link is incorrect. The correct command is:
mkdir /home/basedir ln -s /home/basedir /home/linkdir
Section 4.6.4.6.2, "CTS Compatibility and JDBC," in the Oracle Application Server Upgrade and Compatibility Guide provides information about CTS compatibility mode and Oracle JDBC. The information about the Oracle JDBC NUMBER type in this section is incomplete.
For the latest information concerning Oracle JDBC floating-poing compliance, see "IEEE 754 Floating Point Compliance" in the "Oracle JDBC Notes and Limitations" section of the Oracle Database JDBC Developer's Guide and Reference, which is part of the Oracle Database documentation library on the Oracle Technology Network (OTN):
http://www.oracle.com/technology/documentation/index.html
This is a correction to the Oracle Application Server Installation Guide, Section 12.5.4, Installing on High Availability Environments: OracleAS Cluster (Identity Management).
When installing OracleAS Cluster (Identity Management) on subsequent nodes:
Select an identical set of languages during the installation as for the first node.
Do not disable any languages installed for the first node before installing all of the required subsequent nodes. Disabling languages can result in failure of the Single Sign On Configuration Assistant.
In table I-9, "Schemas and Tablespaces" of the Oracle Application Server Metadata Repository Creation Assistant User's Guide, the row that starts with Oracle Enterprise Manager 10g is an error and should be ignored.
Table A-1, "Forms and Reports Configuration Assistants" of Oracle Application Server Forms and Reports Services Installation Guide does not include the information about ADF configuration assistant.
For more information on the log file location and description, refer to the second table "Oracle Application Server Configuration Assistants" in the appendix chapter "Configuration Assistants" of Oracle Application Server Installation Guide.