This chapter introduces Oracle Fusion Middleware Release Notes, 11g Release 1 (11.1.1). It includes the following topics:
This document is accurate at the time of publication. Oracle will update the release notes periodically after the software release. You can access the latest information and additions to these release notes on the Oracle Technology Network at:
This document contains the release information for Oracle Fusion Middleware 11g Release 1 (11.1.1). It describes differences between Oracle Fusion Middleware and its documented functionality.
Oracle recommends you review its contents before installing, or working with the product.
Oracle Fusion Middleware installation and configuration will not complete successfully unless users meet the hardware and software pre-requisite requirements before installation.
For more information, see "Review System Requirements and Specifications" in the Oracle Fusion Middleware Installation Planning Guide
Oracle Fusion Middleware memory requirements for installation, configuration, and runtime are as follows:
Without a Database on the same server: Minimum 4 GB physical memory and 4 GB swap.
With a Database on the same server: Minimum 6 GB physical memory and 6 GB swap.
Note:These minimum memory values are with the assumption that no user or operating system process is consuming any unusually high amount of memory. If such a condition exists, corresponding amount of additional physical memory will be required.
This section contains the following:
The latest certification information for Oracle Fusion Middleware 11g Release 1 (11.1.1) is available at the Oracle Fusion Middleware Supported System Configurations Central Hub:
This section describes known issues (exceptions) and their workarounds that are associated with Oracle Fusion Middleware 11g certifications. For a list of known issues that are associated with specific Oracle Fusion Middleware 11g Release 1 (11.1.1) components, see the Release Notes for the specific Oracle Fusion Middleware 11g Release 1 (11.1.1) component.
This section contains the following topics:
If you choose to configure Oracle Internet Directory with Database vault, do the following:
Apply patch 8897382 to fix bug 8897382.
Note:the following workaround is required only if the Oracle Fusion Middleware version is 188.8.131.52.0 (11gR1). This issue will be fixed in 184.108.40.206.0.
Apply the workaround for bug 8987186 by editing
<OH>/ldap/datasecurity/dbv_oid_command_rules.sql file and find the following declaration:
/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;/
and change the line that is indicated in bold:
/declare begin dvsys.dbms_macadm.CREATE_COMMAND_RULE( command => 'CONNECT' ,rule_set_name => 'OID App Access' ,object_owner => '%' ,object_name => '%' ,enabled => 'Y'); commit; end;/
For WebCenter 11g Release 1, the following platform has been verified with 32-bit JDK:
HP Itanium and HP PA-RISC:
32-bit HP JDK 1.6.0.02+
Active GridLink for Oracle RAC allows you to create GridLink data sources. GridLink data sources provide connectivity between Oracle WebLogic Server and an Oracle Database service targeted to an Oracle RAC cluster. You can also use GridLink data sources when configuring Oracle Exalogic with an Oracle RAC cluster.
However, GridLink data sources are currently supported for use only with custom Java EE applications running on Oracle WebLogic Server and Oracle Exalogic. They are not supported for use with the other Oracle Fusion Middleware products, such as Oracle SOA Suite, Oracle WebCenter, and Oracle Enterprise Content Management. For products other than Oracle WebLogic Server and Oracle Exalogic, Oracle recommends using JDBC Multi Data Sources to connect to an Oracle RAC service.
For more information about using GridLink data sources, see "Using Grid Link Data Sources" in Configuring and Managing JDBC Data Sources for Oracle WebLogic.
For information, see "Section 220.127.116.11, "Upgrading Sun JDK in the Oracle Home Directory."
When using AQ JMS with Oracle Database 18.104.22.168, JMXDELIVERYCOUNT is not set correctly.
The workaround is to apply patch 9932143 to Oracle Database 22.214.171.124. For more information, contact Oracle Support.
You need a Safari plugin to view raw XML. If there is no plugin installed, you will see unformatted XML which will be difficult to read. This is because Safari applies a default stylesheet, which only displays the text nodes in the XML document.
As a workaround, go to View > View Source in the Safari menu bar to see the full XML of the metadata document. Also, selecting File > Save and choosing XML Files as the file type, will correctly save the XML metadata file with all the markup intact.
After you install and configure Oracle Fusion Middleware 11g Release 1 (126.96.36.199.0), there might be cases where additional patches are required to address specific known issues.
Patches for Oracle Fusion Middleware 11g are available from My Oracle Support:
Table 1-1 lists some of the specific Oracle Fusion Middleware patches that were available at the time these release notes were published.
For additional patching information, see Section 3.1.1, "Patches Required to Address Specific Upgrade and Compatibility Requirements".
|Oracle Fusion Middleware Product or Component||Bug/Patch Number||Description|
Oracle SOA Suite - Oracle BPM Worklist application
Unless you apply this patch, errors appear in the log files when you access the Event Driven page in the Oracle Business Process Management Worklist application.
Oracle XDK for Java
This patch fixes the following issue.
If you use the XSU utility to insert some data into the database, and the database connection had the connection property called
Licensing information for Oracle Fusion Middleware is available at:
Detailed information regarding license compliance for Oracle Fusion Middleware is available at: