This chapter describes issues pertaining to Oracle Fusion Middleware product installation and configuration.
The following topics are covered in this chapter:
This section contains the following topics:
Before installing Oracle Business Activity Monitoring (Oracle BAM) 12c (12.1.3), 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 (12.1.3) immediately after installation.
Before installing any Oracle Fusion Middleware, 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.
This section contains the following topic:
After applying 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
This section contains the following topics:
Section 1.3.1, "Registering Node Manager as a Windows Service"
Section 1.3.2, "Incorrect Step Displayed on the Installation Complete Screen"
Section 1.3.3, "Error Message Displayed When Incorrect Version of JDK Used for Installation"
Section 1.3.4, "Incorrect Error Message Displayed if JDK not Compatible with Operating System"
Section 1.3.6, "Simple Security Mode Does Not Function with OAM Server"
Section 1.3.7, "Memory Usage Log Does Not Generate for -printmemory Option"
Section 1.3.8, "Disk Usage Log Does Not Generate for -printdiskusage Option"
Section 1.3.10, "Exception Appears While Starting RCU with -dropRepository"
Section 1.3.12, "Incorrect config.xml File Generated While Extending a SOA Cluster with OSB"
Section 1.3.13, "install<time-stamp>.out File not Created in the MFT Installation Log Directory"
Section 1.3.14, "Error Message Displayed in oblog.log File After Configuring OHS WebGate"
Section 1.3.15, "Configuring Oracle WebLogic Server to Access Oracle Internet Directory over SSL"
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:
Set the JAVA_OPTIONS environment variable so that it points to the proper Oracle home and Domain home directories.
set JAVA_OPTIONS=-Dohs.product.home=ORACLE_HOME -Dweblogic.RootDirectory=DOMAIN_HOME
For example:
set JAVA_OPTIONS=-Dohs.product.home=C:\Oracle\product\OHS\OracleHome -Dweblogic.RootDirectory=C:\Oracle\config\domains\OHSDomain
Go to the Domain home directory and run the following command:
installNodeMgrSvc.cmd
On completing 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 installing 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 installing the Fusion Middleware software:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
While installing Oracle Web Tier 12c (12.1.3) 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 is not functioning with OAM Server.
While registering new Webgate Agent for artifacts generation, select Open or Cert Security Mode in OAM Server Console.
In Oracle Fusion Middleware 12c (12.1.3), the memory usage log is not generated when you use the -printmemory option.
This issue will be addressed in a future release.
In Oracle Fusion Middleware 12c (12.1.3), the disk usage log is not generated when you use the -printdiskusage option.
This issue will be addressed in a future release.
In Oracle Data Integrator 12c (12.1.3) Standalone, errors of the following format are produced when you launch WLST:
Error execing the Python script
"Oracle_Home/oracle_common/common/wlst/mdsWLSTCommands.py" caused an
error "Traceback (innermost last):
You can safely ignore these error messages. These errors do not affect any functional aspects of WLST.
If you select the Skip this Page Next Time option on the RCU Welcome screen, you may encounter the following exception when you specify -dropRepository from the command line the next time you start RCU in graphical mode:
Exception in thread "main" java.lang.NullPointerException
Choose one of the following recommended workarounds to avoid this issue:
Do not select the Skip this Page Next Time option on the RCU Welcome screen.
For graphical mode, start RCU without the -dropRepository option.
For silent mode, start RCU with the -dropRepository option.
If you selected the Skip this Page Next Time option on the RCU Welcome screen, delete the following file:
/tmp/.skipWelcomePage_Oracle_Home_oracle_common
Restart RCU from the command line with the -dropRepository option.
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 will 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, create new Managed Servers for OSB.
In Managed File Transfer, install<timestamp>.out file is not created in the log inventory.
This is not an error.
After configuring OHS WebGate and restarting 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, do the following:
Run:
cp Oracle_Home/webgate/ohs/config/oblog_config_wg.xml $Oracle_Home/webgate/ohs/config/oblog_config.xml
Restart all the servers.
In order to configure Oracle WebLogic Server to access Oracle Internet Directory (OID) over SSL, 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 for successfully setting 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 Enterprise Deployment Guide for Oracle SOA Suite.
The are cases where he default Coherence configuration will cause errors in multinic systems. Servers use unicast for member to member communications. For this unicast communication, cluster members attempt to obtain the IP to bind to using the java.net.InetAddress.getLocalHost() call. This call returns "incorrect" addresses in some multi-nic configs. To overcome this, users need to add a unicast-listener entry in the default Coherence configuration file located at
ASERVER_HOME/config/coherence/defaultCoherenceCluster-coherence.xml. An entry specifying the <unicast-listen-address> needs to be added in the file. For example;
<name>defaultCoherenceCluster</name>
<coherence-cluster-params>
<unicast-listen-port>9991</unicast-listen-port>
<unicast-listen-address>192.168.4.0/24</unicast-listen-address>
<coherence-cluster-well-known-addresses>
<coherence-cluster-well-known-address>
<name>WKA-1</name>
The unicast address field supports Classless Inter-Domain Routing (CIDR) notation instead of specifying an exact IP address so that the same configuration can be used by different nodes. Refer to the below link for details.
http://docs.oracle.com/middleware/1212/wls/CLUST/coherence.htm#CLUST665
There are no known issues at this time.