|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium B15849-03 |
|
 Previous |
 Next |
|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium B15849-03 |
|
|
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.6, "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 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 message 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.
In Oracle Application Server Cluster (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 running. If Oracle Internet Directory is still not running, the OC4J Configuration Assistant fails.The workaround is to insure that Oracle Internet Directory is successfully restarted, then rerun the OC4J Configuration Assistant.
On installations using simplified/traditional Chinese character sets, the Oracle Universal Installer prerequisite check result messages are not clear and garbled in the installActions.log file.
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 Metadata Repository Creation Assistant, 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
When you select to deinstall Oracle Application Server, immediately after confirming which Oracle Application Server components are to be deinstalled, the deinstallation process may hang on some computers that use ATI video cards.The issue is due to the use of the JRE and DirectDraw Acceleration Utility on Microsoft Windows systems with ATI video cards.To workaround this issue:
Disable the DirectDraw Acceleration utility.
Type the following on the MS-DOS command line:
> dxdiag
Reboot your computer.
Retry the deinstallation.
This section describes issues with the upgrade of Oracle Application Server. It includes the following topics:
Section 2.2.2, "Remaining OracleAS Infrastructure Instance in Farm"
Section 2.2.3, "Failure of File-Based Farm Repository Configuration Assistant"
Section 2.2.6, "Problems or Issues While Upgrading Specific Components"
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 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 Upgrade and Compatibility Guide |
While using Oracle Universal Installer to install the required patch, Oracle Universal Installer may stop 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 and close the oraparam.ini file.
Restart Oracle Universal Installer and install the patch as documented 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.
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
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 and close the infratool_mod_osso.properties file.
Return to Oracle Universal Installer and try to run the configuration assistant again.
This section describes documentation errata. It includes the following topic:
Section 2.1.1, "LDAP Replication Using SSL Mode is not Supported"
Section 2.3.3, "Host Name Limit of 255 Characters Not Checked"
In the Oracle Application Server Installation Guide, section 4.3.2, "Checking If a Port Is in Use", the command to find if a port in use is listed.
An additional command to find if a port is in use on the Microsoft Windows XP operating system is:
C: \> netstat -an | findstr "1814"
In the command above, port number is the port you want to find. If the port is not in use, the command returns no output.
The Safari browser is not supported in this release of Oracle Application Server 10g.
This is stated incorrectly in the "-01" versions of the Oracle Application Server Installation Guide (for example, part number B14088-01 for the Solaris platform) and has been corrected in later versions of the installation guides.
The information about system requirements in Chapter 4 of the Installation Guide should mention that for Hostname, the requirement that host names must not exceed 255 characters is not checked by the installation software.
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 Metadata Repository Creation Assistant User's Guide, you must also include Oracle XML DB. If you do not have all of the required options, OracleAS Metadata Repository Creation Assistant will not run properly.
