| Oracle® Application Server Release Notes 10g (10.1.4.0.1) for Solaris Operating System (x86) and Solaris Operating System (x86-64) Part Number B32092-01 |
|
|
View PDF |
| Oracle® Application Server Release Notes 10g (10.1.4.0.1) for Solaris Operating System (x86) and Solaris Operating System (x86-64) Part Number B32092-01 |
|
|
View PDF |
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, "Unique Global Database Name Required During Installation"
Section 2.1.2, "Do Not Use Turkish Locale During Installation"
Section 2.1.5, "Oracle Internet Directory SSL Connection Fail Intermittently"
Section 2.1.7, "Illegible or Garbage Characters Output in a Russian Locale"
Section 2.1.10, "Excessive Privileges for OracleAS Metadata Repository Installations"
During installation of either of the install types, Oracle Identity Management and OracleAS Metadata Repository, or OracleAS Metadata Repository, you must enter a unique Global Database Name on the Specify Database Information screen.
If there are 2 databases present on the same host, then each database should have a unique SID and Global Database Name.
Currently, the Oracle Universal Installer only checks if a unique SID is entered by user; it does not check if a Global Database Name is entered by the user. Both the SID and Global Database Name values are entered on the Specify Database Information screen. The installation proceeds with a potential Oracle Internet Directory Configuration Assistant failure. You may see an error message such as the following:
"The Network Adapter could not establish the connection"
Oracle recommends that you avoid running the Oracle Universal Installer to install Oracle Application Server using the Turkish locale because some of the installation screens will not be displayed properly and will not be usable.
During loading of OracleAS Metadata Repository into an existing database, OracleAS RepCA fails if the database uses the ZHT16MSWIN950, ZHT16HKSCS, or ZHT16HKSCS31 character set.
To check the character set of your database, query the NLS_DATABASE_PARAMETERS view:
prompt> sqlplus "sys/password as sysdba" SQL> select VALUE from NLS_DATABASE_PARAMETERS where PARAMETER='NLS_CHARACTERSET';
where password specifies the password for the SYS user.
Additional configuration steps are required to configure Oracle Delegated Administration Services to work with an OracleAS Cold Failover Cluster.
Open the ORACLE_HOME/sysman/emd/targets.xml file and locate the oracle_das_server target and the HTTPMachine, DasURL, and DASMonitorURL properties:
<Target TYPE="oracle_das_server" NAME="instance.domain.com_DAS" DISPLAY_NAME="instance.domain.com_DAS"> <Property NAME="HTTPMachine" VALUE="LocalHost"/> ... <Property NAME="DasURL" VALUE="http://LocalHost:7777/oiddas"/> <Property NAME="DasMonitorURL" VALUE="http://LocalHost:7777/oiddas/dasmetrics"/> ... </Target>
Change the HTTPMachine, DasURL, and DASMonitorURL property values to the virtual Apache host:
<Target TYPE="oracle_das_server" NAME="instance.domain.com_DAS" DISPLAY_NAME="instance.domain.com_DAS"> <Property NAME="HTTPMachine" VALUE="VirtualApacheHost"/> ... <Property NAME="DasURL" VALUE="http://VirtualApacheHost:7777/oiddas"/> <Property NAME="DasMonitorURL" VALUE="http://VirtualApacheHost:7777/oiddas/dasmetrics"/> ... </Target>
The Oracle Internet Directory SSL connection may fail intermittently during an Oracle Application Server installation. Specifically, this failure may occur during an Identity Management and High Availability collocated installation.
To workaround this issue, retry the failed configuration assistant from the installation.
If you encounter Oracle Internet Directory SSL connection failure, the log file (ORACLE_HOME/sso/log/ssoca.log) contains the message of connection failure to LDAP URL, but the correct debug message is ldaps url.
When you install Oracle Application Server in Russian locale and some of the configuration assistants fail, you may receive exception message output to Oracle Universal Installer which contain illegible or garbage characters.
If you encounter this type of error message, you can safely ignore the message and continue with the installation and rerun the configuration assistants.
In some non-English locale Oracle Application Server installations the Oracle Enterprise Manager 10g Application Server Control Console (Application Server Control Console) hyperlink is not operational on the Welcome page. If the hyperlink is not working in your installation, do the following:
Open the ORACLE_HOME/Apache/Apache/htdocs/index.html file.
Locate the line <a href="http://%s_hostName%:%s_oemConsolePort%" > in the index.html file.
Replace %s_hostName% with your local hostname.
Replace %s_oemConsolePort% with the value of the Application Server Control Console port from the ORACLE_HOME/install/portlist.ini file,
If you set the following NLS parameters before installation of Oracle Identity Federation through Oracle Application Server:
LANG=zh_CN.GB18030 LC_ALL=zh_CN.GB18030
and then check the ORACLE_HOME/dv/OraHome/inventory/Contents/comp.xml file at line 172 you will see the following:
<DEP NAME="oracle.iappserver.charts"VER="10.1.2.0.0" DEP_GRP_NAME="group2" HOME_IDX="5"/> Column 43 refers to the beginning of attribute VER, just after the XML attribute value of parameter NAME. A whitespace between the double quote and the parameter name is missing.
If you then install an additional Oracle Identity Federation instance on the same computer, you will receive an error message during the installation.
To workaround this problem, set the NLS parameter as follows:
LANG=zh_CN.GBK LC_ALL=zh_CN.GBK
In Oracle Application Server 10g (10.1.4.0.1), the Java Developer Kit does not support GB18030 encoding.
This topic is applicable to installations of OracleAS Metadata Repository created with the Oracle Application Server Repository Creation Assistant or installed as part of an OracleAS Infrastructure installation.
The EXECUTE privilege is given to PUBLIC for the following packages:
UTL_FILE
DBMS_RANDOM
UTL_HTTP
UTL_SMTP
UTL_TCP
These privileges may be excessive, and not necessary for your enterprise.
Oracle recommends that you complete the following steps to determine if the EXECUTE privilege has been applied correctly in your enterprise:
Analyze your application and determine which account / applications require the above packages. If any accounts do require these privileges they will typically be accounts which own applications such as HR or CRM type applications.
Grant execute on the corresponding package to the account / application identified in Step 1. If you were not able to complete the analysis in Step 1, you can optionally grant execute on these packages to the existing application type accounts.
Revoke the EXECUTE privilege for the above packages from the group PUBLIC and verify your application continues to work properly. Completing this step will ensure that new accounts created in the future will not have execute on these packages by default.
The online help for the Specify Database Configuration Options screen lists the following two guidelines for specifying the global database name:
The following characters are valid in the database domain: alphanumeric characters, the underscore (_) character, the minus (-) character, and the pound sign (#) character.
The database name can contain only alphanumeric characters (A-Z and 0-9).
These guidelines are incorrect and should be replaced with the following guideline:
The following characters are valid in the database domain and domain name: alphanumeric characters, the underscore (_) character, and the pound sign (#) character.
This section describes issues with upgrade of Oracle Application Server. It includes the following topics:
Section 2.2.1, "Upgrade of Identity Management Installation to 10.1.4.0.1"
Section 2.2.4, "Harmless Error Messages During OracleAS Metadata Repository Upgrade"
If you have the following upgrade:
Upgrade your Identity Management installation to 10.1.4.0.1
Install Oracle Enterprise Manager 10g Grid Control Plug-in and Oracle Identity Management Grid Control Plug-in Agent
Each Identity Management component will display two targets in Oracle Enterprise Manager Grid Control. One target is for the pre-upgrade Identity Management installation, and the other is for the upgraded Identity Management installation.
This is expected behavior because the pre-upgrade Oracle home is still registered with oraInventory. The Oracle Enterprise Manager Grid Control Plug-in Agent discovers all of the Oracle homes on a host and collects information from the respective targets.xml files.
To avoid this problem:
Upgrade your Identity Management installation to 10.1.4.0.1.
Install Oracle Enterprise Manager 10g Grid Control Agent and Oracle Identity Management Grid Control Plug-in Agent.
Remove the pre-upgrade Oracle Application Server Single Sign-On and Oracle Internet Directory targets as follows:
Open the Oracle Enterprise Manager Grid Control.
Select and click Targets.
Select and click All Targets
For each pre-upgrade Oracle Application Server Single Sign-On and Oracle Internet Directory target:
- Select the target instance
- Click Remove
For the Oracle Enterprise Manager 10g Grid Control Agent to collect proper monitoring data, you will need to reset the password of the database user dbsnmp of the upgraded Identity Management installation.
To reset the database user password, run the following command (sqlplus "/as sysdba") from the Identity Management database ORACLE_HOME:
> alter user dbsnmp identified by "/dbsnmp_passwd/"; > commit;
If you have applied Oracle Application Server 10g (9.0.4) Patchset 3 (9.0.4.3) to your release 9.0.4 instance, and now want to upgrade the OracleAS Metadata Repository to release 10.1.4.0.1 by running 10.1.4.0.1 MRUA, you must first apply patch 5365207 to your 10.1.4.0.1 MRUA. For this, you must copy the contents of the 10.1.4.0.1 MRUA and Utilities CD–ROM to a location where you have write permission. Then apply patch 5365207 on your 10.1.4.0.1 MRUA staged directory. You can find this patch on Oracle Metalink at
Use the patched version of 10.1.4.0.1 MRUA to upgrade a release 9.0.4.3 instance to release 10.1.4.0.1. For details about running MRUA, refer to the Oracle Application Server Upgrade and Compatibility Guide.
If you do not apply patch 5365207, then the portal component upgrade will fail with the following error when running 10.1.4.0.1 MRUA:
Calling upgrade plugin for PORTAL Error: Component upgrade failed PORTAL Error: PORTAL component version is: 9.0.4.3.0 INVALID
This error message is displayed on screen and is also recorded in the MRUA log file, ORACLE_HOME\upgrade\logs\mrua.log. For the detailed error message, review the portal upgrade precheck log file, ORACLE_HOME\upgrade\temp\portal\precheck.log. Refer to the Oracle Application Server Upgrade and Compatibility Guide for further information on reviewing the upgrade log files.
The detailed error message from the precheck.log file reads as follows:
### Install Schema Validation Utility
>>> Running upg/common/prechk/svuver.sql .
Portal SQL script started at Thu Jun 1 08:55:22 2006
Connected.
# Beginning outer script: common/prechk/svuver
# Portal Schema Version = 9.0.4.3.0
# Version of schema validation utility being installed =
Connected.
###
### ERROR: Exception Executing upg/common/prechk/svuver.sql
###
### Check Failed at Thu Jun 1 08:55:24 2006 Continuing as PreCheck mode is
specified
### Invoke Schema Validation Utility in Report Mode
>>> Running upg/common/prechk/../svurun.sql .
Portal SQL script started at Thu Jun 1 08:55:24 2006
Connected.
# Beginning outer script: common/prechk/svurun
#-- Beginning inner script: common/common/svurun
l_mode := wwutl_schema_validation.MODE_REPORT;
*
ERROR at line 5:
ORA-06550: line 5, column 19:
PLS-00201: identifier 'WWUTL_SCHEMA_VALIDATION.MODE_REPORT' must be declared
ORA-06550: line 5, column 9:
PL/SQL: Statement ignored
ORA-06550: line 8, column 19:
PLS-00201: identifier 'WWUTL_SCHEMA_VALIDATION.MODE_CLEANUP' must be declared
ORA-06550: line 8, column 9:
PL/SQL: Statement ignored
ORA-06550: line 15, column 5:
PLS-00201: identifier 'WWUTL_SCHEMA_VALIDATION.VALIDATE_ALL' must be declared
ORA-06550: line 15, column 5:
PL/SQL: Statement ignored
Connected.
###
### ERROR: Exception Executing upg/common/prechk/../svurun.sql REPORT
###
### Check Failed at Thu Jun 1 08:55:25 2006 Continuing as PreCheck mode is
specified
|
Note: In the case where you have already encountered this error, apply patch 5365207 and rerun the upgrade. There is no need to restore the OracleAS Metadata Repository from backup before rerunning the upgrade. This is because the upgrade failed during the precheck phase and the portal schema in the OracleAS Metadata Repository has not been altered in the precheck phase. |
If the portal upgrade fails in the precheck phase even after applying patch 5365207, then review the precheck log file for details about the new error. Based on the description of the error, resolve the problem and perform the upgrade again, or contact Oracle Support Services for help.
The procedure for upgrading to 10g (10.1.4.0.1) Oracle Application Server Cluster (Identity Management) (OracleAS Cluster (Identity Management)) is documented in Appendix B of the Oracle Application Server Upgrade and Compatibility Guide. However, if you are upgrading this type of environment, there is an additional task you must perform if all of the following is true:
You are upgrading an OracleAS Cluster (Identity Management) environment to 10g (10.1.4.0.1).
Your load balancer and Oracle Internet Directory are using different ports.
Your Oracle Internet Directory ports are set to a value less than 1024 and your load balancer ports are set to a value higher than 1024.
In this specific scenario, perform the following steps when you are prompted by Oracle Universal Installer to run the root.sh script:
Use a text editor to open the root.sh file in the Oracle home of the Identity Management instance you are upgrading.
Edit the following two entries in the root.sh file so they point to the SSL and non-SSL port of the Oracle Internet Directory.
For example:
SSLPORT=636 NONSSLPORT=389
Make sure these entries do not point to the load balancer ports.
Save and close the root.sh file.
Run the root.sh file as the root user, as directed by the Oracle Universal Installer instructions.
If you do not perform these steps during the upgrade procedure, the Oracle Internet Directory configuration assistant will fail during the configuration phase of the upgrade procedure.
To fix this problem after the Oracle Internet Directory configuration assistant fails:
Leave Oracle Universal Installer running (with the configuration screen displayed) and open a new terminal window.
From the new terminal window, execute the following commands as the root user in the destination Oracle home:
chown root <DESTINATION_ORACLE_HOME>/bin/oidldapd chmod 4710 <DESTINATION_ORACLE_HOME>/bin/oidldapd
Return to the Oracle Universal Installer window and retry the Oracle Internet Directory configuration assistant.
When you upgrade your OracleAS Metadata Repository ORACLE_HOME to 10g (10.1.4.0.1) you may see the following message in the installActions.log file, or the XTERM terminal or DOS command shell window if you are performing a non-interactive installation:
getXMLUserManager:Exception /ORACLE_HOME/in1014MR/sysman/j2ee/config/jazn-data.xml (No such file or directory) getRealmUser: XMLUserManager is null getXMLUserManager:Exception /ORACLE_HOME/in1014MR/sysman/j2ee/config/jazn-data.xml (No such file or directory)
There is no adverse effects to the installed OracleAS Metadata Repository. The observed messages are only debug messages.
You can ignore the observed messages, there is no adverse effect to the upgrade process.
The Metadata Repository Container (MRC) version in app_registry is 10g (10.1.2.0.2).
There were no schema changes to any OracleAS Metadata Repository components in the 10g (10.1.4.0.1) release. Upgrades from the 10g (10.1.4.0.1) release to the OracleAS Portal (10.1.4.0.0) release is therefore supported.
This section describes issues with Oracle Application Server documentation. It includes the following topics:
Example 8-1, "Sample Output from an MRUA Session" in the Oracle Application Server Upgrade and Compatibility Guide, shows the output from a typical session with the Metadata Repository Upgrade Assistant. However, in the HTML version of the guide, the line breaks are shown incorrectly. The following lines in the sample output should appear as follows:
Upgrading the OracleAS Metadata Repository to release 10.1.4.0.1. Calling upgrade plugin for MRUA Component upgraded successfully MRUA
In Table 4-14, "Database Screens", in the Specify Database Identification screen description in the Oracle Application Server Installation Guide, the section incorrectly states that the database name portion of the global database name must contain alphanumeric characters only. This is incorrect. The database name can contain alphanumeric, underscore (_), and pound (#) characters.
