The following topics are covered in this chapter:
This section contains the following topics:
Before you install any Oracle Fusion Middleware product, it is good practice to review the product information available on My Oracle Support:
When you register for My Oracle Support, you have easy access to important information about available patches and other important Oracle Fusion Middleware product information.
After you install Oracle Fusion Middleware 12c (12.2.1.2), there might be cases where additional patches are required to address specific known issues.
Patches for Oracle Fusion Middleware 12c are available from My Oracle Support:
The following table lists some of the specific Oracle Fusion Middleware patches that were available at the time these release notes were published.
Patch | Description |
---|---|
This is a mandatory patch that must be applied after you install Fusion Middleware 12c (12.2.1.2). See the README file for patching instructions. |
To download a patch:
Log in to My Oracle Support.
Click the Patches & Updates tab.
In the Patch Search area, select Patch Name or Number.
Enter the patch number.
Click Search. The Patch Search Results page appears.
Download and install the patch.
Before you install Oracle Business Activity Monitoring (Oracle BAM) 12c, be sure to review the My Oracle Support Document ID 1682371.1, which is available from My Oracle Support.
This Support Note provides important information about a mandatory patch that must be applied to Oracle BAM 12c immediately after installation.
This section contains the following topics:
After you apply the latest patches to Oracle WebLogic Server, the ORACLE_HOME/wlserver/server/lib/weblogic.policy
file must be edited to include the following entry in order for Middleware services such as Discoverer, Access Manager, and Identity Manager to start:
grant codeBase "file:ORACLE_HOME/WLS/patch_jars/-" { permission java.lang.RuntimePermission "oracle.*","read"; };
Replace ORACLE_HOME
with the location of your Oracle home directory.
Replace WLS
with one of the following:
patch_wls1035
for WebLogic Server version 10.3.5
patch_wls1036
for WebLogic Server version 10.3.6
patch_wls1212
for Weblogic Server version 12.1.2
After you install Oracle Traffic Director (OTD) on Solaris on SPARC (64–bit), you might see warning messages similar to the following examples in the Node Manager log when you start the OTD Node Manager:
WARNING: Key store file keystores.xml integrity check failed. Location: /home/oracle/config/domains/OTDDomain/config/fmwconfig/ Jul 19, 2016 10:44:36 PM oracle.security.jps.internal.keystore.file.FileKeyStoreManager openKeyStore WARNING: Opening of file based keystore failed. Reason : oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06502: Failed to read keystore. Reason javax.xml.bind.UnmarshalException
The first warning is a security warning, and the second warning is because of file synchronization issues with the keystores.xml
file. There is no workaround, as there is no impact on the OTD functionality. You can ignore these warnings.
A partition with a Japanese name cannot be created by using Fusion Middleware Control.
As a workaround, you can either use Fusion Middleware Control to create a partition that uses an English name or use the WebLogic Server Administration Console to create a partition with a Japanese name.
This section contains the following topics:
To register Node Manager as a Windows Service serving either one of the following:
A standalone OHS domain
A domain with a collocated ODI agent
Do the following after you have created the domain:
When you complete a standalone OHS installation, the step Start Node Manager and Domain Servers is displayed as one of the next steps you should take after installation.
This information is incorrect, as there are no domain servers configured during the standalone installation.
When you attempt to install a Fusion Middleware product on a 64-bit system, using a JDK for a 32-bit system, an error message is displayed before the installation begins.
Refer to the Oracle Fusion Middleware System Requirements and Specifications document for your product, and download a suitable JDK from the following location, before you install the Fusion Middleware software:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
If you run the installer jar file from a 32-bit JDK7 JVM on a 64-bit machine, the installer displays an incorrect message that the version of the JVM is correct and the version of the operating system on which the software is installed is incorrect.
Refer to the System Requirements and Specifications document for your product, and download a suitable JDK from the following location, before you install the Fusion Middleware software:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
While installing Oracle Web Tier 12c on AIX operating systems, warning messages may appear in the ORACLE_HOME/install/make.log
file.
These messages can be safely ignored.
On the AIX Platform, Simple Security Mode does not function with OAM Server.
While registering new Webgate Agent for artifacts generation, select Open or Cert Security Mode in the OAM Server Console.
If you configure an OSB and SOA cluster without selecting the correct server groups, then the domain creation fails with the following notice:
Preparing... Extracting Domain Contents... Creating Domain Security Information... Starting OPSS Security Configuration Data Processing... The OPSS Security Configuration Data Processing Completed... Domain Creation Failed!
To avoid this error, select OSB-MGD-SVRS-COMBINED and SOA-MGD-SVRS server groups for all managed servers on the Managed Servers screen.
While extending your SOA cluster domain with OSB, if you delete the existing Managed Server and create a new Managed Server, an incorrect config.xml
file is generated. For example, if you delete the existing soa_server1 and replaced it with osb_server1 you get an incorrect config.xml
file. Specifically, the following SAF tags are missing from config.xml
:
<saf-agent> <name>ReliableWseeSAFAgent_auto_1</name> <target>osb_server1 (migratable)</target> <store>WseeFileStore_auto_1</store> </saf-agent> <saf-agent> <name>ReliableWseeSAFAgent_auto_2</name> <target>ms2 (migratable)</target> <store>WseeFileStore_auto_2</store> </saf-agent>
To avoid this issue, while extending your SOA cluster, create new Managed Servers for OSB.
In Managed File Transfer the, install<timestamp>.out
file is not created in the log inventory.
This is not an error.
After you configure OHS WebGate and restart the servers, the following error message is displayed in oblog.log
file in the Domain_Home/server/ohs1/logs/oblog.log
directory:
2014/06/10@05:56:29.81679 14314 27 INIT ERROR 0x000003B6 ../oblistrwutil.cpp:225 "Could not read file" filename^/scratch/aime/1213FMW/ASCORE/RC4BColocated/MW_HOME/webgate/ohs/config /oblog_config.xml 2014/06/10@05:56:43.14915 14313 9 INIT ERROR 0x000003B6 ../oblistrwutil.cpp:225 "Could not read file" filename^/scratch/aime/1213FMW/ASCORE/RC4BColocated/MW_HOME/webgate/ohs/config /oblog_config.xml
To work around this issue, do the following:
If you want to configure Oracle WebLogic Server to access Oracle Internet Directory (OID) over SSL, then you need to obtain and add an OID server certificate to the WebLogic domain. The OID certificate is necessary for a successful SSL handshake and to successfully set up a connection from Oracle WebLogic Server to Oracle Internet Directory.
For information on obtaining the required certificate and adding it to the WebLogic Server store, see Enabling SSL Communication Between the Middle Tier and the Hardware Load Balancer in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite.