|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux PA-RISC (64-bit) B15511-05 |
|
 Previous |
 Next |
|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux PA-RISC (64-bit) B15511-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.1, "LDAP Replication Using SSL Mode is not Supported"
Section 2.1.2, "Harmless Message in the oraInstall.err Log File"
Section 2.1.4, "The lsnodes Command Fails on Non-RAC HP-UX Systems"
Section 2.1.6, "Warning Message from Oracle Universal Installer"
Section 2.1.7, "Deconfiguration Script Does Not Remove Entries from OracleAS Metadata Repository"
LDAP replication using SSL Mode is not supported when you select the "Use SSL communications to this Internet Directory" option during Oracle Internet Directory replication installation.
If you want to perform LDAP replication using SSL Mode, the workaround is to perform your installation in non-SSL mode first. Then change the Oracle Internet Directory instances to operate in SSL mode using the steps described in the Oracle Application Server 10g Administrator's Guide.
The following error appears in the oraInstall.err log file after certain installations:
java.io.FileNotFoundException: /net/stnfs3/vol/shiphomes/solaris/dailyShiphomes/iashybrid/10.1.2/daily/041221.0020/Disk1/stage/Patches/oracle.rdbms.dbscripts/10.1.0.3.1/1/DataFiles/sql.jar
This error can be safely ignored.
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.
After completing the installation, the install*.err files in the oraInventory/logs directory may contain errors similar to following line and with java exception stack details:
lsnodes: cannot get local node number
This error is harmless and can be safely ignored. It does not affect any functionality.Similar errors may also happen when applying bug fixes using the OPatch utility. However, the patch succeeds and the error can be safely ignored.
In Oracle Application Server Clusters (Identity Management) installations, the installer creates a DCM cluster for the Oracle Internet Directory, OracleAS Single Sign-On, and Oracle Delegated Administration Services components.
As part of the cluster creation operation, which is performed by the OracleAS Cluster Assistant, the assistant also restarts the components. DCM invokes OPMN to restart the components.
Because Oracle Internet Directory is integrated with OPMN, OPMN starts up and monitors oidmon. In turn, oidmon starts up Oracle Internet Directory. However, OPMN returns as soon as oidmon is up; it does not wait for Oracle Internet Directory to start up. This causes a problem because the next configuration assistant, the OC4J Configuration Assistant, requires Oracle Internet Directory to be up and running. If Oracle Internet Directory is still not running, the OC4J Configuration Assistant fails.The workaround is to ensure that Oracle Internet Directory is successfully restarted, then rerun the OC4J Configuration Assistant.
You may receive the following warning message when running Oracle Universal Installer:
Warning : Some Patch Bundles were not found on the system. Please ensure that either June 2003 Quality Pack GoldQPK11i has been installed or verify that the system is at a higher bundle level.
You can ignore this warning.
If you try to deconfigure an Identity Management instance using the deconfiguration script you will not be able to remove entries from the OracleAS Metadata Repository. This occurs when the Identity Management instance is connected to an OracleAS Metadata Repository that has been loaded by OracleAS RepCA, The OracleAS Metadata Repository cannot be reused until the following SQL queries are manually run to remove the entries:
SQL> execute dbms_ias_version.set_component_loading(component_id=>'MRC', component_name=>'Oracle Application Server Metadata Repository Version', schema_name=>'SYS')
SQL> execute dbms_ias_version.set_component_loaded(component_id=>'MRC')
SQL> execute dbms_ias_version.set_component_valid(component_id=>'MRC')
When you run the bulkload.sh utility to create Oracle Internet Directory entries from data residing in or created by other applications, you may observe the following error message:
"SQL*Loader-951: Error calling once/load initialization ORA-39778: the parallel load option is not allowed when loading lob columns".
This issue is caused by bug 3931084. Obtain and apply the patch for bug 3931084 to your Oracle Application Server installation. You can download the patch from OracleMetalink (http://metalink.oracle.com).
The following are known configurations when the patch for bug 3931084 should be applied before running the bulkloa.sh utility:
Oracle Application Server 10g Release 2 (10.1.2) with Oracle9i Database Enterprise Edition 9.2.0.X
Oracle Application Server 10g Release 2 (10.1.2) with Oracle Database 10g Enterprise Edition 10.1.0.4
This section describes issues with the upgrade of Oracle Application Server. It includes the following topics:
Section 2.2.1, "Problems Upgrading Oracle HTTP Server on HP-UX"
Section 2.2.3, "Remaining OracleAS Infrastructure Instance in Farm"
Section 2.2.4, "Failure of File-Based Farm Repository Configuration Assistant"
Section 2.2.7, "Problems or Issues While Upgrading Specific Components"
Section 2.2.8, "Upgrading a Portal and Wireless Installation from 9.0.2.3 to 10.1.2 on HP-UX."
The following message might be displayed if you are upgrading a middle-tier installation:
FastCGI: failed to connect to (dynamic) server "/opt/oracle/inst/Apache/Apache/fcgi-bin/echo": path "/opt/oracle/inst/Apache/Apache/logs/fastcgi/dymanic/aac1cec5416b961cf002c5526b4159" is too long for a Domain socket
On HP-UX, the path for sockets used by FastCGI is limited to 108 characters. If the message is displayed, use the FastCgiIpcDir directive to specify a path name that is significantly shorter than 108 characters, such as /tmp as follows:
Edit the http.conf file for the Oracle HTTP Server that you are trying to upgrade and set the FastCgiIpcDir directive to a short path such as /tmp.
Run the following command:
dcmctl updateConfig -ct ohs
Restart the Oracle HTTP Server.
Restart the Upgrade process.
After you perform an upgrade of Oracle Application Server 10g from version 9.0.4 to version 10.1.2, the Oracle Enterprise Manager login link on the welcome page no longer works. During installation, the port number specified for Oracle Enterprise Manager for version 9.0.4 installation is not updated in the version 10.1.2 welcome pages. There is no workaround for this issue at this time.
After you complete an upgrade of OracleAS Infrastructure in a farm, the pre-upgrade instance of the infrastructure still remains in the farm. There is currently no way to remove the pre-upgrade instance. The remaining instance will not cause any operational problems with the upgraded infrastructure.
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 are upgrading a Release 2 (9.0.2) OracleAS Metadata Repository and you are using OracleAS Portal, then you must apply an OracleAS Portal patch before upgrading the OracleAS Metadata Repository.
|
See Also: Section 6.3.1.1, "Downloading and Installing the OracleAS Portal 10g (9.0.4) Repository Upgrade Software" in the Oracle Application Server 10g Upgrading to 10g (9.0.4) |
However, while using Oracle Universal Installer to install the required patch, Oracle Universal Installer may quit unexpectedly. To prevent this problem from occurring, do the following:
Use a text editor to open the oraparam.ini file, which is located in the following directory in the application server Oracle home:
ORACLE_HOME/oui
Locate the following entry in the oraparam.ini file:
JRE_MEMORY_OPTIONS=" -mx96m"
Modify the entry as follows:
JRE_MEMORY_OPTIONS=" -mx160m"
Save your changes and close the oraparam.ini file.
Restart Oracle Universal Installer and install the patch as documented in the Oracle Application Server 10g Upgrading to 10g (9.0.4).
When you are upgrading Identity Management in an environment where you are using Oracle Internet Directory partial replication, you may encounter a problem while running the upgrade with Oracle Universal Installer: the mod_osso Configuration Assistant may fail.
If this problem occurs, do not quit 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
Modify the contents of the file so it reads as follows:
DCMRESYNC=oracle.ias.configtool.configimpl.DcmResync$0 JAZN=oracle.security.jazn.util.JAZNConfigTool$0 HTTPD=oracle.ias.configtool.configimpl.HttpdSsoConfig$0 MODOSSO=oracle.ias.configtool.configimpl.SsoConfig$0
Save your changes and close the infratool_mod_osso.properties file.
Return to Oracle Universal Installer and try running the configuration assistant again.
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, refer to Chapter 9, "Oracle Ultra Search" for information about issues you may encounter when upgrading Oracle Ultra Search. Refer to Chapter 8, " Oracle Application Server Portal" for information about issues you may encounter while upgrading OracleAS Portal.
After upgrading a Portal and Wireless installation from 9.0.2.3 to 10.1.2, Oracle HTTP Server may fail to start and the following messages may be displayed:
OpenWallet failed with error 28759 [Tue Jan 11 20:39:27 2005] [error] mod_ossl: Failed to open the wallet [Hint: incorrect path, incorrect password, bad wallet, ...]
This issue is due to the loading sequence of mod_ossl and php4. To avoid this problem make sure that the php4_module is loaded before the ossl_module:
Open the $ORACLE_HOME/Apache/Apache/conf/httpd.conf file in a text editor.
Search for the following text, which loads ossl_module.:
<IfDefine SSL>
LoadModule ossl_module libexec/mod_ossl.so
</IfDefine>
Add the following line before the ossl_module load entry:
LoadModule php4_module libexec/libphp4.so
Remove any other line that loads php4_module.
Start the Oracle HTTP Server.
This section describes documentation errata. It includes the following topic:
The Safari browser is not supported in this release of Oracle Application Server 10g.
This is stated incorrectly in the Oracle Application Server 10g Installation Guide.
Table 12-5 "Steps for Installing OracleAS Cluster (Identity Management) on Subsequent Nodes" of the Oracle Application Server 10g Installation Guide does not contain an entry for the Specify LDAP Virtual Hosts and Ports screen. This screen appears before the Specify OID Login screen prompting you to enter the hostname and port for LDAP virtual hosts.
Section 4.2.1 of the Installation Guide asks you to use the following command:
# /usr/sbin/swlist | grep QPK
However, this command may not list patches that were release later than June 2003 Quality Pack GoldQPK11i. Use the following command to list system software:
# /usr/sbin/swlist -l bundle | grep -i gold
If the system meets the software requirement because a later version of a package is installed, the installer may report a warning. It is safe to ignore that warning.
The information about hardware requirements in Chapter 4 of the Installation Guide should mention that for Hostname, host names must not exceed 255 characters, and this is not checked by the installation software.
In the "Configuring Kernel Parameters on HP-UX" section of Chapter 4 of the Installation Guide, the recommended values for the nfile and nproc parameters are too low in the "Kernel Parameter Settings for OracleAS Metadata Repository" table. The recommended values for these parameters should be:
nfile: 65536
nproc: 4200
In addition to the required options listed in Table 8, "Required Database Options" in Section 1.5.9, "Database Options" in the Oracle Application Server Repository Creation Assistant User's Guide, you must also include Oracle XML DB. If you do not have all of the required options, OracleAS RepCA will not run properly.
