| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.2) for AIX Part Number B32414-05 |
|
|
View PDF |
| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.2) for AIX Part Number B32414-05 |
|
|
View PDF |
This chapter describes installation 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.1, "Response Files Created through the Record Mode Are Not Supported"
Section 2.1.5, "Set db_create_file_dest Before Installing Against a File System Database"
Section 2.1.6, "Java Virtual Machine Parameters for Installation"
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.
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.
If Oracle WebCenter Framework and Oracle Content DB are installed on the same machine, you may see a message in opmn.log that is similar to the following:
If your host contains an Oracle Application Server 10g (9.0.4) installation, you may have installed gcc-2.95 or gcc-2.96 on your system, as outlined in Oracle Application Server Quick Installation and Upgrade Guide 10g (9.0.4) for Linux x86. The procedure involved creating symbolic links for /usr/bin/gcc and /usr/bin/cc to the appropriate version of the executables.
06/06/07 06:22:52 [ons-connect] Passive connection 127.0.0.1,6100 missing connect
To check whether these links exist:
ls -l /usr/bin/gcc /usr/bin/cc
Check if the gcc and cc commands are symbolic links, for example:
gcc -> /opt/gcc295/bin/gcc cc -> /opt/gcc295/bin/gcc
This is due to a port conflict. To correct this problem, perform the following steps:
Open the DB_ORACLE_HOME/opmn/conf/ons.config file for editing.
Set the localport to a port other than 6100. For example:
localport=7100
Restart the database listener:
DB_ORACLE_HOME/bin/lsnrctl stop DB_ORACLE_HOME/bin/lsnrctl start
Restart the Oracle WebCenter Framework instance:
opmnctl stopall opmnctl startall
All installation types fail with the Turkish locale:
This is because Oracle WebCenter Framework Configuration Assistant fails with the following errors:
ERROR: 'Instruction unknown: load?nstruction' FATAL ERROR: 'Could not compile stylesheet
For all installation types, the component toolbox on the Configuration Assistants page of Oracle Universal Installer is not displayed properly for the Turkish locale.
Oracle recommends that you avoid running the Oracle Universal Installer to install Oracle Application Server using the Turkish locale.
If you are installing against a file system-based database, you must set the db_create_file_dest parameter to the location of the DB data files before starting the installation. For example:
SQL> ALTER SYSTEM SET db_create_file_dest='C:\oradata' SCOPE=BOTH
This is because Oracle WebCenter Framework Configuration Assistant fails with the following errors:
ERROR: 'Instruction unknown: load?nstruction' FATAL ERROR: 'Could not compile stylesheet
If you are installing against a raw database, this parameter must be null.
Note that the cdb_alter_system.sql script does not set this parameter. You must set it manually.
After installing Oracle Application Server, and then, Oracle Communication and Mobility Server, you must edit the following Java Virtual Machine (JVM) parameters in the $ORACLE_HOME/opmn/conf/opmn.xmlfile:
-Xgcpolicy:gencon -Xmos128m -Xmox128m -Xss128k -Xms1280M -Xmx1280M
-Xss128k -Xms1280m -Xmx1280m -Xmn16m -XX:SurvivorRatio=16 -XX:CICompilerCount=1 -Xoptgc -XX:+ForceMmapReserved -XX:-UseHighResolutionTimer -XX:SchedulerPriorityRange=SCHED_NOAGE -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.DevPollSelectorProvider -XX:-ExtraPollBeforeRead -XX:+UseTLAB -XX:TLABSize=32k -XX:-UseFastAccessorMethods -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=80 -XX:+UseParNewGC -XX:PermSize=128m -XX:MaxPermSize=128m
-XX:NewRatio=3 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:PermSize=128m -XX:MaxPermSize=128m -Xss128k -Xmx1280M -Xms1280M
The JVM parameters are used to activate the Oracle Communication and Mobility Server instance.
Note:
To perform standalone installation of Oracle Communication and Mobility Server, you need to run these parameters in the command-line interface along with the startup command.You must also upgrade Java Development Kit (JDK) to version 1.5.0_05 after installing Oracle Communication and Mobility Server. For more information on upgrading JDK, refer to 396096.1 note available on OracleMetaLink at:
The section describes documentation errata in installation documentation. It includes the following topics:
The following topic in the Application Server Control online help incorrectly states the valid length of the Content Database schema password when installing Oracle Application Server 10g Release 3 (10.1.3.2):
"Specify Content Database Schema Password"
The length of the Content Database schema password must be between 5 and 30 characters long.
The Oracle Application Server Installation Guide lists incorrect paths to files on the DVD-ROM. The DVD-ROM does not have a directory called application_server. Instead, it has the following top-level directories:
bpel
companioncd
esb
owsm
soa
Copying Files for Installation
If you want to copy the files from the DVD-ROM to a drive, you can copy each of the main directories listed above separately. You do not need to copy the entire DVD-ROM, unless you need to install all the products and components.
runInstaller Location
The runInstaller command is found in the following directories:
bpel/bpel_oc4j
companioncd/Disk1
esb/esb
owsm/owsm
soa
Use the one that corresponds to the product or component that you want to install.
Section 6.4.4, "OracleAS Cold Failover Cluster: Details of Installation Steps", in the Oracle Application Server Installation Guide 10g Release 3 (10.1.3.2.0) for all UNIX/Linux platforms contains the following statement:
"Set the VIRTUAL_HOST_NAME environment variable to the virtual hostname on either node of the hardware cluster."
For all UNIX/Linux platforms, the cloned instance will use the hostname of the machine, rather than the virtual hostname, even if you set the VIRTUAL_HOST_NAME environment variable during installation of the source instance and before performing the cloning operation.
Use the ORACLE_HOSTNAME environment variable and the OUI_HOSTNAME install option instead of the VIRTUAL_HOST_NAME environment variable to set the virtual hostname.
For Windows platforms, you can use the VIRTUAL_HOST_NAME environment variable for the virtual hostname installation.
|
 Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
