Oracle® Fusion Middleware Release Notes 11g Release 1 (11.1.1) for Linux x86-64 E14770-11 |
|
![]() Previous |
![]() Next |
This chapter describes issues associated with Oracle Fusion Middleware installation and configuration. It includes the following topics:
This section describes installation issue and workarounds. It includes the following topics:
Section 2.1.1, "Installing Oracle SOA Suite on a Dual Stack Host with IPv4"
Section 2.1.2, "Installing Oracle Web Tier 32-bit on a 64-bit Linux Operating System"
Section 2.1.6, "Problems Installing in Thai and Turkish Locales"
Section 2.1.8, "Setting the nls_length_semantics Parameter in your Database"
Section 2.1.9, "Proper Deinstallation for Reinstallation in the Event of a Failed Installation"
Section 2.1.10, "Running irca.sh or irca.bat Against an Oracle 10g Database"
Section 2.1.11, "Installing the SOAINFRA Schema with DBA Permissions"
Section 2.1.12, "Deinstallation Does Not Remove WebLogic Domains"
Section 2.1.14, "Response File is Missing the MIDDLEWARE_HOME Entry"
If you install Oracle SOA Suite on a dual stack host and the SOA front end URL is only set to IPv4, Oracle BPM Worklist or asynchronous callbacks from IPv6-only clients may have problems resolving IPv4 callback URLs (and vice-versa).
The work around is to use either a split Domain Name System (DNS) or another forward proxy configuration. This enables the IPv6-only client to connect to a dual stack box through its IPv6 interface.
The following note exists in the Oracle Fusion Middleware Installation Guide for Oracle Web Tier and Oracle Fusion Middleware Quick Installation Guide for Oracle Web Tier:
Note: If you are installing the 32-bit version of the product, the system on which you are installing must also be a supported 32-bit system. Installing a 32-bit version of the product on a 64-bit system is not supported. |
A 32-bit Linux version of Oracle Web Tier may be installed on a 64-bit Linux platform by doing the following:
Run the following command before starting the installer:
linux32 bash
During the installation, you will receive an error during the linking phase. To work around this error:
Login as root
user.
Move the existing /usr/bin/gcc
file to /usr/bin/gcc.orig
with the mv
command:
mv /usr/bin/gcc /usr/bin/gcc.orig
Using a text editor such as vi, create a new file called gcc41
that contains the following conent:
#!/bin/sh exec /usr/bin/gcc.orig -m32 -static-libgcc -B/usr/lib/gcc/i586-suse-linux/2.95.3/ $*
Note: The filei586-suse-linux/2.95.3 may differ slightly depending on the exact version of your Linux operating system. Verify the exact version of your Linux operating system in use; search for the 32bit directory in /usr/lib/gcc and obtain the exact file name. |
Change the file permission for the gcc41
file using the following command:
chmod 755 /usr/bin/gcc41
Create a symbolic link to /usr/bin/gcc
with the following command:
ln -s -f /usr/bin/gcc41 /usr/bin/gcc
Vendor release updates cummulative patches and/or packages that may superseed our listed Oracle Fusion Middleware 11g Release 1 prerequisites for platforms. As long as vendor approved patches and/or packages are installed, the prerequisite warnings could be ignored and the installation completed.
Another option is to use -ignoreSysPreReqs
command line additional argument to the runInstaller
as:
$Mount_Point
/runInstaller -ignoreSysPreReqs
other required install options
After extending an Oracle Identity Management domain, you may see exception messages related to JRF Startup Class in the managed server log files. For example:
Failed to invoke startup class "JRF Startup Class", oracle.jrf.PortabilityLayerException: Fail to retrieve the property for the Common Components Home. oracle.jrf.PortabilityLayerException: Fail to retrieve the property for the Common Components Home.
You can safely ignore these exception messages—there is no loss in functionality.
When you install Oracle Identity Management, you have several options for choosing how the Oracle Identity Management components are installed in relation to an Oracle WebLogic Server administration domain. If you select the Extend Existing Domain option on the installer's Select Domain screen, Oracle Identity Management components are installed in an existing Oracle WebLogic Server administration domain.
To install Oracle Identity Management components in an existing administration domain using the Extend Existing Domain option, the Oracle WebLogic Administration Server instance must be running.
Turkish and Thai users are recommended to install and run Oracle Fusion Middleware using the English locale. Oracle Fusion Middleware does support Turkish and Thai locales as clients.
The Oracle WebCenter installation gives you the option of installing Oracle Universal Content Management (UCM). If you choose not to install Oracle UCM during the Oracle WebCenter installation, you can install Oracle UCM separately in stand-alone mode. Installation instructions are available at the following location:
http://download.oracle.com/docs/cd/E10316_01/owc.htm
These installation instructions are missing some important information, which is covered below. The following topics are covered:
The last question is during the installation procedure is:
Select components to install. 1. ContentFolios: Collect related items in folios 2. Folders_g: Organize content into hierarchical folders 3. LinkManager8: Hypertext link management support 4. OracleTextSearch: External Oracle 11g database as search indexer support 5. ThreadedDiscussions: Threaded discussion management Enter numbers separated by commas to toggle, 0 to unselect all, F to finish:
Make sure you DO NOT include number 2 (Folders_g
) for this answer; you should not install Folders_g
using the installation script. Folders_g
will be installed when the wc_contentserverconfig.sh
script is run.
Instead of installing an new Content Server to use with Oracle WebCenter, you have the option of using an existing Content Server. Any existing Content Server used with Oracle WebCenter should have the Trash disabled. Trash will only be in the Content Server if you have installed a foldering component.
To see if Trash is enabled in the Content Server:
Go to Administration.
Go to Folder Configuration.
Go to System Folder Configuration.
The colour of the dot next to the Trash folder indicates whether or not the Trash is enabled:
Green = enabled
Gray = disabled
To disable the Trash:
Ensure you can edit marked folders:
Open the stellent_dir
/custom/Folders_g/folders_environment.cfg
(on UNIX) or stellent_dir
\custom\Folders_g\folders_environment.cfg
(on Windows) file.
Verify that the CollectionReadOnlyMarkedFolders
value is set to true
:
CollectionReadOnlyMarkedFolders=true
Restart the Content Server if you changed the folders_environment.cfg
file.
Log in to the Content Server Home Page as a user with Administrator privileges.
Go to Administration.
Go to Folder Configuration.
Go to System Folder Configuration.
Click on the green dot next to Trash. This will disable the Trash folder and will turn the dot grey.
Restore the value of CollectionReadOnlyMarkedFolders
if you had changed it and restart the Content Server.
Oracle Fusion Middleware only supports schemas in a byte-mode database. The nls_length_semantics
initialization parameter on the database where the schemas reside must be set to BYTE
; setting this parameter to CHAR
is not supported.
To check the values of this parameter using SQL*Plus, you can use the show parameters
command:
prompt> sqlplus "sys/password as sysdba"SQL> show parameters nls_length_semantics
Replace password
with the actual password for the SYS user.
Alternatively, you can check the values by querying the V$PARAMETER
view:
prompt> sqlplus "sys/password as sysdba"SQL> select name,value from v$parameter;
In the event that an installation fails, and you want to deinstall the failed installation and then reinstall the software to the same location, you must do the following:
Make sure that all the managed servers in the failed installation are shut down. You must verify this in the Administration Console; the word "SHUTDOWN" must appear next to the managed server name.
Deinstall the binaries in the Oracle Home directory using the deinstaller in the ORACLE_HOME
/oui/bin
directory.
Delete all the managed servers from the failed installation in the config.xml
file by using the Administration Console or WLST.
Delete all directories in the DOMAIN_HOME
/servers
directory:
This procedure will enable you to reinstall the software to the same location, using the same managed server names.
If you run the Integration Repository Creation Assistance Tool (irca.sh
on UNIX operating systems or irca.bat
on Windows operating systems) against an Oracle 10g database, you will get a java.lang.UnsupportedClassVersionError
error.
If you need to install the SOAINFRA
schema and you are using a user with only DBA permissions, run the following commands on your database prior to running RCU:
GRANT ALL ON dbms_aqadm TO user WITH GRANT OPTION; GRANT ALL ON dbms_aq TO user WITH GRANT OPTION;
Replace user
in the command with the name of your database user.
There may be certain scenarios where you will need to remove WebLogic Domains that you have created. The Oracle Universal Installer is used to remove Oracle Instances and Oracle Home directories only; it does not remove WebLogic Domains.
If you need to remove a WebLogic Domain, you must do so manually. Please refer to your Oracle WebLogic Server documentation for more information.
Upon completing of an Oracle Web Tier, Oracle Identity Management, or Oracle Portal, Forms, Reports and Discoverer installation, the following errors may be seen in the install
time_and_date
.log
file:
[2009-11-04T21:15:13.959-06:00] [OUI] [NOTIFICATION] [] [OUI] [tid: 16] [ecid: 0000IJ2LeAeFs1ALJa5Eif1Aw^9l000007,0] OUI-10080:The pre-requisite for the component Sun JDK 1.6.0.14.08 has failed. [2009-11-04T21:15:13.960-06:00] [OUI] [NOTIFICATION] [] [OUI] [tid: 16] [ecid: 0000IJ2LeAeFs1ALJa5Eif1Aw^9l000007,0] OUI-10080:The pre-requisite for the component Oracle Configuration Manager 10.3.1.2.0 has failed.
These messages occur because the Sun JDK and Oracle Configuration Manager are not installed in the oracle_common
directory. You can safely ignore these messages.
When installing Oracle Web Tier, the sample response files that are provided in the Disk1/stage/Response
(on UNIX operating systems) or Disk1\stage\Response
(on Windows operating systems) directories are missing an entry for specifying the Middleware Home directory.
If you plan on using these response files for silent installation, you must add the MIDDLEWARE_HOME
entry to the file. For example:
MIDDLEWARE_HOME=/home/Oracle/Middleware
This section describes configuration issues and their workarounds. It includes the following topics:
Section 2.2.3, "Specify Security Updates Screen Does Not Appear in the Configuration Wizard"
Section 2.2.4, "Unsupported Database Appears in the Configuration Wizard"
Section 2.2.5, "Configuring Oracle Identity Management When WebLogic Node Manager is Running"
Section 2.2.7, "Password Requirements for Oracle Internet Directory Administrator"
Section 2.2.8, "OPMN Does Not Start if the LD_ASSUME_KERNEL Environment Variable is Set"
Section 2.2.9, "Changing the Listen Address of a Managed Server"
Section 2.2.10, "Expand Cluster Requires Changes to the emd.properties File"
Section 2.2.11, "Domain Extension Overwrites JDBC Data Source Name"
Section 2.2.12, "Schemas Are Not Visible After Upgrade of Oracle Identity Management"
Section 2.2.14, "Error Message When Configuring Oracle Identity Federation"
Section 2.2.15, "Ensure There Are No Missing Products When Using unpack.sh or unpack.cmd"
Section 2.2.16, "Running unpack.sh or unpack.cmd on a Different Host"
Section 2.2.17, "Rerouting to Original URL After SSO Authentication in Firefox Browser"
Oracle Portal, Forms, Reports and Discoverer should be installed in its own Middleware home, which it can not share with any other Fusion Middleware products. All other Fusion Middleware products, such as Oracle SOA Suite, Oracle WebCenter Webcenter, or Oracle Identity Management, can share a Middleware Home.
In scenarios where you are using the Fusion Middleware Configuration Wizard to extend a domain or expand a cluster with remote machines, you must make sure that both the source and destination Middleware Home and Oracle Home directories are identical.
If you use silent installation (response file) to configure Oracle Identity Management, security updates (through Oracle Configuration Manager) are not configured. However, the ocm.rsp
file is created in the Oracle Home directory. If you run the Configuration Wizard GUI from the Oracle Home, you will not see the Specify Security Updates Screen because of the presence of the ocm.rsp
file.
To work around this issue, delete the ocm.rsp
file from the Oracle Home and run the Configuration Wizard to see the Specify Security Updates screen.
When running the Configuration Wizard after an Oracle SOA Suite, Oracle WebCenter, or Oracle Application Developer installation, the "Configure JDBC Component Schema Screen" lists IBM DB2 as one of the options in the drop-down list of the "Vendor" field.
IBM DB2 is not yet supported and should not be selected on this screen.
To configure Oracle Identity Management, using either the Install and Configure option or the Configuration Wizard, when the WebLogic Node Manager utility is running from the same Middleware Home directory where Oracle Identity Management is installed, the StartScriptEnabled
parameter in the nodemanager.properties file must be set to true. For example: StartScriptEnabled=true
To configure Oracle Identity Management when the StartScriptEnabled
parameter is set to false
, you must:
Set the StartScriptEnabled
parameter to true.
Stop, then restart the Node Manager utility.
Configure Oracle Identity Management using either the Install and Configure option or the Configuration Wizard.
Note: The nodemanager.properties file is located in the WL_HOME/common/nodemanager/ directory. |
If you choose to configure Oracle Internet Directory (OID) with Oracle Data Vault:
Apply patch 8897382 (see the README file in the patch for instructions).
In the ORACLE_HOME
/ldap/datasecurity/dbv_oid_command_rules.sql
(on UNIX operating systems) or ORACLE_HOME
\ldap\datasecurity\dbv_oid_command_rules.sql
(on Windows operating systems) file, find the following code:
/declare . begin . dvsys.dbms_macadm.CREATE_COMMAND_RULE( command => 'CONNECT' ,rule_set_name => 'OID App Access' ,object_owner => 'ODS' ,object_name => '%' ,enabled => 'Y'); . commit; . end;/
Change the following line:
,object_owner => 'ODS'
to:
,object_owner => '%'
When configuring Oracle Internet Directory, using either the installer's Install and Configure option or the Configuration Wizard, you must enter and confirm the Administrator Password.
The following is a list of the requirements for the Oracle Internet Directory Administrator Password. The password must contain:
At least 5 characters
No more than 30 characters
At least one number
Only alpha-numeric characters, underscore ( _ ), dollar sign ( $ ), and pound/hash ( # )
Note: If the password you enter does not satisfy these requirements, the following error message appears:INST-07037: Administrator Password field value contains one or more invalid characters or the value is not in proper format. |
For the Oracle Identity Management, Oracle Web Tier, and Oracle Portal, Forms, Reports and Discoverer installations, Oracle Process Manager and Notification Server (OPMN) will not start if the LD_ASSUME_KERNEL
environment variable is set. Make sure that this environment variable is not set.
When you run the Configuration Wizard after installing Oracle Identity Management or Oracle Portal, Forms, Reports and Discoverer, the listen address for WebLogic managed servers is left blank by default (to listen to all network interfaces). If you change the listen address to the actual host name, the managed server stops listening from outside the machine.
It is recommended that you either leave the listen address blank, or specify the IP address of the host rather than using the host name.
After running the Oracle Fusion Middleware Configuration Wizard to expand a cluster, the EMD_URL
parameter in the INSTANCE_HOME
/EMAGENT/EMAGENT/sysman/config/emd.properties
(on UNIX) or INSTANCE_HOME
\EMAGENT\EMAGENT\sysman\config\emd.properties
(on Windows) file contains the values shown below:
EMD_URL=http://localhost.localdomain:port/emd/main
You must edit this parameter and replace localhost
and localdomain
with the actual host and domain information of your environment. For example, using 5160
as the port number:
EMD_URL=http://myhost.mydomain.mycompany.com:5160/emd/main
When a WebLogic Domain with JDBC resources is extended to either Oracle SOA Suite or Oracle WebCenter, the JDBC data source name will be changed. This behavior is commonly observed in cases where WebLogic Server version lower than 9.x is upgraded to a version higher than 9.x and then extended to Oracle SOA Suite or Oracle WebCenter.
To work around this issue, you must manually edit the JDBC data source names.
After upgrading Oracle Identity Management from Release 10g (10.1.4.3) to 11g Release 1 (11.1.1), the Oracle Directory Service schemas (ODS
and ODSSM
) are not visible in the Repository Creation Utility (RCU).
The reason for this is because RCU is not used during the upgrade process, and RCU only recognizes schemas that are created by RCU. Refer to Oracle Fusion Middleware Repository Creation Utility User's Guide for more information.
If you are dropping the Identity Management schemas and you select both Oracle Internet Directory (ODS
) and Oracle Identity Federation (OIF
) to be dropped, the RCU summary screen may not be displayed and an exception may be thrown in the console.
To work around this issue, select and drop one component at a time instead of selecting them both and dropping them together.
When other components are selected for a drop schema operation, the summary screen may display inaccurate information. However, the selected schemas will be successfully dropped from the database in spite of the erroneous information on the summary screen.
To work around this issue, select and drop only one component at a time.
During the configuration of Oracle Identity Federation (OIF), the following error message regarding key store and password may be seen in the configuration log file:
[app:OIF module:/fed path:/fed spec-version:2.5 version:11.1.1.1.0]: Failed while destroying servlet: usermanager. java.lang.RuntimeException: The server could not initialize properly: oracle.security.fed.sec.util.KeySourceException: Invalid/unsupported key store or incorrect password. Please verify that the password is correct and the store is a valid PKCS#12 PFX wallet or Java KeyStore file.
This error message can be safely ignored if OIF is running properly.
Oracle SOA Suite, Oracle WebCenter, and Application Developer all contain the pack.sh
and unpack.sh
(on UNIX systems) or pack.cmd
and unpack.cmd
(on Window systems) commands in their respective ORACLE_HOME
/common/bin
(on UNIX systems) or ORACLE_HOME
\common\bin
(on Windows systems) directories.
The pack.sh
and pack.cmd
scripts are used to create a template archive (.jar
) file that contains a snapshot of either an entire domain or a subset of a domain. The unpack.sh
and unpack.cmd
scripts are used to create a full domain or a subset of a domain used for a Managed Server domain directory on a remote machine.
The unpack.sh
and unpack.cmd
commands will fail if any installed products are missing from the machine where you are running the unpack.sh
or unpack.cmd
command.
If you are running the unpack.sh
(on UNIX) or unpack.cmd
(on Windows) command to unpack a domain on a remote host, the Oracle Home location and the Middleware Home location on the remote host should match the locations on the host where the pack was performed.
Below is a valid example:
Host 1: MW_HOME = /user/home/Middleware ORACLE_HOME =/user/home/Middleware/Oracle_SOA1 @ Host 2: MW_HOME = /user/home/Middleware ORACLE_HOME =/user/home/Middleware/Oracle_SOA1
The example below is NOT valid because the Oracle Homes do not match:
Host 1: MW_HOME = /user/home/Middleware ORACLE_HOME =/user/home/Middleware/Oracle_SOA1 @ Host 2: MW_HOME = /user/home/Middleware ORACLE_HOME =/user/home/Middleware/SOA_Home
The example below is NOT valid because the Middleware Homes do not match:
Host 1: MW_HOME = /user/home/Middleware ORACLE_HOME =/user/home/Middleware/Oracle_SOA1 @ Host 2: MW_HOME = /user/home/MWHome ORACLE_HOME =/user/home/Middleware/Oracle_SOA1
When configuring Oracle Portal, Forms, Reports and Discoverer, when both Oracle HTTP Server and Oracle Web Cache are selected for configuration, re-routing (back to the original URL) after Single Sign-On (SSO) authentication does not work in Firefox Browser when the initial request comes from Oracle HTTP Server.
The work arounds are to either use the Internet Explorer browser, or manually modify the INSTANCE_HOME
/config/OHS/instance_name/httpd.conf
file and change the ServerName
entry to include the port number. For example:
ServerName myhost.mydomain.com
should be changed to:
ServerName myhost.mydomain.com:port
Replace port
with the actual port number.
This section describes known issues. It includes the following topics:
Forms and Reports Builder is not suported on Linux x86-64, Solaris Operating System (SPARC 64-Bit), AIX Based Systems (64-Bit), HP-UX PA-RISC (64-Bit), HP-UX Itanium, and Microsoft Windows x64 platforms. It is supported on Linux x86 and Microsoft Windows (32-Bit) platforms only.
This section describes documentation errata. It includes the following topics:
Section 2.4.3, "Missing Information for Deinstalling Oracle Homes"
Section 2.4.4, "Invalid Oracle Home Installation Location Specified"
Section 2.7 ,"Installing in a Middleware Home Where Oracle SOA Suite or Oracle Identity Management Already Exist" in the Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer is missing a third step. The complete instructions should be as follows:
If you are installing Oracle Portal, Forms, Reports and Discoverer into a Midldeware Home directory that already contains an Oracle SOA Suite or Oracle Identity Management installation, you must do the following before you install:
Navigate to the MW_HOME
/wlserver_10.3/common/nodemanager
(on UNIX operating systems) or MW_HOME
\wlserver_10.3\common\nodemanager
(on Windows operating systems) directory.
Edit the nodemanager.properties
file and set the StartScriptEnabled
property as follows:
StartScriptEnabled=true
Restart Node Manager.
In the deinstallation chapter for the Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer, Step 4 in Section 3.2.1, "Stopping Oracle Fusion Middleware" is missing a piece of information.
While the documentation instructs you to stop the Administration Server, it should be noted that the Administration Server must remain up and running if you are planning to deinstall managed instances.
When you run the deinstaller and you choose to remove an Oracle Home, the documentation is missing some information between the Deinstall Oracle Home and Deinstallation Progress screens.
On the Deinstall Oracle Home screen, you will see and be asked to verify the Oracle Home that is about to be deinstalled. When you click Deinstall, a warning dialog box will appear with the following options:
Click on "Yes" to continue.
Click on "No" to perform deinstall without deleting the directory.
Click on "Cancel" to go back to the "Inventory Dialog".
If you select "Yes" the Oracle Home directory will be removed at the end of the deinstallation procedure.
If you select "No" you must manually remove your Oracle Home directory after the deinstall is complete. For example, if you are deinstalling Oracle SOA Suite and your SOA Oracle Home directory was /home/Oracle/Middleware/Oracle_SOA1
on a UNIX operating system:
> cd /home/Oracle/Middleware > rm -rf Oracle_SOA1
On a Windows operating system, if your SOA Oracle Home directory was C:\Oracle\Middleware\Oracle_SOA1
, use a file manager window and navigate to the C:\Oracle\Middleware
directory, then right-click on the Oracle_SOA1
folder and select Delete.
In the installation guides for Oracle Web Tier and Oracle Portal, Forms, Reports and Discoverer, the documentation contains erroneous information regarding Oracle Home location on the Specify Installaton Location screen. The following text is incorrect:
You can specify a pre-existing Oracle Home directory (for example, you are reinstalling the software into an existing Oracle Home that was created from a previous installation that was incomplete).
If you specify an existing directory that you want to use for your Oracle Home, it must be an empty directory.
In the Installation Guides and Quick Installation Guides for Oracle SOA Suite, Oracle WebCenter, and Application Developer, the following note may appear:
Note: If you are installing the 32-bit version of the product, the system on which you are installing must also be a supported 32-bit system. Installing a 32-bit version of the product on a 64-bit system is not supported. |
This note is not applicable for these products and should be ignored.