| Oracle® Application Server Release Notes 10g Release 2 (10.1.2) for Solaris Operating System (x86) and Solaris Operating System (x86-64) B25853-05 |
|
 Previous |
 Next |
| Oracle® Application Server Release Notes 10g Release 2 (10.1.2) for Solaris Operating System (x86) and Solaris Operating System (x86-64) B25853-05 |
|
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.3, "Additional Steps for Installation on the Solaris10 Operating System"
Section 2.1.6, "Failure of File-Based Farm Repository Configuration Assistant"
Section 2.1.7, "Response Files Created through the Record Mode Are Not Supported"
Section 2.1.8, "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, "Disk Space Needed on a Database that Uses Automatic Storage Management"
Section 2.1.17, "Set ORACLE_HOME Before Running root.sh Script"
Section 2.1.18, "Oracle Ultra Search Required (Oracle Database 10g Release 2 (10.2.x) only)"
Section 2.1.21, "Installer Displays Incorrect Version Number"
Section 2.1.22, "JAccelerator (Ncomp) Is Not Installed with OracleAS Metadata Repository 10.1.2.x"
Section 2.1.25, "Configuring OracleAS Web Cache to Work Within an OracleAS Cold Failover Cluster"
Section 2.1.28, "Incorrect Solaris Integration Installer Error Message"
Section 2.1.30, "TEMP Tablespace Required for Metadata Repository Creation Assistant"
Section 2.1.31, "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.
This section describes the additional steps necessary for installing Oracle Application Server on the Solaris10 Operating System. These steps can be used in conjunction with the installation instructions described in the Oracle Application Server Quick Installation and Upgrade Guide, Oracle Application Server Installation Guide, and the Oracle Application Server Upgrade and Compatibility Guide.
Oracle Application Server has been certified to work in Solaris10 non-global (local) and global containers.
This section contains the following topics:
Section 2.1.3.3, "/etc/system Requirements for Installation"
Section 2.1.3.4, "Database Configuration Assistant Patch Installation"
Section 2.1.3.5, "Support for IP Multipathing and Multiplexing"
Check that your computer contains the following operating system packages. If the packages are not present, Oracle Universal Installer cannot continue.
SUNWarc
SUNWbtool
SUNWhea
SUNWlibm
SUNWlibms
SUNWsprot
SUNWtoo
SUNWi1of
SUNWi1cs
SUNWi15cs
SUNWxwfnt
To check if an operating system package is installed on your computer, run the pkginfo command with the name of the package. The syntax for running pkginfo is:
pkginfo package_name1 package_name2 ...
For example, to check if all of the listed packages are installed on your computer, run the following command:
prompt> pkginfo SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprot SUNWtoo SUNWi1of SUNWi1cs SUNWi15cs SUNWxwfnt
If your computer is missing a package, contact your system administrator.
In Solaris 10, all System V interprocess communication (IPC) facilities are either automatically configured or controlled by resource controls.
Many applications that previously required system tuning to function may now run without tuning because of increased defaults and the automatic allocation of resources.
Solaris 10 IPC tunable default values are higher than those recommended by Oracle. Therefore, no additional operating system tuning is required.
As part of the pre-requisite checks conducted by Oracle Universal Installer prior to installation of Oracle Application Server, kernel parameters are inspected in the /etc/system file. However, the kernel values described in the Oracle Application Server Installation Guide are not used on the Solaris 10 system.
As a workaround, make changes to kernel parameter values in the /etc/system file as indicated in the Requirements chapter of the Oracle Application Server Installation Guide prior to installation of Oracle Application Server. Following installation of Oracle Application Server on the Solaris 10 system, remove the changes you made to the values specified in the /etc/system file.
In summary, the changes made to the kernel parameters in the /etc/system file should be temporary and should be undone after installation of Oracle Application Server is completed.
If you are installing the Oracle Application Server Infrastructure, and encounter failure during the running of the Database Configuration Assistant, you must apply patch 4590858. This patch is available from Oracle MetaLink (http://www.metalink.oracle.com).
Do not use the OPatch installer, as instructed in the README.txt that accompanies the patch 4590858. After you have downloaded the required patch to your system, use the following steps to manually install the patch:
> cp $ORACLE_HOME/lib/libgeneric10.a $ORACLE_HOME/lib/libgeneric10.a_prepatch
> cp $ORACLE_HOME/lib32/libgeneric10.a $ORACLE_HOME/lib32/libgeneric10.a_prepatch
> cd <Replace_With_Path_To_Patch_Directory>/4590858/files
> ar r $ORACLE_HOME/lib/libgeneric10.a lib/libgeneric10.a/skgsn.o
> ar r $ORACLE_HOME/lib32/libgeneric10.a lib32/libgeneric10.a/skgsn.o
> cp $ORACLE_HOME/bin/oracle $ORACLE_HOME/bin/oracle_prepatch
> cd $ORACLE_HOME/rdbms/lib
> make -f ins_rdbms.mk ioracle
Oracle Application Server supports Internet Protocol multipathing and multiplexing (IPMP).
An IPMP group consists of one or more physical interfaces on the same system that are configured with the same IPMP group name. All interfaces in the IPMP group must be connected to the same IP link. The same (non-null) character string IPMP group name identifies all interfaces in the group.
You can place interfaces from NICs of different speeds within the same IPMP group, as long as the NICs are of the same type. For example, you can configure the interfaces of 100-megabit Ethernet NICs and the interfaces of one gigabit Ethernet NICs in the same group.
As another example, suppose you have two 100-megabit Ethernet NICs. You can configure one of the interfaces down to 10 megabits and still place the two interfaces into the same IPMP group.
You cannot place two interfaces of different media types into an IPMP group. For example, you cannot place an ATM interface in the same group as an Ethernet interface.
More information about IPMP is available at:
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.
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.
During installation of Oracle Application Server Problem, you may see an error message similar to the following:
0 files secured on terminal window from where OUI is invoked
This error message is benign and can be ignored.
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 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.
ORACLE_HOME Before Running root.sh ScriptBe sure to set the environment variable ORACLE_HOME before running the root.sh script during installation of Oracle Application Server.
Alternatively, you can add the following in the second line of the root.sh script, prior to running the script:
ORACLE_HOME=/private1/iasinst/OraHome1; export ORACLE_HOME
In the example, the ORACLE_HOME is located in the private1/iasinst/OraHome1 directory.
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.
During the installation of Oracle Application Server on Solaris x86 (32bit/64bit) with Japanese locale (LANG=ja), the Japanese content of some the Oracle Universal Installer help screens are displayed as square boxes.
When running the Oracle Universal Installer to install Oracle Application Server using the Turkish locale, the Configuration Assistant page will not display properly.
The Solaris Integration 10.1.2.0.2 installer incorrectly reports that Solaris 5.10 is not supported with the following error message:
Checking operating system version: must be 5.8 or 5.9. Actual 5.10
To resolve this problem, follow these steps:
Copy oraparam.ini from your CD to a working directory. It is located in install/oraparam.ini.
Modify the following line in oraparam.ini:
Change:
Solaris=5.8,5.9
To:
Solaris=5.8,5.9,5.10
When you run the installer, use the paramFile parameter to specify the edited copy of oraparam.ini. For example:
./runInstaller -paramFile <working_dir>/oraparam.ini
Alternatively, you can obtain an updated oraparam.ini file by downloading patch 5144427 from OracleMetaLink:
When running root.sh during installation, the following errors may appear:
chmod: WARNING: <ORACLE_HOME>/bin/emtgtctl2: Corresponding set-ID alsodisabled on file since set-ID requires execute permission chmod: WARNING: <ORACLE_HOME>/bin/extjob: Corresponding set-ID also disabledon file since set-ID requires execute permission chmod: WARNING: <ORACLE_HOME>/bin/oracle: Corresponding set-ID also disabledon file since set-ID requires execute permission
These error messages are harmless and can be ignored.
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 |
36 MB |
512 MB |
|
Oracle Application Server TopLink |
239 MB |
192 MB |
|
Oracle Sensor Edge Server |
175 MB |
512 MB |
|
Oracle HTTP Server with Apache 1.3 |
1.04 GB |
512 MB |
|
Oracle HTTP Server with Apache 2.0 |
961 MB |
512 MB |
|
OracleAS Web Cache |
846 MB |
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).
The section describes documentation errata in installation and upgrade documentation. It includes the following topics:
Section 2.3.1, "Additional Information About Changing the SYS Password"
Section 2.3.4, "Additional Steps for OracleAS Single Sign-On HA Configuration"
Section 2.3.5, "Incorrect File Extensions in Installed Documentation"
Section 2.3.6, "Incorrect Version Number on Forms and Reports CD-ROM"
Section 2.3.8, "Incorrect Media Reference in Oracle Application Server Installation Guide"
Section 2.3.9, "Invalid Instruction to Apply Database Patch"
Section 2.3.10, "Oracle Developer Suite 10.1.2.0.2 Is Not Available with This Release"
Section 2.3.11, "Incorrect OID Port for Silent Installations"
Section 2.3.13, "Incorrect Environmental Variable Recommendation"
Section 2.3.18, "OracleAS Cluster (Identity Management) Installed Language"
Section 2.3.20, "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 23, "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
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 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.
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.
Section 3.6, "Operating System Groups" of Oracle Application Server Forms and Reports Services Installation Guide does not include the file location to check the installation status of the inventory directory.
The missing file location is /etc/oraInst.loc.
Section 4.10.2 of the Oracle Application Server Installation Guide, Hostname for OracleAS Single Sign-On, currently states the following:
"If you are installing OracleAS Single Sign-On, and your hosts file contains only the hostname of your computer, without the domain name, then you will only be able to sign on to the Single Sign-On server using the hostname by itself (without the domain name)."
"If you want to require a domain name when connecting to the Single Sign-On server, you can edit the hosts file to include the domain name. If you do not want to edit the file, you can use the OUI_HOSTNAME command-line parameter to the installer to override the value in hosts. For example:"
"prompt> mount_point/1012disk1/runInstaller OUI_HOSTNAME=myserver.mydomain.com"
The last sentence in the second paragraph is incorrect. You must edit the /etc/hosts file before running the installer in order for SSO to work properly.
If you have already done the install and encounter the problem, use the Change Hostname procedure described in the Oracle Application Server Administrator's Guide to correct the problem.
