|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Solaris Operating System (SPARC) B25991-01 |
|
 Previous |
 Next |
|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Solaris Operating System (SPARC) B25991-01 |
|
|
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 3.1.1, "Additional Steps for Installation on the Solaris10 Operating System"
Section 3.1.2, "LDAP Replication Using SSL Mode is not Supported"
Section 3.1.3, "Harmless Message in the oraInstall.err Log File"
Section 3.1.6, "Deconfiguration Script Does Not Remove Entries from OracleAS Metadata Repository"
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 10g Installation Guide, and the Oracle Application Server 10g Upgrading to 10g (9.0.4).
Oracle Application Server has been certified to work in Solaris10 non-global (local) and global containers.
This section contains the following topics:
Section 3.1.1.3, "/etc/system Requirements for Installation"
Section 3.1.1.5, "Database Configuration Assistant Patch Installation"
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 10g 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 10g 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 Oracle Application Server on the Solaris 10 operating system, you must install patches 4510761 and 4025481. These 2 patches are available from Oracle MetaLink (http://www.metalink.oracle.com). The following steps describe how to install the patches:
Prior to installation of Oracle Application Server, download and unzip patches 4510761 and 4025481 onto your system.
Patch 4510761 will be used when you invoke the Oracle Universal Installer to install Oracle Application Server
Patch 4025481 will be used later in the installation process prior to configuration as the root user.
Invoke Oracle Universal Installer with the -paramFile option pointing to the oraparam.ini file that was downloaded with patch 4510761.
Run the command as following to start up the Oracle Universal Installer:
> CDROMMountPoint/Disk1/runInstaller –paramFile <4510761_Patch_location>/oraparam.ini.
For example:
> CDROMMountPoint/Disk1/runInstaller –paramFile /tmp/patch4510761/oraparam.ini
During the installation of Oracle Application Server, the Oracle Universal Installer will prompt you to run the root.sh script in a separate window. The message will state or be similar to the following:
"Alert: A configuration script needs to be run as root before installation can proceed. Leaving this window open, open another window and run '/home/oracle/ias/root.sh' as root, then return to this window and click OK to continue."
Before running the root.sh configuration script, apply patch 4025481 for Oracle HTTP Server.
Run the root.sh configuration script as the root user.
Finish the installation of Oracle Application Server.
If you are installing the OracleAS Infrastructure 10g, and encounter failure during the running of the Database Configuration Assistant, you must apply patch 4606056. 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 4606056 patch. 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>/4606056/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
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 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 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 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.
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 can not 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 3.2.2, "Remaining OracleAS Infrastructure Instance in Farm"
Section 3.2.3, "Failure of File-Based Farm Repository Configuration Assistant"
Section 3.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 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 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 10g Upgrading to 10g (9.0.4) |
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 10g Upgrading to 10g (9.0.4).
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.
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".
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 "-01" versions of the Oracle Application Server 10g Installation Guide (for example, part number B14088-01 for the Solaris platform) and has been corrected in later versions of the installation guides.
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.
