Oracle® Fusion Middleware

Infrastructure Release Notes

11g Release 1 (11.1.1.7.0)

E54703-03

July 2015

Oracle Fusion Middleware Infrastructure Release Notes, 11g Release 1 (11.1.1.7.0)

E54703-03

Copyright © 2009, 2015,  Oracle and/or its affiliates. All rights reserved.

Primary Author: Sreetama Ghosh, Peter LaQuerre

Contributors: Paul Dickson, Robert Donat, Sankar Mani, Daniel Mortimer, William Norcott, Michael Rubino, Reza Shafii, Olaf Stullich, Sitaraman Swaminathan, Ken Vincent

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Introduction

- 1.1 Latest Release Information

- 1.2 Purpose of this Document

- 1.3 System Requirements and Specifications

- 1.4 Certification Information

- 1.4.1 Where to Find Oracle Fusion Middleware Certification Information

- 1.4.2 Certification Exceptions

- 1.4.2.1 Certification Information for Oracle Fusion Middleware 11g R1 with Oracle Database 11.2.0.1

- 1.4.2.2 Excel Export Issue on Windows Vista Client

- 1.4.2.3 Oracle Forms and Oracle Reports 11g Installer Issues In Windows Vista and Windows XP

- 1.4.2.4 Restrictions on Specific Browsers

- 1.4.3 JMSDELIVERYCOUNT Is Not Set Properly

- 1.4.4 Viewer Plugin Required On Safari 4 To View Raw XML Source

- 1.5 Downloading and Applying Required Patches

- 1.6 Licensing Information

2 Installation, Patching, and Configuration

- 2.1 Installation Issues and Workarounds

- 2.1.1 Resolving PATH and Directory Issues on Windows

- 2.1.1.1 Oracle Universal Installer Does Not Support Spaces in Directory Paths

- 2.1.1.2 Setting the PATH Environment Variable to Include Directories Containing Spaces or Parentheses

- 2.1.1.3 Setting the PATH Environment Variable for Oracle Configuration Manager

- 2.1.2 Issues Pertaining to Oracle SOA Suite Installation

- 2.1.2.1 Installing Oracle SOA Suite on a Dual Stack Host with IPv4

- 2.1.2.2 Installing Oracle SOA Suite Release 11.1.1.3.0 in a Turkish Environment

- 2.1.2.3 Prerequisite Checks Fail During the Installation of Oracle Portal, Forms, Reports, and Discoverer 11g Release 1 (11.1.1.2.0) on OEL6

- 2.1.3 Issues Pertaining to Oracle Portal, Forms, Reports and Discoverer Installation

- 2.1.3.1 Installing Oracle Portal, Forms, Reports and Discoverer on Windows with IPv6

- 2.1.3.2 Missing Shortcuts in the Oracle Portal, Forms, Reports and Discoverer Installation

- 2.1.3.3 Oracle Configuration Manager Fails During Domain Configuration of Oracle Portal, Forms, Reports, and Discoverer 11g Release 1 (11.1.1.7.0)

- 2.1.3.4 Considerations When Installing Oracle Portal 11g

- 2.1.3.5 Prerequisite Warnings During Installation

- 2.1.4 Issues Pertaining to Oracle Web Tier Installation

- 2.1.4.1 Oracle SOA Suite and Oracle Application Developer Must Be Installed Before Oracle Web Tier

- 2.1.4.2 Re-Installing Oracle Web Cache if Double Backslashes (\\) Are Specified During Installation

- 2.1.4.3 Oracle Web Tier Silent Install Requires Oracle Web Cache Component Name

- 2.1.5 Issues Pertaining to Oracle Identity Management Installation

- 2.1.5.1 Setting ADR_BASE for Oracle Internet Directory on Windows 2008 R2

- 2.1.5.2 WebLogic Administration Server Must Be Running When Extending Oracle Identity Management Domains

- 2.1.5.3 Extending the Schema in Oracle Internet Directory

- 2.1.5.4 Deinstalling a 11g (11.1.1.7.0) Oracle Internet Directory Instance Does Not Clean Up the OID Schema

- 2.1.5.5 Information about the Oracle Virtual Directory Adapters

- 2.1.5.6 Enabling the Retry Button

- 2.1.5.7 Server Startup Failures on Linux Operating Systems

- 2.1.5.8 Configuring OPMN Request Port

- 2.1.5.9 Silent Install with Privileged Ports on Linux Operating Systems

- 2.1.5.10 JDK Installed in ORACLE_COMMON During WebTier and IDM Installation

- 2.1.6 Issues Pertaining to JDK and JRE Installation

- 2.1.6.1 Asian Characters are Not Displayed on Oracle Linux 6.1 with JDK Versions Older Than 6u30

- 2.1.6.2 Specifying the JRE Location if Installing with Automatic Updates

- 2.1.6.3 Upgrading Sun JDK in the Oracle Home Directory

- 2.1.6.4 Out of Memory Errors When Using JDK 6 Update 23

- 2.1.7 Issues Pertaining to Oracle Universal Installer

- 2.1.7.1 Installer Produces Errors When Checking for Software Updates on My Oracle Support

- 2.1.7.2 Entering the Administrator Password for a Simple Oracle Business Intelligence Installation on Linux Operating Systems

- 2.1.7.3 Running the Installer From C:\Documents and Settings When C:\Documents Also Exists

- 2.1.8 Issues Pertaining to Database and Schema Installation

- 2.1.8.1 Error Encountered While Loading the Oracle Internet Directory (ODS) Schema

- 2.1.8.2 Setting the Correct Permission for the DBMS_REPUTIL Database Package

- 2.1.8.3 Setting the Correct Permission for the DBMS_JOB Database Package

- 2.1.8.4 Problems with the Oracle Home Directory Being Overwritten on Windows

- 2.1.8.5 Database Connection Failure During Schema Creation When Installing Oracle Internet Directory

- 2.1.8.6 Command to Drop Tablespaces and Data Files Does Not Drop Data Files from the File System

- 2.1.8.7 Using RCU 11g Release 1 (11.1.1.1.0) with Oracle Database 11g (11.2.0.1)

- 2.1.9 Error Messages and Exceptions Seen During Installation

- 2.1.9.1 Error Messages When Installing on IBM AIX 7.1

- 2.1.9.2 JRF Startup Class Exceptions May Appear in Oracle WebLogic Managed Server Logs After Extending Oracle Identity Management Domain

- 2.1.9.3 Sun JDK and Oracle Configuration Manager Failures in the Installation Log File

- 2.1.10 Issues Pertaining to Product Deinstallation

- 2.1.10.1 Proper Deinstallation for Reinstallation in the Event of a Failed Installation

- 2.1.10.2 Verify PATH Before Starting Classic Installation on Microsoft Windows x64 (64-Bit)

- 2.1.10.3 Deinstallation Does Not Remove WebLogic Domains

- 2.1.11 Oracle Recommends JDK Version 6 Update 29 for Oracle Service Bus 11g Release 1 (11.1.1.7.0)

- 2.1.12 Installing Oracle Service Registry in the Same Domain as Oracle SOA Suite

- 2.1.13 Problems Installing in Thai and Turkish Locales

- 2.1.14 Enterprise Manager Configuration Fails with Timezone Error Message

- 2.2 Patching Issues and Workarounds

- 2.2.1 Applications Will Not Start After WebLogic Server is Updated

- 2.2.2 Issues Pertaining to Patching Oracle SOA Suite

- 2.2.2.1 Patch Set Assistant Fails When Updating the SOAINFRA Schema in SQL Server Databases

- 2.2.2.2 Exception Seen When Extending Your Existing Oracle SOA Suite Domain with Oracle Business Process Management Suite

- 2.2.2.3 Exception Seen When Undeploying any SOA Composite with Range-Based Dimension Business Indicators

- 2.2.2.4 Running Oracle Business Process Management Suite with Microsoft SQL Server 2008 Database

- 2.2.2.5 Update to Oracle SOA Suite Release 11.1.1.3.0 Does Not Remove the b2b.r1ps1 Property

- 2.2.2.6 Manual Steps for Migrating Oracle UMS and Oracle MDS

- 2.2.2.7 Monitored BPEL Processes Generate Warning Messages in Log File After Applying 11g Release 1 (11.1.1.4.0) Patch Set

- 2.2.2.8 Oracle Rules Error in Administration Server Log Files After Patching an 11g Release 1 (11.1.1.2.0) Domain

- 2.2.2.9 Incorrect Instance State of Composite Applications After Applying the Latest Patch Set

- 2.2.3 Issues Pertaining to Patching Oracle WebCenter Portal

- 2.2.3.1 Problem Using WebCenter Portal: Spaces Customizations with .jsp Pages after Installing the 11.1.1.7.0 Patch Set

- 2.2.3.2 Errors When Updating Oracle WebCenter Portal Using WLST Commands

- 2.2.3.3 Errors When Adding Tagging and Search Task Flows to Pages

- 2.2.3.4 Personalization Settings in Activity Graph Task Flows Lost When WebCenter Portal is Patched

- 2.2.3.5 Language Not Displayed in the List of Languages Offered in Spaces

- 2.2.4 Issues Pertaining to Patching Oracle Identity Management

- 2.2.4.1 Access Denied When Running the oimPS1PS2upgrade Script

- 2.2.4.2 Installer Prompts for OID Privileged Ports Twice During the Patch Installation

- 2.2.4.3 Installer Does Not Detect Existing Oracle Home

- 2.2.4.4 Uploading Third Party JAR Files to the Database

- 2.2.4.5 Updating Oracle Identity Management with LDAP Sync Enabled Generates XML Errors

- 2.2.4.6 Access Policy With Approval Does Not Work After Patch

- 2.2.4.7 OID and OVD Saved Connections Not Available After Patch From 11g Release 1 (11.1.1.2.0) or 11g Release 1 (11.1.1.3.0)

- 2.2.4.8 Harmless Error When Running the upgradeOpss() Command When Upgrading Oracle Identity Management

- 2.2.4.9 Harmless Errors in the Log Files After Patching Oracle Identity Management to 11g Release 1 (11.1.1.4.0)

- 2.2.4.10 Harmless Warning Message When Migrating Oracle Identity Federation from 11g Release 1 (11.1.1.1.0) to 11g Release 1 (11.1.1.2.0)

- 2.2.4.11 Harmless Errors Logged When Patching Oracle Identity Management 11g Release 1 (11.1.1.2.0) to 11g Release 1 (11.1.1.3.0)

- 2.2.4.12 Harmless Exception Seen When Starting Oracle Identity Management Server 11g Release 1 (11.1.1.5.0)

- 2.2.5 Issues Pertaining to Patching System Components

- 2.2.5.1 Granting Access to Network-Related Packages for the Oracle Portal Schema

- 2.2.5.2 Redeploy System Components to Ensure Proper Deinstallation

- 2.2.5.3 Setting Execute Permissions for emctl When Migrating System Components

- 2.2.6 Issues Pertaining to Version Numbers After Patching

- 2.2.6.1 Oracle SOA Suite Tasks Not Visible in Firefox Browser After Upgrade

- 2.2.6.2 Some Applications Show Old Version Number After Patching

- 2.2.6.3 MDS Schema Version Number is Incorrect

- 2.2.6.4 Oracle BI Components Show Incorrect Version Number After Patching

- 2.2.6.5 Adding the Version Number for the odi-sdk-ws Application in config.xml

- 2.2.7 Issues Pertaining to Displays During or After Patching

- 2.2.7.1 Pages in Oracle Enterprise Manager and Oracle Directory Services Manager do not Display Correctly

- 2.2.7.2 Patch Set Assistant Does Not Display Multi-Byte Characters on Oracle Linux 6

- 2.2.7.3 Patch Set Assistant Does Not Display Multi-Byte Characters on Oracle Linux 6

- 2.2.8 Warning and Error Messages Seen as a Result of Patching

- 2.2.8.1 Harmless Warnings When Running upgradeOpss()

- 2.2.8.2 Harmless Warning Message in Log File When Patching Multiple Products to the Same Version

- 2.2.8.3 Error When Accessing the Oracle Portal Home Page

- 2.2.8.4 Applications Generate javax.xml.bind.JAXBException Runtime Errors After Installing 11g Release 1 (11.1.1.4.0) Patch Set

- 2.2.9 Oracle Configuration Manager Fails When Patching Oracle Identity Management and Oracle Web Tier

- 2.2.10 Resolving Oracle Service Bus Object Conflicts

- 2.2.11 Manual Step for ODI-BAM Users After Installing 11.1.1.4.0 Patch Set

- 2.3 Configuration Issues and Workarounds

- 2.3.1 Issues Pertaining to Oracle SOA Suite Configuration

- 2.3.1.1 Mediator Component Fails With Windows Server 2008 R2 Enterprise and JRockit

- 2.3.1.2 SOAINFRA Schema Contains Invalid Objects in 11g Release 1 (11.1.1.6.0)

- 2.3.1.3 Harmless Exception Seen for Oracle SOA Suite with WebSphere Application Server

- 2.3.1.4 Oracle SOA Suite Administration Server Fails to Start With Sun JDK on Windows XP 2002

- 2.3.2 Issues Pertaining to Oracle Identity Management Configuration

- 2.3.2.1 Oracle Internet Directory Server Does Not Listen on SSL Port

- 2.3.2.2 Metrics for Oracle Identity Management Components may not be Correctly Displayed in Enterprise Manager

- 2.3.2.3 Configuring Oracle Identity Management When WebLogic Node Manager is Running

- 2.3.2.4 Configuring Oracle Internet Directory with Oracle Data Vault

- 2.3.2.5 OIDMON Does Not Start After Configuring Oracle Internet Directory on Windows

- 2.3.2.6 Password Requirements for Oracle Internet Directory Administrator

- 2.3.2.7 Harmless Error Message When Configuring Oracle Identity Federation

- 2.3.3 Issues Pertaining to Oracle Identity and Access Management Configuration

- 2.3.3.1 Log Messages Appearing on Console During Oracle Identity Manager Schema Creation

- 2.3.3.2 Design Console Connectivity Fails Intermittently

- 2.3.4 Issues Pertaining to the Configuration Wizard

- 2.3.4.1 Starting the Configuration Wizard From a New Window

- 2.3.4.2 Specify Security Updates Screen Does Not Appear in the Configuration Wizard

- 2.3.5 Issues Pertaining to the Repository Creation Utility (RCU)

- 2.3.5.1 Increasing the Tablespace Size for the MDS Schema

- 2.3.5.2 Schemas Are Not Visible After Upgrade of Oracle Identity Management

- 2.3.5.3 RCU Summary Screen Issues

- 2.3.6 Issues Pertaining to Packing and Unpacking a Domain

- 2.3.6.1 Ensure There Are No Missing Products When Using unpack.sh or unpack.cmd

- 2.3.6.2 Running unpack.sh or unpack.cmd on a Different Host

- 2.3.6.3 Starting Managed Servers on Remote System After Packing and Unpacking Domain

- 2.3.7 Issues Pertaining to Cluster Configuration

- 2.3.7.1 Extend Domain and Expand Cluster Scenarios with Remote Systems

- 2.3.7.2 Unable to Extend an Existing Domain by Selecting Only Oracle Directory Integration Platform Without Cluster

- 2.3.7.3 Expand Cluster Requires Changes to the emd.properties File

- 2.3.8 Discoverer URL is not Properly Displayed When Accessed Through SSL

- 2.3.9 Cleaning up the JDeveloper Directories for a Failed Deployment on Windows

- 2.3.10 OPMN Does Not Start if the LD_ASSUME_KERNEL Environment Variable is Set

- 2.3.11 Oracle WebCenter Portal wc-post-install.py Script Not Supported for Oracle RAC Datasources

- 2.3.12 FileNotFoundException When Cloning on Windows

- 2.3.13 Changing the Listen Address of a Managed Server

- 2.3.14 Domain Extension Overwrites JDBC Data Source Name

- 2.3.15 Rerouting to Original URL After SSO Authentication in Firefox and Safari Browsers

- 2.3.16 Deleting the Browser Cache in Browsers

- 2.3.17 WebLogic Administration Server Fails to Start Due to Memory Issues

- 2.4 Known Issues

- 2.4.1 Forms and Reports Builder Not Supported

- 2.5 Documentation Errata

- 2.5.1 Incorrect Option Specified in the RCU Online Help

- 2.5.2 Deinstall Instructions Missing for Oracle HTTP Server, Oracle Traffic Director, and Oracle iPlanet 11g Release 1 WebGates for Oracle Access Manager

- 2.5.2.1 Deinstalling Oracle HTTP Server, Oracle Traffic Director, and Oracle iPlanet 11g Release 1 WebGates for Oracle Access Manager

3 Upgrade

- 3.1 General Issues and Workarounds

- 3.1.1 Patches Required to Address Specific Upgrade and Compatibility Requirements

- 3.1.1.1 Obtaining Patches and Support Documents From My Oracle Support (Formerly OracleMetaLink)

- 3.1.1.2 Upgrading the Oracle BAM Schema on Oracle Database 11g on Microsoft Windows

- 3.1.2 Unable to Read Composite Model Error During SOA Application Upgrade

- 3.1.3 Oracle BAM Upgrade Issues

- 3.1.3.1 Datapump Export for Oracle BAM Upgrade Plug-in Fails in Oracle Database 10g (10.2.0.3), 10g (10.1.2.0.4), and Oracle Database 11g (11.1.0.7)

- 3.1.3.2 Dependent Alerts Do Not Upgrade Correctly

- 3.1.3.3 Problem Upgrading a Report that Contains Calculated Fields

- 3.1.3.4 Calculated Fields Reference the Field ID Rather Than Field Names After Upgrade to Oracle BAM 11g

- 3.1.3.5 Using the Oracle BAM 11g Samples After Upgrade from Oracle BAM 10g

- 3.1.4 Error When Upgrading Oracle Internet Directory Due to Invalid ODS Schema

- 3.1.5 Restore From Backup Required If Upgrade Fails During a Colocated Oracle Internet Directory and Oracle Directory Integration Platform Upgrade

- 3.1.6 Cannot Verify Oracle Forms Services Upgrade When Oracle HTTP Server is Running On a Separate Host

- 3.1.7 WebCenter Security Upgrade Release Notes

- 3.1.7.1 RowSetPermission check fails with compatibility flag set

- 3.1.7.2 Grants not migrated properly if application contains grants without permissions

- 3.1.7.3 Shared/public credentials not found after external application deployed

- 3.1.8 Oracle B2B Upgrade Release Notes

- 3.1.8.1 Service Name Is Required When Using ebMS with Oracle B2B

- 3.1.8.2 Converting Wallets to Keystores for Oracle B2B 11g

- 3.1.8.3 Oracle B2B UCCnet Documents Not Upgraded to 11g

- 3.1.8.4 Errors in the Upgrade Log Files Even When Oracle B2B Schema Upgrade is Successful

- 3.1.9 Problem Accessing the Welcome Pages in Oracle HTTP Server After Upgrade

- 3.1.10 Misleading Error Message When Upgrading Oracle Internet Directory

- 3.1.11 Additional Steps Required When Redeploying the SOA Order Booking Sample Application on Oracle Fusion Middleware 11g

- 3.1.12 Additional Steps Required When Upgrading Human Taskflow Projects

- 3.1.13 Stopping Oracle Virtual Directory Processes During Upgrade

- 3.1.14 Providing Input to Upgrade Assistant Screens When Oracle Internet Directory Upgrade Fails

- 3.1.15 Upgrading Oracle Access Manager Middle Tier

- 3.1.16 Inaccurate Results When Running the Upgrade Assistant Verify Feature

- 3.1.17 Missing jdk_version.log File When Launching Upgrade Assistant

- 3.1.18 Test Suites in Oracle SOA Suite 10g Projects Not Upgraded to 11g

- 3.1.19 Incorrect Wiring When Migrating Certain Oracle SOA Suite 10g Projects to 11g

- 3.2 General Issues and Workarounds for Migrating from 11.1.1.1.0

- 3.2.1 Stopping the 11.1.1.2.0 Domain

- 3.2.2 Editing the patchMaster.properties File

- 3.2.3 Patching the Schema for Oracle Internet Directory

- 3.2.4 Changing the patchmaster.ValidationErrorContinue Property

- 3.2.5 Changing the Default Setting for Validation Tasks

- 3.2.6 Severe Error When Running the execute-sql-rcu Macro

- 3.2.7 Machine Names Do Not Appear in the Oracle WebLogic Server Administration Console

- 3.2.8 Using the Oracle BAM 11g Prepackaged Samples After Migrating from 11.1.1.1.0

- 3.2.8.1 Configuring the Oracle BAM 11g Samples After Migrating from 11.1.1.1.0

- 3.2.8.2 Using the Foreign Exchange Sample After Migrating from 11.1.1.1.0

- 3.3 Documentation Errata for Upgrade

- 3.3.1 Documentation Errata for the Oracle Fusion Middleware Upgrade Guide for Java EE

- 3.3.1.1 Clarification of Post-Upgrade Tasks for SSL-Enabled Oracle HTTP Server

4 Oracle Fusion Middleware Administration

- 4.1 General Issues and Workarounds

- 4.1.1 Clarification About Path for OPMN

- 4.1.2 Fusion Middleware Control May Return Error in Mixed IPv6 and IPv4 Environment

- 4.1.3 Deploying JSF Applications

- 4.1.4 Limitations in Moving from Test to Production

- 4.1.5 Limitations in Moving Oracle Business Process Management from Test to Production Environment

- 4.1.6 Message Returned with Incorrect Error Message Level

- 4.2 Configuration Issues and Workarounds

- 4.2.1 Must Stop Oracle SOA Suite Managed Server Before Stopping soa-infra

- 4.2.2 Fusion Middleware Control Does Not Keep Column Preferences in Log Viewer Pages

- 4.2.3 Topology Viewer Does Not Display Applications Deployed to a Cluster

- 4.2.4 Changing Log File Format

- 4.2.5 SSL Automation Tool Configuration Issues

- 4.3 Documentation Errata for the Oracle Fusion Middleware Administrator's Guide

- 4.3.1 Combining All Oracle Homes in a Single Inventory File

- 4.3.2 Correction to Link About Supported Databases for MDS

- 4.3.3 Clarification of Move Plan Properties for Oracle WebCenter Content

5 Oracle Enterprise Manager Fusion Middleware Control

- 5.1 General Issues and Workarounds

- 5.1.1 Product Behavior After a Session Timeout

- 5.1.2 Fixing Errors Displayed When Selecting the TopLink Sessions Command in Fusion Middleware Control

- 5.1.3 Verifying the DISPLAY Variable to Correct Problems Displaying Graphics

- 5.1.4 Incomplete Information Available on the MDS Configuration Page

- 5.1.5 Exceptions When Starting Oracle Web Cache After Accessing Configuration Pages from Oracle Enterprise Manager Fusion Middleware Control

- 5.1.6 Table Display Problems When Using Some Language Variants

- 5.1.7 Problems When Internet Explorer 7 is Configured to Open Pop-Up Windows in a New Tab

- 5.1.8 Additional Fusion Middleware Control Release Notes

- 5.1.9 Problem with Performance Charts After Moving a Chart Region

- 5.1.10 Memory Issue When Configuring SOA on Microsoft Windows x64 (64-Bit)

- 5.1.11 Display Problems When Running JDK 160_18 on Intel Systems that Support the SSE4.2 Instruction Set

- 5.1.12 Adobe Flash Plugin Required When Displaying Fusion Middleware Control in the Apple Safari Browser

- 5.1.13 Unable to Access Fusion Middleware Control After Installing the Oracle Identity Management 11.1.1.4.0 Patch Set

- 5.1.14 Error Message on Deleting the Shared Folder After Scale-Out

- 5.1.15 Coreapplication Process for Oracle Business Intelligence Reported as Down in Fusion Middleware Control

- 5.1.16 Online Help Error Message in Enterprise Manager Log Files Can Be Ignored

- 5.1.17 Incorrect or Missing Metrics Help Information

- 5.1.18 Error When Accessing the Entry Point URL for the NonJ2EEManagement Internal Application

- 5.2 Documentation Errata

- 5.2.1 Search Unavailable for Some Embedded Administrator's Guides

- 5.2.2 Patching Section in the Fusion Middleware Control Online Help is Not Supported

- 5.2.3 Help Topic for Secure Sockets Layer Tab Needs Updated Description for WebLogic CA Certificate

6 Oracle Fusion Middleware High Availability and Enterprise Deployment

- 6.1 General Issues and Workarounds

- 6.1.1 Secure Resources in Application Tier

- 6.1.2 Accessing Web Services Policies Page in Cold Failover Environment

- 6.1.3 Timeout Settings for SOA Request-Response Operations are Not Propagated in a Node Failure

- 6.1.4 Very Intensive Uploads from I/PM to UCM May Require Use of IP-Based Filters in UCM Instead of Hostname-Based Filters

- 6.1.5 Use srvctl in 11.2 Oracle RAC Databases to Set Up AQ Notification and Server-side TAF

- 6.1.6 Failover Is Not Seamless When Creating Reports in Oracle BI Publisher

- 6.1.7 Cannot Save Agent When Oracle Business Intelligence Managed Server Fails Over

- 6.1.8 Installing Additional Oracle Portal, Forms, Reports, and Discoverer Instances After Upgrading Oracle Single Sign-On 10g to Oracle Access Manager 11g

- 6.1.9 JMS Instance Fails In a BI Publisher Cluster

- 6.1.10 Undelivered Records not Recovered During RAC Failover of Singleton SOA Server

- 6.1.11 Synchronous BPEL Process Issues

- 6.2 Configuration Issues and Workarounds

- 6.2.1 Fusion Middleware Control May Display Incorrect Status

- 6.2.2 Accumulated BPEL Instances Cause Performance Decrease

- 6.2.3 Extra Message Enqueue when One a Cluster Server is Brought Down and Back Up

- 6.2.4 Duplicate Unrecoverable Human Workflow Instance Created with Oracle RAC Failover

- 6.2.5 No High Availability Support for SOA B2B TCP/IP

- 6.2.6 WebLogic Administration Server on Machines with Multiple Network Cards

- 6.2.7 Additional Parameters for SOA and Oracle RAC Data Sources

- 6.2.8 Message Sequencing and MLLP Not Supported in Oracle B2B HA Environments

- 6.2.9 Credentials not Propagated for Transport Protocols in B2B

- 6.2.10 Use Fully-Qualified Hostnames when Configuring Front-end Hosts in High Availability Configurations

- 6.2.11 Managed Server goes into Suspended Status After Oracle RAC Failover

- 6.2.12 Primary/Secondary Configuration Section of the Availability Tab is Not Visible

- 6.2.13 Server Start Parameters Not Getting Set After Scaling Out the Oracle Business Intelligence Managed Server

- 6.2.14 Ensuring the Oracle HTTP Server Lock File is on a Local Drive

- 6.2.15 Recreating OSSO Agents that Point to the Load Balancer URL

- 6.2.16 Use Lower-Case Letters for GridLink Data Source RAC Service Name

- 6.2.17 Additional Steps Needed for Oracle RTD Request Forwarding to Work Correctly

- 6.2.18 Error INST-08075 Occurs When Scaling Out the BI System

- 6.2.19 First Defined RAC Instance Must Be Available On Domain Startup When Configuring with RAC Multi Data Source

- 6.3 Testing Abrupt Failures of WebLogic Server When Using File Stores on NFS

- 6.4 Documentation Errata

- 6.4.1 Documentation Errata for the Fusion Middleware High Availability Guide

- 6.4.1.1 Latest Requirements and Certification Information

- 6.4.1.2 Error in Line to Add to mod_wl_ohs.conf File

- 6.4.2 Documentation Errata for the Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management

- 6.4.2.1 Set -DDomainRegistrationEnabled=true when Starting Node Manager

- 6.4.2.2 Ignore Empty Section in the Oracle Virtual Directory Chapter

- 6.4.2.3 Installing Identity Management Sections Are Incorrectly Organized

- 6.4.2.4 Errors in Instructions for Using the Guide

- 6.4.2.5 LDIF File Error in Procedure for Creating Users and Groups for Oracle WebLogic Server

- 6.4.2.6 Run Additional emctl Commands When Extending the Domain with Oracle Internet Directory or Oracle Virtual Directory

- 6.4.2.7 Errors in Section 2.4, Shared Storage and Recommended Directory Structure

7 Oracle JDeveloper and Oracle Application Development Framework (ADF)

8 Oracle Platform Security Services

- 8.1 Configuration Issues and Workarounds

- 8.1.1 Oracle Fusion Middleware Audit Framework

- 8.1.1.1 Configuring Auditing for Oracle Access Manager

- 8.1.1.2 Audit Reports do not Display Translated Text in Certain Locales

- 8.1.1.3 Audit Reports Always Display in English

- 8.1.1.4 Audit Store Does not Support Reassociation through EM

- 8.1.1.5 OWSM Audit Events not Audited

- 8.1.2 Trailing '\n' Character in Bootstrap Key

- 8.1.3 Users with Same Name in Multiple Identity Stores

- 8.1.4 Script listAppRoles Outputs Wrong Characters

- 8.1.5 Propagating Identities over the HTTP Protocol

- 8.1.5.1 Addition to Section Propagating Identities over the HTTP Protocol

- 8.1.5.2 Correction to Section Client Application Code Sample

- 8.1.5.3 Correction to Section Keystore Service Configuration

- 8.1.5.4 Updating the Trust Service Configuration Parameters

- 8.1.6 Pool Configuration Missing in Identity Store

- 8.2 Documentation Errata

- 8.2.1 Updated Configuration for Role Category

- 8.2.2 Correct setAuditRepository Command Reference Example

- 8.2.3 Demo CA Certificate not for Production Use

- 8.2.4 Incorrect Link to ILM Content

- 8.2.5 Incorrect Table Title in Appendix C

- 8.2.6 Clarification of Note in Appendix C

- 8.2.7 Notes Regarding Need for Server Restarts

9 Web Services Development, Security, and Administration

- 9.1 Using Multibyte User Credentials with wss_http_token_* Policy

- 9.2 Performing a Bulk Upload of Policies

- 9.3 Reviewing Policy Configuration Override Values After Detaching a Client Policy

- 9.4 Removing Post-deployment Customizations

- 9.5 Reviewing Localization Limitations

- 9.6 When Using WLST to Import a Security Policy, the Same Policy May Be Repeatedly Imported

- 9.7 Identity in WSDLs Is Not Used for Enforcement with ADF DC Applications

- 9.8 Fusion Middleware Control Does Not List Policies When Two Servers Are SSL Enabled (Two-way SSL)

- 9.9 Web Service Test Page Cannot Test Input Arguments Bound to SOAP Headers

- 9.10 When Adding SAML Issuer From Fusion Middleware Control the jps-config.xml File Is Incorrectly Updated

- 9.11 Patching of Patch Set 1 WebLogic Server Web Services Attached to Custom Polices With Patch Set 3 Oracle WSM Policy Manager

- 9.12 Custom Policy Fails When an Empty Subject Is Passed

- 9.13 Possible Limitation When Using Custom Exactly-one Policies

- 9.14 Ignore "Services Compatibility" Error for Security Policies Used Between Oracle WSM and WebLogic Server

- 9.15 Compatible Policies Not Returned When Using JDeveloper Wizard to Attach Oracle WSM Policies to Web Service Client

- 9.16 SAML Bearer Token Policies Now Signed by Default

- 9.17 Security Policies Do Not Work on Subscriber Mediator Component

- 9.18 Policy Table Might Not Show Attached Policies for Some Locales

- 9.19 Manual Step Required to Uptake Changes in Predefined Policy

- 9.20 Usage Tracking Not Enabled for WebLogic Web Service Client

- 9.21 Do Not Attach a Permitall and Denyall Policy to the Same Web Service

- 9.22 Additional Quotes in Fusion Middleware Control for Run-time Constraint Input from WLST

- 9.23 Scoped Configuration Override Persists for Subsequent References to the Same Policy

- 9.24 New Default Settings for Policies

- 9.25 Restart Applications to Get an Accurate Policy Usage Count

- 9.26 Kerberos Policy Enforcement Throws an "Unable to Obtain Password from User" Error

- 9.27 The migrateAttachments WLST Command Fails for WebLogic JAX-WS Web Services

- 9.28 A Null Pointer Exception Could be Thrown When Verifying a SOAP Message Signature

- 9.29 checkWSMstatus() WLST Command Fails Against a Domain When wsm-pm Targets Multiple Servers

- 9.30 Performance Improvements in Web Services Policy Pages

- 9.31 Cross-Domain Policy Manager Configuration is Not Supported in this Release

- 9.32 The setWebServicePolicyOverride WLST Command Does Not Apply to JAVA EE (WebLogic) Web Services

- 9.33 Support for JSON Web Tokens Available for This Release

- 9.34 New Functionality and Changes Available in PS6 MLR Patch

- 9.34.1 Removal of SPNEGO Assertion From Multi Token REST Policies

- 9.34.2 RESTful Client Security Support

- 9.34.3 OAuth 2.0 Support for REST and SOAP Services and Clients

- 9.34.4 REST APIs for Managing Credentials, Keystores, and Trust Stores

10 Oracle Fusion Middleware on IBM WebSphere

- 10.1 General Issues and Workarounds

- 10.1.1 Log File Error Message when Starting the SOA Server

- 10.1.2 Save Settings Button Under Accessibility User Preferences Has Incorrect Label

- 10.1.3 Oracle Business Process Management Causes java.lang.OutOfMemoryError on IBM WebSphere Application Server

- 10.1.4 Cannot Create an XA Connection Factory in the IBM WebSphere Administration Console

- 10.1.5 Accessibility Mode for User Messaging Preferences is Ignored on an IBM WebSphere Application Server

- 10.1.6 Adding Shared Libraries to Deploy a Task Form from Oracle JDeveloper

- 10.1.7 Setting Cookie Paths for Oracle SOA Suite Applications

- 10.1.8 Deploying a SOA Composite Application to a SOA Cluster

- 10.1.9 Cannot Deploy a SOA Bundle File from Oracle Enterprise Manager Fusion Middleware Control

- 10.1.10 One-and-Only-One Event Subscriptions Are Not Supported

- 10.1.11 Deployed Task Form Startup Failure in IBM WebSphere Administration Console

- 10.1.12 Oracle BPM Worklist Displays as Undefined in Administration Console

- 10.1.13 Dashboard Tab May Display Completed SOA Composite Instance States as Running

- 10.1.14 Two-Way SSL Configuration with Oracle SOA Suite Is Not Supported

- 10.1.15 Multiple Fault Recovery Failure with the Recover With Options Dialog

- 10.1.16 IBM WebSphere Application Server - ND Installation Requires a Server Restart

- 10.1.17 Test Emulations of Asynchronous BPEL Processes Fail

- 10.1.18 SETMANAGEDCONNECTION() Fails with ILLEGALSTATEEXCEPTION for the AQ Adapter

- 10.1.19 Invalid PolicySet Error When Accessing a Deployed Oracle Fusion Middleware Application on IBM WebSphere

- 10.1.20 Cannot Stop or Start Oracle Internal Applications From Fusion Middleware Control on IBM WebSphere

- 10.1.21 For the JMS Adapter, Instances Become Recoverable Even Without Failover

- 10.1.22 Kerberos and SPNEGO are not supported with Oracle WSM

- 10.1.23 REST Security Policies and Templates Not Certified

- 10.2 Configuration Issues and Workarounds

- 10.2.1 Error Configuring a Cell When IBM WebSphere Installed on Windows 2003 and 2008

- 10.2.2 Configuring Coherence for a SOA Cluster on IBM WebSphere

- 10.2.3 Limitations When Configuring Oracle Business Activity Monitoring for High Availability on IBM WebSphere

- 10.2.4 Requests Received by IBM HTTP Server (IHS) Are Routed to the Fusion Middleware Welcome Page

- 10.2.5 Unable to Register WSRP/JPDK Producers Through Pagelet Producer Console on IBM WebSphere

- 10.2.6 Unable to Configure Password Settings Through Pagelet Producer Console on IBM WebSphere

- 10.2.7 Restart of Deployment Manager Required When Configuring Oracle SOA Suite for High Availability on IBM WebSphere

- 10.2.8 Additional Configurations For SSO Logout on WebSphere

- 10.2.9 java.lang.ClassNotFoundException Error Message seen in the Log File When Deploying SimpleApprovalTaskFlow on IBM WebSphere

- 10.3 Documentation Errata

- 10.3.1 Updates to Steps for Patching WebCenter Portal 11.1.1.6.0 Installations to 11.1.1.7.0

- 10.3.2 Updates to Steps for Configuring Oracle Business Intelligence for Scaling Out on IBM WebSphere

- 10.3.3 Updates to Section on Upgrading

11 SSL Configuration in Oracle Fusion Middleware

- 11.1 General Issues and Workarounds

- 11.1.1 Incorrect Message or Error when Importing a Wallet

Preface

This preface contains the following sections:

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

Audience

This manual is intended for users of Oracle Fusion Middleware.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see these Oracle resources:

- Oracle Fusion Middleware Documentation on Oracle Fusion Middleware Disk 1

- Oracle Fusion Middleware Documentation Library 11g Release 1 (11.1.1)

- Oracle Technology Network at http://www.oracle.com/technetwork/index.html.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Introduction

This chapter introduces Oracle Fusion Middleware Infrastructure Release Notes, 11g Release 1 (11.1.1). It includes the following topics:

- Section 1.1, "Latest Release Information"

- Section 1.2, "Purpose of this Document"

- Section 1.3, "System Requirements and Specifications"

- Section 1.4, "Certification Information"

- Section 1.5, "Downloading and Applying Required Patches"

- Section 1.6, "Licensing Information"

1.1 Latest Release Information

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:

http://www.oracle.com/technetwork/indexes/documentation/index.html

1.2 Purpose of this Document

This document contains the release information for Oracle Application Server 11g Release 1 (11.1.1). It describes differences between Oracle Application Server and its documented functionality.

Oracle recommends you review its contents before installing, or working with the product.

1.3 System Requirements and Specifications

Oracle Application Server 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

1.4 Certification Information

This section contains the following:

- Section 1.4.1, "Where to Find Oracle Fusion Middleware Certification Information"

- Section 1.4.2, "Certification Exceptions"

- Section 1.4.3, "JMSDELIVERYCOUNT Is Not Set Properly"

- Section 1.4.4, "Viewer Plugin Required On Safari 4 To View Raw XML Source"

1.4.1 Where to Find Oracle Fusion Middleware Certification Information

The latest certification information for Oracle Application Server 11g Release 1 (11.1.1) is available at the Oracle Fusion Middleware Supported System Configurations Central Hub:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

1.4.2 Certification Exceptions

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:

- Section 1.4.2.1, "Certification Information for Oracle Fusion Middleware 11g R1 with Oracle Database 11.2.0.1"

- Section 1.4.2.2, "Excel Export Issue on Windows Vista Client"

- Section 1.4.2.3, "Oracle Forms and Oracle Reports 11g Installer Issues In Windows Vista and Windows XP"

- Section 1.4.2.4, "Restrictions on Specific Browsers"

1.4.2.1 Certification Information for Oracle Fusion Middleware 11g R1 with Oracle Database 11.2.0.1

If you choose to configure Oracle Internet Directory with Database vault, do the following:

1. Apply patch 8897382 to fix bug 8897382.

Note:
the following workaround is required only if the Oracle Fusion Middleware version is 11.1.1.1.0 (11gR1). This issue will be fixed in 11.1.1.2.0.

2. 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;/

1.4.2.2 Excel Export Issue on Windows Vista Client

Vista prevents applets from creating files in the local file system if the User Account Control (UAC) system is turned on. You can experience this problem if you have the UAC setting enabled on Vista and if you use a component like Discoverer Plus. If you start Discoverer Plus and if you try exporting a worksheet to a specified directory, the exporting succeeds but you cannot see the exported file in the directory. The available workarounds is to disable UAC and set protection mode to OFF. Refer to Bugs 8410655 and 7328867 for additional information.

1.4.2.3 Oracle Forms and Oracle Reports 11g Installer Issues In Windows Vista and Windows XP

Only the design-time environments (Builders) are supported for Oracle Forms and Oracle Reports in Windows Vista and Windows XP.However, in the Configure Components screen in the Oracle Installer, the Server Components, Management Components and System Components are selected by default, but Developer Tools is deselected. When installing Oracle Forms Builder, or Oracle Reports Builder on Windows Vista and Windows XP computers, you must:

- Select Developer Tools, such as Oracle Forms Builder or Oracle Reports Builder. Their respective server components are automatically selected.

- Deselect all System Components and Management Components.

- Deselect the Portal and Discoverer tools. Two of the Discoverer components – Discoverer Admin and Discoverer Desktop – will be installed even if you do not select Discoverer in the Configure Components screen of the installer. This is the correct, expected behavior in 11.1.1.1.0.

For Oracle Forms, since the System Components including Oracle HTTP Server are not supported in Windows Vista and Windows XP, the following features are not supported:

1. Oracle Forms and Reports integration.

2. The creation of virtual directories.

1.4.2.4 Restrictions on Specific Browsers

This section lists restrictions on specific browsers.

1.4.2.4.1 Internet Explorer Browser Goes Blank When Adding Portlets in Oracle Webcenter

If you add portlets in Oracle Webcenter by using Internet Explorer, then the page can go blank. When it does go blank, a download message appears on the browser's status bar. However, nothing is downloaded and the browser remains blank until you click the browser's back button. If this problem occurs, the portlets will appear only when you hit the browser's back button. This issue does not occur with Firefox.

As a workaround, click the browser's back button.

1.4.2.4.2 Unable to View the Output of a JSPX Page in Internet Explorer 7

When a JSPX page is deployed and is then accessed using Internet Explorer 7 (IE7), the XHTML source is displayed instead of the page contents. This occurs in both normal and osjp.next modes.

The workaround is to instruct application users to access the application with Firefox or Safari.

1.4.2.4.3 Unable to View the Output of SVG files in Internet Explorer 7

When a page using Scalar Vector Graphics is deployed and is then accessed using Internet Explorer 7 (IE7), the source is displayed instead of the page's graphic contents. This occurs in both normal and osjp.next modes.

The workaround for this issue is that Application developers should avoid using SVG graphics in their applications, as it is not natively supported in IE7. If they are used, a warning similar to the following should be added:

All current browsers, with the exception of Internet Explorer, support SVG files. Internet Explorer requires a plug-in to display SVG files. The plug-ins are available for free, for example, the Adobe SVG Viewer at http://www.adobe.com/svg/viewer/install/.

1.4.2.4.4 Java Plugin for Discoverer Plus Not Downloaded Automatically on Firefox

When you attempt to connect to Discoverer Plus by using the Mozilla Firefox browser on a computer that does not have Java 1.6 installed, Firefox does not download the JRE 1.6 plug-in automatically. Instead, Firefox displays the following message: "Additional plugins are required to display this page..."

The workaround is to download the JRE 1.6 plug-in by clicking the Install Missing Plugin link to install it manually.

1.4.3 JMSDELIVERYCOUNT Is Not Set Properly

When using AQ JMS with Oracle Database 11.2.0.1, JMXDELIVERYCOUNT is not set correctly.

The workaround is to apply patch 9932143 to Oracle Database 11.2.0.1. For more information, contact Oracle Support.

1.4.4 Viewer Plugin Required On Safari 4 To View Raw XML Source

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.

1.5 Downloading and Applying Required Patches

After you install and configure Oracle Fusion Middleware 11g Release 1 (11.1.1.4.0), there might be cases where additional patches are required to address specific known issues.

Complete the following steps to obtain a patch:

1. Log into the My Oracle Support web site at https://myoraclesupport.com/.

2. Click the Patches & Updates tab.

3. Use the Patch Search area to locate patches.

4. On the Patch Search Results page, select a patch and click Download to download the patch.

5. Install the patch by following the instructions in the README file that is included with the patch.

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".

Table 1-1 Patches Required to Fix Specific Issues with Oracle Fusion Middleware 11g

Oracle Fusion Middleware Product or Component

Bug/Patch Number

Description

Oracle SOA Suite - Oracle BPM Worklist application

9901600

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

10337609

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 oracle.jdbc.J2EE13Compliant set to "true", and the target column was some kind of numeric column, then it is possible for the insert to fail with a the following error:

java.lang.NumberFormatException

1.6 Licensing Information

Licensing information for Oracle Application Server is available at:

http://oraclestore.oracle.com

Detailed information regarding license compliance for Oracle Application Server is available at:

http://www.oracle.com/technetwork/middleware/ias/overview/index.html

2 Installation, Patching, and Configuration

This chapter describes issues associated with Oracle Fusion Middleware installation, patching, and configuration. It includes the following topics:

- Section 2.1, "Installation Issues and Workarounds"

- Section 2.2, "Patching Issues and Workarounds"

- Section 2.3, "Configuration Issues and Workarounds"

- Section 2.4, "Known Issues"

- Section 2.5, "Documentation Errata"

Note:
This chapter contains issues you might encounter while installing, patching, or configuring any of the Oracle Fusion Middleware products.
Be sure to review the product-specific release note chapters elsewhere in this document for any additional issues specific to the products you are using.

2.1 Installation Issues and Workarounds

This section describes issue and workarounds related to Oracle Fusion Middleware product installation. It includes the following topics:

- Section 2.1.1, "Resolving PATH and Directory Issues on Windows"

- Section 2.1.2, "Issues Pertaining to Oracle SOA Suite Installation"

- Section 2.1.3, "Issues Pertaining to Oracle Portal, Forms, Reports and Discoverer Installation"

- Section 2.1.4, "Issues Pertaining to Oracle Web Tier Installation"

- Section 2.1.5, "Issues Pertaining to Oracle Identity Management Installation"

- Section 2.1.6, "Issues Pertaining to JDK and JRE Installation"

- Section 2.1.7, "Issues Pertaining to Oracle Universal Installer"

- Section 2.1.8, "Issues Pertaining to Database and Schema Installation"

- Section 2.1.9, "Error Messages and Exceptions Seen During Installation"

- Section 2.1.10, "Issues Pertaining to Product Deinstallation"

- Section 2.1.11, "Oracle Recommends JDK Version 6 Update 29 for Oracle Service Bus 11g Release 1 (11.1.1.7.0)"

- Section 2.1.12, "Installing Oracle Service Registry in the Same Domain as Oracle SOA Suite"

- Section 2.1.13, "Problems Installing in Thai and Turkish Locales"

2.1.1 Resolving PATH and Directory Issues on Windows

This section contains the following:

- Section 2.1.1.1, "Oracle Universal Installer Does Not Support Spaces in Directory Paths"

- Section 2.1.1.2, "Setting the PATH Environment Variable to Include Directories Containing Spaces or Parentheses"

- Section 2.1.1.3, "Setting the PATH Environment Variable for Oracle Configuration Manager"

2.1.1.1 Oracle Universal Installer Does Not Support Spaces in Directory Paths

If you are running Oracle Universal Installer from the command line on a Windows operating system and you need to specify the location to a specific JRE, make sure there are no spaces in the directory path to the JRE that is specified as a parameter from the command line. For example, the following is not supported:

setup.exe -jreLoc C:\Program Files\Middleware\jdk160_version

To work around this issue, you must shorten "C:\Program Files" to use the Windows short name "C:\Progra~1" as shown below:

setup.exe -jreLoc C:\Progra~1\Middleware\jdk160_version

2.1.1.2 Setting the PATH Environment Variable to Include Directories Containing Spaces or Parentheses

If your PATH environment variable includes a directory containing spaces or parentheses (for example, C:\Program Files or C:\Program Files (x86)), you must convert this directory to the Windows short name as specified below:

- For C:\Program Files, use the Windows short name C:\PROGRA~1 in your PATH environment variable.

- For C:\Program Files (x86), use the Windows short name C:\PROGRA~2 in your PATH environment variable.

In addition, if your PATH environment variable includes another environment variable that uses either C:\Program Files or C:\Program Files (x86) in its definition, then you must also change C:\Program Files or C:\Program Files (x86) to its respective Windows short name in that environment variable's definition.

2.1.1.3 Setting the PATH Environment Variable for Oracle Configuration Manager

In order for Oracle Configuration Manager to work properly on Windows operating systems, make sure the PATH environment variable is set to C:\windows\system32.

2.1.2 Issues Pertaining to Oracle SOA Suite Installation

This section contains the following:

- Section 2.1.2.1, "Installing Oracle SOA Suite on a Dual Stack Host with IPv4"

- Section 2.1.2.2, "Installing Oracle SOA Suite Release 11.1.1.3.0 in a Turkish Environment"

2.1.2.1 Installing Oracle SOA Suite on a Dual Stack Host with IPv4

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.

2.1.2.2 Installing Oracle SOA Suite Release 11.1.1.3.0 in a Turkish Environment

If you are installing Oracle SOA Suite Release 11.1.1.3.0 in a Turkish environment, there will be some functionality loss for Oracle Enterprise Manager Fusion Middleware Control.

There is no work around for this issue. Oracle recommends that you avoid installing in a Turkish environment and install in an English environment instead.

2.1.2.3 Prerequisite Checks Fail During the Installation of Oracle Portal, Forms, Reports, and Discoverer 11g Release 1 (11.1.1.2.0) on OEL6

During the installation of Oracle Portal, Forms, Reports and Discoverer 11g Release 1 (11.1.1.2.0) on OEL6 operating system, prerequisite checks fail with errors.

To work around this issue, perform any one of the following steps:

- Press Continue and continue with the installation.

- Use -ignoreSysPreReqs command line additional argument to the runInstaller:

./runInstaller -ignoreSysPreReqs

2.1.3 Issues Pertaining to Oracle Portal, Forms, Reports and Discoverer Installation

This section contains the following:

- Section 2.1.3.1, "Installing Oracle Portal, Forms, Reports and Discoverer on Windows with IPv6"

- Section 2.1.3.2, "Missing Shortcuts in the Oracle Portal, Forms, Reports and Discoverer Installation"

- Section 2.1.3.3, "Oracle Configuration Manager Fails During Domain Configuration of Oracle Portal, Forms, Reports, and Discoverer 11g Release 1 (11.1.1.7.0)"

- Section 2.1.3.4, "Considerations When Installing Oracle Portal 11g"

- Section 2.1.3.5, "Prerequisite Warnings During Installation"

2.1.3.1 Installing Oracle Portal, Forms, Reports and Discoverer on Windows with IPv6

If you are installing Oracle Portal, Forms, Reports and Discoverer on a Windows operating system that supports IPv6 (for example, Windows Vista or Windows 7), the components in the installation will not start if IPv6 is enabled.

Make sure that IPv6 is disabled on your Windows operating system before you install these components.

2.1.3.2 Missing Shortcuts in the Oracle Portal, Forms, Reports and Discoverer Installation

During the installation of Oracle Portal, Forms, Reports and Discoverer on any Windows operating system, if you choose to extend your domain or expand a cluster and specify a domain name other than the default "ClassicDomain," you will see a "Missing Shortcut" error when you try to start and stop the Managed Servers.

The work around for this issue is as follows:

1. From the Start menu, right-click on the shortcut that generated the error message.

2. In the shortcut tab, go to the target node.

3. Change the domain name to the correct domain name.

4. Click Apply.

2.1.3.3 Oracle Configuration Manager Fails During Domain Configuration of Oracle Portal, Forms, Reports, and Discoverer 11g Release 1 (11.1.1.7.0)

After upgrading Oracle Portal, Forms, Reports, and Discoverer to 11g Release 1 (11.1.1.7.0), or after installing Oracle Portal, Forms, Reports, and Discoverer 11g Release 1 (11.1.1.7.0), if you choose to configure Oracle Configuration Manager during domain configuration, the configuring Oracle Configuration Manager fails.

The workaround for this issue is as follows:

1. Navigate to the following location on your system:

ORACLE_HOME/ccr/bin

2. Run the following commands in the Oracle Instance home:

$ setupCCR
$ configCCR
$ emCCR collect
$ emCCR status

Note:
You can choose to skip configuring Oracle Configuration Manager when you initially run the 11g Release 1 (11.1.1.7.0) configuration wizard.

To configure Oracle Configuration Manager after configuring the domain, do the following:

1. Navigate to the ORACLE_HOME/ccr/bin directory on your system.

2. Set the variable ORACLE_CONFIG_HOME in your Oracle Instance home directory.

3. Run the following commands:

$ setupCCR
$ configCCR
$ emCCR collect
$ emCCR status

2.1.3.4 Considerations When Installing Oracle Portal 11g

Before you install a new Oracle Portal, Forms, Reports, and Discoverer 11g environment, be sure to review the following important resources:

- Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer

- My Oracle Support document ID 1364497.1

2.1.3.5 Prerequisite Warnings During Installation

Vendor release updates cumulative patches and/or packages that may supersede 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

2.1.4 Issues Pertaining to Oracle Web Tier Installation

This section contains the following:

- Section 2.1.4.1, "Oracle SOA Suite and Oracle Application Developer Must Be Installed Before Oracle Web Tier"

- Section 2.1.4.2, "Re-Installing Oracle Web Cache if Double Backslashes (\\) Are Specified During Installation"

- Section 2.1.4.3, "Oracle Web Tier Silent Install Requires Oracle Web Cache Component Name"

2.1.4.1 Oracle SOA Suite and Oracle Application Developer Must Be Installed Before Oracle Web Tier

To ensure that the oracle_common/soa/modules/commons-cli-1.1.jaroracle_common\soa\modules\commons-cli-1.1.jar file is installed properly, if you plan to associate Oracle Web Tier with an existing domain, you must install Oracle Web Tier after all other products are installed.

2.1.4.2 Re-Installing Oracle Web Cache if Double Backslashes (\\) Are Specified During Installation

During the installation of Oracle Web Tier on Microsoft Windows operating systems, if you accidentally specified an installation directory using double backslash (\\) characters, you will encounter problems when you try to start Oracle Web Cache.

The work around is to re-install Oracle Web Cache without using double backslash characters in the installation location.

2.1.4.3 Oracle Web Tier Silent Install Requires Oracle Web Cache Component Name

If you are performing a silent Oracle Web Tier installation for Oracle HTTP Server, an Oracle Web Cache component name (WEBCACHE_COMPONENT_NAME parameter) must also be mentioned in the response file, even though Oracle Web Cache is not required for Oracle HTTP Server installation. Even though both component names are provided, as long as CONFIGURE_WEBCACHE is set to false then only Oracle HTTP Server will be installed and configured.

There is no work around for this issue.

2.1.5 Issues Pertaining to Oracle Identity Management Installation

This section contains the following:

Note:
For 11g Release 1 (11.1.1.6.0) installation release notes, refer to the following links:

- Oracle Fusion Middleware Release Notes 11g Release 1 (11.1.1) for Linux x86

- Oracle Fusion Middleware Release Notes 11g Release 1 (11.1.1) for Microsoft Windows (32-Bit)

- Section 2.1.5.1, "Setting ADR_BASE for Oracle Internet Directory on Windows 2008 R2"

- Section 2.1.5.2, "WebLogic Administration Server Must Be Running When Extending Oracle Identity Management Domains"

- Section 2.1.5.3, "Extending the Schema in Oracle Internet Directory"

- Section 2.1.5.4, "Deinstalling a 11g (11.1.1.7.0) Oracle Internet Directory Instance Does Not Clean Up the OID Schema"

- Section 2.1.5.5, "Information about the Oracle Virtual Directory Adapters"

- Section 2.1.5.6, "Enabling the Retry Button"

- Section 2.1.5.8, "Configuring OPMN Request Port"

2.1.5.1 Setting ADR_BASE for Oracle Internet Directory on Windows 2008 R2

On Windows 2008 R2 with Service Pack operating systems, while running the Oracle Internet Directory installer or configuration tool, if you encounter issues starting of Oracle Internet Directory instance you must do the following to avoid conflicts with log file creation between the Fusion Middleware components and database components:

- Login to your system as the Administrator.

- In the sqlnet.ora file in the TNS_ADMIN directory (ORACLE_INSTANCE\config) directory of the OID environment, set the ADR_BASE parameter's value to any directory other than the Oracle home (for example, C:\temp). If the sqlnet.ora file does not exist in the TNS_ADMIN directory, create the file and add the ADR_BASE parameter's value as mentioned above.

- Delete the Oracle Internet Directory component with componentType OID and componentName oid1 as described in "Deleting an Oracle Internet Directory Component by Using opmnctl" in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory. You can safely ignore any errors or warnings about the component not existing.

- Create an Oracle Internet Directory component with componentType OID and componentName oid1 as described in "Creating an Oracle Internet Directory Component by Using opmnctl" in Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

- Click Retry.

2.1.5.2 WebLogic Administration Server Must Be Running When Extending Oracle Identity Management Domains

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.

2.1.5.3 Extending the Schema in Oracle Internet Directory

If you have Oracle Identity Manager 11g Release 1 (11.1.1.7.0) against Oracle Internet Directory release prior to Oracle Internet Directory 11g Release 1 (11.1.1.6.0) through libOVD 11g Release 1 (11.1.1.7.0) (with oamEnabled set to true and LDAPSync enabled), when you try to create a new user, the following error is displayed:

javax.naming.directory.SchemaViolationException:[LDAP: error code 65 -Failed to find orclpwdexpirationdate in mandatory or optional attribute list.
]

Workaround:

You need to extend the schema in Oracle Internet Directory that you have installed. To change the backend IDStore schema, do the following:

1. Create a new attribute.

attributetypes: ( 2.16.840.1.113894.200.1.7 NAME 'orclPwdExpirationDate' EQUALITY caseIgnoreMatch SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' SINGLE-VALUE USAGE userApplications).

2. Modify the existing orclIDXPerson objectclass to include orclPwdExpirationDate as an optional attribute.

Note:
You can use Oracle Directory Services Manager to connect to Oracle Internet Directory and make the schema changes.

2.1.5.4 Deinstalling a 11g (11.1.1.7.0) Oracle Internet Directory Instance Does Not Clean Up the OID Schema

When deinstalling a configured Oracle Internet Directory instance from Oracle Identity Management 11g (11.1.1.7.0) the file-based instance directory is removed, but the related Oracle Internet Directory instance configuration is not deleted. Hence, any future configuration adds to the instance count by including the deleted instances.

The following logic is missing from the command to remove a OID instance:

ldapdelete -p <oid ldap port> -D cn=orcladmin -w <password> "cn=<OID
instance name as defined in the ODS
schema>,cn=osdldapd,cn=subconfigsubentry"

Workaround:

After deleting an instance and before recreating the instance run the command:

ldapdelete -p <oid ldap port> -D cn=orcladmin -w <password> "cn=<OID
instance name as defined in the ODS schema>,cn=osdldapd,cn=subconfigsubentry

2.1.5.5 Information about the Oracle Virtual Directory Adapters

Oracle Virtual Directory adapters are not listed in the Home page.

To work around this issue on Linux operating systems, copy the osdt_cert.jar file from the Oracle Common home to the directory under ORACLE_HOME/inventory/Scripts/ext/lib/Oracle_IDM1.

To work around this issue on Windows operating systems, copy the jar prior to the configuration phase because it does not work if you copy it later.

2.1.5.6 Enabling the Retry Button

To retry a failed Oracle Identity Management configuration you must enable the Retry button. Check the box on the left side of the failed item to enable the Retry button.

2.1.5.7 Server Startup Failures on Linux Operating Systems

When starting the Oracle Identity Management server (Managed server or Administration server), the server may fail to start. You may see the following error:

Failed to push ldap config data to
libOvd for service instance "idstore.ldap" in JPS context "default", cause:
java.io.FileNotFoundException: /tmp/.ovdlock.tmp (Permission denied)>

To work around this issue, run the following command and the start he server again:

chmod 666 /tmp/.ovdlock.tmp

2.1.5.8 Configuring OPMN Request Port

The static ports.ini for the Oracle Identity Management 11g Release 1 (11.1.1.7.0) installer has an OPMN request port specified. This port is not used in the Oracle Identity Management configuration and does not serve any specific functional purpose.

To configure the port you have to manually add the entry to opmn.xml after the oracle instance is provisioned.

2.1.5.9 Silent Install with Privileged Ports on Linux Operating Systems

To install and configure privileged ports in silent mode on Linux operating systems, do the following:

1. Complete only a silent install with Oracle Identity Management 11g Release 1 (11.1.1.7.0).

2. Run the oracleroot.sh and oidroot.sh scripts in the Oracle home.
You must run these scripts as root user.

3. Change .apachectl permissions.
Run the following as root user:

/bin/chown root /$OH/ohs/bin/.apachectl
/bin/chmod 6750 /$OH/ohs/bin/.apachectl

4. Complete a silent configuration with the privileged ports.

2.1.5.10 JDK Installed in ORACLE_COMMON During WebTier and IDM Installation

In 11.1.1.2 release, while installing WebTier or IDM on Linux x86-64, AIX and HP-UX platforms, JDK gets installed in both ORACLE_HOME and ORACLE_COMMON. JDK version installed in ORACLE_COMMON is lower in version than that of ORACLE_HOME. Hence should not be used. PS3 patching fails to resolve the JDK issue. However, this issue does not affect the successful installation of Webtier or IDM.

To work around this issue, use the JDK in ORACLE_HOME and avoid using the JDK installed in ORACLE_COMMON.

2.1.6 Issues Pertaining to JDK and JRE Installation

This section contains the following:

- Section 2.1.6.2, "Specifying the JRE Location if Installing with Automatic Updates"

- Section 2.1.6.3, "Upgrading Sun JDK in the Oracle Home Directory"

- Section 2.1.6.4, "Out of Memory Errors When Using JDK 6 Update 23"

2.1.6.1 Asian Characters are Not Displayed on Oracle Linux 6.1 with JDK Versions Older Than 6u30

If you are running on Oracle Linux 6.1 with JDK version older than 6u30, Chinese, Korean, and Japanese characters are not displayed in the Oracle Universal Installer.

To work around this issue, do the following:

1. Go to the JAVA_HOME/jre/lib directory.

2. Copy fontconfig.RedHat.6.0.bfc to fontconfig.RedHat.6.1.bfc.

3. Copy fontconfig.RedHat.6.0.properties.src to fontconfig.RedHat.6.1.properties.src.

4. Run the installer.

2.1.6.2 Specifying the JRE Location if Installing with Automatic Updates

If you are ins7talling one of the following Oracle Fusion Middleware products:

- Oracle SOA Suite

- Oracle WebCenter Portal

- Oracle Service Bus

- Oracle WebCenter Content

- Oracle Data Integrator

- Oracle Identity and Access Management

And you will choose to configure automatic updates on the Install Software Updates screen by selecting Download and install updates from My Oracle Support you must specify the location of a JRE on your system by using the -jreLoc parameter from the command line when you start the installer.

If you do not use the -jreLoc parameter and instead wait for the installer to prompt you for a JRE location, an exception will be seen during the installation.

2.1.6.3 Upgrading Sun JDK in the Oracle Home Directory

Certain installations, including Oracle Identity Management, Oracle Portal, Forms, Reports and Discoverer, and Oracle Web Tier will install a Sun JDK in the Oracle home directory. This version of the Sun JDK may be lower in version than what is specified in the Oracle Fusion Middleware Certification Document:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

This JDK is used internally and should not be used to deploy Oracle SOA, Oracle WebCenter Portal, or any custom J2EE applications.

If you want a single JDK version deployed for all types of applications, you can upgrade the Sun JDK to a higher version (as specified in the Oracle Fusion Middleware Certification document) using the following steps:

1. Shut down all processes.

2. Back up your existing JDK.

3. Install a new JDK in the same location as your existing JDK.

4. Restart all processes.

2.1.6.4 Out of Memory Errors When Using JDK 6 Update 23

If you are experiencing out-of-memory errors when using JDK 6 Update 23, consider the following.

In JDK 6 Update 23, the escape analysis feature was enabled by default.This is an optimization within the hotspot compiler, which may require an increased memory footprint. When there is very little free space in the process for additional native memory allocations, for example due to a very large Java heap, this could lead to an out of memory situation.

The workaround for this issue is to add the following JVM argument when you start your application:

-XX:-DoEscapeAnalysis

You can identify JDK 6 Update 23 by using the java -version command, as follows:

java -version
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b50)
Java HotSpot(TM) Server VM (build 19.1-b02, mixed mode)

2.1.7 Issues Pertaining to Oracle Universal Installer

This section contains the following:

- Section 2.1.7.1, "Installer Produces Errors When Checking for Software Updates on My Oracle Support"

2.1.7.1 Installer Produces Errors When Checking for Software Updates on My Oracle Support

On the Install Software Updates screen, if you select the Search My Oracle Support for Updates option, provide the proper user credentials, and then click Search for Updates, the following error is seen in the installation log file:

java.net.NoRouteToHostException: No route to host

The work around is to use the Search Local Directory for Updates option on the Install Software Update screen and select a patch that has already been downloaded and is available locally. Patches can be downloaded manually from My Oracle Support or they can be obtained from your Oracle Support representative.

2.1.7.2 Entering the Administrator Password for a Simple Oracle Business Intelligence Installation on Linux Operating Systems

If you are installing Oracle Business Intelligence on a Linux operating system, and you select Simple Install on the Select Installation Type screen, the "Password" field is inactive when you navigate to the Administrator Details screen.

To work around this issue, right-click on the "Password" field and select Paste. The "Password" field becomes active and you can enter an Administrator password.

2.1.7.3 Running the Installer From C:\Documents and Settings When C:\Documents Also Exists

If you have downloaded the setup.exe installer in the C:\Document and Settings directory, and there is also the C:\Documents directory already present on your system, the installer will not start as it will attempt to locate files in C:\Documents.

The work around is to either remove or rename the C:\Documents directory.

2.1.8 Issues Pertaining to Database and Schema Installation

This section contains the following:

- Section 2.1.8.1, "Error Encountered While Loading the Oracle Internet Directory (ODS) Schema"

- Section 2.1.8.2, "Setting the Correct Permission for the DBMS_REPUTIL Database Package"

- Section 2.1.8.3, "Setting the Correct Permission for the DBMS_JOB Database Package"

- Section 2.1.8.4, "Problems with the Oracle Home Directory Being Overwritten on Windows"

- Section 2.1.8.5, "Database Connection Failure During Schema Creation When Installing Oracle Internet Directory"

- Section 2.1.8.6, "Command to Drop Tablespaces and Data Files Does Not Drop Data Files from the File System"

- Section 2.1.8.7, "Using RCU 11g Release 1 (11.1.1.1.0) with Oracle Database 11g (11.2.0.1)"

2.1.8.1 Error Encountered While Loading the Oracle Internet Directory (ODS) Schema

If you have password policy enabled at the database level on your Oracle database, you will receive the ORA-28003 error when loading the Oracle Internet Directory (ODS) schema.

To work around this issue, temporarily disable password policy, load the schema, then enable password policy again.

2.1.8.2 Setting the Correct Permission for the DBMS_REPUTIL Database Package

If you are creating the Oracle Internet Directory schemas in Oracle Database version 11.2.0.4 or later, use the following work around if you encounter an error from RCU:

1. Connect to the database as administrator and execute the following:

GRANT EXECUTE ON DBMS_REPUTIL TO PUBLIC;

2. Re-start RCU and create the schema.

3. After the schema is successfully created, connect to the database again as administrator and execute the following:

REVOKE EXECUTE ON DBMS_REPUTIL FROM PUBLIC;

2.1.8.3 Setting the Correct Permission for the DBMS_JOB Database Package

If you are creating the Oracle Internet Directory schema in an Oracle database using RCU, you may encounter the following error messages:

ORA-04063: package body "ODS.TSPURGE" has errors
ORA-06508: PL/SQL: could not find program unit being called: "ODS.TSPURGE"
ORA-06512: at line 3

To work around this issue:

1. Stop RCU and drop any Oracle Internet Directory schemas already created. Refer to "Dropping Schemas" in Oracle Fusion Middleware Repository Creation Utility User's Guide for instructions.

2. Log into the database using SQL*Plus and run the following command:

SQL> grant execute on sys.dbms_job to PUBLIC

3. Run RCU again and create the schemas.

2.1.8.4 Problems with the Oracle Home Directory Being Overwritten on Windows

If you are installing Oracle Fusion Middleware on a Windows system, and that system already contains an Oracle database, then you may encounter issues where the ORACLE_HOME global environment variable used by the database is overwritten by the Oracle Fusion Middleware product installation.

To view the global environment variable, select System Properties > Advanced > Environment variables > System Variables and check the value of ORACLE_HOME. From here, you can set the value of ORACLE_HOME to the location of the desired product.

2.1.8.5 Database Connection Failure During Schema Creation When Installing Oracle Internet Directory

If the installation of Oracle Internet Directory fails due to timeout or connection failure when connecting to a database for schema creation, you can try to reset the timeout parameter in the rcu.properties file. This file is located in the IDM_HOME/rcu/config\rcu\config directory-.

Open the rcu.properties file in a text editor, search for the property JDBC_LOGIN_TIMEOUT, and set its value to 30.

2.1.8.6 Command to Drop Tablespaces and Data Files Does Not Drop Data Files from the File System

On Windows operating systems, the command used to drop tablespaces and data files does not drop data files from the file system.

This is a known problem specific to Oracle databases running on Windows operating systems.

2.1.8.7 Using RCU 11g Release 1 (11.1.1.1.0) with Oracle Database 11g (11.2.0.1)

If you are using the version of RCU that is available in Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) with Oracle Database 11g (11.2.0.1), you will receive the following warning message:

The database you are connecting is not a supported version. Enter Database
with version equal to or higher than 10.2.0.4.0 in 10g or version equal to
higher than 11.1.0.7.0 in 11g. Refer to the certification matrix for
supported DB versions.

This warning can be safely ignored and you can proceed with your RCU operations.

This warning will not appear in the version of RCU available in Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) or later.

2.1.9 Error Messages and Exceptions Seen During Installation

This section contains the following:

- Section 2.1.9.2, "JRF Startup Class Exceptions May Appear in Oracle WebLogic Managed Server Logs After Extending Oracle Identity Management Domain"

- Section 2.1.9.3, "Sun JDK and Oracle Configuration Manager Failures in the Installation Log File"

2.1.9.1 Error Messages When Installing on IBM AIX 7.1

When installing Oracle Fusion Middleware 11g products on IBM AIX 7.1, you may see the following errors during the prerequisite checking portion of the installation:

Checking operating system certification
Expected result: One of 5300.08,6100.02
Actual result:: 7100.xx
Check complete. The overall result of this check is: Failed <<<<
Problem: This Oracle software is not certified on the current operating system

Checking recommended operating system patches
Check complete: The overall result of this check is: Not executed <<<<

These messages can be safely ignored. Selecting Continue in the dialog box will allow the installation to proceed.

2.1.9.2 JRF Startup Class Exceptions May Appear in Oracle WebLogic Managed Server Logs After Extending Oracle Identity Management Domain

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.

2.1.9.3 Sun JDK and Oracle Configuration Manager Failures in the Installation Log File

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 installtime_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.

2.1.10 Issues Pertaining to Product Deinstallation

This section contains the following:

- Section 2.1.10.1, "Proper Deinstallation for Reinstallation in the Event of a Failed Installation"

- Section 2.1.10.3, "Deinstallation Does Not Remove WebLogic Domains"

- Section 2.1.10.2, "Verify PATH Before Starting Classic Installation on Microsoft Windows x64 (64-Bit)"

2.1.10.1 Proper Deinstallation for Reinstallation in the Event of a Failed Installation

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:

1. 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.

2. Deinstall the binaries in the Oracle home directory using the deinstaller in the ORACLE_HOME/oui/bin\oui\bin directory.

3. Delete all the managed servers from the failed installation in the config.xml file by using the Administration Console or WLST.

4. Delete all directories in the DOMAIN_HOME/servers\servers directory:

This procedure will enable you to reinstall the software to the same location, using the same managed server names.

2.1.10.2 Verify PATH Before Starting Classic Installation on Microsoft Windows x64 (64-Bit)

Before starting Classic Application Server installation, any reference to Program Files (x86) must be removed from the PATH environment variable. On echoing PATH on the command prompt, Program Files (x86) should not be present.

2.1.10.3 Deinstallation Does Not Remove WebLogic Domains

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.

2.1.11 Oracle Recommends JDK Version 6 Update 29 for Oracle Service Bus 11g Release 1 (11.1.1.7.0)

Oracle Service Bus performs more slowly when running on certain versions of the Java Platform, Standard Edition Development Kit (JDK). For optimal performance, Oracle recommends using JDK version 6 update 29 with Oracle Service Bus 11g Release 1 (11.1.1.7.0).

2.1.12 Installing Oracle Service Registry in the Same Domain as Oracle SOA Suite

When installing Oracle Service Registry 11g in the same WebLogic Domain as Oracle SOA Suite 11g Release 11.1.1.2.0 or Release 11.1.1.3.0, you may see the following error message on the WebLogic Server console when Oracle Service Registry is starting up:

java.lang.LinkageError: loader constraint violation in interface itable
initialization:....

To work around this issue:

1. Make sure Oracle Service Registry is installed on a different Managed Server from Oracle SOA Suite.

2. Download patch 9499508 and follow the instructions in the README file included with the patch:

1. Go to My Oracle Support.

http://support.oracle.com

2. Click on the Patches & Updates tab.

3. In the Patch Search area, search for patch 9499508.

4. Download the patch.

3. Edit the setDomainEnv.sh file and, for Oracle Service Registry Server, remove fabric.jar from classpath:

if [ "${SERVER_NAME}" != "osr_server1" ] ; then
POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.fabric_11.1.1/oracle.soa.fabric.jar
${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar
${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar
${CLASSPATHSEP}${POST_CLASSPATH}"
else
POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar
${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar
${CLASSPATHSEP}${POST_CLASSPATH}"
fi

When installing Oracle Service Registry 11g in the same Weblogic Domain as Oracle SOA Suite 11g Release 11.1.1.3.0, you may see the following error message when accessing the Oracle Service Registry console:

ClassCastException
java.lang.ClassCastException:org.systinet.uddi.client.serialization.UDDIFaultSerializer

To work around this error, edit the setDomainEnv.sh file and remove oracle.soa.fabric.jar from the classpath when running the Oracle Service Registry Managed Server. To do this:

1. Make a backup of the MW_HOME/user_projects/domains/soa_domain_name/bin/setDomainEnv.sh file.

2. Edit the setDomainEnv.sh file and replace the following line:

POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.fabric_11.1.1/oracle.soa.fabric.jar
${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar
${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar
${CLASSPATHSEP}${POST_CLASSPATH}"

with the following:

if [ "${SERVER_NAME}" != "<your_osr_server_name>" ] ;
then
POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.fabric_11.1.1/oracle.soa.fabric.jar
${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar
${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar
${CLASSPATHSEP}${POST_CLASSPATH}"
else
POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar
${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar
${CLASSPATHSEP}${POST_CLASSPATH}"
fi

3. Restart the Oracle Service Registry Managed Server.

If you have multiple Oracle Service Registry Managed Servers in the domain, each Managed Server must be added to the condition. For example, if you have two Oracle Service Registry Managed Servers named WLS_OSR1 and WLS_OSR2:

case "$SERVER_NAME" in
.
'WLS_OSR1')
.
echo "Setting WLS_OSR1 CLASSPATH..."

POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar
${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar
${CLASSPATHSEP}${POST_CLASSPATH}"
exit;;

.
'WLS_OSR2')
.
echo "Setting WLS_OSR2 CLASSPATH..."

POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar
${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar
${CLASSPATHSEP}${POST_CLASSPATH}"
exit;;
.
*)
.
echo "Setting default SOA CLASSPATH..."

POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.fabric_11.1.1/oracle.soa.fabric.jar
${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar
${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar
${CLASSPATHSEP}${POST_CLASSPATH}"
exit;;
.
esac

2.1.13 Problems Installing in Thai and Turkish Locales

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.

2.1.14 Enterprise Manager Configuration Fails with Timezone Error Message

There is a problem with the timezone detection algorithm on some versions of Windows. When the database is installed on some systems that have a fresh installation of Windows, the configuration of Enterprise Manager fails with a message that indicates that an "America/Rio_Branco" timezone has been detected.

The work around is to reset the timezone to the desired value, then re-install your Oracle Fusion Middleware product.

2.2 Patching Issues and Workarounds

This section describes issue and workarounds related to Oracle Fusion Middleware product patching. It includes the following topics:

- Section 2.2.1, "Applications Will Not Start After WebLogic Server is Updated"

- Section 2.2.2, "Issues Pertaining to Patching Oracle SOA Suite"

- Section 2.2.3, "Issues Pertaining to Patching Oracle WebCenter Portal"

- Section 2.2.4, "Issues Pertaining to Patching Oracle Identity Management"

- Section 2.2.5, "Issues Pertaining to Patching System Components"

- Section 2.2.6, "Issues Pertaining to Version Numbers After Patching"

- Section 2.2.7, "Issues Pertaining to Displays During or After Patching"

- Section 2.2.8, "Warning and Error Messages Seen as a Result of Patching"

- Section 2.2.9, "Oracle Configuration Manager Fails When Patching Oracle Identity Management and Oracle Web Tier"

- Section 2.2.10, "Resolving Oracle Service Bus Object Conflicts"

- Section 2.2.11, "Manual Step for ODI-BAM Users After Installing 11.1.1.4.0 Patch Set"

2.2.1 Applications Will Not Start After WebLogic Server is Updated

After applying the latest patches to Oracle WebLogic Server, the WL_HOME/server/lib/weblogic.policy\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:MW_HOME/WLS/patch_jars/-" {
permission java.lang.RuntimePermission "oracle.*","read";
};

Replace MW_HOME with the location of your Middleware home directory.

Replace WLS with one of the following:

- patch_wls1034 for WebLogic Server version 10.3.4

- patch_wls1035 for WebLogic Server version 10.3.5

- patch_wls1036 for WebLogic Server version 10.3.6

2.2.2 Issues Pertaining to Patching Oracle SOA Suite

This section contains the following:

- Section 2.2.2.1, "Patch Set Assistant Fails When Updating the SOAINFRA Schema in SQL Server Databases"

- Section 2.2.2.2, "Exception Seen When Extending Your Existing Oracle SOA Suite Domain with Oracle Business Process Management Suite"

- Section 2.2.2.3, "Exception Seen When Undeploying any SOA Composite with Range-Based Dimension Business Indicators"

- Section 2.2.2.4, "Running Oracle Business Process Management Suite with Microsoft SQL Server 2008 Database"

- Section 2.2.2.5, "Update to Oracle SOA Suite Release 11.1.1.3.0 Does Not Remove the b2b.r1ps1 Property"

- Section 2.2.2.6, "Manual Steps for Migrating Oracle UMS and Oracle MDS"

- Section 2.2.2.7, "Monitored BPEL Processes Generate Warning Messages in Log File After Applying 11g Release 1 (11.1.1.4.0) Patch Set"

- Section 2.2.2.8, "Oracle Rules Error in Administration Server Log Files After Patching an 11g Release 1 (11.1.1.2.0) Domain"

- Section 2.2.2.9, "Incorrect Instance State of Composite Applications After Applying the Latest Patch Set"

2.2.2.1 Patch Set Assistant Fails When Updating the SOAINFRA Schema in SQL Server Databases

If you attempt to update the SOAINFRA schema in a Microsoft SQL Server database, then the Fusion Middleware Patch Set Assistant fails to complete the operation. This is a known issue with no current workaround. Contact Oracle Support or refer to My Oracle Support for more information:

http://support.oracle.com/

2.2.2.2 Exception Seen When Extending Your Existing Oracle SOA Suite Domain with Oracle Business Process Management Suite

The following intermittent exception may be seen in cases where you have upgraded your Oracle SOA Suite software to release 11.1.1.3.0 with the Patch Set Installer, and are extending your existing domain to include Oracle Business Process Management Suite:

javax.ejb.EJBTransactionRolledbackException: EJB Exception: ; nested exception
is: javax.persistence.PersistenceException: Exception
[EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException:
ORA-02292: integrity constraint (DB9128_SOAINFRA.BPM_CUBE_ROLE_FK1) violated -
child record found.
Error Code: 2292
Call: DELETE FROM BPM_CUBE_PROCESS WHERE (PROCESSID = ?)
bind => [247]
Query: DeleteObjectQuery(CubeProcess(domain:default, composite:counter_extended,
revision:1.0, name:Process, hasNametab:true));
nested exception is: javax.persistence.PersistenceException: Exception
[EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException:
ORA-02292: integrity constraint (DB9128_SOAINFRA.BPM_CUBE_ROLE_FK1) violated -
child record found

This is a harmless exception. To avoid seeing this exception, do the following:

1. Connect to your database as the SOA schema user.

2. Drop the BPM_CUBE_ROLE_FK1 constraint by executing the following:

ALTER TABLE BPM_CUBE_ROLE DROP CONSTRAINT BPM_CUBE_ROLE_FK1;

3. Recreate the BPM_CUBE_ROLE_FK1 constraint by executing the following:

ALTER TABLE BPM_CUBE_ROLE ADD CONSTRAINT BPM_CUBE_ROLE_FK1 FOREIGN KEY @
(ProcessId) REFERENCES BPM_CUBE_PROCESS(ProcessId) ON DELETE CASCADE;

4. Restart the Oracle SOA Managed Server.

2.2.2.3 Exception Seen When Undeploying any SOA Composite with Range-Based Dimension Business Indicators

The following intermittent exception may be seen in cases where you have upgraded your Oracle SOA Suite software to release 11.1.1.3.0 with the Patch Set Installer, and have undeployed SOA composites that have range-based dimension business indicators:

javax.ejb.EJBTransactionRolledbackException: EJB Exception: ; nested
exception is: javax.persistence.PersistenceException: Exception
[EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException:
ORA-02292: integrity constraint (DB9967_SOAINFRA.BPM_CUBE_NAMETAB_RANGE_FK1)
violated - child record found

Error Code: 2292
Call: DELETE FROM BPM_CUBE_NAMETAB WHERE ((EXTENSIONID = ?) AND (NAMETABID =
?))
bind => [0, 603]
Query:
DeleteObjectQuery(oracle.bpm.analytics.cube.persistence.model.CubeNametab@b7b8
2a); nested exception is: javax.persistence.PersistenceException: Exception
[EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException:
ORA-02292: integrity constraint (DB9967_SOAINFRA.BPM_CUBE_NAMETAB_RANGE_FK1)
violated - child record found

This exception is harmless and can be safely ignored. To avoid seeing this exception, do the following:

1. Connect to your database as the SOA schema user.

2. Drop the BPM_CUBE_NAMETAB_RANGE_FK1 constraint by executing the following:

ALTER TABLE BPM_CUBE_NAMETAB_RANGE  DROP CONSTRAINT BPM_CUBE_NAMETAB_RANGE_FK1;

3. Recreate the BPM_CUBE_NAMETAB_RANGE_FK1 constraint by executing the following:

ALTER TABLE BPM_CUBE_NAMETAB_RANGE ADD CONSTRAINT BPM_CUBE_NAMETAB_RANGE_FK1
FOREIGN KEY @ (ProcessId, NametabId, ExtensionId) REFERENCES
BPM_CUBE_NAMETAB (ProcessId, NametabId, ExtensionId) ON DELETE CASCADE;

4. Restart the Oracle SOA Managed Server.

2.2.2.4 Running Oracle Business Process Management Suite with Microsoft SQL Server 2008 Database

If you have patched your existing Oracle SOA Suite installation with the Patch Set Installer to include Oracle Business Process Management Suite and you are using a Microsoft SQL Server 2008 database, the following procedure is required after you have patched your software:

1. Login to the Administration Console.

2. In the "Connection Pools" tab, add the following property in the "Properties" section for the mds-owsm and mds-soa data sources:

ReportDateTimeTypes=false

2.2.2.5 Update to Oracle SOA Suite Release 11.1.1.3.0 Does Not Remove the b2b.r1ps1 Property

After you update your Release 11.1.1.2.0 software to Release 11.1.1.3.0, and login to the Oracle Enterprise Manager Console and navigate to the b2b Properties screen, the b2b.r1ps1 property (used to enable Release 11.1.1.2.0 features such as DocProvisioning and TransportCallout) is still visible. This property is removed for Release 11.1.1.3.0.

To remove this property, use the MBean browser remove property operation in Fusion Middleware Control. For more information, see "Configuring B2B Operations" in Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite.

2.2.2.6 Manual Steps for Migrating Oracle UMS and Oracle MDS

If you migrate your database schemas from Release 11.1.1.1.0 to Release 11.1.1.2.0 with the BAM Alone option:

ant master-patch-schema -DpatchMaster.Componentlist=BAM

The Oracle BAM server will not start and you will receive UMS and MDS exceptions. After executing above command, if no errors are seen in the log files and if the version in schema_version_registry is changed to 11.1.1.2.0 for Oracle BAM, then the following commands must be executed to manually migrate Oracle UMS and MDS:

ant master-patch-schema -DpatchMaster.Componentlist=MDS
ant master-patch-schema -DpatchMaster.Componentlist=UMS

Then, start the Oracle BAM server after running these commands.

2.2.2.7 Monitored BPEL Processes Generate Warning Messages in Log File After Applying 11g Release 1 (11.1.1.4.0) Patch Set

If you deployed BPEL processes that are instrumented with monitors, then Oracle BAM might generate warning messages in the SOA diagnostic log file after you apply the 11g Release 1 (11.1.1.4.0) patch set.

This is because a new business indicator data object field ("LATEST") was added for Oracle Fusion Middleware 11g Release 1 (11.1.1.4.0).

To avoid the warning message and to take advantage of the new data object field, redeploy the BPEL process after you apply the 11g Release 1 (11.1.1.4.0) patch set.

For more information about the LATEST data object field, see "Understanding Business Indicator Data Objects" in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

2.2.2.8 Oracle Rules Error in Administration Server Log Files After Patching an 11g Release 1 (11.1.1.2.0) Domain

If you are applying the latest Oracle Fusion Middleware 11g patch set to an 11g Release 1 (11.1.1.2.0) Oracle home, then you might see the following error in the Administration Server log files:

<Unresolved optional package references (in META-INF/MANIFEST.MF):
[Extension-Name: oracle.rules, referenced from:
/app/orasoa/product/soa11g/middleware/user_projects
/domains/soadev/servers/AdminServer/tmp/_WL_user/emai/xalnv4]
Make sure the referenced optional package has been deployed as a library.>

You will see this error if deployed a Oracle SOA Suite composite application to the domain previous to applying the patch set. This because, starting with Oracle Fusion Middleware 11g Release 1 (11.1.1.3.0), the Rules library (oracle.rules) must be targeted to the Administration Server, as well as to the SOA managed servers.

To avoid this message:

1. Use the Oracle WebLogic Server Administration Console to select the oracle.rules shared library and target it to the Administration Server as well as to the SOA managed servers in the domain.

2. Redeploy the application to the domain using Oracle JDeveloper 11g Release 1 (11.1.1.3.0) or later.

2.2.2.9 Incorrect Instance State of Composite Applications After Applying the Latest Patch Set

If you deployed any composite applications in Oracle SOA Suite 11g Release 1, and then you apply the latest 11g Release 1 patch set, then you might find that the instance state of some of your composite applications appears incorrect.

For example, if any of your composite applications were in a "recovery required" state before you applied the patch set, then those composite applications may be identified as completed when you view them on the Dashboard tab of the SOA Composite page in Fusion Middleware Control.

In these cases, you can ignore the "completed" indicator. The instances are actually still running and will be treated as such by other operations, such as a purge operation.

After you install the patch set, you should analyze each of these instances to determine whether they should be completed, aborted, or left to continue.

For more information about monitoring the state of SOA Composite applications, see "Monitoring SOA Composite Applications" in the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite.

2.2.3 Issues Pertaining to Patching Oracle WebCenter Portal

This section contains the following:

- Section 2.2.3.1, "Problem Using WebCenter Portal: Spaces Customizations with .jsp Pages after Installing the 11.1.1.7.0 Patch Set"

- Section 2.2.3.2, "Errors When Updating Oracle WebCenter Portal Using WLST Commands"

- Section 2.2.3.3, "Errors When Adding Tagging and Search Task Flows to Pages"

- Section 2.2.3.4, "Personalization Settings in Activity Graph Task Flows Lost When WebCenter Portal is Patched"

- Section 2.2.3.5, "Language Not Displayed in the List of Languages Offered in Spaces"

2.2.3.1 Problem Using WebCenter Portal: Spaces Customizations with .jsp Pages after Installing the 11.1.1.7.0 Patch Set

If you extended WebCenter Portal: Spaces 11g Release 1 (11.1.1.2.0) or Release 1 (11.1.1.3.0) with your own customizations, then before you upgrade, you must ensure that the customization shared library uses .jspx pages and not .jsp pages.

After you upgrade to WebCenter Portal: Spaces 11.1.1.7.0, custom site templates will not render if they use .jsp pages.

Note that if you followed the white paper Customizing Site Templates in WebCenter Spaces to develop your custom site templates, then your pages should already be .jspx pages.

2.2.3.2 Errors When Updating Oracle WebCenter Portal Using WLST Commands

If you are updating Oracle WebCenter Portal using WLST commands, you may see some error messages as described in this section. These errors can be safely ignored provided that when the command completes there is some text indicating the successful completion of the command.

When running the upgradeWebCenterDomain WLST command, you may see the following error message:

Error: addTemplate() failed. Do dumpStack() to see details.

When running the upgradeWebCenterPermissions command, you may see the following error message:

Command FAILED, Reason: JPS-04204: Cannot revoke permissions.

2.2.3.3 Errors When Adding Tagging and Search Task Flows to Pages

In your Oracle WebCenter 11.1.1.4.0 instance if you used a resource catalog based on the Default Page Template Catalog, then in your patched WebCenter Portal 11.1.1.7.0 instance you may encounter problems while adding the Tagging and Search task flows to pages. To address this issue, in your patched instance, you must edit your resource catalog, and add the Tagging and Search task flows again.

2.2.3.4 Personalization Settings in Activity Graph Task Flows Lost When WebCenter Portal is Patched

Personalization settings made for Activity Graph task flows, such as Similar Items and Recommended Connections, may be lost and task flows may revert to default settings when you patch WebCenter Portal to the latest release. You must make all the personalization settings again for your Activity Graph task flows as required.

2.2.3.5 Language Not Displayed in the List of Languages Offered in Spaces

If you extended the Spaces application to add support for a new language, you may encounter problems working with the language after you patch to WebCenter Portal 11.1.1.7.0. The language may not display in the default list of languages offered in Spaces. To resolve this issue, you must re-upload the supported-languages.xml file containing the entry for the required language.

2.2.4 Issues Pertaining to Patching Oracle Identity Management

This section contains the following:

- Section 2.2.4.1, "Access Denied When Running the oimPS1PS2upgrade Script"

- Section 2.2.4.3, "Installer Does Not Detect Existing Oracle Home"

- Section 2.2.4.4, "Uploading Third Party JAR Files to the Database"

- Section 2.2.4.5, "Updating Oracle Identity Management with LDAP Sync Enabled Generates XML Errors"

- Section 2.2.4.6, "Access Policy With Approval Does Not Work After Patch"

- Section 2.2.4.7, "OID and OVD Saved Connections Not Available After Patch From 11g Release 1 (11.1.1.2.0) or 11g Release 1 (11.1.1.3.0)"

- Section 2.2.4.8, "Harmless Error When Running the upgradeOpss() Command When Upgrading Oracle Identity Management"

- Section 2.2.4.9, "Harmless Errors in the Log Files After Patching Oracle Identity Management to 11g Release 1 (11.1.1.4.0)"

- Section 2.2.4.10, "Harmless Warning Message When Migrating Oracle Identity Federation from 11g Release 1 (11.1.1.1.0) to 11g Release 1 (11.1.1.2.0)"

- Section 2.2.4.11, "Harmless Errors Logged When Patching Oracle Identity Management 11g Release 1 (11.1.1.2.0) to 11g Release 1 (11.1.1.3.0)"

- Section 2.2.4.12, "Harmless Exception Seen When Starting Oracle Identity Management Server 11g Release 1 (11.1.1.5.0)"

2.2.4.1 Access Denied When Running the oimPS1PS2upgrade Script

If you are upgrading Oracle Identity Management and need to run the oimPS1PS2upgrade.shbat script, you must add the following to the grant() method in the JAVA_HOME\jre\lib\security\java.policy file:

// JMX Java Management eXtensions
permission javax.management.MBeanTrustPermission "register";

After making this change, stop and restart all the servers.

2.2.4.2 Installer Prompts for OID Privileged Ports Twice During the Patch Installation

If you are patching an existing Oracle Internet Directory installation to 11g Release 1 (11.1.1.7.0), you will be prompted to run the oracleRoot.sh script near the end of the patch installation, which in turn will ask for the following:

Do you want to run oidRoot.sh to configure OID for privileged ports?(yes/no)

Depending on the OID version being patched, you may be asked this question a second time. Make sure you enter the same response ("Yes" or "no") both times in order for the script to run correctly.

There is no work around for this issue.

2.2.4.3 Installer Does Not Detect Existing Oracle Home

If you are upgrading to Oracle Identity Management to 11g Release 1 (11.1.1.7.0) from 11g Release 1 (11.1.1.4.0), the installer does not detect the existing Oracle home directory for upgrade in the following environments:

- On 64-bit Windows operating systems, using the Traditional Chinese, Simplified Chinese, or Korean locales.

- On 64-bit Linux operating systems, using the Non UTF-8 locale for Japanese, Korean, Simplified Chinese and Traditional Chinese.

This is caused because the English word "Optional" gets translated in the MW_HOME/oracle_common/inventory/ContentsXML/comps.xml\oracle_common\inventory\ContentsXML\comps.xml file.

There are two work arounds for this issue:

1. Manually specify the Oracle Identity Management Oracle home directory you want to update, and then continue with the upgrade installation.

2. Find all occurrences of the translated word and replace them with the English word "Optional" in the comps.xml file and then run the installer after you are finished making the changes. The word "Optional" appears with the following two parameters in the comps.xml file:

DEP_GRP_NAME="Optional"
EXT_NAME="Optional"

Note:
The comps.xml file is an important file used by the Oracle Universal Installer so it is important that you do not make any errors while editing this file. You should make a backup copy of this file before you make any changes.

2.2.4.4 Uploading Third Party JAR Files to the Database

During the update of Oracle Identity and Access Management to 11g Release 1 (11.1.1.5.0), third party JAR files (for example, ldapbp.jar which is required for connector functionality) that are present in the file system are not uploaded to database by the upgrade process. You must manually upload these JAR files to the database using the UploadJars.shUploadJars.bat utility.

For more information, see the "Upload JAR and Resource Bundle Utilities" chapter in Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager.

2.2.4.5 Updating Oracle Identity Management with LDAP Sync Enabled Generates XML Errors

During the update of Oracle Identity Manager to from 11g Release 1 (11.1.1.3.0) to 11g Release 1 (11.1.1.5.0), the following XML error is generated if LDAP Sync is enabled on Windows operating systems:

XML-22110: (Fatal Error) Invalid StreamResult set in TransformerHandler.
oracle.iam.oimupgrade.exceptions.OIMUpgradeException: Error in writing document EventHandlers.xml

To work around this issue:

1. Edit the ORACLE_OIM_HOME\server\bin\dwps1upgrade.properties file and set the oim.ps1.seedoespolicies property to false:

oim.ps1.seedoespolicies.patch=false;

All other properties should be set to true.

2. Create a log directory (for example, logDir) in ORACLE_OIM_HOME\server\bin.

3. Go to the IAM_11.1.1.5.0_Home\server\bin directory and run the DW2PS1Upgrade.bat script.
For the following command line prompt:

##Enter your Log location directory

Specify the relative path of the log directory created in Step 2 (for example, logDir). Do not specify the absolute path to the log directory.

4. Edit the ORACLE_OIM_HOME\server\bin\dwps1upgrade.properties file again, but this time set the oim.ps1.seedoespolicies property to true and all other properties to false:

oim.ps1.seedoespolicies.patch=true;

This will allow you to upgrade the policies for Oracle Entitlements Server only.

5. Go to the IAM_11.1.1.5.0_Home\server\bin directory and run the DW2PS1Upgrade.bat script again.
For the following command line prompt:

##Enter your Log location directory

Specify the absolute path of the log directory created in Step 2 (for example, logDir) if you are using the same directory, or you can create a new directory and specify the absolute path to the new directory.

2.2.4.6 Access Policy With Approval Does Not Work After Patch

In 11g Release 1 (11.1.1.5.0), the following new policies are introduced for Oracle Entitlements Server (OES):

- SelfServiceUserManagementPolicies.xml

- UserManagementPolicies.xml

Because of this change, a request for approval is not generated when a new policy with approval is added.

To work around this issue, add the "Request Administrator" role to the "Access Policy Based Provisioning" request template:

1. Login to "Advance Console."

2. Go to Request Templates on the Configuration tab.

3. Search for and open the "Access Policy Based Provisioning" request template.

4. Go to the Template User Roles tab on the Template Details page.

5. From the left pane in "Available Roles," search for and assign the "Request Administrators" role.
The assigned role will appear in the right pane under "Selected Roles."

6. Save the request template.

2.2.4.7 OID and OVD Saved Connections Not Available After Patch From 11g Release 1 (11.1.1.2.0) or 11g Release 1 (11.1.1.3.0)

If you are patching Oracle Internet Directory (OID) or Oracle Virtual Directory (OVD) from 11g Release 1 (11.1.1.2.0) or 11g Release 1 (11.1.1.3.0) to 11g Release 1 (11.1.1.4.0) or later, your saved connections in the previous releases will not be available after the patch.

If you are patching from 11g Release 1 (11.1.1.4.0) to any later release, then your saved connections in OID and OVD will be available.

There is no work around for this issue.

2.2.4.8 Harmless Error When Running the upgradeOpss() Command When Upgrading Oracle Identity Management

During the upgrade of Oracle Identity Manager 11g Release 1 (11.1.1.3.0) to 11g Release 1 (11.1.1.5.0), you are asked to run the upgradeOpss WLST (online) command to update Oracle Platform Security Services (OPSS).

The following message will be visible on the console when you run the upgradeOpss command:

WLS ManagedService is not up running. Fall back to use system properties for configuration.
date_and_time oracle.security.jps.internal.tools.utility.destination.apibased.JpsDstPolicy <init>
WARNING: No identity store associate with policy store found.
Upgrade of jps configuration and security stores is done.

This message is harmless and can be safely ignored.

2.2.4.9 Harmless Errors in the Log Files After Patching Oracle Identity Management to 11g Release 1 (11.1.1.4.0)

After patching and configuring Oracle Identity Management to 11g Release 1 (11.1.1.4.0), the following errors are seen in the wls_oif1-diagnostics.log file when Single Sign-On is used for Oracle Identity Federation:

[2010-08-05T13:05:30.754-07:00] [wls_oif1] [INCIDENT_ERROR] [FED-10174]
[oracle.security.fed.model.config.Configuration] [tid:
[ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default
(self-tuning)'] [userId: <anonymous>] [ecid:
42ef6c66fe18f3ad:291f353a:12a43da27c1:-8000-0000000000000021,0] [APP:
OIF#11.1.1.2.0] [arg: certvalidationtimeout] Property was not found:
certvalidationtimeout.
.
[2010-08-05T13:05:37.174-07:00] [wls_oif1] [INCIDENT_ERROR] [FED-10174]
[oracle.security.fed.model.config.Configuration] [tid:
[ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default
(self-tuning)'] [userId: <anonymous>] [ecid:
42ef6c66fe18f3ad:291f353a:12a43da27c1:-8000-0000000000000021,0] [APP:
OIF#11.1.1.2.0] [arg: schemavalidationenabled] Property was not found:
schemavalidationenabled

[2010-08-06T17:09:23.861-07:00] [wls_oif1] [INCIDENT_ERROR] [FED-10174]
[oracle.security.fed.model.config.Configuration] [tid:
[ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default
(self-tuning)'] [userId: <anonymous>] [ecid:
f6d9b81289e40cee:42d4f595:12a49b7af7a:-8000-000000000000086f,0] [APP:
OIF#11.1.1.2.0] [arg: certpathvalidationenabled] Property was not found:
certpathvalidationenabled.

[2010-08-06T17:11:27.173-07:00] [wls_oif1] [INCIDENT_ERROR] [FED-10174]
[oracle.security.fed.model.config.Configuration] [tid:
[ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default
(self-tuning)'] [userId: <anonymous>] [ecid:
f6d9b81289e40cee:42d4f595:12a49b7af7a:-8000-00000000000009a0,0] [APP:
OIF#11.1.1.2.0] [arg: httpheaderattrcollector] Property was not found:
httpheaderattrcollector.

There errors are harmless and can be safely ignored.

To avoid seeing these errors, run the oif-upgrade-11.1.1.2.0-11.1.1.4.0.py script after you have patched your software to 11.1.1.4.0 as described in "Updating Configuration Properties in Oracle Identity Federation" in the Oracle Fusion Middleware Patching Guide.

2.2.4.10 Harmless Warning Message When Migrating Oracle Identity Federation from 11g Release 1 (11.1.1.1.0) to 11g Release 1 (11.1.1.2.0)

When you are using the Patch Assistant migration scripts to migrate Oracle Identity Federation from 11g Release 1 (11.1.1.1.0) to 11g Release 1 (11.1.1.2.0), you may see the following error message:

WLSTException: Error occured while performing addHelpCommandGroup : Error
getting resource bundle: : Can't find bundle for base name
oifWLSTResourceBundle, locale en_US

This message is harmless and can be safely ignored.

2.2.4.11 Harmless Errors Logged When Patching Oracle Identity Management 11g Release 1 (11.1.1.2.0) to 11g Release 1 (11.1.1.3.0)

You may see some of the following error messages in installation log files after patching an Oracle Identity Management 11g Release 1 (11.1.1.2.0) installation to 11g Release 1 (11.1.1.3.0):

External name..INVALID_ORACLE_DIRECTORY_MSG_STRING

In doFinish method checking for inventory lock...InstallProgressPage

Next page is a progress page and the inventory lock is false

/bin/chmod: changing permissions of ORACLE_HOME/install/root.log': Operation not permitted

/bin/chmod: changing permissions of ORACLE_HOME/bin/nmhs': Operation not permitted

/bin/chmod: changing permissions of ORACLE_HOME/bin/nmb': Operation not permitted

/bin/chmod: changing permissions of ORACLE_HOME/bin/nmo': Operation not permitted

inventoryLocation: /scratch/aime1/oraInventory

Mode:init

Such messages can be ignored.

2.2.4.12 Harmless Exception Seen When Starting Oracle Identity Management Server 11g Release 1 (11.1.1.5.0)

After updating Oracle Identity Management to 11g Release 1 (11.1.1.5.0), the following exception may be seen when starting Oracle Identity Management Server:

java.lang.ClassNotFoundException: ADP ClassLoader failed to load:com.thortech.xl.schedule.tasks.tcTskScheduledProvision

This error is harmless and can be safely ignored.

2.2.5 Issues Pertaining to Patching System Components

This section contains the following:

- Section 2.2.5.1, "Granting Access to Network-Related Packages for the Oracle Portal Schema"

- Section 2.2.5.2, "Redeploy System Components to Ensure Proper Deinstallation"

2.2.5.1 Granting Access to Network-Related Packages for the Oracle Portal Schema

While running the Patch Set Assistant to upgrade the schema for Oracle Portal 11g Release 1 (11.1.1.4.0) in an environment where Oracle Single Sign-On 10.1.4.3 is running against Oracle Internet Directory 11g and Oracle Database 11.2.0.2, the following exception is encountered:

ORA-24247: network access denied by access control list (ACL)

To address this issue when executing network-related packages, access must be granted to the user using these packages. You must create the ACL for the ORASSO schema user, and assign it to the OID host. Then, you must run the wdbigra.sql script, which gives the required grants to Oracle Portal schema.

1. Grant the ACL for the PORTAL schema user and assign it for the OID host.
Connect as sys as sysdba and assign the ACL as in the example below, where examplehost.exampledomain.com is the OID hostname and the DEV_PORTAL is the Oracle Portal schema specified for the installation:

DECLARE
acl_path VARCHAR2(4000);

BEGIN

SELECT acl INTO acl_path FROM dba_network_acls
WHERE host = 'examplehost.exampledomain.com' AND lower_port IS NULL AND upper_port IS NULL;
dbms_output.put_line('acl_path = '|| acl_path);
dbms_output.put_line('ACL already Exists. Checks for Privilege and add the Privilege');
IF DBMS_NETWORK_ACL_ADMIN.check_privilege(acl_path,'DEV_PORTAL','connect') IS NULL THEN
DBMS_NETWORK_ACL_ADMIN.add_privilege (
acl => acl_path,
principal => 'DEV_PORTAL',
is_grant => TRUE,
privilege => 'connect');
END IF;
END;
/
COMMIT;

When no ACL has been assigned for the OID host, create the ACL:

EXCEPTION
WHEN no_data_found THEN

DBMS_NETWORK_ACL_ADMIN.create_acl (
acl => 'sso_oid.xml',
description => 'ACL for SSO to connect to OID',
principal => 'ORASSO',
is_grant => TRUE,
privilege => 'connect');

DBMS_NETWORK_ACL_ADMIN.assign_acl (
acl => 'sso_oid.xml',
host => 'examplehost.exampledomain.com');
END;
/
COMMIT;

Use the following SQL command to verify that the ACL was created:

select * from dba_network_acls;

2. Modify the values of the host and schema in the wdbigra.sql file, located in the ORACLE_HOME/upgrade/portal/admin/plsql/wwv\upgrade\portal\admin\plsql\wwv directory.
Change the following:

host varchar2(1)        := '*';
schema varchar2(2000)   := upper('&&1');

To the following:

host varchar2(1)        := '&OID_HOST';
schema varchar2(2000)   := upper('&PORTAL_SCHEMA');

3. Run the wdbigra.sql script to give the grants to the Oracle Portal schema.
The script will prompt you for the following:

- The value for the oid_host.
Specify the host where Oracle Internet Directory is running (for example, examplehost.exampledomain.com).

- The value for the portal_schema.
Specify the prefix and schema name (for example, DEV_PORTAL).

2.2.5.2 Redeploy System Components to Ensure Proper Deinstallation

After you have patched your system component software (Oracle Portal, Forms, Reports and Discoverer, Oracle Identity Management, or Oracle Web Tier) and started all services, you must manually redeploy your system components if you are extending your existing domain. To do so, follow the instructions to redeploy in the "Upgrading System Components" section of the Oracle Fusion Middleware Patching Guide.

If you do not redeploy your system components, you will encounter problems when you attempt to remove them.

2.2.5.3 Setting Execute Permissions for emctl When Migrating System Components

When you migrate any 11g Release 1 (11.1.1.1.0) system component to 11g Release 1 (11.1.1.2.0), the following error message can be seen on the console window:

Process (index=1,uid=1270434032,pid=0)
Executable file does not have execute permission.

INSTANCE_HOME/EMAGENT/EMAGENT/bin/emctl
failed to start a managed process after the maximum retry limit
Executable file does not have execute permission.

The work around is to manually change the permissions of the emctl executable. For example:

chmod +x INSTANCE_HOME/EMAGENT/EMAGENT/bin/emctl

After changing the permissions, restart all the opmnctl processes.

2.2.6 Issues Pertaining to Version Numbers After Patching

This section contains the following:

- Section 2.2.6.1, "Oracle SOA Suite Tasks Not Visible in Firefox Browser After Upgrade"

- Section 2.2.6.2, "Some Applications Show Old Version Number After Patching"

- Section 2.2.6.3, "MDS Schema Version Number is Incorrect"

- Section 2.2.6.4, "Oracle BI Components Show Incorrect Version Number After Patching"

- Section 2.2.6.5, "Adding the Version Number for the odi-sdk-ws Application in config.xml"

2.2.6.1 Oracle SOA Suite Tasks Not Visible in Firefox Browser After Upgrade

If you are upgrading Oracle SOA Suite to 11g Release 1 (11.1.1.7.0) from any previous release, not all tasks may be visible in Firefox browser after the upgrade is complete.

To work around this issue, refresh your browser's cache to see all tasks.

2.2.6.2 Some Applications Show Old Version Number After Patching

After you patch your Oracle Fusion Middleware environment, some applications still show the version number from previous releases. For example, after you patch Oracle WebLogic Server 10.3.4 to the latest release, the version number is still shown as 10.3.4.

There is no work around for this issue.

2.2.6.3 MDS Schema Version Number is Incorrect

If you are running Fusion Middleware products that use the Metadata Services schema (MDS) and your Fusion Middleware products are older than 11g Release 1 (11.1.1.4.0), the schema version number for the MDS schema in Enterprise Manager will be the previous release number, even if you have updated the MDS schema to 11g Release 1 (11.1.1.4.0).

In order for the MDS schema version number to appear correctly, both the schema and the Fusion Middleware product software must be up to date with the most recent version.

2.2.6.4 Oracle BI Components Show Incorrect Version Number After Patching

After you patch your existing Oracle Business Intelligence (BI) software to 11g Release 1 (11.1.1.4.0), some Oracle BI components (for example, Oracle BI Publisher or Oracle RTD) will still show the version number from your previous release when viewed using Oracle Enterprise Manager.

There is no work around for this issue.

2.2.6.5 Adding the Version Number for the odi-sdk-ws Application in config.xml

In 11g Release 1 (11.1.1.6.0), the odi-sdk-ws application was updated to introduce a version number. If you are upgrading the odi-sdk-ws application to 11g Release 1 (11.1.1.6.0) from any previous release, this version number must be added to the config.xml file prior to starting the Administration server or Managed Servers in the domain.

To do this:

1. Edit the DOMAIN_HOME/config/config.xml\config\config.xml file.

2. Change the following line:

<name>odi-sdk-ws</name>

To add a version number, as follows:

<name>odi-sdk-ws#11.1.1.6.0.1</name>

3. Start or restart the Administration Server and Managed Servers in the domain.

2.2.7 Issues Pertaining to Displays During or After Patching

This section contains the following:

- Section 2.2.7.1, "Pages in Oracle Enterprise Manager and Oracle Directory Services Manager do not Display Correctly"

2.2.7.1 Pages in Oracle Enterprise Manager and Oracle Directory Services Manager do not Display Correctly

After upgrading to 11g Release 1 (11.1.1.7.0), if you encounter problems with pages in Oracle Enterprise Manager (EM) or Oracle Directory Services Manager (ODSM) not being displayed correctly, do the following before starting all the servers in the domain:

1. Add the value -XX:-UseSSE42Intrinsics to the DOMAIN_HOME/bin/setDomainEnv.sh\bin\setDomainEnv.cmd file as follows:
Find the following section of code:

if [ "${JAVA_VENDOR}" = "Sun" ] ; then
MEM_ARGS="${MEM_ARGS} ${MEM_DEV_ARGS} ${MEM_MAX_PERM_SIZE}"
export MEM_ARGS
fi

if [ "${JAVA_VENDOR}" = "HP" ] ; then
MEM_ARGS="${MEM_ARGS} ${MEM_MAX_PERM_SIZE}"
export MEM_ARGS
fi

if [ "${JAVA_VENDOR}" = "Apple" ] ; then
MEM_ARGS="${MEM_ARGS} ${MEM_MAX_PERM_SIZE}"
export MEM_ARGS
fi

And change it to:

if [ "${JAVA_VENDOR}" = "Sun" ] ; then
MEM_ARGS="${MEM_ARGS} ${MEM_DEV_ARGS} ${MEM_MAX_PERM_SIZE} -XX:-UseSSE42Intrinsics"
export MEM_ARGS
fi

if [ "${JAVA_VENDOR}" = "HP" ] ; then
MEM_ARGS="${MEM_ARGS} ${MEM_MAX_PERM_SIZE} -XX:-UseSSE42Intrinsics"
export MEM_ARGS
fi

if [ "${JAVA_VENDOR}" = "Apple" ] ; then
MEM_ARGS="${MEM_ARGS} ${MEM_MAX_PERM_SIZE} -XX:-UseSSE42Intrinsics"
export MEM_ARGS
fi

2. For Oracle EM, remove the .css file from the following directory:
On UNIX operating systems:

DOMAIN_HOME/servers/AdminServer/tmp/_WL_user/em/random_dir/public/adf/styles/cache

On Windows operating systems:

DOMAIN_HOME\servers\AdminServer\tmp\_WL_user\em\random_dir\public\adf\styles\cache

3. For ODSM, remove the .css file from the following directory:
On UNIX operating systems:

DOMAIN_HOME/servers/wls_ods1/tmp/_WL_user/odsm_release/random_dir/public/adf/styles/cache

On Windows operating systems:

DOMAIN_HOME\servers\wls_ods1\tmp\_WL_user\odsm_release\random_dir\public\adf\styles\cache

4. Clear your browser cache to remove any browser clients that visited the sites using the .css file you just removed.

5. Start or restart all the servers in the domain.

2.2.7.2 Patch Set Assistant Does Not Display Multi-Byte Characters on Oracle Linux 6

On Oracle Linux 6 operating systems, the Patch Set Assistant does not display multi-byte characters (for example, Japanese, Korean, and both simplified and traditional Chinese).

To work around this issue:

1. Go to the Oracle Common home directory.

2. Save the jdk directory to a temporary jdk directory. For example:

mv jdk jdk_save

3. Create a link to the jdk1.7.0 directory on your system. For example:

ln -s /home/Oracle/Products/jdk/jdk1.7.0 jdk

4. Set the following environment variables (for example, if you wanted to display Japanese characters):

setenv LANG ja_JP
setenv LC_ALL ja_JP

5. Run the Patch Set Assistant from the ORACLE_HOME/bin directory.

It is recommended that you use this work around only for the duration needed to run the Patch Set Assistant; you should restore your environment to their original settings after you are finished.

2.2.7.3 Patch Set Assistant Does Not Display Multi-Byte Characters on Oracle Linux 6

On Oracle Linux 6 operating systems, the Patch Set Assistant does not display multi-byte characters (for example, Japanese, Korean, and both simplified and traditional Chinese).

To work around this issue:

1. Go to the Oracle Common home directory.

2. Save the jdk directory to a temporary jdk directory. For example:

mv jdk jdk_save

3. Create a link to the jdk1.7.0 directory on your system. For example:

ln -s /home/Oracle/Products/jdk/jdk1.7.0 jdk

4. Set the following environment variables (for example, if you wanted to display Japanese characters):

setenv LANG ja_JP
setenv LC_ALL ja_JP

5. Run the Patch Set Assistant from the ORACLE_HOME/bin directory.

It is recommended that you use this work around only for the duration needed to run the Patch Set Assistant; you should restore your environment to their original settings after you are finished.

2.2.8 Warning and Error Messages Seen as a Result of Patching

This section contains the following:

- Section 2.2.8.1, "Harmless Warnings When Running upgradeOpss()"

- Section 2.2.8.2, "Harmless Warning Message in Log File When Patching Multiple Products to the Same Version"

- Section 2.2.8.3, "Error When Accessing the Oracle Portal Home Page"

- Section 2.2.8.4, "Applications Generate javax.xml.bind.JAXBException Runtime Errors After Installing 11g Release 1 (11.1.1.4.0) Patch Set"

2.2.8.1 Harmless Warnings When Running upgradeOpss()

When running the upgradeOpss() WLST command to upgrade configurations and stores to 11g Release 1 (11.1.1.4.0), the following error messages may be seen:

oracle.security.jps.internal.tools.utility.destination.apibased.JpsDstPolicy
migrateData
WARNING: cannot migrate a global grant. Reason
oracle.security.jps.service.policystore.PolicyStoreException: Found 2 permissions
in the store matching: ([PermissionEntry:class=java.util.PropertyPermission
target=weblogic.Name resourceType=null actions=read,PERMISSION, name=null,
uniqueName=null, guid=null]
[jaznGranteeDn=orclguid=AC171BF0E72711DEBF9CCF0B93FB22A1,cn=Grantees,
cn=JAASPolicy,cn=systempolicy,cn=webcenter,cn=JPSContext,cn=jpsroot_webcenter_IR14_prod}),
[PermissionEntry: class=java.util.PropertyPermission target=weblogic.Name
resourceType=null actions=read,PERMISSION, name=8228FD8036F711DEAF24DB7D80B2D07C,
uniqueName=orclguid=8228FD8036F711DEAF24DB7D80B2D07C,cn=Permissions,cn=JAASPolicy,
cn=systempolicy,cn=webcenter,cn=JPSContext,cn=jpsroot_webcenter_IR14_prod,
guid=8228FD8036F711DEAF24DB7D80B2D07C]
[jaznGranteeDn=orclguid=822505e036f711deaf24db7d80b2d07c,cn=grantees,cn=jaas
policy,cn=systempolicy,cn=webcenter,cn=jpscontext,cn=jpsroot_webcenter_ir14_prod}1
[PermissionEntry: class=java.util.PropertyPermission target=weblogic.Name
resourceType=null actions=read,PERMISSION, name=8228FD8036F711DEAF24DB7D80B2D07C,
uniqueName=orclguid=8228FD8036F711DEAF24DB7D80B2D07C,cn=Permissions,cn=JAASPolicy,
cn=systempolicy,cn=webcenter,cn=JPSContext,cn=jpsroot_webcenter_IR14_prod,
guid=8228FD8036F711DEAF24DB7D80B2D07C]
[jaznGranteeDn=orclguid=822505e036f711deaf24db7d80b2d07c,cn=grantees,cn=jaaspolicy
,cn=systempolicy,cn=webcenter,cn=jpscontext,cn=jpsroot_webcenter_ir14_prod}
[PermissionEntry: class=java.util.PropertyPermission target=weblogic.Name
resourceType=null actions=read,PERMISSION, name=AC198CF0E72711DEBF9CCF0B93FB22A1,
uniqueName=orclguid=AC198CF0E72711DEBF9CCF0B93FB22A1,cn=Permissions,cn=JAASPolicy,
cn=systempolicy,cn=webcenter,cn=JPSContext,cn=jpsroot_webcenter_IR14_prod, guid=AC198CF0E72711DEBF9CCF0B93FB22A1]
[jaznGranteeDn=orclguid=822505e036f711deaf24db7d80b2d07c,cn=grantees,cn=jaaspolicy
,cn=systempolicy,cn=webcenter,cn=jpscontext,cn=jpsroot_webcenter_ir14_prod}
[jaznGranteeDn=orclguid=ac171bf0e72711debf9ccf0b93fb22a1,cn=grantees,cn=jaaspolicy
,cn=systempolicy,cn=webcenter,cn=jpscontext,cn=jpsroot_webcenter_ir14_prod}2
[PermissionEntry: class=java.util.PropertyPermission target=weblogic.Name
resourceType=null actions=read,PERMISSION, name=AC198CF0E72711DEBF9CCF0B93FB22A1,
uniqueName=orclguid=AC198CF0E72711DEBF9CCF0B93FB22A1,cn=Permissions,cn=JAASPolicy,
cn=systempolicy,cn=webcenter,cn=JPSContext,cn=jpsroot_webcenter_IR14_prod,
guid=AC198CF0E72711DEBF9CCF0B93FB22A1]
[jaznGranteeDn=orclguid=822505e036f711deaf24db7d80b2d07c,cn=grantees,cn=jaaspolicy
,cn=systempolicy,cn=webcenter,cn=jpscontext,cn=jpsroot_webcenter_ir14_
prod}[jaznGranteeDn=orclguid=ac171bf0e72711debf9ccf0b93fb22a1,cn=grantees,cn=jaas
policy,cn=systempolicy,cn=webcenter,cn=jpscontext,cn=jpsroot_webcenter_ir14_prod}

These messages are harmless and can be safely ignored.

2.2.8.2 Harmless Warning Message in Log File When Patching Multiple Products to the Same Version

In a scenario where you have a product that is already patched to version 11g Release 1 (11.1.1.3.0) in a Middleware home, and then you attempt to patch a second product to the same version in the same Middleware home, a warning message similar to the following will appear in the installtimestamp.out file:

Attempting to install 1 patches
Mar 3, 2010 1:00:07 PM [THREAD: Thread-1]
com.bea.cie.paf.internal.attach.PatchManagerImpl install
WARNING: Warning:  Patch already installed: PBY8

Patch installation success
Patch installation success
Success..
[SOARootService.getRootActions] autoPortsDetect =null
[SOARootService.getRootActions] privilegedPorts =null

This warning message can be safely ignored.

2.2.8.3 Error When Accessing the Oracle Portal Home Page

If you are upgrading to Oracle Portal 11g Release 1 (11.1.1.6.) from any previous release, the following error message is displayed in the browser when accessing the Oracle Portal home page:

XML Parsing Error: syntax error
Location: http://exampleserver.exampledomain:port/portal/pls/portal/dev_portal.home
Line Number 1, Column 1:An error occurred while processing the request. Try refreshing your browser. If the problem persists contact the site administrator
^

This occurs because the Web Cache invalidation password stored in Web Cache and the password stored in the Portal repository are not the same.

To resolve this issue:

1. Reset the Oracle Web Cache invalidator password in the Administration repository:

1. Log in to Enterprise Manager in the domain where Web Cache is running:

http://administration_server_host:administration_server_port/em

2. From the navigation section on the left, open "Web Tier" then click on the Web Cache instance name.

3. Find the drop-down menu on the right-hand side of the page under the Web Cache instance name, then select Administration > Password from the menu.

4. Specify a new invalidation password.

5. Restart Oracle Web Cache.

2. Reset the Oracle Web Cache invalidator password in the Oracle Portal repository:

1. Log in to Enterprise Manager in the domain where Oracle Portal is running:

http://administration_server_host:administration_server_port/em

2. From the navigation section on the left, open "Portal" then click on the Oracle Portal Managed Server name.

3. Find the drop-down menu on the right-hand side of the page under the Oracle Portal instance name, then select Settings > Wire Configuration from the menu.

4. Specify a new invalidation password - the same password you specified in the Administration repository.

Note:
the "Invalidation User" user name should be same as the user name used on the Oracle Web Cache side.

5. Click Apply.
There is a known issue at this point - refer to "Resolving JDBC Errors in Oracle Reports and Oracle Portal" in the Oracle Fusion Middleware Patching Guide for more information.

6. Delete the Oracle Portal File Cache in the ORACLE_INSTANCE/portal/cache\portal\/cache directory.

7. Restart Oracle Web Cache and the Oracle Portal Managed Server.

2.2.8.4 Applications Generate javax.xml.bind.JAXBException Runtime Errors After Installing 11g Release 1 (11.1.1.4.0) Patch Set

If any of the applications you deployed on Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) or 11g Release 1 (11.1.1.3.0) include EclipseLink-JAXB classes that have no-arg constructors missing, then after you install 11g Release 1 (11.1.1.4.0), the application might generate the following exceptions during runtime:

javax.xml.bind.JAXBException

To avoid this error:

1. Modify the classes and add default no-arg constructors where necessary.

2. Compile and redeploy your project to the newly patched Oracle Fusion Middleware 11g Release 1 (11.1.1.4.0) domain.

Below is an example of a typical no-arg constructor:

public class PriceQuote implements Serializable
{
// Make sure you have constructor with no arguments
public PriceQuote() }
}
}

2.2.9 Oracle Configuration Manager Fails When Patching Oracle Identity Management and Oracle Web Tier

If you are upgrading Oracle Identity Management or Oracle Web Tier to 11g Release 1 (11.1.1.7.0) from any release prior to and not including 11g Release 1 (11.1.1.6.0), and you did not previously configure Oracle Configuration Manager, then Oracle Configuration Manager will fail if you decide to configure it in 11g Release 1 (11.1.1.7.0).

To work around this issue, you can do the following prior to running the 11g Release 1 (11.1.1.7.0) configuration wizard:

1. Go to the ORACLE_HOME/ccr/bin directory.

2. Run the following commands:

setupCCR
configCCR
emCCR collect
emCCR status

You can also do the following if you choose to skip the Oracle Configuration Manager configuration when you initially run the 11g Release 1 (11.1.1.7.0) configuration wizard but then choose to configure it later:

1. Go to the ORACLE_HOME/ccr/bin directory.

2. Set the ORACLE_CONFIG_HOME environment variable to your Instance home directory.

3. Run the following commands:

setupCCR
configCCR
emCCR collect
emCCR status

2.2.10 Resolving Oracle Service Bus Object Conflicts

After patching Oracle Service Bus, it is possible that some older objects in the server cache could conflict with the newer version of Oracle Service Bus objects. To clear the cache and prevent these conflicts, delete the DOMAIN_HOME/tmp/cache/stage folder.

You can delete this folder either prior to patching, or after patching. If you do this after patching your software, you must remember to shut down and restart all the servers.

2.2.11 Manual Step for ODI-BAM Users After Installing 11.1.1.4.0 Patch Set

If you are integrating Oracle Data Integrator (ODI) with Oracle Business Activity Monitoring, you should import a new version of the following knowledge module after you install the Oracle Fusion Middleware 11g Release 1 (11.1.1.4.0) patch set:

BAM_ORACLE_HOME/bam/ODI/knowledge modules/KM_RKM Oracle BAM.xml

For more information, see "Importing and Replacing Knowledge Modules" in the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

This new module includes bugs fixes and improvements made for the Oracle Fusion Middleware 11g Release 1 (11.1.1.4.0).

2.3 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

- Section 2.3.1, "Issues Pertaining to Oracle SOA Suite Configuration"

- Section 2.3.2, "Issues Pertaining to Oracle Identity Management Configuration"

- Section 2.3.3, "Issues Pertaining to Oracle Identity and Access Management Configuration"

- Section 2.3.4, "Issues Pertaining to the Configuration Wizard"

- Section 2.3.5, "Issues Pertaining to the Repository Creation Utility (RCU)"

- Section 2.3.6, "Issues Pertaining to Packing and Unpacking a Domain"

- Section 2.3.7, "Issues Pertaining to Cluster Configuration"

- Section 2.3.8, "Discoverer URL is not Properly Displayed When Accessed Through SSL"

- Section 2.3.9, "Cleaning up the JDeveloper Directories for a Failed Deployment on Windows"

- Section 2.3.11, "Oracle WebCenter Portal wc-post-install.py Script Not Supported for Oracle RAC Datasources"

- Section 2.3.12, "FileNotFoundException When Cloning on Windows"

- Section 2.3.13, "Changing the Listen Address of a Managed Server"

- Section 2.3.14, "Domain Extension Overwrites JDBC Data Source Name"

- Section 2.3.15, "Rerouting to Original URL After SSO Authentication in Firefox and Safari Browsers"

- Section 2.3.16, "Deleting the Browser Cache in Browsers"

2.3.1 Issues Pertaining to Oracle SOA Suite Configuration

This section contains the following:

- Section 2.3.1.1, "Mediator Component Fails With Windows Server 2008 R2 Enterprise and JRockit"

- Section 2.3.1.2, "SOAINFRA Schema Contains Invalid Objects in 11g Release 1 (11.1.1.6.0)"

- Section 2.3.1.3, "Harmless Exception Seen for Oracle SOA Suite with WebSphere Application Server"

- Section 2, "Installation, Patching, and Configuration"

2.3.1.1 Mediator Component Fails With Windows Server 2008 R2 Enterprise and JRockit

The Mediator component fails to work when Windows Server 2008 R2 Enterprise is used with following version of the JRockit JDK:

Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
Oracle JRockit(R) (build
R28.2.0-79-146777-1.6.0_29-20111005-1808-windows-x86_64, compiled mode)

To work around this issue, use the Sun JDK by changing the JAVA_HOME in the setDomainEnv.cmd file to point to the Sun JDK Location and setting JAVA_VENDOR=Sun while starting the Administration Server and Managed Servers.

2.3.1.2 SOAINFRA Schema Contains Invalid Objects in 11g Release 1 (11.1.1.6.0)

When the 11g Release 1 (11.1.1.6.0) version of the prefix_SOAINFRA schema is created either by running RCU or the Patch Set Assistant, there are still some invalid objects that exist within the SOA schema.

To work around this issue, compile the prefix_SOAINFRA schema. For example, if the SOA schema user on your system is DEV_SOAINFRA:

exec dbms_utility.compile_schema('DEV_SOAINFRA')

If you choose not to run this command to make the objects valid, the objects will also become valid once they are accessed during runtime.

2.3.1.3 Harmless Exception Seen for Oracle SOA Suite with WebSphere Application Server

When running Oracle SOA Suite on IBM WebSphere application server, the following exception is seen after logging in to Fusion Middleware Control, expanding Application Deployments on the left side and then clicking on any of the applications under it:

[date_and_time] 0000003f OHWHelpProvid E   unable to create global
configuration
[date_and_time] 00000044 OHWHelpProvid E   critical error in OHW
configuration

oracle.help.web.config.parser.ConfigParseException: error finding
configuration file at:
at oracle.help.web.config.parser.OHWParser._openConnection(Unknown
Source)
at oracle.help.web.config.parser.OHWParser.getGlobalConfiguration(Unknown Source)
at oracle.help.web.rich.helpProvider.OHWHelpProvider.getHelpTopic(Unknown Source)
.
.
.

This exception is harmless and can be safely ignored.

2.3.1.4 Oracle SOA Suite Administration Server Fails to Start With Sun JDK on Windows XP 2002

The Administration Server in Oracle SOA Suite does not start with using a Sun JDK on a Windows XP 2002 server with Service Pack 3.

To work around this issue, go to the DOMAIN_HOME\bin directory and set DEFAULT_MEM_ARGS value in setSOADomainEnv.cmd from:

-Xms512m -Xmx1024m

to

-Xms256m -Xmx512m

2.3.2 Issues Pertaining to Oracle Identity Management Configuration

This section contains information pertaining to Oracle Identity Management 11g Release 1 (11.1.1.7.0) configuration:

Note:
For 11g Release 1 (11.1.1.6.0) configuration release notes, refer to the following links:

- Oracle Fusion Middleware Release Notes 11g Release 1 (11.1.1) for Linux x86

- Oracle Fusion Middleware Release Notes 11g Release 1 (11.1.1) for Microsoft Windows (32-Bit)

- Section 2.3.2.1, "Oracle Internet Directory Server Does Not Listen on SSL Port"

- Section 2.3.2.2, "Metrics for Oracle Identity Management Components may not be Correctly Displayed in Enterprise Manager"

- Section 2.3.2.3, "Configuring Oracle Identity Management When WebLogic Node Manager is Running"

- Section 2.3.2.4, "Configuring Oracle Internet Directory with Oracle Data Vault"

- Section 2.3.2.5, "OIDMON Does Not Start After Configuring Oracle Internet Directory on Windows"

- Section 2.3.2.6, "Password Requirements for Oracle Internet Directory Administrator"

- Section 2.3.2.7, "Harmless Error Message When Configuring Oracle Identity Federation"

2.3.2.1 Oracle Internet Directory Server Does Not Listen on SSL Port

If the machine on which Oracle Internet Directory is installed is not configured as a dual stack (IPv4/IPv6) host and the Oracle Internet Directory server is configured to listen on privileged ports, then the Oracle Internet Directory server does not listen on SSL ports.

To work around this issue, do one of the following:

- Enable IPv6 on the machine.

- If pure IPv4/IPv6 addresses are needed, add host=ipv4_ip_address or host=ipv6_ip_address for oidmon parameters in the INSTANCE_HOME/config/OPMN/opmn/opmn.xml file. For example:

<data id="start-cmdline-opts" value="connect=$DB_CONNECT_STR opmnuid=true
host=ipv4_or_ipv6_ip_address start"/>
<data id="stop-cmdline-opts" value="connect=$DB_CONNECT_STR opmnuid=true
host=ipv4_or_ipv6_ip_address stop"/>

2.3.2.2 Metrics for Oracle Identity Management Components may not be Correctly Displayed in Enterprise Manager

When Oracle Identity Management servers are configured on IPv4/IPv6 dual-stack hosts in 11g Release 1 (11.1.1.7.0), the following problems may occur in Enterprise Manager:

- Metrics for Oracle Identity Management components may not be displayed correctly.

- Links to Oracle Directory Services Manager (ODSM) may not work.

To work around this issue, add an alias for the IPv6 address in the /etc/hosts file on your system:

IPv6_host_address host.domain host

For example:

fdc4:82c2:9c80:d47a::3:58 examplehost.exampledomain.com examplehost

2.3.2.3 Configuring Oracle Identity Management When WebLogic Node Manager is Running

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:

1. Set the StartScriptEnabled parameter to true.

2. Stop, then restart the Node Manager utility.

3. 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.

2.3.2.4 Configuring Oracle Internet Directory with Oracle Data Vault

If you choose to configure Oracle Internet Directory (OID) with Oracle Data Vault:

1. Apply patch 8897382 (see the README file in the patch for instructions).

2. In the ORACLE_HOME/ldap/datasecurity/dbv_oid_command_rules.sql\ldap\datasecurity\dbv_oid_command_rules.sql 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;/

3. Change the following line:

,object_owner => 'ODS'

to:

,object_owner => '%'

2.3.2.5 OIDMON Does Not Start After Configuring Oracle Internet Directory on Windows

On Windows platforms, when configuring Oracle Internet Directory using either the installer's Install and Configure option or the Configuration Wizard, OIDMON will not start if the total length of all environment variables, such as ORACLE_HOME, JAVA_HOME, PATH, and so on, exceeds 4,000 characters.

If you see an oidmon.exe application error message while configuring Oracle Internet Directory, or if the installer's log files indicate that OIDMON could not start, you may have encountered this issue.

To work around this issue, reduce the length of environment variables so that the total length of all variables is less than 4,000 characters and then attempt to configure Oracle Internet Directory again.

2.3.2.6 Password Requirements for Oracle Internet Directory Administrator

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.

2.3.2.7 Harmless Error Message When Configuring Oracle Identity Federation

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.

2.3.3 Issues Pertaining to Oracle Identity and Access Management Configuration

This section contains information pertaining to Oracle Identity and Access Management 11g Release 1 (11.1.1.7.0) configuration:

Note:
For 11g Release 1 (11.1.1.6.0) configuration release notes, refer to the following links:

- Oracle Fusion Middleware Release Notes 11g Release 1 (11.1.1) for Linux x86

- Oracle Fusion Middleware Release Notes 11g Release 1 (11.1.1) for Microsoft Windows (32-Bit)

At this time, there are no known issues on Windows operating systems.

2.3.3.1 Log Messages Appearing on Console During Oracle Identity Manager Schema Creation

During the creation of the Oracle Identity Manager (OIM) schema, some log messages will appear in the RCU console window. These log messages are specific to Quartz, which is used by Oracle Identity Manager, and can be safely ignored.

If there are any errors encountered during the loading of this Quartz-specific data, the errors will be written to the RCU log files. Refer to Oracle Fusion Middleware Repository Creation Utility User's Guide for more information about the RCU log files.

2.3.3.2 Design Console Connectivity Fails Intermittently

Design console connectivity to server may fail intermittently in SSL mode.

2.3.4 Issues Pertaining to the Configuration Wizard

This section contains the following:

- Section 2.3.4.1, "Starting the Configuration Wizard From a New Window"

- Section 2.3.4.2, "Specify Security Updates Screen Does Not Appear in the Configuration Wizard"

2.3.4.1 Starting the Configuration Wizard From a New Window

When you start the Configuration Wizard from a terminal window, make sure that it is a new terminal window to ensure that there are no environment variables set to incorrect locations from a previous configuration or installation session.

2.3.4.2 Specify Security Updates Screen Does Not Appear in the Configuration Wizard

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.

2.3.5 Issues Pertaining to the Repository Creation Utility (RCU)

This section contains the following:

- Section 2.3.5.1, "Increasing the Tablespace Size for the MDS Schema"

- Section 2.3.5.2, "Schemas Are Not Visible After Upgrade of Oracle Identity Management"

- Section 2.3.5.3, "RCU Summary Screen Issues"

2.3.5.1 Increasing the Tablespace Size for the MDS Schema

On Oracle databases, a default tablespace size of 1024MB is created for the MDS schema. If you need to increase the size of this tablespace, do the following:

1. Log in to the Database Control page. For example:

https://db_host:db_port/em/

2. Select the Server tab.

3. In the "Storage" section, select Datafiles.

4. Select the row of the datafile corresponding to the schema you want to edit, then click Edit. In the case of the MDS schema, the datafile name should be prefix_mds.dbf.

5. On the "Edit Datafile" page, increase the size of the tablespace.

2.3.5.2 Schemas Are Not Visible After Upgrade of Oracle Identity Management

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.

2.3.5.3 RCU Summary Screen Issues

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.

2.3.6 Issues Pertaining to Packing and Unpacking a Domain

This section contains the following:

- Section 2.3.6.1, "Ensure There Are No Missing Products When Using unpack.sh or unpack.cmd"

- Section 2.3.6.2, "Running unpack.sh or unpack.cmd on a Different Host"

- Section 2.3.6.3, "Starting Managed Servers on Remote System After Packing and Unpacking Domain"

2.3.6.1 Ensure There Are No Missing Products When Using unpack.sh or unpack.cmd

Oracle SOA Suite, Oracle WebCenter Portal, and Application Developer all contain the pack.shcmd and unpack.shcmd scripts in their respective ORACLE_HOME/common/bin\common\bin directories.

The pack.shcmd script is 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.shcmd script is used to create a full domain or a subset of a domain used for a Managed Server domain directory on a remote system.

Both pack.shcmd and unpack.shcmd will fail if any installed products are missing from the system where you are running these scripts.

2.3.6.2 Running unpack.sh or unpack.cmd on a Different Host

If you are running the unpack.shcmd 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

Host 1:
MW_HOME = C:\Oracle\Middleware
ORACLE_HOME = C:\Oracle\Middleware\Oracle_SOA1

@ Host 2:
MW_HOME = C:\Oracle\Middleware
ORACLE_HOME = C:\Oracle\Middleware\Oracle_SOA1

The example below is NOT valid because the Oracle homes do not match:

Host 1:
MW_HOME = C:\Oracle\Middleware
ORACLE_HOME = C:\Oracle\Middleware\Oracle_SOA1

@ Host 2:
MW_HOME = C:\Oracle\Middleware
ORACLE_HOME = C:\Oracle\Middleware\SOA_Home

The example below is NOT valid because the Middleware homes do not match:

Host 1:
MW_HOME = C:\Oracle\Middleware
ORACLE_HOME = C:\Oracle\Middleware\Oracle_SOA1

@ Host 2:
MW_HOME = C:\Oracle\MWHome
ORACLE_HOME = C:\Oracle\Middleware\Oracle_SOA1

2.3.6.3 Starting Managed Servers on Remote System After Packing and Unpacking Domain

After you unpack a domain on a remote system using the unpack command, complete the following steps:

1. Start Node Manager on the remote system. This action creates a nodemanager.properties file on your system in the MW_HOME/wlserver_10.3/common/nodemanager\wlserver_10.3\common\nodemanager directory.

2. Stop Node Manager.

3. Open the nodemanager.properties file in a text editor and set the StartScriptEnabled property to true.

4. Start the Node Manager on the remote system before starting the Managed Server on the remote system through the Oracle WebLogic Administration Console.

2.3.7 Issues Pertaining to Cluster Configuration

This section contains the following:

- Section 2.3.7.1, "Extend Domain and Expand Cluster Scenarios with Remote Systems"

- Section 2.3.7.2, "Unable to Extend an Existing Domain by Selecting Only Oracle Directory Integration Platform Without Cluster"

- Section 2.3.7.3, "Expand Cluster Requires Changes to the emd.properties File"

2.3.7.1 Extend Domain and Expand Cluster Scenarios with Remote Systems

In scenarios where you are using the Fusion Middleware Configuration Wizard to extend a domain or expand a cluster with remote systems, you must make sure that both the source and destination Middleware home and Oracle home directories are identical.

2.3.7.2 Unable to Extend an Existing Domain by Selecting Only Oracle Directory Integration Platform Without Cluster

Selecting only Oracle Directory Integration Platform without cluster in a session followed by creating cluster and extending domain on the same system fails.

In this domain configuration scenario, ensure that you install and configure Oracle Directory Services Manager on the same system where you extending the domain to configure Oracle Directory Integration Platform.

2.3.7.3 Expand Cluster Requires Changes to the emd.properties File

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\EMAGENT\EMAGENT\sysman\config\emd.properties 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://examplehost.exampledomain.com:5160/emd/main

2.3.8 Discoverer URL is not Properly Displayed When Accessed Through SSL

In 11g Release 1 (11.1.1.7.0), the Discoverer page is not displayed properly when accessed through the SSL port of Oracle Web Cache or Oracle HTTP Server.

To work around this issue, do the following:

1. Log in to the Administration Server Console.

2. Select Environment->Servers->AdminServer->Configuration->General->Advanced.

3. Enable "WebLogic Plug-In Enabled".

4. Repeat steps 1-3 for the WLS_DISCO server.

5. Restart all of the servers and access the page again.

2.3.9 Cleaning up the JDeveloper Directories for a Failed Deployment on Windows

When a JDeveloper deployment fails on Windows, you should remove the hidden system directory and all its subdirectories in AppData\Roaming\JDeveloper before you try to deploy again.

2.3.10 OPMN Does Not Start if the LD_ASSUME_KERNEL Environment Variable is Set

On all UNIX operating systems, for all products that install Oracle Process Manager and Notification Server or OPMN (for example, Oracle Identity Management, Oracle Web Tier, Oracle Portal, Forms, Reports and Discoverer, and Oracle Business Intelligence), OPMN will not start if the LD_ASSUME_KERNEL environment variable is set. Make sure that this environment variable is not set.

2.3.11 Oracle WebCenter Portal wc-post-install.py Script Not Supported for Oracle RAC Datasources

The wc-post-install.py script can not be used in an environment with Oracle RAC datasources (gridlink or multi-datasource).

To work around this issue:

1. Edit the WC_ORACLE_HOME/bpm/process_spaces/wc-post-install.py script and comment out all lines containing setDatasource in the file by adding a hash (#) character to the beginning of the line.

2. Use the WebCenter Portal Console and manually configure the following datasources:

- mds-soa

- mds-soa0

- mds-soa1

- SOADataSource

- SOADataSource0

- SOADataSource1

3. Run the wc-post-install.py script.

2.3.12 FileNotFoundException When Cloning on Windows

When you run the applyClone command on Windows operating systems, a java.io.FileNotFoundException is thrown to the console.

This exception can be safely ignored and the applyClone operation will be successfully completed.

2.3.13 Changing the Listen Address of a Managed Server

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 system.

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.

2.3.14 Domain Extension Overwrites JDBC Data Source Name

When a WebLogic Domain with JDBC resources is extended to either Oracle SOA Suite or Oracle WebCenter Portal, 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 Portal.

To work around this issue, you must manually edit the JDBC data source names.

2.3.15 Rerouting to Original URL After SSO Authentication in Firefox and Safari Browsers

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 and Safari browsers 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\config\OHS\instance_name\httpd.conf file and change the ServerName entry to include the port number. For example:

ServerName examplehost.exampledomain.com

should be changed to:

ServerName examplehost.exampledomain.com:port

Replace port with the actual port number.

2.3.16 Deleting the Browser Cache in Browsers

Make sure you clear your browser cache files; otherwise, the objects on your screen (for example, in Oracle Enterprise Manager) may not be refreshed to the latest version, or if you added a new object then it may not appear.

2.3.17 WebLogic Administration Server Fails to Start Due to Memory Issues

On Windows 32-bit operating systems, the WebLogic Administration Server may fail to start, as it cannot allocate sufficient memory despite the availability of free memory.

As a workaround, complete the following steps:

1. Open the setSOADomainEnv.cmd file, located in your <Domain_Home>\bin directory, in a text editor.

2. Update the PORT_MEM_ARGS entry as follows:
set PORT_MEM_ARGS=-Xms512m -Xmx1024m

3. Save the file and close.

2.4 Known Issues

This section describes known issues. It includes the following topics:

- Section 2.4.1, "Forms and Reports Builder Not Supported"

2.4.1 Forms and Reports Builder Not Supported

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 (64-Bit) platforms. It is supported on Linux x86 and Microsoft Windows (32-Bit) platforms only.

2.5 Documentation Errata

This section describes documentation errata. It includes the following topic:

- Section 2.5.1, "Incorrect Option Specified in the RCU Online Help"

- Section 2.5.2, "Deinstall Instructions Missing for Oracle HTTP Server, Oracle Traffic Director, and Oracle iPlanet 11g Release 1 WebGates for Oracle Access Manager"

2.5.1 Incorrect Option Specified in the RCU Online Help

The RCU online help for the Master and Work Repository Custom Variables for Oracle Data Integrator contains an incorrect option.

For the Work Repository Type, the correct options should be:

- Use Development (D) for creating a development repository.

- Use Execution (E) for creating an execution repository.

2.5.2 Deinstall Instructions Missing for Oracle HTTP Server, Oracle Traffic Director, and Oracle iPlanet 11g Release 1 WebGates for Oracle Access Manager

The content in this section is missing from the Installing Webgates for Oracle Access Manager guide:

2.5.2.1 Deinstalling Oracle HTTP Server, Oracle Traffic Director, and Oracle iPlanet 11g Release 1 WebGates for Oracle Access Manager

You should always use the instructions provided in this section for removing the Oracle HTTP Server, Oracle Traffic Director, and Oracle iPlanet 11.1.1.7.0 WebGates for Oracle Access Manager. If you try to remove the software manually, you may experience problems when you try to reinstall the software again at a later time. Following the procedures in this section will ensure that the software is properly removed.

To deinstall the WebGate agent, do the following:

1. Go to the MW_HOME/oracle_common/oui/bin\oracle_common\oui\bin directory.

2. Run the following command:
On UNIX: ./runInstaller -deinstall

On Windows: setup.exe -deinstall -jreLoc JRE_LOCATION

Ensure that you specify the absolute path to your JRE_LOCATION; relative paths are not supported.

After the deinstaller starts, the Welcome screen is displayed. Proceed with the deinstallation by referring to Section 2.5.2.1 for deinstalling 11g Release 1 WebGate agents for Oracle Access Manager.

2.5.2.1.1 Deinstallation Screens and Instructions

Follow the instructions in Table 2-1 to complete the deinstallation.

If you need additional help with any of the deinstallation screens, click Help to access the online help.

Table 2-1 Deinstallation Flow

Sl. No.

Screen

Description

Action Required

1.

Welcome

Each time the deinstaller starts, the Welcome screen is displayed.

Click Next.

2.

Deinstall Oracle Home

The Deinstall Oracle Home screen shows the Oracle home you are about to deinstall.

Verify the Oracle home you are about to deinstall.

Click Deinstall.

On the Warning screen, select whether or not you want the deinstaller to remove the Oracle home directory in addition to removing the software.

Click Yes to have the deinstaller remove the software and Oracle home, No to remove only the software, or Cancel to return to the previous screen.

If you select No, go to Section 2.5.2.1.2 for instructions on how to manually remove your Oracle home directory.

3.

Deinstallation progress

The Deinstallation Progress screen shows the progress and status of the deinstallation.

Wait until the Deinstallation Complete screen appears.

4.

Deinstallation Complete

The Deinstallation Complete screen appears when the deinstallation is complete.

Click Finish to dismiss the screen.

2.5.2.1.2 Manually Removing the Oracle Home Directory

If you have selected No on the warning dialog box, in the Deinstall Oracle Home screen during deinstallation, then you must manually remove your oracle_common directory and any sub-directories. For example: if your Oracle Common home directory was /home/Oracle/Middleware/oracle_common, run the following commands:

cd /home/Oracle/Middleware
rm -rf oracle_common

On Windows, if your Oracle Common home directory was C:\Oracle\Middleware\oracle_common, then use a file manager window, go to the C:\Oracle\Middleware directory, right-click on the oracle_common folder, and then select Delete.

3 Upgrade

This chapter describes issues associated with upgrading your environment and your applications to Oracle Fusion Middleware 11g. It includes the following topics:

- Section 3.1, "General Issues and Workarounds"

- Section 3.2, "General Issues and Workarounds for Migrating from 11.1.1.1.0"

- Section 3.3, "Documentation Errata for Upgrade"

Note:
This chapter contains issues you might encounter while upgrading any of the Oracle Fusion Middleware products.
Be sure to review the product-specific release note chapters elsewhere in this document for any additional issues specific to the products you are using.

3.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topics:

- Section 3.1.1, "Patches Required to Address Specific Upgrade and Compatibility Requirements"

- Section 3.1.2, "Unable to Read Composite Model Error During SOA Application Upgrade"

- Section 3.1.3, "Oracle BAM Upgrade Issues"

- Section 3.1.4, "Error When Upgrading Oracle Internet Directory Due to Invalid ODS Schema"

- Section 3.1.5, "Restore From Backup Required If Upgrade Fails During a Colocated Oracle Internet Directory and Oracle Directory Integration Platform Upgrade"

- Section 3.1.6, "Cannot Verify Oracle Forms Services Upgrade When Oracle HTTP Server is Running On a Separate Host"

- Section 3.1.7, "WebCenter Security Upgrade Release Notes"

- Section 3.1.8, "Oracle B2B Upgrade Release Notes"

- Section 3.1.9, "Problem Accessing the Welcome Pages in Oracle HTTP Server After Upgrade"

- Section 3.1.10, "Misleading Error Message When Upgrading Oracle Internet Directory"

- Section 3.1.11, "Additional Steps Required When Redeploying the SOA Order Booking Sample Application on Oracle Fusion Middleware 11g"

- Section 3.1.12, "Additional Steps Required When Upgrading Human Taskflow Projects"

- Section 3.1.13, "Stopping Oracle Virtual Directory Processes During Upgrade"

- Section 3.1.14, "Providing Input to Upgrade Assistant Screens When Oracle Internet Directory Upgrade Fails"

- Section 3.1.15, "Upgrading Oracle Access Manager Middle Tier"

- Section 3.1.16, "Inaccurate Results When Running the Upgrade Assistant Verify Feature"

- Section 3.1.17, "Missing jdk_version.log File When Launching Upgrade Assistant"

- Section 3.1.18, "Test Suites in Oracle SOA Suite 10g Projects Not Upgraded to 11g"

- Section 3.1.19, "Incorrect Wiring When Migrating Certain Oracle SOA Suite 10g Projects to 11g"

3.1.1 Patches Required to Address Specific Upgrade and Compatibility Requirements

In general, Oracle assumes that you are running the latest Oracle Application Server 10g patch sets before you begin the upgrade to Oracle Fusion Middleware 11g.

In addition, in some specific cases, you must apply an additional software patches to your Oracle Application Server 10g components before you start the upgrade process. These patches are designed to address specific interoperability issues that you might encounter while upgrading your Oracle Application Server 10g environment to Oracle Fusion Middleware 11g.

Table 3-1 lists the specific patch sets required to address specific upgrade and compatibility requirements for Oracle Fusion Middleware 11g.

For more information, refer to the following sections:

- Section 3.1.1.1, "Obtaining Patches and Support Documents From My Oracle Support (Formerly OracleMetaLink)"

- Section 3.1.1.2, "Upgrading the Oracle BAM Schema on Oracle Database 11g on Microsoft Windows"

Table 3-1 Patches Required to Address Specific Upgrade and Compatibility Requirements

Patch Set Number

Description and Purpose

Additional Information

8404955

Before you can perform the Oracle B2B schema upgrade, you must apply this required patch to the Oracle Application Server Integration B2B 10g Release 2 (10.1.2) middle tier.

This patch set is required in order to enable the Java command that you use to export the trading partner agreements, as described in the following step.

"Task 6b: If Necessary, Upgrade the B2B Schema" in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter Portal, and ADF

8451592

If your Oracle BAM 10g schema is stored in Oracle Database 11g (10.1.0.7) on a Microsoft Windows 32-bit computer, then you must apply this patch to the database before using the Upgrade Assistant to upgrade the schema to 11g.

Section 3.1.1.2, "Upgrading the Oracle BAM Schema on Oracle Database 11g on Microsoft Windows"

5746866

If the database that hosts your Oracle Application Server 10g schemas is an Oracle Database 10g (10.1.0.x) database, then make sure that this database patch (or database patch 5126270) has been applied to the 10g (10.1.0.x) database before you upgrade the database to the required Oracle Database 10g (10.2.0.4).

Note that database patch 5746866 includes patch 5126270.

"Upgrading to Oracle Database 10g Release 2 (10.2.0.4)" in the Oracle Fusion Middleware Upgrade Planning Guide

7685124

Apply this patch against Oracle Secure Enterprise Search (10.1.8.3.0) before you attempt to use Oracle Secure Enterprise Search with Oracle Portal 11g.

"Oracle Secure Enterprise Search" in the Oracle Fusion Middleware Administrator's Guide for Oracle Portal

8372141

Apply this patch on your Oracle Application Server 10g Release 3 (10.1.3.4) environment to enable interoperability between Oracle SOA Suite 10g Release 3 (10.1.3.4) and Oracle BPEL Process Manager 11g.

This patch is also referred to as the Oracle SOA Suite 10g Release 3 (10.1.3.4) Cumulative MLR #7.

"Upgrading Oracle SOA Suite Client Applications" in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter Portal, and ADF

6522654

Apply this patch to your Oracle Database before you attempt to upgrade your Oracle BAM schema.

If you do not apply this patch to your Oracle Database 10g (10.2.0.3), 10g (10.2.0.4), or Oracle Database 11g (11.1.0.7) before performing the schema upgrade, you will likely see the following error:

BAM MRUA: SCHEMA UPGRADE FAILED SQLException: ORA-39002: invalid operation

The description for this patch on My Oracle Support is "USING DATA PUMP THROUGH DBLINK CAUSED DATA CORRUPTION FOR CLOB VALUES".

"Task 6c: If Necessary, Upgrade the BAM Schema" in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter Portal, and ADF

Section 3.1.3.1, "Datapump Export for Oracle BAM Upgrade Plug-in Fails in Oracle Database 10g (10.2.0.3), 10g (10.1.2.0.4), and Oracle Database 11g (11.1.0.7)"

7675269

Apply this patch to prevent the occurrence of an ORA-01591 error in an Oracle Real Application Clusters (Oracle RAC) 11g (11.1.0.7) database.

This error can occur for rows locked by transactions which were in the middle of two-phase commit.

The description of this patch on My Oracle Support is "ODAC 2008:RAC NODE AFFINITY: DISTRIBUTED TXN ABORTS WITH ORA-01591."

"Upgrading and Preparing Your Databases" in the Oracle Fusion Middleware Upgrade Planning Guide

8291981

Apply this patch to correct a problem where Metadata Repository (MDS) queries against an Oracle Database 11g (11.1.0.7) database do not find all of the results (documents or elements) that they should.

The description of this patch on My Oracle Support is: "SELECT INCORRECT RESULTS: SOME RESULTS NOT FOUND".

"Managing the MDS Repository" in the Oracle Fusion Middleware Administrator's Guide

9007079

Apply this bundled patch to your Oracle Database 11g (11.1.0.7) Real Application Clusters (Oracle RAC) environment to address three known issues while using the Oracle RAC database with Oracle Fusion Middleware Oracle SOA Suite components.

See the Readme file for the patch for a list of the bugs addressed by the patch.

The description of this patch on My Oracle Support is: "MERGE REQUEST FOR 8886255 AND 7675269".

"Oracle Real Application Clusters and Fusion Middleware" in the Oracle Fusion Middleware High Availability Guide.

8607693

Apply this patch to your Oracle Real Application Clusters (Oracle RAC) 11g (11.1.0.7) database to prevent an error that can occur if an XA transaction branch was being asynchronously rolled back by two or more sessions.

The description of this patch on My Oracle Support is: "STRESS SOA - ORA-00600: INTERNAL ERROR CODE, ARGUMENTS: [504] (Oracle AC)".

"Oracle Real Application Clusters and Fusion Middleware" in the Oracle Fusion Middleware High Availability Guide.

7682186

Apply this patch to your Oracle Real Application Clusters (Oracle RAC) 11g (11.1.0.7) database to prevent an issue that results in an ORA-600 error.

Behavior includes CR-inconsistencies between index and the block, or incorrect results in an Oracle RAC multi-node global transaction environment.

The description of this patch on My Oracle Support is: "ORA-600[KDSGRP1] SIGNALLED DURING BUGOLTP-XA WORKLOAD".

"Oracle Real Application Clusters and Fusion Middleware" in the Oracle Fusion Middleware High Availability Guide.

3.1.1.1 Obtaining Patches and Support Documents From My Oracle Support (Formerly OracleMetaLink)

To obtain a patch, log in to My Oracle Support (formerly OracleMetaLink), click Patches and Updates, and search for the patch number:

http://support.oracle.com/

To obtain a support note or document, log in to My Oracle Support and enter the support note number in the Quick Find search field at the top of the My Oracle Support window and search the Knowledge Base for the note number.

3.1.1.2 Upgrading the Oracle BAM Schema on Oracle Database 11g on Microsoft Windows

If the Oracle Database you use to host your Oracle BAM schema is an Oracle Database 11g database, then you must apply the required patches to upgrade your database to Oracle Database 11g (10.1.0.7).

In addition, if the database is running on a Microsoft Windows 32-bit computer, then you must also apply patch 8451592 to the Oracle Database 11g (10.1.0.7) database before you can run the Upgrade Assistant to upgrade the Oracle BAM schema to 11g.

Patch 8451592 is also referred to as Oracle Database Server Version 11.1.0.7 Patch 11.

Important:
You must perform the steps described in Section 3.3.5, "Post Installation Instructions" of the Oracle Database Server Version 11.1.0.7 Patch 11 Bundle Patch Update Note, which explain in detail how to run the catcpu.sql script.
If you do not run the catcpu.sql script after applying the database patch, then the Oracle BAM schema upgrade will fail.

The patch update note is available by clicking the View Readme button when you locate the patch in My Oracle Support. It is also included in the downloaded ZIP file that contains the patch files.

For more information about upgrading the Oracle BAM schema, see the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter Portal, and ADF.

3.1.2 Unable to Read Composite Model Error During SOA Application Upgrade

The Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter Portal, and ADF describes how Oracle JDeveloper 11g will automatically upgrade specific features of your Oracle SOA Suite 10g applications to 11g.

However, if you see the following error while upgrading your application in JDeveloper 11g, then you can safely ignore the error. Your application will be upgraded, but you will need to create a new SOA-SAR deployment profile after the application upgrade. And use this newly created profile for deploying SOA composite:

SEVERE: Unable to read composite model for project project_name

For more information, see 43.2, "Deploying a Single SOA Composite in Oracle JDeveloper," in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

3.1.3 Oracle BAM Upgrade Issues

The following sections provide information about specific issues related to upgrading Oracle BAM 10g to Oracle BAM 11g:

- Section 3.1.3.1, "Datapump Export for Oracle BAM Upgrade Plug-in Fails in Oracle Database 10g (10.2.0.3), 10g (10.1.2.0.4), and Oracle Database 11g (11.1.0.7)"

- Section 3.1.3.2, "Dependent Alerts Do Not Upgrade Correctly"

- Section 3.1.3.3, "Problem Upgrading a Report that Contains Calculated Fields"

- Section 3.1.3.4, "Calculated Fields Reference the Field ID Rather Than Field Names After Upgrade to Oracle BAM 11g"

- Section 3.1.3.5, "Using the Oracle BAM 11g Samples After Upgrade from Oracle BAM 10g"

3.1.3.1 Datapump Export for Oracle BAM Upgrade Plug-in Fails in Oracle Database 10g (10.2.0.3), 10g (10.1.2.0.4), and Oracle Database 11g (11.1.0.7)

Before you upgrade the Oracle BAM 11g schema to 11g, you must first apply patch 6522654 to your Oracle Database 10g (10.2.0.3), 10g (10.1.2.0.4), and Oracle Database 11g (11.1.0.7).

If you do not apply this patch, then you will likely experience the following error during Oracle BAM schema upgrade:

BAM MRUA: SCHEMA UPGRADE FAILED SQLException: ORA-39002: invalid operation

For more information, see Section 3.1.1, "Patches Required to Address Specific Upgrade and Compatibility Requirements".

3.1.3.2 Dependent Alerts Do Not Upgrade Correctly

When an alert in Oracle BAM 10g is dependent upon another alert, the dependent alert keeps a reference to the parent alert with a GUID reference. When such an alert is exported from 10g it will contain a GUID reference to the parent alert, and import to an Oracle BAM 11g system is not successful.

The following modification to the exported alert definition file can be used as a workaround for import to an Oracle BAM 11g system.

Edit the exported file contents of the dependent alert from the Oracle BAM 10g system, and modify the following element containing reference to parent alert.

Change this:

&lt;param name=&quot;RuleID&quot; order=&quot;0&quot;&gt;
//private:weblogic/Rule/624567ffe84de34c-6e6bdbaa120eb7f6ea6-8000
&lt;/param&gt;

To this:

&lt;param name=&quot;RuleID&quot; order=&quot;0&quot;&gt;
ParentAlertName
&lt;/param&gt;

In other words, the GUID reference for parent alert must be replaced by the parent alert's name.

3.1.3.3 Problem Upgrading a Report that Contains Calculated Fields

If you created a report in Oracle BAM 10g or in Oracle BAM 11g Release 1 (11.1.1.1.0) and the report contains calculated fields that use using datetime type fields, then the Calculations tab displays this error in Oracle BAM 11g Release 1 (11.1.1.2.0):

BAM-01610: INVALID FILTER EXPRESSION

More specifically, this error occurs when the calculation is an expression for equality check against a datetime field in String format. For example, for a datetime field such as Last Modified, the following calculation does not work:

If {Last Modified}=="7/18/2002 1:33:10 PM"

Before you can upgrade the report, you must remove the calculated fields.

3.1.3.4 Calculated Fields Reference the Field ID Rather Than Field Names After Upgrade to Oracle BAM 11g

After upgrading to Oracle BAM 11g Release 1 (11.1.1.2.0), any calculated fields in your reports will reference fields by the field ID, rather than the field name.

Specifically, after upgrade, the field name referenced in the expression will be converted to use the field id (for example, _Num_Sold).

For example, the field reference might appear as follows after the upgrade:

If({_Num_Sold}==5000)
Then("met")
Else("notmet")

Note that the calculated fields will continue to work after the upgrade and after this automatic conversion.

3.1.3.5 Using the Oracle BAM 11g Samples After Upgrade from Oracle BAM 10g

When you install Oracle BAM 11g, the installer copies a set of sample applications to the Oracle SOA Suite Oracle home. Refer to the following sections for more information about using these samples after upgrading to Oracle BAM 11g from Oracle BAM 10g:

- Section 3.1.3.5.1, "General Information About the Oracle BAM Samples"

- Section 3.1.3.5.2, "Removing Any 10g Sample Applications Before Configuring the Oracle BAM 11g Samples"

For information about using the Oracle BAM 11g after migrating from Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0), see Section 3.2.8, "Using the Oracle BAM 11g Prepackaged Samples After Migrating from 11.1.1.1.0".

3.1.3.5.1 General Information About the Oracle BAM Samples

The Oracle Fusion Middleware installer copies the Oracle BAM samples to the following location in the Oracle SOA Suite Oracle home:

SOA_ORACLE_HOME/bam/samples/bam/

Instructions for configuring and using the samples, as well as updated samples, can be found at the following URL on the Oracle Technology Network (OTN):

http://www.oracle.com/technology/products/integration/bam/collateral/samples11g.html

The instructions explain how to use the propert setup script to configure the demos in your Oracle BAM 11g environment. You can also find individual readme file for each demo within each sample directory.

3.1.3.5.2 Removing Any 10g Sample Applications Before Configuring the Oracle BAM 11g Samples

Before you use the instructions on OTN to set up the Oracle BAM 11g samples, remove any data objects, reports, or alerts associated with any existing 10g samples.

For example, be sure to remove any artifacts associated with the Oracle BAM 10g Call Center and Atherton demos before you run the setup scripts.

3.1.4 Error When Upgrading Oracle Internet Directory Due to Invalid ODS Schema

If you receive an error when using the Upgrade Assistant to upgrade the Oracle Internet Directory schema from 10g Release 2 (10.1.2.3) to 11g, then verify that the ODS 10g schema is valid.

To view the status of the Oracle Application Server 10g schemas in your database, use the following SQL command:

SELECT comp_id, version, status FROM app_registry;

If the output from this command shows that the ODS schema is INVALID, then use the instructions in the following My Oracle Support document to install and configure Referential Integrity:

730360.1, "Referential Integrity in Oracle Internet Directory Version 10.1.2.3"

After performing the instructions in the support document, then retry the Oracle Internet Directory schema upgrade.

3.1.5 Restore From Backup Required If Upgrade Fails During a Colocated Oracle Internet Directory and Oracle Directory Integration Platform Upgrade

If you are using the Upgrade Assistant to upgrade both Oracle Internet Directory and Oracle Directory Integration Platform, consider the following.

If the Oracle Internet Directory upgrade fails, then before you can run the Upgrade Assistant again, you must restore your Oracle Internet Directory 10g backup before you can run the Upgrade Assistant again. Otherwise, the Upgrade Assistant will not attempt to upgrade Oracle Directory Integration Platform.

3.1.6 Cannot Verify Oracle Forms Services Upgrade When Oracle HTTP Server is Running On a Separate Host

If you use the Upgrade Assistant to upgrade an Oracle Forms Services instance that does not include a local instance of Oracle HTTP Server, then the Verify feature of the Upgrade Assistant cannot verify that the upgrade was successful. Instead of reporting that the upgrade was successful, the Verify feature will report that the server is unavailable. This verification error may not be valid if the Oracle HTTP Server is installed and configured on a different host than the Oracle Forms Services instance.

3.1.7 WebCenter Security Upgrade Release Notes

The following bugs/release notes relate to security changes for Custom WebCenter applications upgrading from 10.1.3.x:

- Section 3.1.7.1, "RowSetPermission check fails with compatibility flag set"

- Section 3.1.7.2, "Grants not migrated properly if application contains grants without permissions"

- Section 3.1.7.3, "Shared/public credentials not found after external application deployed"

3.1.7.1 RowSetPermission check fails with compatibility flag set

In 10.1.3, the ADF framework performed rowset, attribute, and method permission checks in addition to page permission checks. If a 10.1.3 application grants 'read' permission on the rowset and attribute and 'invoke' permission on the method for all users, then the application will behave as expected in 11R1 without any additional setup.

However, if the 10.1.3 application was designed to allow only certain users to view the rowset, attribute, or invoke method, then a special flag needs to be set to support this style of security. If this flag is not set, then anyone who has page access can view attributes and rowsets and invoke methods since in 11R1 the permission check is performed only on pages and taskflows. The flag must be set for each application in the adf-config.xml file.

<sec:adf-security-child xmlns="http://xmlns.oracle.com/adf/security/config">
<JaasSecurityContext
initialContextFactoryClass=
"oracle.adf.share.security.JAASInitialContextFactory"
jaasProviderClass=
"oracle.adf.share.security.providers.jps.JpsSecurityContext"
authorizationEnforce="true"/>
<contextEnv name="oracle.adf.security.metadata" value="false"/>
<CredentialStoreContext
credentialStoreClass=
"oracle.adf.share.security.providers.jps.CSFCredentialStore"
credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
</sec:adf-security-child>

3.1.7.2 Grants not migrated properly if application contains grants without permissions

Grants are not migrated properly if a 10.1.3 application contains grants without any permissions. Developers should inspect the app-jazn-data.xml file in the 10.1.3 workspace and remove any grants that have empty permission set prior to performing the migration.

3.1.7.3 Shared/public credentials not found after external application deployed

If you have secured your 10.1.3 application, ensure there are no duplicate JaasSecurityContext and CredentialStoreContext elements in the application's adf-config.xml file prior to migration.In the following example, the first JaasSecurityContext element is empty and should be removed (see "Remove entry" in the XML snippet below).

<adf-config-child xmlns="http://xmlns.oracle.com/adf/security/config">
<CredentialStoreContext
credentialStoreClass=
"oracle.adf.share.security.providers.jazn.JAZNCredentialStore"
credentialStoreDefaultUser="anonymous"
credentialStoreLocation="./credential-store.xml"/>
<JaasSecurityContext/> <!--Remove entry-->
<JaasSecurityContext
initialContextFactoryClass=
"oracle.adf.share.security.JAASInitialContextFactory"
jaasProviderClass=
"oracle.adf.share.security.providers.jazn.JAZNSecurityContext"
authorizationEnforce="true"/>
</adf-config-child>

3.1.8 Oracle B2B Upgrade Release Notes

The following release notes apply when you are upgrading Oracle B2B 10g to Oracle B2B 11g:

- Section 3.1.8.1, "Service Name Is Required When Using ebMS with Oracle B2B"

- Section 3.1.8.2, "Converting Wallets to Keystores for Oracle B2B 11g"

- Section 3.1.8.3, "Oracle B2B UCCnet Documents Not Upgraded to 11g"

- Section 3.1.8.4, "Errors in the Upgrade Log Files Even When Oracle B2B Schema Upgrade is Successful"

3.1.8.1 Service Name Is Required When Using ebMS with Oracle B2B

Because the Service Name parameter is required when using the ebMS protocol in Oracle B2B 11g, you may need to provide a value for this field after importing 10g data.

With the agreement in the draft state, update the field on the Partners > Documents tab. When you select a document definition that uses the ebMS protocol, the Document Type > ebMS tab appears in the Document Details area. The Service Name field is on this tab.

3.1.8.2 Converting Wallets to Keystores for Oracle B2B 11g

After upgrading to Oracle B2B 11g, use the orapki pkcs12_to_jks option to replace the entire keystore. Convert the wallet to a keystore as follows:

1. Back up the original keystore.

2. Use the orapki wallet pkcs12_to_jks option to convert to the keystore.

3. Use keytool -list to list the aliases and verify.

4. Use keytool -importkeystore to import the converted keystore to the backup of the original keystore (as done in Step 1)

3.1.8.3 Oracle B2B UCCnet Documents Not Upgraded to 11g

OracleAS Integration B2B provides support for UCCnet under the Custom Document option. UCCnet is a service that enables trading partners to exchange standards-compliant data in the retail and consumer goods industries.

Note, however, that UCCnet documents are not upgraded automatically to Oracle B2B 11g. For information about using UCCnet documents in Oracle B2B 11g, see "Using the UCCnet Document Protocol" in the Oracle Fusion Middleware User's Guide for Oracle B2B.

3.1.8.4 Errors in the Upgrade Log Files Even When Oracle B2B Schema Upgrade is Successful

When you use Oracle Fusion MiddlewareUpgrade Assistant upgrade the Oracle B2B schema, some errors might appear in the upgrade log files even if the Oracle B2B schema upgrade is successful.

For example, you might see an error, such as the following:

oracle.jrf.UnknownPlatformException: JRF is unable to determine the current
application server platform

As long as the Upgrade Assistant reports that the upgrade was successful, these errors can be safely ignored. They will be addressed in a future release.

For more information about troubleshooting upgrade issues, including how to use the upgrade log files, see "General Troubleshooting Guidelines" in the Oracle Fusion Middleware Upgrade Planning Guide.

For more information about the Oracle B2B schema upgrade, see "If Necessary, Upgrade the B2B Schema," in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter Portal, and ADF.

3.1.9 Problem Accessing the Welcome Pages in Oracle HTTP Server After Upgrade

After you upgrade to Oracle HTTP Server 11g, the DirectoryIndex directive in the httpd.conf set to index.html. As a result, if you go to the recommended URL to view the Oracle Fusion Middleware Welcome pages you instead see the "hello world" sample application page.

To address this issue:

1. Edit the httpd.conf file in the following location:

ORACLE_INSTANCE/config/OHS/ohs_component_name/

2. Locate the DirectoryIndex directive in the httpd.conf file and change index.html to welcome-index.html.

3. Restart the Oracle HTTP Server instance.

3.1.10 Misleading Error Message When Upgrading Oracle Internet Directory

When upgrading to Oracle Internet Directory 11g, you might notice an error message in the Upgrade Assistant (Example 3-1). This error message indicates that some managed processes failed to start.

You can safely ignore this message, as long as the Upgrade Assistant messages also indicates that all components were upgraded successfully. This error occurs when the Upgrade Assistant attempts to start the Oracle Enterprise Manager agent and the agent is already running.

Example 3-1 Error Message When Upgrading Oracle Internet Directory

-----------------------------------------------------------
Starting Destination Components
Starting OPMN and managed processes in the destination Oracle instance.
->UPGAST-00141: startup of 11g OPMN managed processes failed.
Starting WebLogic managed server wls_ods1
Clicked OK to continue
Upgrade Progress 100%
All components were upgraded successfully.
------------------------------------------------------------

3.1.11 Additional Steps Required When Redeploying the SOA Order Booking Sample Application on Oracle Fusion Middleware 11g

Appendix A of the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter Portal, and ADF provides an example of how to use Oracle JDeveloper 11g upgrade and redeploy a complex application on Oracle Fusion Middleware 11g.

However, after you install Oracle Fusion Middleware 11g (11.1.1.3.0), you must perform the following additional tasks before you can successfully compile and deploy the application with Oracle JDeveloper 11g:

1. Before you open and upgrade the application with Oracle JDeveloper 11g, edit the original web.xml and replace the <web-app> element with the following:

<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
version="2.5" xmlns="http://java.sun.com/xml/ns/javaee">

2. Follow the steps in Appendix A of the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter Portal, and ADF to open the SOA Order Booking application in Oracle JDeveloper 11g and to upgrade the projects within the application.

3. When you get to Section A.8.10, "ApproveOrderTaskForm," open the web.xml and verify that it contains a <servlet> element and <servlet_mapping> element for the WFTTaskUpdate servlet.
If such an element does not exist in the web.xml file, then edit the web.xml file and add the elements shown in Example 3-2.

4. Continue with the rest of the instructions for deploying the project.

Example 3-2 Servlet Elements to Add to the SOA Order Booking web.xml File

<servlet>
<servlet-name>
WFTaskUpdate
</servlet-name>
<servlet-class>
oracle.bpel.services.workflow.worklist.servlet.WFTaskUpdate
</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>
WFTaskUpdate
</servlet-name>
<url-pattern>
/WFTaskUpdate
</url-pattern>
</servlet-mapping>

3.1.12 Additional Steps Required When Upgrading Human Taskflow Projects

By default, if you deploy an upgraded Oracle SOA Suite 10g Release 3 (10.1.3) application that includes a Human Taskflow project on Oracle Fusion Middleware 11g (11.1.1.3.0), you will not be able to view the taskflow details.

To work around this problem, perform the following additional steps when you are deploying an application with a Human Taskflow project:

1. Before you open and upgrade the application with Oracle JDeveloper 11g, edit the original web.xml and replace the <web-app> element with the following:

<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
version="2.5" xmlns="http://java.sun.com/xml/ns/javaee">

2. After you open and upgrade the application in Oracle JDeveloper 11g, do the following:

1. In Oracle JDeveloper 11g, deploy the application to an EAR file.

2. Expand the EAR file on disk, and then expand the packaged WAR file on disk.
For example:

jar -xvf ear_file_name.ear
jar -xvf war_file_name.war

3. Open the web.xml file in the WEB-INF directory of the WAR file and comment out the following entry:

<!--servlet-mapping>
<servlet-name>jsp</servlet-name>
<url-pattern>*.jsp</url-pattern>
</servlet-mapping-->

4. Repackage WAR and subsequently the EAR.
For example:

jar -cvf war_file_name.war *
jar -cvf ear_file_name.ear *

5. Deploy the EAR using the WebLogic Administration Console.
Note that is important that you use the Oracle WebLogic Server Administration Console to deploy the application and not Oracle JDeveloper 11g. This is because Oracle JDeveloper forces a rebuild of the applciation and your changes will be overwritten.

3.1.13 Stopping Oracle Virtual Directory Processes During Upgrade

When upgrading Oracle Virtual Directory to 11g, you must manually stop Oracle Virtual Directory processes if multiple Oracle Virtual Directory processes are running. When you attempt to stop Oracle Virtual Directory, only the last process that started will stop. If multiple Oracle Virtual Directory processes are running, you must use the kill -9 command to stop the processes before upgrading to Oracle Virtual Directory 11g.

3.1.14 Providing Input to Upgrade Assistant Screens When Oracle Internet Directory Upgrade Fails

If Oracle Internet Directory upgrade fails during the Examine phase in the upgrade process, do not modify the input you entered in the screens. Instead, dismiss the Upgrade Assistant wizard and the upgrade process again.

3.1.15 Upgrading Oracle Access Manager Middle Tier

When running the Upgrade Assistant to upgrade the Oracle Single Sign-On 10g to Oracle Access Manager 11g, you must run the Upgrade Assistant from the same machine where your Oracle Access Manager Managed Server is running.

3.1.16 Inaccurate Results When Running the Upgrade Assistant Verify Feature

For some upgrade scenarios, the Oracle Fusion Middleware Upgrade Assistant provides a Verify feature that attempts to analyze the upgraded 11g environment. When you run the Verify feature, the Upgrade Assistant automatically reports any problems it finds with the upgraded environment.

However, there are cases where the Verify feature incorrectly identifies a problem. For example, when single sign-on is enabled, the Verify feature might report that it cannot access specific URLs for the upgraded components.

In these cases, you should enter the URL directly into a Web browser to verify the URL. In those cases, the URL might indeed be valid and you can ignore the errors generated by the Verify feature.

3.1.17 Missing jdk_version.log File When Launching Upgrade Assistant

When you start the Oracle Fusion Middleware Upgrade Assistant to begin an upgrade of the Oracle Identity and Access Management products, the Upgrade Assistant might display an error message in the terminal window that indicates that the following file is missing:

temp\jdk_version.log

If you see this error, quit the Upgrade Assistant and manually create the following directory before running the Upgrade Assistant:

ORACLE_HOME/upgrade/temp

In this example, ORACLE_HOME is the directory where Oracle Identity and Access Manager product is installed.

3.1.18 Test Suites in Oracle SOA Suite 10g Projects Not Upgraded to 11g

When you upgrade your Oracle SOA Suite 10g projects to Oracle SOA Suite 11g, test suites defined in your Oracle JDeveloper projects will not be upgraded to 11g. In most cases, you will have to modify or recreate your test suites in Oracle JDeveloper 11g.

For more information, refer to the following:

- "Correcting Problems With Oracle BPEL Process Manager Test Suites" in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter Portal, and ADF

- "Automating Testing of SOA Composite Applications" in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite

3.1.19 Incorrect Wiring When Migrating Certain Oracle SOA Suite 10g Projects to 11g

When you migrate certain Oracle SOA Suite 10g projects to 11g, the migration tool wires the composite incorrectly. This occurs if there are duplicate porttypes or partnerlinktypes.

The workaround for this issue is to make sure that the porttypes or partnerlinktypes are unique, and adjust the references before you start the migration process.

3.2 General Issues and Workarounds for Migrating from 11.1.1.1.0

This section describes general issue and workarounds that apply only if you are starting with Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) and you are using the instructions in Appendix B, "Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0)" in the Oracle Fusion Middleware Patching Guide.

This section includes the following topics:

- Section 3.2.1, "Stopping the 11.1.1.2.0 Domain"

- Section 3.2.2, "Editing the patchMaster.properties File"

- Section 3.2.3, "Patching the Schema for Oracle Internet Directory"

- Section 3.2.4, "Changing the patchmaster.ValidationErrorContinue Property"

- Section 3.2.5, "Changing the Default Setting for Validation Tasks"

- Section 3.2.6, "Severe Error When Running the execute-sql-rcu Macro"

- Section 3.2.7, "Machine Names Do Not Appear in the Oracle WebLogic Server Administration Console"

- Section 3.2.8, "Using the Oracle BAM 11g Prepackaged Samples After Migrating from 11.1.1.1.0"

3.2.1 Stopping the 11.1.1.2.0 Domain

While stopping the 11.1.1.2.0 domain by using the ant master-stop-domain-new command, you may see the following exceptions if the Administration Server and the Managed Servers are down:

java.net.ConnectException: Connection refused: connect; No available router to destination.

The admin server and the managed servers should be up while running the command.

3.2.2 Editing the patchMaster.properties File

When specifying values in the patchMaster.properties file on Windows, ensure that / is used for file delimiters. You can use \ as an escape character. When a \ is used in the patchMaster.properties file, Patch Assistant warns you of the existence of the character and prompts if the patch operation should be continued ["y"/"n"]. If you do not desire prompting and have ensured the integrity of the patchMaster.properties file, then run the ant commands with the -noinput option.

3.2.3 Patching the Schema for Oracle Internet Directory

While patching the schema for Oracle Internet Directory, ensure that you specify only OID as the parameter for the patchMaster.Componentlist property in the patchMaster.properties file.

3.2.4 Changing the patchmaster.ValidationErrorContinue Property

By default, the patchMaster.ValidationErrorContinue file appears as patchmaster.ValidationErrorContinue. When you run this property, an error occurs.

Therefore, if you are using this property, replace the default property with patchMaster.ValidationErrorContinue before running Patch Assistant.

3.2.5 Changing the Default Setting for Validation Tasks

Patch Assistant validates the properties specified in the patchMaster.properties file. Additionally it performs the following validation tasks:

- Verify whether the potential source, target home, and instance paths exist.

- Verify locations to discover it they are an instance, home, and so on.

- Validate individual migration task. For example, if you are migrating a domain, then schema-based properties are not required. If the schema-based properties are specified, be sure to set the complete and proper set of schema-based properties.

- Attempts to recognize exceptions to specific components. For example, if Oracle Internet Directory is solely specified as the component being patched, then the property patchMaster.Schemaprefix is not necessary. However, if other components are being patched, then it is assumed that patchMaster.Schemaprefix is a necessary part of schema property validation.

If you want to continue with the Patch Assistant task after a validation error occurs, then you can open the patchMaster.properties file (Located in your patchMaster directory) in a text editor, and change the value to true for the patchMaster.ValidationErrorContinue property (The default value is false). Alternatively, you can use the Ant command-line utility to override the properties set in the patchMaster.properties file. You must specify the required property on the command line as follows:

ant-DpatchMaster.ValidationErrorContinue

3.2.6 Severe Error When Running the execute-sql-rcu Macro

When running the execute-sql-rcu macro, you may see the following error message, while the SQL script is still running:

[java] SEVERE: Error while registering Oracle JDBC Diagnosability MBean.
[java] java.security.AccessControlException: access denied (javax.management.MBeanTrustPermission register)

To resolve this error, you must grant the register permission by adding the following syntax to the java.policy file (Located at JAVA_HOME/jre/lib/security in UNIX and JAVA_HOME\jre\lib\security in Windows):

.
grant codeBase "file:${PATCH-MASTER-HOME}/lib/*.jar" {
permission javax.management.MBeanTrustPermission "register";
};

Note:
Ensure that you replace {PATCH-MASTER-HOME} with your home path.

3.2.7 Machine Names Do Not Appear in the Oracle WebLogic Server Administration Console

After running Patch Assistant, you cannot see the list of machines (Machine-0 and Machine-1) configured during 11.1.1.1.0 and 11.1.1.2.0, in the Oracle WebLogic Server Administration Console. After migrating to 11.1.1.2.0, you must re-enter the machine names using the Oracle WebLogic Server Administration Console. For more information, see Create and configure machines topic in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.

3.2.8 Using the Oracle BAM 11g Prepackaged Samples After Migrating from 11.1.1.1.0

If you are using the Oracle BAM 11g sample applications, refer to the following sections for information about using the samples after migrating from Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0):

- Section 3.2.8.1, "Configuring the Oracle BAM 11g Samples After Migrating from 11.1.1.1.0"

- Section 3.2.8.2, "Using the Foreign Exchange Sample After Migrating from 11.1.1.1.0"

For more information about the Oracle BAM 11g samples, see Section 3.1.3.5.1, "General Information About the Oracle BAM Samples".

3.2.8.1 Configuring the Oracle BAM 11g Samples After Migrating from 11.1.1.1.0

After you migrate from Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) to 11g Release 1 (11.1.1.2.0), be sure to run the proper setup script for setting up samples. Specifically, you must run the recreate script instead of the setup script.

For more information, see the readme file for each of the Oracle BAM 11g samples.

3.2.8.2 Using the Foreign Exchange Sample After Migrating from 11.1.1.1.0

After you run the recreate script to set up the Foreign Exchange sample after migrating from 11.1.1.1.0, you might experience the following error when you open the report (Shared Reports/Demos/Foreign Exchange):

The "Trade Volume" has an error:
CACHEEXCEPTION_NULL_NULL_NULL
Message:BAM-01274: The field ID 1 is not recognized.

To fix this problem, perform the following steps:

1. Open Active Studio.

2. Open the report:

Shared Reports/Demos/Foreign Exchange/SLAViolation Report

3. Click Edit.

4. Select the Trade Volume view and click Edit View.

5. In the Fields tab under Group By, select the field GroupBy.

6. Go to the Surface Prompts tab.

7. From the Display in drop-down menu, in select View Title.

8. Click Apply and save the report.

Visit the Oracle BAM samples page on OTN regularly to obtain updated samples and more information about the Oracle BAM sample applications.

3.3 Documentation Errata for Upgrade

This section provides documentation errata for the following guides:

- Section 3.3.1, "Documentation Errata for the Oracle Fusion Middleware Upgrade Guide for Java EE"

3.3.1 Documentation Errata for the Oracle Fusion Middleware Upgrade Guide for Java EE

This section contains documentation errata for the Oracle Fusion Middleware Upgrade Guide for Java EE. It contains the following sections:

- Section 3.3.1.1, "Clarification of Post-Upgrade Tasks for SSL-Enabled Oracle HTTP Server"

3.3.1.1 Clarification of Post-Upgrade Tasks for SSL-Enabled Oracle HTTP Server

Section 7.5.2, "Verifying and Updating the Oracle HTTP Server and Oracle Web Cache Ports After Upgrade" in the Oracle Fusion Middleware Upgrade Guide for Java EE provides information about additional post-upgrade steps you must perform for Oracle HTTP Server in some situations.

Specifically, if you decide to use the new ports defined for your Oracle Fusion Middleware 11g installation, rather than ports used for your Oracle Application Server 10g installation, then you should verify the listening ports, origin servers, site definitions, and site-to-server mapping settings, and make changes if appropriate.

This section fails to mention that you should perform this task even if the Oracle HTTP Server instance and Oracle Web Cache instance reside in the same Oracle home and you upgrade them together.

For example, if you have enabled end-to-end SSL in your 10g environment, then you must edit the ssl.conf file in the upgraded Oracle home to ensure that the ServerName entry in the Oracle HTTP Server 11g ssl.conf file is correct. Locate the ssl.conf file in the Oracle Fusion Middleware 11g Oracle home, and verify that the ServerName directive is set to the 11g Oracle Web Cache host and listening port:

For example:

ServerName testbox01.example.com:443

4 Oracle Fusion Middleware Administration

This chapter describes issues associated with Oracle Fusion Middleware administration. It includes the following topics:

- Section 4.1, "General Issues and Workarounds"

- Section 4.2, "Configuration Issues and Workarounds"

- Section 4.3, "Documentation Errata for the Oracle Fusion Middleware Administrator's Guide"

Note:
This chapter contains issues you might encounter while administering any of the Oracle Fusion Middleware products.
Be sure to review the product-specific release note chapters elsewhere in this document for any additional issues specific to the products you are using.

4.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topics:

- Section 4.1.1, "Clarification About Path for OPMN"

- Section 4.1.2, "Fusion Middleware Control May Return Error in Mixed IPv6 and IPv4 Environment"

- Section 4.1.3, "Deploying JSF Applications"

- Section 4.1.4, "Limitations in Moving from Test to Production"

- Section 4.1.5, "Limitations in Moving Oracle Business Process Management from Test to Production Environment"

- Section 4.1.6, "Message Returned with Incorrect Error Message Level"

4.1.1 Clarification About Path for OPMN

OPMN provides the opmnctl command. The executable file is located in the following directories:

- ORACLE_HOME/opmn/bin/opmnctl: The opmnctl command from this location should be used only to create an Oracle instance or a component for an Oracle instance on the local system. Any opmnctl commands generated from this location should not be used to manage system processes or to start OPMN.
On Windows, if you start OPMN using the opmnctl start command from this location, OPMN and its processes will terminate when the Windows user has logged out.

- ORACLE_INSTANCE/bin/opmnctl: The opmnctl command from this location provides a per Oracle instance instantiation of opmnctl. Use opmnctl commands from this location to manage processes for this Oracle instance. You can also use this opmnctl to create components for the Oracle instance.
On Windows, if you start OPMN using the opmnctl start command from this location, it starts OPMN as a Windows service. As a result, the OPMN parent process, and the processes which it manages, persist after the MS Windows user has logged out.

4.1.2 Fusion Middleware Control May Return Error in Mixed IPv6 and IPv4 Environment

If your environment contains both IPv6 and IPv4 network protocols, Fusion Middleware Control may return an error in certain circumstances.

If the browser that is accessing Fusion Middleware Control is on a host using the IPv4 protocol, and selects a control that accesses a host using the IPv6 protocol, Fusion Middleware Control will return an error. Similarly, if the browser that is accessing Fusion Middleware Control is on a host using the IPv6 protocol, and selects a control that accesses a host using the IPv4 protocol, Fusion Middleware Control will return an error.

For example, if you are using a browser that is on a host using the IPv4 protocol and you are using Fusion Middleware Control, Fusion Middleware Control returns an error when you navigate to an entity that is running on a host using the IPv6 protocol, such as in the following situations:

- From the Oracle Internet Directory home page, you select Directory Services Manager from the Oracle Internet Directory menu. Oracle Directory Services Manager is running on a host using the IPv6 protocol.

- From a Managed Server home page, you click the link for Oracle WebLogic Server Administration Console, which is running on IPv6.

- You test Web Services endpoints, which are on a host using IPv6.

- You click an application URL or Java application which is on a host using IPv6.

To work around this issue, you can add the following entry to the /etc/hosts file:

nnn.nn.nn.nn  myserver-ipv6 myserver-ipv6.example.com

In the example, nnn.nn.nn.nn is the IPv4 address of the Administration Server host, myserver.example.com.

4.1.3 Deploying JSF Applications

Some JSF applications may experience a memory leak due to incorrect Abstract Window Toolkit (AWT) application context classloader initialization in the Java class library. Setting the oracle.jrf.EnableAppContextInit system property to true will attempt eager initialization of the AWT application context classloader to prevent this leak from occurring. By default, this property is set to false.

4.1.4 Limitations in Moving from Test to Production

Note the following limitations in moving from test to production:

- If your environment includes Oracle WebLogic Server which you have upgraded from one release to another (for example from 10.3.4 to 10.3.5), the pasteConfig scripts fails with the following error:

Oracle_common_home/bin/unpack.sh line29:
WL_home/common/bin/unpack.sh No such file or directory

To work around this issue, edit the following file:

MW_HOME/utils/uninstall/WebLogic_Platform_10.3.5.0/WebLogic_Server_10.3.5.0_Core_Application_Server.txt file

Add the following entries:

/wlserver_10.3/server/lib/unix/nodemanager.sh
/wlserver_10.3/common/quickstart/quickstart.cmd
/wlserver_10.3/common/quickstart/quickstart.sh
/wlserver_10.3/uninstall/uninstall.cmd
/wlserver_10.3/uninstall/uninstall.sh
/utils/config/10.3/setHomeDirs.cmd
/utils/config/10.3/setHomeDirs.sh

- When you are moving Oracle Virtual Directory, the Oracle instance name in the source environment cannot be the same as the Oracle instance name in the target environment. The Oracle instance name in the target must be different than the name in the source.

- After you move Oracle Virtual Directory from one host to another, you must add a self-signed certificate to the Oracle Virtual Directory keystore and EM Agent wallet on Host B. Take the following steps:

1. Set the ORACLE_HOME and JAVA_HOME environment variables.

2. Delete the existing self-signed certificate:

$JAVA_HOME/bin/keytool -delete -alias serverselfsigned
-keystore ORACLE_INSTANCE/config/OVD/ovd_component_name/keystores/keys.jks
-storepass OVD_Admin_password

3. Generate a key pair:

$JAVA_HOME/bin/keytool -genkeypair
-keystore ORACLE_INSTANCE/config/OVD/ovd_component_name/keystores/keys.jks
-storepass OVD_Admin_password -keypass OVD_Admin_password -alias serverselfsigned
-keyalg rsa -dname "CN=Fully_qualified_hostname,O=test"

4. Export the certificate:

$JAVA_HOME/bin/keytool -exportcert
-keystore ORACLE_INSTANCE/config/OVD/ovd_component_name/keystores/keys.jks
-storepass OVD_Admin_password -rfc -alias serverselfsigned
-file ORACLE_INSTANCE/config/OVD/ovd_component_name/keystores/ovdcert.txt

5. Add a wallet to the EM Agent:

ORACLE_HOME/../oracle_common/bin/orapki wallet add
-wallet ORACLE_INSTANCE/EMAGENT/EMAGENT/sysman/config/monwallet
-pwd EM_Agent_Wallet_password -trusted_cert
-cert ORACLE_INSTANCE/config/OVD/ovd_component_name/keystores/ovdcert.txt

6. Stop and start the Oracle Virtual Directory server.

7. Stop and start the EM Agent.

- The copyConfig operation fails if you are using IPv6 and the Managed Server listen address is not set.
To work around this problem, set the Listen Address for the Managed Server in the Oracle WebLogic Server Administration Console. Navigate to the server. Then, on the Settings for server page, enter the Listen Address. Restart the Managed Servers.

- When you are moving Oracle Platform Security and you are using an LDAP store, the LDAP store on the source environment must be running and it must be accessible from the target during the pasteConfig operation.

- The copyConfig script works only with non-SSL ports. Because of this, ensure that non-SSL ports are enabled for all Managed Servers and the Administration Server.

Note that if the administration port feature is enabled for the source Oracle WebLogic Server domain, you must disable it first before running copyConfig as it prevents the usage of non-SSL ports for administrative tasks.

For information about the administration port, see "Administration Port and Administrative Channel" in Oracle Fusion Middleware Configuring Server Environments for Oracle WebLogic Server 10.3.6.

- The movement scripts do not support moving Oracle Identity Manager to another environment, either through the movement scripts or manual steps. In addition, if Oracle Identity Manager is part of the source environment of other components, the movement scripts for that environment will fail. This restriction applies to all 11.1.1 releases of Oracle Identity Manager.

- For Oracle Business Activity Monitoring, if there are remote servers in the test environment and you do not use shared disks, the copyConfig and pasteConfig scripts will fail. In addition, if Oracle BAM is part of the source domain that you are moving, the scripts will fail. For example, if Oracle BAM is part of a domain that contains the SOA Infrastructure and Oracle BPEL Process Manager, the copyConfig and pasteConfig scripts will fail.
To move components other than Oracle BAM move the BAM_t2p_registration.xml file from the following directory, into any other directory:

SOA_ORACLE_HOME/clone/provision

Then, to move Oracle BAM, take the following steps:

1. At the source, export the ORACLEBAM database schema, using the following commands (ORACLE_HOME is the Oracle home for the Oracle Database):

ORACLE_HOME/bin/sqlplus "sys/password as sysdba"
create or replace directory directory as 'path';
grant read,write on DIRECTORY directory to oraclebam;
exit;

ORACLE_HOME/bin/expdp userid=oraclebam/bam@connect_id
directory=directory dumpfile=orabam.dmp
schemas=oraclebam logfile=oraclebam_date.log

See Also:
"Overview of Oracle Data Pump" and other chapters on Oracle Data Pump in Oracle Database Utilities

The Oracle BAM objects, such as reports, alerts, and data definitions from the source environment are exported.

2. At the target, import the ORACLEBAM database schema that you exported from the source environment, using the following commands (ORACLE_HOME is the Oracle home for the Oracle Database):

ORACLE_HOME/bin/impdp userid=system/password dumpfile=ORACLEBAM.DMP
remap_schema=oraclebam:oraclebam TABLE_EXISTS_ACTION=replace
ORACLE_HOME/bin/sqlplus "sys/password as sysdba"
alter user oraclebam account unlock;
alter user oraclebam identified by bam;

Note that impdp may report the following errors:

- ORA-00959: tablespace <source tablespace> does not exist.
You can fix this error by creating the tablespace in the import database before the import or use REMAP_TABLESPACES to change the tablespace referenced in the table definition to a tablespace in the import database.

- You may see failure with restoring index statistics if you use an Oracle database version earlier than 11.2.0.2. You can work around this issue by rebuilding the index statistics after import.

3. Restart the Oracle Business Activity Monitoring Managed Server.

- When you are moving Oracle Platform Security Services and the data is moving from LDAP to LDAP, the source and target LDAP domain component hierarchy must be same. If it is not, the Oracle Platform Security Services data movement will fail. For example, if the source is hierarchy is configured as dc=us,dc=com, the target LDAP must have the same domain component hierarchy.

- Moving Oracle Access Manager may fail.

4.1.5 Limitations in Moving Oracle Business Process Management from Test to Production Environment

Note the following limitations when moving Oracle Business Process Management from a test environment to a production environment:

- When you move Oracle Business Process Management from a test environment to a production environment as described in the Task "Move Oracle Business Process Management to the New Production Environment" in the Oracle Fusion Middleware Administrator's Guide, Oracle Business Process Management Organization Units are not imported.
To work around this issue, you must re-create the Organization Units in the production environment. In addition, if any Organization associations with the Calendar rule for the Role exist in the test environment, you must re-create them, using the Roles screen.

For information, see "Working with Organizations" in the Oracle Fusion Middleware Modeling and Implementation Guide for Oracle Business Process Management.

- Oracle recommends that you move artifacts and data into a new, empty production environment. If the same artifacts are present or some data has been updated on the production environment, the procedure does not update those artifacts.

4.1.6 Message Returned with Incorrect Error Message Level

In Fusion Middleware Control, when you select a metadata repository, the following error messages are logged:

Partitions is NULL
Partitions size is 0

These messages are logged at the Error level, which is incorrect. They should be logged at the debug level, to provide information.

4.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

- Section 4.2.1, "Must Stop Oracle SOA Suite Managed Server Before Stopping soa-infra"

- Section 4.2.2, "Fusion Middleware Control Does Not Keep Column Preferences in Log Viewer Pages"

- Section 4.2.3, "Topology Viewer Does Not Display Applications Deployed to a Cluster"

- Section 4.2.4, "Changing Log File Format"

- Section 4.2.5, "SSL Automation Tool Configuration Issues"

4.2.1 Must Stop Oracle SOA Suite Managed Server Before Stopping soa-infra

Using Fusion Middleware Control, if you stop a Oracle SOA Suite Managed Server before you stop soa-infra, then you start the Managed Server, the soa-infra application is not restarted automatically. If you try to restart the soa-infra, you will received an error. When you encounter the problem, you cannot close the dialog box in the browser, so you cannot take any further actions in Fusion Middleware Control.

To avoid this situation, you should stop the Managed Server, which stops all applications, including the soa-infra application. To start the Managed Server and the soa-infra, start the Managed Server.

To close the browser dialog box, enter the following URL in your browser:

http://host:port/em

4.2.2 Fusion Middleware Control Does Not Keep Column Preferences in Log Viewer Pages

In Fusion Middleware Control, you can reorder the columns in the pages that display log files and log file messages. However, if you navigate away from the page and then back to it, the columns are set to their original order.

4.2.3 Topology Viewer Does Not Display Applications Deployed to a Cluster

In Fusion Middleware Control, the Topology Viewer does not display applications that are deployed to a cluster.

4.2.4 Changing Log File Format

When you change the log file format note the following:

- When you change the log file format from text to xml, specify the path, but omit the file name. The new file will be named log. xml.

- When you change the log file format from xml to text, specify both the path and the file name.

4.2.5 SSL Automation Tool Configuration Issues

The following issues have been observed when using the SSL Automation tool:

- The script creates intermediate files that contain passwords in clear text. If the script fails, these files might not be removed. After a script failure, delete all files under the rootCA directory.

- If Oracle Internet Directory password policy is enabled, passwords entered for wallet or keystore fail if they violate the policy.

- Before you run the script, you must have JDK 1.6 installed and you must have JAVA_HOME set in your environment.

- If the Oracle Virtual Directory configuration script fails, check the run log or enable debug for the shell script to view specific errors. If the error message looks similar to this, rerun the script with a new keystore name:

WLSTException: Error occured while performing cd : Attribute
oracle.as.ovd:type=component.listenersconfig.sslconfig,name=LDAP SSL
Endpoint,instance=%OVD_INSTANCE%,component=ovd1 not found

4.3 Documentation Errata for the Oracle Fusion Middleware Administrator's Guide

The following section describes documentation errata for the Oracle Fusion Middleware Administrator's Guide:

- Section 4.3.1, "Combining All Oracle Homes in a Single Inventory File"

- Section 4.3.2, "Correction to Link About Supported Databases for MDS."

4.3.1 Combining All Oracle Homes in a Single Inventory File

All Oracle homes in the Middleware home on the source environment must be registered in the same Oracle inventory. If you have installed multiple components under the same Middleware home, but used different Oracle inventory locations, the scripts are not able to detect all of the Oracle homes.

To work around this issue, take the following steps:

1. Create a new oraInst.loc pointing to the inventory to which you want to register, using the following commands:

cat oraInst.loc
inventory_loc=new_oraInst_loc_location
inst_group=g900

2. Detach the Oracle Home from its current inventory:

cd ORACLE_HOME/oui/bin
./detachHome.sh -invPtrLoc ORACLE_HOME/oraInst.loc

3. Attach the Oracle Home to the new inventory by passing new oraInst.loc created in step 1:

./attachHome.sh -invPtrLoc new_oraInst_loc_location

Do this for every Oracle home in the Middleware home.

4. Set the necessary dependencies between Oracle homes if required (for example most Oracle homes depend on oracle_common). The dependencies are required when you uninstall. You can check the existing dependencies from the old inventory by checking the file oraInventory/ContentsXML/inventory.xml. The following shows an example of the file:

<?xml version="1.0" standalone="yes" ?>
<!-- Copyright (c) 1999, 2010, Oracle. All rights reserved. -->
<!-- Do not modify the contents of this file by hand. -->
<VERSION_INFO>
<SAVED_WITH>11.1.0.9.0</SAVED_WITH>
<MINIMUM_VER>2.1.0.6.0</MINIMUM_VER>
</VERSION_INFO>
<HOME_LIST>
<HOME NAME="OH339778486" LOC="/scratch/oracle/11gMW/oracle_common" TYPE="O" IDX="1">
<REFHOMELIST>
<REFHOME LOC="/scratch/oracle/11gMW/Oracle_WT1"/>
</REFHOMELIST>
</HOME>
<HOME NAME="OH299443989" LOC="/scratch/oracle/11gMW/Oracle_WT1" TYPE="O"
IDX="2">
<DEPHOMELIST>
<DEPHOME LOC="/scratch/oracle/11gMW/oracle_common"/>
</DEPHOMELIST>
</HOME>
</HOME_LIST>
<COMPOSITEHOME_LIST>
</COMPOSITEHOME_LIST>
</INVENTORY>

5. Run the following command to set up dependencies. Note that this is not mandatory for the movement scripts to work, but is needed when you uninstall.

./runInstaller -updateHomeDeps
"HOME_DEPENDENCY_LIST={/scratch/oracle/11gMW/Oracle_WT1:/scratch/oracle/11gMW/
oracle_common}" -invPtrLoc ~/oraInst.loc

4.3.2 Correction to Link About Supported Databases for MDS

The section "Databases Supported by MDS" in the Oracle Fusion Middleware Administrator's Guide contains an incorrect link to Oracle Fusion Middleware System Requirements and Specifications. The correct link is:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html

4.3.3 Clarification of Move Plan Properties for Oracle WebCenter Content

For the Oracle WebCenter Content server or Oracle WebCenter Content: Records, you have two options for moving the component:

- copy: This option copies the entire source system, including configuration and data, to the target system. Although this is the default, Oracle does not recommend using this option because it moves test data, which might not be appropriate for your environment.

- init: This option initializes a new Content Server or Records instance in the target system. It does not move data.

5 Oracle Enterprise Manager Fusion Middleware Control

This chapter describes issues associated with Fusion Middleware Control. It includes the following topics:

- Section 5.1, "General Issues and Workarounds"

- Section 5.2, "Documentation Errata"

Note:
This chapter contains issues you might encounter while using Fusion Middleware Control to manage any of the Oracle Fusion Middleware products.
Be sure to review the product-specific release note chapters elsewhere in this document for any additional issues specific to the products you are using.

5.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topic:

- Section 5.1.1, "Product Behavior After a Session Timeout"

- Section 5.1.2, "Fixing Errors Displayed When Selecting the TopLink Sessions Command in Fusion Middleware Control"

- Section 5.1.3, "Verifying the DISPLAY Variable to Correct Problems Displaying Graphics"

- Section 5.1.4, "Incomplete Information Available on the MDS Configuration Page"

- Section 5.1.5, "Exceptions When Starting Oracle Web Cache After Accessing Configuration Pages from Oracle Enterprise Manager Fusion Middleware Control"

- Section 5.1.6, "Table Display Problems When Using Some Language Variants"

- Section 5.1.7, "Problems When Internet Explorer 7 is Configured to Open Pop-Up Windows in a New Tab."

- Section 5.1.8, "Additional Fusion Middleware Control Release Notes"

- Section 5.1.9, "Problem with Performance Charts After Moving a Chart Region"

- Section 5.1.10, "Memory Issue When Configuring SOA on Microsoft Windows x64 (64-Bit)"

- Section 5.1.11, "Display Problems When Running JDK 160_18 on Intel Systems that Support the SSE4.2 Instruction Set"

- Section 5.1.12, "Adobe Flash Plugin Required When Displaying Fusion Middleware Control in the Apple Safari Browser"

- Section 5.1.13, "Unable to Access Fusion Middleware Control After Installing the Oracle Identity Management 11.1.1.4.0 Patch Set"

- Section 5.1.14, "Error Message on Deleting the Shared Folder After Scale-Out"

- Section 5.1.15, "Coreapplication Process for Oracle Business Intelligence Reported as Down in Fusion Middleware Control"

- Section 5.1.16, "Online Help Error Message in Enterprise Manager Log Files Can Be Ignored"

- Section 5.1.17, "Incorrect or Missing Metrics Help Information"

- Section 5.1.18, "Error When Accessing the Entry Point URL for the NonJ2EEManagement Internal Application"

5.1.1 Product Behavior After a Session Timeout

For security purposes, your sessions with the Fusion Middleware Control will time out after a predefined period of inactivity, and you will be asked to log in to the console again. In most cases, you are returned to the page you had displayed before the session timed out.

However, in some circumstances, such as when you are using the Fusion Middleware Control deployment wizards, you will not be returned the same location in the product after you log in. In those cases, you will have to navigate to the specific Fusion Middleware Control page you were using before the session timed out.

5.1.2 Fixing Errors Displayed When Selecting the TopLink Sessions Command in Fusion Middleware Control

In Fusion Middleware Control, you can view the Oracle TopLink management pages by selecting TopLink Sessions from the Application Deployment menu.

However, if you receive an error message when you select this command, you can remedy the problem by adding one or both of the following MBean system properties, as follows

On Windows operating systems:

rem set JAVA_OPTIONS=%JAVA_OPTIONS% -Declipselink.register.dev.mbean=true
rem set JAVA_OPTIONS=%JAVA_OPTIONS% -Declipselink.register.run.mbean=true

On UNIX operating systems:

JAVA_OPTIONS="${JAVA_OPTIONS} -Declipselink.register.dev.mbean=true"
JAVA_OPTIONS="${JAVA_OPTIONS} -Declipselink.register.run.mbean=true"

For more information, see the following URL on the Eclipse WIKI Web site:

http://wiki.eclipse.org/Integrating_EclipseLink_with_an_Application_Server_(ELUG)#How_to_Integrate_JMX

5.1.3 Verifying the DISPLAY Variable to Correct Problems Displaying Graphics

The graphics subsystem for the Fusion Middleware Control generates some of its graphics on demand, and if the DISPLAY environment variable is set, Fusion Middleware Control tries to open the specified DISPLAY environment.

If Fusion Middleware Control fails to start due to graphics errors, check to see whether the DISPLAY environment variable is set to a proper DISPLAY environment.

If the DISPLAY environment variable is set incorrectly, unset the DISPLAY environment variable. Then restart Fusion Middleware Control.

5.1.4 Incomplete Information Available on the MDS Configuration Page

After deploying a Oracle SOA Suite application that requires Oracle Metadata Services (MDS), in some rare circumstances, you may find that the MDS configuration page for the application does not contain complete information about the MDS repository.

To address this problem, use the Metadata Repositories page to register the repository again. For more information, see "Create and Register an MDS Repository" in the Fusion Middleware Control online help.

5.1.5 Exceptions When Starting Oracle Web Cache After Accessing Configuration Pages from Oracle Enterprise Manager Fusion Middleware Control

To start, stop, or restart Oracle Web Cache from Fusion Middleware Control, from the Web Cache menu, you can choose Control, and then Start Up, Shut Down, or Restart.

If you select Shut Down, and then Start Up on a configuration page, Fusion Middleware Control may return exception errors. If these errors occur in your environment, perform the operations from Web Cache Home page.

5.1.6 Table Display Problems When Using Some Language Variants

When you use Fusion Middleware Control in some non-English language environments, some of the tables on the component home pages display incorrectly. For example, some rows of the table appear to be merged and without content.

These issues can be safely ignored, since no data on the pages is hidden. The table cells that appear incorrectly do not contain performance data or other information.

5.1.7 Problems When Internet Explorer 7 is Configured to Open Pop-Up Windows in a New Tab

If you configure Microsoft Internet Explorer 7 so it always displays pop-up windows in a new browser tab, then you may experience problems using Fusion Middleware Control. For example, in some cases, Enterprise Manager content displays in a new tab as expected, but Fusion Middleware Control stops responding to mouse clicks. The only way to continue working is to close the tab.

To avoid this problem, use the Internet Options dialog box in Internet Explorer to disable the option for displaying pop-up windows in a new tab.

5.1.8 Additional Fusion Middleware Control Release Notes

Refer to Chapter 4, "Oracle Fusion Middleware Administration" for additional Fusion Middleware Control release notes.

Additional Fusion Middleware Control release notes are also included in the component chapters of the Release Notes.

5.1.9 Problem with Performance Charts After Moving a Chart Region

Oracle Enterprise Manager Fusion Middleware Control provides performance charts on many of the component home pages. For example, it provides charts that display the current response and load metrics, as well as the CPU and memory usage.

If you move one of these charts to a new location on the home page, then sometimes the Table View link (which provides a tabular view of the data) does not work properly and the chart might stop refreshing automatically.

To fix this problem, click the refresh icon at the top, right corner of the page to refresh the page.

5.1.10 Memory Issue When Configuring SOA on Microsoft Windows x64 (64-Bit)

This is a known issue in Release 11.1.1.3.0 only. On configuring the SOA domain with Sun JDK, Admin Server and Managed Server fail to start showing the following error in the Managed server logs:

Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine

On configuring the SOA domain with JRockit JDK, Admin Server and Managed Server start but on logging in to Oracle Enterprise Manager, it shows an error and displays an incorrect status.

To work around this issue, change the memory size in setSOADomainEnv.cmd file by performing the following steps:

- Put the following text in a comment using REM command:

REM set PORT_MEM_ARGS=-Xms768m -Xmx1536m //

- Add the following line to reduce heap size:

set PORT_MEM_ARGS=-Xms512m -Xmx1024m //

5.1.11 Display Problems When Running JDK 160_18 on Intel Systems that Support the SSE4.2 Instruction Set

Some of the newer Intel-based computers support the SSE4.2 instruction set. If you are using the 160_18 version of the Java Development Kit (JDK) on one of these computers, then you might see some display issues in the Oracle Enterprise Manager Fusion Middleware Control.

This is related to the following issue on the Sun Developer Network (SDN):

http://bugs.sun.com/view_bug.do?bug_id=6875866

In particular, when using Fusion Middleware Control, you might experience some font size and alignment issues, and an error similar to the following appears in the server log file:

Servlet failed with Exception
java.lang.StringIndexOutOfBoundsException: String index out of range

To remedy this problem:

1. Locate and open the setDomainEnv configuration file in your Oracle WebLogic Server domain home.
For example:

DOMAIN_HOME/bin/setDomainEnv.sh

For example:

DOMAIN_HOME\bin\setDomainEnv.cmd

2. Add the following to the JAVA_OPTIONS entry in the setDomainEnv file and save your changes:

-XX:-UseSSE42Intrinsics

For example:

JAVA_OPTIONS="${JAVA_OPTIONS} ${JAVA_PROPERTIES}
-Dwlw.iterativeDev=${iterativeDevFlag} -Dwlw.testConsole=${testConsoleFlag}
-Dwlw.logErrorsToConsole=${logErrorsToConsoleFlag} -XX:-UseSSE42Intrinsics"

3. Locate the following directory in your Oracle WebLogic Server domain home:

DOMAIN_HOME/servers/AdminServer/tmp/_WL_user/em/jmb4hf/public/adf/styles/cache/

DOMAIN_HOME\servers\AdminServer\tmp\_WL_user\em\jmb4hf\public\adf\styles\cache\

4. Delete the style sheets (.css) files from the directory.

5. Restart the Oracle WebLogic Server domain.

6. Clear the cache in your Web browser.

5.1.12 Adobe Flash Plugin Required When Displaying Fusion Middleware Control in the Apple Safari Browser

To use the Apple Safari browser to display Fusion Middleware Control, you must have the Adobe Flash browser plugin installed.

If you experience problems displaying graphics or other Fusion Middleware Control elements, download and install a newer version of the plugin from the Adobe Web site.

5.1.13 Unable to Access Fusion Middleware Control After Installing the Oracle Identity Management 11.1.1.4.0 Patch Set

After you install the Oracle Fusion Middleware 11g Release 1 (11.1.1.4.0) patch set, you might experience problems when accessing the Fusion Middleware Control pages used to manage the Oracle Identity Management components.

Specifically, an error similar to the following appears in the Administration Server log files:

[ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default
(self-tuning)'] [userId: <anonymous>] [ecid:
0000In^zrbUF8DQ6ubU4UH1D1qXF00000s,0] [APP: em] [[
oracle.adf.controller.ControllerException: ADFC-00025: The ADF controller has
not been successfully initalized.

If you experience this problem, restart the Administration Server. After the restart, you should be able to log in and access the Fusion Middleware Control pages.

5.1.14 Error Message on Deleting the Shared Folder After Scale-Out

If Oracle Essbase is configured, then the Shared Folder Path field is displayed in the Essbase Agents region on the Failover page of the Availability tab for the Business Intelligence node in Fusion Middleware Control.

You use the Shared Folder Path field when setting up a highly available Essbase deployment. The field specifies a shared location for Essbase configuration files, security files, and all applications and corresponding databases.

If you remove an existing value in the Shared Folder Path field and attempt to apply the change without specifying a replacement value, then the following error message is displayed:

OBI_SYSMAN_1261, "You must not delete the shared folder after a previous scaleout"

To continue, either specify a valid path to the shared location in the Shared Folder Path field, or discard the change.

5.1.15 Coreapplication Process for Oracle Business Intelligence Reported as Down in Fusion Middleware Control

In Fusion Middleware Control, the coreapplication process for Oracle Business Intelligence is erroneously displayed as not running (or "down") even when it is running (or "up"). For example, you might see an error message similar to the following one:

Restart All – Failed. Restart failed with 2 errors and 0 warnings. Problems reported by:coreapplication.

To work around this issue, wait for approximately five to ten minutes, then restart all processes in Fusion Middleware Control. The exact time to wait depends on the environment (for example, on the size of the repository and on the speed of the database connection).

5.1.16 Online Help Error Message in Enterprise Manager Log Files Can Be Ignored

When accessing specific topics in the online help table of contents for Oracle Enterprise Manager Fusion Middleware Control, an error message and a warning message might appear in the log files. These messages can be ignored.

Specifically, the following example shows an error messages that can appear in the AdminServer-diagnostic.log file. You can safely ignore these messages:

<Apr 15, 2012 12:58:15 PM PDT> <Error>
<oracle.help.web.rich.converter.RichTopicConverter> <BEA-000000> <JAR entry
loe.htm not found in
/scratch/pabharga/wls/oracle_common/doc/online_help/owcag/owcag_help.jar>
<Apr 15, 2012 12:58:15 PM PDT> <Warning>
<oracle.help.web.util.OHWLoggerUtils> <HELP-10055> <trying to access invalid
topic id owcag/loe.htm>

5.1.17 Incorrect or Missing Metrics Help Information

When you use Fusion Middleware Control to view metrics, you can obtain Help on the metrics. For this release, all metrics are described in Oracle Enterprise Manager Oracle Fusion Middleware Metric Reference Manual. Consult that manual for complete descriptions of metrics.

5.1.18 Error When Accessing the Entry Point URL for the NonJ2EEManagement Internal Application

When you apply an Oracle Fusion Middleware 11g patch set to an existing 11g Middleware home, you might be instructed to run the upgradenonj2eeapp script, which is required when you are patching Oracle Fusion Middleware 11g system components. For more information, see "Upgrading System Components" in the Oracle Fusion Middleware Patching Guide.

This script deploys an internal application called NonJ2EEManagement to your Oracle WebLogic Server domain. After you run the script, the NonJ2EEManagement application appears in the list of internal applications in Oracle Enterprise Manager Fusion Middleware Control.

If you attempt to navigate to the application home page of the NonJ2EEManagement application, and you click the URL for the entry point for the application, you will receive an error in your browser.

This is a known issue. The NonJ2EEManagement application, like many of the internal applications, does not have a valid context root or HTML entry point. It is used exclusively to facilitate the patching of system components in your Middleware home.

5.2 Documentation Errata

This section describes documentation errata. It includes the following topics:

- Section 5.2.1, "Search Unavailable for Some Embedded Administrator's Guides"

- Section 5.2.2, "Patching Section in the Fusion Middleware Control Online Help is Not Supported"

- Section 5.2.3, "Help Topic for Secure Sockets Layer Tab Needs Updated Description for WebLogic CA Certificate"

5.2.1 Search Unavailable for Some Embedded Administrator's Guides

Search is unavailable for the following embedded administrator's guides in the Fusion Middleware Control help system:

- Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation

- Oracle Fusion Middleware System Administrator's Guide for Content Server for installations with Oracle Enterprise Content Management Suite

5.2.2 Patching Section in the Fusion Middleware Control Online Help is Not Supported

The Fusion Middleware Control online help system includes the contents of the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition. In the Fusion Middleware Control online help, this guide includes Section 17.11, which describes patching the Oracle BI Presentation Catalog. This functionality is not supported in Release 11.1.1.5. The section is not included in the version of the guide that ships with Oracle BI EE or that is posted on the Oracle Technology Network.

5.2.3 Help Topic for Secure Sockets Layer Tab Needs Updated Description for WebLogic CA Certificate

An update is required in the Fusion Middleware Control help system for Oracle Business Intelligence. In the help topic for the Security page: Secure Sockets Layer tab, the Description for the WebLogic CA certificate element must include the following text:

Supported types are .der and .pem. Ensure that the certificate file has the correct extension.

6 Oracle Fusion Middleware High Availability and Enterprise Deployment

This chapter describes issues associated with Oracle Fusion Middleware high availability and enterprise deployment. It includes the following topics:

- Section 6.1, "General Issues and Workarounds"

- Section 6.2, "Configuration Issues and Workarounds"

- Section 6.3, "Testing Abrupt Failures of WebLogic Server When Using File Stores on NFS"

- Section 6.4, "Documentation Errata"

Note:
This chapter contains issues you might encounter while configuring any of the any of the Oracle Fusion Middleware products for high availability or an enterprise deployment.
Be sure to review the product-specific release note chapters elsewhere in this document for any additional issues specific to the products you are using.

6.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topics:

- Section 6.1.1, "Secure Resources in Application Tier"

- Section 6.1.2, "Accessing Web Services Policies Page in Cold Failover Environment"

- Section 6.1.3, "Timeout Settings for SOA Request-Response Operations are Not Propagated in a Node Failure"

- Section 6.1.4, "Very Intensive Uploads from I/PM to UCM May Require Use of IP-Based Filters in UCM Instead of Hostname-Based Filters"

- Section 6.1.5, "Use srvctl in 11.2 Oracle RAC Databases to Set Up AQ Notification and Server-side TAF"

- Section 6.1.6, "Failover Is Not Seamless When Creating Reports in Oracle BI Publisher"

- Section 6.1.7, "Cannot Save Agent When Oracle Business Intelligence Managed Server Fails Over"

- Section 6.1.8, "Installing Additional Oracle Portal, Forms, Reports, and Discoverer Instances After Upgrading Oracle Single Sign-On 10g to Oracle Access Manager 11g"

- Section 6.1.9, "JMS Instance Fails In a BI Publisher Cluster"

- Section 6.1.10, "Undelivered Records not Recovered During RAC Failover of Singleton SOA Server"

- Section 6.1.11, "Synchronous BPEL Process Issues"

6.1.1 Secure Resources in Application Tier

It is highly recommended that the application tier in the SOA Enterprise Deployment topology and the WebCenter Enterprise Deployment topology is protected against anonymous RMI connections. To prevent RMI access to the middle tier from outside the subset configured, follow the steps in "Configure connection filtering" in the Oracle WebLogic Server Administration Console Online Help. Execute all of the steps, except as noted in the following:

1. Do not execute the substep for configuring the default connection filter. Execute the substep for configuring a custom connection filter.

2. In the Connection Filter Rules field, add the rules that will allow all protocol access to servers from the middle tier subnet while allowing only http(s) access from outside the subnet, as shown in the following example:

nnn.nnn.0.0/nnn.nnn.0.0  * * allow
0.0.0.0/0 * * allow t3 t3s

6.1.2 Accessing Web Services Policies Page in Cold Failover Environment

In a Cold Failover Cluster (CFC) environment, the following exception is displayed when Web Services policies page is accessed in Fusion Middleware Control:

Unable to connect to Oracle WSM Policy Manager.
Cannot locate policy manager query/update service. Policy manager service
look up did not find a valid service.

To avoid this, implement one the following options:

- Create virtual hostname aliased SSL certificate and add to the key store.

- Add "-Dweblogic.security.SSL.ignoreHostnameVerification=true" to the JAVA_OPTIONS parameter in the startWeblogic.sh or startWeblogic.cmd files

6.1.3 Timeout Settings for SOA Request-Response Operations are Not Propagated in a Node Failure

In an active-active Oracle SOA cluster, when a node failure occurs, the timeout settings for request-response operations in receive activities are not propagated from one node to the other node or nodes. If a failure occurs in the server that scheduled these activities, they must be rescheduled with the scheduler upon server restart.

6.1.4 Very Intensive Uploads from I/PM to UCM May Require Use of IP-Based Filters in UCM Instead of Hostname-Based Filters

The "Adding the I/PM Server Listen Addresses to the List of Allowed Hosts in UCM" section in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Enterprise Content Management Suite and the "Adding the I/PM Server Listen Addresses to the List of Allowed Hosts in UCM" section in the Oracle Fusion Middleware High Availability Guide describe how to add hostname-based filters for Oracle I/PM managed server listen addresses to the list of allowed hosts in Oracle UCM.

When using hostname-based filters in Oracle UCM (config.cfg file) a high latency/performance impact may be observed in the system for very intensive uploads of documents from Oracle I/PM to Oracle UCM. This is caused by the reverse DNS lookup that is required in Oracle UCM to allow the connections from Oracle I/PM servers. Using hostname-based filters is recommended in preparation for configuring the system for Disaster Protection and to restore to a different host (since the configuration used is IP-agnostic when using hostname-based filters). However if the performance of the uploads needs to be improved, users can use instead IP-based filters. To do this:

1. Edit the file /u01/app/oracle/admin/domainName/ucm_cluster/config/config.cfg and remove or comment out:

SocketHostNameSecurityFilter=localhost|localhost.mydomain.com|ecmhost1vhn1|ecmhost2vhn1

AlwaysReverseLookupForHost=Yes

2. Add the IP addresses (listen address) of the WLS_IPM1 and WLS_IPM2 managed servers (ECMHOST1VHN1 and ECMHOST2VHN1, respectively) to the SocketHostAddressSecurityFilter parameter list as follows:

SocketHostAddressSecurityFilter=127.0.0.1|0:0:0:0:0:0:0:1|X.X.X.X|Y.Y.Y.

where X.X.X.X and Y.Y.Y.Y are the listen addresses of WLS_IPM1 and WLS_IPM2 respectively. Notice that 127.0.0.1 also needs to be added as shown above.

3. Restart the UCM servers.

6.1.5 Use srvctl in 11.2 Oracle RAC Databases to Set Up AQ Notification and Server-side TAF

Because of a known issue in 11.2 Oracle RAC databases, it is required to use srvctl to set up AQ notification and server-side TAF. Using DBMS_SQL packages will not work as expected.

Here is an example use of srvctl:

srvctl modify service -d orcl -s orclSVC -e SELECT -m BASIC -w 5 -z 5 -q TRUE

In the example:

orcl - Database Name

orclSVC - Service Name used by middleware component

SELECT - Failover type

BASIC - Failover method

5 - Failover delay

5 - Failover retry

TRUE - AQ HA notifications set to TRUE

Please refer to the Oracle 11.2 Oracle database documentation for detailed information about this command usage.

6.1.6 Failover Is Not Seamless When Creating Reports in Oracle BI Publisher

If you create a report in Oracle BI Publisher, and a Managed Server is failed over before the report is saved, the failover might not be seamless. For example, when you attempt to save the report, the system might not be responsive.

If this occurs, click one of the header links, such as Home or Catalog, to be redirected to the Oracle BI Publisher login page. Then, log in and create and save the report again.

6.1.7 Cannot Save Agent When Oracle Business Intelligence Managed Server Fails Over

If you create an agent in the Oracle Business Intelligence Web interface, and a Managed Server fails over before you save the agent, an error occurs when you try to save the agent.

To work around this issue, log out, then log back in to Oracle Business Intelligence and create the agent again.

6.1.8 Installing Additional Oracle Portal, Forms, Reports, and Discoverer Instances After Upgrading Oracle Single Sign-On 10g to Oracle Access Manager 11g

This issue occurs with Oracle Portal, Forms, Reports, and Discoverer 11g environments that have been upgraded from using Oracle Single-Sign On 10g to Oracle Access Manager 11g for authentication.

When performing subsequent Oracle Portal, Forms, Reports, and Discoverer 11g installations against the same environment where the initial Oracle Portal, Forms, Reports, and Discoverer 10g installation was upgraded to Oracle Access Manager, there are some requirements that must be met.

- For each subsequent Oracle Portal, Forms, Reports, and Discoverer 11g installation, you must maintain the original Oracle Single Sign-On 10g instance and keep it actively running--in addition to new Oracle Access Manager 11g instance--while the additional Oracle Portal, Forms, Reports, and Discoverer 11g installations are performed.
This is necessary because Oracle Portal, Forms, Reports, and Discoverer 11g cannot be installed directly against Oracle Access Manager 11g.

- After the subsequent classic installs are completed, the Oracle Single Sign-On 10g to Oracle Access Manager 11g upgrade procedure must be performed again. For more information, including an upgrade roadmap, see the Oracle Fusion Middleware Upgrade Guide for Oracle Identity and Access Management.
This procedure upgrades the new Oracle Portal, Forms, Reports, and Discoverer 11g instance to Oracle Access Manager 11g.

Note that these considerations apply only in an environment with Multiple Oracle Portal, Forms, Reports, and Discoverer 11g middle tiers that are installed or added to a your environment after the initial upgrade from Oracle Single Sign-On 10g to Oracle Access Manager 11g.

6.1.9 JMS Instance Fails In a BI Publisher Cluster

On rare occasions, a JMS instance is missing from a BI Publisher Scheduler cluster.

To resolve this issue, restart the BI Publisher application from the WebLogic Server Administration Console.

To restart your BI Publisher application:

1. Log in to the Administration Console.

2. Click Deployments in the Domain Structure window.

3. Select bipublisher(11.1.1).

4. Click Stop.

5. After the application stops, click Start.

6.1.10 Undelivered Records not Recovered During RAC Failover of Singleton SOA Server

If there is a RAC failover in a singleton server in a SOA RAC environment, recovery of undelivered records that appear recoverable in EM will fail.

6.1.11 Synchronous BPEL Process Issues

On a SOA cluster, the following scenarios are not supported:

- Synchronous BPEL process with mid-process receive.

- Synchronous BPEL process calling asynchronous services.

- Callback from synchronous processes.

6.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

- Section 6.2.1, "Fusion Middleware Control May Display Incorrect Status"

- Section 6.2.2, "Accumulated BPEL Instances Cause Performance Decrease"

- Section 6.2.3, "Extra Message Enqueue when One a Cluster Server is Brought Down and Back Up"

- Section 6.2.4, "Duplicate Unrecoverable Human Workflow Instance Created with Oracle RAC Failover"

- Section 6.2.5, "No High Availability Support for SOA B2B TCP/IP"

- Section 6.2.6, "WebLogic Administration Server on Machines with Multiple Network Cards"

- Section 6.2.7, "Additional Parameters for SOA and Oracle RAC Data Sources"

- Section 6.2.8, "Message Sequencing and MLLP Not Supported in Oracle B2B HA Environments"

- Section 6.2.9, "Credentials not Propagated for Transport Protocols in B2B"

- Section 6.2.10, "Use Fully-Qualified Hostnames when Configuring Front-end Hosts in High Availability Configurations"

- Section 6.2.11, "Managed Server goes into Suspended Status After Oracle RAC Failover"

- Section 6.2.12, "Primary/Secondary Configuration Section of the Availability Tab is Not Visible"

- Section 6.2.13, "Server Start Parameters Not Getting Set After Scaling Out the Oracle Business Intelligence Managed Server"

- Section 6.2.14, "Ensuring the Oracle HTTP Server Lock File is on a Local Drive"

- Section 6.2.15, "Recreating OSSO Agents that Point to the Load Balancer URL"

- Section 6.2.16, "Use Lower-Case Letters for GridLink Data Source RAC Service Name"

- Section 6.2.17, "Additional Steps Needed for Oracle RTD Request Forwarding to Work Correctly"

- Section 6.2.18, "Error INST-08075 Occurs When Scaling Out the BI System"

- Section 6.2.19, "First Defined RAC Instance Must Be Available On Domain Startup When Configuring with RAC Multi Data Source"

6.2.1 Fusion Middleware Control May Display Incorrect Status

In some instances, Oracle WebLogic Fusion Middleware Control may display the incorrect status of a component immediately after the component has been restarted or failed over.

6.2.2 Accumulated BPEL Instances Cause Performance Decrease

In a scaled out clustered environment, if a large number of BPEL instances are accumulated in the database, it causes the database's performance to decrease, and the following error is generated: MANY THREADS STUCK FOR 600+ SECONDS.

To avoid this error, remove old BPEL instances from the database.

6.2.3 Extra Message Enqueue when One a Cluster Server is Brought Down and Back Up

In a non-XA environment, MQSeries Adapters do not guarantee the only once delivery of the messages from inbound adapters to the endpoint in case of local transaction. In this scenario, if an inbound message is published to the endpoint, and before committing the transaction, the SOA server is brought down, inbound message are rolled back and the same message is again dequeued and published to the endpoint. This creates an extra message in outbound queue.

In an XA environment, MQ Messages are actually not lost but held by Queue Manager due to an inconsistent state. To retrieve the held messages, restart the Queue Manager.

6.2.4 Duplicate Unrecoverable Human Workflow Instance Created with Oracle RAC Failover

As soon as Oracle Human Workflow commits its transaction, the control passes back to BPEL, which almost instantaneously commits its transaction. Between this window, if the Oracle RAC instance goes down, on failover, the message is retried and can cause duplicate tasks. The duplicate task can show up in two ways - either a duplicate task appears in worklistapp, or an unrecoverable BPEL instance is created. This BPEL instance appears in BPEL Recovery. It is not possible to recover this BPEL instance as consumer, because this task has already completed.

6.2.5 No High Availability Support for SOA B2B TCP/IP

High availability failover support is not available for SOA B2B TCP/IP protocol. This effects primarily deployments using HL7 over MLLP. For inbound communication in a clustered environment, all B2B servers are active and the address exposed for inbound traffic is a load balancer virtual server. Also, in an outage scenario where an active managed server is no longer available, the persistent TCP/IP connection is lost and the client is expected to reestablish the connection.

6.2.6 WebLogic Administration Server on Machines with Multiple Network Cards

When installing Oracle WebLogic Server on a server with multiple network cards, always specify a Listen Address for the Administration Server. The address used should be the DNS Name/IP Address of the network card you wish to use for Administration Server communication.

To set the Listen Address:

1. In the Oracle WebLogic Server Administration Console, select Environment, and then Servers from the domain structure menu.

2. Click the Administration Server.

3. Click Lock and Edit from the Change Center to allow editing.

4. Enter a Listen Address.

5. Click Save.

6. Click Activate Changes in the Change Center.

6.2.7 Additional Parameters for SOA and Oracle RAC Data Sources

In some deployments of SOA with Oracle RAC, you may need to set parameters in addition to the out-of-the-box configuration of the individual data sources in an Oracle RAC configuration. The additional parameters are:

1. Add property oracle.jdbc.ReadTimeout=300000 (300000 milliseconds) for each data source.
The actual value of the ReadTimeout parameter may differ based on additional considerations.

2. If the network is not reliable, then it is difficult for a client to detect the frequent disconnections when the server is abruptly disconnected. By default, a client running on Linux takes 7200 seconds (2 hours) to sense the abrupt disconnections. This value is equal to the value of the tcp_keepalive_time property. To configure the application to detect the disconnections faster, set the value of the tcp_keepalive_time, tcp_keepalive_interval, and tcp_keepalive_probes properties to a lower value at the operating system level.

Note:
Setting a low value for the tcp_keepalive_interval property leads to frequent probe packets on the network, which can make the system slower. Therefore, the value of this property should be set appropriately based on system requirements.

For example, set tcp_keepalive_time=600 at the system running the WebLogic Server managed server.

Also, you must specify the ENABLE=BROKEN parameter in the DESCRIPTION clause in the connection descriptor. For example:

dbc:oracle:thin:@(DESCRIPTION=(enable=broken)(ADDRESS_LIST=(ADDRESS=(PRO
TOCOL=TCP)(HOST=node1-vip.mycompany.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_
NAME=example.com)(INSTANCE_NAME=orcl1)))

As a result, the data source configuration appears as follows:

<url>jdbc:oracle:thin:@(DESCRIPTION=(enable=broken)(ADDRESS_LIST=(ADDRESS=(PRO
TOCOL=TCP)(HOST=node1-vip.us.example.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=example.com)(INSTANCE_NAME=orcl1)))</url>
<driver-name>oracle.jdbc.xa.client.OracleXADataSource</driver-name>
<properties>
<property>
<name>oracle.jdbc.ReadTimeout</name>
<value>300000</value>
</property>
<property>
<name>user</name>
<value>jmsuser</value>
</property>
<property>
<name>oracle.net.CONNECT_TIMEOUT</name>
<value>10000</value>
</property>
</properties>

6.2.8 Message Sequencing and MLLP Not Supported in Oracle B2B HA Environments

Message sequencing and MLLP are not supported in Oracle B2B high availability (HA) environments.

6.2.9 Credentials not Propagated for Transport Protocols in B2B

The Oracle FMW credential store maintains usernames and passwords that you define for Transport protocols. If you use the default file store for these credentials, changes you make to usernames and passwords do not propagate across nodes. You must use a central LDAP for these credentials to be synchronized across nodes in a cluster, as described in, and required by, the Oracle Fusion Middleware High Availability Guide and Enterprise Deployment Guides.

6.2.10 Use Fully-Qualified Hostnames when Configuring Front-end Hosts in High Availability Configurations

Oracle recommends using the full name of the host, including the domain name, when configuring front-end hosts in Oracle Fusion Middleware high availability configurations. Use the host's full name instead of using only the host name.

For example, if myhost is the name of a frontend host in a high availability configuration, set the frontend host URL to the fully-qualified hostname, such as myhost.mycompany.com as DNS or local host name resolution files (for example, /etc/hosts) define.

6.2.11 Managed Server goes into Suspended Status After Oracle RAC Failover

The Managed Server wls_ods(x) can enter a suspended status in the following situations:

- A database connection in the data source is wrong or not complete.

- The host is not a fully-qualified host for the database.

To correct the status of the Managed Server wls_ods(x):

1. Under the data source, verify that the database connection is correct and complete with the domain.

2. Under the data source, verify that the host name for the database is a fully- qualified hostname with the domain.

3. Verify the connection by selecting the Test button.

6.2.12 Primary/Secondary Configuration Section of the Availability Tab is Not Visible

During the system component scale out process, the Primary/Secondary Configuration section in the Availability tab of the Capacity Management page in Fusion Middleware Control may not be visible in the browser. This issue occurs when you perform the scale out process using Microsoft Internet Explorer version 7.0.5730.11.

To avoid this issue, do not use the browser Microsoft Internet Explorer version 7.0.5730.11 to scale out; use another browser such as Google Chrome.

6.2.13 Server Start Parameters Not Getting Set After Scaling Out the Oracle Business Intelligence Managed Server

After scaling out Oracle Business Intelligence, Server Start parameters are not getting set correctly. To work around this issue, update the Server Start parameters for the scaled out BI Managed Server to include the following:

-Dserver.group=obi arguments

6.2.14 Ensuring the Oracle HTTP Server Lock File is on a Local Drive

If you configure an Oracle instance for Oracle HTTP Server 11g on shared storage, such as NAS, NFS, or SAN storage, you must ensure that the lock file is created on a local drive instead of the shared drive. If you do not do this, Oracle HTTP Server might experience performance problems. Perform these steps to point the LockFile directive at a local fi le system:

1. Stop the OHS instances on WEBHOST1 and WEBHOST2.

2. Open the file ORACLE_INSTANCE/config/OHS/ohs_name/httpd.conf in a text editor.

3. Find the LockFile directive, configured under both the prefork and worker MPM configuration blocks in the httpd.conf file. It looks like this:

LockFile ORACLE_INSTANCE/diagnostics/logs/COMPONENT_TYPE/COMPONENT_NAME/http_lock

4. Change the LockFile directive under the appropriate MPM configuration to point to a local file system, for example:

LockFile /local_disk/path/http_lock

5. Restart Oracle HTTP Server.

6. Verify that the http_lock file exists in the directory specified by the LockFile directive.

6.2.15 Recreating OSSO Agents that Point to the Load Balancer URL

A high availability Classic environment typically has a load balancer in front of the Classic OHS instances. When you configure a classic instance with OAM 11g, the Configuration Wizard automatically configures an OSSO agent. The OSSO agent contains the individual Classic OHS instance URL. In a high availability cluster consisting of two Classic instances, the Configuration Wizard automatically configures two OSSO agents. Each OSSO agent contains the URL information of one Classic Webtier instance URL.

In a high availability cluster, you must recreate an OSSO agent that points to the load balancer URL.

To recreate an OSSO agent that points to the load balancer URL:

1. From the OAM console, click New OSSO Agent to open the OSSO Wizard application.

2. Enter the following information:

- Name: Enter any name

- Token Version: Use the default setting, v3.0

- Base URL: Enter the load balancer URL, for example http://haqaedg04.us.example.com:7788

- Admin ID: Leave blank

- Admin Inf: Leave blank

- Host Identifier: Keep default value from the Name field.

- Auto Create Policies: Check this setting to enable it.

3. Copy the osso.conf file of the new OSSO agent from the OAM server to the Classic Web Instances config directory.

6.2.16 Use Lower-Case Letters for GridLink Data Source RAC Service Name

When you create a GridLink data source in the Configuration Wizard, you must verify that the service name on the database uses lowercase letters only and is a qualified domain name. For example, <mydbservice>.us.example.com. The Service Name field is in the Configure GridLink RAC Component Schema screen.

Note:
The Oracle RAC Service name is defined on the database; it is not a fixed name. Oracle recommends that you register/add the RAC service name with the database domain name, for example, us.example.com

6.2.17 Additional Steps Needed for Oracle RTD Request Forwarding to Work Correctly

Due to an Oracle RTD issue related to request forwarding, the frontend URL must be the same as the backend URL for deployments that include Oracle RTD. To set the frontend URL for Oracle RTD, perform the steps listed in the following procedures at the point indicated in the Oracle Business Intelligence EDG task flow.

After performing the steps listed in Section 5.7, "Setting the Listen Address for bi_server1 Managed Server," set the frontend URL for the bi_server1 Managed Server, as follows:

1. Log in to the Administration Console.

2. In the Change Center, click Lock & Edit.

3. Expand the Environment node in the Domain Structure window.

4. Click Servers. The Summary of Servers page is displayed.

5. Select bi_server1 in the Names column of the table. The settings page for bi_server1 is displayed.

6. Click the Protocols tab.

7. Click the HTTP tab.

8. Set the Frontend Host field to APPHOST1VHN1 (your bi_server1 Listen address).

9. Click Save, then click Activate Changes.

After performing the steps listed in Section 6.4.1, "Setting the Listen Address for the bi_server2 Managed Server," set the frontend URL for the bi_server2 Managed Server, as follows:

1. Log in to the Administration Console.

2. In the Change Center, click Lock & Edit.

3. Expand the Environment node in the Domain Structure window.

4. Click Servers. The Summary of Servers page is displayed.

5. Select bi_server2 in the Names column of the table. The settings page for bi_server2 is displayed.

6. Click the Protocols tab.

7. Click the HTTP tab.

8. Set the Frontend Host field to APPHOST2VHN1 (your bi_server2 Listen address).

9. Click Save, then click Activate Changes.

6.2.18 Error INST-08075 Occurs When Scaling Out the BI System

When you are scaling out the BI System using the Oracle Business Intelligence Configuration Assistant, the following error occurs:

INST-08075: Weblogic Server 10.3.6.0 is installed but Weblogic Server Temporary is used in the BI Domain.

To work around this error, perform the following steps:

1. Open MW_HOME/registry.xml for editing.

2. Locate the following line:

<component name="WebLogic Server" version="10.3.6.0" InstallDir="ORACLE_BASE/fmw/wlserver_10.3">

3. Change the line to the following:

<component name="WebLogic Server" version="Temporary" InstallDir="ORACLE_BASE/fmw/wlserver_10.3"

4. Save and close the file.

5. Return to the Oracle Business Intelligence Configuration Assistant and proceed past the Scale Out BI System Details screen.

6. Revert the entry in registry.xml back to version="10.3.6.0".

6.2.19 First Defined RAC Instance Must Be Available On Domain Startup When Configuring with RAC Multi Data Source

When you configure the RAC data source for OPSS, Oracle recommends using an Oracle GridLink data source type. If you decide to use a RAC multi data source, you must ensure that the first RAC instance listed in the multi data source definition is available during the first domain startup. If you do not use the first RAC instance listed, configuration fails.

6.3 Testing Abrupt Failures of WebLogic Server When Using File Stores on NFS

If JMS messages and transaction logs are stored on an NFS-mounted directory, Oracle strongly recommends that you verify the behavior of a server restart after abrupt machine failures. Depending on the NFS implementation, different issues can arise post failover/restart.

To verify server restart behavior, abruptly shut down the node that hosts WebLogic servers while the servers are running.

- If you configured the server for server migration, it should start automatically in failover node after the failover period.

- If you did not configure the server for server migration, you can manually restart the WebLogic Server on the same host after the node completely reboots.

If Oracle WebLogic Server does not restart after abrupt machine failure, the following error entry may appear in server log files:

<MMM dd, yyyy hh:mm:ss a z> <Error> <Store> <BEA-280061> <The persistent
store "_WLS_server_soa1" could not be deployed:
weblogic.store.PersistentStoreException: java.io.IOException:
[Store:280021]There was an error while opening the file store file
"_WLS_SERVER_SOA1000000.DAT"
weblogic.store.PersistentStoreException: java.io.IOException:
[Store:280021]There was an error while opening the file store file
"_WLS_SERVER_SOA1000000.DAT"
at weblogic.store.io.file.Heap.open(Heap.java:168)
at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:88)
...
java.io.IOException: Error from fcntl() for file locking, Resource
temporarily unavailable, errno=11

This error occurs when the NFSv3 system does not release locks on the file stores. WebLogic Server maintains locks on files that store JMS data and transaction logs to prevent data corruption that can occur if you accidentally start two instances of the same managed server. Because the NFSv3 storage device doesn't track lock owners, NFS holds the lock indefinitely if a lock owner crashes. As a result, after abrupt machine failure followed by a restart, subsequent attempts by WebLogic Server to acquire locks may fail.

If it is not reasonably possible to tune locking behavior in your NFS environment, use one of the following solutions to unlock the logs and data files:

- Use the WebLogic Server Administration Console to disable WebLogic file locking mechanisms for the default file store, a custom file store, a JMS paging file store, and a Diagnostics file store. To do this, see Considerations for Using File Stores on NFS in the Oracle Fusion Middleware High Availability Guide.

- Manually unlock the logs and JMS data files and start the servers by creating a copy of the locked persistence store file and using the copy for subsequent operations. See the following section Unlocking Logs and Data Files Manually.

Unlocking Logs and Data Files Manually

Manually unlock the logs and JMS data files and start the servers by creating a copy of the locked persistence store file and using the copy for subsequent operations. To create a copy of the locked persistence store file, rename the file then copy it back to its original name. The following sample steps assume that transaction logs are stored in the /shared/tlogs directory and JMS data is stored in the /shared/jms directory.

cd /shared/tlogs
mv _WLS_SOA_SERVER1000000.DAT _WLS_SOA_SERVER1000000.DAT.old
cp _WLS_SOA_SERVER1000000.DAT.old _WLS_SOA_SERVER1000000.DAT
cd /shared/jms
mv SOAJMSFILESTORE_AUTO_1000000.DAT SOAJMSFILESTORE_AUTO_1000000.DAT.old
cp SOAJMSFILESTORE_AUTO_1000000.DAT.old SOAJMSFILESTORE_AUTO_1000000.DAT
mv UMSJMSFILESTORE_AUTO_1000000.DAT UMSJMSFILESTORE_AUTO_1000000.DAT.old
cp UMSJMSFILESTORE_AUTO_1000000.DAT.old UMSJMSFILESTORE_AUTO_1000000.DAT

With this solution, the WebLogic file locking mechanism continues to protect against accidental data corruption if multiple instances of the same servers are accidently started. However, you must restart the servers manually after abrupt machine failures. File stores create multiple consecutively numbered.DAT files when they store large amounts of data. You may need to copy and rename all files when this occurs.

6.4 Documentation Errata

This section describes documentation errata. It includes the following topics:

- Section 6.4.1, "Documentation Errata for the Fusion Middleware High Availability Guide"

- Section 6.4.2, "Documentation Errata for the Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management"

6.4.1 Documentation Errata for the Fusion Middleware High Availability Guide

This section contains Documentation Errata for Oracle Fusion Middleware High Availability Guide.

It includes the following topics:

- Section 6.4.1.1, "Latest Requirements and Certification Information"

- Section 6.4.1.2, "Error in Line to Add to mod_wl_ohs.conf File"

6.4.1.1 Latest Requirements and Certification Information

Several manuals in the Oracle Fusion Middleware 11g documentation set have information on Oracle Fusion Middleware system requirements, prerequisites, specifications, and certification information. For the latest information on these topics, see the following documents on Oracle Technology Network:

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

This document contains information related to hardware and software requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches. It also includes information on supported installation types, platforms, operating systems, databases, JDKs, and third-party products.

6.4.1.2 Error in Line to Add to mod_wl_ohs.conf File

In Chapter 5., "Configuring High Availability for Oracle SOA Suite," the line <Location /DefaultToDoTaskFlow/> should be <Location /workflow/DefaultToDoTaskFlow/> in the mod_wl_ohs.conf file. Instances of this line are in Sections 5.3.13 and 5.14.15.

6.4.2 Documentation Errata for the Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management

This section contains documentation errata for Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management.

It includes the following topics:

- Section 6.4.2.1, "Set -DDomainRegistrationEnabled=true when Starting Node Manager"

- Section 6.4.2.2, "Ignore Empty Section in the Oracle Virtual Directory Chapter"

- Section 6.4.2.3, "Installing Identity Management Sections Are Incorrectly Organized"

- Section 6.4.2.4, "Errors in Instructions for Using the Guide"

- Section 6.4.2.5, "LDIF File Error in Procedure for Creating Users and Groups for Oracle WebLogic Server"

- Section 6.4.2.6, "Run Additional emctl Commands When Extending the Domain with Oracle Internet Directory or Oracle Virtual Directory"

- Section 6.4.2.7, "Errors in Section 2.4, Shared Storage and Recommended Directory Structure"

6.4.2.1 Set -DDomainRegistrationEnabled=true when Starting Node Manager

The November 2010 edition of Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management failed to mention that, prior to starting the Node Manager that controls the WebLogic Administration Server, you must set -DDomainRegistrationEnabled=true. For example:

export JAVA_OPTIONS=-DDomainRegistrationEnabled=true

6.4.2.2 Ignore Empty Section in the Oracle Virtual Directory Chapter

In the November 2010 edition of Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management, Section 8.1.1 in Chapter 11, "Extending the Domain with Oracle Virtual Directory is an empty section." Please ignore it.

6.4.2.3 Installing Identity Management Sections Are Incorrectly Organized

In Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management 11g Release 1 (11.1.1.5), Part Number E12035-07, Section 4.5.5, "Installing Oracle Identity Management," should be reorganized as follows:

- The content beginning with "Start the Oracle Fusion Middleware 11g Oracle Identity Management Installer" should be in a subsection, Section 4.5.5.1, entitled "Installing Oracle Identity Management 11.1.1.2."

- Section 4.5.6, "Upgrading the Oracle Homes for Oracle Identity Management from 11.1.1.2 to 11.1.1.5" should be Section 4.5.5.2.

6.4.2.4 Errors in Instructions for Using the Guide

Errors exist in Section 1.6, "Using This Guide." They should be corrected as follows:

- Step 11 should be:
If you are using Oracle Access Manager, follow the steps in Chapter 12, "Extending the Domain with Oracle Access Manager 11g."

- Steps 11 through 18 should refer to chapters, not sections.

6.4.2.5 LDIF File Error in Procedure for Creating Users and Groups for Oracle WebLogic Server

The LDIF file in Step 2a of Section 11.4.4, "Creating Users and Groups for Oracle WebLogic Server," is missing some line breaks. It should appear as follows:

dn: cn=orclFAUserReadPrivilegeGroup,cn=Groups,dc=mycompany,dc=com
changetype: modify
add: uniquemember
uniquemember: cn=IDROUser,cn=Users,dc=mycompany,dc=com

6.4.2.6 Run Additional emctl Commands When Extending the Domain with Oracle Internet Directory or Oracle Virtual Directory

In the chapters "Extending the Domain with Oracle Internet Directory" and "Extending the Domain with Oracle Virtual Directory," you are instructed run

./emctl switchOMS ReposURL

to enable the local emagent to communicate with the WebLogic Administration Server using the virtual IP address. After you have run that command, you must also perform the following tasks:

- Force the agent to reload its configuration by issuing the command:

./emctl reload

- Check that the agent is using the correct Upload URL using the command:

./emctl status agent

6.4.2.7 Errors in Section 2.4, Shared Storage and Recommended Directory Structure

Table 2-3, Recommended Directory Structure, is missing some values in the Shared Storage column. The following table entries should have the value "Yes" in the Shared Storage column, indicating that these directories should be on shared storage:

- IAM_ORACLE_HOME

- ASERVER_DOMAIN_HOME

- ASERVER_APP_HOME

7 Oracle JDeveloper and Oracle Application Development Framework (ADF)

The latest known issues associated with Oracle JDeveloper and Application Developer Framework (ADF) are available on the Oracle Technology Network (OTN) at: http://www.oracle.com/technetwork/developer-tools/jdev/default-1399172.html.

For more information and technical resources for Oracle JDeveloper and Application Developer Framework (ADF), visit the product center on the Oracle Technology Network at: http://www.oracle.com/technetwork/developer-tools/jdev/overview/index.html.

8 Oracle Platform Security Services

This chapter describes notes on topics associated with Oracle Platform Security Services (OPSS), in the following sections:

- Section 8.1, "Configuration Issues and Workarounds"

- Section 8.2, "Documentation Errata"

The following documents are relevant to topics included in this chapter:

- Oracle Fusion Middleware Security Guide

- Oracle Fusion Middleware Administrator's Guide

- Oracle Fusion Middleware Administrator's Guide for Authorization Policy Manager

8.1 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

- Section 8.1.1, "Oracle Fusion Middleware Audit Framework"

- Section 8.1.2, "Trailing '\n' Character in Bootstrap Key"

- Section 8.1.3, "Users with Same Name in Multiple Identity Stores"

- Section 8.1.4, "Script listAppRoles Outputs Wrong Characters"

- Section 8.1.5, "Propagating Identities over the HTTP Protocol"

- Section 8.1.6, "Pool Configuration Missing in Identity Store"

8.1.1 Oracle Fusion Middleware Audit Framework

This section describes configuration issues for the Oracle Fusion Middleware Audit Framework. It contains these topics:

- Section 8.1.1.1, "Configuring Auditing for Oracle Access Manager"

- Section 8.1.1.2, "Audit Reports do not Display Translated Text in Certain Locales"

- Section 8.1.1.3, "Audit Reports Always Display in English"

- Section 8.1.1.4, "Audit Store Does not Support Reassociation through EM"

- Section 8.1.1.5, "OWSM Audit Events not Audited"

8.1.1.1 Configuring Auditing for Oracle Access Manager

Although Oracle Access Manager appears as a component in Oracle Enterprise Manager Fusion Middleware Control, you cannot configure auditing for Oracle Access Manager using Fusion Middleware Control.

8.1.1.2 Audit Reports do not Display Translated Text in Certain Locales

The standard audit reports packaged with Oracle Business Intelligence Publisher support a number of languages for administrators. Oracle Business Intelligence Publisher can start in different locales; at start-up, the administrator can specify the language of choice by setting the preferred locale in Preferences.

Due to this bug, if Oracle Business Intelligence Publisher is started on any of these 3 locales:

- zh_CN (simplified chinese)

- zh_TW (traditional chinese)

- pt_BR (portuguese brazilian)

then users cannot see the report in that locale (the entire report including labels, headers, titles and so on appears in English), while the other locales display the translated text as expected. For example, when Oracle Business Intelligence Publisher is started in zh_CN, the text cannot be seen in zh_CN even though the preferred locale is set to zh_CN; information is displayed in English.

This issue will be fixed in a future release of Oracle Business Intelligence Publisher.

8.1.1.3 Audit Reports Always Display in English

The standard audit reports packaged with Oracle Business Intelligence Publisher support a number of languages.

Due to this bug, report titles and descriptions are displayed in English even when they have been translated.

This issue will be fixed in a future release of Oracle Business Intelligence Publisher.

8.1.1.4 Audit Store Does not Support Reassociation through EM

In Release 11gR1 (11.1.1.6.0), if you reassociated security stores through the Fusion Middleware Control Enterprise Manager (EM) console, most stores (policy store, credential store and so on) moved except for the audit store. This is because the audit store did not support reassociation through the console, only through the WLST command reassociateSecurityStore.

In a situation where the original migration from Release 11gR1 (11.1.1.6.0) to Release 11gR1 (11.1.1.7.0) was done through EM, this leaves the audit repository as file-based. You can use the following workaround to move all security store data to LDAP/DB in order to enable audit:

In the PS5 environment, run WLST command reassociateSecurityStore with a different jpsroot node. This effects an OID-to-OID directory reassociation and any existing data also gets migrated to the new node. After you take this action, audit data will no longer be file based and jps-config will have the new node.

8.1.1.5 OWSM Audit Events not Audited

In Release 11.1.1.7, due to a bug, audit events are not logged for Web Services Manager (OWSM) after auditing is configured for the component.

To resolve this issue, proceed as follows:

1. Register the OWSM components AGENT, PM-EJB with the audit service using the registerAudit WLST command:

1. registerAudit(xmlFile="$ORACLE_COMMON/modules/oracle.iau_11.1.1/components/OWSM-AGENT/component_events.xml", componentType="AGENT")

2. registerAudit(xmlFile="$ORACLE_COMMON/modules/oracle.iau_11.1.1/components/OWSM-PM-EJB/component_events.xml", componentType="PM-EJB")

2. Get the list of components using the listAuditComponents WLST command; for example, this command writes the list of components to a file named complist.txt:

listAuditComponents(fileName = "/tmp/complist.txt")

3. For each component in the list, execute the WLST command setAuditPolicy as follows:

setAuditPolicy(componentType="<component name from complist.txt>",  filterPreset="None")

For details about syntax and usage of these commands, see Oracle Fusion Middleware Application Security Guide, part number E10043-11, Appendix C Oracle Fusion Middleware Audit Framework Reference.

8.1.2 Trailing '\n' Character in Bootstrap Key

In 11gR1, the process that reassociates XML to LDAP stores creates a bootstrap key with the trailing new line character '\n', or its equivalent code '&#xA'. This key value is written in the file jps-config.xml and stored in the wallet. In both places, the key value contains the trailing character '\n'.

When reusing that same wallet in 11gR1 PS1, upon retrieving the bootstrap key, the system trims out the trailing '\n' character; but the key value in the wallet, however, still contains the trailing character, a situation that leads to errors since the requested and stored key values no longer match.

To resolve this issue, proceed as follows:

1. Use the WLST command modifyBootStrapCredential to reprovision wallet credentials without trailing '\n'. For details on the command usage, see section 9.5.2.5 in the Oracle Fusion Middleware Security Guide.

2. Manually edit the file jps-config.xml and remove the trailing characters '&#xA' from any bootstrap key.

This problem arises only in the scenario above, namely, when an 11gR1 wallet is reused in 11gR1 PS1; in particular, when reassociating in an 11gR1 PS1 environment, the above trailing character is not an issue.

8.1.3 Users with Same Name in Multiple Identity Stores

If a user name is present in more than one LDAP repositories and the property virtualize is set to use LibOVD, then the data in only one of those repositories is returned by the User and Role API when that name is queried.

8.1.4 Script listAppRoles Outputs Wrong Characters

On Linux and Windows platforms, when the locale is set to non-UTF8 locales, such as fr_FR_iso88591, the OPSS script listAppRoles may wrongly output the character '?' instead of the expected character.

8.1.5 Propagating Identities over the HTTP Protocol

This section includes the following additions, corrections, and new information in the following sections:

- Addition to Section Propagating Identities over the HTTP Protocol

- Correction to Section Client Application Code Sample

- Correction to Section Keystore Service Configuration

- Updating the Trust Service Configuration Parameters

8.1.5.1 Addition to Section Propagating Identities over the HTTP Protocol

The following new information belongs in section 19.3.1.2:

The out of box configuration assumes that the token issuer name and the key alias is based on the WebLogic server name. Note that the key alias server name on WebSphere is set based on the WebSphere server root. For example, if the server root is $T_WORK/middleware/was_profiles/DefaultTopology/was_as/JrfServer then the server name is set to JrfServer. To change the default value, use the procedures explained in section 19.3.12.

8.1.5.2 Correction to Section Client Application Code Sample

The following sample illustrates a client application; note that the file jps-api.jar and OSDT jars osdt_ws_sx.jar, osdt_core.jar, osdt_xmlsec.jar, osdt_saml2.jar must be included the class path for the code sample to compile.

8.1.5.3 Correction to Section Keystore Service Configuration

Assuming that the WebLogic server name is jrfServer_admin, the following command illustrates the creation of the keystore, represented by the generated file default-keystore.jks.

8.1.5.4 Updating the Trust Service Configuration Parameters

The information in this section is new and it explains how to modify the trust service configuration parameters in the file jps-config.xml with a script.

Out-of-the-box the values of the parameters trust.aliasName and trust.issuerName are set to the WebLogic server name. To modify their values to deployment-specific values, use a script like the following:

import sys

wlsAdmin = 'weblogic'
wlsPwd ='password_value'
wlUrl='t3://localhost:7001'
issuer= 'issuer'
alias = 'alias'

print "OPSS Trust Service provider configuration management script.\n"

instance = 'trust.provider'
name = 'trust.provider.embedded'
cfgProps = HashMap()
cfgProps.put("trust.issuerName", issuer)
cfgProps.put("trust.aliasName", alias)
pm = PortableMap(cfgProps);

connect(wlsAdmin, wlsPwd, wlUrl)
domainRuntime()

params = [instance, name, pm.toCompositeData(None)]
sign = ["java.lang.String", "java.lang.String", "javax.management.openmbean.CompositeData"]
on = ObjectName("com.oracle.jps:type=JpsConfig")
mbs.invoke(on, "updateTrustServiceConfig", params, sign)
mbs.invoke(on, "persist", None, None)

print "Done.\n"

8.1.6 Pool Configuration Missing in Identity Store

On the WebSphere Application Server, the out-of-the-box configuration file jps-config.xml is missing an entry for a property of the identity store. When the identity store, added at post-installation, is an LDAP-based identity store, the following property must be manually inserted in the jps-config.xml file within the identity store service instance element:

<property name="CONNECTION_POOL_CLASS"
value="oracle.security.idm.providers.stdldap.JNDIPool"/>

To work around this issue, proceed as follows:

1. Shut down the server.

2. Open the file was_profile_dir/config/cells/cell_name/fmwconfig/jps-config.xml for edit, where was_profile_dir and cell_name stand for the profile directory name and cell name on your system.

3. Insert the missing property CONNECTION_POOL_CLASS into the configuration of the identity store service instance.

4. Save the file and restart the server.

8.2 Documentation Errata

This section contains corrections to documentation errors. It includes the topic:

- Section 8.2.1, "Updated Configuration for Role Category"

- Section 8.2.2, "Correct setAuditRepository Command Reference Example"

- Section 8.2.3, "Demo CA Certificate not for Production Use"

- Section 8.2.4, "Incorrect Link to ILM Content"

- Section 8.2.5, "Incorrect Table Title in Appendix C"

- Section 8.2.6, "Clarification of Note in Appendix C"

- Section 8.2.7, "Notes Regarding Need for Server Restarts"

8.2.1 Updated Configuration for Role Category

This note contains the correct configuration of a role category as described in Section 2.8 "The Role Category" in the Oracle Fusion Middleware Application Security Guide, part number E10043-10.

The configuration of the element <role-category> in the jazn-data.xml illustrated in section 2.8 should be replaced with the following:

<app-roles>
<app-role>
<name>AppRole_READONLY</name>
<display-name>display name</display-name>
<description>description</description>
<class>oracle.security.jps.service.policystore.ApplicationRole</class>
<extended-attributes>
<attribute>
<name>ROLE_CATEGORY</name>
<values>
<value>RC_READONLY</value>
</values>
</attribute>
</extended-attributes>
</app-role>
</app-roles>
<role-categories>
<role-category>
<name>RC_READONLY</name>
<display-name>RC_READONLY display name</display-name>
<description>RC_READONLY description</description>
</role-category>
</role-categories>

The important point about this correction is the following:

- The members of a role category are not configured within the <role-category> element but within the element <extended-attributes> of the corresponding application role.

8.2.2 Correct setAuditRepository Command Reference Example

This note corrects a typo in Section C.4.5 "setAuditRepository" in the Oracle Fusion Middleware Application Security Guide, part number E10043-11.

In the example line:

setAuditRepository(switchToDB='true',dataSourceName='jdbcAuditDB',interval='14')

change 'jdbcAuditDB' to read 'jdbc/AuditDB'.

8.2.3 Demo CA Certificate not for Production Use

In the Oracle Fusion Middleware Application Security Guide, Part Number E10043-11, 11.1.3 Domain Trust Store, insert the following caution note at the top of the section:

Caution:
The Demo CA has a well known hard-coded private key, Care should be taken not to trust the certificates signed by the Demo CA. As such, the Demo CA certificate in the trust store should not be used in production. It should be removed from the domain trust store in production.

8.2.4 Incorrect Link to ILM Content

In the Oracle Fusion Middleware Application Security Guide, part number E10043-12, in the chapter Configuring and Managing Auditing, section titled "Tiered Archival" contains an incorrect link for Oracle Information Lifecycle Management (ILM).

Change the link to read:

http://www.oracle.com/technetwork/database/enterprise-edition/index-090321.html

8.2.5 Incorrect Table Title in Appendix C

In the Oracle Fusion Middleware Application Security Guide, part number E10043-11, in Appendix C Oracle Fusion Middleware Audit Framework Reference, Table C-4 is incorrectly titled. The correct title should be "Oracle Internet Directory Events."

8.2.6 Clarification of Note in Appendix C

In the Oracle Fusion Middleware Application Security Guide, part number E10043-11, in Appendix C Oracle Fusion Middleware Audit Framework Reference, the note at the beginning of section 12.3.3 is incomplete. The note should read:

Note:
The metadata store is separate from the audit data store which contains the actual audit data.

8.2.7 Notes Regarding Need for Server Restarts

In the Oracle Fusion Middleware Application Security Guide, part number E10043-11, Chapter 13 Configuring and Managing Auditing refers to the need to restart the server after audit policy changes. These references are in the following sections:

- Section 13.3 Managing Audit Policies, under the heading 'How Policies are Configured,', second sentence.

- Section 13.3.1 Manage Audit Policies for Java Components with Fusion Middleware Control, second bulleted note under Notes.

- Section 13.3.2 Manage Audit Policies for System Components with Fusion Middleware Control, second bulleted note under Notes.

However, a restart is not necessary; the changes take effect on the managed server after a few minutes.

9 Web Services Development, Security, and Administration

This chapter describes issues associated with Web services development, security, and administration, including Oracle Web Services Manager.

It includes the following topics:

- Using Multibyte User Credentials with wss_http_token_* Policy

- Performing a Bulk Upload of Policies

- Reviewing Policy Configuration Override Values After Detaching a Client Policy

- Removing Post-deployment Customizations

- Reviewing Localization Limitations

- When Using WLST to Import a Security Policy, the Same Policy May Be Repeatedly Imported

- Identity in WSDLs Is Not Used for Enforcement with ADF DC Applications

- Fusion Middleware Control Does Not List Policies When Two Servers Are SSL Enabled (Two-way SSL)

- Web Service Test Page Cannot Test Input Arguments Bound to SOAP Headers

- When Adding SAML Issuer From Fusion Middleware Control the jps-config.xml File Is Incorrectly Updated

- Patching of Patch Set 1 WebLogic Server Web Services Attached to Custom Polices With Patch Set 3 Oracle WSM Policy Manager

- Custom Policy Fails When an Empty Subject Is Passed

- Possible Limitation When Using Custom Exactly-one Policies

- Ignore "Services Compatibility" Error for Security Policies Used Between Oracle WSM and WebLogic Server

- Compatible Policies Not Returned When Using JDeveloper Wizard to Attach Oracle WSM Policies to Web Service Client

- SAML Bearer Token Policies Now Signed by Default

- Security Policies Do Not Work on Subscriber Mediator Component

- Policy Table Might Not Show Attached Policies for Some Locales

- Manual Step Required to Uptake Changes in Predefined Policy

- Usage Tracking Not Enabled for WebLogic Web Service Client

- Do Not Attach a Permitall and Denyall Policy to the Same Web Service

- Additional Quotes in Fusion Middleware Control for Run-time Constraint Input from WLST

- Scoped Configuration Override Persists for Subsequent References to the Same Policy

- New Default Settings for Policies

- Restart Applications to Get an Accurate Policy Usage Count

- Kerberos Policy Enforcement Throws an "Unable to Obtain Password from User" Error

- The migrateAttachments WLST Command Fails for WebLogic JAX-WS Web Services

- A Null Pointer Exception Could be Thrown When Verifying a SOAP Message Signature

- checkWSMstatus() WLST Command Fails Against a Domain When wsm-pm Targets Multiple Servers

- Performance Improvements in Web Services Policy Pages

- Cross-Domain Policy Manager Configuration is Not Supported in this Release

- The setWebServicePolicyOverride WLST Command Does Not Apply to JAVA EE (WebLogic) Web Services

- Support for JSON Web Tokens Available for This Release

- New Functionality and Changes Available in PS6 MLR Patch

9.1 Using Multibyte User Credentials with wss_http_token_* Policy

In this release, multibyte user credentials are not supported for the wss_http_token_* policies. If multibyte user credentials are required, use a different policy, such as wss_username_token_* policy. For more information about the available policies, see Appendix B "Predefined Policies" in the Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

9.2 Performing a Bulk Upload of Policies

When performing a bulk import of policies to the MDS repository, if the operation does not succeed initially, retry the operation until the bulk import succeeds.

For the most part, this can occur for an Oracle RAC database when the database is switched during the metadata upload. If there are n databases in the Oracle RAC database, then you may need to retry this operation n times.

For more information about bulk import of policies, see "Migrating Policies" in the Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

9.3 Reviewing Policy Configuration Override Values After Detaching a Client Policy

If you attach a policy to a client, override policy configuration values, and subsequently detach the policy, the policy configuration override values are not deleted. When attaching new policies to this client, ensure that you review the policy configuration override values and update them appropriately.

9.4 Removing Post-deployment Customizations

When the connections.xml file is changed after deployment using the AdfConnection MBean, the complete connection is saved as a customization. This means that changes to the connection in a redeployed application are overwritten by the customization.

When you use Fusion Middleware Control to make changes to an application's connections.xml file after deployment, a new connections.xml file is created as a customization and stored in the MDS repository. This customization persists for the life of the application. Therefore, if you redeploy the application, the customized connections.xml file continues to be applied as a customization on the application.

To allow the redeployed application's connections.xml file to be applied without the prior customization (from Fusion Middleware Control), you must explicitly remove the connections.xml customizations from the MDS repository.

For example, if you deploy an application with a Web services data control, then use Fusion Middleware Control to attach the 'username token client policy', and subsequently detach the policy. Then, you return to JDeveloper to edit the application and attach the 'http token client policy', and redeploy the application. When you view the application using Fusion Middleware Control, you see that it is not using the 'http token client policy' that you attached. That is because it is using the customized connections.xml file that you previously created using Fusion Middleware Control.

If you remove the connections.xml customizations from the MDS repository, the application will use the its own connections.xml file.

9.5 Reviewing Localization Limitations

The following information is supported in English only in this release of Oracle Enterprise Manager:

- All fields in the policy and assertion template except the orawsp:displayName field.

- If using the ?orawsdl browser address, the orawsp:description field.

- In the System MBean browser, the Description field in the oracle.wsm.upgrade Mbean.

9.6 When Using WLST to Import a Security Policy, the Same Policy May Be Repeatedly Imported

When WLST is used to import a security policy, be aware that the same policy may be repeatedly imported.

9.7 Identity in WSDLs Is Not Used for Enforcement with ADF DC Applications

For ADF DC applications, the identity extension in a WSDL (for example, the certificate published in the WSDL), cannot be used as a recipient certificate for message protection policies. Instead, either the recipient key alias (declarative configuration override) or the default recipient key alias specified in the policy are used.

9.8 Fusion Middleware Control Does Not List Policies When Two Servers Are SSL Enabled (Two-way SSL)

When a Managed Server is Two-way enabled SSL (for example, a SOA server hosting Oracle WSM Policy Manager over Two-way SSL) and the Administration Server hosting Fusion Middleware Control is correctly configured to access the Two-way SSL-enabled Managed Server, Fusion Middleware Control still does not list the Oracle WSM policies.

9.9 Web Service Test Page Cannot Test Input Arguments Bound to SOAP Headers

For Web services that have any input arguments bound to SOAP headers, the Test Web Service page in the Fusion Middleware Control console cannot show the message. Therefore, such operations cannot be tested with the Test Web Service page.

For example, if the input for a multi-part WSDL is viewed through Fusion Middleware Control, and one input argument is bound to a SOAP header, the composite instance fails with the following exception because the other part of the message was missing in the input:

ORAMED-01203:[No Part]No part exist with name "request1" in source message

To resolve such an issue, select XML View for Input Arguments and edit the payload to pass input for both parts of the WSDL.

9.10 When Adding SAML Issuer From Fusion Middleware Control the jps-config.xml File Is Incorrectly Updated

In release 11g R1 (11.1.1.1.0), when you try to add or edit a trusted issuer from the Fusion Middleware Control console, then the jps-config.xml file is incorrectly updated. As a workaround for this issue, Oracle recommends upgrading to 11g R1 Patch Set 2 (11.1.1.3.0).

9.11 Patching of Patch Set 1 WebLogic Server Web Services Attached to Custom Polices With Patch Set 3 Oracle WSM Policy Manager

Due to a new feature in 11g R1 Patch Set 2 (11.1.1.3.0), the "Shared policy store for Oracle Infrastructure Web services and WebLogic Server Web services", WebLogic Server Web services now utilize the Policy Manager by default to retrieve policies from the MDS repository. In Patch Set 1, WebLogic Server Web services used classpath mode by default.

After patching your Oracle Fusion Middleware 11g R1 software installation to Patch Set 2, if you have attached a custom Oracle WSM policy to a WebLogic Server Web service, you need to make sure your custom policy is stored in the MDS repository. Note that only custom policies in use need to be migrated. All seed policies will be available in the MDS repository out-of-the-box.

To migrate policies to the Metadata Services (MDS) repository, see "Maintaining the MDS Repository" in the Security and Administrator's Guide for Web Services.

9.12 Custom Policy Fails When an Empty Subject Is Passed

If an empty subject is passed to a custom policy, it fails with a generic error. To work around this issue, you can create and set an anonymousSubject inside the execute method of the custom step. For example:

javax.security.auth.Subject subject =
oracle.security.jps.util.SubjectUtil.getAnonymousSubject();
context.setProperty(oracle.wsm.common.sdk.IMessageContext.SECURITY_SUBJECT,subject)

Note that in this example the context is of Type oracle.wsm.common.sdk.IContext

9.13 Possible Limitation When Using Custom Exactly-one Policies

In some cases, there can be a limitation when using custom Exactly-one policies. For a set of assertions within the exactly-one policy, if a request message satisfies the first assertion, then the first assertion gets executed and a response is sent accordingly. However, this may not be the desired behavior in some cases because the request may be intended for the subsequent assertions.

For example, you may have a client policy that has Timestamp=ON and a service exactly-one policy that has a wss11 username token with message protection assertions: the first has Timestamp=OFF; the second has Timestamp=ON. Therefore, the first assertion in the service exactly-one policy is not expecting the Timestamp in the request, yet the second assertion does expect it. In this case, the first assertion gets executed and the response is sent with no Timestamp. However, the client-side processing then fails because it expects the Timestamp that was sent in the request.

This limitation can exist with any cases where a client policy expects a greater number of elements to be signed and a service policy does not.

9.14 Ignore "Services Compatibility" Error for Security Policies Used Between Oracle WSM and WebLogic Server

Fusion Middleware Control may display a false error message when verifying compatibility of service policies. This incompatibility message is shown when using Enterprise Manager to attach an Oracle WSM Security client policy. Upon clicking the Check Services Compatibility, a message states that policies are incompatible despite the fact that these might be compatible.

Workaround:

If WSM policies are attached at the Web service endpoint, use the corresponding client policy. For example, if the service has wss11_saml_or_username_token_with_message_protection_service_policy, wss11_saml_token_with_message_protection_client_policy or wss11_username_token_with_message_protection_client_policy will work at the client side. If non-WSM policies are attached to the Web Service, see the Interoperability Guide for Oracle Web Services Manager for information about the corresponding client policy and attach it.

9.15 Compatible Policies Not Returned When Using JDeveloper Wizard to Attach Oracle WSM Policies to Web Service Client

During design time, the JDeveloper Wizard's option for Attaching Oracle WSM Policies to Web Service Clients might not return any compatible policies. This can occur due to one of the following reasons:

- There are no compatible client policies corresponding to the service policies published in the WSDL.

- In some cases, when you are trying to determine the compatible client policies in version 11.1.1.4 of JDeveloper running with Fusion Middleware Control Enterprise Manager that correspond to the service policies published in the WSDL of the Web service in version 11.1.1.3 or earlier.

Workaround:

Disable the Show only the compatible client policies for selection option in the JDeveloper Wizard. This will list all the client policies.

If Oracle WSM policies are attached to the Web service, use the corresponding client policy. For example, if the service has the policy wss11_saml_or_username_token_with_message_protection_service_policy, it is safe to assume that wss11_saml_token_with_message_protection_client_policy or wss11_username_token_with_message_protection_client_policy will work at the client side.

If WSM policies are not attached to the Web service, refer to the Interoperability Guide for Oracle Web Services Manager for instructions on determinant the corresponding client policy and attaching it.

9.16 SAML Bearer Token Policies Now Signed by Default

A new property, saml.enveloped.signature.required, is available when configuring wss_saml_token_bearer_over_ssl policies (both client and service). In releases prior to 11.1.1.4, the SAML bearer token was unsigned by default. In the 11.1.1.4 release and later, the SAML bearer token is signed because the default value for the saml.enveloped.signature.required property is true.

To retain the behavior of the releases prior to 11.1.1.4, set the saml.enveloped.signature.required property to false in both the client and service policies. The SAML bearer token is signed using the domain sign key, but it can be overridden using the keystore.sig.csf.key property set in the bearer client policy.

The affected policies are:

- wss_saml20_token_bearer_over_ssl_client_policy

- wss_saml_token_bearer_over_ssl_client_policy

- wss_saml20_token_bearer_over_ssl_service_policy

- wss_saml_token_bearer_over_ssl_service_policy

9.17 Security Policies Do Not Work on Subscriber Mediator Component

Component Authorization denyall policy does not work at subscriber mediator component. Authorization policy works for other normal mediator component cases.

9.18 Policy Table Might Not Show Attached Policies for Some Locales

Select the Web service application in Fusion Middleware Control and navigate to the Web service endpoint. Attach a policy to the endpoint in the Attach/Detach page. Sometimes the Directly Attached Polices table might not display the attached policies for the following locales: zh-cn, zh-tw, ja, pt-br, es, fr, ko.

As a workaround, enlarge the columns.

9.19 Manual Step Required to Uptake Changes in Predefined Policy

The oracle/wss11_saml_or_username_token_with_message_protection_service_policy now includes five assertions as described in "Configuring a Policy With an OR Group" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services:

- wss_saml_token_bearer_over_ssl (new)

- wss_username_token_over_ssl (new)

- wss_http_token_over_ssl (new)

- wss11_saml_token_with_message_protection (existing)

- wss11_username_token_with_message_protection (existing)

To take advantage of these additional assertions, you need to upgrade the Oracle WSM policies in the repository using the resetWSMPolicyRepository(false) WLST command. Note that executing this command will upgrade all of the predefined policies to the latest version provided in 11.1.1.6. For additional information, see "Upgrading the Oracle WSM Policies in the Repository" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

9.20 Usage Tracking Not Enabled for WebLogic Web Service Client

In this release, usage tracking and analysis is not provided for WebLogic Java EE Web service clients.

9.21 Do Not Attach a Permitall and Denyall Policy to the Same Web Service

Although you can attach multiple authorization policies to the same Web service, you should not attach both a permitall and denyall policy. If you do so, however, the combination validates successfully in this release.

Workaround:

Do not attach a permitall and denyall policy to the same Web service. For more information about authorization policies, see "Authorization Policies and Configuration Steps" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

9.22 Additional Quotes in Fusion Middleware Control for Run-time Constraint Input from WLST

When you specify a run-time constraint using WLST, as described in "Specifying Run-time Constraints in Policy Sets" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services, you must specify the constraint using quotes, for example setPolicySetConstraint('HTTPHeader("VIRTUAL_HOST_TYPE", "external")'). If you then use Fusion Middleware Control to view and edit the policy set constraint, the constraint is shown with the quotes in the Constraint Name and Constraint Value fields. You need to remove the quotes in these fields.

9.23 Scoped Configuration Override Persists for Subsequent References to the Same Policy

When using a scoped configuration override for the server side identity/encryption key (keystore.enc.csf.key) with a message protection policy, the override value is stored in the policy. Because the policy is cached, any subsequent references to this policy by other services will contain the override value. Therefore, the results will not be as expected.

Two examples of this scenario are as follows:

- An Oracle Infrastructure Web service has an attached message protection service policy. Both the service identity (service public encryption key, keystore.enc.csf.key) and the service message protection policy are advertised in the service WSDL. If the service encryption key is overwritten, using the global setPolicySetOverride command for example, then the scoped overwritten value for the keystore.enc.csf.key property that was intended for the specific attachment/reference of the initial service may affect other services attachments/references to the same policy.

- A SOA service composite has an attached message protection service policy and both the service identity (server public encryption key keystore.enc.csf.key) and the service message protection policy are advertised in the service WSDL. If the service encryption key is overwritten, for example, using JDeveloper to override keystore.enc.csf.key while building the service composite, then the scoped overwritten value for the keystore.enc.csf.key property that was intended for the specific attachment/reference of the initial service may affect other services attachments/references to the same policy.

Workaround

The recommended workaround is to perform a cache refresh when possible. For example, if a policy attachment/reference has a scoped override for the property keystore.enc.csf.key and it has been enforced or advertised once, the cached policy contains the override, however the original policy in the repository is not affected. To clear the override you can refresh the cache using methods such as restarting the server, redeploying the application, modifying the policy using Fusion Middleware Control, and so on.

In some scenarios, however, a cache refresh is not feasible. For example, if a service with a policy attachment/reference has a scoped override for the property keystore.enc.csf.key and it is enforced before other services that reference the same policy in a flow of execution that does not allow time for a manual cache refresh, then the policy in the cache referenced by the subsequent services contains the configuration override. For example, in an asynchronous service where the same policy is attached to both the asynchronous request and the asynchronous callback client, and only the asynchronous request attachment/reference has the override (the asynchronous callback does not), the asynchronous callback policy enforcement happens after the asynchronous request. In this case, the callback client accesses the policy in the cache that contains the configuration override. Since there is no opportunity to refresh the cache, there is no workaround available.

9.24 New Default Settings for Policies

For the following predefined policies, the default values for the Nonce Required and Creation Time Required settings are set to False in this release (these settings were True in past releases):

- wss_saml_or_username_token_over_ssl_service_policy

- wss_username_token_over_ssl_service_policy

- wss11_saml_or_username_token_with_message_protection_service_policy

Users should take into consideration that the nonce and created elements in the username token will be ignored by the service policy. This change, however, will not impact the security of your Web service. If you wish to maintain the old behavior, create a copy of the policy and set the values to True, as described in "Creating a Web Service Policy from an Existing Policy" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

For more information about the policies, see "Predefined Policies" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

Note:
If policy advertisement is configured to use WS-SecurityPolicy version 1.3, as described in "Policy Advertisement" Oracle Fusion Middleware Security and Administrator's Guide for Web Services, then no compatible client policy will be returned, but the runtime will be compatible. With default advertisement (for example, wssp1.1), client compatibility will operate as expected.

9.25 Restart Applications to Get an Accurate Policy Usage Count

If a policy that is being referred to by a Web Service is deleted and then re-imported, then its usage count will not be correct and application(s) must be restarted to obtain an accurate usage count.

9.26 Kerberos Policy Enforcement Throws an "Unable to Obtain Password from User" Error

This issue can occur if a Java EE client and service are using different keytabs, and both the client and the service are in same server. In this case, When the client invokes a Java EE service which is protected with Kerberos authentication policy, an "Unable to Obtain Password from User" error can be thrown. The error is thrown because the Krb5LoginModule implementation provided by the JDK caches only a single keytab.

To work around this issue, put the client and the service principal into a single keytab. This issue is not limited only to client and service pairs, but also to two Java EE clients running in same server. Thus, in all such cases, only a single keytab should be created that contains all of the required principals.

9.27 The migrateAttachments WLST Command Fails for WebLogic JAX-WS Web Services

The migrateAttachments WLST command migrates direct (local) policy attachments that are identical to the external global policy attachments that would otherwise be attached to each policy subject in the current domain.

In PS6, the migrateAttachments command will fail and throw an exception if the WebLogic Server JAX-WS Web service is deployed into the current domain.

Note:
If the current domain does not have any deployed WebLogic JAX-WS Web services, then this command will work correctly.

To work around this problem, follow these steps:

1. Run the listWebServices(detail='true') command.
For more information about this command, see "listWebServices" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

2. From the output of the listWebServices command, determine which Web services have the same directly attached policies as the global policy attachments.

3. Run the detachWebServicePolicy command to remove the directly attached policies for each Web service or Web service client identified in Step 2.
For more information about this command, see "detachWebServicePolicy" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

4. Run the listWebServiceClients(detail='true') command.
For more information about this command, see "listWebServiceClients" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

5. From the output of the listWebServiceClients command, determine which Web service clients have the same directly attached policies as the global policy attachments.

6. Run the detachWebServicePolicy command to remove the directly attached policies for each Web service client identified in Step 5.

9.28 A Null Pointer Exception Could be Thrown When Verifying a SOAP Message Signature

A Null Pointer Exception could be thrown when verifying the SOAP message signature. This issue can be seen especially with message protection policies that use higher algorithm suites, where the default XML namespace is defined in the SOAP message. In the following example, http://www.oracle.com/sb/qa/config is the default namespace:

<soapenv:Envelope  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="http://www.oracle.com/sb/qa/config">
<soap:Header></soap:Header>
<soapenv:Body></soapenv:Body>
</soapenv:Envelope>

To work around this issue, do not use the default XML namespace in the SOAP message.

9.29 checkWSMstatus() WLST Command Fails Against a Domain When wsm-pm Targets Multiple Servers

The agent check does not perform correctly for scenarios where wsm-pm is targeted to multiple servers or in a cluster. Also, the agent check does not perform correctly if the t3 port and HTTP port are different.

To perform an agent check for these scenarios, you must explicitly provide the value of the address argument. The address argument must be a valid HTTP URL with the host name and the port name of the server on which wsm-pm is running.

9.30 Performance Improvements in Web Services Policy Pages

Performance improvements have been made to the Web Services Policy pages in Fusion Middleware Control by removing the unnecessary role query.

9.31 Cross-Domain Policy Manager Configuration is Not Supported in this Release

Configuration to a Policy Manager in a remote domain is not supported in this release. Therefore, the following topics in Oracle Fusion Middleware Security and Administrator's Guide for Web Services have been updated to remove the procedures to connect to a remote Policy Manager:

- Configuring the Policy Manager Connection and Tuning the Policy Cache

- Configuring Web Service Policy Retrieval

9.32 The setWebServicePolicyOverride WLST Command Does Not Apply to JAVA EE (WebLogic) Web Services

In this release, the setWebServicePolicyOverride command, as described in "Web Services Custom WLST Commands" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference, applies to Oracle Infrastructure Web Services and SOA composites only. The wls module type is not supported.

9.33 Support for JSON Web Tokens Available for This Release

Support for JSON Web tokens is available for this release. To get this functionality, you must install Patch 18220367: TRACKING: CUMULATIVE OPATCH FOR PS6 MLR PATCH#10, available through OPatch. For information about downloading and installing patches using OPatch, see Oracle Fusion Middleware Patching Guide.

Related Oracle WSM documentation for this feature has been added to Oracle Fusion Middleware Security and Administrator's Guide for Web Services. For information about the documentation updates in this guide, see "Support for JSON Web Tokens (JWT) for Identity Propagation."

Note:
The following WLST token issuer trust commands have been updated to support dns.jwt as a valid value for the type argument:

- displayWSMTokenIssuerTrust

- setWSMTokenIssuerTrust

- deleteWSMTokenIssuerTrust

The descriptions in "Web Services Custom WLST Commands" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference have not been updated to include this value. For details about using these commands with JWT, see "Defining Trusted Issuers and Managing DN Lists Using WLST" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

9.34 New Functionality and Changes Available in PS6 MLR Patch

Oracle has released MLR patch 21223480 with the following new functionality and changes:

- Removal of SPNEGO Assertion From Multi Token REST Policies

- RESTful Client Security Support

- OAuth 2.0 Support for REST and SOAP Services and Clients

- REST APIs for Managing Credentials, Keystores, and Trust Stores

To get this new functionality, you must install MLR patch 21223480, available through OPatch. For information about downloading and installing patches using OPatch, see the Oracle Fusion Middleware Patching Guide.

New and Revised Documentation

To support this new patch, the following documents have been revised or added for this release:

- Oracle Fusion Middleware Introducing Web Services

- Oracle Fusion Middleware Security and Administrator's Guide for Web Services

- Oracle Fusion Middleware Programming Advanced Features of JAX-WS Web Services for Oracle WebLogic Server

- Oracle Fusion Middleware Using the Jersey JAX-RS Reference Implementation (new)

- Oracle Fusion Middleware REST API for Managing Credentials and Keystores with Oracle Web Services Manager (new)

These documents are available on the Web Services page in the Oracle Fusion Middleware Online Documentation Library 11g Release 1 (11.1.1.7) library:

http://docs.oracle.com/cd/E28280_01/nav/webservices.htm

9.34.1 Removal of SPNEGO Assertion From Multi Token REST Policies

This MLR patch removes the SPNEGO assertion from the out-of-the-box multi token REST policy descriptions:

- multi_token_rest_service_policy

- multi_token_over_ssl_rest_service_policy

If you install this MLR patch, your existing multi token REST policies will not function properly. For a workaround, use Enterprise Manager to perform one of these options:

- Create a copy of the default multi token policy and then add the SPNEGO assertion to the policy.
or

- Create a SPNEGO assertion policy instead of a multi token policy.

For more information, see Appendix B, "Predefined Policies" in the Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

9.34.2 RESTful Client Security Support

This MLR patch allows you to secure RESTful web service clients by attaching Oracle WSM policies globally using WLST and local policies programmatically with support for policy configuration overrides.

You are not required to make any changes to your applications unless you want to use these new features. For more information, see "Attaching Policies to RESTful Web Service Clients Using WLST" in the Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

9.34.3 OAuth 2.0 Support for REST and SOAP Services and Clients

This MLR patch enables Oracle WSM to allow web service clients to interact with the OAuth 2.0 server for both SOAP and REST web services, for "2-legged" authorization.

For more information, see "Using OAuth2 with Oracle WSM" in the Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

9.34.4 REST APIs for Managing Credentials, Keystores, and Trust Stores

This MLR patch includes credential and keystore management REST APIs that provide endpoints for creating and configuring credential stores, keystores, and trust stores for your domain or web services.

For more information about using these APIs, see Oracle Fusion Middleware REST API for Managing Credentials and Keystores with Oracle Web Services Manager.

10 Oracle Fusion Middleware on IBM WebSphere

This chapter describes issues you might encounter when you install and configure supported Oracle Fusion Middleware products on IBM WebSphere. It includes the following topics:

- Section 10.1, "General Issues and Workarounds"

- Section 10.2, "Configuration Issues and Workarounds"

- Section 10.3, "Documentation Errata"

Note:
This chapter contains issues you might encounter while installing, configuring, or managing any of the Oracle Fusion Middleware products on IBM WebSphere.
Be sure to review the product-specific release note chapters elsewhere in this document for any additional issues specific to the products you are using.

10.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topics:

- Section 10.1.1, "Log File Error Message when Starting the SOA Server"

- Section 10.1.2, "Save Settings Button Under Accessibility User Preferences Has Incorrect Label"

- Section 10.1.4, "Cannot Create an XA Connection Factory in the IBM WebSphere Administration Console"

- Section 10.1.5, "Accessibility Mode for User Messaging Preferences is Ignored on an IBM WebSphere Application Server"

- Section 10.1.6, "Adding Shared Libraries to Deploy a Task Form from Oracle JDeveloper"

- Section 10.1.7, "Setting Cookie Paths for Oracle SOA Suite Applications"

- Section 10.1.8, "Deploying a SOA Composite Application to a SOA Cluster"

- Section 10.1.9, "Cannot Deploy a SOA Bundle File from Oracle Enterprise Manager Fusion Middleware Control"

- Section 10.1.10, "One-and-Only-One Event Subscriptions Are Not Supported"

- Section 10.1.11, "Deployed Task Form Startup Failure in IBM WebSphere Administration Console"

- Section 10.1.12, "Oracle BPM Worklist Displays as Undefined in Administration Console"

- Section 10.1.13, "Dashboard Tab May Display Completed SOA Composite Instance States as Running"

- Section 10.1.14, "Two-Way SSL Configuration with Oracle SOA Suite Is Not Supported"

- Section 10.1.15, "Multiple Fault Recovery Failure with the Recover With Options Dialog"

- Section 10.1.16, "IBM WebSphere Application Server - ND Installation Requires a Server Restart"

- Section 10.1.17, "Test Emulations of Asynchronous BPEL Processes Fail"

- Section 10.1.18, "SETMANAGEDCONNECTION() Fails with ILLEGALSTATEEXCEPTION for the AQ Adapter"

- Section 10.1.19, "Invalid PolicySet Error When Accessing a Deployed Oracle Fusion Middleware Application on IBM WebSphere"

- Section 10.1.20, "Cannot Stop or Start Oracle Internal Applications From Fusion Middleware Control on IBM WebSphere"

- Section 10.1.21, "For the JMS Adapter, Instances Become Recoverable Even Without Failover"

- Section 10.1.22, "Kerberos and SPNEGO are not supported with Oracle WSM"

- Section 10.1.23, "REST Security Policies and Templates Not Certified"

10.1.1 Log File Error Message when Starting the SOA Server

When you start the SOA server (for this example, named soa_server1) in an IBM WebSphere Application Server environment, you can receive the following error message in the WAS_HOME/profiles/CustomXX/logs/soa_server1/soa_server1-diagnostic.log file.

This message can be safely ignored.

[2013-02-21T10:46:10.786-08:00] [soa_server1] [ERROR] []
[oracle.soa.mediator.dfw] [tid: Non-deferrable Alarm : 0] [ecid:
disabled,0] [APP: soa-infra] failed to deregister mbean[[
javax.management.InstanceNotFoundException:
oracle.mediator:type=MediatorDiagnostic,name=MediatorDiagnostic
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean
(DefaultMBeanServerInterceptor.java:1106)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.
exclusiveUnregisterMBean (DefaultMBeanServerInterceptor.java:427)
at
. . .
. . .

10.1.2 Save Settings Button Under Accessibility User Preferences Has Incorrect Label

In Business Process Workspace, the Save Settings button under Preferences > Accessibility contains an incorrect label. The label for this button should be OK instead of LABEL_OK.

10.1.3 Oracle Business Process Management Causes java.lang.OutOfMemoryError on IBM WebSphere Application Server

When Oracle Business Process Management (Oracle BPM) is installed on IBM WebSphere Application Server, a java.lang.OutOfMemoryError occurs when running automation tests. This is because the default memory configuration for WebSphere Application Server is set too low for this. This does not occur when Oracle BPM is installed on IBM WebSphere Network Deployment.

As a workaround, make the following changes to the JVM properties:

- Initial heap size increased to 1024MB

- Maximum heap size increased to 2148MB

- MaxPermSize increased to 512 MB

- Verbose garbage collection is selected

10.1.4 Cannot Create an XA Connection Factory in the IBM WebSphere Administration Console

You cannot create an XA connection factory as a messaging provider in the IBM WebSphere Administration Console. The connection factories created by default are non-XA types. For example:

1. Go to IBM WebSphere Administration Console:

http://host:port/ibm/console

2. Go to Resources > Queue connection Factories.

3. Attempt to create an XA-based connection factory.
There is no provision to select an XA mode. You can only create non-XA connection factories.

10.1.5 Accessibility Mode for User Messaging Preferences is Ignored on an IBM WebSphere Application Server

On an IBM WebSphere Application Server instance, the accessibility options will not be set even if you have selected the option on the User Messaging Preferences login screen.

As a workaround, set the accessibility option on the User Messaging Preferences Settings page as follows:

1. Go to Oracle UMS User Messaging Preferences UI:

http://host:port/sdpmessaging/userprefs-ui

2. Enter a valid user name and password.

3. In the User Messaging Preference Login page, select Standard from the Accessibility Mode drop-down list and click Login.

4. After logging in, click the Settings link at the top right corner of the User Messaging Preferences page.

5. In the Settings page, you can set your Accessibility options in the following manner:

- Select Screen Reader from the Accessibility Mode options, if desired.

- Select the High Contrast checkbox if you want the text to be displayed in high contrast.

- Select the Large Fonts check box if you want the text to be displayed in large fonts.

6. Click the Home link to go to the User Messaging Preferences page. The Accessibility options, that you chose to set in the Settings page, will be enabled.

Note:
The Settings options in UMS User Messaging Preferences is session based. If you log out or close the browser, you will lose the accessibility options settings. You will need to reset the settings after each login.

10.1.6 Adding Shared Libraries to Deploy a Task Form from Oracle JDeveloper

When you deploy a SOA composite application with a task flow from Oracle JDeveloper to the SOA server on IBM WebSphere, the application cannot be started correctly due to a ClassNotFound error. The shared library of the application is empty.

As a workaround, perform the following steps:

1. Go to IBM WebSphere Administration Console.

2. Select Applications > Application Types > WebSphere Enterprise Applications > task_form_name > Shared library references.

3. Manually add adf.oracle.domain_1.0_11.1.1.2.0 and oracle.jsp.next_11.1.1_11.1.1.

4. Restart the application.

10.1.7 Setting Cookie Paths for Oracle SOA Suite Applications

By default, applications deployed on IBM WebSphere have their cookie path set to "/". This default setting means that all applications on the same IBM WebSphere cell share the same session identifier. Therefore, as you move between applications, the session identifier value for the previous application is overwritten.

For example, if you access Oracle SOA Composer (/soa/composer), then access Oracle Enterprise Manager (/em), and then return to Oracle SOA Composer (/soa/composer), you are prompted to log in again because the previous session identifier value is overwritten at the point at which you log in to Oracle Enterprise Manager.

Section "Setting Cookie Paths for WebCenter Portal Application Modules Post Deployment" of the Oracle Fusion Middleware Third-Party Application Server Guide describes how to specify unique cookie paths for each application. This action enables you to avoid session invalidation as you move between applications.

In Step 4 of that section, where you click Manage Modules in IBM WebSphere Administration Console to select the modules to manage, and Step 5, where you specify the cookie path, note the following Oracle SOA Suite details to specify.

Target Server

Application Name

Modules

Cookie Path

soa_server1

composer
(Oracle SOA Composer)

soa-composer-was.war

/soa/composer

worklistapp
(Oracle BPM Worklist)

worklist-was.war

/integration/worklistapp

bam_server1

oracle-bam
(Oracle BAM)

bam-web.war

/OracleBAM

soa_server1/bam_server1

usermessagingserver
(Oracle User Messaging Server)

sdpmessaginguserprefs-ui-web.war

/sdpmessaging/userprefs-ui

OracleAdminServer

em
(Oracle Enterprise Manager)

em.war

/em

After performing these tasks, you must restart the target servers (soa_server1, bam_server1, and OracleAdminServer).

10.1.8 Deploying a SOA Composite Application to a SOA Cluster

When you deploy a SOA composite application from Oracle JDeveloper, you cannot select the application server to which to deploy. Instead, the application is deployed to the Deployment Manager by default.

As a workaround, log in to the IBM WebSphere Administration Console, uninstall the application from the Deployment Manager, and reinstall the application to the SOA cluster by using the generated .ear file.

10.1.9 Cannot Deploy a SOA Bundle File from Oracle Enterprise Manager Fusion Middleware Control

You cannot deploy a SOA bundle file from Oracle Enterprise Manager Fusion Middleware Control. As a workaround, use the wsadmin command line shell.

For example, assume vacationapproval.zip is a SOA bundle file that includes three SOA composite applications.

wsadmin> soa.sca_deployComposite("http://myhost.us.example.com:7001",
"/tmp/vacationapproval.zip")

For more information about wsadmin commands, see Section "Oracle SOA Suite wsadmin and WLST Command Differences" of the Oracle Fusion Middleware Third-Party Application Server Guide.

10.1.10 One-and-Only-One Event Subscriptions Are Not Supported

Business events are published to the Event Delivery Network (EDN). EDN provides support for delivering events to one-and-only-one subscribers, in which the event is sent to the subscriber in its own global (that is, JTA) transaction. However, one-and-only-one subscriptions are not supported when using EDN with IBM WebSphere Server.

As a workaround, change the one and only one consistency level of the event subscription to guaranteed in the Create Mediator dialog.

Note:
This change downgrades the consistency level. Therefore, a system failure may cause an event to be delivered more than once because there is no global transaction. If the subscriber fails to process the event, the event is not resent.

10.1.11 Deployed Task Form Startup Failure in IBM WebSphere Administration Console

When you attempt to start a deployed task form application in the IBM WebSphere Administration Console, it fails. You receive an error message similar to the following:

Was2Form failed to start. Check the logs for server dmgr on node
DefaultCellManager01 for details.
ErrorAn error occurred while starting Was2Form. Check the logs for server
dmgr on node DefaultCellManager01 for more information.

As a workaround, perform the following steps:

1. Deploy the task flow in Oracle JDeveloper at the application level, instead of the project level. This generates the EAR file.

2. Undeploy the task flow from the IBM WebSphere Administration Console. Save directly to the master configuration to synchronize changes to all nodes.

3. Deploy the EAR file generated in step 1 through the IBM WebSphere Administration Console.

1. Go to Websphere Enterprise Applications > Install > Pick EAR from Locale file system.

2. Click Next (use the default options).

3. On step 2 of the deploy page "Map modules to servers," select all modules, highlight only the SOA server (for example, soa_server1), and click Apply.

4. On step 3, "Map virtual hosts for Web modules," select the WAR file.

5. At the end, save directly to the master configuration again.

4. Select the EAR file to start it.

10.1.12 Oracle BPM Worklist Displays as Undefined in Administration Console

If you configure an Oracle SOA Suite cluster or single server environment on IBM WebSphere, you may receive an error when accessing Oracle BPM Worklist indicating that it is undefined. If you log in to IBM WebSphere Administration Console, and select Applications > WebSphere enterprise applications > worklistapp > Shared library references, and see that only one row (worklistapp) is displayed when two rows should display (worklistapp and worklist-was.war), you must perform the following steps.

- Uninistall Oracle BPM Worklist (known as worklistapp in the IBM WebSphere Administration Console).

- Re-install Oracle BPM Worklist.

To uninistall Oracle BPM Worklist:

1. Log in to the IBM WebSphere Administration Console.

2. From the panel on the left hand side, select Applications > Application Type > WebSphere enterprise applications.

3. Select the check box for worklistapp from the Enterprise Applications list.

4. Click the Stop button to stop worklistapp.

5. Select worklistapp again.

6. Click the Uninstall button, and click OK.

7. Select Review from the Save and Review options.

8. Select Synchronize changes with nodes, and click Save.

9. Wait until configuration synchronization is complete, then click OK.

10. Confirm that worklistapp is now removed (uninstalled) from Enterprise Applications.

To re-install Oracle BPM Worklist:

1. If not already there, navigate to Applications > Application Type > WebSphere enterprise applications.

2. Click Install.

3. Select the Remote file system option:

1. Click Browse > DefaultCellDepMgrNode.

2. Click the root directory (/), and go to your ORACLE_HOME.

3. Navigate to soa/applications.

4. Select worklist-was.ear, and click OK.

4. Select the default Fast Path, and click Next.

5. Select the installation options:

1. Change the name Oracle BPM Worklist to worklistapp, and click Next.

6. Map the modules to the servers:

1. Select the check boxes for the two modules (jar and war).

2. From the Clusters and servers list, select server=soa_server1 or the server or cluster on which Oracle SOA Suite is installed.

3. Click Apply.

4. Confirm that the two modules now have the correct server value (for example, soa_server1) in the server column.

5. Click Next.

7. Map the virtual hosts for the web modules:

1. Select the one web module.

2. Click Next.

8. On the Summary screen, review the information, and click Finish.
Output displays on the screen, and you are prompted to save or review your local changes.

9. Select Review.

10. Save your workspace changes:

1. Click Synchronize changes with Nodes.

2. Verify that Total changed documents is 29 (if not, there may be an error).

3. Click Save.

11. Wait until configuration synchronization is complete, then click OK.
The worklistapp is now installed and ready to be started.

12. Verify that the worklistapp is present in the Enterprise Applications list.

13. Select worklistapp, and click Start.

14. Confirm that the Application Status is up.

15. Test that Oracle BPM Worklist in accessible by visiting the following URL:

http://host:port/integration/worklistapp

10.1.13 Dashboard Tab May Display Completed SOA Composite Instance States as Running

The Dashboard tab of a SOA composite application in Oracle Enterprise Manager Fusion Middleware Control may show the state of an instance as running even though the instance has actually completed. In this scenario, verify the actual instance state on the Flow Trace page.

10.1.14 Two-Way SSL Configuration with Oracle SOA Suite Is Not Supported

Two-way SSL configuration on IBM WebSphere is not supported. Therefore, there is no support for Oracle Web Service Manager (OWSM) two-way security policies that are SSL-configured. Note that one-way SSL is supported (for example, in which you create an SSL-configured SOA service that invokes another SOA service).

10.1.15 Multiple Fault Recovery Failure with the Recover With Options Dialog

If you click Recover With Options on the Fault and Rejected Messages tab of a SOA composite application, and attempt to recover all faults by selecting Recover All in the Recover With Options dialog, the faults are not recovered and display as pending. The problem only occurs with the Recover With Options dialog. Individual instance recovery and selecting multiple instances for recovery works correctly.

10.1.16 IBM WebSphere Application Server - ND Installation Requires a Server Restart

If you install IBM WebSphere Application Server - Network Deployment (ND) for use with Oracle SOA Suite, you must restart the server for JCA adapter binding components to be active. Otherwise, JNDIs are not active, and you receive the following error message:

Non Recoverable System Fault :
BINDING.JCA-12563 Exception occured when binding was invoked. Exception
occured during invocation of JCA binding: "JCA Binding execute of Reference
operation 'Write' failed due to: JCA Binding Component connection issue. JCA
Binding Component is unable to create an outbound JCA (CCI) connection.
File_MEDComposite:WriteMed [ Write_ptt::Write(body) ] : The JCA Binding
Component was unable to establish an outbound JCA CCI connection due to the
following issue: BINDING.JCA-12510 JCA Resource Adapter location error.
. . .
. . .

10.1.17 Test Emulations of Asynchronous BPEL Processes Fail

You cannot create test emulations involving asynchronous BPEL processes in a SOA composite application on IBM WebSphere. During test execution, this results in an CannotInstantiateObjectException exception error.

10.1.18 SETMANAGEDCONNECTION() Fails with ILLEGALSTATEEXCEPTION for the AQ Adapter

When running Oracle AQ Technology Adapter cases on the WebSphere Platform, you might encounter the following error:

javax.resource.spi.ResourceAllocationException: setManagedConnection: illegal state exception. State = STATE_ACTIVE_FREE MCW = 28392839

To follow-up on this exception, IBM PMR # 69026,756 has been created

10.1.19 Invalid PolicySet Error When Accessing a Deployed Oracle Fusion Middleware Application on IBM WebSphere

When you deploy an application using Oracle Fusion Middleware on IBM WebSphere, you might receive the following runtime error:

oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid:
WSM-06102 PolicyReference The policy reference URI
oracle/wss_username_token_service_policy is not valid

To workaround this issue, perform the following steps:

1. Open the policy-accessor-config.xml file, which can found at the following location:

WAS_HOME/profiles/Dmgr01/config/cells/DefaultCell/fmwconfig/

2. Locate the policy-accessor properties and uncomment the following properties and set the value of each property as shown:

<property name="active.protocol">
remote
</property>
<property name="java.naming.provider.url">
corbaloc:iiop:hostname:rmi.port
</property>

In this example, replace hostname and rmi.port to identify the host and RMI port where the policy manager is running.

No restart is required. By default, the new version of the policy-accessor-config.xml is loaded every 10 mins. However, if you want to pick up the changes immediately, then you can restart the server.

10.1.20 Cannot Stop or Start Oracle Internal Applications From Fusion Middleware Control on IBM WebSphere

When running Oracle Enterprise Manager Fusion Middleware Control on IBM WebSphere, you might experience errors if you attempt to stop or start the internal Oracle applications that are displayed under the Internal Applications folder in the target navigation pane.

The applications listed here are internal Oracle applications. You should not start or stop these applications from Fusion Middleware Control. If you must stop or start these applications, then start or stop the managed servers that host the internal applications.

10.1.21 For the JMS Adapter, Instances Become Recoverable Even Without Failover

When the SOA JMS adapter is installed on WebSphere and is communicating with the IBM WebSphere Default JMS Messaging provider, you must set the property Persistent message reliability to Assured persistent rather than Reliable persistent; otherwise, an incorrect setting can result in loss of messages.

Also, occasionally when the failover scenario does not occur, you can see situations that include an error (transaction timing out, or the closing of JMS session) from the IBM WebSphere JMS, making instances become recoverable. If this happens, you need to manually recover the instances from the Oracle Enterprise Manager.

10.1.22 Kerberos and SPNEGO are not supported with Oracle WSM

Kerberos and Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO) are not supported with Oracle Web Services Manager.

Note the following limitations:

- The Kerberos policies and assertion templates included with Oracle WSM are not supported.

- SPNEGO functionality is not supported.

10.1.23 REST Security Policies and Templates Not Certified

The current release of REST security policies and templates are not certified on IBM WebSphere.

10.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

- Section 10.2.1, "Error Configuring a Cell When IBM WebSphere Installed on Windows 2003 and 2008"

- Section 10.2.2, "Configuring Coherence for a SOA Cluster on IBM WebSphere"

- Section 10.2.3, "Limitations When Configuring Oracle Business Activity Monitoring for High Availability on IBM WebSphere"

- Section 10.2.4, "Requests Received by IBM HTTP Server (IHS) Are Routed to the Fusion Middleware Welcome Page"

- Section 10.2.5, "Unable to Register WSRP/JPDK Producers Through Pagelet Producer Console on IBM WebSphere"

- Section 10.2.6, "Unable to Configure Password Settings Through Pagelet Producer Console on IBM WebSphere"

- Section 10.2.7, "Restart of Deployment Manager Required When Configuring Oracle SOA Suite for High Availability on IBM WebSphere"

- Section 10.2.8, "Additional Configurations For SSO Logout on WebSphere"

- Section 10.2.9, "java.lang.ClassNotFoundException Error Message seen in the Log File When Deploying SimpleApprovalTaskFlow on IBM WebSphere"

10.2.1 Error Configuring a Cell When IBM WebSphere Installed on Windows 2003 and 2008

When IBM WebSphere is installed on Windows 2003 or Windows 2008, the following error sometimes displays when you attempt to create a cell:

WebSphere Profile Update Failed!
No Changes Were Saved To The WebSphere Profile
Profile Location: x:\mydir\APPSER~1\profiles\Dmgr02
Reason Exception saving changes to WebSphere configuration

The issue is due to the Jython libraries shipped with IBM WebSphere. As a workaround:

1. Locate and edit the file:

WAS_HOME\optionalLibraries\jython\Lib\javaos.py

2. Locate the function: _getOsType

3. Edit the _osTypeMap variable to return "nt" as the default.

_osTypeMap = (
( "nt", r"(nt)|(Windows NT)|(Windows NT 4.0)|(WindowsNT)|"
r"(Windows 2000)|(Windows XP)|(Windows CE)" ),
( "dos", r"(dos)|(Windows 95)|(Windows 98)|(Windows ME)" ),
( "mac", r"(mac)|(MacOS.*)|(Darwin)" ),
( "None", r"(None)" ),
( "nt", r"(.*)" ), # default - posix seems to vary mast widely
)

4. Save the changes.

10.2.2 Configuring Coherence for a SOA Cluster on IBM WebSphere

When you configure a SOA cluster on IBM WebSphere, you must configure Oracle Coherence with the host names and other required cluster properties.

For Oracle WebLogic Server environments, refer to the Oracle Coherence configuration information "Configuring Oracle Coherence for Deploying Composites" in the Oracle Fusion Middleware High Availability Guide.

When configuring a SOA Cluster on IBM WebSphere, you perform a similar set of tasks, using the following instructions that are specific to IBM WebSphere:

1. Login to the IBM WebSphere Administrative Console.

2. Navigate to the Java Virtual Machine Custom Properties page:
Servers > soa_server_name > Java and Process Management > Process Definition > Java Virtual Machine > Custom Properties

3. Add the following properties:

- For a multicast cluster:

tangosol.coherence.clusteraddress
tangosol.coherence.clusterport

- For a unicast cluster:

tangosol.coherence.wka1 (= host1)
tangosol.coherence.wka2 (= host2)
tangosol.coherence.localhost = (host?)
tangosol.coherence.wka1.port
tangosol.coherence.wka2.port
tangosol.coherence.localport

10.2.3 Limitations When Configuring Oracle Business Activity Monitoring for High Availability on IBM WebSphere

When you install and configure Oracle BAM on IBM WebSphere, you cannot configure the Oracle BAM servers in the high availability, two-node configuration as described "Configuring High Availability for Oracle BAM" in the Oracle Fusion Middleware High Availability Guide.

Instead, when configuring Oracle BAM on IBM WebSphere, you must use a cold failover configuration. For more information, see "Active-Passive Topologies for Oracle Fusion Middleware High Availability" in the Oracle Fusion Middleware High Availability Guide.

10.2.4 Requests Received by IBM HTTP Server (IHS) Are Routed to the Fusion Middleware Welcome Page

When using Fusion Middleware products on IBM WebSphere ND with an IBM @ HTTPServer (IHS) front end, requests coming in to the Content Server may instead be routed to the Fusion Middleware Welcome page that is running on the cell's Administration Server (OracleAdminServer).

For requests to be properly routed to the Content Server, perform the following steps after fully configuring the cell.

Refer to IBM's Network Deployment documentation for detailed information about editing, propagating, and regenerating the plugin-cfg.xml file:

1. Disable automatic propagation of the plugin-cfg.xml file.
For example:

IBM/HTTPServer/plug-in/config/webserver1/plugin-cfg.xml

2. Manually regenerate plugin-cfg.xml.

3. Manually edit plugin-cfg.xml to remove any entries that may cause requests to be routed to OracleAdminServer.

4. Manually propagate plugin-cfg.xml to the IHS Web server plugin.

If you update the cell after performing these steps, you might see this issue again. If so, then repeat these configuration steps.

10.2.5 Unable to Register WSRP/JPDK Producers Through Pagelet Producer Console on IBM WebSphere

Users are not able to register WSRP/JPDK Producers in Oracle WebCenter Portal's Pagelet Producer Console in an IBM WebSphere Application Server instance. To resolve this issue, follow the steps below to add the necessary role (AppConnectionManager) to the Pagelet Producer application.

1. Open WebSphere Admin Console.

2. Under WebSphere Applications Deployment, right-click pagelet-producer and select Security and Application Roles.

3. Click Application stripe and select pagelet-producer.

4. In the Starts with field, enter AppConnectionManager and click Search. Select the AppConnectionManager role and click Edit.

5. Under Members, click Add to open a dialog that allows you to search for principals and assign the necessary users or groups to the role. Select the required user(s) and click OK to close the dialog.

6. Click OK to save the application settings.

7. Restart the WC_Portlet managed server (the updated security settings do not take effect until the server is restarted).

10.2.6 Unable to Configure Password Settings Through Pagelet Producer Console on IBM WebSphere

While trying to set passwords (such as the Proxy Password), through WebCenter Portal's Pagelet Producer Console in an IBM WebSphere Application Server instance, the following error displays:

ADF_FACES-60097: For more information, please see the server's error log foran entry beginning with: ADF_FACES-60096:Server Exception during PPR, #9

To workaround this issue you must grant some additional permissions to the pagelet producer application:

1. Using wsadmin, connect to the Dmgr server for the cell configured with the pagelet producer application:

WC_HOME/common/bin/wsadmin.sh -conntype SOAP -user admin username -password password -host Dmgr_host -port admin_SOAP_port

See also "Running WebCenter Portal wsadmin Commands " in Oracle Fusion Middleware Third-Party Application Server Guide.

2. Run the following Opss.grantPermission command to grant permissions to the pagelet producer application to update proxy passwords:

wsadmin> Opss.grantPermission(appStripe=None,principalClass=None,principalName=None, codeBaseURL='file:${user.install.root}/installedApps/DefaultCell/pageletproduc er.ear/', permClass='oracle.security.jps.service.credstore.CredentialAccessPermission', permTarget='context=SYSTEM,mapName=ensemble,keyName=*',permActions='read,write ,update,delete')

3. Restart the WC_Portlet managed server (the updated security settings do not take effect until the server is restarted).

10.2.7 Restart of Deployment Manager Required When Configuring Oracle SOA Suite for High Availability on IBM WebSphere

To configure Oracle SOA Suite for high availability on WebSphere, follow the instructions in "Federating a Remote Machine to an Existing Cell" in Oracle Fusion Middleware Configuration Guide for IBM WebSphere Application Server.

However, when following these instructions, you must be sure to stop and restart the Deployment Manager before configuration of the second node. For more information, see "Configuring the Deployment Manager to Detect the Remote Node Agent" in the Oracle Fusion Middleware Third-Party Application Server Guide.

10.2.8 Additional Configurations For SSO Logout on WebSphere

You must configure the Sync Filter to get SSO logout on WebSphere to work well. In the deployment descriptor (for example, web.xml) of the application, the filter can be configured for certain URL patterns as in the following example.

<filter>
<display-name>SSOSessionSynchronizationFilter</display-name>
<filter-name>SSOSessionSynchronizationFilter</filter-name>
<filter-class>oracle.security.was.filter.SSOSessionSynchronizationFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>SSOSessionSynchronizationFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>

You also need to add the following JAR to the WebSphere classpath:

$MiddleWareHome/oracle_common/modules/oracle.ssofilter_11.1.1/ssofilter.jar

10.2.9 java.lang.ClassNotFoundException Error Message seen in the Log File When Deploying SimpleApprovalTaskFlow on IBM WebSphere

You can receive an ArrayIndexOutOfBoundsException error in the log file after accessing the Log Configuration page in Oracle Enterprise Manager Fusion Middleware Control.

The Log Configuration page is displayed correctly. The error has no impact on product functionality and can be ignored.

10.3 Documentation Errata

This section describes documentation errata. It includes the following topic:

- Section 10.3.1, "Updates to Steps for Patching WebCenter Portal 11.1.1.6.0 Installations to 11.1.1.7.0"

- Section 10.3.2, "Updates to Steps for Configuring Oracle Business Intelligence for Scaling Out on IBM WebSphere"

- Section 10.3.3, "Updates to Section on Upgrading"

10.3.1 Updates to Steps for Patching WebCenter Portal 11.1.1.6.0 Installations to 11.1.1.7.0

Steps that describe how to patch a WebCenter Portal 11.1.1.6.0 installation to 11.1.1.7.0 are documented in "Patching WebCenter Portal on IBM WebSphere from 11.1.1.6 to 11.1.1.7"in Oracle Fusion Middleware Third-Party Application Server Guide.

Changes to the information provided are listed below:

- Before you start - Determine your existing Oracle Web Services Manager (OWSM) security policy URIs
Oracle recommends that you record your existing OWSM policy URI settings before you patch to WebCenter Portal 11.1.1.7.0. This step is missing from the documentation.

To determine your existing settings prior to patching WebCenter Portal 11.1.1.6.0, follow the steps described in "Determining OWSM Policy URIs for Spaces, Discussions, and Portlet Web Service End Points" in Oracle Fusion Middleware Patching Guide.

- Step 10 - Use the Patch Set Assistant to update all the required schemas
This step must be done before Step 5 "Start the upgraded IBM WebSphere node agent and deployment manager".

10.3.2 Updates to Steps for Configuring Oracle Business Intelligence for Scaling Out on IBM WebSphere

Section 10.2.11.1 of Oracle Fusion Middleware Third-Party Application Server Guide describes the steps for configuring for scaling out JEE components for Oracle Business Intelligence on IBM WebSphere. These steps must be updated because they differ slightly depending on whether you install with the Installer for 32-bit or 64-bit systems.

The steps when using the 32-bit Installer are as follows:

1. Use the Administration Console for IBM WebSphere to verify that the following conditions are met:

- Oracle Business Intelligence is installed with IBM WebSphere on the first host computer.

- The installation of Oracle Business Intelligence on the first host computer includes two servers, which are named OracleAdminServer and bi_server1. The installation also includes a Node Agent and a single Deployment Manager.

- The servers are managed as a cluster for IBM WebSphere that is called bi_cluster.

2. Install IBM WebSphere on the second host computer. Ensure that you select None as the installation type and click Finish on the Installation Results page.
The Profile Management tool is displayed at the end of the IBM WebSphere installation. Provide the settings for the Profile Management tool as described in the existing Step 4 in Section 10.2.11.1.

3. Stop the NodeAgent using the stopNode.sh script.

4. Apply any patches as appropriate for IBM WebSphere on the second host computer, so that the second computer runs the same version as the first computer.

5. Start the NodeAgent using the startNode.sh script.

6. Install Oracle Business Intelligence on the second host computer and select the following options:

- For installation type, select Software-Only.

- Install Oracle Business Intelligence in the same directory structure on the second host computer as it is installed on the first host computer, such as /mydir/myname/mw_home

7. Follow the existing Step 6 in Section 10.2.11.1 to create an IBM Managed Server (similar to bi_server1 on the first node) to handle the JEE applications for Oracle Business Intelligence on the new node.

The steps when using the 64-bit Installer are as follows:

1. Use the Administration Console for IBM WebSphere to verify that the following conditions are met:

- Oracle Business Intelligence is installed with IBM WebSphere on the first host computer.

- The installation of Oracle Business Intelligence on the first host computer includes two servers, which are named OracleAdminServer and bi_server1. The installation also includes a Node Agent and a single Deployment Manager.

- The servers are managed as a cluster for IBM WebSphere that is called bi_cluster.

2. Install IBM WebSphere on the second host computer. Ensure that you select None as the installation type and click Finish on the Installation Results page.

3. Apply any patches as appropriate for IBM WebSphere on the second host computer, so that the second computer runs the same version as the first computer.
Unlike for the 32-bit Installer, the NodeAgent does not exist until the profile is created for the 64-bit Installer.

4. Run the Profile Management tool as described in the existing Step 4 in Section 10.2.11.1.

5. Stop the NodeAgent using the stopNode.sh script.

6. Install Oracle Business Intelligence on the second host computer and select the following options:

- For installation type, select Software-Only.

- Install Oracle Business Intelligence in the same directory structure on the second host computer as it is installed on the first host computer, such as /mydir/myname/mw_home

7. Start the NodeAgent using the startNode.sh script.

8. Follow the existing Step 6 in Section 10.2.11.1 to create an IBM Managed Server (similar to bi_server1 on the first node) to handle the JEE applications for Oracle Business Intelligence on the new node.

10.3.3 Updates to Section on Upgrading

Section 10.4 describes how to upgrade Oracle Business Intelligence to run on IBM WebSphere. The section begins with a bulleted list that needs to be reworded as follows:

- If you have a 10g Release of Oracle Business Intelligence that is running on IBM WebSphere.

- If you have a previous 11g Release of Oracle Business Intelligence that is running on Oracle WebLogic Server.

11 SSL Configuration in Oracle Fusion Middleware

This chapter describes issues associated with SSL configuration in Oracle Fusion Middleware. It includes the following topic:

- Section 11.1, "General Issues and Workarounds"

11.1 General Issues and Workarounds

This section describes general issues and workarounds. It includes the following topic:

- Section 11.1.1, "Incorrect Message or Error when Importing a Wallet"

11.1.1 Incorrect Message or Error when Importing a Wallet

Problem 1

Fusion Middleware Control displays an incorrect message when you specify an invalid wallet password while attempting to import a wallet. The issued message "Cannot create p12 without password." is incorrect. Instead, it should notify the user that the password is incorrect and request a valid password.

Problem 2

Fusion Middleware Control displays an incorrect message when you attempt to import a password-protected wallet as an autologin wallet. The issued message "Cannot create p12 without password." does not provide complete information. Instead, it should notify the user that importing a password-protected wallet requires a password.

Problem 3

If you attempt to import an autologin wallet as a password-protected wallet using either Fusion Middleware Control or WLST, a NullPointerException error is displayed.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2015, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.