Oracle® Fusion Middleware

Oracle Fusion Middleware Release Notes

11g Release 1 (11.1.1) for Oracle Solaris

E14772-55

April 2014

Oracle Fusion Middleware Oracle Fusion Middleware Release Notes, 11g Release 1 (11.1.1) for Oracle Solaris

E14772-55

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

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, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

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

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

Part I Oracle Fusion Middleware

1 Introduction

- 1.1 Latest Release Information

- 1.2 Purpose of this Document

- 1.3 System Requirements and Specifications

- 1.4 Memory Requirements

- 1.5 Certification Information

- 1.5.1 Where to Find Oracle Fusion Middleware Certification Information

- 1.5.2 Certification Exceptions

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

- 1.5.2.2 Excel Export Issue on Windows Vista Client

- 1.5.2.3 Restrictions on Specific Browsers

- 1.5.2.4 Process to Install and Configure WebCenter With 32-bit JDK on Supported 64-Bit Platform

- 1.5.3 JMSDELIVERYCOUNT Is Not Set Properly

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

- 1.6 Downloading and Applying Required Patches

- 1.7 Licensing Information

2 Installation, Patching, and Configuration

- 2.1 Installation Issues and Workarounds

- 2.1.1 Issues Pertaining to Oracle SOA Suite Installation

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

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

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

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

- 2.1.2.2 Considerations When Installing Oracle Portal 11g

- 2.1.2.3 Prerequisite Warnings During Installation

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

- 2.1.3 Issues Pertaining to Oracle Web Tier Installation

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

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

- 2.1.4 Issues Pertaining to Oracle Identity Management Installation

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

- 2.1.4.2 Extending the Schema in Oracle Internet Directory

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

- 2.1.4.4 Information about the Oracle Virtual Directory Adapters

- 2.1.4.5 Enabling the Retry Button

- 2.1.4.6 Server Startup Failures on Linux Operating Systems

- 2.1.4.7 Configuring OPMN Request Port

- 2.1.4.8 Silent Install with Privileged Ports on Linux Operating Systems

- 2.1.5 Issues Pertaining to JDK and JRE Installation

- 2.1.5.1 Specifying the JRE Location if Installing with Automatic Updates

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

- 2.1.6 Issues Pertaining to Oracle Universal Installer

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

- 2.1.6.2 Installer is Checking for the Wrong System Patches on Solaris x86-64

- 2.1.7 Issues Pertaining to Database and Schema Installation

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

- 2.1.7.2 Setting the Correct Permission for the DBMS_JOB Database Package

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

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

- 2.1.8 Error Messages and Exceptions Seen During Installation

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

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

- 2.1.9 Issues Pertaining to Product Deinstallation

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

- 2.1.9.2 Deinstallation Does Not Remove WebLogic Domains

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

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

- 2.1.12 Problems Installing in Thai and Turkish Locales

- 2.1.13 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 Patching Oracle WebCenter Portal and Oracle WebCenter Content with Other Fusion Middleware Products in the Same Domain

- 2.2.3 Issues Pertaining to Patching Oracle SOA Suite

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

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

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

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

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

- 2.2.3.6 Manual Steps for Migrating Oracle UMS and Oracle MDS

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

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

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

- 2.2.4 Issues Pertaining to Patching Oracle WebCenter Portal

- 2.2.4.1 Configuring Additional Crawl Sources for Discussions After Patching Oracle WebCenter Portal

- 2.2.4.2 Problem Using WebCenter Portal Customizations with .jsp Pages

- 2.2.4.3 Errors When Updating Oracle WebCenter Portal Using WLST Commands

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

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

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

- 2.2.4.7 Patches Required After Updating Oracle WebCenter Portal

- 2.2.5 Issues Pertaining to Patching Oracle Identity Management

- 2.2.5.1 Access Denied When Running the oimPS1PS2upgrade Script

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

- 2.2.5.3 Installer Does Not Detect Existing Oracle Home

- 2.2.5.4 Uploading Third Party JAR Files to the Database

- 2.2.5.5 Access Policy With Approval Does Not Work After Patch

- 2.2.5.6 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.5.7 Harmless Error When Running the upgradeOpss() Command When Upgrading Oracle Identity Management

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

- 2.2.5.9 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.5.10 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.5.11 Harmless Exception Seen When Starting Oracle Identity Management Server 11g Release 1 (11.1.1.5.0)

- 2.2.6 Issues Pertaining to Patching System Components

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

- 2.2.6.2 Redeploy System Components to Ensure Proper Deinstallation

- 2.2.6.3 Setting Execute Permissions for emctl When Migrating System Components

- 2.2.7 Issues Pertaining to Version Numbers After Patching

- 2.2.7.1 Some Applications Show Old Version Number After Patching

- 2.2.7.2 MDS Schema Version Number is Incorrect

- 2.2.7.3 Oracle BI Components Show Incorrect Version Number After Patching

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

- 2.2.8 Issues Pertaining to Displays During or After Patching

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

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

- 2.2.9.1 Harmless Warnings When Running upgradeOpss()

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

- 2.2.9.3 Error When Accessing the Oracle Portal Home Page

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

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

- 2.2.11 Resolving Oracle Service Bus Object Conflicts

- 2.2.12 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 SOAINFRA Schema Contains Invalid Objects in 11g Release 1 (11.1.1.6.0)

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

- 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 Password Requirements for Oracle Internet Directory Administrator

- 2.3.2.6 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.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.4.3 Some Text Truncated on the "Server Start Mode and JDK Configuration" Screen

- 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 Oracle WebCenter Portal wc-post-install.py Script Not Supported for Oracle RAC Datasources

- 2.3.11 Changing the Listen Address of a Managed Server

- 2.3.12 Domain Extension Overwrites JDBC Data Source Name

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

- 2.3.14 Deleting the Browser Cache in Browsers

- 2.3.15 Oracle Fusion Middleware Configuration Fails

- 2.4 Known Issues

- 2.4.1 Oracle Universal Installer Lists Errors While Checking For Required Operating System Patches On Solaris 10

- 2.4.2 Forms and Reports Builder Not Supported

- 2.4.3 Failure to Start a 64-bit JVM Process on Oracle Solaris on SPARC (64-bit)

- 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

- 2.5.3 Incorrect Command Specified for Adding the AttributeAccessPermission Grant after Patching Oracle WebCenter Portal

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.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 Upgrade Assistant Fails While Restarting OPMN Managed Processes After Oracle Identity Federation Upgrade

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

- 3.1.11 Misleading Error Message When Upgrading Oracle Internet Directory

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

- 3.1.13 Additional Steps Required When Upgrading Human Taskflow Projects

- 3.1.14 Stopping Oracle Virtual Directory Processes During Upgrade

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

- 3.1.16 Upgrading Oracle Access Manager Middle Tier

- 3.1.17 Inaccurate Results When Running the Upgrade Assistant Verify Feature

- 3.1.18 Missing jdk_version.log File When Launching Upgrade Assistant

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

- 3.1.20 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 Patching the Schema for Oracle Internet Directory

- 3.2.3 Changing the patchmaster.ValidationErrorContinue Property

- 3.2.4 Changing the Default Setting for Validation Tasks

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

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

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

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

- 3.2.7.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 Display Problems When Running JDK 160_18 on Intel Systems that Support the SSE4.2 Instruction Set

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

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

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

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

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

- 5.1.16 Incorrect or Missing Metrics Help Information

- 5.1.17 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 Fusion Middleware on IBM WebSphere

- 7.1 General Issues and Workarounds

- 7.1.1 Log File Error Message when Starting the SOA Server

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

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

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

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

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

- 7.1.7 Setting Cookie Paths for Oracle SOA Suite Applications

- 7.1.8 Deploying a SOA Composite Application to a SOA Cluster

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

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

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

- 7.1.12 Oracle BPM Worklist Displays as Undefined in Administration Console

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

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

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

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

- 7.1.17 Test Emulations of Asynchronous BPEL Processes Fail

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

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

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

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

- 7.1.22 Kerberos and SPNEGO are not supported with Oracle WSM

- 7.1.23 REST Security Policies and Templates Not Certified

- 7.2 Configuration Issues and Workarounds

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

- 7.2.2 Configuring Coherence for a SOA Cluster on IBM WebSphere

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

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

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

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

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

- 7.2.8 Additional Configurations For SSO Logout on WebSphere

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

- 7.2.10 Oracle Fusion Middleware Configuration Fails on IBM WebSphere

- 7.2.11 Domain Creation Fails During the Oracle Data Integrator Configuration on IBM WebSphere

- 7.2.12 OutofMemory Error Appears During the Oracle Data Integrator Configuration on IBM WebSphere

- 7.3 Documentation Errata

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

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

- 7.3.3 Updates to Section on Upgrading

Part II Oracle Development Tools

8 Oracle JDeveloper and Oracle Application Development Framework (ADF)

9 Oracle TopLink

- 9.1 General Issues and Workarounds

- 9.1.1 TopLink Object-Relational Issues

- 9.1.1.1 Cannot set EclipseLink log level in WLS System MBean Browser

- 9.1.1.2 Incorrect outer join SQL on SQLServer2005

- 9.1.1.3 UnitOfWork.release() not Supported with External Transaction Control

- 9.1.1.4 Returning Policy for UPDATE with Optimistic Locking

- 9.1.1.5 JDBC Drivers returning Timestamps as Strings

- 9.1.1.6 Unit of Work does not add Deleted Objects to Change Set

- 9.1.2 TopLink Workbench Issues

- 9.1.2.1 User Interface Issue

- 9.1.2.2 Accessibility

- 9.1.2.3 Running the TopLink Workbench on Windows OS

- 9.1.3 Oracle Database Extensions with TopLink

- 9.1.3.1 Template JAR for Spatial and XDB Support in Oracle WebLogic Server

- 9.1.4 Allowing Zero Value Primary Keys

- 9.1.5 Managed Servers on Sybase with JCA Oracle Database Service

- 9.1.6 Logging Configuration with EclipseLink Using Container Managed JPA

- 9.1.7 Grid Cache requires CacheLoader

Part III Web Tier

10 Oracle HTTP Server

- 10.1 mod_security Reintroduced

- 10.2 Installing OHS 11.1.1.7 with WLS 12g

11 Oracle Web Cache

- 11.1 Configuration Issues and Workarounds

- 11.1.1 Reset the Random Password Generated When Installing Oracle Portal, Forms, Reports, and Discoverer

- 11.1.2 Running Oracle Web Cache Processes as a Different User Is Not Supported

- 11.1.3 Using Web Cache in an IPv6 Network

- 11.2 Documentation Errata

- 11.2.1 Procedure to Enable Generation of Core Dump

- 11.2.2 Clarification About Support for CRLs

- 11.2.3 Clarifications About Configuring the CRL Location

Part IV Oracle WebLogic Server

12 Oracle WebLogic Server

- 12.1 General Issues and Workarounds

- 12.1.1 Multi-Byte Characters Display Incorrectly in Filenames When Using Safari

- 12.1.2 Oracle WebLogic Server Version Number

- 12.1.3 Oracle ojdbc14.jar File Has Been Changed to ojdbc6.jar

- 12.1.4 Strong Password Enforcement May Cause Issues With WLST Offline Scripts

- 12.1.5 In Turkish Locale, MDS Initialization Fails

- 12.1.6 Administration Server Reports a 'Too Many Open Files' Message on the EM Console

- 12.1.7 Availability of Sun JDK 6 U35-B52 for 10.3.5.0 Oracle WLS Generic Installation

- 12.2 Administration Console Issues and Workarounds

- 12.2.1 Cached JDBC Information is not Displayed

- 12.2.2 Pressing Browser Back Button Discards Context

- 12.2.3 Unsupported Work Manager Configurations Can Be Created

- 12.2.4 Server Status Table Reflects Inconsistent Information

- 12.2.5 Exceptions When Defining a Security Policy for an EJB

- 12.2.6 Administration Console Does Not Always Reflect External Changes Made in a Deployment Plan

- 12.2.7 Oracle OCI Driver Support

- 12.2.8 Data Takes a Long Time to Display on the Metric Browser Tab

- 12.3 Apache Beehive Support Issues and Workarounds

- 12.4 Clustering Issues and Workarounds

- 12.4.1 Threads Are Blocked on Cluster Messaging in Unicast Mode

- 12.5 Configuration Issues and Workarounds

- 12.5.1 ASProvWorkflowException Occurs When Creating a WebLogic Domain

- 12.5.2 Directory For a Non-Existent Server Name Is Created

- 12.5.3 Abnormal Behavior in Terminal Window After Entering WebLogic Password

- 12.5.4 Creating and Updating Domains Takes Too Long

- 12.5.5 Password Field Is Not Editable When Configuring a New Domain

- 12.6 Connector (Resource Adapter) Issues and Workarounds

- 12.7 Console Extensions Issues and Workarounds

- 12.8 Core Server and Core Work Manager Issues and Workarounds

- 12.8.1 Threads Become Stuck While Waiting to Get a Connection

- 12.8.2 Using IPv6-Formatted Addresses

- 12.8.3 Server Cannot Be Started After a Whole Server Migration

- 12.8.4 Object State is not Retained After Renaming Field

- 12.8.5 Forcing Unicast Messages To Be Processed in Order

- 12.8.6 Servers Configured to Listen on a Host Name Are Listening on a Different Host Name After Startup

- 12.8.7 Administration Server or Node Manager Cannot Track the Status of a Managed Server

- 12.8.8 Multicast Traffic Observed to be Unreliable During or After a Network Partition

- 12.9 Deployment Issues and Workarounds

- 12.9.1 security-permission Element is not Available in weblogic-application.xml

- 12.9.2 Extraneous String Values Interpreted as File Specification

- 12.9.3 java.lang.NoClassDefFoundError is Displayed

- 12.9.4 The restore Method Does Not Update the DConfig Bean With Plan Overrides

- 12.9.5 config-root <directory> not found Warning Is Displayed When Applying a Plan

- 12.9.6 Deployment Task Fails When a Large Application File Is Deployed

- 12.9.7 Application State Is Not Updated If the Server Starts in MSI Mode

- 12.9.8 Attempting to Redeploy an Application Fails if the Application is Already Deployed Using a Different Source File Location

- 12.10 EJB Issues and Workarounds

- 12.10.1 Primary Key in Oracle Table is CHAR

- 12.10.2 No Available Annotation That Enables Creation of a Clusterable Timer

- 12.10.3 Kodo's MappingTool Cannot Generate Schemas

- 12.10.4 Extensions to the JPA Metadata Model Can Only Be Specified Via Annotations

- 12.10.5 Lookup Method Injection Not Supported by Spring

- 12.10.6 Deserializing a JDO PersistenceManagerFactory in a Managed Environment May Fail

- 12.10.7 Indexes Not Always Created During Schema Creation

- 12.10.8 OpenJPA throws an exception when @Id fields are also annotated as @Unique

- 12.10.9 Cache Hit and Miss Counts May Rise Unexpectedly

- 12.10.10 Open JPA Tries to Create a Table Even if the Table Exists

- 12.10.11 EJB Applications Fail During Serialization

- 12.10.12 Non-Transactional Message-Driven Bean Container Can Fail to Provide Reproducible Behavior For Foreign Topics

- 12.11 Examples Issues and Workarounds

- 12.11.1 Security Configuration in medrec.wls.config

- 12.11.2 HTML File not Created for StreamParser.java File

- 12.11.3 Warning Message Appears When Starting Medrec or Samples Domain

- 12.12 HTTP Publish/Subscribe Server Issues and Workarounds

- 12.12.1 Authentication and Authorization of the Local Client is not Supported

- 12.12.2 Event Messages Published by Local Clients Cannot Be Received

- 12.12.3 Event Messages Published By Local Clients Do Not Go Through Filters

- 12.13 Installation Issues and Workarounds

- 12.13.1 Sybase JDBC Drivers Not Downloaded with Upgrade Installation

- 12.13.2 Improper Rollback to Previous Installation May Occur After Exiting an Upgrade Installation Prematurely

- 12.13.3 WebLogic Server Installer Fails With Insufficient Disk Space Error

- 12.13.4 Installation Fails with Fatal Error

- 12.13.5 Oracle WebLogic Server Installation Fails on Oracle Solaris 11

- 12.14 Java EE Issues and Workarounds

- 12.14.1 FastSwap May Relax the Access Modifiers of Fields and Methods

- 12.14.2 FastSwap Does Not Support Redefinition of the Entity Bean and ejbClass

- 12.14.3 Classpath Order Is Not Guaranteed When There Are Multiple JARs in an EAR File

- 12.15 JDBC Issues and Workarounds

- 12.15.1 Call To setTransactionIsolation() May Fail When Using the JDBC Driver for MS SQLServer

- 12.15.2 An Attempt to Access a Remote 10.3.2 or Later WLS Data Source Fails

- 12.15.3 ORA-01591 Errors Occur on SOA Servers Configured to Use Multiple Oracle RAC Nodes

- 12.16 JDK Issues and Workarounds

- 12.16.1 SSLv2Hello Not Supported by IBM JDK

- 12.17 JMS Issues and Workarounds

- 12.17.1 Deployment Descriptor Validation Fails

- 12.17.2 Exception When Multiple Producers Use the Same Client SAF Instance

- 12.17.3 Multi-byte Characters are not Supported in Store File and Directory Names

- 12.17.4 Generation of the Default UOO Name Has Changed

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

- 12.17.6 JMS Message Consumers Will Not Always Reconnect After a Service Migration

- 12.17.7 Forcing Unicast Messages To Be Processed in Order

- 12.18 JNDI Issues and Workarounds

- 12.19 JSP and Servlet Issues and Workarounds

- 12.19.1 Deployment Plans Cannot Be Used To Override Two Descriptors

- 12.19.2 Spring Dependency Injection Not Supported on JSP Tag Handlers

- 12.19.3 503 Error When Accessing an Application With a Valid sessionid

- 12.20 JTA Issues and Workarounds

- 12.21 Java Virtual Machine (JVM) Issues and Workarounds

- 12.21.1 1.4 Thin Client Applet Cannot Contact WebLogic Server

- 12.21.2 JRockit JVM Appears to Freeze When Doing Long Array Copies

- 12.21.3 Using AWT libraries May Cause a JVM Crash

- 12.22 Monitoring Issues and Workarounds

- 12.22.1 MBean Attributes Not Explicitly Marked as @unharvestable Appear as Harvestable

- 12.22.2 Events Generated By the JVM Level Are Not Generated at Low Volume

- 12.22.3 WLDF Performance Issues Can Occur When JVM Events Are Enabled

- 12.23 Node Manager Issues and Workarounds

- 12.24 Operations, Administration, and Management Issues and Workarounds

- 12.25 Oracle Kodo Issues and Workarounds

- 12.26 Protocols Issues and Workarounds

- 12.27 RMI-IIOP Issues and Workarounds

- 12.27.1 Ant 1.7 rmic Task Incompatibility

- 12.28 Security Issues and Workarounds

- 12.28.1 StoreBootIdentity Works Only if the Appropriate Server Security Directory Exists

- 12.28.2 Boot Time Failure Occurs With SecurityServiceException

- 12.28.3 Authentication Failure After Upgrading a Domain From WLS 6.1

- 12.28.4 InvalidParameterException Message Generated and Displayed

- 12.28.5 Enabling Both the Authentication and Passive Attributes In SML 2.0 Service Provider Services Is an Invalid Configuration

- 12.28.6 Running the WebLogic Full Client in a Non-Forked VM

- 12.29 SNMP Issues and Workarounds

- 12.30 Spring Framework on WebLogic Server Issues and Workarounds

- 12.30.1 OpenJPA ClassFileTranformer Does Not Work When Running on JRockit

- 12.30.2 petclinic.ear Does Not Deploy on WebLogic Server

- 12.31 System Component Architecture (SCA) Issues and Workarounds

- 12.32 Upgrade Issues and Workarounds

- 12.32.1 Domains Created on WebLogic Server 10.3.1 Cannot Be Run on WebLogic Server 10.3

- 12.33 Web Applications Issues and Workarounds

- 12.33.1 Administration Console Fails to Implement session-timeout Changes

- 12.33.2 Connection Pool Connection Reserve Timeout Seconds Value is Overridden

- 12.33.3 Database Connections Become Unstable When a PoolLimitSQLException Occurs

- 12.33.4 Web Page Fails to Open When Accessing It Using the SSL Port

- 12.34 WebLogic Server Scripting Tool (WLST) Issues and Workarounds

- 12.34.1 Permission Denied Error Occurs for WLST Offline Logging

- 12.34.2 Property Names Containing '.' Characters Are Not Supported by loadProperties

- 12.34.3 Invalid cachedir Created by Jython Causes WLST to Error Out

- 12.34.4 WLST returnType='a' Option Returns Child Management Objects

- 12.35 Web Server Plug-Ins Issues and Workarounds

- 12.35.1 MOD_WLS_OHS Does Not Fail Over

- 12.36 Web Services and XML Issues and Workarounds

- 12.36.1 weblogic.wsee.jaxws.mdb.DispatchPolicy WorkManager Cannot Be Found

- 12.36.2 Multiple Resize Buffer Calls Occur

- 12.36.3 Troubleshooting Problems When Applying the WebLogic Advanced Web Services for JAX-WS Extension Template

- 12.36.4 Sparse Arrays and Partially Transmitted Arrays Are Not Supported

- 12.36.5 WSDL Compiler Does Not Generate Serializable Data Types

- 12.36.6 Use of Custom Exception on a Callback

- 12.36.7 Cannot Use JMS Transport in an Environment That Also Uses a Proxy Server

- 12.36.8 clientgen Fails When Processing a WSDL

- 12.36.9 JAX RPC Handlers in Callback Web Services Are Not Supported

- 12.36.10 Message-level Security in Callback Web Services Is Not Supported

- 12.36.11 Handling of Java Method Arguments or Return Parameters That Are JAX-RPC-style JavaBeans

- 12.36.12 IllegalArgumentException When Using a Two-Dimensional XML Object in a JWS Callback

- 12.36.13 Using SoapElement[] Results in Empty Array

- 12.36.14 FileNotFound Exception When a Web Service Invokes Another Web Service

- 12.36.15 Client Side Fails to Validate the Signature on the Server Response Message

- 12.36.16 xmlcatalog Element Entity Cannot Be a Remote File or a File in an Archive

- 12.36.17 Catalog File's public Element Is Not Supported When Using XML Catalogs

- 12.36.18 Local xmlcatalog Element Does Not Work Well

- 12.36.19 JAXRPC Client Does Not Encode the HTTP SOAPAction Header With Multi-byte Characters

- 12.36.20 External Catalog File Cannot Be Used in the xmlcatalog Element of clientgen

- 12.36.21 Exceptions When Running Reliable Messaging Under Heavy Load

- 12.36.22 ClassNotFound Exception Occurs When Using wseeclient.jar

- 12.36.23 Incomplete Configuration When Adding Advanced Web Services Component to SOA Domain

- 12.36.24 WS-AT Interoperation Issues With WebSphere and WebLogic Server

- 12.37 WebLogic Tuxedo Connector Issues and Workarounds

- 12.37.1 View Classes are not Set on a Per Connection Basis

- 12.38 Documentation Errata

- 12.38.1 Japanese Text Displays in Some Search Results Topics Avitek Medical Records

- 12.38.2 HTML Pages For Downloaded Libraries Do Not Display Properly

- 12.38.3 Evaluation Database Component Is Not Listed For silent.xml

- 12.38.4 Instructions for Reliable SOAP Messaging Code Example Are Incorrect

- 12.38.4.1 About the Example

- 12.38.4.2 Files Used in This Example

- 12.38.4.3 Prepare the Example

- 12.38.4.4 Run the Example

Part V Oracle WebCenter Portal

13 Oracle WebCenter Portal

- 13.1 General Issues and Workarounds

- 13.1.1 Installing the WebCenter Portal Extension Version 11.1.1.8.3 for JDeveloper

- 13.1.2 Support for Discussions Server from Jive Software

- 13.1.3 Oracle WebCenter Portal's Pagelet Producer Failover Support

- 13.1.4 SQL Query with NCHAR Data Type Throws Exception

- 13.1.5 Configuring the REST Server Post-Installation

- 13.1.6 Cannot Customize or Personalize a JSF Portlet

- 13.1.7 Portals Do Not Display Correct Language When WebCenter Portal is Accessed Using OAM

- 13.1.8 Announcement Publication Format can be Incorrect in Thai

- 13.1.9 The Run as Servlet Link on Producer Test Page Does Not Work for JSF Portlet

- 13.1.10 Using OpenSocial Pagelets to Post Activities to User's Activity Stream

- 13.1.11 Accessing Owners' Profile Information Using the OpenSocial API

- 13.1.12 Unable to View Entire Content on iPad as Scrollbars Not Displayed

- 13.1.13 RSS Links Not Working Properly on iPad

- 13.1.14 Cannot Upload Content Using iPad

- 13.1.15 Cannot Copy Text Displayed on Pages

- 13.1.16 Embedded Images Not Rendered

- 13.1.17 Unable to Check Out a Document When Using Firefox First Time

- 13.1.18 Web Clipping Portlet is Deprecated

- 13.1.19 Deployment Fails Because Versioned Applications Are Not Supported

- 13.1.20 Exception Reported When Running WC_Spaces Managed Server

- 13.1.21 Upgraded Portals Do Not Render Properly

- 13.1.22 Displaying a Page on a Device when the Page Name Includes a Space

- 13.1.23 Problem Integrating PeopleSoft and WebCenter Portal

- 13.1.24 Unable to Create Pages in Portals Created Using REST APIs

- 13.1.25 Mobile Page Variants Not Displayed Correctly on Nexus 4 Devices

- 13.1.26 Configuring Oracle SES 11.2.2.2 for Oracle WebCenter Portal

- 13.1.27 Clicking the Create Topic Button in a Discussion Forum Does Not Open the Create Topic Dialog

- 13.1.28 Duplicate Copies Created when Copying, Moving, or Cutting and Pasting Files and Folders with the Same Name

- 13.1.29 Invalid Characters in Folder and File Names

- 13.1.30 Comment and Tag Updates Not Listed in Activity Stream of Portal Framework Applications

- 13.1.31 Imprecise Error Message When Uploading a File with the Same Name as a Checked Out File

- 13.1.32 Cannot Create or Move Files by Using CMIS REST API

- 13.1.33 Tabs Not Displayed on Document Management Taskbar

- 13.1.34 Imprecise Error Messages When Renaming or Pasting a File in Workflow

- 13.1.35 Unable to Access Files Using Direct URL in Home Portal

- 13.1.36 Creating a Portal based on a Template Containing Blogs or Wikis

- 13.1.37 FrameworkFolders Not Supported When Oracle BPM Process Spaces is Enabled for WebCenter Portal

14 Web Services Development, Security, and Administration

- 14.1 Using Multibyte User Credentials with wss_http_token_* Policy

- 14.2 Performing a Bulk Upload of Policies

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

- 14.4 Removing Post-deployment Customizations

- 14.5 Reviewing Localization Limitations

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

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

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

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

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

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

- 14.12 Custom Policy Fails When an Empty Subject Is Passed

- 14.13 Possible Limitation When Using Custom Exactly-one Policies

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

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

- 14.16 SAML Bearer Token Policies Now Signed by Default

- 14.17 Security Policies Do Not Work on Subscriber Mediator Component

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

- 14.19 Manual Step Required to Uptake Changes in Predefined Policy

- 14.20 Usage Tracking Not Enabled for WebLogic Web Service Client

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

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

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

- 14.24 New Default Settings for Policies

- 14.25 Restart Applications to Get an Accurate Policy Usage Count

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

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

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

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

- 14.30 Performance Improvements in Web Services Policy Pages

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

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

Part VI Oracle WebCenter Content

15 Oracle WebCenter Application Adapters

- 15.1 Configuration Issues and Workarounds

- 15.1.1 Populating the AXF_MA_PARAMETERS Table to Pass Extra Metadata Values (Managed Attachments)

- 15.2 Documentation Errata

- 15.2.1 Incorrect Default Document Type Specified

- 15.2.2 dPrivilege Parameter in AFGrants Table Incorrectly Identified as Optional

16 Oracle WebCenter Content Installation and Configuration

- 16.1 Rebranding of Oracle Enterprise Content Management Suite to Oracle WebCenter Content

- 16.2 Documentation Errata

- 16.2.1 Start Capture Managed Server Before Setting Application Roles

17 Oracle WebCenter Content: Imaging

- 17.1 General Issues

- 17.1.1 Imaging Session Time Out When Using OSSO Requires Browser Refresh

- 17.1.2 Mixed Translations On Page

- 17.1.3 Deleting More Than 100 Documents Can Cause Http 404 Errors

- 17.1.4 Time Zone Based on Time Zone of Imaging Server

- 17.1.5 Imaging Documents May Be Visible Natively Within WebCenter

- 17.1.6 Removing Full-Text Search Capabilities From Defined Applications

- 17.1.7 Application Field Limitations When Using Oracle Text Search

- 17.1.8 Records Missing from Imaging Searches

- 17.1.9 WebLogic Server Listening Address and AXF Driver Page URL Must Reference the Same Domain

- 17.1.10 Must Start NFS Locking Service When Input Agent Used with Linux Shares

- 17.1.11 DefaultSecurityGroup MBean Allows For Assigning Administrator Rights to Security Group at First Log In

- 17.1.12 Input Mapping Error When Input Definition File Includes Blank Line

- 17.1.13 Differing Behavior of Decimals When Ingested Into Number or Decimal Fields

- 17.1.14 Using Browser Forward, Back, and Refresh Navigation Not Recommended

- 17.1.15 Document Upload or Update Failure if Content Server English-US Locale Not Enabled

- 17.1.16 Document Move Failure if Content Server Not Started with English-US Locale

- 17.1.17 Clearing Java Temporary Files of Cached Files

- 17.1.18 Solution Editor Enabled Only On Imaging Systems Using an Oracle Database

- 17.1.19 Additional MBean Configuration Options

- 17.1.20 Viewer Cache Does Not Work After Upgrading or Patching

- 17.2 Browser Compatibility Issues

- 17.2.1 IE: Non-ASCII Characters Not Supported in Internet Explorer for ExecuteSearch

- 17.2.2 Firefox: Version and Download Dialog Boxes Appear Behind Viewer in Advanced Mode

- 17.2.3 Internet Explorer 9: Problem With Link to Install Java SE Runtime Environment Necessary for Viewer

- 17.3 Accessibility Issues

- 17.3.1 Button Activation Behavior Different Depending on Viewer Mode

- 17.3.2 Limitations of Sticky Note Contents

- 17.3.3 Skip to Content Link Added for Keyboard Navigation

- 17.3.4 Firefox: Skip to Applet Link Added for Keyboard Navigation in Advanced Viewer Mode

- 17.3.5 Internet Explorer 7: Focus Issue on Upload Document and Preferences Pages

- 17.3.6 Name of File Selected For Import Not Displayed in Screen Reader Mode

- 17.3.7 Issues Selecting From Calendar Using Keyboard

- 17.3.8 Focus Issue in Create Searches Wizard Using Keyboard

- 17.3.9 Annotations Not Recognized By JAWS

- 17.3.10 Date Selected From Calendar Lost Using Keyboard

- 17.3.11 Some Annotation Buttons Incorrectly Read by JAWS

- 17.3.12 Internet Explorer: Long Panels Not Visible In Screen Reader

- 17.4 Documentation Errata

18 Oracle WebCenter Capture

- 18.1 General Issues and Workarounds

- 18.1.1 Batch Processing Error Message Not Displayed in Client

- 18.1.2 Bi-Directional Display Issues Detected in Client

- 18.1.3 Certain Client Error Messages Display in Server Language Rather Than Browser Language

- 18.1.4 Capture Client Error Resulted After SSO Time-out

- 18.1.5 Rare Batch Commit Error Not Cleared After Subsequent Commit By Another Commit Profile

- 18.1.6 Document Conversion Processor Error Detected During PDF Conversion With No Monitor Configuration

- 18.1.7 Search Criteria Issue Detected When Granting Security Access to Workspaces or Client Profiles

- 18.1.8 Certain Import Processor Metric Table Values May Display Zero Values

- 18.1.9 Need to Specify the Server System Fonts Location For PDF Image Only Commit

- 18.2 Configuration Issues and Workarounds

- 18.3 Documentation Errata

19 Oracle Information Rights Management

- 19.1 General Issues and Workarounds

- 19.1.1 Data Truncation May Occur If One Large or Multiple Excel Files Are Open

- 19.1.2 Some Functionality is Disabled or Restricted in Adobe Reader X and Adobe Reader 9

- 19.1.3 Limitations of Support for Microsoft SharePoint in this Release

- 19.1.4 Lotus Notes Email Message May be Lost if Context Selection Dialog is Canceled

- 19.1.5 Save As is Blocked in Microsoft Office 2000/XP for Sealed Files if the Destination is a WebDAV Folder

- 19.1.6 No Prompt to Use Local Drafts Folder for Sealed Files in SharePoint 2010

- 19.1.7 Incorrect Initial Display of Oracle IRM Fields in Microsoft Excel Spreadsheets When Used With SharePoint

- 19.1.8 Behavior of Automatic Save and Automatic Recovery in Microsoft Office Applications and SharePoint

- 19.1.9 Support for Microsoft Windows 2000 Has Been Removed

- 19.1.10 Unreadable Error Message Text When Client and Server Locales are Different

- 19.1.11 Changes Lost if Tab Changed Before Applying the Apply Button

- 19.1.12 Some File Formats are Not Supported When Using the Microsoft Office 2007 Compatibility Pack with Microsoft Office 2003

- 19.1.13 Microsoft Word May Hang if a Sealed Email is Open During Manual Rights Check-In

- 19.1.14 Sealed Emails in Lotus Notes will Sometimes Show a Temporary File Name

- 19.1.15 No Support for Sealing Files of 2GB or Larger in Size in Oracle IRM Desktop

- 19.1.16 Inappropriate Authentication Options After Failed Login on Legacy Servers When Setting Up Search

- 19.1.17 Opening Legacy Sealed Documents in Microsoft Office 2007 May Fail on First Attempt

- 19.1.18 Log Out Link Inoperative When Using OAM 11g for SSO

- 19.1.19 Double-byte Languages Cannot be Used for Entering Data with Legacy Servers

- 19.1.20 Use of SPACE Key Instead of Return Key in Oracle IRM Server

- 19.1.21 Calendar Controls in Oracle IRM Server Not Accessible Via the Keyboard

- 19.2 Configuration Issues and Workarounds

- 19.2.1 New JPS Configuration Properties for User and Group Searches

- 19.2.2 Mandatory Patch Number 12369706 For Release 11.1.1.5.0 of Oracle IRM Server, To Fix Role Edit Bug

- 19.2.3 Installing the 64-Bit Version of Oracle IRM Desktop

- 19.2.4 Reboot Necessary to Obtain New Online Information Button

- 19.2.5 Deploying Oracle IRM Using Oracle Access Manager Version 10g

- 19.2.6 LDAP Reassociation Fails if User and Group Names are Identical

- 19.2.7 Upgrading Oracle IRM Desktop From Versions Earlier Than 5.5

- 19.2.8 Synchronizing Servers After an Upgrade of Oracle IRM Desktop

- 19.2.9 Reapplying Lost Settings After an Upgrade of Oracle IRM Desktop

- 19.2.10 Changing Oracle IRM Account When Authenticated Using Username and Password

- 19.2.11 Post-Installation Steps Required for Oracle IRM Installation Against Oracle RAC

- 19.2.12 Enabling the Oracle IRM Installation Help Page to Open in a Non-English Server Locale

- 19.3 Documentation Errata

20 Oracle WebCenter Content

- 20.1 General Issues and Workarounds

- 20.1.1 Site Studio Does Not Support Multibyte Characters in Site IDs, Directory Names, and Page Names

- 20.1.2 Site Studio Publisher Does Not Support Multibyte Characters

- 20.1.3 Oracle WebCenter Content Servers and IPv6 Support

- 20.1.4 Content Categorizer Trace Log Settings Discontinued

- 20.1.5 Extra Lines Displayed Viewing Contribution Folders in Internet Explorer 8

- 20.1.6 WebDAV Connection Fails After Logout or Restart

- 20.1.7 Detailed Oracle OpenOffice Configuration Settings

- 20.1.8 Clarification When Setting Classpath to OpenOffice Class Files

- 20.1.9 Inbound Refinery PDF Conversion May Differ Visually from the Original Content

- 20.1.10 Mismatching User and Server Locales Prevent Access to Oracle E-Business Suite and PeopleSoft Managed Attachment Pages in WebCenter Content

- 20.1.11 Connection Issues with Windows to WebDAV

- 20.1.12 Manual Addition of xdoruntime.ear Library for Records Management

- 20.1.13 Using HCSP Custom Elements with SSXA

- 20.1.14 Backing Up Site Studio Websites Using Chrome

- 20.1.15 DAM Video Storyboard Errors With Chrome and Safari

- 20.1.16 Issues Applying Table Styles When Using FireFox and FCK Editor

- 20.1.17 Content Information Server Is Not Supported for 11g

- 20.1.18 Window Size Using Trays with Firefox

- 20.1.19 VB6 Component Dependency for Kofax 9

- 20.1.20 Using URLs With SSP Include and Exclude Filters

- 20.1.21 Disabling the Folders_g Deprecation Alert

- 20.1.22 Accessing ZipRenditionStaticAccess Scheduled Job Information

- 20.1.23 Check-in and Search Forms Pop Up Error Messages when UCM is in EBR Mode

- 20.1.24 View Publishing Errors Are Observed in Logs When UCM is in EBR Mode

- 20.1.25 Optimization Errors with External OracleTextSearch

- 20.1.26 Propagating the cwallet.sso Changes to Deployment Manager

- 20.1.27 UCM in EBR Mode Fails to Start when Dynamic Converter Component is Enabled

- 20.1.28 Content Tracker Report Date Format Supported in Nine Languages

- 20.1.29 Inbound Refinery PDF Optimization Not Supported with Ghostscript 9.07

- 20.1.30 Thai Locale in Firefox Browser Displays Larger Asian Font

- 20.1.31 'Show on Top' Context Menu Option Does Not Display as Expected in WebCenter Content User Interface

- 20.1.32 Using Dropdown Menu on Chrome When Ask.com Toolbar Present

- 20.1.33 Using Tabular View in Screen Reader Mode in WebCenter Content User Interface

- 20.1.34 Framework Folders AutoSuggest Type-Ahead Feature Limitation

- 20.1.35 Site Studio ASP and JSP Sites Functionality in 11gR1

- 20.2 Configuration Issues and Workarounds

- 20.2.1 Minimum JDBC Driver Version Required for Oracle Text Search Component

- 20.2.2 Setting Security Privileges for Modifying Contribution Folders

- 20.2.3 Site Studio for External Applications (SSXA) Port Values for Oracle Content Server 10gR3

- 20.2.4 SSXA Required DC Version for Oracle Content Server 10gR3

- 20.2.5 Content Portlet Suite (SCPS) WebCenter as Producer Targeting Libraries

- 20.2.6 Logout URL for SSO Logout Integrating with Oracle Access Manager 11g

- 20.2.7 Using the Custom Truststore with the JPS Connection to ActiveDirectory

- 20.2.8 Setting the Connection Pool for an External LDAP ID Store on IBM WebSphere Application Servers

- 20.2.9 Electronic Signature Login and Time Limit

- 20.2.10 Configuring Temporary Directories

- 20.2.11 Setting Maximum Windows Per Session Parameter

- 20.2.12 AutoSuggestConfig Component Must Be Disabled in Native 11g Interface

- 20.2.13 Content Server Localization and Verbose Tracing

- 20.2.14 FrameworkFolders Patch for Release 11gR1 (11.1.1.8.0)

- 20.3 Documentation Errata

- 20.3.1 Content Portlet Suite (CPS) WSRP URLs for WebCenter as Producer

- 20.3.2 Update Component Configuration Information Missing in 11.1.1.8.0 Documentation Set

21 Oracle WebCenter Content: Records

- 21.1 General Issues and Workarounds

- 21.1.1 Role Report Output is Dependent on User Generating the Report

- 21.1.2 Items Returned When Using Screening

- 21.1.3 Oracle Text Search and Report Configuration Options

- 21.1.4 Upgrade from 10g Audit Trail Periods Missing

- 21.1.5 DB2 Databases and FOIA/PA Functionality

- 21.1.6 Sorting and Listing Retention Category Content

- 21.1.7 Using Firefox to Configure the Dashboard

- 21.1.8 Setting Security Group for Retention Items

- 21.1.9 Problem Viewing the Search Results

- 21.2 Configuration Issues and Workarounds

- 21.2.1 Import FOIA Archive Error Message

- 21.2.2 Restart Required: Performance Monitoring and Reports

- 21.2.3 Audit Trail Sorting Results and Database Fulltext Search

- 21.2.4 Prefix Size Limitation When Using Offsite Storage

- 21.2.5 Enabling Email Metadata Component

- 21.2.6 Relative Web Root Must Be Changed

- 21.2.7 Configuring 10g Adapters for Version 11g

- 21.2.8 Configuring RSS Reader for Dashboard

- 21.3 Documentation Errata

- 21.3.1 Menu Name Changes Not Reflected in Documentation

- 21.3.2 Physical Content Management Services Not Documented

- 21.3.3 Additional FTP Option for Offsite Storage

Part VII Oracle WebCenter Sites

22 Oracle WebCenter Sites

- 22.1 What's New in This Release

- 22.1.1 Support for Mobile-Optimized Websites

- 22.1.2 Updates to Content Targeting (Engage Component)

- 22.1.3 Marketing-Friendly URL Management (Vanity URLs)

- 22.1.4 New Integrations

- 22.1.5 AviSports Sample Site Updates

- 22.1.6 Platform Updates

- 22.2 Deprecated Functionality

- 22.3 Limitations

- 22.3.1 Asset Type Name Restrictions

- 22.3.2 API

- 22.3.3 Browser Support

- 22.3.4 BulkLoader and BulkApprover

- 22.3.5 CatalogManager

- 22.3.6 CatalogMover

- 22.3.7 Collection

- 22.3.8 Content Tags

- 22.3.9 Contributor Interface

- 22.3.10 Developer Tools

- 22.3.11 Database

- 22.3.12 Installing WebCenter Sites

- 22.3.13 Localization

- 22.3.14 OAM Integration

- 22.3.15 Page Cache: inCache

- 22.3.16 Publishing

- 22.3.17 REST API

- 22.3.18 Satellite Server

- 22.3.19 Search

- 22.3.20 Sites Explorer

- 22.3.21 Site Capture

- 22.3.22 Site Management

- 22.3.23 Sites DocLink (Deprecated)

- 22.3.24 Sites Desktop (Deprecated)

- 22.3.25 Tags

- 22.3.26 Template, Site Entry, and CS-Element

- 22.3.27 Vanity URL

- 22.3.28 WebCenter Content Integration

- 22.4 General Issues and Workarounds

- 22.4.1 API

- 22.4.2 Admin Interface

- 22.4.3 Analytics Integration

- 22.4.4 Approval

- 22.4.5 AssetCache

- 22.4.6 Browser Support

- 22.4.7 Caching: inCache

- 22.4.8 Caching: Satellite Server

- 22.4.9 CKEditor

- 22.4.10 Cluster

- 22.4.11 Content Query

- 22.4.12 Contributor Interface

- 22.4.13 Developer Tools

- 22.4.14 Engage

- 22.4.15 Flex Assets

- 22.4.16 Installation / Upgrade

- 22.4.17 Mobility

- 22.4.18 Performance

- 22.4.19 Proxy Assets

- 22.4.20 Publish Console

- 22.4.21 Publishing

- 22.4.22 REST API

- 22.4.23 Revision Tracking

- 22.4.24 Satellite Server

- 22.4.25 Site Capture

- 22.4.26 Site Launcher

- 22.4.27 Site Plan

- 22.4.28 Sites Desktop (Deprecated)

- 22.4.29 Sites DocLink (Deprecated)

- 22.4.30 Sites Explorer

- 22.4.31 Start Menu

- 22.4.32 System Tools

- 22.4.33 Tags

- 22.4.34 WebLogic Server

- 22.4.35 WEM Admin

- 22.4.36 WEM Framework

- 22.4.37 Workflow

- 22.4.38 UI Customization

- 22.4.39 Upgrade

- 22.4.40 XMLPost

23 Oracle WebCenter Sites: Community-Gadgets

- 23.1 Community-Gadgets Enhancements

- 23.2 Limitations

- 23.2.1 Browser Support

- 23.2.2 General Limitations

- 23.2.3 Community Application

- 23.2.4 Gadgets Application

- 23.2.5 Installing Community-Gadgets

- 23.2.6 Oracle Access Manager Integration

- 23.3 General Issues and Workarounds

- 23.3.1 Browser Support

- 23.3.2 Community Application

- 23.3.2.1 General Issues and Workarounds

- 23.3.2.2 Comments

- 23.3.2.3 Reviews

- 23.3.3 Gadgets Application

- 23.3.4 Janrain Integration

- 23.3.5 Localization

- 23.3.6 OAM Integration

- 23.3.7 Performance

- 23.4 Upgrading the Community Blogs Module

Part VIII Oracle SOA Suite and Business Process Management Suite

24 Oracle SOA Suite, Oracle BPM Suite, and Common Functionality

Part IX Communication Services

25 Oracle User Messaging Service

- 25.1 General Issues and Workarounds

- 25.1.1 UMS Schema Purge Script Now Available

- 25.1.2 Permission Grants for Upgraded Domains

- 25.1.3 XML File Handle Left Open after Upload Fails

- 25.1.4 Messages Metrics Rendered as Unavailable in the Performance Page for User Messaging Server

- 25.1.5 User Messaging Service URLs Unavailable After Restart

- 25.1.6 User Preferences User Interface Renders Improperly

- 25.1.7 UMS Cluster Failover May Lose Messages

- 25.2 Configuration Issues and Workarounds

- 25.2.1 Enable Extension Driver after Upgrade

- 25.2.2 Preseeded Channel for Worklist and Pop-up Drivers Cannot be Removed

- 25.2.3 Worklist Driver Configuration

- 25.2.4 Migrate Custom Business Terms After PS3 Patch

- 25.2.5 Use Correct SSL Trust Store When Configuring Drivers

- 25.2.6 User Messaging Service Driver Configuration Changes Not Immediately Effective

- 25.2.7 Email Notifications Sent Even if You Do Not Change Default Parameters in driverconfig.xml

26 Oracle WebLogic Communication Services

- 26.1 General Issues and Workarounds

- 26.1.1 Active SIP Session and APP Session Count Show as -1 in Clustered Configuration

- 26.1.2 Oracle WebLogic Server Pack/Unpack Tool Does Not Function in OWLCS

- 26.1.3 Oracle WebLogic Server Cloning Tool Does Not Function in OWLCS

- 26.1.4 Messages Metrics Rendered as Unavailable in the Performance Page for User Messaging Server

- 26.2 Configuration Issues and Workarounds

- 26.2.1 Launch_sash Option Error

- 26.2.2 Same User Who Installed WLS/WLSS Product Must Perform Uninstall

- 26.2.3 Uppercase Usernames Cause Reregistration and Presence Subscription Failures

- 26.2.4 Running the uninstall.sh Script in Text Mode Does Not Uninstall the Product

- 26.2.5 SIP Monitor in F5 Networks BigIP Does Not Work in UDP Mode

- 26.2.6 SIP Container Does Not Bind to IPV6 Interfaces for Listening on Windows

- 26.2.7 JAWS Unable to Read Some Install Screens

- 26.2.8 Configure VoiceXML Driver Receive URLs Correctly

- 26.3 Documentation Errata

- 26.3.1 Create a Basic SIP Domain

- 26.3.2 Create a Custom AUID with OCP (Presence)

- 26.3.3 Cannot Create a SIP Server Domain Using Default WebLogic Platform Components

- 26.3.4 Broken Documentation Links in Some (SIP Server) Translated Files

- 26.3.5 Missing (SIP Server) Online Help Regarding Security Providers

Part X Oracle Identity Management

27 Oracle Adaptive Access Manager

- 27.1 General Issues and Workarounds

- 27.1.1 OAAM Sessions is Not Recorded When IP Address from Header is an Invalid IP Address

- 27.1.2 Checkpoint Boxes in Session are Displayed with Same Timestamp

- 27.1.3 Autogenerated Agent Cases Display User Specific Data

- 27.2 Policy Management Issues and Workarounds

- 27.2.1 Rule Condition Check Current Transaction Using the Filter Conditions Cannot Be Configured for Corresponding Attributes of Two Entity Instances

- 27.2.2 Rule Condition to Check Consecutive Transactions Fails Entity Check

- 27.2.3 Exclude IP List Parameter for User and Device Velocity Rule Conditions

- 27.2.4 OAAM Offline Displays Only the Last Rule Executed Overwriting Previous

- 27.2.5 User: Check First Login Time Rule Condition Always Triggers

- 27.3 Transaction Issues and Workarounds

- 27.3.1 OAAM Displays Only the Last Rule Executed and Overwrites Previous Rules

- 27.3.2 OAAM Shows Only 25 Transactions in Session Details

- 27.3.3 Alerts Are Not Displayed Beyond 25 Transactions

- 27.3.4 OAAM Transaction Cannot Be Created with Numeric Parameter of More than 16 Digits

- 27.3.5 Transactions in Session Details Duplicated After 25

- 27.3.6 Transaction ID Association with Alert Does Not Work

- 27.3.7 OAAM Console Does Not Display Transaction Status

- 27.3.8 Transaction Mapping Substring Error for First Character Value

- 27.3.9 Update Time for Entity Is Updated Without Any Change in Entity Data

- 27.4 Knowledge-Based Authentication Issues and Workarounds

- 27.4.1 Registration Logic Page Does Not Display KBA Logic

- 27.4.2 Answer Logic Abbreviation Resource Was Not Used

- 27.4.3 Update KBA for FFIEC Compliance

- 27.4.4 Closing Browser on Image and Security Phrase Registration Page

- 27.4.5 OAAM Change Password Does Not Display Any Validation for Password Fields

- 27.4.6 ORA-01722 Occurs During KBA Update

- 27.4.7 Registered Questions Are Deleted and Subsequent Challenge Does Not Succeed

- 27.5 Integration Issues and Workarounds

- 27.5.1 setupOAMTapIntegration.sh Does Not Set oaam.uio.oam.secondary.host.port

- 27.5.2 OAAM Does Not Support Juniper Single Sign-On for Authentication and Forgot Password Flow

- 27.5.3 Step Up Authentication Changes

- 27.5.4 TAP: Incorrect Error Message

- 27.5.5 OAAM 11g SOAP Timeout Exception Handling

- 27.5.6 OAAM Should Call UserManager.Unlock() in the Forgot Password Workflow

- 27.6 Reporting Issues and Workarounds

- 27.6.1 Alert Message Link in Session Details Page Does Not Open the Alert Details

- 27.6.2 OAAM Rules Breakdown Report Does Not Provide Correct Information

- 27.7 Configuration Issues and Workarounds

- 27.7.1 Database Archive and Purge Scripts Missing from Installation

- 27.7.2 Juniper Login Fails Due to Incorrect CN Value and No UID Attribute in SAML Response

- 27.8 Customer Care Issues and Workarounds

- 27.8.1 Investigator Role Overrides CSR Role When Both Roles Are Given to a User

- 27.8.2 Scroll Bars Missing from Some Case Management Screens

- 27.8.3 Case Search and Case Details Do Not Display Case Disposition

- 27.8.4 Wrong User Attributed for Last Notes Added If Two Users Concurrently Update Case Notes

- 27.8.5 Manually Created OAAM Agent Cases Cannot Be Searched by Username or User ID

- 27.8.6 OAAM Allows Case Ownership Change and Add Notes Actions to Closed Case

- 27.8.7 Create Agent Case Configurable Action Displays Wrong Name for Action

- 27.8.8 KBA and OTP Failure Counter Reset and Unlock

- 27.9 Performance Issues and Workarounds

- 27.9.1 Out of Memory Error Occurs Scrolling through Sessions Search in OAAM Admin

- 27.10 Geolocation Data Loader Issues and Workarounds

- 27.10.1 Upload of Geolocation Data Causes Unique Constraint Violation

- 27.10.2 IP Location Data Loader Fails If There is a Blank Line in the File

- 27.11 Multi-Language Support Issues and Workarounds

- 27.11.1 Session or Cases Page Cannot Open if Browser Language is Italian

- 27.11.2 Session Search and Case Search By Date Range Does Not Work in OAAM Admin Console When Browser Language is Brazilian Portuguese or Spanish

28 Oracle Access Manager

- 28.1 Patch Requirements

- 28.1.1 Plain Text Credentials Exposed in Diagnostic Logs when Creating an Identity Store

- 28.2 General Issues and Workarounds

- 28.2.1 Resource Protected By Federation Shown Without Authentication

- 28.2.2 Issues Registering the OSSO Plugin

- 28.2.3 Modify Authentication Scheme When Upgrading OAM 11.1.1.5 to OAM 11.1.1.7

- 28.2.4 RemoteRegistrationServerException Seen After PasteConfig IDM (T2P)

- 28.2.5 System Error Page Displayed After Login

- 28.2.6 T2P Paste Config Operation Fails With Exception

- 28.2.7 Creating Policies For Webgate 11g

- 28.2.8 Sending Valid Cookie For Embedded BI Content

- 28.2.9 Incorrect SSO Agent Date/Time Shown to User

- 28.2.10 Initial Messages After Webgate Registration Are Not Shown in the User's Locale

- 28.2.11 Single-Click to Open Child Node is Not Supported in the Navigation Tree

- 28.2.12 User Credential for Registration Tool Does Not Support Non-ASCII Characters on Native Server Locale

- 28.2.13 Turkish and Greek Character Issues on Oracle Access Manager Authentication Page

- 28.2.14 Oracle Access Manager Authentication Does Not Support Non-ASCII Passwords on Locales Other than UTF8

- 28.2.15 Error Message of Create Agent Shows as Server Locale

- 28.2.16 Referrals in LDAP Searches

- 28.2.17 Non-ASCII Resources Require OHS To Restart To Make Protection Take Effect

- 28.2.18 Non-ASCII Characters on Success/Failure URL Results in Garbled Redirect URL

- 28.2.19 Resource with Non-ASCII Characters Cannot Be Protected by an OSSO Agent

- 28.2.20 Error in Administration Server Log from Console Logins

- 28.2.21 Application Domain Subtree in the Navigation Tree Is Not Rendered and Does Not Respond to User Actions

- 28.2.22 editWebgateAgent Command Does Not Give An Error If Invalid Value is Entered

- 28.2.23 WLST Command displayWebgate11gAgent In Offline Mode Displays the Webgate Agent Entry Twice

- 28.2.24 Message Logged at Error Level Instead of at INFO When Servers in Cluster Start

- 28.2.25 Help Is Not Available for WLST Command registeroifdappartner

- 28.2.26 User Must Click Continue to Advance in Authentication Flow

- 28.2.27 OCSP-Related Fields are Not Mandatory

- 28.2.28 Database Node is Absent in the Console

- 28.2.29 Online Help Provided Might Not Be Up To Date

- 28.2.30 Oracle Access Manager Audit Report AUTHENTICATIONFROMIPBYUSER Throws a FROM Keyword Not Found Where Expected Error

- 28.2.31 Disabled: Custom Resource Types Cannot be Created

- 28.2.32 Use of a Non-ASCII Name for a Webgate Might Impact SSO Redirection Flows

- 28.2.33 Authentication Module Lists Non-Primary Identity Stores

- 28.2.34 Unable to Stop and Start OAM Server Through Identity and Access Node in Fusion Middleware Control

- 28.2.35 AdminServer Won't Start if the Wrong Java Path Given with WebLogic Server Installation

- 28.2.36 Changing UserIdentityStore1 Type Can Lock Out Administrators

- 28.2.37 Page Layouts and Locales

- 28.2.38 Some Pages Are Not Correctly Localized

- 28.2.39 Non-ASCII Query String Issues with Internet Explorer v 7, 8, 9

- 28.2.40 Oracle Virtual Directory with SSL Enabled

- 28.2.41 Query String Not Properly Encoded

- 28.3 Configuration Issues and Workarounds

- 28.3.1 For mod-osso Value for RedirectMethod Should be "POST"

- 28.3.2 User Wrongly Directed to the Self-User Login after Logging Out of the Oracle Identity Manager Administration Console

- 28.3.3 11g Webgate Fails to Install with Compact Configuration

- 28.3.4 Auditing Does Not Capture the Information Related to Authentication Failures if a Resource is Protected Using Basic Authentication Scheme

- 28.3.5 Unable to Access Partner Information on the Production Environment

- 28.3.6 Incompatible Msvcirt.dll Files

- 28.3.7 IPv6 Support

- 28.3.8 What to Avoid or Note in Oracle Access Manager Configuration

- 28.3.8.1 Unsupported Operations for WLST Scripts

- 28.3.8.2 Unsupported Operations for Oracle Access Manager Console and WLST

- 28.3.9 Install Guides Do Not Include Centralized Logout Configuration Steps

- 28.3.10 NULL Pointer Exception Shown in Administration Server Console During Upgrade

- 28.3.11 Using Access SDK Version 10.1.4.3.0 with Oracle Access Manager 11g Servers

- 28.3.12 Finding and Deleting Sessions Using the Console

- 28.3.13 Non-ASCII Users with Resource Protected by Kerberos Authentication Scheme

- 28.4 Oracle Security Token Service Issues and Workarounds

- 28.4.1 No Warnings Given If Required Details are Omitted

- 28.4.2 New Requester Pages, Internet Explorer v7, and Japanese Locale

- 28.4.3 Delete Button Not Disabled When Tables Have No Rows

- 28.4.4 Copying an Issuance Template Does Not Copy All Child Elements

- 28.4.5 Apply and Revert Buttons are Enabled

- 28.4.6 Only Generic Fault Errors Written to Oracle WSM Agent Logs

- 28.4.7 Server and Client Key Tab Files Must be the Same Version

- 28.4.8 Default Partner Profile Required for WS-Security

- 28.4.9 SAML Token Issued When NameID is Not Found

- 28.5 Integration and Inter-operability Issues and Workarounds

- 28.5.1 WNA Authentication Does Not Function on Windows 2008

- 28.5.2 JVM Plug-in Ignores Cookies Marked 'httponly'

- 28.6 Oracle Access Manager with Impersonation Workarounds

- 28.6.1 Impersonation Can Fail on Internet Explorer v 7, 8, 9

- 28.6.2 With Oracle Access Manager 11g ORA_FUSION_PREFS Cookie Domain is Three Dots

- 28.7 Documentation Errata

- 28.7.1 Oracle Fusion Middleware Administrator's Guide for Oracle Access Manager with Oracle Security Token Service

- 28.7.2 Oracle Fusion Middleware Developer's Guide for Oracle Access Manager and Oracle Security Token Service

- 28.7.3 Oracle Fusion Middleware Integration Guide for Oracle Access Manager

- 28.7.3.1 Updates to Prerequisites for OAM-OIM Integration

- 28.7.3.2 Properties for configOIM Command

- 28.7.3.3 Updated Example for Integrating OIF/SP

29 Oracle Entitlements Server

- 29.1 General Issues and Workarounds

- 29.1.1 Using Backslash on Oracle Internet Directory Policy Store

- 29.1.2 Performance Tuning the Oracle Database Policy Store

- 29.1.3 Action Bar Disappears When Using Internet Explorer 7

- 29.1.4 Re-created Application May Not Be Distributed in Controlled Mode

- 29.1.5 Enterprise Manager Doesn't Pick Up Newly Added Audit Events

- 29.1.6 Attributes Passed to Authorization Request Are Treated as Case Sensitive

- 29.1.7 Audit Schema Definitions are Incomplete

- 29.1.8 Java Security Module on IPv6 Client Not Supported on Windows

- 29.1.9 Validating Attribute Names in Custom Functions

- 29.2 Configuration Issues and Workarounds

- 29.3 Documentation Errata

30 Oracle Identity Federation

- 30.1 General Issues and Workarounds

- 30.1.1 Database Table for Authentication Engine must be in Base64 Format

- 30.1.2 Considerations for Oracle Identity Federation HA in SSL mode

- 30.1.3 Database Column Too Short error for IDPPROVIDEDNAMEIDVALUE

- 30.2 Configuration Issues and Workarounds

- 30.2.1 WLST Environment Setup when SOA and OIF are in Same Domain

- 30.2.2 Oracle Virtual Directory Requires LSA Adapter

- 30.2.3 Settings for Remote WS-Fed SP Must be Changed Dynamically

- 30.2.4 Required Property when Creating a WS-Fed Trusted Service Provider

- 30.2.5 Federated Identities Table not Refreshed After Record Deletion

- 30.2.6 Default Authentication Scheme is not Saved

- 30.2.7 Configuring 10g to Work with 11g Oracle Identity Federation using Artifact Profile

- 30.2.8 Regenerating OAM 11g Key Requires Oracle Identity Federation Upgrade Script

- 30.3 Documentation Errata

- 30.3.1 Incorrect Command Cited for BAE Configuration Procedure

- 30.3.2 SP Post-Processing Plug-in Properties for OAM 11g

- 30.3.3 Short Hostname Redirect Using mod_rewrite Configuration

31 Oracle Identity Manager

- 31.1 Patch Requirements

- 31.1.1 Obtaining Patches From My Oracle Support (Formerly OracleMetaLink)

- 31.1.2 Patch Requirements for Oracle Database 11g (11.1.0.7)

- 31.1.3 Patch Requirements for Oracle Database 11g (11.2.0.2.0)

- 31.1.4 Patch Requirements for Segregation of Duties (SoD)

- 31.1.5 Patch Upgrade Requirement

- 31.2 General Issues and Workarounds

- 31.2.1 Do Not Use Platform Archival Utility

- 31.2.2 SPML-DSML Service is Unsupported

- 31.2.3 Resource Object Names Longer than 100 Characters Cause Import Failure

- 31.2.4 Status of Users Created Through the Create and Modify User APIs

- 31.2.5 Status of Locked Users in Oracle Access Manager Integrations

- 31.2.6 Generating an Audit Snapshot after Bulk-Loading Users or Accounts

- 31.2.7 Browser Timezone Not Displayed

- 31.2.8 Date Format Change in the SoD Timestamp Field Not Supported

- 31.2.9 Bulk Loading CSV Files with UTF-8 BOM Encoding Not Supported

- 31.2.10 Date Type Attributes are Not Supported for the Default Scheduler Job, "Job History Archival"

- 31.2.11 Low File Limits Prevent Adapters from Compiling

- 31.2.12 Reconciliation Engine Requires Matching Rules

- 31.2.13 SPML Requests Do Not Report When Any Date is Specified in Wrong Format

- 31.2.14 Logs Populated with SoD Exceptions When the SoD Message Fails and Gets Stuck in the Queue

- 31.2.15 A Backslash (\) Cannot Be Used in a weblogic.properties File

- 31.2.16 Underscore Character Cannot Be Used When Searching for Resources

- 31.2.17 Assign to Administrator Action Rule is Not Supported by Reconciliation

- 31.2.18 Some Buttons on Attestation Screens Do Not Work in Mozilla Firefox

- 31.2.19 The maxloginattempts System Property Causes Autologin to Fail When User Tries to Unlock

- 31.2.20 "<User not found>" Error Message Appears in AdminServer Console While Setting-Up an Oracle Identity Manager-Oracle Access Manager Integration

- 31.2.21 Do Not Use Single Quote Character in Reconciliation Matching Rule

- 31.2.22 Do Not Use Special Characters When Reconciling Roles from LDAP

- 31.2.23 SoD Check During Request Provisioning Fails While Using SAML Token Client Policy When Default SoD Composite is Used

- 31.2.24 SoD Check Fails While Using Client-Side Policy in Callback Invocation During Request Provisioning

- 31.2.25 Error May Appear During Provisioning when Generic Technology Connector Framework Uses SPML

- 31.2.26 Cannot Click Buttons in TransUI When Using Mozilla Firefox

- 31.2.27 LDAP Handler May Cause Invalid Exception While Creating, Deleting, or Modifying a Role

- 31.2.28 Cannot Reset User Password Comprised of Non-ASCII Characters

- 31.2.29 Benign Exception and Error Message May Appear While Patching Authorization Policies

- 31.2.30 The DateTime Pick in the Trans UI Does Not Work Correctly in the Thai Locale

- 31.2.31 User Without Access Policy Administrators Role Cannot View Data in Access Policy Reports

- 31.2.32 Archival Utility Throws an Error for Empty Date

- 31.2.33 TransUI Closes with Direct Provisioning of a Resource

- 31.2.34 Scheduler Throws "ParameterValueTypeNotSupportedException" Instead of "RequiredParameterNotSetException"

- 31.2.35 All New User Attributes Are Not Supported for Attestation in Oracle Identity Manager 11g

- 31.2.36 LDAP GUID Mapping to Any Field of Trusted Resource Not Supported

- 31.2.37 User Details for Design Console Access Field Must Be Mapped to Correct Values When Reading Modify Request Results

- 31.2.38 Cannot Create a User Containing Asterisks if a Similar User Exists

- 31.2.39 Blank Status Column Displayed for Past Proxies

- 31.2.40 Mapping the Password Field in a Reconciliation Profile Prevents Users from Being Created

- 31.2.41 UID Displayed as User Login in User Search Results

- 31.2.42 Roles/Organizations Browse Trees Disappear

- 31.2.43 Entitlement Selection Is Not Optional for Data Gathering

- 31.2.44 Oracle Identity Manager Server Throws Generic Exception While Deploying a Connector

- 31.2.45 Create User API Allows Any Value for the "Users.Password Never Expires", "Users.Password Cannot Change", and "Users.Password Must Change" Fields

- 31.2.46 Incorrect Label in JGraph Screen for the GTC

- 31.2.47 Running the Workflow Registration Utility Generates an Error

- 31.2.48 Native Performance Pack is Not Enabled On Solaris 64-bit JVM Install

- 31.2.49 Error in the Create Generic Technology Connector Wizard

- 31.2.50 DSML Profile for the SPML Web Service is Not Deployed With Oracle Identity Manager

- 31.2.51 New Human Tasks Must Be Copied in SOA Composites

- 31.2.52 Modify Provisioned Resource Request Does Not Support Service Account Flag

- 31.2.53 Erroneous "Query by Example" Icon in Identity Administration Console

- 31.2.54 The XL.ForcePasswordChangeAtFirstLogin System Property Is No Longer Used

- 31.2.55 The tcExportOperationsIntf.findObjects(type,name) API Does Not Accept the Asterisk (*) Wilcard Character in Both Parameters

- 31.2.56 Disabled Links on the Access Policy Summary Page Opened in Mozilla FireFox

- 31.2.57 Benign Error is Generated on Editing the IT Resource Form in Advanced Administration

- 31.2.58 User Account is Not Locked in iPlanet Directory Server After it is Locked in Oracle Identity Manager

- 31.2.59 Oracle Identity Manager Does Not Support Autologin With JavaAgent

- 31.2.60 Benign Error Logged on Opening Access Policies, Resources, or Attestation Processes

- 31.2.61 User Locked in Oracle Identity Manager But Not in LDAP

- 31.2.62 Reconciliation Profile Must Not Be Regenerated Via Design Console for Xellerate Organization Resource Object

- 31.2.63 Benign Error Logged on Clicking Administration After Upgrade

- 31.2.64 Provisioning Fails Through Access Policy for Provisioned User

- 31.2.65 Benign Warning Messages Displayed During Oracle Identity Manager Managed Server Startup

- 31.2.66 Benign Message Displayed When Running the Deployment Manager

- 31.2.67 Deployment Manager Export Fails When Started Using Microsoft Internet Explorer 7 With JRE Plugin 1.6_23

- 31.2.68 User Creation Fails in Microsoft Active Directory When Value of Country Attribute Exceeds Two Characters

- 31.2.69 Deployment Manager Import Fails if Scheduled Job Entries Are Present Prior To Scheduled Task Entries in the XML File

- 31.2.70 Permission on Target User Required to Revoke Resource

- 31.2.71 Reconciliation Event Fails for Trusted Source Reconciliation Because of Missing Reconciliation Rule in Upgraded Version of Oracle Identity Manager

- 31.2.72 XML Validation Error on Oracle Identity Manager Managed Server Startup

- 31.2.73 Cannot View or Edit Adapter Mapping in the Data Object Manager Form of the Design Console

- 31.2.74 Role Memberships for Assign or Revoke Operations Not Updated on Enabling or Disabling Referential Integrity Plug-in

- 31.2.75 Deployment Manager Import Fails if Data Level for Rules is Set to 1

- 31.2.76 Reconciliation Data Displays Attributes That Are Not Modified

- 31.2.77 Benign Errors Displayed on Starting the Scheduler Service When There are Scheduled Jobs to be Recovered

- 31.2.78 Trusted Source GTC Reconciliation Mapping Cannot Display Complete Attribute Names

- 31.2.79 Benign Error Logged for Database Connectivity Test

- 31.2.80 MDS Validation Error When Importing GTC Provider Through the Deployment Manager

- 31.2.81 Encrypted User-Defined Field (UDF) Cannot be Stored with Size of 4000 Characters or More

- 31.2.82 Request Approval Fails With Callback Service Failure

- 31.2.83 Localized Display Name is Not Reconciled Via User/Role Incremental Reconciliation with iPlanet Directory Server

- 31.2.84 LDAP Role Hierarchy and Role Membership Reconciliation With Non-ASCII Characters Does Not Reconcile Changes in Oracle Identity Manager

- 31.2.85 Import of Objects Fails When All Objects Are Selected for Export

- 31.2.86 Benign Audit Errors Logged After Upgrade

- 31.2.87 Connector Upgrade Fails if Existing Data is Bigger in Size Than New Column Length

- 31.2.88 Connector Artifacts Count Increases in the Deployment Manager When File is Not Imported

- 31.2.89 Uploading JAR Files By Using the Upload JAR Utility Fails

- 31.2.90 Oracle Identity Manager Data and MT Upgrade Fails Because Change of Database User Password

- 31.2.91 Reverting Unsaved UDFs Are Not Supported in the Administration Details Page for Roles and Organizations

- 31.2.92 Resources Provisioned to User Without Checking Changes in User Status After Request is Submitted

- 31.2.93 Config.sh Command Fails When JRockit is Installed With Data Samples and Source

- 31.2.94 Unexpected Memory Usage in Oracle Identity Manager 11g Release 1(11.1.1)

- 31.2.95 Reports Link No Longer Exists in the Administrative and User Console

- 31.2.96 Not Allowing to Delete a Role Whose Assigned User Members are Deleted

- 31.2.97 Roles and Organizations Do Not Support String UDFs of Password Type

- 31.2.98 Manage Localizations Dialog Box Does Not Open After Modifying Roles

- 31.2.99 Not Allowing to Create User With Language-Specific Display Name Values

- 31.2.100 SoD Check Results Not Displayed for Requests Created by Users for the PeopleSoft Resource

- 31.2.101 The XL.UnlockAfter System Property and the Automatically Unlock User Scheduled Job Do Not Take Effect

- 31.2.102 Resetting Password on Account Lockout Does Not Unlock User

- 31.2.103 Incremental and Full Reconciliation Jobs Cannot Be Run Together

- 31.2.104 Incorrect Content in the ScheduleTask Jars Loaded and Third Party Jars Tables in the MT Upgrade Report

- 31.2.105 Scroll Bar Not Available on the Select Connector Objects to Be Upgraded Page of the Connector Management - Upgrading Wizard

- 31.2.106 Adapter Import Might Display Adapter Logic if Compilation Fails Because of Incorrect Data

- 31.2.107 XIMDD Tests Fail in Oracle Identity Manager

- 31.2.108 Error While Installing Oracle Identity Manager

- 31.3 Configuration Issues and Workarounds

- 31.3.1 Configuring UDFs to be Searchable for Microsoft Active Directory Connectors

- 31.3.2 Creating or Modifying Role Names When LDAP Synchronization is Enabled

- 31.3.3 ADF Issue Causes Oracle Identity Manager to Fail on the Sun JDK

- 31.3.4 Nexaweb Applet Does Not Load In an Oracle Identity Manager and Oracle Access Manager Integrated Environment

- 31.3.5 Packing a Domain With managed=false Option

- 31.3.6 Option Not Available to Specify if Design Console is SSL-Enabled

- 31.3.7 Nexaweb Applet Does Not Load in JDK 1.6.0_20

- 31.3.8 Oracle Identity Manager and Design Console Must be Installed in Different Directory Paths

- 31.3.9 Error on Adding Organization to User in Windows Explorer 8

- 31.4 Multi-Language Support Issues and Limitations

- 31.4.1 Multi-language Valued Attributes in SPML and Oracle Identity Manager Do Not Match

- 31.4.2 Login Names with Some Special Characters May Fail to Register

- 31.4.3 The Create Role, Modify Role, and Delete Role Request Templates are Not Available for Selection in the Request Templates List

- 31.4.4 Parameter Names and Values for Scheduled Jobs are Not Translated

- 31.4.5 Bidirectional Issues for Legacy User Interface

- 31.4.6 Localization of Role Names, Role Categories, and Role Descriptions Not Supported

- 31.4.7 Localization of Task Names in Provisioning Task Table Not Supported

- 31.4.8 Localization of Search Results of Scheduled Tasks Not Supported

- 31.4.9 Searching for User Login Names Containing Certain Turkish Characters Causes an Error

- 31.4.10 Localization of Notification Template List Values for Available Data Not Supported

- 31.4.11 Searching for Entity Names Containing German "ß" (Beta) Character Fails in Some Features

- 31.4.12 Special Asterisk (*) Character Not Supported

- 31.4.13 Translated Error Messages Are Not Displayed in UI

- 31.4.14 Reconciliation Table Data Strings are Hard-coded on Reconciliation Event Detail Page

- 31.4.15 Translated Password Policy Strings May Exceed the Limit in the Background Pane

- 31.4.16 Date Format Validation Error in Bi-Directional Languages

- 31.4.17 Mistranslation on the Create Job page

- 31.4.18 E-mail Notification for Password Expiration Cannot Be Created With Arabic Language Setting

- 31.4.19 Translated Justification is Not Displayed in Access Policy-Based Resource Provisioning Request Detail

- 31.4.20 Additional Single Quotes Displayed in GTC Reconciliation Mapping Page for French UI

- 31.4.21 Not Allowing to Enter Design Console Password When Server Locale is Set to Simple Chinese, Traditional Chinese, Japanese, or Korean

- 31.4.22 Bidirectional Text Not Supported in Nexaweb Pages

- 31.4.23 Do Not Modify Oracle Identity Manager Predefined System Properties in Non-English Locale

- 31.4.24 Error Generated When Translated String for System Property Name Exceeds Maximum Allowed Length in PTY_NAME Column

- 31.4.25 Password Notification is Not Sent if User Login Contains Special Characters

- 31.4.26 Reset Password Fails if User Login Contains Lowercase Special Characters

- 31.4.27 Email Notification Not Send Per Preferred Locale

- 31.4.28 Help Contents Displayed in English on Non-English Browsers

- 31.5 Documentation Errata

32 Oracle Identity Navigator

- 32.1 General Issues and Workarounds

- 32.1.1 Avoid Selecting Reset Page in Dashboard Edit Mode

- 32.1.2 How to Navigate Product Registration Using the Keyboard

- 32.1.3 How to Navigate Product Discovery When Using the Keyboard

- 32.1.4 Color Contrast is Inadequate for Some Labels in Edit Mode

- 32.1.5 No Help Topic in Dashboard Edit Mode

- 32.1.6 Customization Problem in Internet Explorer 7

- 32.1.7 Discovery Problem in Internet Explorer 7

- 32.1.8 How to Navigate BI Publisher Configuration When Using the Keyboard

- 32.1.9 User Missing From Common Admin Role Search Results

- 32.1.10 Unable to View Users After Log in Or Log In Fails In Oracle Identity Manager Environment

- 32.1.11 Horizontal Scroll-bar Missing in Discovery Wizard

- 32.2 Configuration Issues and Workarounds

- 32.2.1 No Oracle Icon is Visible in HTML Reports

- 32.2.2 Problems with Administration Screen When Using JAWS Screen Reader

- 32.2.3 SSO-Protected Consoles Must Be Configured by Name and Domain

- 32.3 Documentation Errata

- 32.3.1 IPv4/IPv6 Translation Issues

33 Oracle Internet Directory

- 33.1 General Issues and Workarounds

- 33.1.1 Cloned Oracle Internet Directory Instance Fails or Runs Slowly

- 33.1.2 Oracle Internet Directory Fails to Start on Solaris SPARC System Using ISM

- 33.1.3 Custom Audit Policy Settings Fail When Set Through Enterprise Manager

- 33.1.4 Deleting Mandatory attributeTypes Referenced by objectClass is Successful

- 33.1.5 Oracle Unified Directory 11.1.2.0 orclguid Attribute is Not Mapped for Server Chaining

- 33.1.6 ODSM is Not Displaying Online Help Correctly in Internet Explorer 11

- 33.1.7 ODSM Browser Window Becomes Unusable

- 33.1.8 In ldapdelete Command -V Should Be The Last Parameter

- 33.1.9 Upgrading from 10.1.2.0.2 Infrastructure to Application Server 11g Infrastructure

- 33.1.10 Bulkmodify Might Generate Errors

- 33.1.11 Turkish Dotted I Character is Not Handled Correctly

- 33.1.12 OIDCMPREC Might Modify Operational Attributes

- 33.1.13 OIDREALM Does Not Support Realm Removal

- 33.1.14 Apply Patch to Oracle Database 11.2.0.1.0 to Fix Purge Job Problem

- 33.1.15 SQL of OPSS ldapsearch Might Take High %CPU

- 33.1.16 If you Start the Replication Server by Using the Command Line, Stop it Using the Command Line

- 33.1.17 ODSM Problems in Internet Explorer 7

- 33.2 Configuration Issues and Workarounds

- 33.2.1 Re-Create Wallet After Moving Oracle Internet Directory from Test to Production

- 33.3 Documentation Errata

- 33.3.1 Description of the orclrevpwd Attribute Needs Clarification

- 33.3.2 LDAP Commands Do Not Support the -k|-K Option

- 33.3.3 Description of the orclOIDSCExtGroupContainer Attribute Needs Clarification

- 33.3.4 Setting Up LDAP Replication Needs Clarification

- 33.3.5 Password Expired Response Control is Not Documented

- 33.3.6 Configuring the SSO Server for ODSM Integration Needs Clarification

- 33.3.7 Determining Expired Users in Oracle Internet Directory

- 33.3.8 New Superuser Account Must be Direct Member of DirectoryAdminGroup Group

- 33.3.9 SSL Authentication Mode 1 and Anonymous SSL Ciphers Need Clarification

- 33.3.10 Documentation of Replication Server Control and Failover is Incomplete

- 33.3.11 Server Restart After Adding an Encrypted Attribute is Not Documented

- 33.3.12 PASSWORD_VERIFY_FUNCTION Must be Set to NULL to Work with RCU is Not Documented

- 33.3.13 Setting Up Oracle Internet Directory SSL Mutual Authentication

- 33.3.14 Replication Instructions in Tutorial for Identity Management are Incomplete

34 Oracle Platform Security Services

- 34.1 Configuration Issues and Workarounds

- 34.1.1 Oracle Fusion Middleware Audit Framework

- 34.1.1.1 Configuring Auditing for Oracle Access Manager

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

- 34.1.1.3 Audit Reports Always Display in English

- 34.1.1.4 Audit Store Does not Support Reassociation through EM

- 34.1.1.5 OWSM Audit Events not Audited

- 34.1.2 Trailing '\n' Character in Bootstrap Key

- 34.1.3 Users with Same Name in Multiple Identity Stores

- 34.1.4 Script listAppRoles Outputs Wrong Characters

- 34.1.5 Propagating Identities over the HTTP Protocol

- 34.1.5.1 Addition to Section Propagating Identities over the HTTP Protocol

- 34.1.5.2 Correction to Section Client Application Code Sample

- 34.1.5.3 Correction to Section Keystore Service Configuration

- 34.1.5.4 Updating the Trust Service Configuration Parameters

- 34.1.6 Pool Configuration Missing in Identity Store

- 34.2 Documentation Errata

- 34.2.1 Updated Configuration for Role Category

- 34.2.2 Correct setAuditRepository Command Reference Example

- 34.2.3 Demo CA Certificate not for Production Use

- 34.2.4 Incorrect Link to ILM Content

- 34.2.5 Incorrect Table Title in Appendix C

- 34.2.6 Clarification of Note in Appendix C

- 34.2.7 Notes Regarding Need for Server Restarts

35 SSL Configuration in Oracle Fusion Middleware

- 35.1 General Issues and Workarounds

- 35.1.1 Incorrect Message or Error when Importing a Wallet

36 Oracle Directory Integration Platform

- 36.1 General Issues and Workarounds

- 36.1.1 Enabling the Domain-Wide Administration Port on Oracle WebLogic Server Prevents use of the DIP Command Line Interface

- 36.1.2 The AttrMapping Rule dnconvert() function is not Working During Directory Synchronization

- 36.1.3 The Oracle Password Filter for Microsoft Active Directory is not Certified for use With Oracle Unified Directory or Oracle Directory Server Enterprise Edition

- 36.1.4 LDIF Files That Contain Non-ASCII Characters Will Cause the testProfile Command Option to Fail if the LDIF File has Native Encoding

- 36.1.5 Some Changes May Not Get Synchronized Due to Race Condition in Heavily-Loaded Source Directory

- 36.1.6 Synchronization Continues After Stopping Oracle Directory Integration Platform

- 36.1.7 PKCS11 Exception in DIP Server Log File

- 36.1.8 Certain Queries and Provisioning Profile Functionality may Fail on JDK 1.6 u 21

- 36.2 Configuration Issues and Workarounds

- 36.2.1 Update the Mapping Rule for Novell eDirectory

- 36.2.2 Do not use localhost as Oracle Internet Directory Hostname When Configuring Oracle Directory Integration Platform

- 36.2.3 You may Need to Restart the Directory Integration Platform After Running dipConfigurator Against Oracle Unified Directory

- 36.2.4 When Configuring a Profile, you may Need to Scroll Past a Section of Whitespace to View Mapping Rules

- 36.2.5 Resource Usage Charts will not Display if Multiple IDM Domains are Running on the Same Host

- 36.3 Documentation Errata

37 Oracle Virtual Directory

- 37.1 General Issues and Workarounds

- 37.1.1 Oracle Virtual Directory Fails to Start When Unsupported Ciphersuite for Listener SSL Config is Selected in Enterprise Manager

- 37.1.2 EUS Adapter Creation Failed

- 37.1.3 Manually Edit adapters.os_xml File When Creating DB Adapter For Sybase

- 37.1.4 ODSM Version Does Not Change in Enterprise Manager after Patching ODSM to 11.1.1.6.0

- 37.1.5 ODSM Bug Requires Editing of odsmSkin.css File

- 37.1.6 Oracle Directory Services Manager Browser Window is Not Usable

- 37.1.7 Exceptions May Occur in Oracle Directory Services Manager When Managing Multiple Oracle Virtual Directory Components and One is Stopped

- 37.1.8 Identifying the DN Associated with an Access Control Point in Oracle Directory Services Manager

- 37.1.9 Issues With Oracle Virtual Directory Metrics in Fusion Middleware Control

- 37.1.9.1 Configuring Operation-Specific Plug-Ins to Allow Performance Metric Reporting in Fusion Middleware Control After Upgrading to 11g Release 1 (11.1.1)

- 37.1.10 Using a Wildcard when Performing an LDAPSEARCH on a TimesTen Database Causes an Operational Error

- 37.1.11 ODSM Version 11.1.1.4.0 Does Not Support OVD Versions 11.1.1.2.0 or 11.1.1.3.0

- 37.1.12 ODSM Version 11.1.1.5.0 Does Not Support OVD Versions 11.1.1.2.0, 11.1.1.3.0, or 11.1.1.4.0

- 37.1.13 ODSM Version 11.1.1.6.0 Does Not Support OVD Versions 11.1.1.2.0, 11.1.1.3.0, 11.1.1.4.0, or 11.1.1.5.0

- 37.1.14 Users with Non-ASCII Names Might Encounter Problems when Using ODSM with SSO

- 37.1.15 Creating an Attribute/Object Class Throws NPE Error

- 37.1.16 Patch Required to Enable Account Lockout Feature

- 37.1.17 ODSM Problems in Internet Explorer 7

- 37.1.18 Strings Related to New Enable User Account Lockout Feature on EUS Wizard Are Not Translated

- 37.1.19 All Connections Created In ODSM 11.1.1.1.0 Are Lost After Upgrading to OVD or OID Version 11.1.1.7.0

- 37.1.20 Incorrect ODSM Version Displays in Enterprise Manager Console After OVD Upgrade

- 37.1.21 Connection Issues to OVD

- 37.1.22 ODSM Version 11.1.1.70 Does Not Support OVD Versions 11.1.1.2.0, 11.1.1.3.0, 11.1.1.4.0, 11.1.1.5.0, or 11.1.1.6.0

- 37.1.23 Modify Completes When Updating a Mandatory Attribute to Null

- 37.1.24 Online Help Section is Not Working

- 37.2 Configuration Issues and Workarounds

- 37.2.1 Configuring an OVD/OID Adapter For SSL Mutual Authentication

- 37.3 Documentation Errata

- 37.3.1 Deploying Oracle Unified Directory with Oracle Virtual Directory

38 Oracle Authentication Services for Operating Systems

- 38.1 What is New with Oracle Authentication Services for Operating Systems 11.1.1.3 ?

- 38.2 General Issues and Workarounds

Part XI Oracle Portal, Forms, Reports and Discoverer

39 Oracle Business Intelligence Discoverer

- 39.1 General Issues

- 39.1.1 Error while Accessing a Discoverer Menu Option in Enterprise Manager

- 39.1.2 Issues with Metadata Repository and Oracle Database 10g Release 1

- 39.1.3 Compatibility Issues with Required Support Files

- 39.1.4 Serif Font Issue in Worksheets

- 39.1.5 Additional Fonts Required for Non-ASCII Data When Exporting to PDF

- 39.1.6 Query Prediction Requires the Majority of the Query Time

- 39.1.7 Word Wrapping Behavior with Oracle BI Discoverer Plus and Oracle BI Discoverer Viewer

- 39.1.8 Applet Appears Behind Browser Window

- 39.1.9 Issues with Mac OS X Browser and Oracle BI Discoverer Plus

- 39.1.10 Issues with Turkish Regional Settings

- 39.1.11 Multibyte Characters Rendered as Square Boxes in Exported PDF and Other Formats

- 39.1.12 Java Plug-in Not Downloaded Automatically on Firefox

- 39.1.13 HTTP 404 Error While Accessing Discoverer on a Remote Machine

- 39.1.14 Error While Launching Discoverer Plus Applet on an IPv6 Environment

- 39.1.15 Error While Updating the Discoverer Web Services Configuration Parameter

- 39.1.16 Exception Logged for Discoverer Web-Based Applications in an Extended Domain

- 39.1.17 Issue with Discoverer Application URL in Fusion Middleware Control after a Backup Recovery

- 39.1.18 Incorrect Version Number for Discoverer in Fusion Middleware Control 11g

- 39.1.19 Oracle BI Discoverer Startup Fails after Shutdown

- 39.1.20 The Database Export and Import Utility does not Work with Applications Mode EUL

- 39.1.21 Install-level Scripts are not Updated in Existing Instances after Patching

- 39.1.22 Oracle Business Intelligence Sessions Fail to Start

- 39.2 Issues Specific to Oracle BI Discoverer Plus Relational

- 39.2.1 Text Appearing Truncated or Clipped

- 39.2.2 Non-ASCII Characters Not Saved Correctly in Title or Text Area

- 39.2.3 Canceling Query Causes Discoverer to Hang

- 39.2.4 Nonaggregable Values Not Displayed for Scheduled Workbooks

- 39.2.5 Migrating Oracle BI Discoverer Plus Relational Worksheets from Oracle BI Discoverer Desktop

- 39.3 Issues Specific to Oracle BI Discoverer Plus OLAP

- 39.3.1 Issues with Applet Download

- 39.3.2 Disabled Netscape and Mozilla Browsers

- 39.3.3 Tabbing Fails to Synchronize Menus

- 39.3.4 Esc Key Fails to Close Certain Dialogs

- 39.3.5 Link Tool Works Incorrectly in Some Locales

- 39.3.6 Memory Issues when Exporting Extremely Large Graphs

- 39.3.7 Issue While Printing Worksheets with Large Data Values

- 39.3.8 Issues with Titles and Text Areas

- 39.3.9 Errors with JAWS and Format Dialogs

- 39.4 Issues Specific to Oracle BI Discoverer Portlet Provider

- 39.4.1 Inability to Turn Off Display of Range Min and Max as Labels

- 39.4.2 Issues with Discoverer Portlets in WebCenter

- 39.4.3 Issue while Publishing Discoverer WSRP Portlets in Portals Other than Oracle Portal and Oracle WebCenter

- 39.4.4 Issue with Portlet Titles in Discoverer WSRP Portlets Published on IBM WebSphere

- 39.4.5 Issue with Color and Date Pickers in Discoverer WSRP Portlets

- 39.4.6 Worksheet Parameter LOV is not Displayed in Discoverer WSRP Portlets on IBM WebSphere Portal

- 39.4.7 Issue with Worksheet Parameter LOV Pop-Up Window in Discoverer WSRP Portlets

- 39.5 Issues Specific to Oracle BI Discoverer Viewer

- 39.5.1 Drill Icons Cannot Be Hidden in Oracle BI Discoverer Viewer

- 39.5.2 Error Displaying Page for Multiple SSO Users

- 39.5.3 Inability to Disable the Display of Row Numbers

- 39.5.4 Issues with Oracle BI Discoverer Viewer Embedded in Frames

- 39.5.5 Issue Exporting to PDF Under Certain Circumstances

- 39.5.6 Issue When Changing Colors for Oracle BI Discoverer Viewer in Fusion Middleware Control on Mac OS X

- 39.5.7 Discoverer Catalog Items Not Visible From UNIX Servers

- 39.5.8 Known Bug with JAWS Prevents Drilling Using the Enter Key

- 39.5.9 JAWS Does Not Read Asterisks that Precede Fields

- 39.5.10 Oracle BI Discoverer Viewer Pages are not Cached by Oracle Web Cache

- 39.6 Issues Specific to Oracle BI Discoverer EUL Command Line for Java

- 39.6.1 Issue with Exported Non-ASCII Data

- 39.7 Issues Specific to Oracle BI Discoverer Administrator

- 39.7.1 Issue with Installation of Video Stores Tutorial

40 Oracle Forms

- 40.1 General Issues and Workarounds

- 40.1.1 Backwards Compatibility with Earlier Releases

- 40.1.2 Linux/UNIX Issues and Workarounds

- 40.1.2.1 LD_PRELOAD Setting Required for Signal Chaining Facility

- 40.1.2.2 Check the Reports Engine Logs for FRM-41214

- 40.1.2.3 Changing User Permissions

- 40.2 Configuration Issues and Workarounds

- 40.2.1 Non-Internet Explorer Browser Proxy Settings when Using One-Button-Run

- 40.2.2 WebUtil Client Files Allow Configuration of Destination Directory

- 40.2.3 webutil.properties Files Renamed for Different Libraries

- 40.2.4 Forms does not Work with JDK 1.6.0_12 on Client with WinRunner

- 40.2.5 JavaScript Communication Does not Work in IE for Framed HTML File

- 40.2.6 JavaScript Events Calling Forms Applications in a Safari 5 Browser Do not Work

- 40.3 Documentation Errata

- 40.3.1 Passing userid in Secure Mode

- 40.3.2 JDAPI Programming Example

- 40.3.3 Changes and workarounds affecting the number of characters that can be typed into an item

41 Oracle Reports

- 41.1 General Issues and Workarounds

- 41.1.1 Mapping Users and Roles to Reports Application

- 41.1.2 Reports Weblayout not Supported on SUSE 10

42 Oracle Portal

- 42.1 Before You Begin

- 42.2 General Issues and Workarounds

- 42.2.1 Editing a Database Link Requires Password

- 42.2.2 Moving Content When Approval Is Enabled Does Not Require Approval

- 42.2.3 Firefox and Safari Browsers Do Not Display Tooltips on Oracle Portal Screens

- 42.2.4 Non-ASCII URLs Cannot be Decoded in Some Scenarios

- 42.2.5 Adding a Zip File with a Non-ASCII Character Name

- 42.2.6 Manual Changes to Oracle Portal Default Schema Objects

- 42.2.7 Error When Creating RCU Portal Schema

- 42.2.8 Portal Throws Discoverer Provider is Busy Error Message

- 42.2.9 Error When Adding Sample RSS Portlets to a Page

- 42.2.10 Internal Error when Using Portal Search With Oracle Text Enabled to Search for Pages

- 42.2.11 Issue After Creating a Oracle Portal Schema

- 42.2.12 Updating Database Tables

- 42.2.13 Apply Patch to Address Performance Issue

- 42.3 Upgrade Issues and Workarounds

- 42.3.1 Upgrading Portal 10g SSL Environment to Oracle Portal 11g Release 1 (11.1.1)

- 42.4 Interoperability Issues and Workarounds

- 42.4.1 Interoperability Between Oracle Portal 11g Release 1 (11.1.1) with Secured Enterprise Search (SES) 10.1.8.3

- 42.4.2 Interoperability Between Oracle Portal 11g Release 1 (11.1.1) with Secured Enterprise Search (SES) 10.1.8.4

- 42.4.3 Creating Webproviders in the Oracle Portal 11g Release 1 (11.1.1) Midtier Interoperability with Oracle Portal Repository 10g Release

- 42.5 User Interface Issue and Workaround

- 42.6 Export and Import Issues and Workarounds

- 42.6.1 Export and Import Does Not Support Reports Server Components

- 42.6.2 Saving the Transport Set

- 42.6.3 Error when importing a page group

- 42.7 Portlet and Provider Issues and Workarounds

- 42.7.1 Issue When Accessing Page Portlet Using Federated Portal Adapter

- 42.7.2 Error in JPS Portlet After Redeployment

- 42.7.3 SSL Support for Oracle Portal Integration Solutions (Microsoft Exchange)

- 42.8 PDK Issue and Workaround

- 42.9 Globalization Support Issues and Workarounds

- 42.9.1 Text Entry Always Right to Left in BiDi Languages

- 42.9.2 Non-ASCII Character Limitations in Oracle Portal

- 42.9.3 Multibyte Characters in Log Files

Part XII Oracle Data Integrator

43 Oracle Data Integrator

- 43.1 Configuration Issues and Workarounds

- 43.1.1 Generated Templates Including a Datasource With an Oracle RAC URL Fail to Deploy

- 43.1.2 Generated Templates Including Datasources Fail to Deploy

- 43.1.3 Setting Test Queries on WLS Datasources

- 43.1.4 Oracle Web Service Manager (OWSM) Integration with ODI Web Services Not Available on IBM WebSphere Platform

- 43.2 Design-Time Environment Issues and Workarounds

- 43.2.1 For File Datastores, the View Data operation always looks for global context

- 43.2.2 Quick Edit Editor deletes incorrect Joins when sorted

- 43.2.3 Quick Edit Editor displays a Source as removed regardless of the Selection made in the Warning Dialog

- 43.2.4 Inconsistent Behavior when Refreshing Load Plans

- 43.2.5 User Parameters are not Taken into Account by the Runtime Agents

- 43.2.6 Incorrect Non-ASCII File Names in Zip Export Files

- 43.2.7 Non-ASCII Characters Incorrectly Converted to Underscore Characters

- 43.3 Oracle Data Integrator Console Issues and Workarounds

- 43.3.1 Oracle Data Integrator Console Page Task Flow Resets When Another Tab Is Closed.

- 43.3.2 Enterprise Manager Logout Does Not Propagate to Oracle Data Integrator Console

- 43.3.3 Standalone Agent Target Does Not Show Current Status

- 43.3.4 Basic Configuration Cannot Be Done Through FMW Console

- 43.3.5 Error with Variable Handling in Sequences in ODI Studio

- 43.4 Technologies and Knowledge Modules Issues and Workarounds

- 43.4.1 For Microsoft Excel Target Datastores, column names must be in upper case

- 43.4.2 For File Datastores, reverse-engineering process cannot be canceled

- 43.4.3 SQL Keywords are not imported when importing a Technology in Duplication Mode

- 43.4.4 SQL Exception "Unknown Token" appears when using Complex File or XML as Staging Area

- 43.4.5 Adding Subscribers fails for Consistent Set JKMs when the Model Code Contains Non-ASCII Characters

- 43.4.6 IKM and LKM SQL Incremental Update (Row by Row) fail with Non-ASCII Characters

- 43.4.7 IKM SQL Incremental Update (Row by Row) Cannot Target Japanese Tables

- 43.5 Oracle Data Profiling and Oracle Data Quality Issues and Workarounds

- 43.5.1 ODIDQ fails to Create Loader Connection when Server is Installed on Linux 64 bits

- 43.5.2 Unable to Connect the Client to a Data Quality Server on UNIX

- 43.5.3 Menus Are in English When Starting the Client Using a .tss File.

Part XIII Oracle Business Intelligence

44 Oracle Business Intelligence

- 44.1 Patch Requirements

- 44.1.1 Obtaining Patches from My Oracle Support

- 44.2 Oracle Business Intelligence Issues and Workarounds Identified or Changed Since the Last Revision

- 44.3 Which Releases Are Covered by These Release Notes?

- 44.3.1 Oracle Business Intelligence Issues and Workarounds that Apply Only to Release 11.1.1.3

- 44.4 Oracle Business Intelligence General Issues and Workarounds

- 44.4.1 Oracle BI Disconnected Analytics Not Included in Oracle Business Intelligence 11g, Releases 11.1.1.5 and Later

- 44.4.2 Oracle Hyperion Smart View for Office Not Supported in Oracle Business Intelligence 11g, Releases 11.1.1.5, 11.1.1.6.0, and 11.1.1.6.2

- 44.4.3 Issue with JAR File Size When Moving from a Test to a Production Environment

- 44.4.4 Adobe Flash Player Version 10.1 or Later Required to View Graphs and Scorecards

- 44.4.5 Recommended Page Size Setting on Oracle Solaris

- 44.4.6 Siteminder Not Supported with Full-Text Catalog Search with Oracle Secure Enterprise Search

- 44.4.7 Full-Text Search Not Finding BI Publisher Reports by Report Column

- 44.4.8 Out of Memory Error When Crawling the Catalog

- 44.4.9 Problems Installing in Thai and Turkish Locales

- 44.4.10 Graph Subtypes Are Not Refreshed in BI Composer

- 44.4.11 Dashboards and Scorecards Whose Paths Contain Multibyte Characters Do Not Display on ADF Pages

- 44.4.12 Characters Supported in Folder Names by BI Presentation Services Not Supported by BI Publisher

- 44.4.13 Configuring SSO for Essbase and Hyperion Financial Management Data Sources with Oracle Business Intelligence 11.1.1.3

- 44.4.14 Configuring SSO for Essbase and Hyperion Financial Management Data Sources With Oracle Business Intelligence 11.1.1.5, 11.1.1.6, and 11.1.1.6.2

- 44.4.14.1 Configuring SSO for Essbase and Hyperion Financial Management Release 11.1.2.1 or Later

- 44.4.14.2 Configuring SSO for Essbase and Hyperion Financial Management Release 11.1.2.0 or Earlier

- 44.4.15 Patch Available to Hide Selected Consistency Check Warnings

- 44.4.16 Issues with WebLogic LDAP User Passwords

- 44.4.17 Configuring the GUID Attribute in the Identity Store

- 44.4.18 Rendering Issues Might Occur in Presentation Services When Using Microsoft Internet Explorer 9.x

- 44.4.19 Links Fail to Open in PDF Format of the Briefing Book

- 44.4.20 Poor Performance Starting Up WebLogic Server

- 44.4.21 Analysis State Is Not Maintained for Breadcrumbs

- 44.4.22 Enhancements to Accessibility Features

- 44.4.23 Using Non-Native Characters In ODBC Data Source Administrator Wizard

- 44.5 Oracle Business Intelligence Installation Issues and Workarounds

- 44.5.1 Error When Installing Oracle Business Intelligence Against a SQL Server Database

- 44.5.2 Scale-Out Scenarios Are Not Supported on OS with Different Patch Levels

- 44.5.3 Need to Correctly Create the Oracle Central Inventory in a UNIX Environment

- 44.5.4 Oracle Business Intelligence Installer Stops at Administrator User Details Screen

- 44.5.5 Installing Oracle Business Intelligence on a Shared Drive Might Fail

- 44.5.6 Configuring DB2 to Support Multibyte Data

- 44.5.7 Using Multibyte Data Causes Issues with Microsoft SQL Server 2005/2008 Driver in Oracle BI Scheduler

- 44.5.8 Missing Locale Causes Oracle Business Intelligence Installation to Fail on UNIX

- 44.5.9 Ignore FAT File System Error Message When Performing an Enterprise Installation

- 44.5.10 Financial Reporting Print Server Not Enabled

- 44.5.11 Oracle Hyperion Calculation Manager does not work correctly without Adobe Flash Player

- 44.5.12 Oracle Universal Installer Incorrectly Reports "No IPv4 Network Interfaces Found"

- 44.5.13 Oracle Business Intelligence Configuration Error with Multiple Instances

- 44.5.14 Managed Server Starts with Low Memory Settings

- 44.6 Oracle Business Intelligence Upgrade Issues and Workarounds

- 44.6.1 General Upgrade Issues and Workarounds

- 44.6.1.1 Conditional Formatting Might Not Work After Upgrading from Oracle Business Intelligence Release 10g to Release 11g

- 44.6.1.2 Issues Exporting Large Data Sets to Microsoft Excel

- 44.6.1.3 Managed Server for Oracle BI Encounters Issues After Upgrade from Release 11.1.1.3

- 44.6.1.4 MapViewer Runtime Failure After Upgrading from Release 11.1.1.6 to Release 11.1.1.7

- 44.6.2 Security-related Upgrade Issues and Workarounds

- 44.6.2.1 Warnings Might Be Reported When Upgrading an RPD with Non-English User or Group Names

- 44.6.2.2 Users or Groups With Names Containing Invalid Characters Are Not Upgraded

- 44.6.2.3 RPD Upgrade Process Fails If the 10g Administrator UserID or Password Contains any Non-Native Characters

- 44.6.2.4 Errors Might Be Reported In Upgraded Analyses that Contain EVALUATE_ Database Analytic Function

- 44.6.2.5 Configuration Assistant for Update BI Domain Steps Incorrectly Reports an OCM Configuration Error at 91% Complete when Moving from Earlier 11g Releases

- 44.6.2.6 SSL Configured in Oracle BI EE 11.1.1.5.x or 11.1.1.6.x Fails After Upgrading to 11.1.1.7

- 44.7 Oracle Business Intelligence Installation Guidelines for 64-Bit Platforms

- 44.7.1 Prerequisites for Software Only Installation on 64-Bit Platforms

- 44.7.2 Supported Installation Types for Oracle Business Intelligence on 64-Bit Platforms

- 44.7.3 Considerations and Limitations of Enterprise Install Type for Scaling Out Existing Installations

- 44.8 Oracle Business Intelligence Analyses and Dashboards Issues and Workarounds

- 44.8.1 General Analyses and Dashboards Issues and Workarounds

- 44.8.1.1 Existing Dashboard Prompts Based on Columns Renamed in the Business Model Do Not Work

- 44.8.1.2 Gauge Views Might Be Cut Off and Not Visible Under Certain Conditions

- 44.8.1.3 Numerical Units on a Dashboard Prompt Slider Might Not Be Translated Correctly

- 44.8.1.4 After Printing a Dashboard Page Using the Safari Browser on Windows, the Page No Longer Responds to Certain Left Clicks

- 44.8.1.5 Scorecard Diagrams on Dashboard Pages Might Print as Tables

- 44.8.1.6 Using Maps with Column Selectors

- 44.8.1.7 Issue with Wrap-Around Feature for Maps

- 44.8.1.8 Inability to Delete Map Tiles in MapViewer

- 44.8.1.9 Support for Rendering Small Form-Factor Graphs

- 44.8.1.10 Analyses Whose Paths Contain Latin Supplement Characters Fail to Open on Dashboard Pages

- 44.8.1.11 In Selection Steps Search for Members in Hierarchical Columns That Are Non-Text Yields No Results

- 44.8.1.12 Interactions on Right-Click Menus Are Not Translated

- 44.8.1.13 Issues with the Alignment of Trellis Views

- 44.8.1.14 Characters in Trellis Title Display Incorrectly in Certain Languages

- 44.8.1.15 Export to Excel 2007+ and Export to PDF Do Not Support Custom CSS Styles

- 44.8.1.16 Items Not Supported When Using Custom Print Layouts

- 44.8.1.17 Grand Total Shows Zero in Reports After Applying BI 11.1.1.7.1 Patch

- 44.8.2 Actions Issues and Workarounds

- 44.8.2.1 EJBs in Action Framework Must Be Deployed to the WebLogic Managed Server

- 44.8.3 Scorecards and KPI Issues and Workarounds

- 44.8.3.1 No Results Returned When Searching in the Related Documents of Scorecards or Scorecard Components

- 44.8.3.2 Accessing a Smart Watchlist from the Oracle Secure Enterprise Search Results Page Causes an Error

- 44.8.3.3 Item Stale Error When Editing a Shared Scorecard in Parallel

- 44.8.3.4 Scorecard Pie Chart and Gauge Labels are Not Readable in Chrome

- 44.8.4 Agents Issues and Workarounds

- 44.8.4.1 Agent Deliveries Fail with Microsoft Active Directory and Oracle Virtual Directory

- 44.8.4.2 Agent Incorrectly Delivers Content to Active Delivery Profile When Only the Home Page and Dashboard Option Is Selected

- 44.8.5 Microsoft Office Integration Issues and Workarounds

- 44.8.5.1 Using Microsoft Office 2007 with Oracle BI Add-in for Microsoft Office

- 44.8.5.2 Server Connections Are Not Automatically Shared by Microsoft Excel and PowerPoint

- 44.8.5.3 Previous Installation of Oracle BI Add-in for Microsoft Office Must Be Manually Uninstalled

- 44.8.5.4 Errors in the Online Help for Oracle BI Add-In for Microsoft Office

- 44.8.5.5 Refreshing Table or Pivot Table Views with Double Columns in Page Edge Might Result in Error

- 44.8.5.6 Double Column Cascading Results in Incorrect Display Values

- 44.8.5.7 Intermittent Timeout Errors

- 44.8.5.8 Lack of Support for Vary Color By Target Area

- 44.8.5.9 Measure Column Labels Might Display Incorrectly When Inserted into Microsoft Excel

- 44.8.5.10 Stacked Graphs Do Not Display Negative Values

- 44.8.5.11 Scatter Graphs with Lines Display as Default Scatter Graphs in Excel and PowerPoint

- 44.8.5.12 Graphs With Section Edges Are Not Supported Starting With Release 11.1.1.6.x

- 44.8.5.13 Refreshing Table Views in Arabic or German Versions of Excel Result in Incorrect Data Values

- 44.8.5.14 Inserting a View With a Grand Total Column or Row into Microsoft Office Might Cause Issues

- 44.8.5.15 Time Displayed in Table or Pivot View Title Might Be Incorrect after Insertion

- 44.8.5.16 Graphs Might Be Displayed Differently After Insertion into Microsoft Office

- 44.8.5.17 Legends in Bubble and Scatter Graphs Might Display Differently After Insertion into Microsoft Office

- 44.8.5.18 Help System Does Not Work When Running Oracle BI Office for PowerPoint in Norwegian or Polish

- 44.8.5.19 Protected Worksheet Causing Incorrect Message When Inserting View in Oracle BI Add-in for Microsoft Office

- 44.8.5.20 Column Data in Section Edge Is Not Obtained

- 44.9 Oracle Business Intelligence Mobile Issues and Workarounds

- 44.10 Oracle Business Intelligence Mobile App Designer Issues and Workarounds

- 44.11 Oracle Business Intelligence Publisher Reporting and Publishing Issues and Workarounds

- 44.11.1 General Oracle BI Publisher Issues and Workarounds

- 44.11.1.1 JDBC Driver Throws Unsupported Function for setBigDecimal

- 44.11.1.2 Searching the Catalog from the Oracle BI Publisher User Interface Does Not Work When BI Publisher Is Integrated with Oracle BI Enterprise Edition

- 44.11.1.3 Data Source List in BI Publisher Administration Page Includes Data Sources That Are Not Supported

- 44.11.1.4 Menu Items Do Not Display When Using Internet Explorer 7 or 8 with a Bidirectional Language Preference

- 44.11.1.5 Data Source Definition for Microsoft SQL Server 2008 Analysis Services Does Not Get Saved

- 44.11.1.6 Issues with Viewing Some Report Formats on Apple iPad

- 44.11.1.7 BI Publisher Objects Exhibit Unexpected Behavior When Located Inside a Folder Named with a Single Quote Character

- 44.11.1.8 Components Folder Missing from SampleApp Lite Web Catalog

- 44.11.1.9 Boilerplate Templates in the Components Folder Do Not Display Table Borders Properly in Chrome Browsers

- 44.11.1.10 Local Policy Attachments (LPAs) Removed from Web Services in Release 11.1.1.5

- 44.11.1.11 Oracle BI Publisher Requires Oracle WebLogic Server to Run in en_US Locale

- 44.11.1.12 Search Might Return Incorrect Number of Results

- 44.11.1.13 Schedule Report Option Is Not Displayed Correctly for Non-Administrator Users

- 44.11.1.14 Additional Setup for BI Publisher Desktop Tools in 11.1.1.6.2

- 44.11.1.15 Oracle Endeca Search Does Not Work from /xmlpserver URL

- 44.11.1.16 Older Version of Adobe Flash Player Packaged with the Google Chrome Browser Might Cause Unexpected Behavior in the Interactive Viewer

- 44.11.1.17 "Failed to Add" Error When Adding Report Objects to Favorites

- 44.11.1.18 Cannot Add Reports with Multibyte Character Names to Favorites Using the Catalog Task Option

- 44.11.1.19 Excel Analyzer and Online Analyzer Deprecated in Release 11.1.1.7

- 44.11.2 Oracle BI Publisher Security Issues and Workarounds

- 44.11.2.1 Limitations for Administrator Username in LDAP Security Model

- 44.11.2.2 Oracle E-Business Suite Security Requires the BI Publisher Server Operating System Language to Match an E-Business Suite Enabled Language

- 44.11.3 Oracle BI Publisher Delivery Manager Issues and Workarounds

- 44.11.4 Oracle BI Publisher Scheduler Issues and Workarounds

- 44.11.4.1 Scheduler Does Not Support Multibyte Characters When Schema Installed on Microsoft SQL Server

- 44.11.4.2 URL in E-mail Notification of Recurring or Future-Dated Jobs Might Fail to Display Job History for the Job

- 44.11.4.3 After Editing an Existing Job, Immediately Creating a New Job Using "Submit as New" Overwrites the Original Job

- 44.11.5 Oracle BI Publisher RTF Template Issues and Workarounds

- 44.11.5.1 RTF Templates in 11g Require Number Conversion on String Expressions

- 44.11.6 Oracle BI Publisher Excel Template Issues and Workarounds

- 44.11.6.1 Limitations for Excel Template Output on Apple iPad

- 44.11.7 Oracle BI Publisher Desktop Tools Issues and Workarounds

- 44.11.7.1 Oracle BI Publisher's Template Builder for Microsoft Word Is Not Compatible with Microsoft Office Live Add-in

- 44.11.8 Oracle BI Publisher Layout Editor Issues and Workarounds

- 44.11.8.1 Editing an XPT Layout and Clicking Return in Layout Editor Results in Exception

- 44.11.8.2 Interactive Viewer Might Return Unexpected Results from Formula Columns

- 44.11.8.3 Interactive Viewer Returns Incorrect Results for Data Aggregation Functions When the Data Set Is Not a Single, Flat Data Set

- 44.11.8.4 Division Results Rounded Inconsistently When Used with the #,##0 Custom Format Mask

- 44.11.9 Oracle BI Publisher Data Model Issues and Workarounds

- 44.11.9.1 Data Model Is Not Editable When Created by Upgrade Assistant

- 44.11.9.2 Issues with Upgraded 10g Data Models That Include Ref Cursors and Stored Procedures

- 44.11.9.3 After Editing a View Object Data Set, the Elements Are Duplicated

- 44.11.9.4 Excel Workbooks Used as Data Sources Cannot Contain Ampersand (&) in the Sheet Name

- 44.11.10 Oracle BI Publisher Report Building Issues and Workarounds

- 44.11.10.1 Use Oracle BI Publisher Conversion Assistant to Convert Oracle Reports to Oracle BI Publisher 11g

- 44.11.10.2 "Enable Bursting" Report Property Displays Enabled State When Disabled

- 44.11.11 Oracle BI Publisher Documentation Errata

- 44.11.11.1 Oracle Fusion Middleware Report Designer's Guide for Oracle Business Intelligence Publisher

- 44.11.11.2 Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher

- 44.12 Oracle Business Intelligence Metadata Repository Development Issues and Workarounds

- 44.12.1 General Metadata Repository Development Issues and Workarounds

- 44.12.1.1 Use of NQClient (BI ODBC Client) Utility Is Deprecated

- 44.12.1.2 Update Logical Table Source Modeling when Using paint.rpd for Testing

- 44.12.1.3 FIRST and LAST Aggregation Rules Cause Inconsistent Sorting for Time Dimensions

- 44.12.1.4 Oracle OLAP Jars on JavaHost Computer Must Be Updated When Using Oracle OLAP 11.2.x

- 44.12.1.5 Using the BIServerT2PProvisioner.jar Utility to Change Connection Pool Passwords

- 44.12.1.6 Configuring a Servlet for Oracle BI Server Communication with Oracle OLAP

- 44.12.1.7 Enhancing Performance of Aggregates with TimesTen Release 11.2.2.3 or Later

- 44.12.1.8 Performing Merges on Repositories That Contain System-Generated Tables Can Cause Loss of Metadata

- 44.12.1.9 Create Aggregates Operations Can Time Out for TimesTen Targets

- 44.12.1.10 Logical Display Folders Are Deleted During MUD Publish

- 44.12.2 Oracle BI Server Issues and Workarounds

- 44.12.2.1 Configuration Required for Microsoft SQL Server and Oracle BI Summary Advisor

- 44.12.3 Oracle BI Administration Tool Issues and Workarounds

- 44.12.3.1 Administration Tool Incorrectly Displays Option for Generate Deployment File

- 44.12.3.2 Issue with Online Import Object Checkout

- 44.12.3.3 Ignore RPD Consistency Warnings Related to Required Database Feature Changes for Oracle OLAP

- 44.12.3.4 Select Nullable Option for Root Member of Parent-Child Hierarchies from OLAP Sources

- 44.12.3.5 Oracle BI Repository Can Become Corrupt When Objects Are Deleted in MUD Environments

- 44.12.3.6 Model Checker Not Enabled in Release 11.1.1.6.2

- 44.12.3.7 Publishing a Duplicate Dimension Object in a MUD Environment

- 44.13 Oracle Business Intelligence System Administration Issues and Workarounds

- 44.13.1 General System Administration Issues and Workarounds

- 44.13.2 Configuration Issues and Workarounds

- 44.13.2.1 Removal of DefaultImageType and HardenXSS Elements

- 44.13.3 Deployment, Availability, and Capacity Issues and Workarounds

- 44.13.4 Sign-in and Security Issues and Workarounds

- 44.13.4.1 Permission Required to Open Catalog Manager in Online Mode

- 44.13.5 Oracle BI Scheduler Issues and Workarounds

- 44.13.6 Oracle Essbase Suite Issues and Workarounds

- 44.13.6.1 Ensure that the Installation Uses a JDK Installed into a Folder that Does Not Contain Spaces

- 44.13.6.2 Essbase SQL Interface Using Oracle Call Interface (OCI) to Connect to Oracle Requires Oracle Instant Client

- 44.13.6.3 Options to Set Accessibility Preferences When Using Workspace Are Not Available

- 44.13.6.4 Issue with Dashboards Menu in EPM Workspace

- 44.13.6.5 Merant 6.1 ODBC Drivers Are Not Configured on Linux

- 44.14 Oracle Business Intelligence Integration and API Issues and Workarounds

- 44.14.1 General Integration Issues and Workarounds

- 44.14.2 Oracle Business Intelligence API Issues and Workarounds

- 44.15 Oracle Business Intelligence Localization Issues and Workarounds

- 44.15.1 Product Localization Issues and Workarounds

- 44.15.1.1 Unable to Save Strings with Multibyte Characters to an External File Using ANSI Encoding

- 44.15.1.2 BI Publisher User Interface Components Do Not Support Supplementary Characters

- 44.15.1.3 Non-English Log Files Displayed Incorrectly in Fusion Middleware Control

- 44.15.1.4 Error Messages in BI Publisher Data Model Editor Honor Server Locale Setting

- 44.15.1.5 Incorrect Layout in Tables and Pivot Tables in PDF Files and PowerPoint Presentations When Locale for BI Server Is Arabic or Hebrew

- 44.15.1.6 Excel2007 Output in BI Publisher Does Not Honor Locale Settings for Number and Date Format

- 44.15.1.7 Excel2007 Output in BI Publisher Supports Gregorian Calendar Only

- 44.15.1.8 Template Builder for Microsoft Word Chart Wizard Does Not Format Dates

- 44.15.1.9 Number and Date Format Issues with Charts in BI Publisher Layout Templates

- 44.15.1.10 BI Publisher Report Creation Wizard "Select Columns" Step Does Not Render Properly When UI Language Is Francais

- 44.15.1.11 Albany Fonts Delivered with BI Publisher for PDF Output Do Not Support Bold and Italic for Multibyte Characters

- 44.15.2 Help System Localization Issues and Workarounds

- 44.15.2.1 Oracle Business Intelligence Help Systems Are Not Translated

- 44.16 Oracle Business Intelligence Documentation Errata

- 44.16.1 General Oracle Business Intelligence Documentation Errata

- 44.16.2 Oracle Fusion Middleware Quick Installation Guide for Oracle Business Intelligence

- 44.16.3 Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence

- 44.16.3.1 Installation Guide Contains Misinformation About Installing the Client Tools

- 44.16.3.2 Installation Guide Contains Misinformation About pasteBinary Script

- 44.16.3.3 Installation Guide Contains Misinformation About Installing on a Hardened Database

- 44.16.4 Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence Enterprise Edition

- 44.16.4.1 Incorrect Information on Aggregation

- 44.16.4.2 Incorrect Information on Database Authentication

- 44.16.5 Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition

- 44.16.5.1 Oracle BI Mobile: Embedding a Dashboard or Answers Report Link in an E-mail

- 44.16.5.2 Oracle BI Mobile: Easy Access to Dashboards

- 44.16.5.3 Information about Oracle Hyperion Smart View for Office Must Be Ignored

- 44.16.5.4 Columns from Multiple Subject Areas Included in a Single Query Must Be Compatible

- 44.16.5.5 Error in the "How Will Prompts Created in Previous Versions Be Upgraded?" Topic in Chapter 6, "Prompting in Dashboards and Analyses"

- 44.16.5.6 Content Missing from Appendix E, "User Interface Reference," "Edit Page Settings dialog" Topic, Prompt Buttons Field

- 44.16.5.7 Incorrect Default Pixel Value Specified in Chapter 6, "Prompting in Dashboards and Analyses" and Appendix E, "User Interface Reference"

- 44.16.5.8 Error in the "Actions that Invoke Operations, Functions or Processes in External Systems" Topic in Chapter 10, "Working with Actions"

- 44.16.5.9 Error in the "Show More Columns dialog" Topic in Appendix E, "User Interface Reference"

- 44.16.5.10 Error in the "New Filter dialog" Topic in Appendix E, "User Interface Reference"

- 44.16.5.11 Information on View Latest Version Feature in Error

- 44.16.5.12 Changes to the Instructions for Installing and Configuring BI Composer

- 44.16.5.13 Mentions of the KPI Editor: Data Input Security Page Must Be Ignored

- 44.16.5.14 Breadcrumbs Disabled for Embedded Objects in ADF

- 44.16.5.15 Note on Fixed Headers with Scrolling Content Is Incorrect

- 44.16.5.16 Misinformation About Adding HTML Code in Prompt Labels

- 44.16.5.17 Enable on Totals for Action Links Not Described

- 44.16.5.18 Use of Multiple Values in Presentation Variable on Dashboards Not Described

- 44.16.6 Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Mobile

- 44.16.7 Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition

- 44.16.7.1 Manual opmn.xml Edits Needed to Use Teradata as a Data Source

- 44.16.7.2 Updates to Text for Consistency Check Warnings 39009 and 39059

- 44.16.7.3 Other Changes to List of New Consistency Check Warnings

- 44.16.7.4 Select the Virtual Private Database Option when Authenticating Against Essbase or Hyperion Financial Management Using a Shared Token

- 44.16.7.5 Manually Updating the Master MUD Repository

- 44.16.7.6 Initialization Block Failure at Server Start-Up Causes Connection Pool to be Blacklisted

- 44.16.7.7 Merge Local Changes Step Does Not Lock the Master Repository

- 44.16.7.8 Information Now Available for All Import Metadata Wizard Screens

- 44.16.7.9 Remove Smart View Mention in Appendix C

- 44.16.7.10 Explicitly Check Out Projects to Add Objects in a Multiuser Development Environment

- 44.16.7.11 Changes to DataDirect Drivers and Directories

- 44.16.7.12 Additional Information Available on SCM Configuration Template Files

- 44.16.7.13 Statement on Aggregate Creation Failure is Incorrect

- 44.16.7.14 Prefer Optimizer Estimates Option Available for Summary Advisor in Release 11.1.1.6.2, Bundle Patch 1

- 44.16.8 Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition

- 44.16.8.1 Event Polling Tables Must Be Created Using the Repository Creation Utility (RCU)

- 44.16.8.2 Use of ps: Prefix in Elements Is Unnecessary

- 44.16.8.3 Lowercase for Boolean Values for Configuration Elements

- 44.16.8.4 Removal of Section 11.5, "Configuring to Download Oracle Hyperion Smart View for Office"

- 44.16.8.5 Issue Copying a Jar File when Registering with EPM Workspace Release 11.2.3.00

- 44.16.8.6 Incomplete Information in "Validating the Catalog" Section

- 44.16.8.7 Missing Privilege for Using the Full-Text Catalog Search

- 44.16.8.8 Error for Configuring the Data Source for the Full-Text Catalog Search

- 44.16.8.9 Removal of Section 19.7.2.6, "Including Links with Analyses on Dashboards"

- 44.16.8.10 MaxColumns Element Not Supported

- 44.16.8.11 Error in Section 22.3.2, "Specifying Defaults for Styles and Skins"

- 44.16.8.12 Clarification of CaseInsensitiveMode Element

- 44.16.8.13 Updates of Information About the Catalog

- 44.16.8.14 Section on Manually Configuring for Interactions In Views Does Not Apply

- 44.16.8.15 Omission of Enabled Element in Custom Links Section

- 44.16.8.16 Omission of Section on Updating Java Development Kit (JDK)

- 44.16.8.17 Remove Mention of pasteBinary Script

- 44.16.8.18 Parameter Descriptions Missing or Inaccurate in NQSConfig.INI File Configuration Settings Appendix

- 44.16.8.19 Incorrect Commands to Start and Stop Administration Server on a Windows Environment

- 44.16.9 Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition

- 44.16.9.1 SASchInvoke Always Prompts for the Password in 11.1.1.5

- 44.16.9.2 Setup Multiple Authentication Providers

- 44.16.9.3 Error in Code Example for Refreshing User GUIDs

- 44.16.9.4 Adding UserName Attribute Properties user.login.attr and username.attr to Identity Store is Not Applicable

- 44.16.9.5 Removal of Invalid LDAP Configuration Properties when Setting Up SSL

- 44.16.9.6 Error in Code Example for Configuring a Database Adaptor

- 44.16.9.7 Error in Code Example for Configuring the WebLogic Server Environment

- 44.16.10 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence

- 44.16.11 Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition

- 44.16.11.1 Error in the "Passing Business Intelligence Content with the Oracle BI EE Contextual Event Action" Topic in Chapter 1, "Embedding Business Intelligence Objects in ADF Applications"

- 44.16.12 Oracle Fusion Middleware Integrator's Guide for Oracle Business Intelligence Enterprise Edition

- 44.16.12.1 Addendum to the "Overview of Integrating with Oracle Business Intelligence" Topic in Chapter 10, "Integrating Other Clients with Oracle Business Intelligence"

- 44.16.13 Oracle Fusion Middleware XML Schema Reference for Oracle Business Intelligence Enterprise Edition

- 44.16.14 Oracle Business Intelligence Help System Errata

- 44.16.14.1 Addendum to the Oracle BI Server DSN Configuration Wizard Help

45 Oracle Business Intelligence Applications and Data Warehouse Administration Console

- 45.1 Patch Requirements

- 45.1.1 Obtaining Patches from My Oracle Support

- 45.2 Oracle Business Intelligence Applications Release Notes

- 45.2.1 Oracle Business Intelligence Applications Issues and Workarounds Identified Since the Previous Revision

- 45.2.2 General Issues and Workarounds for Oracle Business Intelligence Applications

- 45.2.2.1 Patch Installation Instructions for Informatica Repository in Oracle BI Applications Release 11.1.1.5.2

- 45.2.2.2 About Issues For Both Oracle Fusion Transactional Business Intelligence and Oracle Business Intelligence Applications

- 45.2.2.3 CONFIGURE_RPD.PY Script Does Not Set Connection Pool for Oracle BI Applications Configuration Manager

- 45.2.2.4 Using Multiple Execution Plans Using Different Source Connection Names But Running On The Same BI Server

- 45.2.2.5 NLS:SDE_FUSION_DOMAINGENERAL_SALESINVOICESOURCE_FULL Failed With Syntax Error

- 45.2.2.6 Informatica License Dis-associating After Installation

- 45.2.2.7 JAZN File Not Translated

- 45.2.2.8 Duplicate Rows in GL Account Segment Hierarchy Tables

- 45.2.2.9 Instructions to Change Create Navigate Actions and Create Invoke Actions to BI Author

- 45.2.2.10 Extracting Fusion Descriptive Flexfield (DFF) Information Into Oracle Business Analytics Warehouse

- 45.2.3 Installation Issues and Workarounds for Oracle Business Intelligence Applications

- 45.2.3.1 Installing Informatica PowerCenter 8.6.1 On Mount Points with Free Disk Space in Terabytes

- 45.2.3.2 Restarting Components After Completing The Post-Installation Setup Steps

- 45.2.3.3 Customer Cost Lines and Product Cost Lines Configuration is Missing From FSM Tasks for Oracle Financial Analytics

- 45.2.4 Upgrade Issues and Workarounds for Oracle Business Intelligence Applications

- 45.2.5 Oracle Business Intelligence Applications Offering/Module-specific Issues

- 45.2.5.1 Issues for Oracle Customer Data Management Analytics Offering

- 45.2.5.2 Issues for Oracle Financial Analytics Offering

- 45.2.5.3 Issues for Oracle Human Resources Analytics Offering

- 45.2.5.4 Issues for Oracle Marketing Analytics Offering

- 45.2.5.5 Issues for Oracle Partner Analytics Offering

- 45.2.5.6 Issues for Oracle Product Information Management Analytics Offering

- 45.2.5.7 Issues for Oracle Procurement and Spend Analytics Offering

- 45.2.5.8 Issues for Oracle Project Analytics Offering

- 45.2.5.9 Issues for Oracle Sales Analytics Offering

- 45.2.5.10 Issues for Oracle Supply Chain and Order Management Analytics Offering

- 45.2.6 Translated Content in Non-English Reports and Dashboards

- 45.2.7 Error in Execution of Task SDE_FUSION_PayrollRunBalanceDetailFact

- 45.2.8 Oracle Business Intelligence Applications Configuration Manager and FSM Issues

- 45.2.9 Security-related Issues for Oracle Business Intelligence Applications

- 45.2.10 Oracle Business Intelligence Applications Documentation Errata

- 45.2.10.1 General Oracle Business Intelligence Documentation Errata

- 45.2.10.2 Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications

- 45.2.10.3 Oracle BI Applications Configuration Manager Help System

- 45.2.10.4 Oracle Fusion Middleware Reference Guide for Oracle Business Intelligence Applications

- 45.3 Oracle Business Intelligence Data Warehouse Administration Console (DAC) Platform Release Notes

- 45.3.1 DAC Issues and Workarounds Identified Since the Previous Revision

- 45.3.2 DAC General Issues and Workarounds

- 45.3.3 DAC Installation Issues and Workarounds

- 45.3.4 DAC Upgrade Issues and Workarounds

- 45.3.5 DAC Documentation Errata

- 45.3.5.1 Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console

- 45.3.5.2 DAC Client Help System

46 Oracle Real-Time Decisions

- 46.1 Oracle RTD General Issues and Workarounds

- 46.1.1 Transient Likelihood Problems

- 46.1.2 Use Development Deployment State Only

- 46.1.3 Error Deploying Inline Services from Command Line if Inline Service Uses Certain Functions

- 46.1.4 Ensuring Unique Batch Names Across a Cluster

- 46.1.5 Safari and Chrome Accessibility Items

- 46.1.6 Learning Service May Skip Processing of Some Learning Records if SDDB is on Oracle RAC Database

- 46.1.7 External Rule Editor Does Not Work in Mozilla Firefox Version 16

- 46.2 Oracle RTD Installation Issues and Workarounds

- 46.3 Oracle RTD Upgrade Issues and Workarounds

- 46.4 Oracle RTD Configuration Issues and Workarounds

- 46.5 Oracle RTD Security Issues and Workarounds

- 46.5.1 Decision Center Logout Not Redirected Correctly for Oracle Access Manager (OAM) 11g Form-Based Authentication

- 46.6 Oracle RTD Administration Issues and Workarounds

- 46.7 Oracle RTD Integration Issues and Workarounds

- 46.7.1 Java Smart Client Run Configuration Changes Required for Different Properties Files

- 46.8 Oracle RTD Decision Studio Issues and Workarounds

- 46.8.1 Mapping Array Attributes in a Multi-Level Entity Hierarchy

- 46.8.2 Issues When Trying to Enable Caching for Some Entities

- 46.8.3 Terminate Active Sessions in Cluster Works Only on Decision Server Receiving Deployment Request

- 46.9 Oracle RTD Decision Center Issues and Workarounds

- 46.10 Oracle RTD Performance Monitoring Issues and Workarounds

- 46.11 Oracle RTD Externalized Objects Management Issues and Workarounds

- 46.12 Oracle RTD Localization Issues and Workarounds

- 46.13 Oracle RTD Documentation Errata

- 46.13.1 Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions

- 46.13.2 Oracle Fusion Middleware Platform Developer's Guide for Oracle Real-Time Decisions

- 46.13.2.1 External Rules Development Helper Mismatch between Code and Manual Description

- 46.13.2.2 Save Choice IDs in Inline Services Rather Than Choices

- 46.14 Oracle RTD Third-Party Software Information

- 46.14.1 Displaytag Download Location

Preface

This preface includes the following sections:

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

Audience

This document is intended for users of Oracle Fusion Middleware 11g.

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

Part I

Oracle Fusion Middleware

Part I contains the following chapters:

- Chapter 1, "Introduction"

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

- Chapter 3, "Upgrade"

- Chapter 4, "Oracle Fusion Middleware Administration"

- Chapter 5, "Oracle Enterprise Manager Fusion Middleware Control"

- Chapter 6, "Oracle Fusion Middleware High Availability and Enterprise Deployment"

- Chapter 7, "Oracle Fusion Middleware on IBM WebSphere"

1 Introduction

This chapter introduces Oracle Fusion Middleware 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, "Memory Requirements"

- Section 1.5, "Certification Information"

- Section 1.6, "Downloading and Applying Required Patches"

- Section 1.7, "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 Fusion Middleware 11g Release 1 (11.1.1). It describes differences between Oracle Fusion Middleware and its documented functionality.

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

1.3 System Requirements and Specifications

Oracle Fusion Middleware installation and configuration will not complete successfully unless users meet the hardware and software pre-requisite requirements before installation.

For more information, see "Review System Requirements and Specifications" in the Oracle Fusion Middleware Installation Planning Guide

1.4 Memory Requirements

Oracle Fusion Middleware memory requirements for installation, configuration, and runtime are as follows:

1. Without a Database on the same server: Minimum 4 GB physical memory and 4 GB swap.

2. With a Database on the same server: Minimum 6 GB physical memory and 6 GB swap.

Note:

These minimum memory values are with the assumption that no user or operating system process is consuming any unusually high amount of memory. If such a condition exists, corresponding amount of additional physical memory will be required.

1.5 Certification Information

This section contains the following:

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

- Section 1.5.2, "Certification Exceptions"

- Section 1.5.3, "JMSDELIVERYCOUNT Is Not Set Properly"

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

1.5.1 Where to Find Oracle Fusion Middleware Certification Information

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

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

1.5.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.5.2.1, "Certification Information for Oracle Fusion Middleware 11g R1 with Oracle Database 11.2.0.1"

- Section 1.5.2.3, "Restrictions on Specific Browsers"

- Section 1.5.2.4, "Process to Install and Configure WebCenter With 32-bit JDK on Supported 64-Bit Platform"

1.5.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.5.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.5.2.3 Restrictions on Specific Browsers

1.5.2.3.1 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.5.2.3.2 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.5.2.4 Process to Install and Configure WebCenter With 32-bit JDK on Supported 64-Bit Platform

For WebCenter 11g Release 1, the following platform has been verified with 32-bit JDK:

Solaris Sparc:

32-bit Sun JDK 1.6.0_11+

1.5.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.5.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.6 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.7 Licensing Information

Licensing information for Oracle Fusion Middleware is available at:

http://oraclestore.oracle.com

Detailed information regarding license compliance for Oracle Fusion Middleware 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, "Issues Pertaining to Oracle SOA Suite Installation"

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

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

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

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

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

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

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

- Section 2.1.9, "Issues Pertaining to Product Deinstallation"

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

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

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

- Section 2.1.13, "Enterprise Manager Configuration Fails with Timezone Error Message"

2.1.1 Issues Pertaining to Oracle SOA Suite Installation

This section contains the following:

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

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

2.1.1.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.1.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 Issues Pertaining to Oracle Portal, Forms, Reports and Discoverer Installation

This section contains the following:

- Section 2.1.2.1, "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.2.2, "Considerations When Installing Oracle Portal 11g"

- Section 2.1.2.3, "Prerequisite Warnings During Installation"

- Section 2.1.2.4, "Prerequisite Checks Fail During the Installation of Oracle Portal, Forms, Reports, and Discoverer 11g Release 1 (11.1.1.2.0) on Solaris 11"

2.1.2.1 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.2.2 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.2.3 Prerequisite Warnings During Installation

Vendor release updates cummulative patches and/or packages that may superseed our listed Oracle Fusion Middleware 11g Release 1 prerequisites for platforms. As long as vendor approved patches and/or packages are installed, the prerequisite warnings could be ignored and the installation completed.

Another option is to use -ignoreSysPreReqs command line additional argument to the runInstaller as:

$  Mount_Point/runInstaller -ignoreSysPreReqs other required install options

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

During the installation of Oracle Portal, Forms, Reports and Discoverer 11g Release 1 (11.1.1.2.0) on Solaris 11 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 Web Tier Installation

This section contains the following:

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

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

2.1.3.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.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.3.2 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.4 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.4.1, "WebLogic Administration Server Must Be Running When Extending Oracle Identity Management Domains"

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

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

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

- Section 2.1.4.5, "Enabling the Retry Button"

- Section 2.1.4.6, "Server Startup Failures on Linux Operating Systems"

- Section 2.1.4.7, "Configuring OPMN Request Port"

- Section 2.1.4.8, "Silent Install with Privileged Ports on Linux Operating Systems"

2.1.4.1 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.4.2 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.4.3 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.4.4 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.4.5 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.4.6 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.4.7 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.4.8 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 Issues Pertaining to JDK and JRE Installation

This section contains the following:

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

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

2.1.5.1 Specifying the JRE Location if Installing with Automatic Updates

If you are installing 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.5.2 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.6 Issues Pertaining to Oracle Universal Installer

This section contains the following:

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

- Section 2.1.6.2, "Installer is Checking for the Wrong System Patches on Solaris x86-64"

2.1.6.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.6.2 Installer is Checking for the Wrong System Patches on Solaris x86-64

The installer for Fusion Middleware products is looking for following operating system patches on Solaris x86-64 operating systems:

- 127111-02

- 137111-04

These are incorrect; the correct operating system patches required for Solaris x86-64 operating systems are:

- 127112

- 137112

More information about these patches can be found in notes 1000642.1 and 1019395.1 on My Oracle Support.

2.1.7 Issues Pertaining to Database and Schema Installation

This section contains the following:

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

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

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

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

2.1.7.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.7.2 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.7.3 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 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.7.4 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.8 Error Messages and Exceptions Seen During Installation

This section contains the following:

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

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

2.1.8.1 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.8.2 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.9 Issues Pertaining to Product Deinstallation

This section contains the following:

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

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

2.1.9.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 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 directory:

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

2.1.9.2 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.10 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.11 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.12 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.13 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, "Patching Oracle WebCenter Portal and Oracle WebCenter Content with Other Fusion Middleware Products in the Same Domain"

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

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

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

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

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

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

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

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

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

- Section 2.2.12, "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 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 Patching Oracle WebCenter Portal and Oracle WebCenter Content with Other Fusion Middleware Products in the Same Domain

Oracle recommends that all products in the same domain have the same version number (see "Middleware Home and Domain Interoperability" in Oracle Fusion Middleware Interoperability and Compatibility Guide for details).

However, in Oracle Fusion Middleware 11g Release 1 (11.1.1.8.0), only Oracle WebCenter Portal and Oracle WebCenter Content are released. All other products are at 11g Release 1 (11.1.1.7.0) or earlier, depending on their respective latest available versions. Therefore, it is possible to have a domain with Oracle WebCenter Portal and Oracle WebCenter Content that have different version numbers than other Fusion Middleware Products in the same domain.

Note:

If you want to patch to 11g Release 1 (11.1.1.8.0), it is recommended that you patch both Oracle WebCenter Portal and Oracle WebCenter Content to 11g Release 1 (11.1.1.8.0) within the same domain. You do not need to install them into separate domains because of mixed release versions. After you have patched Oracle WebCenter Portal and Oracle WebCenter Content to release 11.1.1.8.0, you can then apply the latest patches available for these products.

2.2.3 Issues Pertaining to Patching Oracle SOA Suite

This section contains the following:

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

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

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

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

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

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

- Section 2.2.3.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.3.8, "Oracle Rules Error in Administration Server Log Files After Patching an 11g Release 1 (11.1.1.2.0) Domain"

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

2.2.3.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.3.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.3.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.3.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.3.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 BPM Suite.

2.2.3.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.3.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.3.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.3.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 BPM Suite.

2.2.4 Issues Pertaining to Patching Oracle WebCenter Portal

This section contains the following:

- Section 2.2.4.1, "Configuring Additional Crawl Sources for Discussions After Patching Oracle WebCenter Portal"

- Section 2.2.4.2, "Problem Using WebCenter Portal Customizations with .jsp Pages"

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

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

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

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

- Section 2.2.4.7, "Patches Required After Updating Oracle WebCenter Portal"

2.2.4.1 Configuring Additional Crawl Sources for Discussions After Patching Oracle WebCenter Portal

After patching Oracle WebCenter Portal to the latest release, you must configure two additional crawl sources for discussions that reference the MESSAGECRAWLER_VW and THREADCRAWLER_VW views. Once configured, Oracle SES can crawl topics and replies in discussions forums as well as forums (FORUMCRAWLER_VW). The latest release uses three separate crawl sources so that users can see search results for forums without also seeing results for all the messages and replies in it.

For information, see "Setting Up Oracle SES to Search Discussions and Announcements" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

2.2.4.2 Problem Using WebCenter Portal Customizations with .jsp Pages

In Oracle WebCenter Portal 11g Release 1 (11.1.1.2.0) or Release 1 (11.1.1.3.0), if you extended WebCenter Portal (previously called WebCenter Spaces) 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 the latest release of Oracle WebCenter Portal, custom portal templates will not render if they use .jsp pages.

2.2.4.3 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.4.4 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 Oracle WebCenter Portal 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.4.5 Personalization Settings in Activity Graph Task Flows Lost When Oracle 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 Oracle WebCenter Portal to the latest release. You must make all the personalization settings again for your Activity Graph task flows as required.

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

If you extended WebCenter Portal (previously called WebCenter Spaces) to add support for a new language, you may encounter problems working with the language after you patch your Oracle WebCenter Portal instance. The language may not display in the default list of languages offered in WebCenter Portal. To work around this issue, you must re-upload the supported-languages.xml file containing the entry for the required language.

2.2.4.7 Patches Required After Updating Oracle WebCenter Portal

After you patch Oracle WebCenter Portal, you can apply the following one-off patches available on My Oracle Support to address specific known issues:

- Patch 16908144
This patch addresses a problem where Portal Framework applications generate an error and cannot be run when you are using the updated WebCenter Portal JDeveloper Extension.

- Patch 16757223
This patch improves the performance of WebCenter Portal applications.

- Patch 16743904
This patch addresses issues with Portal Framework applications that take advantage of Metadata Services (MDS).

2.2.5 Issues Pertaining to Patching Oracle Identity Management

This section contains the following:

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

- Section 2.2.5.2, "Installer Prompts for OID Privileged Ports Twice During the Patch Installation"

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

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

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

- Section 2.2.5.6, "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.5.7, "Harmless Error When Running the upgradeOpss() Command When Upgrading Oracle Identity Management"

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

- Section 2.2.5.9, "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.5.10, "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.5.11, "Harmless Exception Seen When Starting Oracle Identity Management Server 11g Release 1 (11.1.1.5.0)"

2.2.5.1 Access Denied When Running the oimPS1PS2upgrade Script

If you are upgrading Oracle Identity Management and need to run the oimPS1PS2upgrade.sh 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.5.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.5.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 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.5.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.sh 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.5.5 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.5.6 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.5.7 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.5.8 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.5.9 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.5.10 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.5.11 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.6 Issues Pertaining to Patching System Components

This section contains the following:

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

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

- Section 2.2.6.3, "Setting Execute Permissions for emctl When Migrating System Components"

2.2.6.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 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.6.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.6.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.7 Issues Pertaining to Version Numbers After Patching

This section contains the following:

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

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

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

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

2.2.7.1 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.7.2 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.7.3 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.7.4 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 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.8 Issues Pertaining to Displays During or After Patching

This section contains the following:

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

2.2.8.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 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.9 Warning and Error Messages Seen as a Result of Patching

This section contains the following:

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

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

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

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

2.2.9.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.9.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.9.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 directory.

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

2.2.9.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.10 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.11 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.12 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.10, "Oracle WebCenter Portal wc-post-install.py Script Not Supported for Oracle RAC Datasources"

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

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

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

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

- Section 2.3.15, "Oracle Fusion Middleware Configuration Fails"

2.3.1 Issues Pertaining to Oracle SOA Suite Configuration

This section contains the following:

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

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

2.3.1.1 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.2 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.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, "Password Requirements for Oracle Internet Directory Administrator"

- Section 2.3.2.6, "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 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 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.6 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)

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

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

- Section 2.3.4.3, "Some Text Truncated on the "Server Start Mode and JDK Configuration" Screen"

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.4.3 Some Text Truncated on the "Server Start Mode and JDK Configuration" Screen

If you run the Oracle Fusion Middleware Configuration Wizard on an AIX 64-bit system, the Graphics Manager on that system will cause some text to be truncated on the "Server Start Mode and JDK Configuration" screen.

There is no work around for this issue.

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.sh and unpack.sh scripts in their respective ORACLE_HOME/common/bin directories.

The pack.sh 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.sh 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.sh and unpack.sh 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.sh 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 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 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 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.11 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.12 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.13 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 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.14 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.15 Oracle Fusion Middleware Configuration Fails

The Oracle Fusion Middleware 11g Release 1 (11.1.1.7.0) configuration on Oracle Solaris on SPARC (64-bit) fails while running the was_config.sh script and displays the following error message:

/scratch/aime/11GPS6/oracle_common/common/bin/was_config.sh:
WAS_HOME=/scratch/aime/IBM/WebSphere/AppServer: is not an identifier.

Complete the following steps for a workaround:

1. Start the Oracle Fusion Middleware configuration.

2. Open the /scratch/aime/11GPS6/oracle_common/common/bin/setWasHome.sh file.

3. Set the value for the WAS_HOME environment variable as follows:

WAS_HOME=${WAS_HOME:-/scratch/aime/IBM/WebSphere/AppServer}

4. Export the WAS_HOME environment variable as shown:

export  WAS_HOME

5. Run the was_config.sh script.

2.4 Known Issues

This section describes known issues. It includes the following topics:

- Section 2.4.1, "Oracle Universal Installer Lists Errors While Checking For Required Operating System Patches On Solaris 10"

- Section 2.4.2, "Forms and Reports Builder Not Supported"

- Section 2.4.3, "Failure to Start a 64-bit JVM Process on Oracle Solaris on SPARC (64-bit)"

2.4.1 Oracle Universal Installer Lists Errors While Checking For Required Operating System Patches On Solaris 10

When the Oracle Universal Installer (OUI) checks for Solaris operating system patches 127111-02 and 137111-04 on Solaris 10, OUI lists failures even if superseding patches exist on the server. If superseding patches exist, these errors can be safely ignored. Following is an example of checking if a patch that supersedes patch 127111-02 is installed on the server:

showrev -p | grep 127111

If this line returns a superseding patch, the OUI error can be safely ignored and the installation can continue.

2.4.2 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.4.3 Failure to Start a 64-bit JVM Process on Oracle Solaris on SPARC (64-bit)

While installing Oracle Fusion Middleware 11g on Oracle Solaris on SPARC (64-bit), it shows failed to start a 64-bit JVM process error.

It displays an error trying to execute the following:

/home/ora_admin/JDK/jdk1.6.0_20/bin/sparcv9/java

This occurs as the Java executable is a 32-bit version of JVM rather than the expected 64-bit version.

Workaround

On Oracle Solaris on SPARC (64-bit), a 64-bit JDK installation is successful after the initial installation of 32-bit version, followed by a 64-bit installation into that base installation to provide the additional 64-bit libraries.

Thus, perform the following steps to work around this issue:

1. Install 32-bit JDK by following the steps documented at:

http://www.java.com/en/download/help/5000010600.xml

2. Install the supplemental files for 64-bit support by following the 64-bit installation instructions at:

http://www.java.com/en/download/help/5000010700.xml

3. Finally, proceed with the installation of Oracle Weblogic Server.

For more information, see Java Platform, Standard Edition 6 Update Release Notes.

2.5 Documentation Errata

This section describes documentation errata. It includes the following topics:

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

- Section 2.5.3, "Incorrect Command Specified for Adding the AttributeAccessPermission Grant after Patching Oracle WebCenter Portal"

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

2.5.3 Incorrect Command Specified for Adding the AttributeAccessPermission Grant after Patching Oracle WebCenter Portal

In Oracle Fusion Middleware Patching Guide, in the "Verifying SSOFilter Grant" section, the WLST command for adding the AttributeAccessPermission grant is incorrect. The following is the correct WLST command:

grantPermission(codeBaseURL='file:${common.components.home}/modules/oracle.ssofilter_11.1.1/ssofilter.jar',
permClass='oracle.security.jps.service.attribute.AttributeAccessPermission',
permTarget='*', permActions='get,set,remove')

3 Upgrade

This chapter describes issues associated with upgrading your environment and your applications to Oracle Fusion Middleware 11g. It includes the following topics:

Note:

This feature is not supported on Oracle Solaris on x86-64 (64-Bit).

- 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, "Upgrade Assistant Fails While Restarting OPMN Managed Processes After Oracle Identity Federation Upgrade"

- Section 3.1.10, "Problem Accessing the Welcome Pages in Oracle HTTP Server After Upgrade"

- Section 3.1.11, "Misleading Error Message When Upgrading Oracle Internet Directory"

- Section 3.1.12, "Additional Steps Required When Redeploying the SOA Order Booking Sample Application on Oracle Fusion Middleware 11g"

- Section 3.1.13, "Additional Steps Required When Upgrading Human Taskflow Projects"

- Section 3.1.14, "Stopping Oracle Virtual Directory Processes During Upgrade"

- Section 3.1.15, "Providing Input to Upgrade Assistant Screens When Oracle Internet Directory Upgrade Fails"

- Section 3.1.16, "Upgrading Oracle Access Manager Middle Tier"

- Section 3.1.17, "Inaccurate Results When Running the Upgrade Assistant Verify Feature"

- Section 3.1.18, "Missing jdk_version.log File When Launching Upgrade Assistant"

- Section 3.1.19, "Test Suites in Oracle SOA Suite 10g Projects Not Upgraded to 11g"

- Section 3.1.20, "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)"

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, and ADF

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

Section 42.4, "Interoperability Issues and Workarounds"

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, 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, 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.2 Unable to Read Composite Model Error During SOA Application Upgrade

The Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, 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.7, "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 sucessful, 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, and ADF.

3.1.9 Upgrade Assistant Fails While Restarting OPMN Managed Processes After Oracle Identity Federation Upgrade

Upgrade Assistant Fails while restarting Oracle HTTP Server (OHS) for Oracle Instance. The following error is seen on using the opmnctl startall command:

Process (index=1,uid=994650225,pid=11673) failed to start a managed process after the maximum retry limit.

Oracle HTTP Server does not start by opmnctl, as the OHS log file

/scratch/aime/bea_idmupg_rc2/asinst_1/diagnostics/logs/OHS/ohs1/console~OHS~1.log

Displays the message "Could not resolve address '255.255.255.255' -- check resolver configuration".

There are three ways to workaround Oracle HTTP Server startup failure. They are as follows:

- Modify the ORACLE_INSTANCE/config/OHS/component_name/ssl.conf file by replacing Virtualhost (_default_) with Virtualhost (*). Then restart the OHS using opmnctl.

- Disable the "name-service-cache". As a root user execute the following steps to disable:

# /usr/sbin/svcadm disable svc:/system/name-service-cache
# svcs svc:/system/name-service-cache.

Repeat the installation or upgradation process once the "name-service-cache" is disabled.

- Upgrade to Solaris 10 update 5 and above. After the upgrade, repeat the installation or upgradation process.

3.1.10 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.11 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.12 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, 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, 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.13 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.14 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.15 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.16 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.17 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.18 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.19 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, and ADF

- "Automating Testing of SOA Composite Applications" in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite

3.1.20 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, "Patching the Schema for Oracle Internet Directory"

- Section 3.2.3, "Changing the patchmaster.ValidationErrorContinue Property"

- Section 3.2.4, "Changing the Default Setting for Validation Tasks"

- Section 3.2.5, "Severe Error When Running the execute-sql-rcu Macro"

- Section 3.2.6, "Machine Names Do Not Appear in the Oracle WebLogic Server Administration Console"

- Section 3.2.7, "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 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.3 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.4 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.5 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.6 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.7 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.7.1, "Configuring the Oracle BAM 11g Samples After Migrating from 11.1.1.1.0"

- Section 3.2.7.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.7.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.7.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:

Note:

This feature is not supported on Oracle Solaris on x86-64 (64-Bit).

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

- 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, as described in Section 28.2.6.

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:

Note:

This feature is not supported on Oracle Solaris on x86-64 (64-Bit).

- 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, "Display Problems When Running JDK 160_18 on Intel Systems that Support the SSE4.2 Instruction Set"

- Section 5.1.11, "Adobe Flash Plugin Required When Displaying Fusion Middleware Control in the Apple Safari Browser"

- Section 5.1.12, "Unable to Access Fusion Middleware Control After Installing the Oracle Identity Management 11.1.1.4.0 Patch Set"

- Section 5.1.13, "Error Message on Deleting the Shared Folder After Scale-Out"

- Section 5.1.14, "Coreapplication Process for Oracle Business Intelligence Reported as Down in Fusion Middleware Control"

- Section 5.1.15, "Online Help Error Message in Enterprise Manager Log Files Can Be Ignored"

- Section 5.1.16, "Incorrect or Missing Metrics Help Information"

- Section 5.1.17, "Error When Accessing the Entry Point URL for the NonJ2EEManagement Internal Application"

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

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, Enteprise 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 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

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/

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.11 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.12 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.13 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.14 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.15 Online Help Error Message in Enterprise Manager Log Files Can Be Ignored

When acessing 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.16 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.17 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 facilicate 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:

Note:

This feature is not supported on Oracle Solaris on x86-64 (64-Bit).

- 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 informationon 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 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:

Note:

This feature is not supported on Oracle Solaris on x86-64 (64-Bit).

- Section 7.1, "General Issues and Workarounds"

- Section 7.2, "Configuration Issues and Workarounds"

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

7.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topics:

- Section 7.1.1, "Log File Error Message when Starting the SOA Server"

- Section 7.1.2, "Save Settings Button Under Accessibility User Preferences Has Incorrect Label"

- Section 7.1.4, "Cannot Create an XA Connection Factory in the IBM WebSphere Administration Console"

- Section 7.1.5, "Accessibility Mode for User Messaging Preferences is Ignored on an IBM WebSphere Application Server"

- Section 7.1.6, "Adding Shared Libraries to Deploy a Task Form from Oracle JDeveloper"

- Section 7.1.7, "Setting Cookie Paths for Oracle SOA Suite Applications"

- Section 7.1.8, "Deploying a SOA Composite Application to a SOA Cluster"

- Section 7.1.9, "Cannot Deploy a SOA Bundle File from Oracle Enterprise Manager Fusion Middleware Control"

- Section 7.1.10, "One-and-Only-One Event Subscriptions Are Not Supported"

- Section 7.1.11, "Deployed Task Form Startup Failure in IBM WebSphere Administration Console"

- Section 7.1.12, "Oracle BPM Worklist Displays as Undefined in Administration Console"

- Section 7.1.13, "Dashboard Tab May Display Completed SOA Composite Instance States as Running"

- Section 7.1.14, "Two-Way SSL Configuration with Oracle SOA Suite Is Not Supported"

- Section 7.1.15, "Multiple Fault Recovery Failure with the Recover With Options Dialog"

- Section 7.1.16, "IBM WebSphere Application Server - ND Installation Requires a Server Restart"

- Section 7.1.17, "Test Emulations of Asynchronous BPEL Processes Fail"

- Section 7.1.18, "SETMANAGEDCONNECTION() Fails with ILLEGALSTATEEXCEPTION for the AQ Adapter"

- Section 7.1.19, "Invalid PolicySet Error When Accessing a Deployed Oracle Fusion Middleware Application on IBM WebSphere"

- Section 7.1.20, "Cannot Stop or Start Oracle Internal Applications From Fusion Middleware Control on IBM WebSphere"

- Section 7.1.21, "For the JMS Adapter, Instances Become Recoverable Even Without Failover"

- Section 7.1.22, "Kerberos and SPNEGO are not supported with Oracle WSM"

- Section 7.1.23, "REST Security Policies and Templates Not Certified"

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

7.1.23 REST Security Policies and Templates Not Certified

The current release of REST security policies and templates are not certified on IBM WebSphere.

7.2 Configuration Issues and Workarounds

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

- Section 7.2.1, "Error Configuring a Cell When IBM WebSphere Installed on Windows 2003 and 2008"

- Section 7.2.2, "Configuring Coherence for a SOA Cluster on IBM WebSphere"

- Section 7.2.3, "Limitations When Configuring Oracle Business Activity Monitoring for High Availability on IBM WebSphere"

- Section 7.2.4, "Requests Received by IBM HTTP Server (IHS) Are Routed to the Fusion Middleware Welcome Page"

- Section 7.2.5, "Unable to Register WSRP/JPDK Producers Through Pagelet Producer Console on IBM WebSphere"

- Section 7.2.6, "Unable to Configure Password Settings Through Pagelet Producer Console on IBM WebSphere"

- Section 7.2.7, "Restart of Deployment Manager Required When Configuring Oracle SOA Suite for High Availability on IBM WebSphere"

- Section 7.2.8, "Additional Configurations For SSO Logout on WebSphere"

- Section 7.2.9, "java.lang.ClassNotFoundException Error Message seen in the Log File When Deploying SimpleApprovalTaskFlow on IBM WebSphere"

- Section 7.2.10, "Oracle Fusion Middleware Configuration Fails on IBM WebSphere"

- Section 7.2.11, "Domain Creation Fails During the Oracle Data Integrator Configuration on IBM WebSphere"

- Section 7.2.12, "OutofMemory Error Appears During the Oracle Data Integrator Configuration on IBM WebSphere"

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

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

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

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

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

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

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

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

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

7.2.10 Oracle Fusion Middleware Configuration Fails on IBM WebSphere

While configuring Oracle Fusion Middleware 11g Release 1 (11.1.1.7.0) on IBM WebSphere, the configuration fails while running the ORACLE_HOME/common/bin/wsadmin.sh script and displays the following error message:

Error Message : "./wsadmin.sh: test: argument expected"

To workaround this issue, complete the following steps:

1. Open the ORACLE_HOME/common/bin/setWsadminEnv.sh file.

2. In the setWsadminEnv.sh file, add quotation marks (" ") to the $WSADMIN_SCRIPT_LIBRARIES variable in the if [ ! $WSADMIN_SCRIPT_LIBRARIES]; then statement as follows:

if [ ! "${WSADMIN_SCRIPT_LIBRARIES}" ]; then

3. Run the ORACLE_HOME/common/bin/wsadmin.sh script.

7.2.11 Domain Creation Fails During the Oracle Data Integrator Configuration on IBM WebSphere

Impacted Releases: 11.1.1.7.0

The creation of a domain fails while running the was_config.sh script when JRF templates are applied during the Oracle Data Integrator domain configuration on IBM WebSphere. The following error message is displayed:

ArrayIndexOutOfBoundsException

Also, the following error messages are seen in the wsadmin.traceout log file:

[11/12/12 6:54:40:432 UTC] 0000000a AbstractShell A   WASX7487E: Failed to import script libraries modules:
MW_HOME/oracle_common/common/wsadmin/ADFShareHelperWSAdmin.py;
com.ibm.bsf.BSFException: exception from Jython:
[11/12/12 6:54:41:156 UTC] 0000000a AbstractShell A   WASX7487E: Failed to import script libraries modules:
MW_HOME/oracle_common/common/wsadmin/wsmManage.py;
com.ibm.bsf.BSFException: exception from Jython:

Complete the following steps for a workaround:

1. Create a new profile through the Domain Configuration Wizard by completing the steps provided in Oracle Fusion Middleware Configuration Guide for IBM WebSphere Application Server.

2. Select Oracle Data Integrator templates and complete the Oracle Data Integrator domain configuration.

7.2.12 OutofMemory Error Appears During the Oracle Data Integrator Configuration on IBM WebSphere

Impacted Releases: 11.1.1.7.0

Domain creation may fail with the OutofMemory error while running the was_config.sh script during the Oracle Data Integrator domain configuration on IBM WebSphere.

Complete the following steps for a workaround:

1. Modify the $WAS_HOME/bin/wsadmin.sh script by completing the steps provided in the following website:
http://www-01.ibm.com/support/docview.wss?uid=swg1PK70783

2. Run the was_config.sh.

7.3 Documentation Errata

This section describes documentation errata. It includes the following topic:

- Section 7.3.1, "Updates to Steps for Patching WebCenter Portal 11.1.1.6.0 Installations to 11.1.1.7.0"

- Section 7.3.2, "Updates to Steps for Configuring Oracle Business Intelligence for Scaling Out on IBM WebSphere"

- Section 7.3.3, "Updates to Section on Upgrading"

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

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

7.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 you have a previous 11g Release of Oracle Business Intelligence that is running on Oracle WebLogic Server.

Part II

Oracle Development Tools

Part II contains the following chapters:

- Chapter 8, "Oracle JDeveloper and Oracle Application Development Framework (ADF)"

- Chapter 9, "Oracle TopLink"

8 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/index-101256.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.

9 Oracle TopLink

This chapter describes issues associated with Oracle TopLink. It includes the following topics:

Note:

This tool is not supported on Oracle Solaris on x86-64 (64-Bit).

- Section 9.1, "General Issues and Workarounds"

9.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topic:

- Section 9.1.1, "TopLink Object-Relational Issues"

- Section 9.1.2, "TopLink Workbench Issues"

- Section 9.1.3, "Oracle Database Extensions with TopLink"

- Section 9.1.4, "Allowing Zero Value Primary Keys"

- Section 9.1.5, "Managed Servers on Sybase with JCA Oracle Database Service"

- Section 9.1.6, "Logging Configuration with EclipseLink Using Container Managed JPA"

- Section 9.1.7, "Grid Cache requires CacheLoader"

9.1.1 TopLink Object-Relational Issues

This section contains information on the following issues:

- Section 9.1.1.1, "Cannot set EclipseLink log level in WLS System MBean Browser"

- Section 9.1.1.2, "Incorrect outer join SQL on SQLServer2005"

- Section 9.1.1.3, "UnitOfWork.release() not Supported with External Transaction Control"

- Section 9.1.1.4, "Returning Policy for UPDATE with Optimistic Locking"

- Section 9.1.1.5, "JDBC Drivers returning Timestamps as Strings"

- Section 9.1.1.6, "Unit of Work does not add Deleted Objects to Change Set"

9.1.1.1 Cannot set EclipseLink log level in WLS System MBean Browser

Use Oracle Enterprise Manager to set the EclipseLink log level; do not use the WLS System MBean Browser to complete this action.

9.1.1.2 Incorrect outer join SQL on SQLServer2005

TopLink generates incorrect outer join for SQL Server v2005. The outer join syntax generated is correct for earlier versions of this database. To work around this limitation, reconfigure the database compatibility (refer to the SQLServer documentation for details). Alternatively, you can use a custom TopLink database platform.

9.1.1.3 UnitOfWork.release() not Supported with External Transaction Control

A unit of work synchronized with a Java Transaction API (JTA) will throw an exception if it is released. If the current transaction requires its changes to not be persisted, the JTA transaction must be rolled back.

When in a container-demarcated transaction, call setRollbackOnly() on the EJB/session context:

@Stateless
public class MySessionBean
{    @Resource
SessionContext sc;

public void someMethod()
{
...
sc.setRollbackOnly();
}
}

When in a bean-demarcated transaction then you call rollback() on the UserTransaction obtained from the EJB/session context:

@Stateless
@TransactionManagement(TransactionManagementType.BEAN)
public class MySessionBean implements SomeInterface
{
@Resource
SessionContext sc;

public void someMethod()
{
sc.getUserTransaction().begin();
...
sc.getUserTransaction().rollback();
}
}

9.1.1.4 Returning Policy for UPDATE with Optimistic Locking

The returning policy, which allows values modified during INSERT and UPDATE to be returned and populated in cached objects, does not work in conjunction with numeric version optimistic locking for UPDATE. The value returned for all UPDATE operations is 1 and does not provide meaningful locking protection.

Do not use a returning policy for UPDATE in conjunction with numeric optimistic locking.

The use of returning policy for INSERT when using optimistic locking works correctly.

9.1.1.5 JDBC Drivers returning Timestamps as Strings

TopLink assumes that date and time information returned from the server will use Timestamp. If the JDBC driver returns a String for the current date, TopLink will throw an exception. This is the case when using a DB2 JDBC driver.

To work around this issue, consider using a driver that returns Timestamp (such as COM.ibm.db2.jdbc.app.DB2Driver) or change the policy to use local time instead of server time.

Another option is to use a query re-director on the ValueReadQuery used by the platform:

ValueReadQuery vrq = new ValueReadQuery(
"SELECT to_char(sysdate, 'YYYY-MM-DD HH:MM:SS.SSSSS') FROM DUAL"
);
vrq.setRedirector(new TSQueryRedirector());
...
class TSQueryRedirector implements QueryRedirector
{
public Object invokeQuery(DatabaseQuery query, Record arguments, Session session)
{
String value = (String)session.executeQuery(query);
return ConversionManager.getDefaultManager().convertObject(
value, java.sql.Timestamp.class
);
}
}

9.1.1.6 Unit of Work does not add Deleted Objects to Change Set

When accessing the change set of a Unit of Work to determine what has changed, objects that are pending deletion (such as uow.deleteObject( ) and uow.deleteAllObjects( )) will not be returned from the result set.

The objects pending deletion are only available through the Unit of Work getDeletedObjects call.

9.1.2 TopLink Workbench Issues

This section contains information on the following issues:

- Section 9.1.2.1, "User Interface Issue"

- Section 9.1.2.2, "Accessibility"

- Section 9.1.2.3, "Running the TopLink Workbench on Windows OS"

9.1.2.1 User Interface Issue

When running TopLink Mapping Workbench using JDK 1.7, dialogs with a group box containing check boxes or radio buttons may display duplicated or truncated group box titles. There is no loss of functionality, and you should proceed as usual.

9.1.2.2 Accessibility

Due to an issue with Sun JDK 1.6, if NullPointExecption error dialog is generated when saving a file, the error dialog window is not in focus.

9.1.2.3 Running the TopLink Workbench on Windows OS

Due to an issue with certain configurations and versions of Windows operating systems, users that launch the TopLink Workbench with the workbench.cmd file may receive a dialog that states: Could not find the main class. This occurs because the classpath specified contains a directory path which has periods in it. The workaround is to rename the offending directory or change the classpath to use directory paths which do not contain periods.

9.1.3 Oracle Database Extensions with TopLink

This section contains information on the following issue:

- Section 9.1.3.1, "Template JAR for Spatial and XDB Support in Oracle WebLogic Server"

9.1.3.1 Template JAR for Spatial and XDB Support in Oracle WebLogic Server

To fully support Oracle Spatial and Oracle XDB mapping capabilities (in both standalone Oracle WebLogic Server and the Oracle JDeveloper integrated WebLogic Server), you must use the toplink-spatial-template.jar and toplink-xdb-template.jar to extend the WebLogic Server domain to support Oracle Spatial and XDB, respectively.

To extend your WebLogic Server domain:

1. Download the toplink-spatial-template.jar (to support Oracle Spatial) and toplink-xdb-template.jar (to support Oracle XDB) files from:

- http://download.oracle.com/otn/java/toplink/111110/toplink-spatial-template.jar

- http://download.oracle.com/otn/java/toplink/111110/toplink-xdb-template.jar

2. Use Table 9-1, "To Support Oracle Spatial" or Table 9-2, "To Support Oracle XDB" to determine which files to copy.

Table 9-1 To Support Oracle Spatial

Copy this file

From...Foot 1

To...Foot 2

sdoapi.jar

<ORACLE_DATABASE_HOME>/md/jlib

<WEBLOGIC_HOME>/server/lib

Footnote 1 These are the default locations. Your actual location may vary depending on your specific environment, installed options, and version.

Footnote 2 When using Oracle JDeveloper integrated WebLogic Server, the <WEBLOGIC_HOME> is located within the <JDEVELOPER_HOME> directory.

Table 9-2 To Support Oracle XDB

Copy this file

From...Foot 1

To...Foot 2

xdb.jar

<ORACLE_DATABASE_HOME>/rdbms/jlib

<WEBLOGIC_HOME>/server/lib

xml.jar

<ORACLE_DATABASE_HOME>/lib

<WEBLOGIC_HOME>/server/lib

xmlparserv2.jar

<ORACLE_DATABASE_HOME>/lib

<WEBLOGIC_HOME>/server/lib

ori18n-mapping.jarFoot 3

<ORACLE_DATABASE_HOME>/jlib

<WEBLOGIC_HOME>/server/lib

Footnote 1 These are the default locations. Your actual location may vary depending on your specific environment, installed options, and version.

Footnote 2 When using Oracle JDeveloper integrated WebLogic Server, the <WEBLOGIC_HOME> is located within the <JDEVELOPER_HOME> directory.

Footnote 3 Use orai18n-mapping.jar for Oracle Database 11.2 and higher.

Note:

Although the actual JAR file may be named differently in your From directory, the file must be named as shown, when copied to the To directory.

3. Launch the Config Wizard (<WEBLOGIC_HOME>/common/bin/config.sh (or .bat).

4. Select Extend an existing WebLogic domain.

5. Browse and select your WebLogic Server domain.
When using JDeveloper with integrated WebLogic Server, the typical WebLogic Server domain location may be similar to:

- In Windows environments: %APPDATA%\JDeveloper\systemXX.XX.XX.XX\DefaultDomain
where XX.XX.XX.XX is the unique number of the product build.

For Windows platforms, you must enable the Show hidden files and folders folder option.

- In non-Windows environments, the default location is under the current user's default home directory: <$Home>/DefaultDomain

Refer to the Oracle JDeveloper documentation for details.

6. Select Extend my domain using an existing extension template.

7. Browse and select the required template JAR (toplink-spatial-template.jar for Oracle Spatial, toplink-xdb-template.jar for Oracle XDB).

8. Complete the remaining pages of the wizard.

9.1.4 Allowing Zero Value Primary Keys

By default, EclipseLink interprets zero as null for primitive types that cannot be null (such as int and long) causing zero to be an invalid value for primary keys. You can modify this setting by using the allow-zero-id property in the persistence.xml file. Valid values are:

- true – EclipseLink interprets zero values as zero. This permits primary keys to use a value of zero.

- false (default) – EclipseLink interprets zero as null.

Refer the EclipseLink User's Guide at http://wiki.eclipse.org/EclipseLink/UserGuide for more information.

9.1.5 Managed Servers on Sybase with JCA Oracle Database Service

When using a JCA service with the Oracle Database adapter in a cluster to perform database operations on a Sybase database, the managed nodes in the cluster process the messages and may attempt to perform duplicate operations.

Because supported versions of Sybase do not support Oracle TopLink record locking, Sybase allows the duplicate operation attempts.

9.1.6 Logging Configuration with EclipseLink Using Container Managed JPA

By default, EclipseLink users in container managed JPA will use the Oracle WebLogic Server logging options to report all log messages generated by EclipseLink. Refer to "Configuring WebLogic Logging Services" in Oracle® Fusion Middleware Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server.

To use the EclipseLink native logging configuration, add the following property to your persistence.xml file:

<property name="eclipselink.logging.logger" value="DefaultLogger"/>

9.1.7 Grid Cache requires CacheLoader

An oracle.eclipselink.coherence.integrated.EclipseLinkJPACacheLoader must be configured for entities configured as Grid Cache to ensure the necessary TopLink Grid wrapper class is generated.

Part III

Web Tier

Part III contains the following chapters:

- Chapter 10, "Oracle HTTP Server"

- Chapter 11, "Oracle Web Cache"

10 Oracle HTTP Server

This chapter describes issues and release-specific user information associated with Oracle HTTP Server. It includes the following notes:

- Section 10.1, "mod_security Reintroduced"

- Section 10.2, "Installing OHS 11.1.1.7 with WLS 12g"

10.1 mod_security Reintroduced

The mod_security plug-in was removed from earlier versions of Oracle HTTP Server but is reintroduced in version 11.1.1.7. This version follows the recommendations and practices prescribed for open source mod_security 2.6.2. Only documentation applicable to open source Apache mod_security 2.6.2 is applicable to the Oracle HTTP Server implementation of the module.

10.2 Installing OHS 11.1.1.7 with WLS 12g

You can install Oracle HTTP Server 11.1.17 with the Oracle WebLogic Server 12c JRF/ADF combination if you do the following:

- Install the two components separately, from scratch, and choose the correct versions (Oracle HTTP Server 11.1.17 with Oracle WebLogic Server 12c JRF/ADF)

- During the OHS 11g installation, deselect the components associated with a WebLogic Domain.

11 Oracle Web Cache

This chapter describes issues associated with Oracle Web Cache. It includes the following topics:

- Section 11.1, "Configuration Issues and Workarounds"

- Section 11.2, "Documentation Errata"

11.1 Configuration Issues and Workarounds

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

- Section 11.1.1, "Reset the Random Password Generated When Installing Oracle Portal, Forms, Reports, and Discoverer"

- Section 11.1.2, "Running Oracle Web Cache Processes as a Different User Is Not Supported"

- Section 11.1.3, "Using Web Cache in an IPv6 Network"

11.1.1 Reset the Random Password Generated When Installing Oracle Portal, Forms, Reports, and Discoverer

For enhanced security, no default hard-coded passwords are used for managing Oracle Web Cache.

When you install the Oracle Web Tier installation type, the Oracle Universal Installer prompts you to choose a password. The Web Cache Administrator page of the Oracle Universal Installer prompts you to enter a password for the administrator account. The administrator account is the Oracle Web Cache administrator authorized to log in to Oracle Web Cache Manager and make configuration changes through that interface.

When you install Oracle Portal, Forms, Reports, and Discoverer, the prompt for the administrator password is missing. Instead, the Oracle Portal, Forms, Reports and Discoverer install type uses a random value chosen at install time.

Regardless of the installation type, before you begin configuration, change the passwords for these accounts to a secure password. If you are configuring a cache cluster, all members of the cluster must use the same password for the administrator account.

To change the password, use the Passwords page of Fusion Middleware Control, as described in "Configuring Password Security" in the Oracle Fusion Middleware Administrator's Guide for Oracle Web Cache.

11.1.2 Running Oracle Web Cache Processes as a Different User Is Not Supported

Running Oracle Web Cache as a user other than the installed user through the use of the webcache_setuser.sh setidentity command is not supported.

Specifically, you cannot change the user ID with the following sequence:

1. Change the process identity of the Oracle Web Cache processes in the Process Identity page using Oracle Web Cache Manager (Properties > Process Identity).

2. Use the webcache_setuser.sh script as follows to change file and directory ownership:

webcache_setuser.sh setidentity user_ID

user_ID is the user you specified in the User ID field of the Process Identity page.

3. Restart Oracle Web Cache using opmnctl.
Oracle Web Cache will start and then immediately shut down.

In addition, messages similar to the following are displayed in the event log:

[2009-06-02T21:22:46+00:00] [webcache] [ERROR:1] [WXE-13212] [logging] [ecid: ]
Access log file /scratch/webtier/home/instances/instance1/diagnostics/logs/WebCache/webcache1/access_log could not be opened.
[2009-06-02T21:22:46+00:00] [webcache] [WARNING:1] [WXE-13310] [io] [ecid: ]
Problem opening file /scratch/webtier/home/instances/instance1/config/WebCache/webcache1/webcache.pid (Access Denied).
[2009-06-02T21:22:46+00:00] [webcache] [ERROR:1] [WXE-11985] [esi] [ecid: ]
Oracle Web Cache is unable to obtain the size of the default ESI fragment page
/scratch/webtier/home/instances/instance1/config/WebCache/webcache1/files/esi_fragment_error.txt.
[2009-06-02T21:22:46+00:00] [webcache] [WARNING:1] [WXE-11905] [security]
[ecid: ] SSL additional information: The system could not open the specified file.

For more information about the webcache_setuser.sh script, see "Running webcached with Root Privilege" in the Oracle Fusion Middleware Administrator's Guide for Oracle Web Cache.

11.1.3 Using Web Cache in an IPv6 Network

Oracle Web cache supports the IPv6 address family by default. However, before using IPv6, you must ensure that IPv6 support is enabled in the operating system. This issue is not applicable for IPv4-only systems and for systems that support IPv6 at the kernel level.

11.2 Documentation Errata

This section provides clarifications for errors in Oracle Web Cache documentation. It includes the following topics:

- Section 11.2.1, "Procedure to Enable Generation of Core Dump"

- Section 11.2.2, "Clarification About Support for CRLs"

- Section 11.2.3, "Clarifications About Configuring the CRL Location"

11.2.1 Procedure to Enable Generation of Core Dump

Information about enabling generation of core dump is not available in the Oracle Fusion Middleware Administrator's Guide for Oracle Web Cache.

To enable generation of a core dump when Oracle Web Cache is shut down, add CORE="YES" to the TRACEDUMP element in the $INSTANCE_HOME/config/WebCache/webcache_name/webcache.xml file.

The updated TRACEDUMP element would look like the following:

<TRACEDUMP FILENAME=file_name CORE="YES"/>

The core dump file with the specified name is created in the $INSTANCE_HOME/config/WebCache/webcache_name directory.

11.2.2 Clarification About Support for CRLs

Section 5.1.1.2.2, "Certificate" of the Oracle Fusion Middleware Administrator's Guide for Oracle Web Cache states the following:

"Although the Oracle HTTP Server supports OpenSSL certificate revocation lists, Oracle Web Cache does not."

This statement is incorrect. Oracle Web Cache does support CRLs.

11.2.3 Clarifications About Configuring the CRL Location

Section 5.5.3, "Configuring Certificate Revocation Lists (CRLs)" of the Oracle Fusion Middleware Administrator's Guide for Oracle Web Cache has the following incorrect statements:

- Incorrect statement: "Fusion Middleware Control or Oracle Web Cache Manager do not provide support for client certificate validation with Certificate Revocation Lists (CRLs). You can configure this support by manually editing the webcache.xml file."
Clarification: This statement is incorrect. You can enable and configure support for CRLs by using the Oracle Web Cache Manager, as follows:

1. Go to the Listen Ports page.

2. Select the HTTPS port for which you want to configure CRL settings, and click Edit Selected.
The Edit/Add Listen Port dialog box is displayed.

3. Select the Certificate Revocation List Enabled option.

4. In the CRL Path field, specify the fully qualified path to the directory in which the CRLs are stored. For example, /home/crl.

5. In the CRL File field, specify the fully qualified path and filename of the CRL file. For example, /home/oracle/crl/CA/crl.

- Incorrect statement: Step 4 of the procedure to configure certificate validation using CRLs: "Configure CRL file location by adding the SSLCRLPATH and SSLCRLFILE parameters to the HTTPS LISTEN directive."
Clarification: This statement is incorrect. You must add either SSLCRLPATH or SSLCRLFILE to the HTTPS LISTEN directive, not both.

Part IV

Oracle WebLogic Server

Part IV contains the following chapters:

- Chapter 12, "Oracle WebLogic Server"

12 Oracle WebLogic Server

This chapter describes issues associated with Oracle WebLogic Server. It includes the following topics:

- Section 12.1, "General Issues and Workarounds"

- Section 12.2, "Administration Console Issues and Workarounds"

- Section 12.3, "Apache Beehive Support Issues and Workarounds"

- Section 12.4, "Clustering Issues and Workarounds"

- Section 12.5, "Configuration Issues and Workarounds"

- Section 12.6, "Connector (Resource Adapter) Issues and Workarounds"

- Section 12.7, "Console Extensions Issues and Workarounds"

- Section 12.8, "Core Server and Core Work Manager Issues and Workarounds"

- Section 12.9, "Deployment Issues and Workarounds"

- Section 12.10, "EJB Issues and Workarounds"

- Section 12.11, "Examples Issues and Workarounds"

- Section 12.12, "HTTP Publish/Subscribe Server Issues and Workarounds"

- Section 12.13, "Installation Issues and Workarounds"

- Section 12.14, "Java EE Issues and Workarounds"

- Section 12.15, "JDBC Issues and Workarounds"

- Section 12.16, "JDK Issues and Workarounds"

- Section 12.17, "JMS Issues and Workarounds"

- Section 12.18, "JNDI Issues and Workarounds"

- Section 12.19, "JSP and Servlet Issues and Workarounds"

- Section 12.20, "JTA Issues and Workarounds"

- Section 12.21, "Java Virtual Machine (JVM) Issues and Workarounds"

- Section 12.22, "Monitoring Issues and Workarounds"

- Section 12.23, "Node Manager Issues and Workarounds"

- Section 12.24, "Operations, Administration, and Management Issues and Workarounds"

- Section 12.25, "Oracle Kodo Issues and Workarounds"

- Section 12.26, "Protocols Issues and Workarounds"

- Section 12.27, "RMI-IIOP Issues and Workarounds"

- Section 12.28, "Security Issues and Workarounds"

- Section 12.29, "SNMP Issues and Workarounds"

- Section 12.30, "Spring Framework on WebLogic Server Issues and Workarounds"

- Section 12.31, "System Component Architecture (SCA) Issues and Workarounds"

- Section 12.32, "Upgrade Issues and Workarounds"

- Section 12.33, "Web Applications Issues and Workarounds"

- Section 12.34, "WebLogic Server Scripting Tool (WLST) Issues and Workarounds"

- Section 12.35, "Web Server Plug-Ins Issues and Workarounds"

- Section 12.36, "Web Services and XML Issues and Workarounds"

- Section 12.37, "WebLogic Tuxedo Connector Issues and Workarounds"

- Section 12.38, "Documentation Errata"

Note:

For a list of bugs that are fixed in WebLogic Server 11g Release 1 (10.3.6), enter the following document ID in the Search Knowledge Base field. You must enter the entire document ID.

1302753.1

12.1 General Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.1.1, "Multi-Byte Characters Display Incorrectly in Filenames When Using Safari"

- Section 12.1.2, "Oracle WebLogic Server Version Number"

- Section 12.1.3, "Oracle ojdbc14.jar File Has Been Changed to ojdbc6.jar"

- Section 12.1.4, "Strong Password Enforcement May Cause Issues With WLST Offline Scripts"

- Section 12.1.5, "In Turkish Locale, MDS Initialization Fails"

- Section 12.1.6, "Administration Server Reports a 'Too Many Open Files' Message on the EM Console"

- Section 12.1.7, "Availability of Sun JDK 6 U35-B52 for 10.3.5.0 Oracle WLS Generic Installation"

12.1.1 Multi-Byte Characters Display Incorrectly in Filenames When Using Safari

When using the Safari browser to download content, if a filename contains multi-byte characters, the characters are displayed as '------' in the filename.

Workaround

Set UseHeaderEncoding to true on the Managed Server. Use the following WLST commands to do so:

connect("admin_name", "admin_password", "t3://localhost:port")
edit()
startEdit()
cd("Servers/server_name/WebServer/server_name")
set("UseHeaderEncoding", "true")
save()
activate()
exit()

12.1.2 Oracle WebLogic Server Version Number

Oracle Fusion Middleware 11g contains Oracle WebLogic Server 11g. The version number of Oracle WebLogic Server is 10.3.6.

12.1.3 Oracle ojdbc14.jar File Has Been Changed to ojdbc6.jar

The Oracle ojdbc14.jar file has been changed to ojdbc6.jar, for use with JDK 5 or 6. As a result, any explicit references you make to ojdbc14.jar must be changed to ojdbc6.jar.

12.1.4 Strong Password Enforcement May Cause Issues With WLST Offline Scripts

With the implementation of strong password enforcement (8 character minimum with one numeric or special character) in this release of WebLogic Server, existing scripts could potentially encounter issues.

Workaround

Use either of the following workarounds to bypass the new password restrictions.

- Set the BACKWARD_COMPAT_PW_CHECK environment variable to true.

- Include the -Dbackward.compat.pw.check=true option when invoking WLST.

Oracle recommends that you change passwords to comply with the new password requirements, as this variable and option will be removed in a future release of WebLogic Server.

12.1.5 In Turkish Locale, MDS Initialization Fails

Any applications that use an MDS repository cannot be deployed or run with the JAXB version bundled with WebLogic Server as null values are returned for attributes named id.

Workaround

Start the server in English locale.

12.1.6 Administration Server Reports a 'Too Many Open Files' Message on the EM Console

The WebLogic Server Administration Server reports a Too Many Open Files message on the Enterprise Manager (EM) console when the maximum number of file descriptors configured for the Administration Server is less than 65535.

Workaround

Increase the number of file descriptors within the shell and restart the WLS Administration Server within that shell. The command to increase the number of file descriptors (nofiles) differs across Operating Systems and shells but it is usually done with the ulimit command on UNIX platforms. So, consult the man pages for ulimit.

For example:

$ ulimit -n 65535

12.1.7 Availability of Sun JDK 6 U35-B52 for 10.3.5.0 Oracle WLS Generic Installation

Sun JDK 1.6.0.U35-B52 version is required for Oracle WebLogic Server 10.3.5.0 (PS4) generic installation on Linux x86-64, Microsoft Windows x64 (64-Bit), and Oracle Solaris platforms.

The mentioned version of JDK is not available for download from the Oracle Web site:

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

Complete the following steps to download the required JDK version:

1. Go to My Oracle Support:

https://support.oracle.com

2. Click the Patches & Updates tab.

3. Enter patch 12346791 in the Patch Name or Number field, under Patch Search.

4. Click Search.

5. Select and download the patch for the required platform by following the instructions in the README file included with the patch.

12.2 Administration Console Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.2.1, "Cached JDBC Information is not Displayed"

- Section 12.2.2, "Pressing Browser Back Button Discards Context"

- Section 12.2.3, "Unsupported Work Manager Configurations Can Be Created"

- Section 12.2.4, "Server Status Table Reflects Inconsistent Information"

- Section 12.2.5, "Exceptions When Defining a Security Policy for an EJB"

- Section 12.2.6, "Administration Console Does Not Always Reflect External Changes Made in a Deployment Plan"

- Section 12.2.7, "Oracle OCI Driver Support"

- Section 12.2.8, "Data Takes a Long Time to Display on the Metric Browser Tab"

12.2.1 Cached JDBC Information is not Displayed

Information about cached JDBC statements is not displayed on the JDBC Monitoring pages.

12.2.2 Pressing Browser Back Button Discards Context

After a page flow completes in the Administration Console, it forwards to a different page, typically a table.

Pressing the browser Back button at this point results in an attempt to load the last JSP file in the completed assistant. At this point, all of the context for this assistant is discarded.

Workaround

Oracle recommends that you do not use the browser Back button to step back into an assistant once changes are cancelled or finished, and that you do not go back to a previous step in an assistant. Instead, use the navigation links and buttons in the Administration Console.

12.2.3 Unsupported Work Manager Configurations Can Be Created

The Administration Console permits the creation of Work Manager configurations that are not supported and do not function as intended. Incorrect Work Manager configurations may result in a number of exceptions being recorded in the server logs, most commonly 'Validation problems were found' exceptions while parsing deployment descriptors.

Workaround

Follow the guidelines described in the online help for Work Manager configurations. Specifically, you can only assign one request class to any given Work Manager, and that request class must be of the same or a broader scope than the Work Manager. You should not assign an application-scoped request class to a global Work Manager, and you should not create more than one application-scoped request class for an application-scoped Work Manager.

Correcting the Work Manager configurations to match the documented constraints resolves these issues.

12.2.4 Server Status Table Reflects Inconsistent Information

The Server Status table on the Cluster: Monitoring: Summary page includes two default columns: Primary and Secondary Distribution Names. These fields do not always reflect all of the replication statistics that are collected and displayed on the Cluster: Monitoring: Failover page, depending on the replication scenario.

Please refer to the Cluster: Monitoring: Failover page for definitive information.

12.2.5 Exceptions When Defining a Security Policy for an EJB

When defining security policies in the Administration Console for an EJB deployment that references types defined in a separate library deployment, exceptions can be observed if that library deployment is not available to the Console.

Workaround

All library deployments should be targeted at the WebLogic Server Administration Server as well as any Managed Servers needed to support referencing applications. This will ensure that when defining policies, the Console will have access to those library deployments so that referenced types can be class-loaded as needed.

12.2.6 Administration Console Does Not Always Reflect External Changes Made in a Deployment Plan

The Administration Console does not always reflect external changes made in a deployment plan. If a change is made in a deployment plan outside of the Console (for example, using Workshop, editing the plan text files directly, or updating a deployment with a new plan using WLST or webLogic.Deployer) while a Console user is also viewing that deployment plan, the Console user will not see those changes.

Workaround

Navigate to a configuration page for a different deployment, then navigate back to the original deployment again.

12.2.7 Oracle OCI Driver Support

The Oracle OCI driver is no longer explicitly listed as a preconfigured driver type in the Administration Console.

Workaround

The Oracle OCI driver remains a supported driver for application data connectivity, consistent with prior releases of Oracle WebLogic Server. However, users must now specify all required configuration properties manually, including the data base username.

12.2.8 Data Takes a Long Time to Display on the Metric Browser Tab

When using Internet Explorer 7 (IE 7) to display data on the Metric Browser tab of the Monitoring Dashboard, it takes an unusually long time for the data to display, and during this time, the page is unresponsive. The amount of time it takes to display data on this tab depends on the size of the domain.

Workaround

If you need to display data on the Monitoring Dashboard > Metric Browser tab, open the Administration Console in a supported web browser other than IE 7, such as Internet Explorer 8 or greater, Firefox 3 or greater, or Safari 4 or greater.

12.3 Apache Beehive Support Issues and Workarounds

There are no known Apache Beehive Support issues in this release of WebLogic Server.

12.4 Clustering Issues and Workarounds

This section describes the following issue and workaround:

- Section 12.4.1, "Threads Are Blocked on Cluster Messaging in Unicast Mode"

12.4.1 Threads Are Blocked on Cluster Messaging in Unicast Mode

When using Unicast mode for cluster communication, many threads are blocked on cluster messaging, which may result in cluster members having difficulty sending heartbeat messages. In this situation, some cluster members drop out from the cluster and may take some time to rejoin the cluster.

Workaround

Set the following system property to resolve this issue:

-Dweblogic.unicast.HttpPing=true

12.5 Configuration Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.5.1, "ASProvWorkflowException Occurs When Creating a WebLogic Domain"

- Section 12.5.2, "Directory For a Non-Existent Server Name Is Created"

- Section 12.5.3, "Abnormal Behavior in Terminal Window After Entering WebLogic Password"

- Section 12.5.4, "Creating and Updating Domains Takes Too Long"

- Section 12.5.5, "Password Field Is Not Editable When Configuring a New Domain"

12.5.1 ASProvWorkflowException Occurs When Creating a WebLogic Domain

In rare cases, if your installation environment contains existing JAVA_OPTIONS prior to starting a Fusion Middlware product installation, these may cause an ASProvWorkflowException, preventing the domain from being created.

Workaround

Prior to starting the Fusion Middleware product installation, clear the existing JAVA_OPTIONS. If you have an applicagtion in the environment that use these JAVA_OPTIONS, the applications may not work after clearing the options. In this case, save the existing JAVA_OPTIONS to a text file and investigate alternatives for running your other application.

12.5.2 Directory For a Non-Existent Server Name Is Created

If you attempt to connect to the WebLogic Server Administration Server with a non-existent server name, a directory for the non-existent server name is created under the domain_name/servers directory.

Workaround

Specify a valid server name when connecting to the Administration Server.

12.5.3 Abnormal Behavior in Terminal Window After Entering WebLogic Password

After pressing Ctrl-C to terminate the startManagedWebLogic.sh process immediately after entering the WebLogic password, abnormal behavior may be experienced in the terminal window. For example, when pressing Return, the prompt is tabbed instead of going to the next line, and any characters that are entered at the prompt are not displayed in the terminal.

Workaround

Either close the current xterm and start a new one, or enter stty echo into the xterm.

12.5.4 Creating and Updating Domains Takes Too Long

It can take a long time to create or update WebLogic Server domains when:

- Installing WebLogic Server on UNIX or Linux operating systems if the Server Examples are included in the installation.

- Using the WebLogic Server Configuration Wizard to create or update a domain.

- Using WLST to create or update a domain.

Workaround

Set the CONFIG_JVM_ARGS environment variable to the following value:

-Djava.security.egd=file:/dev/./urandom

12.5.5 Password Field Is Not Editable When Configuring a New Domain

On Linux systems, when creating a new domain in the Oracle Fusion Middleware Configuration Wizard, the Password and Confirm Password fields are sometimes not editable, and you cannot enter a password to create a domain.

Workaround

There are two ways to work around this issue:

- To work around the issue each time it happens, click the Close Window X button in the upper right corner of the Configuration Wizard. In the confirmation dialog that appears, click No to return to the Configuration Wizard. You can then enter and confirm the password for the domain.

- To fix this issue permanently:

1. Kill all scim processes. For example:
kill `pgrep scim`

2. Modify (or create) the file ~/.scim/config to include the following line (case-sensitive):
/FrontEnd/X11/Dynamic = true

3. If you are running VNC, restart the VNC server.

4. Run the Configuration Wizard again.

12.6 Connector (Resource Adapter) Issues and Workarounds

There are no known Connector (Resource Adapter) issues in this release of WebLogic Server.

12.7 Console Extensions Issues and Workarounds

There are no known Extensions issues in this release of WebLogic Server.

12.8 Core Server and Core Work Manager Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.8.1, "Threads Become Stuck While Waiting to Get a Connection"

- Section 12.8.2, "Using IPv6-Formatted Addresses"

- Section 12.8.3, "Server Cannot Be Started After a Whole Server Migration"

- Section 12.8.4, "Object State is not Retained After Renaming Field"

- Section 12.8.5, "Forcing Unicast Messages To Be Processed in Order"

- Section 12.8.6, "Servers Configured to Listen on a Host Name Are Listening on a Different Host Name After Startup"

- Section 12.8.7, "Administration Server or Node Manager Cannot Track the Status of a Managed Server"

- Section 12.8.8, "Multicast Traffic Observed to be Unreliable During or After a Network Partition"

12.8.1 Threads Become Stuck While Waiting to Get a Connection

When a machine that is hosting one of the Managed Servers is abruptly shut down, a network cable is pulled, or its network interface card has issues, and any server attempts communication with that managed server, threads become stuck waiting to get a connection.

Workaround

This can currently be resolved by using a private flag:

-Dweblogic.client.SocketConnectTimeoutInSecs

and setting an appropriate timeout value that will release the thread attempting to make the connection and allow the request to fail quickly.

12.8.2 Using IPv6-Formatted Addresses

When using an IPv6-formatted address for WebLogic Server, the URL should include square brackets ('[' and ']') for the host address. Otherwise, WLST may fail to connect to the running server.

Workaround

Add square brackets to the host address. For example:

t3://[fe80:0:0:0:203:baff:fe2f:59e5]:9991

12.8.3 Server Cannot Be Started After a Whole Server Migration

If the WebLogic Server Administration Server is down when a Whole Server Migration occurs for a clustered server, and the server migrates to a machine on which it was never run before, the server cannot be started on the new machine.

Workaround

Use one of the following workarounds for this issue:

- Ensure that the Administration Server is up when the server migration is being performed.

- Use a shared disk/NFS for all the migratable servers in the cluster.

12.8.4 Object State is not Retained After Renaming Field

When FastSwap is enabled in a J2EE application, you can make certain types of changes to Java classes during development and expect to see the change without re-deploying, with all instance states of the Java object being retained.

One type of change that does NOT retain the object state is that when a field name is changed, it is treated as follows:

- the field with old name is deleted

- the field with new name is added

Thus, in this case, any state in the old field is not carried over to the renamed field.

Using the Workshop or FastSwap ant task, you may see a FastSwap operation completed successfully message, even when an instance field name change causes a value reset.

Workaround

You should expect an instance value to be reset when you change a field name.

12.8.5 Forcing Unicast Messages To Be Processed in Order

The following conditions can cause very frequent JNDI updates, and as a result, JMS subscribers may encounter a java.naming.NameNotFoundException:

1. Unicast messaging is being used for cluster communication.

2. The JMS topic connection is set with setReconnectPolicy("all").

3. JMS durable subscribers on topic are created and removed very frequently.

Workaround

To fix this issue, a new property, MessageOrderingEnabled, has been added to the ClusterMBean. This property forces unicast messages to be processed in strict order. By default, this property is not enabled. To enable the property, add the following line manually to the <cluster> element in config.xml.

<message-ordering-enabled>true</message-ordering-enabled>

12.8.6 Servers Configured to Listen on a Host Name Are Listening on a Different Host Name After Startup

When using a host name to specify configuring the listen address on the WebLogic Server Administration Server or a Managed Server, machines that are configured with multiple Ethernet cards may listen on a different host name after startup. For example:

- The machine has 3 Ethernet cards

- Card 1 is mapped to hostname1-s (DNS registered host name)

- Card 2 is mapped to hostname1-i (DNS registered host name)

- Card 3 is mapped to hostname1 (actual node's host name)

- You configure the server to listen on hostname1

- After starting the server, it is listening on hostname1-s because Windows resolves the actual node's host name to the first enabled Ethernet card address

Workaround

Use one of the following three workarounds for this issue:

1. Use the IP address, instead of the host name, as the listen address of the WebLogic Server Administration Server. On Managed Servers, use the IP address as the listen address, or configure the actual physical host name to the first Ethernet card in the machine.

2. Add the following entry to the C:\Windows\system32\drivers\etc\hosts file on the machine:
<ip_address> <hostname>

3. Change the order of the network cards in the machine so that the card with the actual node's host name is Card 1.

12.8.7 Administration Server or Node Manager Cannot Track the Status of a Managed Server

If you start a managed server by providing an incorrect WebLogic Server Administration Server URL from the command line (that is, the Administration Server cannot be reachable at the provided URL), the managed server will start in Managed Server Independence (MSI) mode.

In this case, neither the Administration Server nor Node Manager can track the status of the managed server. The Administration Console will show the status of the managed server as UNKNOWN, but the server will actually be RUNNING in MSI mode.

12.8.8 Multicast Traffic Observed to be Unreliable During or After a Network Partition

During or after a network partition that causes a server migration to take place, multicast traffic has been observed to be unreliable. For example, one node may be receiving multicast traffic, but traffic originating from this node is not received on other nodes in the network. As a result, the migrated servers are not added to the cluster because their heartbeats were not received.

Workaround

Currently, the only known workaround is to use unicast cluster messaging.

12.9 Deployment Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.9.1, "security-permission Element is not Available in weblogic-application.xml"

- Section 12.9.2, "Extraneous String Values Interpreted as File Specification"

- Section 12.9.3, "java.lang.NoClassDefFoundError is Displayed"

- Section 12.9.4, "The restore Method Does Not Update the DConfig Bean With Plan Overrides"

- Section 12.9.5, "config-root <directory> not found Warning Is Displayed When Applying a Plan"

- Section 12.9.6, "Deployment Task Fails When a Large Application File Is Deployed"

- Section 12.9.7, "Application State Is Not Updated If the Server Starts in MSI Mode"

- Section 12.9.8, "Attempting to Redeploy an Application Fails if the Application is Already Deployed Using a Different Source File Location"

12.9.1 security-permission Element is not Available in weblogic-application.xml

The security-permission element is available in the weblogic.xml and weblogic-ejb-jar.xml deployment descriptors, but is not available in the weblogic-application.xml descriptor. Therefore, in an Enterprise application, you can only apply security policies to JAR files that are EJBs or Web applications.

12.9.2 Extraneous String Values Interpreted as File Specification

The weblogic.Deployer tool interprets any extraneous string values between command-line arguments as a file specification. For example, if you enter the command:

java weblogic.Deployer -activate -nostage true -name myname -source c:\myapp\mymodule

the tool attempts to activate a file specification named true, because the -nostage option takes no arguments and true is an extraneous string value.

12.9.3 java.lang.NoClassDefFoundError is Displayed

While using the WebLogic Server Administration Console with applications or EJBs deployed on a Managed Server that depend on a deployed library, you may encounter a java.lang.NoClassDefFoundError.

Workaround

The WebLogic Server Administration Console needs access to any shared library deployments so that Java data types and annotations can be processed. Therefore, all shared library deployments should always be targeted to the WebLogic Server Administration Server in addition to any Managed Servers or clusters.

12.9.4 The restore Method Does Not Update the DConfig Bean With Plan Overrides

The restore method does not correctly update the DConfig Bean with the plan overrides. For example, given the following steps:

DeployableObject dObject =
WebLogicDeployableObject.createDeployableObject(new File(appName));
DeploymentConfiguration dConfig =
WebLogicDeploymentManager.createConfiguration(dObject);
dConfig.restore(new FileInputStream(new File(plan)));

the plan does not correctly override the DConfig Bean.

Workaround

Specify the plan when initializing the configuration for the application. For example:

helper = SessionHelper.getInstance(
SessionHelper.getDisconnectedDeploymentManager());
helper.setApplication(app);
helper.setPlan(new File(plan));
helper.initializeConfiguration();

12.9.5 config-root <directory> not found Warning Is Displayed When Applying a Plan

If you use the Administration Console to make configuration changes to an application, a deployment plan will be generated. If external descriptors are generated as part of the deployment plan, they are placed in the config root plan directory. This directory will be set in the deployment plan 'config-root' attribute.

If no external descriptors are required, the config root directory will not be created, and a warning is displayed when you apply the deployment plan. This results in the following warning in the server output:

<Warning <WWebLogicDescriptorWL> <BEA-2156000><"config-root" C:\deployments\plan was not found>.

Workaround

Create the plan directory manually.

12.9.6 Deployment Task Fails When a Large Application File Is Deployed

When a large application file is deployed using the upload option, the deployment task fails with the following error:

java.lang.OutOfMemoryError: Java heap space

To resolve this issue, a new system property, weblogic.deploy.UploadLargeFile, has been added. If you see this issue, include this flag in the java command you use to launch a deployment client.

If you are using the WebLogic Server patch releases 9.2 MP2, 9.2 MP3,10.0 MP1, 10.0 M2, 10.3, 10.3.1, 10.3.2, 10.3.3, or 10.3.4, this flag is not needed.

12.9.7 Application State Is Not Updated If the Server Starts in MSI Mode

A managed server will start in MSI mode if the WebLogic Server Administration Server is not available when the managed server starts. If you start the Administration Server later, the managed server will connect to the Administration Server. However, the state of each application deployed to the managed server is not updated to reflect the state of the applications on the managed server. Each application's state is displayed as NEW or PREPARED in the WebLogic Server Administration Console.

Workaround

There are two workarounds for this issue:

- Start the Administration Server before starting the managed server, or

- Redeploy the application after starting the Administration Server.

12.9.8 Attempting to Redeploy an Application Fails if the Application is Already Deployed Using a Different Source File Location

If you initially deployed an application using one source file location, then attempt to redeploy the application using a new location for the source file, the deployment fails with the following exception:

New source location <new_source_file_path> cannot be configured deployed to
configured application, <application_name>. The application source is at
original_source_file_path. Changing the source location is not allowed for a
previously attempted deployment. Try deploying without specifying the source.

This is due to a WebLogic Server deployment restriction. Once you specify the source file for a deployment, you cannot change it on a redeployment.

Workaround

Undeploy the application before attempting to redeploy it using a new source file location.

12.10 EJB Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.10.1, "Primary Key in Oracle Table is CHAR"

- Section 12.10.2, "No Available Annotation That Enables Creation of a Clusterable Timer"

- Section 12.10.3, "Kodo's MappingTool Cannot Generate Schemas"

- Section 12.10.4, "Extensions to the JPA Metadata Model Can Only Be Specified Via Annotations"

- Section 12.10.5, "Lookup Method Injection Not Supported by Spring"

- Section 12.10.6, "Deserializing a JDO PersistenceManagerFactory in a Managed Environment May Fail"

- Section 12.10.7, "Indexes Not Always Created During Schema Creation"

- Section 12.10.8, "OpenJPA throws an exception when @Id fields are also annotated as @Unique"

- Section 12.10.9, "Cache Hit and Miss Counts May Rise Unexpectedly"

- Section 12.10.10, "Open JPA Tries to Create a Table Even if the Table Exists"

- Section 12.10.11, "EJB Applications Fail During Serialization"

- Section 12.10.12, "Non-Transactional Message-Driven Bean Container Can Fail to Provide Reproducible Behavior For Foreign Topics"

12.10.1 Primary Key in Oracle Table is CHAR

The primary key in an Oracle table is a CHAR but the query field in the SQL table is a VARCHAR2.

Workaround

Change the database schema from CHAR to VARCHAR2. Using CHAR as a primary key is not recommended for the Oracle database.

12.10.2 No Available Annotation That Enables Creation of a Clusterable Timer

There is no annotation for EJB3 beans or Ejbgen that enables creation of a clusterable timer.

Workaround

Create a weblogic-ejb-jar.xml file and put the <timer-implementation> element and corresponding values into the file.

12.10.3 Kodo's MappingTool Cannot Generate Schemas

Kodo's MappingTool cannot generate schemas for classes that use BLOBs in their primary key. BLOBs can be used in a primary key, but the schema must be defined manually. Note that support for BLOB columns in primary keys is not mandated by either the JDO or JPA specifications.

12.10.4 Extensions to the JPA Metadata Model Can Only Be Specified Via Annotations

Extensions to the JPA metadata model can only be specified via annotations, and not via a structure similar to the orm.xml file defined by the specification.

Workaround

To specify Kodo-specific metadata for your object model, either:

- use the Kodo-specific annotations, or

- convert your XML-based metadata to the JDO metadata format, which does support XML specification of extensions.

12.10.5 Lookup Method Injection Not Supported by Spring

The Weblogic Spring injection extension model doesn't support lookup method injection.

12.10.6 Deserializing a JDO PersistenceManagerFactory in a Managed Environment May Fail

Deserializing a JDO PersistenceManagerFactory in a managed environment may fail. The exception states that the javax.jdo.PersistenceManagerFactoryClass property is missing. Note that serializing a PersistenceManagerFactory should not generally be necessary in a managed environment.

12.10.7 Indexes Not Always Created During Schema Creation

Indexes declared at the class level are not always created during schema creation.

Workaround

Create the indexes manually after running the schema generation tools.

12.10.8 OpenJPA throws an exception when @Id fields are also annotated as @Unique

OpenJPA throws an exception when @Id fields are also annotated as @Unique in some databases. Database primary keys are unique by definition. Some databases implement this by creating a unique index on the column.

Workaround

Do not specify both @Id and @Unique on a single field.

12.10.9 Cache Hit and Miss Counts May Rise Unexpectedly

The cache hit and miss counts may rise unexpectedly when manipulating entities without version data. The extra cache access occurs when the EntityManager closes and all contained entities are detached. Entities without version fields appear to the system to be missing their version data, and the system responds by checking their version in the cache before detachment.

Workaround

Entities with version fields or other version strategies do not cause extra cache access.

12.10.10 Open JPA Tries to Create a Table Even if the Table Exists

When using the MySQL database, and OpenJPA is configured to automatically run the mapping tool at runtime and create tables within the default schema (for example):

<property name='openjpa.jdbc.SynchronizeMappings' value='buildSchema'/>
<property name='openjpa.jdbc.Schema' value='MySQL database name' />

OpenJPA will try to create the table even if the table already exists in the database. A PersistenceException will be thrown to indicate that the table already exists and the table creation statement fails.

Workaround

To avoid this problem, if you are using the MySQL database, don't configure OpenJPA to automatically run the mapping tool at runtime and specify the default schema at the same time.

12.10.11 EJB Applications Fail During Serialization

EJB applications that use IIOP and send JPA entities from the server to the client will fail during deserialization if the entities are Serializable (but not Externalizable) and do not declare a writeObject() method.

Workaround

Add a writeObject() method to such entity classes. The write object can be trivial:

private void
writeObject(java.io.ObjectOutputStream out)
throws IOException {
out.defaultWriteObject();
}

12.10.12 Non-Transactional Message-Driven Bean Container Can Fail to Provide Reproducible Behavior For Foreign Topics

When using multi-threaded processing for non-transactional topic Message-Driven Beans (MDBs) that specify a foreign topic (non-WebLogic) JMS, the MDB container can fail to provide reproducible behavior. For example, if a runtimeException is thrown in the onmessage() method, the container may still acknowledge the message.

Workaround

Set the max-beans-in-free-pool attribute to 1 in the deployment descriptor.

12.11 Examples Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.11.1, "Security Configuration in medrec.wls.config"

- Section 12.11.2, "HTML File not Created for StreamParser.java File"

- Section 12.11.3, "Warning Message Appears When Starting Medrec or Samples Domain"

12.11.1 Security Configuration in medrec.wls.config

The medrec.wls.config target in SAMPLES_HOME/server/medrec/setup/build.xml has a known issue with respect to security configuration.

12.11.2 HTML File not Created for StreamParser.java File

The ../xml/stax example contains two files with the same root but different extensions: StreamParser.java and StreamParser.jsp. The samples viewer build, however, creates just one corresponding HTML file, rather than two for each type of file. In this case only the StreamParser.jsp file has an equivalent HTML file; the StreamParser.java file does not.

The problem occurs because of a setting in the build.xml file that controls the behavior of java2html to generate the files for the documentation.

When using java2html, the useShortFileName="true" parameter crops off the file extensions for the source files to create the file names for the HTML output files. If two files have the same name and different file extensions, whichever HTML file is generated last will overwrite previous ones.

Workaround

Set the useShortFileName parameter to "false". This setting generates HTML files with the file extensions included in the name. The drawback to this solution is that every link that points to the HTML output file needs to be revised, regardless of whether the files in question were affected by the bug.

12.11.3 Warning Message Appears When Starting Medrec or Samples Domain

When you start the medrec or samples domains, you may see a warning message similar to this:

<Warning> <WorkManager> <BEA-002919> <Unable to find a WorkManager with name
weblogic.wsee.mdb.DispatchPolicy. Dispatch policy
weblogic.wsee.mdb.DispatchPolicy will map to the default WorkManager for the
application bea_wls_async_response>

This warning message appears in the standard output of the Console while starting a WebLogic Server sample application with an asynchronous Web Service deployed.

Workaround

The warning is harmless and can be ignored.

12.12 HTTP Publish/Subscribe Server Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.12.1, "Authentication and Authorization of the Local Client is not Supported"

- Section 12.12.2, "Event Messages Published by Local Clients Cannot Be Received"

- Section 12.12.3, "Event Messages Published By Local Clients Do Not Go Through Filters"

12.12.1 Authentication and Authorization of the Local Client is not Supported

The HTTP Publish/Subscribe server does not support authentication and authorization of the local client. The local client has full permissions to operate on channels of the HTTP Publish/Subscribe server, which means the local client can create/delete channels and publish/subscribe events from channels.

12.12.2 Event Messages Published by Local Clients Cannot Be Received

In a clustering environment, event messages published by a local client on a server can be received only by subscribed clients connected to the same server. These messages cannot be received by subscribed clients connected to other servers in the cluster.

12.12.3 Event Messages Published By Local Clients Do Not Go Through Filters

Event messages published to a channel by a local client will not go through the Message Filters configured to that channel.

12.13 Installation Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.13.1, "Sybase JDBC Drivers Not Downloaded with Upgrade Installation"

- Section 12.13.2, "Improper Rollback to Previous Installation May Occur After Exiting an Upgrade Installation Prematurely"

- Section 12.13.3, "WebLogic Server Installer Fails With Insufficient Disk Space Error"

- Section 12.13.4, "Installation Fails with Fatal Error"

- Section 12.13.5, "Oracle WebLogic Server Installation Fails on Oracle Solaris 11"

12.13.1 Sybase JDBC Drivers Not Downloaded with Upgrade Installation

The Oracle WebLogic Server 11g Release 1 installer does not download the Sybase JDBC drivers. When you try to upgrade an existing WebLogic Server 10.3 installation using the latest installer, it does not remove the Sybase JAR files from the original installation. The installer upgrades only the weblogic.jar file.

The Sybase JAR files (jconn2.jar, jconn3.jar, and jConnect.jar) in the /server/lib or /server/ext/jdbc/sybase directories are removed from the manifest classpath in the upgraded weblogic.jar file. Therefore, if the classpath of a WebLogic Server application does not include Sybase JAR files and only includes weblogic.jar then after the upgrade installation, the application will throw a ClassNotFoundException.

To work around this issue, explicitly add Sybase JAR files in the WebLogic Server application classpath.

12.13.2 Improper Rollback to Previous Installation May Occur After Exiting an Upgrade Installation Prematurely

When using an Upgrade installer or Smart Update to upgrade an existing WebLogic Server 10.3.x installation to WebLogic Server 10.3.4, if you abort the upgrade before completion, the installation should automatically roll back to the prior installation. This may not always occur, resulting in an unusable installation.

12.13.3 WebLogic Server Installer Fails With Insufficient Disk Space Error

The WebLogic Server installer can fail with an insufficient disk space error, even when there is a large amount of available disk space on the file system or disk.

Workaround

Use the -Dspace.detection property in the installation command to disable the available space check. For example:

java -Xmx1024M -Dspace.detection=false -jar installer_file_name -mode=silent -silent_xml=silent.xml

or

wls1034_linux.bin -Dspace.detection=false

12.13.4 Installation Fails with Fatal Error

The installer does not verify whether sufficient disk space is available on the machine prior to completing the installation. As a result, if an installation cannot be completed due to insufficient space, the installer displays the following error message and exits:

Fatal error encountered during file installation. The installer will now
cleanup and exit!

Workaround

If this problem occurs, restart the installer using the following command:

server103_linux32.bin -log=log.out -log_priority=debug

The preceding command generates a log of the installation procedure, providing details about the exact cause of the failure. If the cause is indeed insufficient space, the log file indicates it explicitly.

12.13.5 Oracle WebLogic Server Installation Fails on Oracle Solaris 11

When you use JRockit based Oracle Solaris Package installer to install Oracle WebLogic Server for Oracle Solaris 11 on Oracle Solaris on SPARC (64-Bit) systems, the installation fails and the following error is displayed:

dl failure on line 742Error: failed
/var/tmp/aaalpa4OF/jre160_29/lib/sparcv9/jrockit/libjvm.so, because ld.so.1:java: fatal: relocation error: file
/var/tmp/aaalpa4OF/jre160_29/lib/sparcv9/jrockit/libjvm.so: symbol_walkcontext: referenced symbol not found
** Error during execution, error code = 1536.

Workaround

Install Oracle WebLogic Server using the Generic Package installer wls1036_generic.jar that is enabled with jrockit-jdk1.6.0_29-R28.2.1-4.1.0-solaris-sparcv9.bin.

12.14 Java EE Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.14.1, "FastSwap May Relax the Access Modifiers of Fields and Methods"

- Section 12.14.2, "FastSwap Does Not Support Redefinition of the Entity Bean and ejbClass"

- Section 12.14.3, "Classpath Order Is Not Guaranteed When There Are Multiple JARs in an EAR File"

12.14.1 FastSwap May Relax the Access Modifiers of Fields and Methods

FastSwap may relax the access modifiers of fields and methods. Private and protected members may be made public at runtime. This changes the behavior of reflection and may affect reflection-based frameworks such as Struts.

12.14.2 FastSwap Does Not Support Redefinition of the Entity Bean and ejbClass

FastSwap does not support redefinition of the Entity bean and ejbClass (Session/MDB). Therefore, any updates to entity classes will cause redefinition errors.

Workaround

After updating an entity class, redeploy the application.

12.14.3 Classpath Order Is Not Guaranteed When There Are Multiple JARs in an EAR File

When you have an EAR file containing separate JAR files, and two or more of those JAR files have a class with the same name, it is not possible to predict from which of those JAR files WebLogic Server will instantiate the class. This is not an issue if the classes are the same, but if they are different implementations, the results are unpredictable.

Workaround

Currently there is no known workaround for this issue.

12.15 JDBC Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.15.1, "Call To setTransactionIsolation() May Fail When Using the JDBC Driver for MS SQLServer"

- Section 12.15.2, "An Attempt to Access a Remote 10.3.2 or Later WLS Data Source Fails"

- Section 12.15.3, "ORA-01591 Errors Occur on SOA Servers Configured to Use Multiple Oracle RAC Nodes"

12.15.1 Call To setTransactionIsolation() May Fail When Using the JDBC Driver for MS SQLServer

When using the JDBC driver for MS SQLServer, a call to setTransactionIsolation() may fail in a transactional context if getTransactionIsolation() is called first.

12.15.2 An Attempt to Access a Remote 10.3.2 or Later WLS Data Source Fails

A new system property, -Dweblogic.jdbc.remoteEnabled, has been added to JDBC in Oracle WebLogic Server 10.3.2. For compatibility with prior releases of WebLogic Server, the default setting of this property is true. When this property is set to false, remote JDBC access is turned off, and such access results in an exception.

Remote access may occur explicitly in an application, or implicitly during a global (XA/JTA) transaction with a participating non-XA data source that is configured with the LLR, 1PC or Emulate XA global transaction option. The following enumerates the cases when an exception will be thrown, and work-arounds for each case (if any).

An exception occurs in the following cases. A workaround (if any) for a given case is provided.

- When a stand-alone client application uses any type of data source.

- When an application that is hosted on WebLogic Server uses any type of data source, and the data source is not configured (targeted) locally. A potential workaround is to target the data source locally.

- When accessing a same named non-XA data source with a transaction option of LLR, 1PC or Emulate XA on multiple WebLogic Server instances in the same global transaction. In this case, there are two potential work-arounds:

- Change data sources to use XA instead (this may lower performance), or

- For the 1PC/emulateXA types, change the application to ensure the data source is accessed from a single server.

- When accessing a non-XA data source with the LLR transaction option on a server that is different than the transaction coordinator. For server-initiated transactions, the coordinator location is chosen based on the first participating resource in the transaction. In this case, there are two potential work-arounds: (a) change the data source to use XA instead (this may lower performance); or (b) change the application to ensure data source access on the transaction coordinator, as described in "Optimizing Performance with LLR" in Oracle Fusion Middleware Programming JTA for OracleWebLogic Server. The latter may not be possible in some cases; for example, when an MDB application receives messages from a remote WebLogic JMS server, the transaction coordinator will always be the WebLogic server that's hosting the JMS server, but it may not be possible to move the MDB application to the same WebLogic server.

- Change the data source to use XA instead (this may lower performance), or

- Change the application to ensure data source access on the transaction coordinator, as described in "Optimizing Performance with LLR" in Oracle Fusion Middleware Programming JTA for Oracle WebLogic Server. This workaround may not be possible in some cases. For example, when an MDB application receives messages from a remote WebLogic JMS server, the transaction coordinator will always be the WebLogic Server instance that is hosting the JMS server, but it may not be possible to move the MDB application to the same WebLogic Server instance.

12.15.3 ORA-01591 Errors Occur on SOA Servers Configured to Use Multiple Oracle RAC Nodes

On SOA servers using multiple Oracle RAC database nodes, when WebLogic Server multi data sources are configured for XA and load balancing, ORA-10591 errors can occur.

Workaround

Download and apply Oracle RAC database patch 7675269 for Linux x86, Oracle Release 11.1.0.7.0. You can download this patch from My Oracle Support. Alternatively, you can download and apply patch set 9007079 for Linux x86, Oracle Release 11.1.0.7.0, which includes the patch 7675269.

12.16 JDK Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.16.1, "SSLv2Hello Not Supported by IBM JDK"

12.16.1 SSLv2Hello Not Supported by IBM JDK

The IBMJSSE2 Provider does not support the SSL version 2 protocol.

Workaround

Set oracle.net.ssl_version=3.0 or oracle.net.ssl_version=1.0 which allows you use SSLv3 and TLSv1 protocols.

12.17 JMS Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.17.1, "Deployment Descriptor Validation Fails"

- Section 12.17.2, "Exception When Multiple Producers Use the Same Client SAF Instance"

- Section 12.17.3, "Multi-byte Characters are not Supported in Store File and Directory Names"

- Section 12.17.4, "Generation of the Default UOO Name Has Changed"

- Section 12.17.5, "Testing Abrupt Failures of WebLogic Server When Using File Stores on NFS"

- Section 12.17.6, "JMS Message Consumers Will Not Always Reconnect After a Service Migration"

- Section 12.17.7, "Forcing Unicast Messages To Be Processed in Order"

12.17.1 Deployment Descriptor Validation Fails

Deployment descriptor validation fails when descriptor validation is enabled, and an EAR file contains only JMS modules.

Workaround

Make sure that there is at least one J2EE specification-compliant module in the EAR.

12.17.2 Exception When Multiple Producers Use the Same Client SAF Instance

When multiple JMS producers use the same JMS Client SAF instance (within a single JVM), depending on the timing of the JMS SAF client creation, you might receive the following exception:

Error getting GXA resource [Root exception is weblogic.jms.common.JMSException:
weblogic.messaging.kernel.KernelException: Error getting GXA resource]

Workaround

When using multiple JMS SAF client producers, try introducing a small delay between the creation of each new client.

12.17.3 Multi-byte Characters are not Supported in Store File and Directory Names

There is no support for multi-byte characters in WebLogic Store file and directory names. For instance, when the WebLogic Server name has multi-byte characters, the default store cannot be created, and WebLogic Server will not boot.

Workaround

Create WebLogic Server instances without multi-byte characters in the path name and use that path name for the default store configuration. Do not use multi-byte characters in the Weblogic Server name.

12.17.4 Generation of the Default UOO Name Has Changed

WebLogic Server 10.3.4 contains a fix for configurations that set a default unit-of-order (UOO) on a JMS regular destination, distributed destination, or template. This fix ensures that the default unit-of-order name stays the same even after a restart of the destination's host JMS server. The default UOO name is now based on the domain, JMS server, and destination names.

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

Oracle strongly recommends verifying the behavior of a server restart after abrupt machine failures when the JMS messages and transaction logs are stored on an NFS mounted directory. Depending on the NFS implementation, different issues can arise post failover/restart. For more information, see Section 6.3, "Testing Abrupt Failures of WebLogic Server When Using File Stores on NFS."

12.17.6 JMS Message Consumers Will Not Always Reconnect After a Service Migration

JMS message consumers will not always reconnect after a service migration when an application's WLConnection.getReconnectPolicy() attribute is set to all. If the consumers do not get migrated, either an exception is thrown or onException will occur to inform the application that the consumer is no longer valid.

Workaround

The application can refresh the consumer either in the exception handler or through onException.

12.17.7 Forcing Unicast Messages To Be Processed in Order

Certain conditions can cause very frequent JNDI updates, and as a result, JMS subscribers may encounter a java.naming.NameNotFoundException. For more information, see Section 12.8.5, "Forcing Unicast Messages To Be Processed in Order."

12.18 JNDI Issues and Workarounds

There are no known JNDI issues in this release of WebLogic Server.

12.19 JSP and Servlet Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.19.1, "Deployment Plans Cannot Be Used To Override Two Descriptors"

- Section 12.19.2, "Spring Dependency Injection Not Supported on JSP Tag Handlers"

- Section 12.19.3, "503 Error When Accessing an Application With a Valid sessionid"

12.19.1 Deployment Plans Cannot Be Used To Override Two Descriptors

Deployment plans cannot be used to override the following two descriptors during deployment of a Web application or a Web module: WEB-INF/classes/META-INF/persistence.xml and WEB-INF/classes/META-INF/persistence-configuration.xml. Deployment plans can otherwise be used to override any descriptor.

Workaround

Package WEB-INF/classes/META-INF/persistence.xml and WEB-INF/classes/META-INF/persistence-configuration.xml (if present) along with related class files into a JAR file. The JAR file must then be placed in the WEB-INF/lib directory of the Web application or Web module. A deployment plan can be used to override the two descriptors in such a JAR file.

12.19.2 Spring Dependency Injection Not Supported on JSP Tag Handlers

With the Spring extension model enabled, WebLogic Server 10.3 or later does not support Spring Dependency Injection (DI) on JSP tag handlers for performance reasons.

Currently, WebLogic Server supports Spring DI on most Web components, for example, servlets, filters and listeners. Spring DI is not, however, presently supported on JSP tag handlers for performance reasons.

12.19.3 503 Error When Accessing an Application With a Valid sessionid

When a session is persistent and an older version of a servlet context is retired, accessing the application with a valid sessionid will cause a 503 error.

For example, the session-persistent type of a versioned Web application is 'file'. A user can access the application successfully. Later, version 2 of the application is redeployed and version 1 is retired. If the same user accesses the application, they will get a 503 error.

12.20 JTA Issues and Workarounds

There are no known JTA issues in this release of WebLogic Server.

12.21 Java Virtual Machine (JVM) Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.21.1, "1.4 Thin Client Applet Cannot Contact WebLogic Server"

- Section 12.21.2, "JRockit JVM Appears to Freeze When Doing Long Array Copies"

- Section 12.21.3, "Using AWT libraries May Cause a JVM Crash"

12.21.1 1.4 Thin Client Applet Cannot Contact WebLogic Server

Due to a known Sun Microsystems VM bug (513552), a 1.4 Thin Client Applet cannot contact WebLogic Server 9.0 or later. This is because the VM does not distinguish correctly between a client and a server connection. The VM creates a server-type connection and caches it. It then attempts to make a client-type connection, finds the cached connection and tries to use that, but then encounters an error because clients are not allowed to use server connections.

12.21.2 JRockit JVM Appears to Freeze When Doing Long Array Copies

The JRockit JVM appears to freeze when doing long array copies as part of unlimited forward rolling. This can happen when multiple server reboots occur due to Out Of Memory conditions.

Workaround

When booting the servers, include the following JRockit JVM flag:

-XXrollforwardretrylimit:-1

12.21.3 Using AWT libraries May Cause a JVM Crash

You might encounter a JVM crash when using GUI libraries such as AWT or javax.swing (which often delegates to AWT).

Workaround

Start the server using the following flag:

-Djava.awt.headless=true

12.22 Monitoring Issues and Workarounds

This section describes the following issue and workaround:

- Section 12.22.1, "MBean Attributes Not Explicitly Marked as @unharvestable Appear as Harvestable"

- Section 12.22.2, "Events Generated By the JVM Level Are Not Generated at Low Volume"

- Section 12.22.3, "WLDF Performance Issues Can Occur When JVM Events Are Enabled"

12.22.1 MBean Attributes Not Explicitly Marked as @unharvestable Appear as Harvestable

The @unharvestable tag is not being honored at the interface level. If MBean attributes are not explicitly marked as @unharvestable, they are considered to be harvestable and will appear as harvestable in the WebLogic Administration Console.

Workaround

You can explicitly mark MBean attributes as @unharvestable.

12.22.2 Events Generated By the JVM Level Are Not Generated at Low Volume

In WebLogic Server 10.3.3, the default WLDF diagnostic volume setting was Off. As of WebLogic Server 10.3.4, the default diagnostic volume setting is Low Volume, and events generated by the JVM level are not being generated at the Low Volume setting in WebLogic Server 10.3.4 (JVM-level events were generated at the Low Volume setting in WebLogic Server 10.3.3). The JVM-level events are still generated at the High Volume and Medium Volume settings in WebLogic Server 10.3.4.

Workaround

Use one of the following workarounds to cause the JVM-level events to be generated:

- Increase the WLDF diagnostic volume to the Medium or High level.

- Use JRMC, JRCMD, or the JRockit command line settings to activate a separate flight recording in the WebLogic Server instance. By doing so, JVM will cause JVM events to be present at all WLDF diagnostic volume settings (Off, Low, Medium, and High).

12.22.3 WLDF Performance Issues Can Occur When JVM Events Are Enabled

When JVM events are enabled, WLDF performances issues may occur in the following situations:

- If there are no other JRockit flight recordings enabled, performance can degrade when the WLDF diagnostic volume is set to Medium or High level.

- If other JRockit flight recordings are enabled, performance can degrade at all WLDF diagnostic volume levels (Off, Low, Medium, and High).

12.23 Node Manager Issues and Workarounds

There are no known Node Manager issues in this release of WebLogic Server.

12.24 Operations, Administration, and Management Issues and Workarounds

There are no known Operations, Administration, and Management issues in this release of WebLogic Server.

12.25 Oracle Kodo Issues and Workarounds

There are no known Oracle Kodo issues in this release of WebLogic Server.

12.26 Protocols Issues and Workarounds

There are no known Protocols issues in this release of WebLogic Server.

12.27 RMI-IIOP Issues and Workarounds

This section describes the following issue and workaround:

- Section 12.27.1, "Ant 1.7 rmic Task Incompatibility"

12.27.1 Ant 1.7 rmic Task Incompatibility

Calls to the Ant version 1.7 rmic task automatically add a -vcompat flag, which is not compatible with rmic for Oracle WebLogic Server.

Workaround

Use either of the following workarounds if your rmic call is of the form:

rmic classname="com.bea.crmsimulation.legacyra.LegacyAdapter"
base="${module_location}/core-legacy-ra/classes"
classpath="${core.classes}" compiler="weblogic" />

- Add a stubversion

<rmic classname="com.bea.crmsimulation.legacyra.LegacyAdapter"
base="${module_location}/core-legacy-ra/classes"
classpath="${core.classes}" compiler="weblogic"
stubversion="1.2"/>

- Remove the compiler flag

<rmic classname="com.bea.crmsimulation.legacyra.LegacyAdapter"
base="${module_location}/core-legacy-ra/classes"
classpath="${core.classes}"

12.28 Security Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.28.1, "StoreBootIdentity Works Only if the Appropriate Server Security Directory Exists"

- Section 12.28.2, "Boot Time Failure Occurs With SecurityServiceException"

- Section 12.28.3, "Authentication Failure After Upgrading a Domain From WLS 6.1"

- Section 12.28.4, "InvalidParameterException Message Generated and Displayed"

- Section 12.28.5, "Enabling Both the Authentication and Passive Attributes In SML 2.0 Service Provider Services Is an Invalid Configuration"

- Section 12.28.6, "Running the WebLogic Full Client in a Non-Forked VM"

12.28.1 StoreBootIdentity Works Only if the Appropriate Server Security Directory Exists

The option -Dweblogic.system.StoreBootIdentity works only if the appropriate server security directory exists. This directory is usually created by the Configuration Wizard or upgrade tool.

However, the appropriate server security directory could be absent in domains checked into source-control systems.

12.28.2 Boot Time Failure Occurs With SecurityServiceException

A WebLogic Server instance can experience a boot time failure with a SecurityServiceException when the RDBMS Security Data Store is configured for a DB2 database using the DB2 driver supplied with WebLogic Server.

Workaround

When RDBMS Security Data Store is using the AlternateId connection property for a DB2 database, you must also set the additional property BatchPerformanceWorkaround as true when using the DB2 driver supplied with WebLogic Server.

12.28.3 Authentication Failure After Upgrading a Domain From WLS 6.1

After upgrading a domain from WLS 6.1, the WebLogic Server instance will not boot due to an authentication failure.

Workaround

A system user password must be set up in the WLS 6.1 domain before or after the upgrade process in order for the WebLogic Server instance to boot properly.

12.28.4 InvalidParameterException Message Generated and Displayed

After you configure either the Identity Provider or Service Provider services for SAML 2.0 and attempt to publish the SAML 2.0 services metadata file, an InvalidParameterException message may be generated and displayed in the Administration Console.

Workaround

When configuring the SAML 2.0 federation services for a WebLogic Server instance, be sure to enable all binding types that are available for the SAML role being configured. For example, when configuring SAML 2.0 Identity Provider services, you should enable the POST, Redirect, and Artifact bindings. When configuring SAML 2.0 Service Provider services, enable the POST and Artifact bindings. Optionally, you may choose a preferred binding.

12.28.5 Enabling Both the Authentication and Passive Attributes In SML 2.0 Service Provider Services Is an Invalid Configuration

When configuring SAML 2.0 Service Provider services, enabling both the Force Authentication and Passive attributes is an invalid configuration that WebLogic Server is unable to detect. If both these attributes are enabled, and an unauthenticated user attempts to access a resource that is hosted at the Service Provider site, an exception is generated and the single sign-on session fails.

Note that the Force Authentication attribute has no effect because SAML logout is not supported in WebLogic Server. So even if the user is already authenticated at the Identity Provider site and Force Authentication is enabled, the user is not forced to authenticate again at the Identity Provider site.

Avoid enabling both these attributes.

12.28.6 Running the WebLogic Full Client in a Non-Forked VM

If the WebLogic Full Client is running in a non-forked VM, for example by means of a <java> task invoked from an Ant script without the fork=true attribute, the following error might be generated:

java.lang.SecurityException: The provider self-integrity check failed.

This error is caused by the self-integrity check that is automatically performed when the RSA Crypto-J library is loaded. (The Crypto-J library, cryptoj.jar, is in the wlfullclient.jar manifest classpath.)

This self-integrity check failure occurs when the client is started in a non-forked VM and it uses the Crypto-J API, either directly or indirectly, as in the following situations:

- The client invokes the Crypto-J library directly.

- The client attempts to make a T3S connection, which triggers the underlying client SSL implementation to invoke the Crypto-J API.

When the self-integrity check fails, further invocations of the Crypto-J API fail.

Workaround

When running the full client in a <java> task that is invoked from an Ant script, always set the fork attribute to true.

For more information about the self-integrity check, see "How a Provider Can Do Self-Integrity Checking" in How to Implement a Provider in the Java™ Cryptography Architecture, available at the following URL:

http://download.oracle.com/javase/6/docs/technotes/guides/security/crypto/HowToImplAProvider.html#integritycheck

12.29 SNMP Issues and Workarounds

There are no known SNMP issues in this release of WebLogic Server.

12.30 Spring Framework on WebLogic Server Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.30.1, "OpenJPA ClassFileTranformer Does Not Work When Running on JRockit"

- Section 12.30.2, "petclinic.ear Does Not Deploy on WebLogic Server"

12.30.1 OpenJPA ClassFileTranformer Does Not Work When Running on JRockit

The OpenJPA ClassFileTranformer does not work when running WebLogic Server on JRockit.

Workaround

Use an alternative method of applying enhancements at build time through an OpenJPA enhancer compiler; do not use the LoadTimeWeaver.

12.30.2 petclinic.ear Does Not Deploy on WebLogic Server

For the SpringSource petclinic sample, the petclinic.war deploys without any problems. The petclinic.ear will not deploy on WebLogic Server because it is not packaged correctly. A request has been sent to SpringSource to fix the petclinic.ear packaging.

12.31 System Component Architecture (SCA) Issues and Workarounds

There are no known SCA issues in this release of WebLogic Server.

12.32 Upgrade Issues and Workarounds

This section describes the following issue:

- Section 12.32.1, "Domains Created on WebLogic Server 10.3.1 Cannot Be Run on WebLogic Server 10.3"

12.32.1 Domains Created on WebLogic Server 10.3.1 Cannot Be Run on WebLogic Server 10.3

If you create a domain using WebLogic Server 10.3.1, then roll back to WebLogic Server 10.3, you will not be able to start the servers that you created in that domain. This is a known restriction, as the config.xml file contains references to newer schema definitions (xmlns.oracle.com) that did not exist in WebLogic Server 10.3.

12.33 Web Applications Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.33.1, "Administration Console Fails to Implement session-timeout Changes"

- Section 12.33.2, "Connection Pool Connection Reserve Timeout Seconds Value is Overridden"

- Section 12.33.3, "Database Connections Become Unstable When a PoolLimitSQLException Occurs"

- Section 12.33.4, "Web Page Fails to Open When Accessing It Using the SSL Port"

12.33.1 Administration Console Fails to Implement session-timeout Changes

If the session-timeout is configured in the web.xml file, any changes made to change the session-timeout using the Administration Console do not take effect.

Workaround

Use a deployment plan to override the session-timeout setting.

12.33.2 Connection Pool Connection Reserve Timeout Seconds Value is Overridden

When using a JDBC session, the value of Connection Reserve Timeout Seconds for a connection pool is changed to be one of the following:

- the JDBC connection timeout seconds, which is defined in the session descriptor (either in weblogic.xml or weblogic-application.xml)

- the default value of 120 seconds

Workaround

Configure jdbc-connection-timeout-secs in the session descriptor.

12.33.3 Database Connections Become Unstable When a PoolLimitSQLException Occurs

When a PoolLimitSQLException occurs during a JDBC persistence session, connections to the database become unstable, and may fail with recovery or fail without recovery. This results in the loss of session data. Either an older session or null is returned.

12.33.4 Web Page Fails to Open When Accessing It Using the SSL Port

When accessing a Web page using the SSL port, the page fails to open and the following error is reported:

Secure Connection Failed

An error occurred during a connection to <hostname>.

You have received an invalid certificate. Please contact the server
administrator or email correspondent and give them the following information:

Your certificate contains the same serial number as another certificate
issued by the certificate authority. Please get a new certificate containing a unique serial number.

Workaround

The following workaround can be used for Firefox.

If you have received this error and are trying to access a web page that has a self-signed certificate, perform the following steps in Firefox:

1. Go to Tools > Options >Advanced > Encryption tab > View Certificates.

2. On the Servers tab, remove the certificates.

3. On the Authorities tab, find the Certificate Authority (CA) for the security device that is causing the issue, and then delete it.

If you are using Internet Explorer or other web browsers, you can ignore the Warning page that appears and continue to the web page.

12.34 WebLogic Server Scripting Tool (WLST) Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.34.1, "Permission Denied Error Occurs for WLST Offline Logging"

- Section 12.34.2, "Property Names Containing '.' Characters Are Not Supported by loadProperties"

- Section 12.34.3, "Invalid cachedir Created by Jython Causes WLST to Error Out"

- Section 12.34.4, "WLST returnType='a' Option Returns Child Management Objects"

12.34.1 Permission Denied Error Occurs for WLST Offline Logging

When there are multiple processes, owned by different filesystem users, that are performing concurrent WLST offline operations, a FileNotFoundException, Permission Denied error may occur.

Workaround

To avoid collisions on log file names, set the following property in the environment prior to invoking wlst.sh script_name:

export WLST_PROPERTIES="-Dwlst.offline.log=./logs/filename.log"

Substitute a unique name for filename. You must you use a unique name for each log file to ensure that there will be no log file name collisions.

12.34.2 Property Names Containing '.' Characters Are Not Supported by loadProperties

The WLST loadProperties command does not support loading a property with a name that contains "." characters. For example, if the property myapp.db.default is present in the property file, WLST throws a name exception:

Problem invoking WLST - Traceback (innermost last):
File "<iostream>", line 7, in ?
File "<iostream>", line 4, in readCustomProperty
NameError: myapp

This is a system limitation of Python and the loadProperties command. WLST reads the variable names and values and sets them as variables in the Python interpreter. The Python interpreter uses "." as a delimiter to indicate module scoping for the namespace, or package naming, or both. Therefore, the properties file fails because myapp.db.default.version=9i is expected to be in the myapp.db.default package. This package does not exist.

Workaround

Use variable names that do not have periods. This will allow you to load the variables from the property file and refer to them in WLST scripts. You could use another character such as "_" or lowercase/uppercase character to delimit the namespace.

As an alternative, you can set variables from a properties files. When you use the variables in your script, during execution, the variables are replaced with the actual values from the properties file. For example:

myapp.py
var1=10
var2=20
import myapp
print myapp.var1
10
print myapp.var2
20

This will work for one level of namespaces (myapp.var1, myapp.var2). It will not work for top level variables that share the same name as the namespace (for example, myapp=oracle and myapp.var1=10). Setting the myapp variable will override the myapp namespace.

If you need multiple levels, then you can define a package namespace using directories. Create a myapp/db/default directory with a vars.py file as follows:

var1=10
var2=20

Then import:

import myapp.db.default.vars
print myapp.db.default.vars.var1
10

You may need to add __init__.py files to the subdirectories. Refer to the Python documentation for more information on packages:

http://docs.python.org/tut/node8.html

12.34.3 Invalid cachedir Created by Jython Causes WLST to Error Out

The default cachedir created by Jython 2.2 is not a valid directory. If you are using Jython directly from weblogic.jar, this causes WLST to error out.

Workaround

There are two workarounds for this issue:

- When invoking WLST, specify the -Dpython.cachedir=<valid_directory> parameter, or

- Install Jython 2.2.1 separately instead of using the partial Jython that is included in weblogic.jar.

12.34.4 WLST returnType='a' Option Returns Child Management Objects

The WLST returnType='a' option should only return attributes from the specified directory. Instead it also returns child management objects. For example:

ls('Server')
drw-   AdminServer
drw-   worker01

ls('Server', returnMap='true', returnType='a')
drw-   AdminServer
drw-   worker01

ls('Server', returnMap='true',returnType='c')
drw-   AdminServer
drw-   worker01

The ls with returnType='a' should not list any child management objects, but AdminServer and worker01 are children.

Workaround

When processing the output from ls(returnType='a'), check to see if the returned entry is a directory.

12.35 Web Server Plug-Ins Issues and Workarounds

This section describes the following issue:

- Section 12.35.1, "MOD_WLS_OHS Does Not Fail Over"

12.35.1 MOD_WLS_OHS Does Not Fail Over

Currently, mod_wl and mod_wl_ohs only support container level failover and not application level failover. mod_wl_ohs continues to route requests to a down application as long as the managed server is up and running. In the clustered case, requests continue to go to the container where the original session started even when the application is shutdown, typically resulting in the http error 404.

12.36 Web Services and XML Issues and Workarounds

This section describes the following issues and workarounds:

- Section 12.36.1, "weblogic.wsee.jaxws.mdb.DispatchPolicy WorkManager Cannot Be Found"

- Section 12.36.2, "Multiple Resize Buffer Calls Occur"

- Section 12.36.3, "Troubleshooting Problems When Applying the WebLogic Advanced Web Services for JAX-WS Extension Template"

- Section 12.36.4, "Sparse Arrays and Partially Transmitted Arrays Are Not Supported"

- Section 12.36.5, "WSDL Compiler Does Not Generate Serializable Data Types"

- Section 12.36.6, "Use of Custom Exception on a Callback"

- Section 12.36.7, "Cannot Use JMS Transport in an Environment That Also Uses a Proxy Server"

- Section 12.36.8, "clientgen Fails When Processing a WSDL"

- Section 12.36.9, "JAX RPC Handlers in Callback Web Services Are Not Supported"

- Section 12.36.10, "Message-level Security in Callback Web Services Is Not Supported"

- Section 12.36.11, "Handling of Java Method Arguments or Return Parameters That Are JAX-RPC-style JavaBeans"

- Section 12.36.12, "IllegalArgumentException When Using a Two-Dimensional XML Object in a JWS Callback"

- Section 12.36.13, "Using SoapElement[] Results in Empty Array"

- Section 12.36.14, "FileNotFound Exception When a Web Service Invokes Another Web Service"

- Section 12.36.15, "Client Side Fails to Validate the Signature on the Server Response Message"

- Section 12.36.16, "xmlcatalog Element Entity Cannot Be a Remote File or a File in an Archive"

- Section 12.36.17, "Catalog File's public Element Is Not Supported When Using XML Catalogs"

- Section 12.36.18, "Local xmlcatalog Element Does Not Work Well"

- Section 12.36.19, "JAXRPC Client Does Not Encode the HTTP SOAPAction Header With Multi-byte Characters"

- Section 12.36.20, "External Catalog File Cannot Be Used in the xmlcatalog Element of clientgen"

- Section 12.36.21, "Exceptions When Running Reliable Messaging Under Heavy Load"

- Section 12.36.22, "ClassNotFound Exception Occurs When Using wseeclient.jar"

- Section 12.36.23, "Incomplete Configuration When Adding Advanced Web Services Component to SOA Domain"

- Section 12.36.24, "WS-AT Interoperation Issues With WebSphere and WebLogic Server"

12.36.1 weblogic.wsee.jaxws.mdb.DispatchPolicy WorkManager Cannot Be Found

In some situations, warning messages are logged indicating that the weblogic.wsee.jaxws.mdb.DispatchPolicy WorkManager cannot be found, although this WorkManager is targeted to one or more of the Managed Servers in the domain.

Workaround

Use one of the following workarounds to resolve this issue.

- To prevent these warning messages, start the WebLogic Server instance with the -Dweblogic.wsee.skip.async.response=true flag. See Programming Advanced Features of JAX-RPC Web Services for Oracle WebLogic Server for more information on this flag.

- Manually target the weblogic.wsee.jaxws.mdb.DispatchPolicy WorkManager to the Administration Server.

12.36.2 Multiple Resize Buffer Calls Occur

When executing Web services client calls where Message Transmission Optimization Mechanism (MTOM) attachments are processed for send, multiple resize buffer calls occur..

Workaround

There is a patch available to resolve this issue. This patch can be applied only to WebLogic Server 10.3.4. It provides the system property jaxws.transport.streaming, which enables or disables streaming at the transport layer for a Web services client. Set this property to true for CPU-intensive applications that are running on a WebLogic Server instance that is participating in Web services interactions as a client, and is sending out large messages.

To obtain the patch, do one of the following:

- Contact My Oracle Support and request the patch for bug 9956275, or

- Download the patch from My Oracle Support and install it using Smart Update per the instructions in the following My Oracle Support document:
1302053.1

Search for Oracle patch number 9956275 or Smart Update patch 7Z5H.

12.36.3 Troubleshooting Problems When Applying the WebLogic Advanced Web Services for JAX-WS Extension Template

After upgrading from WebLogic Server 10.3.4 to 10.3.5, when creating or extending a domain using the WebLogic Advanced Web Services for JAX-WS Extension template (wls_webservices_jaxws.jar), you may encounter an exception during the execution of the final.py script. For complete details and a workaround, see "Troubleshooting Problems When Applying the WebLogic Advanced Services for JAX-WS Extension Template" in Getting Started With JAX-WS Web Services for Oracle WebLogic Server.

12.36.4 Sparse Arrays and Partially Transmitted Arrays Are Not Supported

WebLogic Server does not support Sparse Arrays and Partially Transmitted Arrays as required by the JAX-RPC 1.1 Spec.

12.36.5 WSDL Compiler Does Not Generate Serializable Data Types

The Web Service Description Language (WSDL) compiler does not generate serializable data types, so data cannot be passed to remote EJBs or stored in a JMS destination.

12.36.6 Use of Custom Exception on a Callback

WebLogic Server does not support using a custom exception on a callback that has a package that does not match the target namespace of the parent Web Service.

Workaround

Make sure that any custom exceptions that are used in callbacks are in a package that matches the target namespace of the parent Web service.

12.36.7 Cannot Use JMS Transport in an Environment That Also Uses a Proxy Server

You cannot use JMS transport in an environment that also uses a proxy server. This is because, in the case of JMS transport, the Web Service client always uses the t3 protocol to connect to the Web Service, and proxy servers accept only HTTP/HTTPS.

12.36.8 clientgen Fails When Processing a WSDL

clientgen fails when processing a WSDL that uses the complex type http://www.w3.org/2001/XMLSchema{schema} as a Web Service parameter.

12.36.9 JAX RPC Handlers in Callback Web Services Are Not Supported

WebLogic Server 9.2 and later does not support JAX RPC handlers in callback Web Services.

Workaround

If JAX RPC handlers were used with Web Services created with WebLogic Workshop 8.1, then such applications must be redesigned so that they do not use callback handler functionality.

12.36.10 Message-level Security in Callback Web Services Is Not Supported

WebLogic Server 9.2 and later does not support message-level security in callback Web Services.

Workaround

Web Services created with WebLogic Workshop 8.1 that used WS-Security must be redesigned to not use message-level security in callbacks.

12.36.11 Handling of Java Method Arguments or Return Parameters That Are JAX-RPC-style JavaBeans

WebLogic Server does not support handling of Java method arguments or return parameters that are JAX-RPC-style JavaBeans that contain an XmlBean property. For example, applications cannot have a method with a signature like this:

void myMethod(myJavaBean bean);

where myJavaBean class is like:

public class MyJavaBean {
private String stringProperty;
private XmlObject xmlObjectProperty;

public MyJavaBean() {}
String getStringProperty() {
return stringProperty;
}
void   setStringProperty(String s) {
stringProperty = s;
}
XmlObject getXmlObjectProperty() {
return xmlObjectProperty;
}
void      getXmlObjectProperty(XmlObject x) {
xmlObjectProperty = x;
}
}

Workaround

Currently there is no known workaround for this issue.

12.36.12 IllegalArgumentException When Using a Two-Dimensional XML Object in a JWS Callback

Using a two dimensional XmlObject parameter (XmlObject[][]) in a JWS callback produces an IllegalArgumentException.

Workaround

Currently there is no known workaround for this issue.

12.36.13 Using SoapElement[] Results in Empty Array

Using SoapElement[] as a Web Service parameter with @WildcardBinding(className="javax.xml.soap.SOAPElement[]", binding=WildcardParticle.ANYTYPE) will always result in an empty array on the client.

Workaround

Do not use the @WildcardBinding annotation to change the default binding of SOAPElement[] to WildcardParticle.ANYTYPE. The SOAPElement[] default binding is set to WildcardParticle.ANY.

12.36.14 FileNotFound Exception When a Web Service Invokes Another Web Service

When Web Service A wants to invoke Web Service B, Web Service A should use the @ServiceClient annotation to do this. If Web Service B needs a custom policy file that is not attached to the WSDL for Web Service B, then Web Service A will fail to run. Web Service A will look for the policy file at /Web-Inf/classes/policies/filename.xml. Since no policy file exists at that location, WebLogic Server will throw a 'file not found' exception.

Workaround

Attach the custom policy file to Web Service B, as in this example:

@Policy(uri="CustomPolicy.xml",
attachToWsdl=true)
public class B {
...
}

12.36.15 Client Side Fails to Validate the Signature on the Server Response Message

When the security policy has one of these Token Assertions, the client side may fail to validate the signature on the server response message.

<sp:WssX509PkiPathV1Token11/>
<sp:WssX509Pkcs7Token11/>
<sp:WssX509PkiPathV1Token10/>
<sp:WssX509Pkcs7Token10/>

In addition, when there are more than two certifications in the chain for X509 certification for <sp:WssX509Pkcs7Token11/> or <sp:WssX509Pkcs7Token10/> Token Assertion, the server side may fail to validate the signature on the incoming message.

A policy such as the following policy is not supported, unless the entire certificate chain remains on the client side.

<sp:AsymmetricBinding>
<wsp:Policy>
<sp:InitiatorToken>
<wsp:Policy>
<sp:X509Token
sp:IncludeToken='. . ./IncludeToken/AlwaysToRecipient'>

<wsp:Policy>
<sp:WssX509Pkcs7Token11/>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:InitiatorToken>
<sp:RecipientToken>
<wsp:Policy>
<sp:X509Token sp:IncludeToken='. . ./IncludeToken/Never'>
<wsp:Policy>
<sp:WssX509Pkcs7Token11/>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:RecipientToken>
. . .
</wsp:Policy>
</sp:AsymmetricBinding>

Workaround

Use either of the following two solutions:

1. Configure the response with the <sp:WssX509V3Token10/> Token Assertion, instead of WssX509PkiPathV1Token11/>. The policy will look like this:

<sp:AsymmetricBinding>
<wsp:Policy>
<sp:InitiatorToken>
<wsp:Policy>
<sp:X509Token sp:IncludeToken='. . ./IncludeToken/AlwaysToRecipient'>
<wsp:Policy>
WssX509PkiPathV1Token11/>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:InitiatorToken>
<sp:RecipientToken>
<wsp:Policy> sp:IncludeToken='. . ./IncludeToken/Never'>
<sp:X509Token
<wsp:Policy>
<sp:WssX509V3Token10/>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:RecipientToken>
. . .
</wsp:Policy>
</sp:AsymmetricBinding>

2. Configure the response with the WssX509PkiPathV1Token11/> token assertion, but include it in the message. The policy will look like this:

<sp:AsymmetricBinding>
<wsp:Policy>
<sp:InitiatorToken>
<wsp:Policy>
<sp:X509Token sp:IncludeToken='. . ./IncludeToken/AlwaysToRecipient'>
<wsp:Policy>
WssX509PkiPathV1Token11/>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:InitiatorToken>
<sp:RecipientToken>
<wsp:Policy>
<sp:X509Token sp:IncludeToken='. . ./IncludeToken/AlwaysToInitiator'>
<wsp:Policy>
WssX509PkiPathV1Token11/>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:RecipientToken>
. . .
</wsp:Policy>
</sp:AsymmetricBinding>

When there are multiple certifications in the X509 Certificate chain, WssX509PkiPathV1Token11/> or <sp:WssX509PkiPathV1Token10/> should be used, instead of <sp:WssX509Pkcs7Token11/> or <sp:WssX509Pkcs7Token10/>.

12.36.16 xmlcatalog Element Entity Cannot Be a Remote File or a File in an Archive

For the xmlcatalog element in build.xml, the location of an entity must be a file on the local file system. It cannot be a remote file (for example, http:) or a file in an archive (for example, jar:).

Workaround

If necessary, define the remote element as an entity in a catalog file instead.

12.36.17 Catalog File's public Element Is Not Supported When Using XML Catalogs

The public element in a catalog file is not supported when using the XML Catalogs feature. It is not supported to be consistent with JAX-WS EntityResolver implementation. WebLogic Server only supports defining the system element in a catalog file.

12.36.18 Local xmlcatalog Element Does Not Work Well

The local xmlcatalog element does not work well due to an Ant limitation.

Workaround

In the ant build.xml file, you have to define a local element above a clientgen(wsdlc) task when you are in the same target, or define the element out of any targets.

12.36.19 JAXRPC Client Does Not Encode the HTTP SOAPAction Header With Multi-byte Characters

The WebLogic Server Web Service JAXRPC client doesn't encode the HTTP SOAPAction header with multi-byte characters, but WebLogic Server only supports ASCII for HTTP headers.

Workaround

Change the SOAP action to ASCII in the WSDL.

12.36.20 External Catalog File Cannot Be Used in the xmlcatalog Element of clientgen

An external catalog file cannot be used in the xmlcatalog element of a clientgen task. For example, this snippet of an ant build file will not work:

<clientgen ...
<xmlcatalog>
<catalogpath>
<pathelement location='wsdlcatalog.xml'/>
</catalogpath>
</xmlcatalog>

This is a limitation of the Ant XML Catalog.

Workaround

Resource locations can be specified either in-line or in an external catalog file(s), or both. In order to use an external catalog file, the xml-commons resolver library (resolver.jar) must be in your classpath. External catalog files may be either plain text format or XML format. If the xml-commons resolver library is not found in the classpath, external catalog files, specified in <catalogpath> paths, will be ignored and a warning will be logged. In this case, however, processing of inline entries will proceed normally.

Currently, only <dtd> and <entity> elements may be specified inline. These correspond to the OASIS catalog entry types PUBLIC and URI respectively.

12.36.21 Exceptions When Running Reliable Messaging Under Heavy Load

When running a Web services reliable messaging scenario under heavy load with file based storage that has the Direct-Write synchronous write policy setting, you may encounter IO exceptions similar to the following in the WebLogic Server log:

weblogic.store.PersistentStoreRuntimeException: [Store:280029]The
persistent store record <number> could not be found

or

Could not load conversation with id uuid:<some ID> -> Conversation read
failed:
...
weblogic.wsee.jws.conversation.StoreException:
Conversation read failed: id=uuid:<some ID>
weblogic.store.PersistentStoreException: [Store:280052]The
persistent store was not able to read a record.
java.io.OptionalDataException

These exceptions are known to occur only when using Web Services reliable messaging. They indicate a failure to read a record from the file store and are considered 'fatal' data access errors.

The underlying issue causing these errors will be addressed in a future release.

Workaround

The following workarounds are available for this issue:

- Change the file store synchronous write policy to Direct-Write-With-Cache
or

- Change the file store synchronous write policy to Cache-Flush.
or

- Keep the Direct-Write synchronous write policy and add the following Java system property to your WebLogic server startup scripts:

-Dweblogic.store.AvoidDirectIO=true

Note:

The -Dweblogic.store.AvoidDirectIO system property has been deprecated in WebLogic Server 10.3.4. Oracle recommends configuring the store synchronous write policy to Direct-Write-With-Cache instead.

The Direct-Write-With-Cache option may improve performance; it creates additional files in the operating system's temporary directory by default.

The Cache-Flush and AvoidDirectIO workarounds may lead to some performance degradation; it may be possible to reduce or eliminate the degradation by configuring a different block-size for the file store.

For important information about these settings and additional options, see "Tuning File Stores" in Oracle Fusion Middleware Performance and Tuning for Oracle WebLogic Server.

12.36.22 ClassNotFound Exception Occurs When Using wseeclient.jar

Stand-alone JAX-WS clients are not supported in this release.

Workaround

Use the client-side JAX-WS 2.1 that is integrated with the Java Standard Edition Release 6 (JDK 1.6), Update 4 and later. This requires using the JAX-WS API instead of any WebLogic Server specific APIS.

Current releases of JDK 1.6 are available for download at http://java.sun.com/javase/downloads/index.jsp. For information about writing a standalone JAX WS 2.1 client application, see the JAX-WS Users Guide on the JAX-WS 2.1 Reference Implementation Web site at http://jax-ws.java.net/2.2.6/docs/ch03.html.

12.36.23 Incomplete Configuration When Adding Advanced Web Services Component to SOA Domain

An incomplete configuration can result when you use the Configuration Wizard to add the WebLogic Server Advanced Web Services component to a newly created SOA domain. If you create a cluster that contains only the default 'out-of-the-box' soa_server1 server definition, the resulting cluster does not include the resources needed to run WebLogic Server Web Services in that cluster.

Workaround

Use either of the following workarounds for this issue:

1. While running Configuration Wizard, create a second server in the cluster:

1. On the Select Optional Configuration screen, select Managed Servers, Clusters, and Machines.

2. On the Configure Managed Servers screen, add a managed server.

3. On the Assign Servers to Clusters screen, add this server to the cluster in which the default soa_server1 server resides.

2. On the Configuration Wizard Target Services to Servers or Clusters screen, target Web Services resources (for example, WseeJmsServer, WseeJmsModule) to the cluster.

Either of these workarounds will cause the Configuration Wizard to apply the resources for the WebLogic Server Advanced Web Services component to the cluster.

12.36.24 WS-AT Interoperation Issues With WebSphere and WebLogic Server

Web Services Atomic Transactions (WS-AT) 1.1 interoperation using WebSphere as the client and either WebLogic Server or JRF as the service does not work.

WS-AT 1.1 interoperation does work when WebSphere is the service and either WebLogic Server or JRF is the client. In this case, interoperation works only if you have WebSphere 7 with Fix/Feature Pack 7.

12.37 WebLogic Tuxedo Connector Issues and Workarounds

This section describes the following issue and workaround:

- Section 12.37.1, "View Classes are not Set on a Per Connection Basis"

12.37.1 View Classes are not Set on a Per Connection Basis

View classes are not set on a per connection basis.

A shared WebLogic Tuxedo Connector hash table can cause unexpected behavior in the server if two applications point to the same VIEW name with different definitions. There should be a hash table for the view classes on the connection as well as for the Resource section.

Workaround

Ensure that all VIEW classes defined across all your WebLogic Workshop applications are consistent, meaning that you have the same VIEW name representing the same VIEW class.

12.38 Documentation Errata

This section describes documentation errata:

- Section 12.38.1, "Japanese Text Displays in Some Search Results Topics Avitek Medical Records"

- Section 12.38.2, "HTML Pages For Downloaded Libraries Do Not Display Properly"

- Section 12.38.3, "Evaluation Database Component Is Not Listed For silent.xml"

- Section 12.38.4, "Instructions for Reliable SOAP Messaging Code Example Are Incorrect"

12.38.1 Japanese Text Displays in Some Search Results Topics Avitek Medical Records

The samples viewer Search function may sometimes return topics that display the Japanese and English versions of some Avitek Medical Records topics simultaneously.

12.38.2 HTML Pages For Downloaded Libraries Do Not Display Properly

After extracting the WebLogic Server documentation library ZIP files that are available from http://www.oracle.com/technetwork/middleware/weblogic/documentation/index.html, the HTML pages may not display properly in some cases for the following libraries:

- E12840_01 (WebLogic Server 10.3.0 documentation library)

- E12839_01 (Weblogic Server 10.3.1 documentation library)

- E14571_01 (WebLogic Server 10.3.3 documentation library)

Workarounds

For library E12840-01, after extracting the E12840_01.zip library file, if the HTML pages are not formatting correctly, perform the following steps:

1. Go to the directory in which you extracted the zip file.

2. Locate the /global_resources directory in the directory structure.

3. Copy the /global_resources directory to the root directory of the same drive.

For libraries E12839-01 and E14571-01, this issue occurs only on Windows operating systems. If the HTML pages of the extracted library are not formatting correctly, try extracting the ZIP file using another extraction option in your unzip utility. For example, if you are using 7-Zip to extract the files, select the Full pathnames option. Note that you cannot use the Windows decompression utility to extract the library ZIP file.

12.38.3 Evaluation Database Component Is Not Listed For silent.xml

In the WebLogic Server Installation Guides for WebLogic Server 10.3.3 and 10.3.4, the Evaluation Database is not listed as an installable component in Table 5-1 of Chapter 5, "Running the Installation Program in Silent Mode.:" The following entry should be included in the Component Paths row:

WebLogic Server/Evaluation Database

The Evaluation Database component is automatically installed if the Server Examples component is included in silent.xml. Therefore, it does not have to be explicitly included in silent.xml. If, however, you do not install the Server Examples, but you want to install the Evaluation Database, you must include WebLogic Server/Evaluation Database in silent.xml.

12.38.4 Instructions for Reliable SOAP Messaging Code Example Are Incorrect

The instructions for the "Configuring Secure and Reliable SOAP Messaging for JAXWS Web Services" example are a copy of the instructions for the "Using Make Connection and Reliable Messaging for JAX-WS Web Service" example.

The correct instructions for the "Configuring Secure and Reliable SOAP Messaging for JAXWS Web Services" example are provided here.

12.38.4.1 About the Example

This example shows how to configure secure, reliable messaging for JAX-WS Web services. The example includes the following WebLogic Web services:

- Web service whose operations can be invoked using reliable and secure SOAP messaging (destination endpoint).

- Client Web service that invokes an operation of the first Web service in a reliable and secure way (source endpoint).

Overview of Secure and Reliable SOAP Messaging

Web service reliable messaging is a framework that enables an application running on one application server to reliably invoke a Web service running on another application server, assuming that both servers implement the WS-RelicableMessaging specification. Reliable is defined as the ability to guarantee message delivery between the two endpoints (Web service and client) in the presence of software component, system, or network failures.

WebLogic Web services conform to the WS-ReliableMessaging 1.2 specification (February 2009) and support version 1.1. This specification describes how two endpoints (Web service and client) on different application servers can communicate reliably. In particular, the specification describes an interoperable protocol in which a message sent from a source endpoint (or client Web service) to a destination endpoint (or Web service whose operations can be invoked reliably) is guaranteed either to be delivered, according to one or more delivery assurances, or to raise an error.

WebLogic Web services use WS-Policy files to enable a destination Web service to describe and advertise its reliable SOAP messaging capabilities and requirements. WS-Policy files are XML files that describe features such as the version of the WS-ReliableMessaging specification that is supported, the source Web service retransmission interval, the destination Web service acknowledgment interval, and so on.

Overview of the Example

This example uses JWS annotations to specify the shape and behavior of the Web services. It describes additional JWS annotations to enable reliable and secure SOAP messaging in the destination Web service and to reliably invoke an operation from the source Web service in a secure way.

The destination ReliableEchoService Web service has two operations that can be invoked reliably and in a secure way: echo and echoOneway. The JWS file that implements this Web service uses the @Policies and @Policy JWS annotations to specify the WS-Policy file, which contains the reliable and secure SOAP messaging assertions.

The source ClientService Web service has one operation for invoking the echo operations of the ReliableEchoService Web service reliably and in a secure way within one conversation: runTestEchoWithRes. The JWS file that implements the ClientService Web service uses the @WebServiceRef JWS annotation to specify the service name of the reliable Web service being invoked.

To generate the Web services, use the jwsc WebLogic Web service Ant task, as shown in the build.xml file. The jwsc target generates the reliable and secure Web service and the jwsc-client-app target creates the source Web service that invoke the echo operations of the ReliableEchoService Web service. The jwsc Ant task compiles the JWS files, and generates the additional files needed to implement a standard J2EE Enterprise Web service, including the Web service deployment descriptors, the WSDL file, data binding components, and so on. The Ant task automatically generates all the components into an Enterprise Application directory structure that you can then deploy to WebLogic Server. This example uses the wldeploy WebLogic Ant task to deploy the Web service.

The jwsc-client-app target also shows how you must first execute the clientgen Ant task to generate the JAX-WS stubs for the destination ReliableEchoService Web service, compile the generated Java source files, and then use the classpath attribute of jwsc to specify the directory that contains these classes so that the ClientServiceImpl.java class can find them.

The WsrmJaxwsExampleRequest.java class is a standalone Java application that invokes the echo operation of the source Web service. The client target of the build.xml file shows how to run clientgen, and compile all the generated Java files and the WsrmJaxwsExampleRequest.java application.

12.38.4.2 Files Used in This Example

Directory Location: MW_HOME/wlserver_10.3/samples/server/examples/src/examples/webservices/wsrm_jaxws/wsrm_jaxws_security

MW_HOME represents the Oracle Fusion Middleware home directory.

File

Description

ClientServiceImpl.java

JWS file that implements the source Web service that reliably invokes the echo operation of the ReliableEchoService Web service in a secure way.

ReliableEchoServiceImpl.java

JWS file that implements the reliable destination Web service. This JWS file uses the @Policies and @Policy annotation to specify a WS-Policy file that contains reliable and secure SOAP messaging assertions.

client/WsrmJaxwsExampleRequest.java

Standalone Java client application that invokes the source WebLogic Web service, that in turn invokes an operation of the ReliableEchoervice Web service in a reliable and secure way.

ws_rm_configuration.py

WLST script that configures the components required for reliable SOAP messaging. Execute this script for the WebLogic Server instance that hosts the reliable destination Web service. The out-of-the-box Examples server has already been configured with the resources required for the source Web service that invokes an operation reliably.

configWss.py

WLST script that configures the components required for secure SOAP messaging. Execute this script for the WebLogic Server instance that hosts the source Web service. Remember to restart the source WebLogic Server after executing this script.

configWss_Service.py

WLST script that configures the components required for secure SOAP messaging. Execute this script for the WebLogic Server instance that hosts the destination Web service. Remember to restart the destination WebLogic Server after executing this script.

certs/serverKeyStore.jks

Server-side key store used to create the server-side BinarySecurityToken credential provider.

certs/clientKeyStore.jks

Client-side key store used to create the client-side BinarySecurityToken credential provider.

jaxws-binding.xml

XML file that describes the package name of the generated code and indicate the client side code needs to contain asynchronous invocation interface.

build.xml

Ant build file that contains targets for building and running the example.

12.38.4.3 Prepare the Example

This section describes how to prepare the example.

Prerequisites

Before working with this example:

1. Install Oracle WebLogic Server, including the examples.

2. Start the Examples Server.

3. Set up your environment.

Configure the Destination WebLogic Server Instance (Optional)

The default configuration for this example deploys both the source and destination Web services to the Examples server. You can use this default configuration to see how the example works, but it does not reflect a real life example of using reliable and secure SOAP messaging in which the source Web service is deployed to a WebLogic Server that is different from the one that hosts the destination Web service. This section describes how to set up the real life example.

The example includes WebLogic Server Scripting Language (WLST) scripts that are used to configure:

- Store-and-forward (SAF) service agent

- File store

- JMS server

- JMS module

- JMS subdeployment

- JMS queues

- Logical store

- Credential provider for Security Context Token

- Credential provider for Derived Key

- Credential provider for x.509

- KeyStores for Confidentiality and Integrity

- PKI CreditMapper

Follow these steps if you want to deploy the secure and reliable destination Web service to a different WebLogic Server instance:

1. If the managed WebLogic Server to which you want to deploy the reliable JAX-WS Web service does not exist, create it.

2. Change to the SAMPLES_HOME\server\examples\src\examples\webservices\wsrm_jaxws\wsrm_jaxws_security directory, where SAMPLES_HOME refers to the main WebLogic Server examples directory, such as c:\Oracle\Middleware\wlserver_10.3\samples.

3. Edit the build.xml file and update the following property definitions to ensure that the reliable JAX-WS Web service is deployed to the destination WebLogic Server:

<property name="wls.service.server" value="destinationServerName" />
<property name="wls.service.hostname" value="destinationHost" />
<property name="wls.service.port" value="destinationPort" />
<property name="wls.service.username" value="destinationUser" />
<property name="wls.service.password" value="destinationPassword" />

Substitute the italicized terms in the preceding properties with the actual values for your destination WebLogic Server. The default out-of-the-box build.xml sets these properties to the Examples server.

Build and Deploy the Example

To build and deploy the example:

1. Change to the SAMPLES_HOME\server\examples\src\examples\webservices\wsrm_jaxws\wsrm_jaxws_security directory, where SAMPLES_HOME refers to the main WebLogic Server examples directory, such as c:\Oracle\Middleware\wlserver_10.3\samples.

2. Run the WLST script that configures the destination WebLogic Server by executing the config.ws.reliable.service target of the build.xml file from the shell where you set your environment:
prompt> ant config.ws.reliable.service

3. Execute the following command to configure JAX-WS Web service Security from the shell where you set your environment:
prompt> ant config.wss

4. If you have configured a different destination WebLogic Server (that is, the destination server is not the Examples server), copy the certs\serverKeyStore.jks file to the domain directory of your destination server.

5. Restart both your client and destination WebLogic Server to activate the MBean changes.

6. Execute the following command from the shell where you set your environment:
prompt> ant build

This command compiles and stages the example. Specifically, it compiles both the source and destination Web services. It also compiles the standalone WsrmJaxwsExampleRequest application that invokes the source Web service, which in turn invokes the reliable destination Web service.

7. Execute the following command from the shell where you set your environment:
prompt> ant deploy

This command deploys, by default, both the source and destination Web services to the wl_server domain of your WebLogic Server installation. If you have configured a different destination WebLogic Server and updated the build.xml file accordingly, then the reliable JAX-WS Web service is deployed to the configured destination server.

12.38.4.4 Run the Example

To run the example, follow these steps:

1. Complete the steps in the Prepare the Example section.

2. In your development shell, run the WsrmJaxwsExampleRequest Java application using the following command from the main example directory (SAMPLES_HOME\server\examples\src\examples\webservices\wsrm_jaxws\wsrm_jaxws_security):
prompt> ant run

This command runs the standalone WsrmJaxwsExampleRequest application that invokes the source Web service, which in turn invokes the reliable destination JAX-WS Web service.

3. To test the reliability of the Web service, stop the destination WebLogic Server, and then rerun the WsrmJaxwsExampleRequest application. When you restart the destination WebLogic Server and the reliable Web service is deployed, you should see that the operation is also automatically invoked.

Check the Output

If your example runs successfully, the following messages display in the command shell from which you ran the WsrmJaxwsExampleRequest application:

Trying to override old definition of task clientgen

run:
[java]
[java]
[java] ###########################################
[java]     In testEcho_AsyncOnServerClient_ServiceBuffered...
[java]     On-Server / Async / Buffered case
[java]     2011/06/160 03:30:29.938
[java] ###########################################
[java]
[java]
[java] Client addr:http://localhost:9001/wsrm_jaxws_sc_example_client/Clien
tService
[java] ---[HTTP request - http://localhost:9001/wsrm_jaxws_sc_example_clien
t/ClientService]---
[java] Content-type: text/xml;charset=utf-8
[java] Soapaction: ""
[java] Accept: text/xml, multipart/related, text/html, image/gif, image/jpe
g, *; q=.2, */*; q=.2
[java] <?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://sc
hemas.xmlsoap.org/soap/envelope/"><S:Body><ns2:runTestEchoWithRes xmlns:ns2="htt
p://example.wsrm_jaxws/"><arg0>Foo bar</arg0><arg1>localhost</arg1>
<arg2>8001</arg2><arg3>C:\Oracle\Middleware\wlserver_10.3\samples\server\
examples\src\examples\webservices\wsrm_jaxws_security/certs</arg3>
</ns2:runTestEchoWithRes></S:Body></S:Envelope>--------------------
[java]
[java] ---[HTTP response - http://localhost:9001/wsrm_jaxws_sc_example_clie
nt/ClientService - 200]---
[java] Transfer-encoding: chunked
[java] null: HTTP/1.1 200 OK
[java] Content-type: text/xml;charset=utf-8
[java] X-powered-by: Servlet/2.5 JSP/2.1
[java] Date: Thu, 09 Jun 2011 07:30:33 GMT
[java] <?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://sc
hemas.xmlsoap.org/soap/envelope/"><S:Body><ns2:runTestEchoWithResResponse xmlns:
ns2="http://example.wsrm_jaxws/"><return>[2011/06/160 03:30:33.953] ## Making Ec
ho Requests (ASYNC/BUFFERED) ##
[java] [2011/06/160 03:30:42.703] *** On first good invoke ***
[java] [2011/06/160 03:30:42.703] echo returned: Foo bar expected: Foo bar
[java] [2011/06/160 03:30:42.922] echo returned: foo bar 2 expected: foo ba
r 2
[java] [2011/06/160 03:30:43.031] echo returned: foo bar 3 expected: foo ba
r 3
[java] [2011/06/160 03:30:43.031] ## Done Making Echo Requests (ASYNC/BUFFE
RED) ##
[java] </return></ns2:runTestEchoWithResResponse></S:Body>
</S:Envelope>--------------------
[java]
[java] [2011/06/160 03:30:33.953] ## Making Echo Requests (ASYNC/BUFFERED)
##
[java] [2011/06/160 03:30:42.703] *** On first good invoke ***
[java] [2011/06/160 03:30:42.703] echo returned: Foo bar expected: Foo bar
[java] [2011/06/160 03:30:42.922] echo returned: foo bar 2 expected: foo ba
r 2
[java] [2011/06/160 03:30:43.031] echo returned: foo bar 3 expected: foo ba
r 3
[java] [2011/06/160 03:30:43.031] ## Done Making Echo Requests (ASYNC/BUFFE
RED) ##
[java]

BUILD SUCCESSFUL
Total time: 2 minutes 33 seconds

The following messages display in the command window from which you started as the client WebLogic Server (that hosts the reliable source Web service):

Service addr:http://localhost:7001/wsrm_jaxws_sc_example/ReliableEchoService
[2011/06/180 01:33:40.906] ## Making Echo Requests (ASYNC/BUFFERED) ##

[2011/06/180 01:33:40.906] In invokeEchoAsync, invoking echo with request: Foo bar

[2011/06/180 01:33:40.906] In invokeEchoAsync, waiting for response to request: Foo bar ...

SignInfo mismatch  Algo mismatch http://www.w3.org/2000/09/xmldsig#rsa-sha1 VS.
http://www.w3.org/2000/09/xmldsig#hmac-sha1 Refs: Msg size =1#Signature_prfr5thF
y2vRPbpC, Policy size =3 #unt_w7HSTtcGcebXFWEr, #Timestamp_XIXttwj9Yq2XO7Tj, #Bo
dy_81D2x3V7iTNyy1I5,
STR type mismatch Actual KeyInfo:{http://docs.oasis-open.org/wss/2004/01/oasis-2
00401-wss-wssecurity-secext-1.0.xsd}KeyIdentifier|http://docs.oasis-open.org/wss
/oasis-wss-soap-message-security-1.1#ThumbprintSHA1,  StrTypes size=1 :{http://d
ocs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Refere
nce||http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512/dk,
Security Token mismatch, token type =http://docs.oasis-open.org/ws-sx/ws-securec
onversation/200512/dk and actual ishttp://docs.oasis-open.org/wss/2004/01/oasis-
200401-wss-x509-token-profile-1.0#X509v3
<WSEE:15>There is no information on the incoming SOAP message.
<SmartPolicySelect or.getSmartPolicyBlueprint:501>
testing...................

[2011/06/180 01:33:41.718] In ClientServiceImpl.onEchoResponse(request:
examplesServer: 4b1c0f3e575dfa8c:7291c50f:130d9cbaace:-7fb8)

[2011/06/180 01:33:41.718] Done with ClientServiceImpl.onEchoResponse(request:
examplesServer: 4b1c0f3e575dfa8c:7291c50f:130d9cbaace:-7fb8): Foo bar

[2011/06/180 01:33:41.718] *** On first good invoke ***

[2011/06/180 01:33:41.734] echo returned: Foo bar expected: Foo bar

[2011/06/180 01:33:41.734] In invokeEchoAsync, invoking echo with request: foo bar 2

[2011/06/180 01:33:41.750] In invokeEchoAsync, waiting for response to request: foo bar 2 ...

<WSEE:15>There is no information on the incoming SOAP message.
<SmartPolicySelect or.getSmartPolicyBlueprint:501>
testing...................

[2011/06/180 01:33:41.984] In ClientServiceImpl.onEchoResponse(request:
examplesServer: 4b1c0f3e575dfa8c:7291c50f:130d9cbaace:-7fae)

[2011/06/180 01:33:41.984] Done with ClientServiceImpl.onEchoResponse(request:
examplesServer: 4b1c0f3e575dfa8c:7291c50f:130d9cbaace:-7fae): foo bar 2

[2011/06/180 01:33:41.984] echo returned: foo bar 2 expected: foo bar 2

[2011/06/180 01:33:42.000] In invokeEchoAsync, invoking echo with request: foo bar 3

[2011/06/180 01:33:42.015] In invokeEchoAsync, waiting for response to request: foo bar 3 ...

<WSEE:31>There is no information on the incoming SOAP message.
<SmartPolicySelect or.getSmartPolicyBlueprint:501>
testing...................

[2011/06/180 01:33:42.187] In ClientServiceImpl.onEchoResponse(request:
examplesServer:4b1c0f3e575dfa8c:7291c50f:130d9cbaace:-7fab)

[2011/06/180 01:33:42.328] Done with ClientServiceImpl.onEchoResponse(request:
examplesServer:4b1c0f3e575dfa8c:7291c50f:130d9cbaace:-7fab): foo bar 3

[2011/06/180 01:33:42.328] echo returned: foo bar 3 expected: foo bar 3

[2011/06/180 01:33:42.328] ## Done Making Echo Requests (ASYNC/BUFFERED) ##

<WSEE:46>There is no information on the incoming SOAP message.
<SmartPolicySelect or.getSmartPolicyBlueprint:501>

The following messages display in the command window from which you started the destination WebLogic Server (that hosts the reliable destination Web service):

%% Echoing: Foo bar %%
%% Echoing: foo bar 2 %%
%% Echoing: foo bar 3 %%

If you deploy both the source and destination Web services to the same Server, the following messages display in the command window from which you started your client and destination WebLogic Server:

Service addr:http://localhost:7001/wsrm_jaxws_sc_example/ReliableEchoService
[2011/06/180 01:33:40.906] ## Making Echo Requests (ASYNC/BUFFERED) ##

[2011/06/180 01:33:40.906] In invokeEchoAsync, invoking echo with request: Foo bar

[2011/06/180 01:33:40.906] In invokeEchoAsync, waiting for response to request: Foo bar ...

SignInfo mismatch  Algo mismatch http://www.w3.org/2000/09/xmldsig#rsa-sha1 VS.
http://www.w3.org/2000/09/xmldsig#hmac-sha1 Refs: Msg size =1#Signature_prfr5thF
y2vRPbpC, Policy size =3 #unt_w7HSTtcGcebXFWEr, #Timestamp_XIXttwj9Yq2XO7Tj, #Bo
dy_81D2x3V7iTNyy1I5,
STR type mismatch Actual KeyInfo:{http://docs.oasis-open.org/wss/2004/01/oasis-2
00401-wss-wssecurity-secext-1.0.xsd}KeyIdentifier|http://docs.oasis-open.org/wss
/oasis-wss-soap-message-security-1.1#ThumbprintSHA1,  StrTypes size=1 :{http://d
ocs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Refere
nce||http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512/dk,
Security Token mismatch, token type =http://docs.oasis-open.org/ws-sx/ws-securec
onversation/200512/dk and actual ishttp://docs.oasis-open.org/wss/2004/01/oasis-
200401-wss-x509-token-profile-1.0#X509v3
%% Echoing: Foo bar %%
<WSEE:15>There is no information on the incoming SOAP message.
<SmartPolicySelect or.getSmartPolicyBlueprint:501>
testing...................

[2011/06/180 01:33:41.718] In ClientServiceImpl.onEchoResponse(request:
examplesServer: 4b1c0f3e575dfa8c:7291c50f:130d9cbaace:-7fb8)

[2011/06/180 01:33:41.718] Done with ClientServiceImpl.onEchoResponse(request:
examplesServer: 4b1c0f3e575dfa8c:7291c50f:130d9cbaace:-7fb8): Foo bar

[2011/06/180 01:33:41.718] *** On first good invoke ***

[2011/06/180 01:33:41.734] echo returned: Foo bar expected: Foo bar

[2011/06/180 01:33:41.734] In invokeEchoAsync, invoking echo with request: foo bar 2

[2011/06/180 01:33:41.750] In invokeEchoAsync, waiting for response to request: foo bar 2 ...

%% Echoing: foo bar 2 %%
<WSEE:15>There is no information on the incoming SOAP message.
<SmartPolicySelect or.getSmartPolicyBlueprint:501>
testing...................

[2011/06/180 01:33:41.984] In ClientServiceImpl.onEchoResponse(request:
examplesServer: 4b1c0f3e575dfa8c:7291c50f:130d9cbaace:-7fae)

[2011/06/180 01:33:41.984] Done with ClientServiceImpl.onEchoResponse(request:
examplesServer: 4b1c0f3e575dfa8c:7291c50f:130d9cbaace:-7fae): foo bar 2

[2011/06/180 01:33:41.984] echo returned: foo bar 2 expected: foo bar 2

[2011/06/180 01:33:42.000] In invokeEchoAsync, invoking echo with request: foo bar 3

[2011/06/180 01:33:42.015] In invokeEchoAsync, waiting for response to request: foo bar 3 ...

%% Echoing: foo bar 3 %%
<WSEE:31>There is no information on the incoming SOAP message.
<SmartPolicySelect or.getSmartPolicyBlueprint:501>
testing...................

[2011/06/180 01:33:42.187] In ClientServiceImpl.onEchoResponse(request:
examplesServer:4b1c0f3e575dfa8c:7291c50f:130d9cbaace:-7fab)

[2011/06/180 01:33:42.328] Done with ClientServiceImpl.onEchoResponse(request:
examplesServer:4b1c0f3e575dfa8c:7291c50f:130d9cbaace:-7fab): foo bar 3

[2011/06/180 01:33:42.328] echo returned: foo bar 3 expected: foo bar 3

[2011/06/180 01:33:42.328] ## Done Making Echo Requests (ASYNC/BUFFERED) ##

<WSEE:46>There is no information on the incoming SOAP message.
<SmartPolicySelect or.getSmartPolicyBlueprint:501>

Part V

Oracle WebCenter Portal

Part V contains the following chapter:

- Chapter 13, "Oracle WebCenter Portal"

13 Oracle WebCenter Portal

This chapter describes issues associated with Oracle WebCenter Portal. It includes the following topic:

- Section 13.1, "General Issues and Workarounds"

Note:

For release notes related to WebCenter Portal installed on IBM WebSphere, see Chapter 7, "Oracle Fusion Middleware on IBM WebSphere."

13.1 General Issues and Workarounds

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

- Section 13.1.1, "Installing the WebCenter Portal Extension Version 11.1.1.8.3 for JDeveloper"

- Section 13.1.2, "Support for Discussions Server from Jive Software"

- Section 13.1.3, "Oracle WebCenter Portal's Pagelet Producer Failover Support"

- Section 13.1.4, "SQL Query with NCHAR Data Type Throws Exception"

- Section 13.1.5, "Configuring the REST Server Post-Installation"

- Section 13.1.6, "Cannot Customize or Personalize a JSF Portlet"

- Section 13.1.7, "Portals Do Not Display Correct Language When WebCenter Portal is Accessed Using OAM"

- Section 13.1.8, "Announcement Publication Format can be Incorrect in Thai"

- Section 13.1.9, "The Run as Servlet Link on Producer Test Page Does Not Work for JSF Portlet"

- Section 13.1.10, "Using OpenSocial Pagelets to Post Activities to User's Activity Stream"

- Section 13.1.11, "Accessing Owners' Profile Information Using the OpenSocial API"

- Section 13.1.12, "Unable to View Entire Content on iPad as Scrollbars Not Displayed"

- Section 13.1.13, "RSS Links Not Working Properly on iPad"

- Section 13.1.14, "Cannot Upload Content Using iPad"

- Section 13.1.15, "Cannot Copy Text Displayed on Pages"

- Section 13.1.16, "Embedded Images Not Rendered"

- Section 13.1.17, "Unable to Check Out a Document When Using Firefox First Time"

- Section 13.1.18, "Web Clipping Portlet is Deprecated"

- Section 13.1.19, "Deployment Fails Because Versioned Applications Are Not Supported"

- Section 13.1.20, "Exception Reported When Running WC_Spaces Managed Server"

- Section 13.1.21, "Upgraded Portals Do Not Render Properly"

- Section 13.1.22, "Displaying a Page on a Device when the Page Name Includes a Space"

- Section 13.1.23, "Problem Integrating PeopleSoft and WebCenter Portal"

- Section 13.1.24, "Unable to Create Pages in Portals Created Using REST APIs"

- Section 13.1.25, "Mobile Page Variants Not Displayed Correctly on Nexus 4 Devices"

- Section 13.1.26, "Configuring Oracle SES 11.2.2.2 for Oracle WebCenter Portal"

- Section 13.1.27, "Clicking the Create Topic Button in a Discussion Forum Does Not Open the Create Topic Dialog"

- Section 13.1.28, "Duplicate Copies Created when Copying, Moving, or Cutting and Pasting Files and Folders with the Same Name"

- Section 13.1.29, "Invalid Characters in Folder and File Names"

- Section 13.1.30, "Comment and Tag Updates Not Listed in Activity Stream of Portal Framework Applications"

- Section 13.1.31, "Imprecise Error Message When Uploading a File with the Same Name as a Checked Out File"

- Section 13.1.32, "Cannot Create or Move Files by Using CMIS REST API"

- Section 13.1.33, "Tabs Not Displayed on Document Management Taskbar"

- Section 13.1.34, "Imprecise Error Messages When Renaming or Pasting a File in Workflow"

- Section 13.1.35, "Unable to Access Files Using Direct URL in Home Portal"

- Section 13.1.36, "Creating a Portal based on a Template Containing Blogs or Wikis"

- Section 13.1.37, "FrameworkFolders Not Supported When Oracle BPM Process Spaces is Enabled for WebCenter Portal"

13.1.1 Installing the WebCenter Portal Extension Version 11.1.1.8.3 for JDeveloper

The WebCenter Portal extension is an add-in that provides JDeveloper with the complete set of WebCenter Portal capabilities and features. Oracle WebCenter Portal 11.1.1.8.3 works only with WebCenter Portal extension 11.1.1.8.x and Oracle JDeveloper 11.1.1.7.0. By default, JDeveloper will recommend you to download the WebCenter Portal extension for release 11.1.1.8.3 as it is the latest version. You must ensure that you have the correct version installed. For information about installing the extension, see the "Installing the WebCenter Portal Extension for JDeveloper" section in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

13.1.2 Support for Discussions Server from Jive Software

Oracle supports the embedded discussions server from Jive Software. Use the supplied task flows that come with WebCenter Portal to call this discussions server. Any custom development against APIs in the Jive Web Service layer are subject to review by Oracle and may not be supported.

There are a limited set of beta features that Jive Software delivers as part of the discussions server that Oracle does not recommend and cannot yet support.

Documentation for Jive Forums is included for reference only. Jive software installations and upgrades outside of the WebCenter Portal product installation are not supported.

13.1.3 Oracle WebCenter Portal's Pagelet Producer Failover Support

Oracle WebCenter Portal's Pagelet Producer supports failover in a clustered configuration. However, the in-flight data (unsaved or pending changes) is not preserved. On failover, administrators must reestablish their administrative session. End users may also need to reestablish the session if the proxy is required to have a state. If SSO is configured, credentials are automatically provided, and the session is reestablished.

13.1.4 SQL Query with NCHAR Data Type Throws Exception

When using a SQL data control, you may encounter an error if the query contains a column with the NCHAR data type. As a workaround, you can use the to_char(NCHAR_COLUMN NAME) function.

13.1.5 Configuring the REST Server Post-Installation

For certain features of the WebCenter Portal REST server to work correctly when using a REST client like the Oracle WebCenter Portal iPhone application, the flag WLForwardUriUnparsed must be set to ON for the Oracle WebLogic Server Plugin that you are using.

- If you are running Apache in front of WebLogic Server, add this flag to weblogic.conf.

- If you are running Oracle HTTP Server (OHS) in front of WebLogic Server, add this flag to mod_wl_ohs.conf.

The examples below illustrate the possible configurations for both of these cases.

For more information about how to configure WebLogic Server Plugins, see Oracle Fusion Middleware Using Web Server 1.1 Plug-Ins with Oracle WebLogic Server.

Example 1: Using <location /rest> to apply the flag only for /rest URIs (recommended)

<Location /rest>
# the flag below MUST BE set to "On"
WLForwardUriUnparsed    On

# other settings, example: WebLogicCluster or WebLogicHost & WebLogicPort

# set the handler to be weblogic
SetHandler weblogic-handler
</Location>

Example 2: Applying the flag to all URIs served by Oracle WebLogic Server

<IfModule mod_weblogic.c>
# the flag below MUST BE set to "On"
WLForwardUriUnparsed    On

# other settings, example: WebLogicCluster or WebLogicHost & WebLogicPort
WebLogicCluster johndoe02:8005,johndoe:8006
Debug ON
WLLogFile             c:/tmp/global_proxy.log
WLTempDir             "c:/myTemp"
DebugConfigInfo       On
KeepAliveEnabled ON
KeepAliveSecs  15
</IfModule>

13.1.6 Cannot Customize or Personalize a JSF Portlet

When clicking OK after customizing or personalizing a JSF portlet (that is, a portlet created using the Oracle JSF Portlet Bridge), the portlet does not respond and displays a timeout message. This is caused by performing an edit action and changing the portlet mode in a single operation. End users can work around this issue by clicking Apply (instead of OK) to perform the edit action first, then clicking Return to change the portlet mode back to View mode. Portlet developers can avoid the issue occurring by editing the code for the generated Edit Defaults mode (in the edit_defaults.jspx file) and Edit mode (in the edit.jspx file) and removing the code for the OK button so that end users are forced to use the Apply button instead.

13.1.7 Portals Do Not Display Correct Language When WebCenter Portal is Accessed Using OAM

When users access WebCenter Portal through OAM, portals do not display the language selected on the OAM login page. WebCenter Portal does not use the same xlf file name standard as OAM.

13.1.8 Announcement Publication Format can be Incorrect in Thai

When the display language is set to Thai, the announcement publication format can be incorrect. This happens when announcements are opened to edit and are then saved, even if nothing in the announcement itself is updated.

13.1.9 The Run as Servlet Link on Producer Test Page Does Not Work for JSF Portlet

You can create a JSF portlet (that is, a portlet that uses the Oracle JSF Portlet Bridge) using the Create JSR 286 Java Portlet Wizard by selecting the Generate ADF-Faces JSPX implementation method on the third step of the wizard.

If you create a JSF portlet in this way, you may find that clicking the Run as Servlet link on the portlet's Producer Test Page produces an error. The portlet itself, however, runs correctly.

To avoid this issue, add the ADF Page Flow scope to the project that contains the portlet. For information, see the "Adding and Removing Technology Scopes" section in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

13.1.10 Using OpenSocial Pagelets to Post Activities to User's Activity Stream

Pagelets based on OpenSocial gadgets are not able to post activities to a user's activity stream. To implement a temporary solution, grant User Profile 'edit' permission to Oracle WebCenter Portal's Pagelet Producer using the following WLST/WSAdmin command:

grantPermission(appStripe="pagelet-producer",
principalClass="oracle.security.jps.internal.core.principals.JpsAuthenticatedRoleImpl", principalName="authenticated-role",
permClass="oracle.webcenter.peopleconnections.profile.security.ProfilePermission",
permTarget="/oracle/webcenter/peopleconnections/profile/s8bba98ff_4cbb_40b8_beee_296c916a23ed/.*", permActions="view,edit")

After running the command, restart the Pagelet Producer server.

13.1.11 Accessing Owners' Profile Information Using the OpenSocial API

To access owners' Profile/Activities/Friends information using the OpenSocial API with Oracle WebCenter Portal's Pagelet Producer, you must target the WebCenterDS data source to the WC_Portlet managed server as described in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter. After saving this configuration, Activities and Friends information can be fetched, but Profile information is not returned. To access Profile information, restart the WC_Portlet managed server.

13.1.12 Unable to View Entire Content on iPad as Scrollbars Not Displayed

The Apple iOS platform does not display scrollbars. When you view a page on an iPad, content may appear truncated because scrollbars are not displayed. Also, iFrame components ignore dimensions on iPad. To view the entire content area, use the two-finger scroll gesture on your iPad.

13.1.13 RSS Links Not Working Properly on iPad

The Apple iOS platform renders RSS links by loading them through the site reader.mac.com. If the WebCenter Portal instance is not accessible outside your firewall, RSS links cannot be viewed.

13.1.14 Cannot Upload Content Using iPad

The Apple iOS platform does not support a native file system browser. Therefore, you cannot upload content from an iPad. All upload actions, such as publish, upload, and share are disabled or hidden when you access WebCenter Portal from an iPad.

13.1.15 Cannot Copy Text Displayed on Pages

If you access a page through an iPad, you cannot copy the text displayed on the page. This is a limitation from the Apple iOS platform.

13.1.16 Embedded Images Not Rendered

The Mail task flow does not render embedded images. If an email contains inline images, they are shown as attachments, and not within the message body.

13.1.17 Unable to Check Out a Document When Using Firefox First Time

The first time you access WebCenter Portal using the Mozilla Firefox browser, and attempt to open a document using Desktop Integration over an SSL or HTTPS connection, you will receive a warning that the certificate is not trusted, even if the environment has a valid certificate. You can open the document, but cannot check in or check out the document from within a Microsoft Office application. However, subsequent use of Desktop Integration through the Firefox browser will work as expected and you will be able to check documents in and out from within a Microsoft Office application.

13.1.18 Web Clipping Portlet is Deprecated

The Web Clipping portlet is deprecated in Release 11g (11.1.1.8.0) and should not be used. Instead, create a clipper pagelet using Oracle WebCenter Portal's Pagelet Producer.

13.1.19 Deployment Fails Because Versioned Applications Are Not Supported

Application versioning is no longer supported by default for ADF applications. Upon initial deployment, an existing 11.1.1.7.0 (or earlier) or new application (11.1.1.8.0 or later) deploys successfully regardless of the application's versioning. However, when redeploying an unversioned application from JDeveloper 11.1.1.7.0 to a WebLogic Server where a versioned instance of that application is already running, deployment will fail. This is because the server is already running a versioned instance and WebLogic Server does not allow deploying an unversioned instance of the same application. You will see an error message like this:

Weblogic Server Exception:
weblogic.management.ManagementException: [Deployer:149082]You cannot deploy application 'Application1_application1' without version. The application was previously deployed with version 'V2.0'.

To resolve this issue, undeploy the versioned application first and then deploy the unversioned application.

13.1.20 Exception Reported When Running WC_Spaces Managed Server

When you start the WC_Spaces managed server, the following exception is reported in server logs after the server reaches the running state.

"Could not fetch the default portal configuration from webcenter-config oracle.webcenter.webcenterapp.WebCenterException: Getting WebCenter Attributes "

This does not cause any functionality loss. It is a known issue.

13.1.21 Upgraded Portals Do Not Render Properly

In WebCenter Portal, when you display a portal upgraded from a previous Oracle WebCenter Portal installation, the top banner of the portal does not render correctly. This happens when the portal has a page template set to a specific value, and the skin is left as [System Default]. To work around this issue, you must choose a skin to match the page template. Configure the upgraded portal to use the Spaces FX or Fusion FX skin, depending on the page template.

13.1.22 Displaying a Page on a Device when the Page Name Includes a Space

An issue exists when accessing a portal page on a device (such as a tablet or iPhone) when all of the following conditions are true:

- The page has a space in its name

- The page does not have a page variant defined

- The Page Fallback setting for the page or the portal is Display No Page

In this case, the expected behavior is to see Page Not Available on the device. However, when all of the condition above are true, the content of the page displays (without the page title) on the device instead of Page Not Available.

For more information, see the "Setting Page Behavior for a Portal When No Page Variant Exists" and "Setting Page Behavior for a Specific Page When No Page Variant Exists" sections in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.

13.1.23 Problem Integrating PeopleSoft and WebCenter Portal

This release has a known issue when integrating PeopleSoft and WebCenter Portal leveraging WSS1.0 Username Token with Password. This is the recommended approach for customers who require secure consumption of PeopleSoft portlets in WebCenter Portal. Customers should contact Oracle Customer Support to obtain a patch to address this issue.

Oracle does not recommend using WSS1.0 SAML Token with Message Protection. This approach is not supported for integration between WebCenter Portal and PeopleSoft.

13.1.24 Unable to Create Pages in Portals Created Using REST APIs

In a portal created using WebCenter Portal REST APIs, you will face problems creating pages. To work around this issue, you need to reapply Page permissions. Navigate to the Security page in WebCenter Portal Builder Administration. On the Roles tab, deselect all the permissions for Pages and save the setting. Now select the same permissions again and save the settings.

13.1.25 Mobile Page Variants Not Displayed Correctly on Nexus 4 Devices

Mobile page variants are not displayed on the new Nexus 4 devices. To resolve this issue, create a new device with the following user agent string:

Mozilla/5.0 \(Linux; Android.+4.2.+Nexus 4.+Chrome.*Mobile Safari.*

For information about creating new devices and specifying the user agent string, see the "Creating and Managing Devices" section in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

13.1.26 Configuring Oracle SES 11.2.2.2 for Oracle WebCenter Portal

Oracle WebCenter Portal release 11.1.1.8.0 supports Oracle SES 11.2.2.2. If you patch your existing Oracle SES installation to release 11.2.2.2, you must install the new version of Oracle WebCenter Portal's Document Service Manager on Oracle SES and configure Oracle SES facets and sorting attributes. For information, see the "Installing Oracle SES 11.2.2.2" section in Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal.

13.1.27 Clicking the Create Topic Button in a Discussion Forum Does Not Open the Create Topic Dialog

When you navigate to a discussions page by using its direct URL and pass forumId as a query parameter in the page URL, clicking the Create Topic button in the discussion forum displays a list of forums instead of opening the Create Topic dialog. You encounter this issue when accessing the pages that contain the Discussion Forums task flow with #{param.forumId} set as the value for the Forum ID attribute.

To ensure that clicking the Create Topic button displays the Create Topic dialog, implement the following workaround:

1. Open the page that contains the Discussion Forums task flow in edit mode in Composer.

2. Ensure that the View Switcher is set to Data.

3. On the Source tab, click PageDef at the bottom of the frame.

4. Locate the task flow binding within the <executables> section of the PageDef source.
You will notice that this task flow binding has the attribute Refresh="ifNeeded", and one of the input parameters to the task flow binding is "param.forumId".

5. Delete the attribute Refresh="ifNeeded".

6. Replace it with the following attribute: RefreshCondition="#{param.forumId!=null}".

7. Click Save to save the changes.

13.1.28 Duplicate Copies Created when Copying, Moving, or Cutting and Pasting Files and Folders with the Same Name

Duplicate copies of files and folders (prefixed with "Copy of") are created when you "copy and paste", "cut and paste", or "move and paste" to a location that already contains a file or folder with the same name. For example, if you copy or cut the file Events.docx and paste it to a folder containing that file, the new pasted version is named Copy of Events.docx.

This is applicable only when Oracle WebCenter Portal is configured to use FrameworkFolders as the folder service. If Folders_g is configured, files and folders are not duplicated if a matching copy is found at the target.

13.1.29 Invalid Characters in Folder and File Names

If WebCenter Portal is configured to use FrameworkFolders as the folder service, the following characters are not allowed in folder and file names:

? # & / \ * " | < > : î

13.1.30 Comment and Tag Updates Not Listed in Activity Stream of Portal Framework Applications

In a Portal Framework application, when you add comments or tags to a newly uploaded document, these updates are not listed in the Activity Stream of the application. This happens when Oracle WebCenter Portal is configured to use the FrameworkFolders component.

13.1.31 Imprecise Error Message When Uploading a File with the Same Name as a Checked Out File

When a user has checked out a file, and another user tries to upload a new version of the file with the same name, an error message is shown specifying that the user does not have the permission. The error message is not complete as it does not specify that the file has already been checked out by a user. This error is displayed when Oracle WebCenter Portal is configured to use the FrameworkFolders component.

13.1.32 Cannot Create or Move Files by Using CMIS REST API

The feature to create files or folders or move files from one folder to another using the CMIS REST API does not work when FrameworkFolders is enabled as the folder service.

13.1.33 Tabs Not Displayed on Document Management Taskbar

When editing a WebCenter Portal document in Word, Excel, or PowerPoint, the tabs (Status, Members, Tasks, Documents, and Links) do not appear on the Document Management taskbar, which is invoked by clicking on the Office icon > Server > Document Management. The tabs are displayed only after the document has been checked in. This happens when Oracle WebCenter Portal is configured to use the FrameworkFolders component.

13.1.34 Imprecise Error Messages When Renaming or Pasting a File in Workflow

When you try to rename or cut and paste a file that is part of workflow, an error message appears indicating that the file cannot be renamed or moved as it no longer exists. For example, the following error message appears when you rename a file:

"Messages for this page are listed below.
Unable to rename the selected document.
The document no longer exists.
Please refresh to see the latest content (View > Refresh Content)."

This error message is incorrect, and is displayed when Oracle WebCenter Portal is configured to use the FrameworkFolders component. The error message should specify that the file cannot be renamed or moved because it is part of workflow and the user is not added as a reviewer to the workflow.

13.1.35 Unable to Access Files Using Direct URL in Home Portal

In Home portal, accessing a file under Item Level Security using direct URL does not work if you do not have access to all the folders in the chain. This happens when Oracle WebCenter Portal is configured to use the FrameworkFolders component.

13.1.36 Creating a Portal based on a Template Containing Blogs or Wikis

When you create a portal from a portal template that contains blogs and wikis, the blogs and wikis are not displayed in the newly created portal. This happens when Oracle WebCenter Portal is configured to use the FrameworkFolders component.

13.1.37 FrameworkFolders Not Supported When Oracle BPM Process Spaces is Enabled for WebCenter Portal

Oracle BPM Process Spaces requires that Folders_g must be enabled on Content Server. In a new installation of Oracle WebCenter Portal 11.1.1.8.3, if you want to enable Process Spaces for WebCenter Portal, you must ensure that Folders_g is enabled and FrameworkFolders is disabled.

14 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:

- Section 14.1, "Using Multibyte User Credentials with wss_http_token_* Policy"

- Section 14.2, "Performing a Bulk Upload of Policies"

- Section 14.3, "Reviewing Policy Configuration Override Values After Detaching a Client Policy"

- Section 14.4, "Removing Post-deployment Customizations"

- Section 14.5, "Reviewing Localization Limitations"

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

- Section 14.7, "Identity in WSDLs Is Not Used for Enforcement with ADF DC Applications"

- Section 14.8, "Fusion Middleware Control Does Not List Policies When Two Servers Are SSL Enabled (Two-way SSL)"

- Section 14.9, "Web Service Test Page Cannot Test Input Arguments Bound to SOAP Headers"

- Section 14.10, "When Adding SAML Issuer From Fusion Middleware Control the jps-config.xml File Is Incorrectly Updated"

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

- Section 14.12, "Custom Policy Fails When an Empty Subject Is Passed"

- Section 14.13, "Possible Limitation When Using Custom Exactly-one Policies"

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

- Section 14.15, "Compatible Policies Not Returned When Using JDeveloper Wizard to Attach Oracle WSM Policies to Web Service Client"

- Section 14.16, "SAML Bearer Token Policies Now Signed by Default"

- Section 14.17, "Security Policies Do Not Work on Subscriber Mediator Component"

- Section 14.18, "Policy Table Might Not Show Attached Policies for Some Locales"

- Section 14.19, "Manual Step Required to Uptake Changes in Predefined Policy"

- Section 14.20, "Usage Tracking Not Enabled for WebLogic Web Service Client"

- Section 14.21, "Do Not Attach a Permitall and Denyall Policy to the Same Web Service"

- Section 14.22, "Additional Quotes in Fusion Middleware Control for Run-time Constraint Input from WLST"

- Section 14.23, "Scoped Configuration Override Persists for Subsequent References to the Same Policy"

- Section 14.24, "New Default Settings for Policies"

- Section 14.25, "Restart Applications to Get an Accurate Policy Usage Count"

- Section 14.26, "Kerberos Policy Enforcement Throws an "Unable to Obtain Password from User" Error"

- Section 14.27, "The migrateAttachments WLST Command Fails for WebLogic JAX-WS Web Services"

- Section 14.28, "A Null Pointer Exception Could be Thrown When Verifying a SOAP Message Signature"

- Section 14.29, "checkWSMstatus() WLST Command Fails Against a Domain When wsm-pm Targets Multiple Servers"

- Section 14.30, "Performance Improvements in Web Services Policy Pages"

- Section 14.31, "Cross-Domain Policy Manager Configuration is Not Supported in this Release"

- Section 14.32, "The setWebServicePolicyOverride WLST Command Does Not Apply to JAVA EE (WebLogic) Web Services"

Note:

For WebLogic Web Services, see Section 12.36, "Web Services and XML Issues and Workarounds."

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

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

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

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

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

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

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

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

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

14.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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

14.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 procedures to connect to a remote Policy Manager, described in the following topics in Oracle Fusion Middleware Security and Administrator's Guide for Web Services, are not recommended in a production environment:

- Configuring a Web Service on a Remote Policy Manager and Tuning the Policy Cache

- Configuring Web Service Policy Retrieval

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

Part VI

Oracle WebCenter Content

Part VI contains the following chapters:

- Chapter 15, "Oracle WebCenter Application Adapters"

- Chapter 16, "Oracle WebCenter Content Installation and Configuration"

- Chapter 17, "Oracle WebCenter Content: Imaging"

- Chapter 19, "Oracle Information Rights Management"

- Chapter 20, "Oracle WebCenter Content"

- Chapter 21, "Oracle WebCenter Content: Records"

15 Oracle WebCenter Application Adapters

This chapter describes issues associated with Oracle WebCenter application adapters. It includes the following topics:

- Section 15.1, "Configuration Issues and Workarounds"

- Section 15.2, "Documentation Errata"

15.1 Configuration Issues and Workarounds

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

- Section 15.1.1, "Populating the AXF_MA_PARAMETERS Table to Pass Extra Metadata Values (Managed Attachments)"

15.1.1 Populating the AXF_MA_PARAMETERS Table to Pass Extra Metadata Values (Managed Attachments)

This section provides additional information on passing extra metadata values from a business application to Content Server for an Oracle E-Business Suite Forms configuration, as described in "Passing Extra Metadata Values From a Business Application to Content Server" in Oracle Fusion Middleware Administering the Application Adapters for Oracle WebCenter.

To populate the AXF_MA_PARAMETERS table, use a script similar to the following:

Example 15-1 PL/SQL Script to Populate the AXF_MA_PARAMETERS Table

BEGIN
FOR x1 IN
(SELECT fndid, block_name FROM axf.axf_fnd_map WHERE FORM_NAME = 'APXINWKB')
LOOP
INSERT
INTO AXF.AXF_MA_PARAMETERS VALUES
(
AXF.AXF_MA_PARAMETERS_SEQ.nextval,
x1.fndid,
'extraxIDNumber',
'DATA',
x1.block_name,
'INVOICE_NUM',
NULL,
'0',
SYSDATE,
SYSDATE,
'0',
'0'
);
END LOOP;
END;

Note that this script creates many new rows in the AXF_MA_PARAMETERS table. You can use the script for other forms by changing the form_name parameter (APXINWKB). You can also change the metadata field (xIDNumber) to another field. If pulling a different field value from the Oracle E-Business Suite form (xl.block_name and INVOICE_NUM), replace these settings.

15.2 Documentation Errata

This section describes documentation errata. It includes the following topic:

- Section 15.2.1, "Incorrect Default Document Type Specified"

- Section 15.2.2, "dPrivilege Parameter in AFGrants Table Incorrectly Identified as Optional"

15.2.1 Incorrect Default Document Type Specified

In the section "Customizing the Document Type Used For New Attachments" in Oracle Fusion Middleware Administering the Application Adapters for Oracle WebCenter, the entry used to specify the default document type is incorrect: afDocType should be replaced with dDocType.

15.2.2 dPrivilege Parameter in AFGrants Table Incorrectly Identified as Optional

In the section "AFGrants Table" in Oracle Fusion Middleware Administering the Application Adapters for Oracle WebCenter, the dPrivilege table entry incorrectly states that the dPrivilege parameter is optional. This parameter is required. If not specified, the access level specified for the AppAdapterGrantPrivilege configuration variable is used.

16 Oracle WebCenter Content Installation and Configuration

This chapter describes installation and configuration issues associated with Oracle WebCenter Content. It includes the following topics:

- Section 16.1, "Rebranding of Oracle Enterprise Content Management Suite to Oracle WebCenter Content"

- Section 16.2, "Documentation Errata"

For more information about Oracle WebCenter Content installation and configuration, see the Oracle WebCenter Content Installation Guide or the Oracle WebCenter Content Quick Installation Guide.

16.1 Rebranding of Oracle Enterprise Content Management Suite to Oracle WebCenter Content

Oracle Enterprise Content Management Suite has been changed to Oracle WebCenter Content in the Oracle Fusion Middleware 11g (11.1.1.6.0) release. Oracle WebCenter Content is part of the Oracle WebCenter product stack, to provide the most complete, open, and unified enterprise content management platform.

The software and documentation for most of the Oracle WebCenter Content products have been rebranded accordingly. Table 16-0 shows the new and previous names.

Table 16-1 Oracle WebCenter Content Names Rebranded from Oracle Enterprise Content Management Suite

New Name

New Short Name

Previous Name

Previous Short Name

Oracle WebCenter Content

None

Oracle Enterprise Content Management Suite

Oracle ECM

Oracle WebCenter Content

WebCenter Content

Oracle Universal Content Management

Oracle UCM

Oracle WebCenter Content Server

Content Server

Oracle Content Server

Content Server

Oracle WebCenter Content: Inbound Refinery

Inbound Refinery

Oracle Inbound Refinery

Oracle IBR

Oracle WebCenter Content: Imaging

Oracle WebCenter Imaging

Imaging

Oracle Imaging and Process Management

Oracle I/PM

Oracle WebCenter Content: Records

Records

Oracle Universal Records Management

Oracle URM

Oracle WebCenter Content: Desktop

Desktop

Oracle UCM Desktop Integration Suite

Oracle DIS

The following names remain unchanged:

- Oracle Information Rights Management (Oracle IRM)

- Oracle UCM Site Studio, or Oracle Site Studio (Site Studio)

- Oracle Universal Records Management Adapters

- Oracle Forms Recognition

16.2 Documentation Errata

This section describes documentation errata. It includes the following topic:

- Section 16.2.1, "Start Capture Managed Server Before Setting Application Roles"

16.2.1 Start Capture Managed Server Before Setting Application Roles

The order of tasks for configuring Oracle WebCenter Content: Capture is incorrect in Section 7.2, "Completing the Initial Configuration of Capture," in Oracle Fusion Middleware Installing and Configuring Oracle WebCenter Content, version 11gR1 (11.1.1.8.0).

The tasks should be in the following order because the Capture Managed Server needs to be started before the application roles are set:

1. Start the Capture Managed Server.

2. Assign roles to Capture users in Fusion Middleware Control.

3. Modify system-level settings through MBeans.

Likewise, the sections for these tasks should be in the following order:

- 7.2.1 Starting the Capture Managed Server

- 7.2.2 Assigning Roles to Capture Users

- 7.2. Modifying System-Level Settings

17 Oracle WebCenter Content: Imaging

This chapter describes issues associated with Oracle WebCenter Content: Imaging. It includes the following topics:

- Section 17.1, "General Issues"

- Section 17.2, "Browser Compatibility Issues"

- Section 17.3, "Accessibility Issues"

- Section 17.4, "Documentation Errata"

17.1 General Issues

This section describes general issues. It includes the following topics:

- Section 17.1.1, "Imaging Session Time Out When Using OSSO Requires Browser Refresh"

- Section 17.1.2, "Mixed Translations On Page"

- Section 17.1.3, "Deleting More Than 100 Documents Can Cause Http 404 Errors"

- Section 17.1.4, "Time Zone Based on Time Zone of Imaging Server"

- Section 17.1.5, "Imaging Documents May Be Visible Natively Within WebCenter"

- Section 17.1.6, "Removing Full-Text Search Capabilities From Defined Applications"

- Section 17.1.7, "Application Field Limitations When Using Oracle Text Search"

- Section 17.1.8, "Records Missing from Imaging Searches"

- Section 17.1.9, "WebLogic Server Listening Address and AXF Driver Page URL Must Reference the Same Domain"

- Section 17.1.10, "Must Start NFS Locking Service When Input Agent Used with Linux Shares"

- Section 17.1.11, "DefaultSecurityGroup MBean Allows For Assigning Administrator Rights to Security Group at First Log In"

- Section 17.1.12, "Input Mapping Error When Input Definition File Includes Blank Line"

- Section 17.1.13, "Differing Behavior of Decimals When Ingested Into Number or Decimal Fields"

- Section 17.1.14, "Using Browser Forward, Back, and Refresh Navigation Not Recommended"

- Section 17.1.15, "Document Upload or Update Failure if Content Server English-US Locale Not Enabled"

- Section 17.1.16, "Document Move Failure if Content Server Not Started with English-US Locale"

- Section 17.1.17, "Clearing Java Temporary Files of Cached Files"

- Section 17.1.18, "Solution Editor Enabled Only On Imaging Systems Using an Oracle Database"

- Section 17.1.19, "Additional MBean Configuration Options"

- Section 17.1.20, "Viewer Cache Does Not Work After Upgrading or Patching"

17.1.1 Imaging Session Time Out When Using OSSO Requires Browser Refresh

When using Oracle Single Sign On and an Imaging session expires, WebLogic Server will return an internal server error. Refreshing the page returns to the Imaging log in page for reauthentication to start a new session.

17.1.2 Mixed Translations On Page

Oracle products support 10 standard languages for administrative tasks and 27 standard languages for user tasks. This means that in instances when a selected language is supported for user tasks and an administrative task is performed, multiple languages may be displayed in the user interface.

17.1.3 Deleting More Than 100 Documents Can Cause Http 404 Errors

There is a known issue with Microsoft Internet Explorer if attempting to delete more than 100 documents using a search results table. Doing so can cause Internet Explorer to return a 404 Page Not Found error or potentially lock. This is due to Internet Explorer limiting URL strings to a maximum of 2083 characters. If it is necessary to delete over 100 documents using a search results table, Mozilla Firefox supports URLs up to 65,000 characters.

17.1.4 Time Zone Based on Time Zone of Imaging Server

All time information is now based on the time zone of the Imaging server. This means that any date metadata generated by the Imaging system, such as document creation date, modify date, or other audit events, is governed by the time zone of the Imaging server, and not the user time zone. This can cause date data to be displayed differently to what may be expected on some documents because the time zone may cross midnight.

For example, if the Imaging server is in the Greenwich Mean Time (GMT) time zone and a document is created in the GMT+6 time zone on January 10th at 2:00 AM local time, the creation date that will be displayed in the user interface will be January 9th at 8:00 PM. This can have implications when searching for content based on creation and modification dates of documents.

17.1.5 Imaging Documents May Be Visible Natively Within WebCenter

If an Imaging document is viewed through WebCenter, then the document is cached in WebCenter. This means that if a document is viewed in WebCenter prior to being annotated, the non-annotated document is viewable until such time as the WebCenter cache is refreshed. Redacting a document after it has been cached in WebCenter does not cause the original document to be purged from the WebCenter cache, and so redacted content may be compromised. To help protect redacted content when Imaging is integrated with WebCenter, use the Viewer on the Upload page to redact documents prior to uploading to Imaging.

17.1.6 Removing Full-Text Search Capabilities From Defined Applications

Removing full-text search capabilities from a defined application can cause an error in any defined search against that application if the Document Content condition is not also removed from the search. When modifying an existing application to remove full-text indexing capabilities, ensure that you also remove all Document Content conditions from any defined searches against that application.

17.1.7 Application Field Limitations When Using Oracle Text Search

When Imaging is configured to use OracleTextSearch and an application is defined to do full-text indexing, a maximum limit of 20 SDATA fields for the Content Server repository is imposed on Imaging. SDATA fields are defined as optimized fields by the Oracle Text Search component and are typically non-text, non-memo fields, although other criteria can exist to define text fields as optimized SDATA fields.

When defining an application, Imaging queries the repository DOCMETA table for the number of available SDATA fields and does not allow the creation of any non-text fields within the application beyond the available number. However, additional components installed on the Content Server repository, such as Folders or Discussions, may reduce the total number of available SDATA fields. Because other configurations may consume SDATA outside of the DOCMETA table, you may be able to add fields to an application but get an error when trying to rebuild the search index in Content Server. If this occurs, you must redefine the application using a different Content Server connection with available SDATA fields. If no additional Content Server connection is defined, you can install and configure an additional Content Server and create a new connection to it in Imaging. Alternately, you can redefine the application using the original Content Server connection but with fewer non-text fields until you are able to successfully rebuild the search index.

17.1.8 Records Missing from Imaging Searches

Care should be taken when integrating Imaging with Oracle WebCenter Content: Records. If a document is uploaded into an Imaging application that has been configured to use a Records-only Retention Category and the user who uploaded the document does not have rights on the Content Server repository to see records, they will not be able to see any of the uploaded documents in an Imaging search. Rights to retention categories are determined in Records. If integrating Imaging and Records, ensure that all users needing rights to view records have the correct security, that Retention Categories are set correctly in all Imaging applications, and that users understand what can happen if the Records-only Retention Categories are used.

17.1.9 WebLogic Server Listening Address and AXF Driver Page URL Must Reference the Same Domain

If leveraging AXF functionality with Imaging, the Listen Address base domain configured in the WebLogic Server console must match how the domain is specified in the URL used to access AXF. Otherwise content may not load properly and users may not have access to AXF. To configure the Listen address in AXF, do the following:

1. Log in to the WebLogic Server administration console.

2. Under the Environment section of the ecm_domain, select Servers. The Summary of Servers page is displayed with the Configuration tab active.

3. Click imaging_server<number>. The Setting for imaging_server<number> page is displayed for the selected Imaging server with the Configuration and General tabs active.

4. Set the Listen Address to the preferred URL. The Listen Address specified should be the base domain without the protocol.

Note:

The Listen Address base domain and the URL base domain used to access AXF must be identical. If the fully qualified domain name is used for the Listen Address setting, then it must also be used for the access URL, even when inside the domain. For example, if the base domain server_name.domain.com is used in the Listen Address configuration setting, the access URL would be http://server_name.domain.com:<port>/.

17.1.10 Must Start NFS Locking Service When Input Agent Used with Linux Shares

When Input Agent is being used with Linux and NFS shares, the NFS locking service must be started in addition to the other NFS services. If the NFS locking service is not running, Input Agent fails to acquire file locks and displays an error message stating that no locks are available. If this happens, Input Agent cannot function until the NFS locking service is started.

17.1.11 DefaultSecurityGroup MBean Allows For Assigning Administrator Rights to Security Group at First Log In

The functionality of the DefaultSecurityGroup MBean has been augmented. In addition to being the default security group to use for document security when creating an application, this setting can also be used during security initialization to assign full administrative permissions to a specified group. If a value is specified in the DefaultSecurityGroup MBean prior to Imaging security being initialized, then when the first user logs in, the specified group is given full administrative permissions as well as the user logging in.

17.1.12 Input Mapping Error When Input Definition File Includes Blank Line

Note that when mapping an input definition file, the input field mapping page may display an error if it encounters a line with no data in the definition file. Should this occur, map the fields using a line in the definition file that contains data. You can move to a different line in the definition file using the Show Previous Line and Show Next Line icons in the Sample Data column of the input field mapping page.

17.1.13 Differing Behavior of Decimals When Ingested Into Number or Decimal Fields

When ingesting a decimal representation of a whole number into a number field, the decimal is stripped. For example, "1.0" is ingested as "1." When ingesting a decimal that is not whole, the ingestor does not round the value and an error occurs. For example, "1.1" is not ingested into a number field and causes an error.

When ingesting a decimal value into a decimal field, the decimal value must not exceed the precision specified in the application, even if the represented value is the same. For example, if the application specifies a scale of 2, then "123.45" is ingested correctly, where "123.450" would cause an error. This is because "123.450" exceeds the number of decimal places allowed by the application. This behavior is consistent with the conversion routines available in Java.

17.1.14 Using Browser Forward, Back, and Refresh Navigation Not Recommended

Using browser navigation such as Forward, Back, and Refresh does not provide navigation within a document, a document's panels, or between document tabs open in the Viewer. Instead, browser controls navigate outside of the Imaging Viewer. When viewing a document, it is recommended that all navigation within the Viewer be done using the navigation controls in the Viewer toolbar.

17.1.15 Document Upload or Update Failure if Content Server English-US Locale Not Enabled

The Content Server locale English-US must be enabled on the Content Server. Imaging documents will fail to upload or update if the English-US locale in the Content Server is disabled. It does not need to be set as the active locale, but it must be enabled.

17.1.16 Document Move Failure if Content Server Not Started with English-US Locale

The Content Server must be initially started with the active locale set to English-US or moving Imaging documents from one application to another fails. Once started, the active locale can be changed and documents can be successfully moved as necessary.

17.1.17 Clearing Java Temporary Files of Cached Files

When viewing files in advanced mode, some files are cached on the local client computer. If storage space is a concern on the client computer, manually delete any cached files in the client temp directory.

17.1.18 Solution Editor Enabled Only On Imaging Systems Using an Oracle Database

The Solution Editor is enabled in the Tools menu of the Navigator Pane provided that Imaging is using an Oracle database. If Imaging is using a database other than Oracle, access to the Solution Editor is not available.

17.1.19 Additional MBean Configuration Options

The following configuration MBeans are read only and not included in Section 3.6, "Configuring MBeans" of the Oracle WebCenter Content Administrator's Guide for Imaging. They are part of Oracle's implementation of the Java Management Extension (JMX) standard and are visible in the Enterprise Manager System MBean browser but cannot be altered.

MBean

Description

ConfigMBean

Indicates if this MBean is a Config MBean.

Default: false

eventProvider

Indicates that this MBean is an event provider as defined by JSR-77.

Default: true

eventTypes

All the event's types emitted by this MBean.

Default: jmx.attribute.change

objectName

The MBean's unique JMX name .

Default: oracle.imaging:type=config

ReadOnly

If true, it indicates that this MBean is a read only MBean.

Default: false

RestartNeeded

Indicates whether a restart is needed.

Default: false

stateManageable

Indicates that this MBean provides State Management capabilities as defined by JSR-77.

Default: false

statisticsProvider

Indicates that this MBean is a statistic provider as defined by JSR-77.

Default: false

SystemMBean

It indicates that this MBean is a System MBean.

Default: false

17.1.20 Viewer Cache Does Not Work After Upgrading or Patching

Beginning with the 11g Release 1 (11.1.1.7.0) patch set, follow these steps to enable the Viewer Cache in Imaging or to preserve it if upgrading. In order to enable the Viewer Cache, you will need to extend the Imaging domain with a new separately packaged Viewer Cache component. In previous releases, the Imaging domain was extended using a manually run script that produced the domain extension. However, the 11g Release 1 (11.1.1.7.0) patch set leverages a user friendly configuration wizard to provide the domain extension.

Note:

If you are upgrading from 11g Release 1 (11.1.1.4.0), 11g Release 1 (11.1.1.5.0), or 11g Release 1 (11.1.1.6.0) and you are already using the Viewer Cache feature, then you must complete the steps in this section to extend the domain to enable Viewer Cache in the 11g Release 1 (11.1.1.7.0) patch set.

To extend the Imaging domain:

1. Navigate to the following directory:
cd $ORACLE_HOME/common/bin

2. Run the following script to start the domain configuration wizard:
./config.sh

3. Select Extend an existing WebLogic domain and click Next. The Select a WebLogic Domain Directory screen is displayed.

4. Select the domain in which Imaging is currently configured. By default, the domain name of the ECM install is base_domain.

5. Click Next. The Select Extension Source screen is displayed.

6. Select Oracle WebCenter Content: Imaging Viewer Cache - 11.1.1.0 [wcc] and click Next.

7. If you are applying the patch set to upgrade from a previous release which already had the Viewer Cache enabled, the Conflict Detected dialog box is displayed indicating that the component Viewer JMS ConnectionFactory is already defined. Select the Replace existing component option and click OK. The Configure JDBC Component Schema screen is displayed.

8. Click Next. The Configure GridLink RAC Data Sources screen is displayed.

9. Click Next. The Test JDBC Component Schema screen is displayed.

10. Click Next and then click Extend.

11. Restart the system's Weblogic Managed servers.

12. Upgraded systems with previously configured Viewer Caches will operate as before. To take advantage of the new feature for the first time, use the steps listed in "Configuring the Imaging Viewer Cache" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter Content.

17.2 Browser Compatibility Issues

This section describes browser compatibility issues. It includes the following topics:

- Section 17.2.1, "IE: Non-ASCII Characters Not Supported in Internet Explorer for ExecuteSearch"

- Section 17.2.2, "Firefox: Version and Download Dialog Boxes Appear Behind Viewer in Advanced Mode"

- Section 17.2.3, "Internet Explorer 9: Problem With Link to Install Java SE Runtime Environment Necessary for Viewer"

17.2.1 IE: Non-ASCII Characters Not Supported in Internet Explorer for ExecuteSearch

The Search URL Tool (ExecuteSearch) does not work in Microsoft Internet Explorer if non-ascii characters are used in the search name. If it is necessary for your search name to have non-ascii characters, you must use Mozilla Firefox version 3.5 or higher and set the following parameters:

- prefs.converted-to-utf8=true

- network.standard-url.escape-utf8=true

- network.standard-url.encode-utf8=true

- network.standard-url.encode-query-utf8=true

17.2.2 Firefox: Version and Download Dialog Boxes Appear Behind Viewer in Advanced Mode

There is a problem with how Firefox 3.6, 5.0 and higher handles layer order of page items in the advanced mode of the Viewer. This causes the main page region where documents are displayed to hide the Version and Download dialog boxes when a document is viewed using Firefox. To work around this issue, expand the Properties, History, or Sticky Notes panel into the main page region enough to allow the obscured items to be displayed prior to accessing dialog boxes. This is not an issue when using Microsoft Internet Explorer or Firefox 3.5.x and a workaround would be to use either of these browsers to view documents when using the advanced Viewer mode.

17.2.3 Internet Explorer 9: Problem With Link to Install Java SE Runtime Environment Necessary for Viewer

The Viewer requires a Java SE Runtime Environment (JRE) plug-in to be installed to view documents in advanced mode. If a JRE is not installed, the Viewer will prompt you to install the plug-in the first time it is used in advanced mode. If using Internet Explorer 9, the link to install the JRE plug-in fails. If using Internet Explorer 9, you must obtain and install the JRE plug-in manually to use the Viewer in advanced mode.

17.3 Accessibility Issues

This section describes accessibility issues. It includes the following topics:

- Section 17.3.1, "Button Activation Behavior Different Depending on Viewer Mode"

- Section 17.3.2, "Limitations of Sticky Note Contents"

- Section 17.3.3, "Skip to Content Link Added for Keyboard Navigation"

- Section 17.3.4, "Firefox: Skip to Applet Link Added for Keyboard Navigation in Advanced Viewer Mode"

- Section 17.3.5, "Internet Explorer 7: Focus Issue on Upload Document and Preferences Pages"

- Section 17.3.6, "Name of File Selected For Import Not Displayed in Screen Reader Mode"

- Section 17.3.7, "Issues Selecting From Calendar Using Keyboard"

- Section 17.3.8, "Focus Issue in Create Searches Wizard Using Keyboard"

- Section 17.3.9, "Annotations Not Recognized By JAWS"

- Section 17.3.10, "Date Selected From Calendar Lost Using Keyboard"

- Section 17.3.11, "Some Annotation Buttons Incorrectly Read by JAWS"

- Section 17.3.12, "Internet Explorer: Long Panels Not Visible In Screen Reader"

17.3.1 Button Activation Behavior Different Depending on Viewer Mode

The keyboard command to activate a button that has focus is different between basic and advanced Viewer modes. The enter key is used to activate a focused button when using the basic Viewer mode. The space key is used to activate a focused button when using the advanced Viewer mode.

17.3.2 Limitations of Sticky Note Contents

The contents of sticky notes are not downloaded or printed with the document, nor are they viewable through the REST Viewer. The contents of a sticky note can be printed, with limitations, by expanding the sticky note in the Sticky Notes Panel and printing the web page.

17.3.3 Skip to Content Link Added for Keyboard Navigation

The first link encountered on a page when using keyboard navigation in the Imaging user interface is a Skip to Content link at the top of the page. Selecting this link and pressing Enter takes the focus to the first item in the content region of the page. For example, if on the home page, the first content item is the help links. If a search has been executed and the results are displayed in the content region, then the Skip to Content link takes you to the first search tab.

17.3.4 Firefox: Skip to Applet Link Added for Keyboard Navigation in Advanced Viewer Mode

When viewing a document in the advanced Viewer mode, keyboard focus starts in the Viewer toolbar. However, in Firefox, if focus moves out of the toolbar, it will not return when cycling through the elements using the keyboard. To work around this, a Skip to Applet link is at the top of the page. To return keyboard focus to the Viewer toolbar, tab to the Skip to Applet link and press Enter.

17.3.5 Internet Explorer 7: Focus Issue on Upload Document and Preferences Pages

When using Internet Explorer 7, the keyboard appears not to focus on any command buttons on the Upload Document page (Open Viewer, Create, Reset, Close) or Preferences page (Apply, Revert, Close). Focus is achieved, however there is no indication which button is active. This issue does not occur in Internet Explorer 8.

17.3.6 Name of File Selected For Import Not Displayed in Screen Reader Mode

When in screen reader mode and selecting a file to import, the file is loaded and the Next button becomes available, but the name of the file to be imported is not displayed.

17.3.7 Issues Selecting From Calendar Using Keyboard

In Internet Explorer 7, when selecting dates from a calendar using the keyboard, you cannot select a day. This is not an issue in Firefox, Safari and later versions of Internet Explorer. In addition, the following buttons are skipped when tabbing: Previous month, Previous year, Month increase/decrease, and Year increase/decrease. An alternative to selecting the date with the keyboard is to manually enter the date with the number keys.

17.3.8 Focus Issue in Create Searches Wizard Using Keyboard

After completing fields in the Create New Search Wizard, the keyboard focus changes to the browser URL and you must tab through the banner and navigation before you can edit the current page.

17.3.9 Annotations Not Recognized By JAWS

When viewing a document with annotations while running JAWS, you can tab to an annotation, but no description is read by JAWS.

17.3.10 Date Selected From Calendar Lost Using Keyboard

When using the keyboard to select a date from a calendar control, the selected date is not retained. The workaround is to enter the date into the date field using the number keys on the keyboard.

17.3.11 Some Annotation Buttons Incorrectly Read by JAWS

When you first open a document in Advanced Viewer mode using screen reader mode, JAWS incorrectly adds the phrase Insert F1 Help Text after each button name.

17.3.12 Internet Explorer: Long Panels Not Visible In Screen Reader

When using Microsoft Internet Explorer and I use a screen reader is enabled on the user preferences page, some panels in the Navigation pane may not display, although the text of the panel title is still read. This is caused when the panel name is too long. Depending on the user interface language, this could happen to one or multiple panels. If you expand the panel above the hidden panel, the hidden panel is then displayed.

17.4 Documentation Errata

Documentation Errata: Currently, there are no documentation issues to note.

18 Oracle WebCenter Capture

This chapter describes issues associated with Oracle WebCenter Capture (also referred to as Oracle WebCenter Enterprise Capture). It includes the following topics:

- Section 18.1, "General Issues and Workarounds"

- Section 18.2, "Configuration Issues and Workarounds"

- Section 18.3, "Documentation Errata"

Note:

Ensure that the most recent patches are applied. You can download patches from My Oracle Support (support.oracle.com).

18.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topics:

- Section 18.1.1, "Batch Processing Error Message Not Displayed in Client"

- Section 18.1.2, "Bi-Directional Display Issues Detected in Client"

- Section 18.1.3, "Certain Client Error Messages Display in Server Language Rather Than Browser Language"

- Section 18.1.4, "Capture Client Error Resulted After SSO Time-out"

- Section 18.1.5, "Rare Batch Commit Error Not Cleared After Subsequent Commit By Another Commit Profile"

- Section 18.1.6, "Document Conversion Processor Error Detected During PDF Conversion With No Monitor Configuration"

- Section 18.1.7, "Search Criteria Issue Detected When Granting Security Access to Workspaces or Client Profiles"

- Section 18.1.8, "Certain Import Processor Metric Table Values May Display Zero Values"

- Section 18.1.9, "Need to Specify the Server System Fonts Location For PDF Image Only Commit"

ncluded per bug 17049053 (base bug 16608070).

18.1.1 Batch Processing Error Message Not Displayed in Client

An issue was discovered in which a recognition batch processing error occurred, but the batch error and its error message did not display in the client. This type of error indicates a system level issue. If an issue like this occurs, review the log file for information.

18.1.2 Bi-Directional Display Issues Detected in Client

Issues were discovered with fields in the client not displaying correctly in RTL (Right to Left) layout with a bi-directional language such as Arabic or Hebrew selected as the browser language.

18.1.3 Certain Client Error Messages Display in Server Language Rather Than Browser Language

An issue was discovered in which some error messages in the client display in the server language rather than the browser language.

18.1.4 Capture Client Error Resulted After SSO Time-out

An issue was discovered in which the Capture client, when integrated with OAM (Oracle Access Manager), experienced an error after timing out. To work around this issue, use the Oracle WebLogic Server Administration Console to set the Capture application's time-out setting to the same value as set for OAM.

18.1.5 Rare Batch Commit Error Not Cleared After Subsequent Commit By Another Commit Profile

A rare case was encountered in which an unsuccessful batch commit error was not cleared when it should have been. In this instance, after a commit by one commit profile failed, the batch was later successfully committed by another commit profile. However, document level errors relating to the initial failed commit were reported. Instead, the batch's errors should have been cleared, and the batch removed.

18.1.6 Document Conversion Processor Error Detected During PDF Conversion With No Monitor Configuration

A PDF conversion issue was discovered when the Document Conversion Processor is used in a headless (no display monitor) configuration, resulting in an error.

To work around this issue, set the DISPLAY environment variable to the following:

DISPLAY=:0

18.1.7 Search Criteria Issue Detected When Granting Security Access to Workspaces or Client Profiles

When granting security access for users or groups to a workspace or client profile, the Add Security Member window provides a text entry field in which to specify search criteria. However, searching does not work as indicated in the window. Instead, entering any single letter of a user or group, with or without a wildcard, yields a match.

18.1.8 Certain Import Processor Metric Table Values May Display Zero Values

When viewing the Performance Summary page in Enterprise Manager after starting an import processor job, values for Total Imported Batches, Total Imported Documents, and Total Imported Pages may fluctuate between displaying an expected value and 0.

18.1.9 Need to Specify the Server System Fonts Location For PDF Image Only Commit

After installing Oracle WebCenter Capture in a UNIX environment, the system administrator should identify the system font location on the server for the PDF Image-Only export commit driver.

On the Capture configuration page in Enterprise Manager, enter the system font location in the GD Font Path field. For example, you might enter the following location:

/usr/share/X11/fonts

18.2 Configuration Issues and Workarounds

There are no known issues at this time.

18.3 Documentation Errata

There are no known issues at this time.

19 Oracle Information Rights Management

This chapter describes issues associated with Oracle IRM Server and Oracle IRM Desktop, together known as 'Oracle IRM'. Unless otherwise stated, the version of Oracle IRM to which these release notes apply is 11.1.1.5.0 (incorporating version 11.1.50 of Oracle IRM Desktop).

This chapter includes the following topics:

- Section 19.1, "General Issues and Workarounds"

- Section 19.2, "Configuration Issues and Workarounds"

- Section 19.3, "Documentation Errata"

19.1 General Issues and Workarounds

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

- Section 19.1.1, "Data Truncation May Occur If One Large or Multiple Excel Files Are Open"

- Section 19.1.2, "Some Functionality is Disabled or Restricted in Adobe Reader X and Adobe Reader 9"

- Section 19.1.3, "Limitations of Support for Microsoft SharePoint in this Release"

- Section 19.1.4, "Lotus Notes Email Message May be Lost if Context Selection Dialog is Canceled"

- Section 19.1.5, "Save As is Blocked in Microsoft Office 2000/XP for Sealed Files if the Destination is a WebDAV Folder"

- Section 19.1.6, "No Prompt to Use Local Drafts Folder for Sealed Files in SharePoint 2010"

- Section 19.1.7, "Incorrect Initial Display of Oracle IRM Fields in Microsoft Excel Spreadsheets When Used With SharePoint"

- Section 19.1.8, "Behavior of Automatic Save and Automatic Recovery in Microsoft Office Applications and SharePoint"

- Section 19.1.9, "Support for Microsoft Windows 2000 Has Been Removed"

- Section 19.1.10, "Unreadable Error Message Text When Client and Server Locales are Different"

- Section 19.1.11, "Changes Lost if Tab Changed Before Applying the Apply Button"

- Section 19.1.12, "Some File Formats are Not Supported When Using the Microsoft Office 2007 Compatibility Pack with Microsoft Office 2003"

- Section 19.1.13, "Microsoft Word May Hang if a Sealed Email is Open During Manual Rights Check-In"

- Section 19.1.14, "Sealed Emails in Lotus Notes will Sometimes Show a Temporary File Name"

- Section 19.1.15, "No Support for Sealing Files of 2GB or Larger in Size in Oracle IRM Desktop"

- Section 19.1.16, "Inappropriate Authentication Options After Failed Login on Legacy Servers When Setting Up Search"

- Section 19.1.17, "Opening Legacy Sealed Documents in Microsoft Office 2007 May Fail on First Attempt"

- Section 19.1.18, "Log Out Link Inoperative When Using OAM 11g for SSO"

- Section 19.1.19, "Double-byte Languages Cannot be Used for Entering Data with Legacy Servers"

- Section 19.1.20, "Use of SPACE Key Instead of Return Key in Oracle IRM Server"

- Section 19.1.21, "Calendar Controls in Oracle IRM Server Not Accessible Via the Keyboard"

19.1.1 Data Truncation May Occur If One Large or Multiple Excel Files Are Open

A product defect has been identified in Oracle IRM when it is used with a single large size or multiple open Microsoft Excel files. This may affect the integrity of the Microsoft Excel files that are saved with Oracle IRM.

When you have Oracle IRM enabled with multiple Excel files open or a single large size sealed Excel file, the defect causes data truncation in the open Excel files. There is no error message or warning when the truncation happens.

This defect has been observed for file sizes greater than 10MB although the issue cannot be ruled out for smaller size files as well. The amount of data truncated is random but the rows affected are typically those at the bottom of the file. After the truncation occurs, the data is permanently lost data when the file is saved.

The workaraound is to use smaller sealed Excel workbooks, if possible. If not, confirm the correct row size with the document author, and confirm that value each time you open the sealed file.

There is no confirmation of a resolution as Oracle IRM is nearing the end of support and will be EOL soon.

19.1.2 Some Functionality is Disabled or Restricted in Adobe Reader X and Adobe Reader 9

To protect the security of sealed PDF documents, some Adobe Reader functionality is disabled or restricted, as described below.

Protected Mode in Adobe Reader X

Sealed PDF documents cannot be opened if Adobe Reader Protected Mode is active. If Protected Mode has not been disabled in advance, Oracle IRM will offer to disable Protected Mode when you attempt to open a sealed PDF document. You can choose not to accept, in which case Protected Mode will remain active and the sealed PDF document will not be opened.

Use of Toolbar and Other Controls in Adobe Reader X

When using a sealed PDF document in the traditional view, you cannot use the toolbar that is shown within Internet Explorer across the top of the document. Instead, you must switch to the Read-Mode view (using Ctrl+H) and use the buttons on the floating toolbar that appears in that view. You can use the buttons on the Read-Mode floating toolbar to save and print the sealed PDF document (if you have sufficient rights), and to page up and down, or to zoom in and out. You can also, subject to your rights, use the following keyboard shortcuts: Print (Ctrl+P), Save (Ctrl+Shift+S), and Copy (Ctrl+C).

Use of Toolbar and Other Controls in Adobe Reader 9

The following Adobe Reader 9 toolbar buttons do not function:

- Email

- Collaborate

- Create Adobe PDF using Acrobat.com

If you click these buttons, you will see a message that the associated function is unavailable.

All other Adobe Reader 9 controls are available if you have sufficient rights. If you do not have sufficient rights, you will see a message when you attempt to use the control.

A further restriction applies to controls added to the Adobe Reader 9 interface by users when they have a sealed PDF document open: the added control will be inactive until Adobe Reader is closed and reopened.

19.1.3 Limitations of Support for Microsoft SharePoint in this Release

Read-only support for Windows 2000/XP

Sealed documents will always open read-only when opened from Microsoft SharePoint using Microsoft Office 2000 or Microsoft Office XP. From Microsoft Office 2003 onwards, full checkout, edit, and save capabilities are supported. The following is the behavior when using a Microsoft SharePoint web site to browse and open sealed files:

- Microsoft Office 2000 "open" behavior. Clicking any file in Microsoft SharePoint will result in the option to open the file or save it locally. Sealed files will always open read-only unless saved locally.

- Microsoft Office 2000 "edit" behavior. The Edit in Microsoft Word [PowerPoint/Excel] option is not supported for any file (sealed or unsealed).

- Microsoft Office XP "open" behavior. In Microsoft SharePoint 2007, when clicking a sealed file, a download dialog will be presented offering the option to open the file or save it locally. Sealed files will always open read-only unless saved locally. In Microsoft SharePoint 2010, when clicking a sealed file, a download dialog will be presented offering only the option to save the file locally.

- Microsoft Office XP "edit" behavior. In Microsoft SharePoint 2007 and 2010, when choosing Edit in Microsoft Word [PowerPoint/Excel] from the drop- down list for the file, nothing will happen for the following sealed file types: .sppt, .spot, .sxlt, .sdot. All other sealed file formats will open read-only. In Microsoft SharePoint 2010, the Edit Document option is missing for sealed files when using the Datasheet view.

No support for merging

Files opened from Microsoft SharePoint that are locked for editing by another user will not offer the chance to edit a local copy and merge changes later. Oracle IRM Desktop forces the document to open read-only. In Microsoft Office 2010, the Office bar and Backstage view offer an Edit button to switch to edit mode: this is prevented for sealed documents. If you wish to edit the file, you will need to open it for editing from the Web browser: if it is not locked for editing elsewhere, it will open editable.

Microsoft Word 2010 files opened from SharePoint 2010 are read-only

The following Microsoft Word 2010 sealed file types cannot be edited if they are opened from SharePoint 2010: .sdocx, .sdocm, .sdotx, .sdotm. Other sealed Microsoft Word formats (for example, .sdoc) will open as normal. The workaround is to save a copy of the file locally, edit that file, then upload it to SharePoint.

The Check Out button is sometimes missing when opening a sealed Excel file in Protected Mode

If the Microsoft SharePoint Web site is running under Protected Mode in Internet Explorer on Microsoft Vista or Microsoft Windows 7, the Check Out button is not shown. To work around this issue, check out the file first from the Web browser, or open the file directly via Windows Explorer, the Open dialog (available by choosing Open on the File menu), or the most-recently-used (MRU) list.

Using Microsoft Outlook to work with SharePoint offline

Microsoft Office 2007 onwards supports the ability to open a SharePoint folder in Outlook. The SharePoint files can then be worked on while offline, and Outlook will handle the synchronization of any changes. There are known issues with this capability when working with sealed files because Outlook opens them differently to native Microsoft Office files. You may get the message "Outlook cannot track the program used to open this document. Any changes you make to the document will not be saved to the original document" when opening sealed files from this view, and changes made to the sealed file will not automatically upload to the server. A manual send/receive is required.

In Microsoft Office 2010 the sealed files are opened in a mode which is similar to email attachments and require the following protected view settings:

- Uncheck Enable Protected View for Outlook Attachments. This will allow opening of the server file from within the Outlook offline view.

- Uncheck Enable Protected View for file originating from the Internet. This will allow opening of files when they are being edited offline.

Using Windows Explorer to open sealed files from SharePoint

Microsoft Office 2003 on Windows Vista may have problems opening sealed files from the Windows Explorer view of SharePoint. Microsoft Office may display a message similar to the following:

Could not open http://<sp_server>/DavWWWRoot/Docs/MyFolder/file.sdoc

A workaround for this is to access the folder using UNC. For example:

\\<sp_server>\Docs\MyFolder

19.1.4 Lotus Notes Email Message May be Lost if Context Selection Dialog is Canceled

When using the base release of Lotus Notes version 8.5, if the context selection dialog is canceled when sending a sealed email, an error occurs and the message is lost. This does not occur in earlier versions of Lotus Notes. This issue is resolved in Lotus Notes version 8.5.2.

19.1.5 Save As is Blocked in Microsoft Office 2000/XP for Sealed Files if the Destination is a WebDAV Folder

The use of Save As is blocked in Microsoft Office 2000/XP for sealed files if the destination is a WebDAV folder (for example, in UCM). You'll need to save the sealed file to the local file system and upload it manually to the WebDAV folder. However, if you have the 11g UCM Desktop Integration Suite (DIS) installed, you can save sealed files as a new content item in UCM using the DIS menu in Microsoft Office.

The use of Save as Sealed, or of right-click Seal To (from Windows Explorer), will work when the destination is a WebDav folder.

19.1.6 No Prompt to Use Local Drafts Folder for Sealed Files in SharePoint 2010

When you check out unsealed files in SharePoint 2010, you are warned about the checkout and given the choice to use a local drafts folder. When you check out sealed files in SharePoint 2010, the file is checked out without giving the option to use a local drafts folder.

19.1.7 Incorrect Initial Display of Oracle IRM Fields in Microsoft Excel Spreadsheets When Used With SharePoint

This issue refers to Oracle IRM Fields set up using custom properties, as described in the Oracle IRM Desktop help, in the topic Adding Oracle IRM Fields in Microsoft Excel.

The problem occurs when using a combination of Microsoft Windows Vista, Microsoft Internet Explorer 7 or 8, Microsoft Office 2007, and Microsoft SharePoint 2007.

If you open a sealed Microsoft Excel spreadsheet that contains custom properties, when you go to edit the spreadsheet, the custom properties are initially shown with the placeholder #NAME? rather than with their correct values. The custom properties should update with their correct values when you start to edit the spreadsheet.

19.1.8 Behavior of Automatic Save and Automatic Recovery in Microsoft Office Applications and SharePoint

The behavior of automatic save and automatic recovery in Microsoft Office applications is as detailed below.

General

On automatic recovery, users are prompted to save the file to disk immediately in order to persist the recovered changes to a sealed file on disk. This is true for all versions and applications which support auto-recovery.

Word

- All supported versions: automatic save and recovery of sealed files should behave as normal, with the exception that automatic saving is blocked if the filename contains a dot that is not part of the extension (for example, my.filename.sdoc), or if the filename contains any double byte character.

- In Word 2010, automatically saved files recovered from the Recovery pane will not automatically prompt for a Save As: users will need to perform the Save As manually.

PowerPoint

- PowerPoint XP, 2003: automatic save and recovery of sealed files should behave as normal.

- PowerPoint 2007: the automatic saving of sealed files does not take place.

- PowerPoint 2000: automatic save is disabled if sealed files are open, meaning that, if the system crashes, any unsaved changes to any file (sealed or original) will be lost.

- PowerPoint 2010: Automatically saved files do not appear in the Recovery pane, but Microsoft Office 2010 creates auto-saved files that can be opened via the Backstage view, enabling changes to be recovered.

Excel

- All supported versions: automatically saved Excel files (.xar) will be sealed, but the recovery of these files does not happen automatically. To recover "lost" changes, users need to locate the .xar file and rename it to .sxls.

- Excel 2010: Automatically saved files do not appear in the Recovery pane, but Microsoft Office 2010 creates auto-saved files that can be opened via the Backstage view, enabling changes to be recovered.

Microsoft Office draft documents

- Microsoft Office keeps unsaved copies of files for a short period. These are accessible from the Backstage view. Oracle IRM treats these files as auto-saved files, and opening them users will be prompted to perform a Save As operation. To use the restored file in place of the original file, users must copy the saved version over the original.

Because of these restrictions, it is recommended that you do not rely on automatic save and recovery. Instead, save your work frequently when using these applications.

19.1.9 Support for Microsoft Windows 2000 Has Been Removed

Oracle IRM no longer supports the Microsoft Windows 2000 operating system.

19.1.10 Unreadable Error Message Text When Client and Server Locales are Different

Error messages are sent to the client (Oracle IRM Desktop) in the language of the server (Oracle IRM Server). Therefore, if the locale of the server is different to the locale of the client, the error code may be rendered in garbage characters. The error code remains readable, and can be provided to support services as necessary.

19.1.11 Changes Lost if Tab Changed Before Applying the Apply Button

On the Oracle IRM Server Management Console, if you make changes on a tabbed page that has an Apply button, and then move to another tab without using the Apply button, the changes will be lost. You will not be prompted to save the changes that you made.

19.1.12 Some File Formats are Not Supported When Using the Microsoft Office 2007 Compatibility Pack with Microsoft Office 2003

The following Microsoft PowerPoint and Microsoft Excel formats are not supported for sealing when using the Office 2007 Compatibility Pack with Office 2003 and earlier: SPOTM, SPOTX, SPPTM, SPPTX, SXLSX, and SXLTX. For these applications, use other file formats that are supported for sealing.

19.1.13 Microsoft Word May Hang if a Sealed Email is Open During Manual Rights Check-In

In Oracle IRM Desktop, if you attempt to check in your rights while a sealed email is open in Microsoft Word, Microsoft Word may hang. It is recommended that you do not check in your rights while a sealed email is open.

19.1.14 Sealed Emails in Lotus Notes will Sometimes Show a Temporary File Name

In Lotus Notes, if a sealed email has a communication thread with multiple messages or replies, the title bar may show a temporary file name instead of the correct subject name. You may also be prompted to save changes when you have not made any. No harm should arise from these anomalies.

19.1.15 No Support for Sealing Files of 2GB or Larger in Size in Oracle IRM Desktop

Sealing files of size 2GB or larger is not supported in the current release of Oracle IRM Desktop.

19.1.16 Inappropriate Authentication Options After Failed Login on Legacy Servers When Setting Up Search

When setting up indexed search, if you enter incorrect authentication credentials for a legacy server (for example, a 10g Oracle IRM Server) that has been set up for Windows NT authentication, the login retry dialog will show options for Windows basic authentication. You should not use Windows Authentication credentials to log in to legacy servers set up for Windows NT Authentication.

19.1.17 Opening Legacy Sealed Documents in Microsoft Office 2007 May Fail on First Attempt

If users attempt to open a legacy Microsoft Office 2007 document (a document sealed with an older version of Oracle IRM), and Oracle IRM Desktop has not been synchronized with the server against which the document was sealed, the attempt will fail. The sealed document will not be opened, and the user will not be prompted to authenticate against the server to which the document was sealed. A second attempt to open the sealed document should succeed, because the initial attempt should have synchronized Oracle IRM Desktop with the server. Alternatively, the user can synchronize to the server manually (using the Oracle IRM Desktop Options dialog) before opening a legacy sealed document.

19.1.18 Log Out Link Inoperative When Using OAM 11g for SSO

When using OAM (Oracle Access Management) 11g for SSO, the Log Out link on the Oracle IRM Server Management Console does not log the user out.

19.1.19 Double-byte Languages Cannot be Used for Entering Data with Legacy Servers

This release of Oracle IRM Desktop is available in many more languages than previous releases, including some double-byte languages. However, for legacy (10g) servers, as previously, data (user names, etc.) must still be entered using the 7-bit ASCII range of characters.

19.1.20 Use of SPACE Key Instead of Return Key in Oracle IRM Server

In some dialogs in the Oracle IRM Server Management Console, the Return key does not execute buttons. When this occurs, use the SPACE key instead.

19.1.21 Calendar Controls in Oracle IRM Server Not Accessible Via the Keyboard

In the Oracle IRM Server Management Console, the calendar controls are not accessible via the keyboard, and do not appear if the console is in Screen Reader mode. To enter a date using the keyboard, the date should be typed in.

19.2 Configuration Issues and Workarounds

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

- Section 19.2.1, "New JPS Configuration Properties for User and Group Searches"

- Section 19.2.2, "Mandatory Patch Number 12369706 For Release 11.1.1.5.0 of Oracle IRM Server, To Fix Role Edit Bug"

- Section 19.2.3, "Installing the 64-Bit Version of Oracle IRM Desktop"

- Section 19.2.4, "Reboot Necessary to Obtain New Online Information Button"

- Section 19.2.5, "Deploying Oracle IRM Using Oracle Access Manager Version 10g"

- Section 19.2.6, "LDAP Reassociation Fails if User and Group Names are Identical"

- Section 19.2.7, "Upgrading Oracle IRM Desktop From Versions Earlier Than 5.5"

- Section 19.2.8, "Synchronizing Servers After an Upgrade of Oracle IRM Desktop"

- Section 19.2.9, "Reapplying Lost Settings After an Upgrade of Oracle IRM Desktop"

- Section 19.2.10, "Changing Oracle IRM Account When Authenticated Using Username and Password"

- Section 19.2.11, "Post-Installation Steps Required for Oracle IRM Installation Against Oracle RAC"

- Section 19.2.12, "Enabling the Oracle IRM Installation Help Page to Open in a Non-English Server Locale"

19.2.1 New JPS Configuration Properties for User and Group Searches

The following new JPS configuration properties are supported in PS5. These settings allow the attributes used in the Oracle IRM Server Management Console user and group searches to be defined.

Property: oracle.irm.default.search.user.attributes

Valid values (one or more values are allowed, separated with a comma):

- NAME

- USER_NAME

- FIRST_NAME

- LAST_NAME

- BUSINESS_EMAIL

Default value = "NAME,USER_NAME,FIRST_NAME,LAST_NAME,BUSINESS_EMAIL"

Property: oracle.irm.default.search.group.attributes

Valid value:

- ROLE_NAME

Default value = "ROLE_NAME"

This complements the search filter attributes already supported in jps-config.xml.

Property: oracle.irm.default.search.filter

Valid values (one of the following):

- EQUALS

- BEGINS

- ENDS

- CONTAINS

Default value = "CONTAINS"

Example

An example JPS LDAP service instance entry:

<serviceInstance name="idstore.ldap" provider="idstore.ldap.provider">
<property name="idstore.config.provider" value="oracle.security.jps.wls.internal.idstore.WlsLdapIdStoreConfigProvider"/>
<property name="CONNECTION_POOL_CLASS" value="oracle.security.idm.providers.stdldap.JNDIPool"/>
<property name="oracle.irm.default.search.filter" value="BEGINS"/>
<property name="oracle.irm.default.search.user.attributes" value="USER_NAME,NAME,BUSINESS_EMAIL"/>
<property name="oracle.irm.default.search.group.attributes" value="ROLE_NAME"/>
</serviceInstance>

19.2.2 Mandatory Patch Number 12369706 For Release 11.1.1.5.0 of Oracle IRM Server, To Fix Role Edit Bug

The Oracle IRM Server Management Console has an issue that requires a patch to be applied to the installed or upgraded system. When selecting rights for a context, the Properties, Edit, and Remove buttons are always disabled and cannot be used. Selecting one or more rights will not enable the buttons.

Patch 12369706 fixes this issue. This patch can be downloaded from https://support.oracle.com

To install the patch:

1. Log onto https://support.oracle.com

2. Select Patches & Updates.

3. Enter the patch number 12369706 in the patch search.

4. Click Search.

5. Follow the installation instructions provided with the patch.

19.2.3 Installing the 64-Bit Version of Oracle IRM Desktop

For this release, you can choose to install a 64-bit version of the Oracle IRM Desktop client tool. There are no specific instructions for this installation, but if you attempt to install the 64-bit version in a 32-bit environment, you will see messages that this is not possible.

19.2.4 Reboot Necessary to Obtain New Online Information Button

After an upgrade from a previous release of Oracle IRM Desktop, the new Online Information button on the IRM tab in the Properties dialog (obtained by right-clicking Properties on a file in Windows Explorer) is missing until the system is rebooted. This does not affect new installations. A workaround is to restart after upgrading from a previous release of Oracle IRM Desktop, even though the installer does not prompt that a reboot is necessary.

19.2.5 Deploying Oracle IRM Using Oracle Access Manager Version 10g

Deploying Oracle IRM version 11gR1 in an environment using Oracle Access Manager version 10g requires additional configuration to process logout requests properly. For detailed information, see the section "Configuring Global Logout for Oracle Access Manager 10g and 10g WebGates" in the Oracle Fusion Middleware Application Security Guide.

19.2.6 LDAP Reassociation Fails if User and Group Names are Identical

When reassociating an LDAP identity store, the Oracle IRM process for exporting user and group information has an issue if user and group names are identical. If a user and group have identical names, the export process will lose either the user or the group details during the export step. This is because the user or group name is used as the file name, so one file overwrites the other. A post-reassociation workaround is to check user and group right assignments, and to manually reassign any that are missing.

19.2.7 Upgrading Oracle IRM Desktop From Versions Earlier Than 5.5

You can upgrade to this release from Oracle IRM Desktop version 5.5 onwards, by running the installation wizard on the computer that has the older version.

For versions earlier than 5.5, or from any version of SealedMedia Unsealer or Desktop, you can upgrade to this release only by uninstalling the older version and installing this release.

If you are upgrading to this release of Oracle IRM Desktop from a 10g release, you will lose the locally stored rights to use sealed documents (the rights that enable you to continue working when you are offline). When this happens, you will have to obtain new rights by going online and synchronizing with the server. For this reason, do not begin an upgrade unless you have online access to the server.

When upgrading on Windows Vista or Windows 7, you may encounter a file lock and be prompted to retry, ignore, or cancel. You can safely use the ignore option if this happens.

19.2.8 Synchronizing Servers After an Upgrade of Oracle IRM Desktop

If you are upgrading to this release of Oracle IRM Desktop from a 10g release, you will not be synchronized to any servers (Oracle IRM Server). This will show as a blank list on the Servers tab of the Oracle IRM Desktop Options dialog. Servers are automatically added to the list when you open sealed documents for which you have access rights. The easiest way to repopulate your list of servers is to open documents that have been sealed against servers on which you have rights.

19.2.9 Reapplying Lost Settings After an Upgrade of Oracle IRM Desktop

If you are upgrading to this release of Oracle IRM Desktop from a 10g release, your previous settings (as shown on the Oracle IRM Desktop Options dialog) are not applied to the new installation. These include support for email systems, so you should reset these before attempting to work with sealed emails in Microsoft Outlook and Lotus Notes.

19.2.10 Changing Oracle IRM Account When Authenticated Using Username and Password

Oracle IRM Desktop caches user rights in an offline database. In earlier releases, this database was shared by all users of a machine. In this release, there is one offline database per Windows user.

You are strongly advised to use only one Oracle IRM account with each Windows account.

If you authenticate to the server (Oracle IRM Server) with a username and password, you can change the account you use as follows:

1. On the Update Rights tab of the Oracle IRM Desktop Options dialog, check in rights for all servers by clicking Check in.

2. On the Servers tab of the Oracle IRM Desktop Options dialog, select the server to be updated and click Clear Password.

3. Quit from any Oracle IRM-enabled applications, such as Adobe Reader and Microsoft Office.
If you think that Oracle IRM-enabled applications may still be running, restart Microsoft Windows.

4. On the Update Rights tab of the Oracle IRM Desktop Options dialog, synchronize rights for all servers by clicking Synchronize.

Users who are automatically authenticated to the server using Windows authentication cannot change their Oracle IRM account.

Access to the offline database is protected by your Windows credentials. You are no longer required to additionally authenticate to Oracle IRM when working offline.

19.2.11 Post-Installation Steps Required for Oracle IRM Installation Against Oracle RAC

To use Oracle RAC with an Oracle IRM instance, the Oracle IRM data source needs to be altered using the WebLogic Administration Console and the following procedure:

1. From Services, select JDBC, then select DataSources.

2. Select the OracleIRM data source.

3. On the Transaction tab, check Supports Global Transactions, then check Emulate Two-Phase Commit.

4. Click Save.

This will set the global-transactions-protocol for Oracle IRM data-sources for Oracle RAC to EmulateTwoPhaseCommit.

19.2.12 Enabling the Oracle IRM Installation Help Page to Open in a Non-English Server Locale

Use the following procedure to enable the Oracle IRM installation help page to open in a non-English server locale:

1. Unzip the shiphome.

2. Extract all the non-HTM files (7 files in total) from help\en in the ecminstallhelp.jar file located in Disk1\stage\ext\jlib\

3. Put these 7 files into the folder jar for the locale in which you will install ECM.

4. Overwrite ecminstallhelp.jar with the modified version.

19.3 Documentation Errata

There are no known issues at this time.

20 Oracle WebCenter Content

This chapter describes issues associated with Oracle WebCenter Content. It includes the following topics:

- Section 20.1, "General Issues and Workarounds"

- Section 20.2, "Configuration Issues and Workarounds"

- Section 20.3, "Documentation Errata"

20.1 General Issues and Workarounds

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

- Section 20.1.1, "Site Studio Does Not Support Multibyte Characters in Site IDs, Directory Names, and Page Names"

- Section 20.1.2, "Site Studio Publisher Does Not Support Multibyte Characters"

- Section 20.1.3, "Oracle WebCenter Content Servers and IPv6 Support"

- Section 20.1.4, "Content Categorizer Trace Log Settings Discontinued"

- Section 20.1.5, "Extra Lines Displayed Viewing Contribution Folders in Internet Explorer 8"

- Section 20.1.6, "WebDAV Connection Fails After Logout or Restart"

- Section 20.1.7, "Detailed Oracle OpenOffice Configuration Settings"

- Section 20.1.8, "Clarification When Setting Classpath to OpenOffice Class Files"

- Section 20.1.9, "Inbound Refinery PDF Conversion May Differ Visually from the Original Content"

- Section 20.1.10, "Mismatching User and Server Locales Prevent Access to Oracle E-Business Suite and PeopleSoft Managed Attachment Pages in WebCenter Content"

- Section 20.1.11, "Connection Issues with Windows to WebDAV"

- Section 20.1.12, "Manual Addition of xdoruntime.ear Library for Records Management"

- Section 20.1.13, "Using HCSP Custom Elements with SSXA"

- Section 20.1.14, "Backing Up Site Studio Websites Using Chrome"

- Section 20.1.15, "DAM Video Storyboard Errors With Chrome and Safari"

- Section 20.1.16, "Issues Applying Table Styles When Using FireFox and FCK Editor"

- Section 20.1.17, "Content Information Server Is Not Supported for 11g"

- Section 20.1.18, "Window Size Using Trays with Firefox"

- Section 20.1.19, "VB6 Component Dependency for Kofax 9"

- Section 20.1.20, "Using URLs With SSP Include and Exclude Filters"

- Section 20.1.21, "Disabling the Folders_g Deprecation Alert"

- Section 20.1.22, "Accessing ZipRenditionStaticAccess Scheduled Job Information"

- Section 20.1.23, "Check-in and Search Forms Pop Up Error Messages when UCM is in EBR Mode"

- Section 20.1.24, "View Publishing Errors Are Observed in Logs When UCM is in EBR Mode"

- Section 20.1.25, "Optimization Errors with External OracleTextSearch"

- Section 20.1.26, "Propagating the cwallet.sso Changes to Deployment Manager"

- Section 20.1.27, "UCM in EBR Mode Fails to Start when Dynamic Converter Component is Enabled"

- Section 20.1.28, "Content Tracker Report Date Format Supported in Nine Languages"

- Section 20.1.29, "Inbound Refinery PDF Optimization Not Supported with Ghostscript 9.07"

- Section 20.1.30, "Thai Locale in Firefox Browser Displays Larger Asian Font"

- Section 20.1.31, "'Show on Top' Context Menu Option Does Not Display as Expected in WebCenter Content User Interface"

- Section 20.1.32, "Using Dropdown Menu on Chrome When Ask.com Toolbar Present"

- Section 20.1.33, "Using Tabular View in Screen Reader Mode in WebCenter Content User Interface"

- Section 20.1.34, "Framework Folders AutoSuggest Type-Ahead Feature Limitation"

- Section 20.1.35, "Site Studio ASP and JSP Sites Functionality in 11gR1"

20.1.1 Site Studio Does Not Support Multibyte Characters in Site IDs, Directory Names, and Page Names

Oracle Site Studio does not support multibyte characters in any value that will be used in URLs, including site IDs, directory names, and page names.

20.1.2 Site Studio Publisher Does Not Support Multibyte Characters

Oracle Site Studio Publisher does not support multibyte characters.

20.1.3 Oracle WebCenter Content Servers and IPv6 Support

Oracle WebCenter Content servers are supported on IPv4/IPv6 dual-stack hosts, but not on"IPv6-only" hosts. The following topologies are supported:

- Oracle Database on IPv4 hosts

- Oracle WebCenter Content, Oracle WebCenter Content: Records, Oracle WebCenter Content: Inbound Refinery on IPv4/IPv6 dual-stack hosts

- Client (browser) on either IPv4 or IPv6 hosts

20.1.4 Content Categorizer Trace Log Settings Discontinued

The Content Categorizer-specific execution trace log settings are discontinued. Use the Content Server System Audit Information facility instead. To enable Content Categorizer execution trace, enter contentcategorizer in the Active Sections control of the Tracing Sections Information section of the Admin System Audit Information page.

20.1.5 Extra Lines Displayed Viewing Contribution Folders in Internet Explorer 8

When using Folders in Internet Explorer 8 with default settings, IE8 adds extra lines. This is solved by opening the Compatibility View Settings dialog and unselecting the Display intranet sites in Compatibility View checkbox.

20.1.6 WebDAV Connection Fails After Logout or Restart

In Windows 7 and Windows Vista clients, after logging out and logging back in or after restarting, the Network Place used to access WebCenter Content over WebDAV may no longer work. This is solved by deleting and recreating the connection.

20.1.7 Detailed Oracle OpenOffice Configuration Settings

When configuring Inbound Refinery to convert content using Oracle OpenOffice, additional configuration details can be found in the Oracle 10g release of the PDF Converter Installation and Administration Guide. The complete guide is available for download in either PDF or HTML format from Oracle Technology Network at the following URL:

http://download.oracle.com/docs/cd/E10316_01/ouc.htm

Oracle OpenOffice configuration is detailed in the "OpenOffice" section of "Installing Third-Party Applications" in Chapter 4, "Installing PDF Converter" and can be accessed directly at the following URL:

http://download.oracle.com/docs/cd/E10316_01/refinery/refinery_doc_10/pdfconverter/wwhelp/wwhimpl/common/html/wwhelp.htm?context=install_admin_pdfc_10en&file=page_04_19.htm

Oracle OpenOffice configuration is detailed in the "OpenOffice" section of "Installing Third-Party Applications" in Chapter 4, "Installing PDF Converter" and can be accessed directly at the following URL:

http://download.oracle.com/docs/cd/E10316_01/refinery/refinery_doc_10/pdfconverter/wwhelp/wwhimpl/common/html/wwhelp.htm?context=install_admin_pdfc_10en&file=page_04_19.htm

20.1.8 Clarification When Setting Classpath to OpenOffice Class Files

In the Oracle Digital Asset Manager and Conversion Administration guide, chapter 2 "Managing Conversions" under the section "Configuring Content Server and Refinery Communication," step 2 asks you to enter:

JAVA_CLASSPATH_openoffice_jars=<OfficePath>/Basis/program/classes/unoil.jar:<OfficePath>/URE/java/ridl.jar:<OfficePath>/URE/java/jurt.jar:<OfficePath>/URE/java/juh.jar

Note that the true value for <OfficePath> is likely to include spaces and care must be taken when setting this in a Microsoft Windows environment.

Ensure that the paths are not enclosed in quotes, that slashes (/) are used for path separators and not backslashes (\), and that any space in the path is escaped using a backslash (\). For example, a properly formed classpath in a Windows environment could look like this:

JAVA_CLASSPATH_openoffice_jars=C:/Program\Files/OpenOffice.org\3/Basis/program/classes/unoil.jar:C:/Program\Files/OpenOffice.org\3/URE/java/ridl.jar:C:/Program\ Files/OpenOffice.org\3/URE/java/jurt.jar:C:/Program\ Files/OpenOffice.org\ 3/URE/java/juh.jar

20.1.9 Inbound Refinery PDF Conversion May Differ Visually from the Original Content

Oracle WebCenter Content: Inbound Refinery makes every effort to maintain the visual integrity and formatting of content being converted from its native format to PDF, but Oracle cannot guarantee that the resulting PDF will be an exact visual replication.

20.1.10 Mismatching User and Server Locales Prevent Access to Oracle E-Business Suite and PeopleSoft Managed Attachment Pages in WebCenter Content

For the Oracle E-Business Suite and PeopleSoft managed attachment function in WebCenter Content, users are not granted access to managed attachment pages if their user locale does not match the server locale, which means they cannot view these pages.

20.1.11 Connection Issues with Windows to WebDAV

Supported Windows operating systems may have difficulty connecting to a WebDAV server running over HTTP and using HTTP Basic authentication in some situations. To correct for this, you must edit the registry of the client computer to enable Basic authentication. For detailed information, see Microsoft Knowledge Base Article 841215 at http://support.microsoft.com/kb/841215.

20.1.12 Manual Addition of xdoruntime.ear Library for Records Management

If the Records Management feature is installed in an Oracle WebCenter Content product, xdoruntime.ear library needs to be added manually from the Oracle WebLogic administration console after a domain is created. A reference to the library must be added to the weblogic-application.xml file of the Oracle WebCenter Content EAR file before the managed server is started for the first time.

To add xdoruntime.ear to the WebLogic WebCenter Content domain, follow these steps:

1. After a domain is created, start the Admin Server only. If a managed WebCenter Content server has already been started, then the administrator will have to perform additional steps to add reference to the deployed WebCenter Content server instance later.

2. Open WebLogic console in browser. Click on Deployments in the left pane. Browse the pages to check if there is already a xdoruntime.ear file in the WebLogic administration console. If it is already present, then no more steps need to be performed.

3. If no xdoruntime.ear file is present, click Install on the Deployments display. A file selection dialog opens. Browse the available file system and select xdoruntime.ear in the following path:

/FMW_HOME/Oracle_ECM1/ucm/idc/components/ReportPublisher/lib/xdoruntime.ear

4. Click Next. The option page to select the file as library opens. Select "Install this deployment as a library" and click Next.

5. The Target Selection Screen opens. Select all targets and click Next.

6. The Deployment Name screen opens. In the Security section, select "DD Only: Use only roles and policies that are defined in the deployment descriptors." In the Source accessibility section, select "Copy this application onto every target for me" and click Next.

7. In the Additional Configuration section, select "Yes, Take me to the deployment's configuration screen" and click Finish. The library is now deployed in the environment.

To reference the deployed library from the WebCenter Content Enterprise Application library, follow these steps:

1. Extract the cs.ear file from the following path:

/FMW_HOME/Oracle_ECM1/ucm/idc/components/ServletPlugin/cs.ear

2. In the extracted directory modify META-INF/weblogic-application.xml and add the following line for library reference:

<library-ref>
<library-name>oracle.xdo.runtime</library-name>
</library-ref>

3. Create an archive file named cs.ear from the extracted modified directory and replace the file by the same name in the path it was retrieved from. This change will take for all undeployed WebCenter Content server instances.

4. Start the managed server.

If the managed server has been started at least once after the domain has been created, complete the following:

- Locate the weblogic-application.xml of the Oracle WebCenter Content enterprise application in the deployed WebCenter Content domain at a path similar to the following example:

/FMW_HOME/domain path/servers/UCM_server1/servers/UCM_server1/tmp/_WL_user/Oracle Universal Content Management - Content Server/k6ggd/META-INF/weblogic-application.xml

Modify the META-INF/weblogic-application.xml and add the following line for library reference:

<library-ref>
<library-name>oracle.xdo.runtime</library-name>
</library-ref>

If the UCM_server1 is not available in /FMW_HOME/domain path/servers/, then this step is not needed, as the managed server has not been started, which would have deployed the UCM_server1 at this location.

20.1.13 Using HCSP Custom Elements with SSXA

When a new custom element form is created from scratch (rather than copying an existing form to build an element from), it may have issues lading properly in SSXA.

To use HCSP custom elements within SSXA, you must include the following in the SSXA application's web.xml file:

<mime-mapping>
<extension>hcsp</extension>
<mime-type>text/html</mime-type>
</mime-mapping>

This will allow the files related to the custom element to be executed rather than downloaded.

20.1.14 Backing Up Site Studio Websites Using Chrome

When backing up a Site Studio website using Chrome, and manage the archive and download as a ZIP file, the name of the ZIP file might not be as expected.

The name of an archive downloaded as a ZIP file should be in this format: server_DDMMYYYY_HHMMSS.zip. But when using Chrome, the name may be idcplg.zip.

20.1.15 DAM Video Storyboard Errors With Chrome and Safari

The storyboard links on the Rendition Info page for a video item (which should make the video start playing at a specific spot) are not working in Chrome or Safari browsers with Windows Media or QuickTime player plug-ins. Nothing happens when you click on the links. They do work in Chrome and Safari with the flash player, and they work with all plugins in Firefox and IE.

20.1.16 Issues Applying Table Styles When Using FireFox and FCK Editor

When using FCK editor and the Firefox browser with Site Studio Contributor, it is difficult to apply available table styles to a table. This is a functionality missing from FCK editor, and not a limitation of Firefox or Site Studio.

20.1.17 Content Information Server Is Not Supported for 11g

Oracle Content Information Server (CIS) is not supported for WebCenter Content 11g connections in any formats.

20.1.18 Window Size Using Trays with Firefox

When using the Trays view with Site Studio on the Content Server, some screens viewed with the Firefox browser may not correctly fill the browser window.

20.1.19 VB6 Component Dependency for Kofax 9

Kofax 9 does not install VB6 components required for many of the Export Connectors. Install and register the required VB6 components to use the Export Connectors.

20.1.20 Using URLs With SSP Include and Exclude Filters

If URLs are used in the Include or Exclude Filters list then any periods ('.') will need to be escaped, otherwise the filter will fail. For example:

http://www\.oracle\.com/information/about\.html

Note the '.' have been escaped with '\'

20.1.21 Disabling the Folders_g Deprecation Alert

There is an alert displayed when Folders_g is enabled that says, "The Folders_g component is in use but is now deprecated. Folders_g is replaced with the FrameworkFolders component, which implements the Folders feature. Folders_g data can be migrated to the new Folders feature."

To prevent this alert from displaying, open the config.cfg file and set the following configuration value:

DisableFoldersgDeprecationMesssage=1

20.1.22 Accessing ZipRenditionStaticAccess Scheduled Job Information

The ZipRenditionManagement component automatically creates a scheduled job to aid in the creation of static renditions. This job is sometimes created at the wrong time during the setup or configuration process, which causes an error when an administrator accesses the Administration > Scheduled Jobs Administration > Active Scheduled Jobs page. If the administrator deletes the job and restarts Content Server, the job will be recreated, and the Active Scheduled Jobs page will not throw an error.

20.1.23 Check-in and Search Forms Pop Up Error Messages when UCM is in EBR Mode

When UCM is run in EBR more, the following errors pop up when opening check-in or search forms.

"Unable to generate data for the view websiteobjecttypelist. Unable to build where clause for for view WebsiteObjectTypeList. The field dKey does not exist in table OptionsList"

"Unable to generate data for the view pachagedconversionslist. Unable to build where clause for for view PachagedConversionsList. The field dKey does not exist in table OptionsList"

"Unable to generate data for the view pdfwtemplatetypelist. Unable to build where clause for for view PdfwTemplateTypeList. The field dKey does not exist in table OptionsList"

"Unable to generate data for the view videorenditionslist. Unable to build where clause for for view VideoRenditionsList. The field dKey does not exist in table OptionsList"

As a result, some dropdowns in the forms are not populated with data.

20.1.24 View Publishing Errors Are Observed in Logs When UCM is in EBR Mode

Once UCM managed server is started, errors of the kind !csSchemaUnableToPublishView can sometimes be seen. These errors happen only when UCM is in EBR mode.

20.1.25 Optimization Errors with External OracleTextSearch

When using OracleTextSearch using an Oracle 11.2.0.2.0 database as an external search provider, optimization errors may appear in the logs. It is an issue with the database, not UCM. This issue is resolved in the 11.2.0.3.0 database.

20.1.26 Propagating the cwallet.sso Changes to Deployment Manager

The updates to the cwallet.sso file, in some cases, are not propagated from the UCM server to the Deployment Manager. In these cases, you must propagate the change manually.

The Oracle UCM server updates the cwallet.sso file located in

WAS_PROFILES/UCM_SERVER_NAME/config/cells/UCM_CELL_NAME/fmwconfig/

when it starts after completing configuration on the Post Install Configuration Page or after enabling PdfWatermark or BpelIntegration components. In these instances, propagate this change back to the Deployment Manager.

To do this, copy the cwallet.sso file to

WAS_PROFILES/DEPLOYMENT_MANAGER_NAME/config/cells/UCM_CELL_NAME/fmwconfig/

immediately after the start.

20.1.27 UCM in EBR Mode Fails to Start when Dynamic Converter Component is Enabled

When the UCM is in EBR mode, and Dynamic Converter is enabled, UCM managed server will not start due to an error with creating the HtmlConversions object. An ORA-00955 error will be referenced in this exception:

!csDbUnableToPerformAction_create,HtmlConversions!$ORA-00955: name is already used by an existing object

A possible workaround is to disable DynamicConverter component using the Component Wizard.

20.1.28 Content Tracker Report Date Format Supported in Nine Languages

Auto-filled dates in the Content Tracker Report page are only supported in nine languages. If the admin locale is not set to one of the nine languages, the date format is displayed in the default (English).

The nine supported admin locales are: Chinese-Simplified, Chinese-Traditional, Deutsche, English-UK, English-US, Espanol, Francais, Italiano, Japanese.

20.1.29 Inbound Refinery PDF Optimization Not Supported with Ghostscript 9.07

When using Inbound Refinery WinNativeConverter to convert documents to PDF, the PDF Optimization option does not work if the distiller being used is Ghostscript version 9.07. PDF Optimization does work with Ghostscript version 9.06.

20.1.30 Thai Locale in Firefox Browser Displays Larger Asian Font

When using Firefox browser with Content Server set for the Thai locale, the font size for Asian characters is larger than for non-Asian characters. This issue is specific to Firefox. A general recommendation is to use a different browser.

A workaround for using Firefox with the Thai locale is to access the Accessibility preferences in Content Server and select Use Large Fonts. Then in the Firefox Options, open the Advanced dialog in the Fonts & Colors section and deselect "Allow pages to choose their own fonts." The Thai font will display more accurately.

20.1.31 'Show on Top' Context Menu Option Does Not Display as Expected in WebCenter Content User Interface

When using the WebCenter Content user interface (as opposed to the native 11g interface) to work with a multi-level folder tree and doing a right-click on a sub-folder to display the "Show on Top" context menu option, the option is not always immediately displayed. Also, when the option does display, it does not always immediately function when clicked.

A workaround is always select the folder first (by doing a left-click), then do a right-click to invoke the context menu.

20.1.32 Using Dropdown Menu on Chrome When Ask.com Toolbar Present

When using the WebCenter Content user interface (as opposed to the native 11g interface) and Chrome, the presence of the Ask.com toolbar disables dropdown menu functionality. A workaround is to remove the Ask.com toolbar.

20.1.33 Using Tabular View in Screen Reader Mode in WebCenter Content User Interface

When using the WebCenter Content user interface (not the native 11g interface) in Screen Reader mode to access a Documents, Libraries, Favorites, or Folders page, then switching to the Tabular view, an error will occur if you perform a right click to get to the Context menu. The workaround is to select the desired document and then access the Context menu by using the menu bar and More menu. This situation only occurs when using the Screen Reader mode with the Tabular view.

20.1.34 Framework Folders AutoSuggest Type-Ahead Feature Limitation

When the WebCenter Content user interface is implemented instead of the native 11g interface, Framework Folders must be enabled (Folders_g cannot be used). As of 11.1.1.8.0, Framework Folders uses an AutoSuggest type-ahead feature when users enter search terms. The AutoSuggest feature is required and is enabled as part of the AutoSuggestConfig component with the WebCenter Content user interface. By default the AutoSuggest index engine splits a term into grams and stores them in the index. For better performance the minimum gram length is set to a default of 2. Because the minimum gram length is 2, users cannot select user and role names that are only one character in length. Avoid creating documents, folders, libraries, users, and roles with a single character name.

20.1.35 Site Studio ASP and JSP Sites Functionality in 11gR1

Active Server Page (ASP) and Java Server Pages (JSP) sites are still available for legacy (pre-10gR4) projects, but they do not have 11gR1 functionality. They will function as they did with previous releases of Site Studio.

ASP sites will work only when the Site Studio 11gR1 component is installed on a 10g Content Server. IIS is not a supported web server for 11g Content Server, so it is not possible for ASP sites to work out-of-the-box on 11g Content Server.

20.2 Configuration Issues and Workarounds

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

- Section 20.2.1, "Minimum JDBC Driver Version Required for Oracle Text Search Component"

- Section 20.2.2, "Setting Security Privileges for Modifying Contribution Folders"

- Section 20.2.3, "Site Studio for External Applications (SSXA) Port Values for Oracle Content Server 10gR3"

- Section 20.2.4, "SSXA Required DC Version for Oracle Content Server 10gR3"

- Section 20.2.5, "Content Portlet Suite (SCPS) WebCenter as Producer Targeting Libraries"

- Section 20.2.6, "Logout URL for SSO Logout Integrating with Oracle Access Manager 11g"

- Section 20.2.7, "Using the Custom Truststore with the JPS Connection to ActiveDirectory"

- Section 20.2.9, "Electronic Signature Login and Time Limit"

- Section 20.2.10, "Configuring Temporary Directories"

- Section 20.2.11, "Setting Maximum Windows Per Session Parameter"

- Section 20.2.12, "AutoSuggestConfig Component Must Be Disabled in Native 11g Interface"

- Section 20.2.13, "Content Server Localization and Verbose Tracing"

- Section 20.2.14, "FrameworkFolders Patch for Release 11gR1 (11.1.1.8.0)"

20.2.1 Minimum JDBC Driver Version Required for Oracle Text Search Component

The Oracle Text Search component that is part of WebCenter Content 11gR1 requires a JDBC driver version of 10.2.0.4 or higher. The component will not work with older JDBC driver versions.

20.2.2 Setting Security Privileges for Modifying Contribution Folders

By default, users only need RW privileges to modify contribution folders (Folders_g), where before the default was that RWD or owner was required unless collaboration was enabled.

Users explicitly relying on RWD privileges must set the environment variable to allow for this. WebCenter users and those with no upgrade issues are not affected.

For those who require RWD rather than RW, set the variable as:

FoldersModifyWithRW=false

20.2.3 Site Studio for External Applications (SSXA) Port Values for Oracle Content Server 10gR3

The JDeveloper Site Studio for External Applications connections dialog is pre-populated with a default web connection port value of 16200 for an Oracle Content Server 11g instance. Oracle Content Server 10gR3 web servers most often listen on port 80. As such, this value will likely have to be changed when connecting to an Oracle Content Server 10gR3 instance.

20.2.4 SSXA Required DC Version for Oracle Content Server 10gR3

To use dynamic conversion of native documents on your Site Studio web sites running off of Oracle Content Server 10gR3, you must install and configure Dynamic Converter build version 8.1.0.736 or greater.

20.2.5 Content Portlet Suite (SCPS) WebCenter as Producer Targeting Libraries

When creating a custom managed server, the following libraries need to be targeted to the newly created managed server (for example, CPS_Portlet). Note that the libraries for 11gR1 PS2 (11.1.1.3) are different from the libraries for 11gR1 PS3 (11.1.1.4) and 11gR1 PS4 (11.1.1.5) installation of WebCenter.

Libraries for 11gR1 PS2 (11.1.1.3) installation of WebCenter:

- oracle-ridc-client-app-lib(10.3.2,10.3.2)

- oracle-ucm-spi-app-lib(10.3.2,10.3.2)

- p13n-app-lib-base(10.3.2,10.3.2)

- vcr-app-lib(10.3.2,10.3.2)

- oracle.webcenter.framework(11.1.1,11.1.1)

- oracle.webcenter.spaces.fwk(11.1.1,11.1.1)

Libraries for 11gR1 PS3 (11.1.1.4) and 11gR1 PS4 (11.1.1.5) installation of WebCenter:

- oracle.ucm.ridc.app-lib(11.1.1,11.1.1)

- p13n-app-lib-base(10.3.2,10.3.2)

- oracle.webcenter.framework(11.1.1,11.1.1)

- oracle.webcenter.spaces.fwk(11.1.1,11.1.1)

- oracle.webcenter.framework.core(11.1.1,11.1.1)

When consuming Oracle Content Portlet Suite 11gR1 PS3 (11.1.1.4) on Oracle WebCenter 11gR1 PS3 (11.1.1.4), users will see the exception "java.lang.IllegalArgumentException:IdcContext.setUser() method not valid, do not use this method."

Contact Oracle support for the options available to resolve this issue.

20.2.6 Logout URL for SSO Logout Integrating with Oracle Access Manager 11g

When integrating WebCenter Content with Oracle Access Manager 11g, add the following to the Logout URL setting for the WebGate:

/oamsso/logout.html

20.2.7 Using the Custom Truststore with the JPS Connection to ActiveDirectory

JpsUserProvider should be up for WebCenter Content to be able to fetch users' roles/groups from the LDAP server. The JPS layer does not automatically pick up the SSL truststore configuration from WLS. Since a custom truststore is being used in the WLS configuration, the problem is that the JPS connection to ActiveDirectory is not using this custom truststore.

Therefore, set the following Java properties when starting UCM_server1:

Djavax.net.ssl.trustStore=<location of custom truststore>
Djavax.net.ssl.trustStorePassword=<truststore password>

If you start the server from the command line using startManagedWeblogic.sh you can set the environment variable EXTRA_JAVA_PROPERTIES before invoking startManagedWeblogic.sh.

If you start the server using the NodeManager, these can be set using the WLS Admin console by setting the Arguments in the Server Start tab for the Configuration of UCM_server1.

20.2.8 Setting the Connection Pool for an External LDAP ID Store on IBM WebSphere Application Servers

An LDAP server is not automatically installed and configured when you install Oracle WebCenter Content on IBM WebSphere Application Server - Network Deployment (ND) or IBM WebSphere Application Server. Before you can configure WebCenter Content, you must install and configure an external LDAP identity store for your WebCenter Content applications. For information about how to set up external LDAP identity stores, such as Oracle Internet Directory, see the "IBM WebSphere Identity Stores" section of the "Managing Oracle Fusion Middleware Security on IBM WebSphere" chapter of the Oracle Fusion Middleware Third-Party Application Server Guide.

After the LDAP identity store is set up for a cell, you must set the CONNECTION_POOL_CLASS property in the cell's jps-config.xml file to avoid excessive LDAP connections. You need to add the following property to the <serviceInstance> entry in the file:

<property name="CONNECTION_POOL_CLASS" value="oracle.security.idm.providers.stdldap.JNDIPool"/>

To set the connection pool for an external LDAP ID store on IBM WebSphere application servers:

1. Modify your cell's jps-config.xml file with a text editor:

1. Open the WAS_HOME/profiles/profile_name/config/cells/cell_name/fmwconfig/jps-config.xml file.
WAS_HOME is the location where the WebSphere application server is installed, DISK/IBM/WebSphere/Application Server by default, profile_name is the name of the WebSphere Deployment Manager profile for the cell, and cell_name is the name of the cell.

2. Specify the CONNECTION_POOL_CLASS property in the <serviceInstance> entry as follows:

<serviceInstance name="idstore.ldap.0" provider="idstore.ldap.provider">
<property name="subscriber.name" value="dc=us,dc=oracle,dc=com"/>
<property name="CONNECTION_POOL_CLASS" value="oracle.security.idm.providers.stdldap.JNDIPool"/>
<property name="bootstrap.security.principal.key" value="bootstrap_idstore"/>
<property name="idstore.type" value="OID"/>
<property name="ldap.url" value="ldap://example.com:3060"/>
<property name="bootstrap.security.principal.map" value="BOOTSTRAP_JPS"/>
<property name="user.login.attr" value="mail"/>
<property name="username.attr"  value="mail"/>
<extendedProperty>
<name>user.search.bases</name>
<values>
<value>cn=Users,dc=us,dc=oracle,dc=com</value>
</values>
</extendedProperty>
<extendedProperty>
<name>group.search.bases</name>
<values>
<value>cn=Groups,dc=us,dc=oracle,dc=com</value>
</values>
</extendedProperty>
</serviceInstance>

2. Synchronize all managed nodes.

3. Restart all the servers.

For more information about installing and configuring Oracle WebCenter Content on WebSphere application servers, see the "Managing Oracle WebCenter Content on IBM WebSphere Application Servers" chapter of the Oracle Fusion Middleware Third-Party Application Server Guide.

20.2.9 Electronic Signature Login and Time Limit

The electronic signature authentication process has been redesigned to include changes to the ESIG_GET_SIGN_CONTENT_FORM and ESIG_SIGN_CONTENT services in order to redirect users to the Oracle WebLogic Server login page before they can sign content items.

The Sign Content Item page has a time limit cookie (the default is 2 minutes) for re-authenticating users before signing content items. The cookie timeout can be reconfigured by setting the ESigCookieTimeOut property (with the value in seconds) in the electronicsignatures_environment.cfg file. For example, to set the cookie timeout value to 30 seconds, specify the following: ESigCookieTimeOut=30

20.2.10 Configuring Temporary Directories

For systems using the WebCenter Content user interface instead of the native 11g interface, the administrator must set the application configuration property temporaryDirectory to a safe location that does not automatically get cleaned up by the operating system or other scheduled jobs.

For example, if the temporaryDirectory property is not set, on the Linux operating system it defaults to /tmp. Many Linux distributions include cron jobs that automatically clean up the /tmp directory. If this happens, the application cannot recover from this unexpected error and it needs to be restarted.

20.2.11 Setting Maximum Windows Per Session Parameter

For systems using the WebCenter Content user interface instead of the native 11g interface, the configuration parameter maximumWindowsPerSession is used to limit the number of active Doc Properties windows. The default is set to 10. If the WebCenter Content instance is experiencing higher than desired memory consumption, the setting can be changed to 6 to reduce the required heap size.

20.2.12 AutoSuggestConfig Component Must Be Disabled in Native 11g Interface

The AutoSuggestConfig component is a new feature that is valid only with the WebCenter Content user interface, not with the native 11g interface. When using the WebCenter Content user interface, both the FrameworkFolders and AutoSuggestConfig components are required and must be enabled. When using the native 11g interface, the AutoSuggestConfig component must be disabled, even if the FrameworkFolders component is enabled.

20.2.13 Content Server Localization and Verbose Tracing

Enabling Content Server localization tracing with Verbose also enables strict error detection. As a result, Content Server throws an exception when it tries to localize a key that is not valid. When Content Server gets in this state, the only solution is to restart the server. To disable strict error detection for localization, set the parameter EnableLocalizationAssertions=false in the config.cfg file.

20.2.14 FrameworkFolders Patch for Release 11gR1 (11.1.1.8.0)

Administrators should contact Support to obtain a patch for the following FrameworkFolders bugs in release 11gR1 (11.1.1.8.0):

- 17171852: FLD_PROPAGATE Should Not Allow Content to Have xLibraryGUID Altered

- 17171834: UPDATE_DOCINFO Should Not Allow Content to Have xLibraryGUID Altered

- 17171818: UPDATE_DOCINFO Should Not Allow Content to be Unfiled

- 17164502: UPDATE_DOCINFO to Move Content from EL to ADHOC Does Not Error

- 17160600: UPDATE_DOCINFO to Move Content from EL to Another EL Does Not Update GUID

- 17153780: Move of an EL Folder to Another EL Folder, Subfolder Content Fail to Update GUID

- 17362858: FLD_MOVE to /Enterprise Libraries Does Not Update xLibraryGUID

- 17323595: Copying a Folder: All Files Are Flattened into One Directory

- 17317268: FLD_MOVE with OverrideDuplicates Does Not Correctly Handle xLibraryGUID

- 17314494: Folder Move with RESOLVE on a Folder Renames Subfolders in Conflict Resolution

- 17312366: FLD_COPY with ReviseDuplicates Does Not Correctly Handle xLibraryGUID

20.3 Documentation Errata

This section describes documentation errata. It includes the following topics:

- Section 20.3.1, "Content Portlet Suite (CPS) WSRP URLs for WebCenter as Producer"

- Section 20.3.2, "Update Component Configuration Information Missing in 11.1.1.8.0 Documentation Set"

20.3.1 Content Portlet Suite (CPS) WSRP URLs for WebCenter as Producer

After deploying the CPS EAR file to WebCenter as a producer, the WSDL URL for 11g PS2 (11.1.1.3) is different from the WSDL URL for PS3 (11.1.1.4) and PS4 (11.1.1.5). For more information, see the Deployment Guide for Content Portlet Suite, Section 3.1.4, Step 17.

WSRP URL for PS2 (11.1.1.3) installation of WebCenter:

http://Host_Name:Port/cps/portlets/wsrp1?wsdl

WSRP URL for PS3 (11.1.1.4) and PS4 (11.1.1.5) installations of WebCenter:

http://Host_Name:Port/cps/portlets/wsrp2?WSDL

20.3.2 Update Component Configuration Information Missing in 11.1.1.8.0 Documentation Set

Update component configuration information included in the 11.1.1.6.0 documentation set is not included in the 11.1.1.7.0 and 11.1.1.8.0 documentation sets. The information in section A.3.7 "Update Component Configuration Interface" in the 11.1.1.6.0 Oracle WebCenter Content System Administrator's Guide for Content Server is valid and can be viewed on the Oracle online documentation library at http://docs.oracle.com/cd/E23943_01/doc.1111/e10792/e01_interface.htm#CIACFBAG

21 Oracle WebCenter Content: Records

This chapter describes issues associated with Oracle WebCenter Content: Records. It includes the following topics:

- Section 21.1, "General Issues and Workarounds"

- Section 21.2, "Configuration Issues and Workarounds"

- Section 21.3, "Documentation Errata"

In addition to the information discussed here, see the chapter in this release note documentation concerning Oracle WebCenter Content. Issues which affect WebCenter Content may also affect Records.

21.1 General Issues and Workarounds

This section describes general issues and workarounds. It contains the following sections:

- Section 21.1.1, "Role Report Output is Dependent on User Generating the Report"

- Section 21.1.2, "Items Returned When Using Screening"

- Section 21.1.3, "Oracle Text Search and Report Configuration Options"

- Section 21.1.4, "Upgrade from 10g Audit Trail Periods Missing"

- Section 21.1.5, "DB2 Databases and FOIA/PA Functionality"

- Section 21.1.6, "Sorting and Listing Retention Category Content"

- Section 21.1.7, "Using Firefox to Configure the Dashboard"

- Section 21.1.8, "Setting Security Group for Retention Items"

21.1.1 Role Report Output is Dependent on User Generating the Report

A role report can be generated by choosing Records then Reports then Role from the Main menu. Note that the output of the report may not show all data for all roles. The output is dependent on the user who is generating the report and the permissions given to that user.

21.1.2 Items Returned When Using Screening

It should be noted that screening is a retention feature that only returns content items with a life cycle or items that are frozen.

21.1.3 Oracle Text Search and Report Configuration Options

When using Oracle Text Search, an incompatibility existed with the options to exclude report templates and reports in search results. These options appear on the Configure Report Settings Page.

It is now possible to exclude reports in search results by selecting the Exclude Reports in Search Results checkbox. However, if the Exclude Report Template in Search Results checkbox is selected, templates are still included in searches. Oracle is aware of this issue and is working to fix it in a future release.

21.1.4 Upgrade from 10g Audit Trail Periods Missing

When upgrading this product from release version 10g to release version 11g, the complete audit trail dates are not available. The audit periods from 2001 to 2010 should be present after upgrading, but only periods between 2001 to 2006 are present. The missing years can be added manually. Oracle is aware of this issue and is working to fix it in a future release.

21.1.5 DB2 Databases and FOIA/PA Functionality

Due to the size of the database used with the Freedom of Information Act/Privacy Act (FOIA/PA) functionality, the FOIA/PA option is not supported for those sites using DB2 for their database.

21.1.6 Sorting and Listing Retention Category Content

When retention categories are sorted then listed, they are listed on a per-source basis. For example, if three sources are used (Source1, Source2, Source3), all items from Source1 are sorted as a separate group, items from Source2 are sorted as a separate group, and items from Source3 are sorted as a separate group. Then items from each source are displayed in a "round robin" style with the first item of Source1, the first item from Source2, and the first item from Source3, followed by the second item of each source.

21.1.7 Using Firefox to Configure the Dashboard

"Drag and drop" functionality to move dashboard panels is not available when using the Firefox browser. Instead, you should remove the panel and re-insert a new panel in the proper location.

21.1.8 Setting Security Group for Retention Items

Items created for use in the Retention Schedule should have the security group set to recordsgroup rather than Public. If set to Public, non-URM users may have access to items in the Retention Schedule when performing standard searches.

21.1.9 Problem Viewing the Search Results

If you upgrade URM from 10g to 11.1.1.8.0 using a DB2 database, then you will be able to view only the first page of the search results. Attempts to view subsequent pages will display blank pages.

To workaround, go to Settings and then RM Security Options. Select one of the options like Supplemental Marking or Classification. Ensure that the no security or no post filtering rights are turned off.

21.2 Configuration Issues and Workarounds

This section describes configuration issues and workarounds. It contains the following sections:

- Section 21.2.1, "Import FOIA Archive Error Message"

- Section 21.2.2, "Restart Required: Performance Monitoring and Reports"

- Section 21.2.3, "Audit Trail Sorting Results and Database Fulltext Search"

- Section 21.2.4, "Prefix Size Limitation When Using Offsite Storage"

- Section 21.2.5, "Enabling Email Metadata Component"

- Section 21.2.6, "Relative Web Root Must Be Changed"

- Section 21.2.7, "Configuring 10g Adapters for Version 11g"

- Section 21.2.8, "Configuring RSS Reader for Dashboard"

21.2.1 Import FOIA Archive Error Message

Importing the Freedom of Information Act (FOIA) archive from the Setup Checklist page may display a spurious error message stating Archiver is already running, please try again later.

This error may be safely ignored. It is generated because the click to initiate the archive is registered twice. Ignore the warning, wait fifteen minutes and then see if the alert notification for that task is removed. The import of the archive can also be confirmed by opening the Archiver and verifying that the FOIAPrivacyAct archive is present.

21.2.2 Restart Required: Performance Monitoring and Reports

After performance monitoring is selected and enabled, the Content Server must be restarted in order for monitoring to commence. Note that a restart is also required after configuration of the software in order for all report options to appear on the appropriate menus.

21.2.3 Audit Trail Sorting Results and Database Fulltext Search

When sorting the audit trail using Oracle DB, the output depends on the type of sort being performed.

When sorting with Database Fulltext Search, sorting is case-sensitive, meaning that upper case items will always appear first in a list. When sorting with Oracle Text Search, a case-insensitive search is performed.

21.2.4 Prefix Size Limitation When Using Offsite Storage

If offsite storage functionality is enabled on the system, the total size allowed for the content ID for a physical item is 11 characters. When setting up offsite storage, verify if automatic assignment of IDs is enabled and if so, make sure the content prefix is set to 5 characters or less.

21.2.5 Enabling Email Metadata Component

If the EmailMetadata component is installed for use with WebCenter Content, a configuration variable must be set in order for the user interface to be made available in Records.

Set the ShowEmailMetadataMenu variable to TRUE in the emailmetadata_environment.cfg file in the /components/EmailMetadata directory.

Restart Content Server after setting the variable then refresh or reload the browser. Options become available to map email fields to metadata fields. To use those options, choose Administration then Configure Email Metadata from the Main menu.

21.2.6 Relative Web Root Must Be Changed

When upgrading from the 10g version, the HttpRelativeWebRoot configuration parameter must be changed in the config.cfg file to the following:

HttpRelativeWebRoot=/urm/

It is critical to change the parameter exactly as shown.

21.2.7 Configuring 10g Adapters for Version 11g

A connection address must be changed to enable 10g adapters to work with version 11g.

Previous connection strings were similar to the following example:

http://myhost.mycompany.com:myport/URMinstance/idcplg

The new connection string should be similar to the following example:

http://myhost.mycompany.com:myport/_dav/URMinstance/idcplg

The addition of the _dav string is all that changes.

21.2.8 Configuring RSS Reader for Dashboard

The following configuration variables should be set in the config.cfg file to configure the RSS Reader in the Dashboard.

If the Content Server is used behind a proxy server, the proxy address and port number must be set:

RssProxyServerAutoDetected= content server network's proxy address

You must also configure the proxy port for the content server network:

RssProxyPortAutoDetected=content server network's proxy port

21.3 Documentation Errata

This section describes changes in the documentation. It contains the following sections:

- Section 21.3.1, "Menu Name Changes Not Reflected in Documentation"

- Section 21.3.2, "Physical Content Management Services Not Documented"

- Section 21.3.3, "Additional FTP Option for Offsite Storage"

21.3.1 Menu Name Changes Not Reflected in Documentation

The External Performance Monitoring menu listed in documentation should be changed to Performance Monitoring. This is accessed by choosing Records then Audit then Performance Monitoring from the Top menu.

21.3.2 Physical Content Management Services Not Documented

The following services were omitted from the PCM services documented in the Oracle WebCenter Content Services Reference Guide:

- GET_RELATED_CONTENT: retrieves a page used to show Related Links for the specified content. The following are additional required service parameters:

- dSource: source being used for the search (for example, "Physical").

- dID: the unique identifier of the external item.

- dLinkTypeID: the unique identifier for the related content type link.

- GET_EXTERNAL_ITEM_SEARCH_RESULTS: retrieves a page used to search physical items. The following are additional required service parameters:

- dSource: source being used for the search (for example, "Physical").

- QueryText: the text used for the search.

- ErmSearchTable: the source table name. This should be EXTERNAL_SOURCE for a Physical source.

- SearchEngineName: the search engine to use. Default is DATABASE.

- SearchQueryFormat: the search query format to use. Default is UNIVERSAL.

21.3.3 Additional FTP Option for Offsite Storage

The option to use sftp is now available (in addition to other options) as the FTP protocol when creating Offsite Storage. This was omitted from the documentation.

Part VII

Oracle WebCenter Sites

Part VII contains the following chapters:

- Chapter 22, "Oracle WebCenter Sites"

- Chapter 23, "Oracle WebCenter Sites: Community-Gadgets"

22 Oracle WebCenter Sites

This chapter describes issues associated with Oracle WebCenter Sites. It includes the following topics:

- Section 22.1, "What's New in This Release"

- Section 22.2, "Deprecated Functionality"

- Section 22.3, "Limitations"

- Section 22.4, "General Issues and Workarounds"

22.1 What's New in This Release

WebCenter Sites 11.1.1.8.0 introduces new features focused on ease-of-use for marketing personnel and includes integration with other Oracle products that are part of the digital marketing ecosystem. The new features are:

- Extended use of WebCenter Sites to support mobile websites. See Section 22.1.1, "Support for Mobile-Optimized Websites" for more information.

- Updated content targeting (Engage interface) to make it easier to target content for the website. Targeting is further enabled by a new integration API for Oracle Real-Time Decisions, which supports automated recommendation of content to website visitors. See Section 22.1.2, "Updates to Content Targeting (Engage Component)" for more information.

- Creation and management of vanity URLs for any asset by marketing users. See Section 22.1.3, "Marketing-Friendly URL Management (Vanity URLs)" for more information.

- Integration framework that supports incorporation of assets hosted by third-party systems (such as hosted video platforms) and leverages content from Oracle WebCenter Content. See Section 22.1.4, "New Integrations" for more information.

- Sample site updates. See Section 22.1.5, "AviSports Sample Site Updates" for more information.

- Platform updates. See Section 22.1.6, "Platform Updates" for more information.

- Updates to the Oracle WebCenter Sites Community and Gadgets applications to simplify installation, enable integration with the Contributor interface, and support Oracle Access Manager Social integration. For complete information about Community-Gadgets, see Chapter 23, "Oracle WebCenter Sites: Community-Gadgets."

22.1.1 Support for Mobile-Optimized Websites

Many new capabilities extend WebCenter Sites for use in building mobile-optimized websites:

- Detection and identification of mobile devices making requests.

- Device group management, which includes definition of groups with similar characteristics (such as screen size, tablet devices, non-touch devices) to aid with mobile site management.

- Site plan updates that allow creation of multiple site plans to support delivery of different site navigations to mobile devices.

- Drag-and-drop assembly of mobile pages.

- Preview of websites for different mobile devices.

- In-context editing of mobile pages.

- Ability to run variations of the website using the same URLs (for example, one website for desktops, one for tablets, and one for smartphones, as opposed to creating a separate 'm.' variation of the site).

- Ability to manage mobile templates from WebCenter Sites: Developer Tools.

22.1.2 Updates to Content Targeting (Engage Component)

The following new features are included for content targeting:

- Content Tagging and Content Queries: In the Contributor interface, tags consisting of single words or short phrases can be attached to content. These tags can be placed across different assets types. Content queries can then be written using the tags and other metadata for use in search and in targeted recommendations.

- New Segment and Recommendation Interface: The Engage Segment and Recommendation interface has been enhanced with an entirely new interface for specifying filtering criteria and allowing for more intuitive creation of site visitor segments. Recommendations can also now be created by use of drag-and-drop functionality.

- Preview by Segment: After the creation of segments and recommendations within the Engage interface, the website can be previewed in the context of different segments.

- REST API Updates: The WebCenter Sites REST API has been updated to include APIs to access recommendations.

22.1.3 Marketing-Friendly URL Management (Vanity URLs)

URLs to any asset in WebCenter Sites can now be easily created and managed. Content authors and marketers can do the following:

- Create short, human readable, easy-to-control URLs that are SEO friendly for any web content. These can be either pattern-based for similar content or contributor defined. URLs could point to any host name, desktop version of the site or a mobile device, specific template and wrapper.

- Control redirection with specific HTTP status.

- Auto-generate URLs according to user-defined patterns.

Note:

A utility is shipped in the \misc folder of the WebCenter Sites distribution to allow you to apply these changes to existing assets.

- Generate reports on all URLs managed in the system. Administrators can run queries against these URLs and manage URL cache from System Tools for bulk URL management.

22.1.4 New Integrations

WebCenter Sites includes the following new integrations and features to incorporate assets and capabilities from other products in the digital marketing ecosystem:

- Proxy Assets Framework: New APIs are included that allow for access to external content from the Contributor interface. External content can therefore be referenced from WebCenter Sites without duplicating or copying the content into WebCenter Sites. Contributors can access that content by using content trees, preview, and search, and then drag and drop the content into slots. A reference integration with YouTube is included to demonstrate access to video content inside the Contributor interface.

- WebCenter Content Integration: Content items stored in WebCenter Content can be migrated to WebCenter Sites according to a configured attribute mapping. A simple Sync to Sites check box can be selected in WebCenter Content to select which content to copy and to keep it synchronized with WebCenter Sites when the connector runs. Administration tools are included in WebCenter Sites to configure the connector, manage the connector configuration, and monitor the synchronization process.

- Real-Time Decisions (RTD) Integration: Users can now automate and optimize targeting by combining WebCenter Sites managed segments with the RTD-automated predictive content recommendations engine. This release includes an API to invoke Real-Time Decisions from WebCenter Sites to get recommendations.

22.1.5 AviSports Sample Site Updates

The avisports demonstration website has been updated to include examples of targeting, mobile websites, and workflow.

22.1.6 Platform Updates

Platform updates include support for Oracle HTTP Server (OHS), updated browser support, an update to the CKEditor version (we are now shipping version 3.6.6.1), and a new operating system and application server support for Community-Gadgets. Refer to the Oracle WebCenter Sites Certification Matrix for more information.

22.2 Deprecated Functionality

- The following functionality is deprecated, starting with the 11.1.1.6.0 release:

- Mirror publishing. Use RealTime publishing, instead.

- SOAP-based web services. Use the public REST API.

- Page Debugger. Use IDE integration for JSP debug capabilities. DebugServlet is not deployed.

- The following functionality is deprecated, starting with the 11.1.1.8.0 release:

- Static Publishing

- Sites Desktop

- Sites DocLink

22.3 Limitations

- Section 22.3.1, "Asset Type Name Restrictions"

- Section 22.3.2, "API"

- Section 22.3.3, "Browser Support"

- Section 22.3.4, "BulkLoader and BulkApprover"

- Section 22.3.5, "CatalogManager"

- Section 22.3.6, "CatalogMover"

- Section 22.3.7, "Collection"

- Section 22.3.8, "Content Tags"

- Section 22.3.9, "Contributor Interface"

- Section 22.3.10, "Developer Tools"

- Section 22.3.11, "Database"

- Section 22.3.12, "Installing WebCenter Sites"

- Section 22.3.13, "Localization"

- Section 22.3.14, "OAM Integration"

- Section 22.3.15, "Page Cache: inCache"

- Section 22.3.16, "Publishing"

- Section 22.3.17, "REST API"

- Section 22.3.18, "Satellite Server"

- Section 22.3.19, "Search"

- Section 22.3.20, "Sites Explorer"

- Section 22.3.21, "Site Capture"

- Section 22.3.22, "Site Management"

- Section 22.3.23, "Sites DocLink (Deprecated)"

- Section 22.3.24, "Sites Desktop (Deprecated)"

- Section 22.3.25, "Tags"

- Section 22.3.26, "Template, Site Entry, and CS-Element"

- Section 22.3.27, "Vanity URL"

- Section 22.3.28, "WebCenter Content Integration"

22.3.1 Asset Type Name Restrictions

- All administrative database tables created by WebCenter Sites are prefixed with FW_ (the tables were added after the 7.5 release of FatWire Content Server). Asset types should not be created with a prefix of FW_.

- The following tables display the asset type names used by WebCenter Sites:
Table 22-1 lists asset types that are created by default:

Table 22-1 Default Asset Types

Default Asset Type

Default Asset Type

Default Asset Type

AdvCols

AttrTypes

Collection

Content Query

CSElement

Device

Device Group

Dimension

DimensionSet

FW_Application

FW_View

HFields

HistoryVals

Page

PageAttribute

PageDefinition

PageFilter

Promotions

Query

ScalarVals

Segments

SiteEntry

Site Plan

Slots

Template

WebRoot

--

Table 22-2 lists asset types that are installed by the avisports sample site:

Table 22-2 Asset Types in the Avisports Sample Site

Avisports Asset Types

Avisports Asset Types

Avisports Asset Types

ArticleCategory

AVIArticle

AVIImage

ContentAttribute

ContentDef

ContentFilter

ContentParentDef

ImageCategory

YouTube

Table 22-3 lists asset types that are installed by the FirstSite II sample site:

Table 22-3 Asset Types in the FirstSite II Sample Site

FirstSite II Asset Types

FirstSite II Asset Types

FirstSite II Asset Types

Content_A

Content_C

Content_CD

Content_F

Content_PD

Document_A

Document_C

Document_CD

Document_F

Document_PD

FSIIVisitor

FSIIVisitorAttr

FSIIVisitorDef

FSIIVisitorParent

FSIIVisitorPDef

Media_A

Media_C

Media_CD

Media_F

Media_P

Media_PD

Product_A

Product_C

Product_CD

Product_F

Product_P

Product_PD

StyleSheet

--

--

Table 22-4 lists names (in alphabetical order) that are reserved for use by WebCenter Sites and must not be assigned to custom asset types:

Table 22-4 Restricted Names for Asset Types

Restricted Names

Restricted Names

Restricted Names

Restricted Names

ActiveList

AdvCols

AdvCols_Dim

AdvCols_DimP

AdvCols_Extension

AdvCols_ManRec

AdvCols_Publish

AdvCols_SSpec

AdvCols_Types

ApprovalQueue

ApprovedAssetDeps

ApprovedAssets

AssetDefaultTemplate

AssetEditPane

AssetExportData

AssetIndexSourceConfig

AssetListener_reg

AssetPublication

AssetPublishList

AssetQueues

AssetRelationTree

AssetStubElementCatalog

AssetSubtypes

AssetType

Assignment

AssocNamed

AssocNamed_Subtypes

CARTSET

Category

CCFunction

CCRoles

CheckOutInfo

Collection

Collection_Dim

Collection_DimP

Comparators

ComplexAssets

CSElement

CSElement_Arg

CSElement_ArgVals

CSElement_CArgs

CSElement_Composition

CSElement_Dim

CSElement_DimP

CSElement_Map

CSElement_Publish

CSEvents

DeliveryType

Desktop

Dimension

Dimension_Dim

Dimension_DimP

DimensionSet

DimensionSet_Dim

DimensionSet_DimP

DimensionSet_EDim

DistributionList

Dtproperties

ElementCatalog

EmbeddedReference

Externalclients

Extension

Externalclientsconfig

Filters

FlexAssetDef_reg

FlexAssetTypes

FlexFilterTypes

FlexGroupTypes

FlexGrpTmplTypes

FlexTmplTypes

FunctionPrivs

FW_CSGroups

FW_CSUserGroups

FW_SecurityConfig

FW_UIConfiguration

Global_Q

GroupParticipants

HFields

HFields_Dim

HFields_DimP

HFields_Extension

HFields_Publish

HistoryVals

HistoryVals_Dim

HistoryVals_DimP

Include

IndexSourceMetaDataConfig

Link

Link_Dim

Link_DimP

Linkset

Linkset_Dim

Linkset_DimP

Locale

LocaleMap

LocaleTree

MenuArgs

MenuLegalArgs

MimeType

MungoBlobs

ObjectPrivs

ObjectPublish

ObjectRegistry

Page

Page_Dim

Page_DimP

Previewgen

Promotions

Promotions_Dim

Promotions_DimP

Promotions_Extension

Promotions_Goals

Promotions_ManRec

Promotions_Publish

PubContext

PubKeyTable

Publication

Publication_Replicate

PublicationTree

Publish

PublishedAssets

PubMessage

PubSession

PubTarget

PubTarget_Distribution

PubTarget_Satellites

PubTarget_Sites

Query

Query_Dim

Query_DimP

Rank

Remove

Replicate

Replicate_Assets

Replicate_AssetTypes

RTInfo

RuleMap

RuleSetDef

SaveSearch

SaveSearch_Roles

SaveSearch_Sites

ScalarVals

ScalarVals_Dim

ScalarVals_DimP

ScalarVals_Extension

ScalarVals_Publish

Scratch

SearchEngineMetaDataConfig

Segments

Segments_Dim

Segments_DimP

Segments_Extension

Segments_Publish

SiteCatalog

SiteEntry

SiteEntry_Dim

SiteEntry_DimP

SiteEntry_Publish

SitePlanTree

Source

StartMenu

StartMenu_Roles

StartMenu_SChoices

StartMenu_Sites

StartParticipantChoice

StartProcessChoice

StatusCode

SystemACL

SystemEvents

SystemIdGenerator

SystemInfo

SystemItemCache

SystemLocalAlias

SystemLocaleString

SystemPageCache

SystemRemoteAlias

SystemSatellite

SystemSeedAccess

SystemSQL

SystemTransforms

SystemUserAttr

SystemUsers

Tab

TempBlobs

Template

Template_Arg

Template_ArgVals

Template_CArgs

Template_Composition

Template_Dim

Template_DimP

Template_Map

Template_Publish

Template_Subtypes

Template_Thumb

Template_TName

TempObjects

TNames

TreeTabs

TreeTabs_Items

TreeTabs_Roles

TreeTabs_Sect

TreeTabs_Sect_Roles

TreeTabs_Sect_Sites

TreeTabs_Sites

Type

UITag

UITagItem

UIUserLoggedInDetails

UnassignedObjects

UserPublication

VMACCESSKEY

VMACCESSMETHOD

VMATTRIBUTECATEGORY

VMHISTORYATTRIBUTEDEF

VMHISTORYATTRIBUTEFIELD

VMHISTORY

ATTRIBUTEFIELDDEF

VMSCALARATTRIBUTEDEF

VMVISITOR

VMVISITORSCALARBLOB

VMVISITORALIAS

VMVISITORSCALARVALUE

Any name that starts with VMz

Workflow

Workflow_ARols

Workflow_Assets

Workflow_DlgA

Workflow_Roles

Workflow_Sites

Workflow_TActs

WorkflowAsgAction

WorkflowAsgsActions

WorkflowConditions

WorkflowDlgActions

WorkflowDlkActions

WorkflowGroups

WorkflowGroups_Dlock

WorkflowGroups_DRoles

WorkflowGroups_ERoles

WorkflowGroups_Sites

WorkflowGrp Actions

WorkflowObjects

WorkflowObjsAction

WorkflowParticipants

WorkflowProActions

WorkflowRoutes

WorkflowRoutes_Comp

WorkflowRoutes_Cond

WorkflowRoutes_Dead

WorkflowStatusCode

WorkflowStatusCode_TActs

WorkflowStpActions

WorkflowSubject

--

--

--

- For a given database, the name of a flex asset type must have ten characters less than the maximum number of characters that are allowed for database table names.

- For a given database, the name of a basic asset type must have five characters less than the maximum number of characters that are allowed for database table names.

- Attributes "Start Date" and "End Date" are reserved, as WebCenter Sites uses them for out-of-the-box asset types. They should not be used in user-created AssetMaker assets.

22.3.2 API

- Dynamic loading of new DataSource using the loadproperty tag is not supported.

- When the Asset API is used in a standalone application and called from the main method, it does not automatically terminate after the Asset API call is complete (unlike other Java applications). The reason is that Asset API behaves like another cluster member of WebCenter Sites and boots up all the events in the background. To terminate, code should call System.exit(0)

22.3.3 Browser Support

- If Apache Web Server is not configured to use HTTP 1.1, pages will be cached by Internet Explorer.

- In Internet Explorer, the Tools > Internet Options > Settings > Every Visit to the page must be set to true.

- For information about browser support for Community and Gadgets interfaces, see Section 23.2.1, "Browser Support" in Chapter 23, "Oracle WebCenter Sites: Community-Gadgets."

22.3.4 BulkLoader and BulkApprover

- Without validation, the utility ignores versioning of content. With validation, if the content type is under versioning, it will not update the content.

- Page cache is not flushed by BulkLoader. Because page cache is persistent, the cache should be cleared prior to running BulkApprover.

- Using BulkApprover requires running WebCenter Sites, as it is implemented via WebCenter Sites tags.

- Flex filters are not fired (for example, FieldCopier).

- BulkLoader does not support BLOBs. For this, you should use XMLPost.

- Start and End date cannot be specified nor configured for bulk transferred assets using BulkLoader.

- BulkLoader should not be executed while WebCenter Sites is running.

- When assets are added using BulkLoader, the assets will not be indexed in Lucene. You will need to re-index after import.

- Running multiple BulkLoader instances is not recommended unless it is performing the same operations for example, all insert or all update and multiple source tables do not refer to the same asset. Doing so will cause data corruption.

- BulkApprover will not update the PubAsset table to reflect the publish status after running Approve and Mark Publish.

22.3.5 CatalogManager

- If revision tracking is enabled for an object table, and you delete the table using CatalogManager, WebCenter Sites continues to treat the table as revision tracked.

- WebCenter Sites allows the value in the tablename column in the SystemSQL table to be null. However, for ResultSet caching to work properly, this value must be specified.

- You cannot log in to WebCenter Sites if your user name has the "id" value of an existing user in the SystemUsers table. For example, DefaultReader has an ID value of 2. If you create a user with the username "2," that user cannot log in.

22.3.6 CatalogMover

CatalogMover does not export from columns that hold BLOBS. For example, a table is created with a column using the data type specified by the property cc.blob. An image is uploaded to the table. When CatalogMover exports the row, the image is not written to the export data.

22.3.7 Collection

Modifying the rank of assets in a collection that has been previously approved does not put the collection into the approval queue, even after rebuilding.

22.3.8 Content Tags

Newly added tags appear in search results only after a refresh.

22.3.9 Contributor Interface

- Use of the browser back button is not supported in this release.

- Approval and Delete listing screens shows references based on evaluation of the layout template. If the layout template execution fails for any reason, the assets presented in the tables may not be correct.

- Page Layout allows for multiple levels of nested slots. However, the slot properties are only for the first two levels. The tool allows drag-and-drop to multiple levels.

- Drag-and-drop in the Contributor interface will not work if the page uses an iFrame.

- Clarkii Image Editor is not supported in Web Mode.

- Changing device views in Web Mode will not retain unsaved changes.

- The Contributor interface does not support multi-selection of items in docked search mode.

- Use of Internet Explorer in Compatibility Mode is not supported.

22.3.10 Developer Tools

- Developer Tools export created from Content Server 7.6 patch 2:
Import will not succeed if it contains Page Assets. The recommendation is to upgrade to WebCenter Sites 11gR1 and then re-export by using the Developer Tools Plug-in for this version before the next import.

- Developer Tools does not support assets enabled for revision tracking.

22.3.11 Database

WebCenter Sites 11gR1 uses the length specification for strings to specify the underlying database column sizes in bytes. When specifying the maximum length of a text field, keep in mind that multibyte characters will need more bytes per character.

22.3.12 Installing WebCenter Sites

- When cs.use.short.jsp.names=false (the new default value, which used to be true by default), JSP elements that contain dots (such as www.xyz.com/common/flexLinkButton) will not be deployed properly. They will be deployed without the .jsp extension. As a result, the application server will not be able to run them. To work around this, if you use dots in your JSP element names, set cs.use.short.jsp.names=true.

- If your installation of WebCenter Sites fails, take the following steps before re-executing the installation:

- Drop the database tables.

- Undeploy the .ear/.war file.

- Delete the WebCenter Sites installation folder.

- Restart the application servers and web servers.

- When installing a Web Server in between Remote Satellite Server and WebCenter Sites, you must set the cookie header property http.protocol.single-cookie-header=true in the httpaccess.properties file and place it in the <remote_satellite_server install folder>/WEB-INF/classes folder

- If you enable J2EE security on WebSphere 8.0, you will need to add additional classes to the security policy in the .ear file. Two of these are:

- java.lang.reflect.ReflectPermission.suppressAccessChecks

- java.lang.RuntimePermission.modifyThreadGroup

- For security reasons, we recommend providing only internal access for the following servlets:

- Install

- HelloCS

- CatalogManager

- TreeManager

- CacheServer

- Inventory

- WebCenter Sites is not supported on OHS Webcache with WebLogic domain. Currently this is supported on OHS in standalone mode.

22.3.13 Localization

- Non-ASCII characters should not be used in the following Form Name Fields:

- Site

- Template

- Site Entry

- CS-Element

- Attribute

- Recommendation

- Segment

- Use only alphanumeric characters for the following:

- AssetTypes

- Asset Definitions

- Asset Subtypes

- Legal Arguments

22.3.14 OAM Integration

- Sites Desktop and Sites DocLink are not supported with Oracle Access Manager as they are deprecated, starting with 11.1.1.8.0.

- For information about OAM integration and Community-Gadgets, see Section 23.3.6, "OAM Integration" in Chapter 23, "Oracle WebCenter Sites: Community-Gadgets."

22.3.15 Page Cache: inCache

- Persisting cache to disk clears the Last Access Time and hit count on Remote Satellite Server.

- The recommendation is to initialize inCache by accessing one page of the site from each of the WebCenter Sites cluster members.

22.3.16 Publishing

- Ensure that the maximum number of open file handles for your publishing destination operating system is set to 65000. The source system should be set to at least 32000. These numbers are only a guideline and may need to be adjusted based on the type of data and size of publishing operations.

- Export to Disk: Exported page effectively rendered with wrong template when using SIMPLENAME. Contact technical support for a utility to remove the duplicate pub keys.

- Publishing is not supported from multiple development WebCenter Sites instances to a single delivery WebCenter Sites instance.

22.3.17 REST API

- The INPUTFORM tag support is limited in the Asset API when creating basic asset types via REST. As a result, unsupported INPUTFORM TYPES are interpreted as <INPUTFORM TYPE="TEXT" WIDTH="48" REQUIRED="YES"/>. For users to see proper asset type attributes in WebCenter Sites interfaces, the INPUTFORM tags need to be updated in the asset descriptor file through the database (AssetType table in Sites Explorer).

- Setting BufferingConfig.xml to use multiple threads is not supported

- It is possible to create duplicate fw_uid if you perform a GET operation and use PUT on the resulting bean when using the REST API. In this scenario, a new asset with a different asset id will be created, but it will still have the same fw_uid. The workaround is to clear the fw_uid in the bean before performing the PUT operation.

- When using the REST API, you will see the following message displayed on the server side. The message can be safely ignored:

com.sun.jersey.core.impl.provider.xml.SAXParserContextProvider getInstance
WARNING: JAXP feature XMLConstants.FEATURE_SECURE_PROCESSING cannot be set on a
SAXParserFactory. External general entity processing is disabled but other
potential security related features will not be enabled.
org.xml.sax.SAXNotRecognizedException:
http://javax.xml.XMLConstants/feature/secure-processing

22.3.18 Satellite Server

WebCenter Sites and Satellite Server must be configured to be in the same time zone.

22.3.19 Search

- Lucene fails to index text that comes after dashes, underscores, and other special characters.

- If indexing takes longer than the cs.timeout setting, exceptions will be thrown and indexing may be in an unstable state. The timeout should be adjusted based on the size of the index.

- SQL Server only stores milliseconds up to 3.33 millisecond precision with data type DATETIME.

- WebCenter Sites does not support indexing of legacy Word 95 documents and throws exceptions in the logs.

- Lucene standard analyzer treats words differently if they contain a hyphen (-) For example:
ABC-DEF-HIJ is sometimes indexed as one word and sometimes indexed separately as "ABC" and "DEF-HIJ", when this occurs, searching for "ABC-DEF-HIJ" will not always return the proper results.

- Searching for text within XML or HTML tags is not supported.

22.3.20 Sites Explorer

Sites Explorer fails to start on some Windows 2008 R2 servers.

22.3.21 Site Capture

- Status messages are not shown in the application user interface. Check the crawler.log file for log messages.

- Site Capture session failover is not supported in this release.

22.3.22 Site Management

- Creating a site without a Preview asset assigned results in errors in the log which can be safely ignored
CS.XCELERATE.ASSET][ERROR] error: unable to load asset type information for Variables.previewAssetType, in tag asset.load pagename:OpenMarket/Xcelerate/Admin/SiteFront" and "[CS.XML][ERROR] object.get no object named previewAsset"

- Site names that include a hyphen '-' are not supported if using LDAP.

22.3.23 Sites DocLink (Deprecated)

- If Windows is configured using the "Show All Folders" option, if your session times out and you are using Sites DocLink, the login window will appear when Explorer loads the shortcuts.

- Revision tracking of DocLink assets is not supported in this release.

22.3.24 Sites Desktop (Deprecated)

Revision tracking and workflow are not supported from Sites Desktop in this release.

22.3.25 Tags

- Choice of values entered for variant attribute used in insite:calltemplate must be applicable to all types valid for clegal argument.

- Change of behavior for render:callelement from FatWire Content Server 7.x to WebCenter Sites 11g Release 1:
In earlier versions of WebCenter Sites, <render:callelement scoped="local"> would copy all variables from the calling element to the called element, which was a bug. In 11gR1+, the behavior has been corrected to match the documentation in the Oracle WebCenter Sites Tag Reference and it will now only copy over those variables that are passed to the called element as arguments. To retain the incorrect behavior, you can add -DuserLegacyLocalScoping=true to the JAVA_OPTS of the application server.

22.3.26 Template, Site Entry, and CS-Element

- Wrapper pages with "." in the name will not execute. Templates and Site Entry assets should not have a dot (.) in their names.

- Do not use the tag <throwexception> in the code of a template asset. The <throwexception> tag effectively terminates execution in WebCenter Sites for itself and any nested or parent WebCenter Sites engine. This breaks template execution and streaming of data to the client. In addition, when a user approves a template for export publish, a <throwexception> terminates the execution of the approval page and the user gets no feedback.

- No warning is given regarding the potential for broken pages when templates are deleted. Users should delete templates with care, as they may be used as default templates in other assets. Deletion will result in failure to render those pages.

22.3.27 Vanity URL

Removing a URL pattern does not remove the URLs based on that pattern.

22.3.28 WebCenter Content Integration

When importing assets into WebCenter Sites, the WebCenter Content connector does not check asset permissions and will take action regardless of asset-level restrictions (for example, if the asset is revision tracked). This is an Asset API limitation.

22.4 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topic:

- Section 22.4.1, "API"

- Section 22.4.2, "Admin Interface"

- Section 22.4.3, "Analytics Integration"

- Section 22.4.4, "Approval"

- Section 22.4.5, "AssetCache"

- Section 22.4.6, "Browser Support"

- Section 22.4.7, "Caching: inCache"

- Section 22.4.8, "Caching: Satellite Server"

- Section 22.4.9, "CKEditor"

- Section 22.4.10, "Cluster"

- Section 22.4.11, "Content Query"

- Section 22.4.12, "Contributor Interface"

- Section 22.4.13, "Developer Tools"

- Section 22.4.14, "Engage"

- Section 22.4.15, "Flex Assets"

- Section 22.4.16, "Installation / Upgrade"

- Section 22.4.17, "Mobility"

- Section 22.4.18, "Performance"

- Section 22.4.19, "Proxy Assets"

- Section 22.4.20, "Publish Console"

- Section 22.4.21, "Publishing"

- Section 22.4.22, "REST API"

- Section 22.4.23, "Revision Tracking"

- Section 22.4.24, "Satellite Server"

- Section 22.4.25, "Site Capture"

- Section 22.4.26, "Site Launcher"

- Section 22.4.27, "Site Plan"

- Section 22.4.28, "Sites Desktop (Deprecated)"

- Section 22.4.29, "Sites DocLink (Deprecated)"

- Section 22.4.30, "Sites Explorer"

- Section 22.4.31, "Start Menu"

- Section 22.4.32, "System Tools"

- Section 22.4.33, "Tags"

- Section 22.4.34, "WebLogic Server"

- Section 22.4.35, "WEM Admin"

- Section 22.4.36, "WEM Framework"

- Section 22.4.37, "Workflow"

- Section 22.4.38, "UI Customization"

- Section 22.4.39, "Upgrade"

- Section 22.4.40, "XMLPost"

22.4.1 API

- ics.CommitBatchedCommands() does not return the correct status or set the errno variable properly in every situation.

- JSP processing adds whitespace.

- When using asset:export / asset.export tags on an asset that isn't a page or collection, the output XML doesn't contain info about the unnamed associations.

- The Asset API Tutorial contains example byte d = fileObj.getBinary(); However getBinary() no longer exist. It has been changed to getBinaryStream() which returns an InputStream. Instead of byte d = fileObj.getBinary() , the example should be changed to: byte d = newbyte[fileObj.getBinaryStream().available()];

- The XML tag ASSET.DELETEREVISION, which deletes a specific revision of the asset, fails to execute. The JSP variant asset:deleterevision should be used.

- For case-sensitive databases, setting the case sensitivity to false does not disable the case sensitivity of the search query.

22.4.2 Admin Interface

- In the Admin interface, the tree applet will not reflect changes when Start Menu name is edited.

- Downloading thread dumps from the System Tools is not supported for WebSphere.

- 500 error is thrown if you browse directly to the WebCenter Sites-Cache status page when AssetCache is not started or enabled.

- Pasting text using Ctrl+V into the query box of the Log Viewer triggers the View Logs function. The correct shortcut for log viewer functionality is Ctrl+Shift+V.

- Downloaded log files from System Tools do not include information from cas.log.

- Right-clicking REFRESH does not refresh the page for Thread Info, Sites Info, and DB Info.

- The message "An error has occurred" appears when attempts are made to view logs in Log Viewer, but the logs are empty.

- "No access allowed" messages appear multiple times when permissions are insufficient for viewing table information in DB Info.

- Unable to run the File System test multiple times without changing the type of test to run.

- System Tools, File System Test information is not displayed in graph form in Internet Explorer. To view this graph, use Firefox.

- When creating a new AssetMaker asset type, using the tab key to move through the fields will result in the Browse button disappearing from view. Clicking in the area where the button originally appeared will allow browse to continue.

- Setting the xcelerate.showSiteTree property to false does not turn the applet off in the Admin interface.

- When WebCenter Sites is configured to use hierarchical LDAP, if the user only has access to the Management Site and you log in to the Admin interface, the tree tab loads and shows the tabs, but all the tabs are empty.

22.4.3 Analytics Integration

Assets deleted in the Contributor interface are not reflected in the Analytics data.txt file.

22.4.4 Approval

- Approving a site plan using the right-click in the Contributor interface will not include any slot assets in the approval. Pages with slots will need to be approved separately.

- When a recommendation or promotion is approved, it does not show segment as a dependency.

22.4.5 AssetCache

- When a revision tracked asset is deleted, on the initial inspection of the asset, AssetCache shows this asset with updated time and valid dependency, which is incorrect.

- Uploading a BLOB larger than 5MB will result in an exception, which can be safely ignored:
"Error met serializing / deserializing <Assettype ID> for copying purpose in AssetCache"

- <render:LogDep> could cause un-linked cache. If there is an un-recognized rendermode passed, the system will cache the page and not log the dependencies. This will cause the page to not be flushed in any way since their dependencies are not there.

- A warning message in the log is sometimes seen: "Creating a new instance of CacheManager using the diskStorePath". The message can be safely ignored.

22.4.6 Browser Support

- Selecting Delete from the top menu in the Contributor interface will throw a JavaScript error when Internet Explorer 9 is used. To avoid this issue, delete by using the Delete button.

- The Site Plan tab in the Contributor interface may not display properly on initial login when Internet Explorer 10 is used. Refresh the page to correct this.

- When using Chrome, unable to upload user avatar.

- The Admin interface tree applet fails to load in Chrome when the browser is run on Linux.

- In Internet Explorer 9, the Web Experience Management (WEM) Framework site selector drop-down list is not populated with sites when the user name contains non-ASCII characters.

- In Web Mode, the upload icon does not appear in Internet Explorer 10. Switch to form mode to upload files or images.

- In Internet Explorer 9, the selected date is shown in UTC format in Web Mode.

- The Contributor interface is best viewed at 100% zoom. Changing this to a higher zoom results in unexpected behavior such as:

- All drag-and-drop fields may not appear in Web Mode.

- Additional horizontal and vertical lines appear.

22.4.7 Caching: inCache

Disk store size keeps growing as the cache gets more usage, even if the actual number of items in cache remains the same.

22.4.8 Caching: Satellite Server

- Any blob which is not supposed to be cached by the Satellite Server will be added under <sscachedir>/uncachedblob. This directory can grow if blobs are not being cached on the Satellite Server. The content of this directory can be safely deleted at any time. It can be deleted manually or by using the FlushServer reset call.

Note:

The FlushServer reset call will clear all the cache from the Satellite Server.

- Pages based on a template variant are not cached on Remote Satellite Server on the first request.

22.4.9 CKEditor

- Anchor name is added before the selected text when using Internet Explorer 9.

- Upgraded assets may have an extra <p> <span> added when viewed in Form Mode post upgrade. This can be resolved by changing the attribute to use the updated CKEditor.

- For assets created prior to Content Server 7.5 Patch 1 - If the first piece of data in the FCKEditor window is an embedded link or included asset, you must switch to source view to add additional content prior to the embedded link or included asset. Similarly, if the last asset is an embedded link or included asset, source view must also be used to add additional content immediately following the link or included asset.

- Frame shows "Loading" message if target is set to "not set", "frame" or "Same Window (_self)" while creating the external link in CKEditor.

22.4.10 Cluster

For a WebSphere cluster, user session replication for the management interfaces will not properly failover in all scenarios when one cluster member fails.

22.4.11 Content Query

Content Query throws errors when selecting an assettype which contains a subtype.

22.4.12 Contributor Interface

- If there is a failure due to template compatibility reasons while swapping a slot, the original slot content is cleared. Refresh or cancel the save to revert back to the previously saved state.

- Bookmarks are not appearing in the tree for sites that are imported using Developer Tools. To resolve this, edit and save the bookmark tree tab in Admin.

- When dragging and dropping from the docked search, the avatar window (showing the asset name in blue) tends to hide behind the search.

- Drag-and-drop of pages to the Site Plan Tree is not supported. Doing so may result in the tree node indicator to spin and not return results. Other operations are able to continue during this time except action initiated from the node of the site plan tree that is no longer responding.

- Progress bar is not displayed accurately for large file uploads (>64MB) for Basic Assets.

- Setting bs.security=true results in blobs failing to render in Web Mode or Preview

- Setting bs.security=true results in a failure of the blob to render correctly on create screen, inspect will display properly.

- The select layout template appears behind videos added as part of a proxy asset in the Contributor interface.

- Date picker does not work in Web Mode if the value is empty.

- In Web Mode, the selected layout in the Change Layout option is retained in the browser even when the asset is not saved

- Changes to the presentation of a slot are not copied during an asset copy operation in Web Mode.

22.4.13 Developer Tools

- Importing a Developer Tools export from version 11.1.1.6.0 or 11.1.1.6.1 to 11.1.1.8.0 will fail if the export includes fw_attributeeditor or fw_uiconfiguration assettypes, users should remove these types from the datastore prior to the import.

- Developer Tools import from version 7.6.x will not be successful if the DatePicker attribute editor is included in the datastore, as the calendar is different between this version and 11gR1+. Remove the attribute to import this data.

- When creating templates using the existing element option, if the specified element does not exist, an empty template will be created in WebCenter Sites, but cannot be exported.

- If filename length of exported file exceeds the operating system filename limitation, the file cannot be exported. This is likely to happen if the filename of uploaded blob is too long.

- Deleting a site does not update information about the exported assets. The workaround is to first unshare the assets from the site which you wish to delete, and then delete the site.

- Deleting of non-asset resources should be done manually on each destination. This is currently no sync for deleted non-asset resources.

- User must be cautious of the order in which resources are imported. Consider the situation in which all developers have "A points to B" in their system. Then one developer changes A to point to C and deletes B. If other developers were to sync B before A, the import would fail, since an asset that is being referenced cannot be deleted.

- During import, you may experience some indexing data exceptions. This will affect only the search index and not the actual data import. Re-index the affected asset types after the import, if necessary.

- Resources that contain fw_uids which include slashes or commas cannot be exported.

- The Sync and FW workspace views in Eclipse do not properly display UTF-8 characters on Windows.

- The locale hierarchy information is not preserved for exported hierarchical DimensionSet. The workaround is to manually configure the hierarchal information after import.

- SiteCatalog resources do not contain a dependency on the ElementCatalog resource. These currently need to be exported/imported manually.

- The Developer Tools Eclipse Plug-in auto complete will add double quotes if your application server does not support this. The double quotes must be changed to single quotes manually.

- Import fails to import segment assets when the segment criteria contains history definition with string value.

- When connecting to a remote instance, the project WEB-INF folder points to a non-existent location. As a result, code completion will not work. To work around this issue, map to local jars / tlds when working with remote connections.

- If an ElementCatalog entry is created with the name of an existing ElementCatalog entry, the JSP will be overridden with a new empty JSP.

- In some Linux systems, the WebCenter Sites interface and log sections are not appearing.

- Site Entry creation fails via Developer Tools.

22.4.14 Engage

Setting an asset which is part of recommendation to rating of 100 results in only that asset being returned.

22.4.15 Flex Assets

- If using multiple parents, they should all use the same Parent Select Style.

- Parent asset cannot be deselected when using Select Box attribute editor for an optional parent attribute. The workaround is to use Pick from Tree.

22.4.16 Installation / Upgrade

- Going back or restarting the installation process after entering passwords requires that the passwords be re-entered, or the system defaults will be used.

- During upgrade, the following ERROR may appear in the sites log and can be safely ignored:
[com.fatwire.logging.cs] Exception loading properties from file list futuretense.ini java.lang.Exception: Required key not found: cs.pgCacheTimeout"

- Installation should not be initiated to a path that includes multibyte characters.

- "Exception loading applications assetcom.fatwire.assetapi.common.AssetAccessException: asset type FW_Application cannot be found in Content Server" may appear in sites.log when installing avisports sample site, or when a new site is created. This exception can be safely ignored.

- Occasionally, the midpoint installation tests will fail for WebSphere secondary cluster member. If this occurs, try again. The same issue may occur on login after a restart.

- Download patch 14847089 if installing on WebSphere to avoid the following exception after starting the server during installation:

JPAPUnitInfo  E   CWWJP0015E: An error occurred in the org.eclipse.persistence.jpa.PersistenceProvider persistence
@ provider when it attempted to create the container entity manager factory for the JpsDBDataManagerV3 persistence unit. The following error occurred:
java.lang.ClassNotFoundException:
org.eclipse.persistence.jpa.PersistenceProvider
at java.net.URLClassLoader.findClass(URLClassLoader.java:434)
at
com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:198)
at java.lang.ClassLoader.loadClass(ClassLoader.java:646)

22.4.17 Mobility

- The devices.xml file provides a sample that works best using user-agent identification to identify by device name. Modify this file for greater granularity.

- Entering more than 31 characters in the device name field will result in the name appearing outside the device area in multi-device preview.

22.4.18 Performance

The tree applet in the Admin interface takes 2 to 4 minutes to release memory used when switching sites. This is a JRE limitation.

22.4.19 Proxy Assets

Creating a Content Query that contains proxy assets will show only dots (…) in the search results.

22.4.20 Publish Console

During publishing to a cluster, the progress bars in the publish status screen show progress out of order from the actual steps.

22.4.21 Publishing

- Export to Disk: Changing display template results in multiple assets in pub list. Contact technical support for a utility to resolve this.

- Removing a published child page from the site plan and later only publishing the parent will leave the child page on the destination, but the page will not appear in the site plan.

- Temp files created during publishing remain in the file system after publication.

- Dependent asset relation for promotion is lost after publishing. This also occurs via REST and Developer Tools import / export.

- Error -3100 when publishing BLOBS may occur. This can be safely ignored.

22.4.22 REST API

- When you use an invalid multi-ticket in a REST call to Satellite Server, instead of redirecting to the login screen, it throws the following exception: javax.servlet.ServletException: Failed to parse assertion for multi ticket xxx

- When you use an invalid multi-ticket in a REST call to Satellite Server, it does redirect to the login screen. However, instead of generating a ticket and displaying the requested information, the redirect fails, and an error is shown.

- Initiating a REST call using an invalid ticket or multi-ticket via the browser while you are logged into WebCenter Sites will be successful, as it will use the session ticket.

- Multivalued association is not returned with the ordinal value.

- Deleted groups are not deleted from the Security Configuration. The group can be manually deleted by removing the entries from the FW_CSSecurityConfig table.

- When under load, the following exception may occur when using Buffered Writes. This can be safely ignored, as the data is properly returned:
com.sun.jersey.server.impl.application.WebApplicationImpl onException SEVERE: Internal server error javax.ws.rs.WebApplicationException: javax.xml.bind.MarshalException

- Content-type header must be set to allow delete operations.

- When creating asset types in REST, Plural Form is not reflected/honored in the Admin interface.

- Invoking the Delete method on a non-existent object returns a 200 status code.

- Update is not working for Application object type if Delete permission is not also granted.

- If the first request after a restart of WebCenter Sites is a PUT, the create will fail with a 500 error.

- The Navigation service will return a 500 instead of 200 error if there are no Page assets.

- Although description is a required attribute for a Site, the WebCenter Sites REST service doesn't validate for a Site description during create/edit.

- When roles are deleted via REST, the corresponding entry for Site and Users is not deleted. Use WEM Admin interface to delete a role or manually clean up the UserPublication table to remove the dependencies.

- Access to navigation service requires user to be part of the RESTAdmin Group.

- REST API for asset data sometimes returns an empty string when the attribute data is null.

- REST API calls to Remote Satellite Server through Central Authentication Service (CAS) must be made after acquiring a multi-ticket and using that multi-ticket in each REST call.

22.4.23 Revision Tracking

- Viewing the version of a revision tracked asset where the parent has been deleted will display a blank screen.

- If access to Checkout is denied, clicking on the Checkout button in the Contributor interface will result in no response.

- Deleting an asset that was associated to a revision tracked asset removes all associations on rollback.

22.4.24 Satellite Server

Content-type header is lost when a wrapper page is called using Co-resident Satellite Server. WebCenter Sites logs "Unable to set header (header name) because the header has already been committed".

The workaround is to increase the application server response buffer size.

22.4.25 Site Capture

- Download Archives action may time out if the archive size is large.

- Multiple Jobs and Archives get created if schedules overlap for the same crawler. It is recommended to create only one schedule for each crawler to avoid creation of duplicate jobs and archives.

- In some cases, when the installation is performed on Solaris, if the start URI is not configured correctly, errors will be reported as HTTP instead of network errors. Ensure that the start URI is configured correctly.

22.4.26 Site Launcher

Sites Desktop information in the replicated site does not set the description field for Sites Desktop to enabled in the copied site.

22.4.27 Site Plan

- If a page is moved to a different site plan while another user is editing or viewing the page in the Contributor interface, the multi-device preview may not accurately reflect the correct device group.

- Setting showparentnodes=false will result in related assets of the last node in the tree appearing as children of the root node.

22.4.28 Sites Desktop (Deprecated)

- The following error may appear in the sites.log file when assets are created using Word 2010:
[ERROR] [WebContainer : 6] [docx4j.openpackaging.contenttype.ContentTypeManager] No subclass found for /word/stylesWithEffects.xml.

This error can be safely ignored.

- Locale selected during creating an asset from Sites Desktop does not appear in Sites Desktop before save even though it is saved correctly.

- Unable to upload multiple images to a multivalued attribute.

- Unable to reorder multivalued attributes in Sites Desktop.

22.4.29 Sites DocLink (Deprecated)

- Unable to create translated assets using 'copy' option.

- After the Document Type is changed in WebCenter Sites, refreshing DocLink does not make this change active. The user must log out and log back in for the change to take effect.

- Required fields are not marked as "Required" in the DocLink Edit Configuration screen.

22.4.30 Sites Explorer

Login via Sites Explorer on Windows 2008R2 over https fails to authenticate. It is recommended to use Sites Explorer on Windows XP or Windows 7 if configured using https.

22.4.31 Start Menu

Start menus that contain more than 21 characters are not displayed properly in the search box in the Contributor interface.

22.4.32 System Tools

- ResultSet Summary screen refresh does not always refresh properly. Use the individual screen for each cache for more accurate reporting.

- Setting fatwire.logging.cs.xml logger to DEBUG level will cause the Admin interface to fail to load properly until the server is restarted.

22.4.33 Tags

- The POST tag works incorrectly when USERNAME, PASSWORD or LOGOUT attributes are passed to it. Login and logout requests are sent to the URL being posted to, instead of CatalogManager. One workaround is to perform login before this tag is executed. Alternatively, the FormPoster API can be directly used to perform the post operation.

- SEARCHSTATE.ADDRICHTEXTCONSTRAINT fails when the ResultSet returns more than 1000 rows.

- Unable to delete page and basic assets using asset:void tag if a valid pubid is not present in the session. The workaround is to set the pubid in the session to "0", then remove it again after voiding.

22.4.34 WebLogic Server

Exception is thrown when WebLogic Server starts. This can be safely ignored:

java.net.ConnectException: Tried all: '1' addresses , but could not connect over HTTP to server

22.4.35 WEM Admin

- Case sensitivity for sorting is inconsistent.

- Site names with special characters or symbols are not getting deleted. Delete the site by using the Admin interface.

- Deleting a site does not clean up the Apps assigned to the site. To resolve this, manually remove the site entries from the urlaccessroles column in the FW_Applications table, using Sites Explorer.

- Cannot assign roles to a user who has stale group membership data. The workaround for this is to edit and save the user in the WEM Admin interface.

22.4.36 WEM Framework

- The SiteAdmin role is not added to the user for WEM Admin by default when the user has been assigned the SiteAdmin role in another site. The user should be manually assigned access to the WEM Admin application, if required.

- If the last accessed application or asset no longer exists, subsequent login to WebCenter Sites will result in a blank screen.

- If an incorrect old password is entered when changing the password in the WEM Admin interface, selecting Save and Close will fail to display a warning that the old password is incorrect. The password will not be changed in this case.

22.4.37 Workflow

- Shared roles need to be reselected if a workflow report is edited after the initial save.

- The DashUser role is listed in the list of Workflow Participants if the user was part of the group before upgrade. This user role should be removed and replaced with SitesUser.

22.4.38 UI Customization

If the left navigation and right navigation panels in LayoutConfig are swapped, the Contributor interface throws errors and does not load.

22.4.39 Upgrade

- The upgrade utility will not apply indexes to the tables listed below if the assets were created prior to version 7.6 Patch 2 and a previous upgrade was done to an earlier version of WebCenter Sites 11gR1. To take advantage of performance enhancements, apply indexes to these tables manually:

- AssetType_Dim

- AssetType_DimP

- AssetType_Amap

- AssetType_Group

- After upgrade, the Content Query start menu is not present even though the asset type is enabled for sites. The start menu must be created manually.

- The timezone utility does not update previously exported data that contains a user-defined attribute of type date. The serialized data needs to be manually updated to UTC before import.

- For information about upgrading the Community Blogs module, see Section 23.4, "Upgrading the Community Blogs Module" in Chapter 23, "Oracle WebCenter Sites: Community-Gadgets."

22.4.40 XMLPost

- XML namespaces are stripped from XML elements during evaluation.

- XMLPost created as recursive dependency on the asset when modifying a parent asset.

23 Oracle WebCenter Sites: Community-Gadgets

This chapter describes issues associated with the Oracle WebCenter Sites: Community-Gadgets web application and its individual WEM applications, Community and Gadgets. This chapter also contains information about upgrading the Oracle WebCenter Sites: Community Blogs module.

This chapter includes the following topics:

- Section 23.1, "Community-Gadgets Enhancements"

- Section 23.2, "Limitations"

- Section 23.3, "General Issues and Workarounds"

- Section 23.4, "Upgrading the Community Blogs Module"

23.1 Community-Gadgets Enhancements

WebCenter Sites: Community-Gadgets contains the following usability and platform enhancements:

- Contributor Interface Integration: Widgets and gadgets can be accessed from within the WebCenter Sites Contributor interface. Users can now easily search for social components (such as polls, comment widgets, and gadgets) and drag and drop them directly onto a page.

- OAM Social Integration: OAM Social integration enables support to multiple social networks to authenticate site visitors and authenticate moderators using OAM on the management side.

- Improved Installation: Community and Gadgets servers are now bundled into a single installer, making the installation process easy.

- Enhancements to Community Widgets: Users can filter out and moderate comments and reviews pertaining to any category. Visitors can be authenticated through Google accounts. Moderators can accept or disallow posting of comments on any page at the click of a button.

- Enhancements for Gadgets: The Gadgets Admin interface is localized and includes localized gadgets support. In addition, multiple gadgets can be rendered along with Community widgets on the same web page. Other enhancements include a pluggable login bar for Gadgets and maintenance of the user session across Gadgets and the Dashboard.

- Updated platform support for Community and Gadgets, including a new operating system and application server. Refer to the Oracle WebCenter Sites Certification Matrix for more information Refer to the Oracle WebCenter Sites Certification Matrix for more information.

23.2 Limitations

This section includes the following topics:

- Section 23.2.1, "Browser Support"

- Section 23.2.2, "General Limitations"

- Section 23.2.3, "Community Application"

- Section 23.2.4, "Gadgets Application"

- Section 23.2.5, "Installing Community-Gadgets"

- Section 23.2.6, "Oracle Access Manager Integration"

23.2.1 Browser Support

For Community and Gadgets interfaces, Internet Explorer users must set the browser to receive third-party cookies.

23.2.2 General Limitations

- Widgets are certified with valid HTML host pages only (tested on XHTML 1.0 of Strict doctype).

- Widgets are certified with host page URLs that contain valid query strings only (see http://en.wikipedia.org/wiki/Query_string).

- The CSS of the host page may potentially impact the look-and-feel of widgets. It may be necessary to apply custom CSS to widgets or even adjust your host page CSS.

- Community and Gadgets Admin interfaces are not supported in standalone mode (view) and are meant to be accessed only via the WebCenter Sites WEM Framework.

- Ensure Lucene indexing is enabled for all Community and Gadgets asset types.

- JavaScript must be turned on for all admin pages and end site widgets.

- Visitor authentication is not supported against both the WebCenter Sites/WEM database and LDAP at the same time.

- Support for the latest available OpenSocial API is not implemented; the OpenSocial Gadget Container shipped with Community-Gadgets continues to support all features that were supported in prior releases.

- If the diskstore is enabled, Community-Gadgets may freeze for several minutes at shutdown until the populated cache is flushed to disk. Any interruption during this process can corrupt the cache.

23.2.3 Community Application

Changes made to the Restricted Words list will have no effect on existing posts.

23.2.4 Gadgets Application

- Gadget validation is only for the XML descriptor. It will not check to guarantee successful rendering of the gadget on the Dashboard. This should be verified prior to deployment.

- Pagination settings are not preserved after registering new gadgets.

- OAuth Gadgets are no longer supported.

23.2.5 Installing Community-Gadgets

- In case of deploying both the management and production Community-Gadgets web applications on the same machine, we recommend changing the default context root for one of the Community-Gadgets web applications (for example, the management web application using context cgm, or the production web application using context cgp).

Note:

Single-server installation is supported only for development purposes.

- When deploying Visitor CAS on a machine where another CAS application is already deployed (for example, Sites CAS), it is recommended to change the default Visitor CAS context root (for example, from cas to vcas).

- Visitor CAS should be installed on the same domain as the live site.

- The WebCenter Sites URL provided during Community-Gadgets installation should be the same as used to access WebCenter Sites. Otherwise, there will be failure in loading the Community Admin interface and Gadgets Admin interface. For example, if you specify the WebCenter Sites host name in the Community-Gadgets installer, accessing WebCenter Sites via the IP address will result in failure to load the Community Admin interface and Gadgets Admin interface.

23.2.6 Oracle Access Manager Integration

The following exception may be seen in the Oracle Access Manager (OAM) Console during login to Community and Gadgets WEM applications and can be safely ignored:

<Error> <oracle.oam.engine.authz> <BEA-000000><Initialization of Module TokenIssuer failed. oracle.security.am.engines.tpe.TokenProcessingException: OAMSSA-16002: Initialization of Module TokenIssuer failed.

23.3 General Issues and Workarounds

This section includes the following topics:

- Section 23.2.1, "Browser Support"

- Section 23.3.2, "Community Application"

- Section 23.3.3, "Gadgets Application"

- Section 23.3.4, "Janrain Integration"

- Section 23.3.5, "Localization"

- Section 23.3.6, "OAM Integration"

- Section 23.3.7, "Performance"

23.3.1 Browser Support

Social Login/Sharing of posted Comments is not working in Internet Explorer 8.

23.3.2 Community Application

This section includes the following topics:

- Section 23.3.2.1, "General Issues and Workarounds"

- Section 23.3.2.2, "Comments"

- Section 23.3.2.3, "Reviews"

23.3.2.1 General Issues and Workarounds

- Only 500 users are displayed in the "Available" box of the Add Visitors to the Blacklist and Whitelist screens.

- Janrain JavaScript is loaded by the deployed widget regardless of enabling Janrain support.

- If the Community application is integrated with LDAP and the LDAP server is not available, users will receive an "invalid credential" message instead of a "server down" indication when trying to log in to the site.

- Setting Permalink to the second page of comments or reviews will continue to show the first page when the display order setting is "Newest at the top."

- Unable to select Current/Today's date for poll closure in the calendar window when creating a poll.

23.3.2.2 Comments

- Uploading a file with duplicate categories will result in the category appearing twice in the "Reviews by Topic" page.

- Visitor display names are not updated in the Community interface for comments posted prior to the name change.

- Sorting on the date/time field in the Comments by Topic page may not show the correct ordering if a comment has been deleted as the "Last Commented on" field is not shown once a comment is deleted.

- Blank 'Category title' is displayed if Category Title is given between '< >' while uploading Categories.

- Under periods of high load, the count on the Comments By Topic page may not match the filter count.

23.3.2.3 Reviews

- Uploading a file with duplicate categories will result in the category appearing twice in the "Reviews by Topic" page.

- Deploying the reviews deployment tag with Rating Only and Reviewing Enabled set to NO will result in a blank page being rendered.

- The order of categories in the Category drop-down list on the Reviews Deployment page will not match the order in which they were entered in the uploaded category file.

- An alert message is not displayed when a guest user attempts to review an article for the second time when the admin setting is to only review once on a page.

- Deploying the default Thumbs Up or Thumbs Down rating widget using a ResourceID that is already in use will result in the posted ratings not being updated on the site. Users should ensure that duplicate ResourceIDs are not being assigned.

- The count for Pending, Approved and Inappropriate reviews is not updated in the Filter Panel of Reviews by Topic Page until a manual refresh is initiated.

- When Max Number of Reviews is reached, Community-Gadgets still allows for additional reviews to be posted.

23.3.3 Gadgets Application

- When a large number of gadgets exist on the dashboard, it may require multiple movements to render a gadget in the desired location.

- Drag-and-drop is not capable of scrolling on large dashboards.

- When six or more category filters exist, the pagination buttons overlap the filter names on the Dashboard.

23.3.4 Janrain Integration

Unable to log in using MySpace or WordPress account credentials when integrated with Janrain.

23.3.5 Localization

- Registering as an anonymous user in a localized instance of Community-Gadgets will result in the user being created as a new user with the localized user name.

- The following pages do not appear correctly in German locale:

- Reply as Admin

- Comments by User

- Create Poll

- Edit Poll

23.3.6 OAM Integration

Unable to log in using Twitter when Community-Gadgets is integrated with Oracle Access Manager Mobile Social.

23.3.7 Performance

Under periods of high load, the count on the Comments By Topic page may not match the filter count.

23.4 Upgrading the Community Blogs Module

General information about the Community Blogs upgrade:

- The upgrade process updates all default templates to new versions. Any customizations done to these should be backed up prior to running the installer.

- During the upgrade process, two additional properties cos.protocol and cos.contextroot are added to the futuretense_xcel.ini file.

Part VIII

Oracle SOA Suite and Business Process Management Suite

Part VIII contains the following chapters:

- Chapter 24, "Oracle SOA Suite, Oracle BPM Suite, and Common Functionality"

- Chapter 14, "Web Services Development, Security, and Administration"

24 Oracle SOA Suite, Oracle BPM Suite, and Common Functionality

To view the latest known issues associated with Oracle SOA Suite, BPM Suite, and related SOA technologies, go to Oracle Technology Network (OTN) at http://www.oracle.com/technetwork/middleware/docs/soa-aiafp-knownissuesindex-364630.html. These known issues documents include the following products:

- Oracle Adapter for Oracle Applications (Oracle E-Business Suite Adapter)

- Oracle AIA Foundation Pack

- Oracle Application Adapters for Oracle WebLogic Server

- Oracle Application Server Legacy Adapters

- Oracle B2B

- Oracle BPEL Process Manager

- Oracle Business Activity Monitoring

- Oracle Business Process Management

- Oracle Business Rules

- Oracle Complex Event Processing

- Oracle Enterprise Repository

- Oracle Human Workflow

- Oracle Mediator

- Oracle Service Bus

- Oracle SOA Suite and Oracle BPM Suite Common Functionality

- Oracle Technology Adapters

Part IX

Communication Services

Part IX contains the following chapters:

- Chapter 25, "Oracle User Messaging Service"

- Chapter 26, "Oracle WebLogic Communication Services"

25 Oracle User Messaging Service

This chapter describes issues associated with Oracle User Messaging Service. It includes the following topics:

- Section 25.1, "General Issues and Workarounds"

- Section 25.2, "Configuration Issues and Workarounds"

25.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topics:

- Section 25.1.1, "UMS Schema Purge Script Now Available"

- Section 25.1.2, "Permission Grants for Upgraded Domains"

- Section 25.1.3, "XML File Handle Left Open after Upload Fails"

- Section 25.1.4, "Messages Metrics Rendered as Unavailable in the Performance Page for User Messaging Server"

- Section 25.1.5, "User Messaging Service URLs Unavailable After Restart"

- Section 25.1.6, "User Preferences User Interface Renders Improperly"

- Section 25.1.7, "UMS Cluster Failover May Lose Messages"

25.1.1 UMS Schema Purge Script Now Available

A UMS schema purge script is available for your download and use. You can access the script and instructions for its use by contacting Oracle Support.

25.1.2 Permission Grants for Upgraded Domains

In order for Oracle User Messaging Service to run as a specific user, a code-based permission grant is required. This grant is pre-seeded in WebLogic domains that are created after the Fusion Middleware 11gR1 Patch Set 2 upgrade.

If you created a WebLogic domain prior to the Patch Set 2 upgrade, you must manually add this grant by running the following Oracle Platform Security Services (OPSS) WLST commands in online (connected) mode:

wls:/mydomain/serverConfig>
grantPermission(codeBaseURL="file:${ums.oracle.home}/communications/modules/oracle.sdp.client_11.1.1/-",
permClass="oracle.security.jps.JpsPermission",permTarget="IdentityAssertion", permActions="execute")

wls:/mydomain/serverConfig>
grantPermission(codeBaseURL="file:${ums.oracle.home}/communications/modules/oracle.sdp.messaging_11.1.1/-",
permClass="oracle.security.jps.JpsPermission",permTarget="IdentityAssertion", permActions="execute")

See Oracle WebLogic Fusion Middleware Scripting Tool Command Reference for information regarding grantPermission

25.1.3 XML File Handle Left Open after Upload Fails

If an error occurs when uploading a user messaging preferences XML file using the WLST manageUserMessagingPrefs command, the XML file handle is left open. On the Microsoft Windows platform, this file cannot be deleted until you exit the WLST shell.

25.1.4 Messages Metrics Rendered as Unavailable in the Performance Page for User Messaging Server

When no metric data is found (for example when no messages have been sent or received after server setup), the Metrics Performance page will display Unavailable. This is not a problem with the software, and the Performance reporting is operating properly. As soon as Send and Receive traffic exists, the Performance page will display results normally.

25.1.5 User Messaging Service URLs Unavailable After Restart

Upon restarting the User Messaging Service server (usermessagingserver) from Oracle Enterprise Manager Fusion Middleware Control or through Oracle WebLogic Console, you may get an error: Error 503--Service Unavailable when attempting to access any URLs served by the User Messaging Service server, such as the User Preferences UI (/sdpmessaging/userprefs-ui) or the various Web Services endpoints. This error occurs intermittently in cases when the Oracle WebLogic Server is heavily loaded (such as with a SOA instance). To work around this issue:

- Restart the User Messaging Service server again (two or more restarts may be required).

- If multiple User Messaging Service server restarts are not sufficient, then restart the entire Oracle WebLogic Server instance.

25.1.6 User Preferences User Interface Renders Improperly

Intermittent UI rendering errors have been reported in some languages, due to the generation of a corrupted .css file. If you experience problems, follow these steps to work around the issue:

1. Delete the cached, auto-generated .css file for the affected locale (or simply, all locales) on the server located at DOMAIN_HOME/servers/<server_name>/tmp/_WL_user/usermessagingserver/<random_name>/public/adf/styles/cache and restart the usermessagingserver application using Oracle Enterprise Manager Fusion Middleware Control. Have all users clear their browser caches.
The next time the UI is accessed from a browser, a new .css file will be generated for the desired locale, and it is very likely that it will be a valid .css file. If not, repeat this process a couple of times.

2. If the previous solution does not work, disable content compression in the web.xml file of the User Preferences Web Module located at DOMAIN_HOME/servers/<server_name>/tmp/_WL_user/usermessagingserver/<random_name>/sdpmessaginguserprefs-ui-web.war. In particular, extract web.xml, add the following <context-param/> to it:

<context-param>
<param-name>org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION</param-name>
<param-value>true</param-value>
</context-param>

Then, re-archive it to the war module.

Finally, restart the usermessagingserver application using Oracle Enterprise Manager Fusion Middleware Control.

25.1.7 UMS Cluster Failover May Lose Messages

Since XA is not supported for UMS in 11gR1PS6, UMS cluster failover may lose messages.

25.2 Configuration Issues and Workarounds

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

- Section 25.2.1, "Enable Extension Driver after Upgrade"

- Section 25.2.2, "Preseeded Channel for Worklist and Pop-up Drivers Cannot be Removed"

- Section 25.2.3, "Worklist Driver Configuration"

- Section 25.2.4, "Migrate Custom Business Terms After PS3 Patch"

- Section 25.2.5, "Use Correct SSL Trust Store When Configuring Drivers"

- Section 25.2.6, "User Messaging Service Driver Configuration Changes Not Immediately Effective"

- Section 25.2.7, "Email Notifications Sent Even if You Do Not Change Default Parameters in driverconfig.xml"

25.2.1 Enable Extension Driver after Upgrade

When you upgrade to the current release, you must complete the following manual configuration steps in order to enable use of the Extension driver:

1. Stop all servers it the domain.

2. Add this .jar file to the classpath of the domain:

$UMS_ORACLE_HOME/communications/modules/usermessaging-config_11.1.1.jar

This can be done by modifying the setDomainEnv.sh/setDomainEnv.cmd in the domain's bin folder. That is, the POST_CLASSPATH variable is updated like this:

POST_CLASSPATH="${UMS_ORACLE_HOME}/communications/modules/usermessaging-config_11.1.1.jar${CLASSPATHSEP}${POST_CLASSPATH}"export POST_CLASSPATH

3. From the template .jar file at $UMS_ORACLE_HOME/common/templates/applications/oracle.ums_template_11.1.1.jar extract the .xml files:

/config/fmwconfig/usermessagingconfig.xml
/config/fmwconfig/mbeans/ums-mbeans.xml

4. Copy these two .xml files into the domain's config and fmwconfig folders:

$DOMAIN_HOME/config/fmwconfig/usermessagingconfig.xml
$DOMAIN_HOME/config/fmwconfig/mbeans/ums-mbeans.xml

5. Start the servers.

6. Deploy the UMS Extension Driver by executing the WLST driver deployment command. For example:

wls:/emsoa/serverConfig> deployUserMessagingDriver(baseDriver='extension',appName='extension', targets='soa_server1')

The UMS Extension Driver is now enabled.

25.2.2 Preseeded Channel for Worklist and Pop-up Drivers Cannot be Removed

If you deinstall the Worklist or Pop-up driver, the preseeded channel for these drivers cannot be removed. The preseeded channel will remain available in your preference list.

25.2.3 Worklist Driver Configuration

While following the Worklist Driver configuration instructions, you may see that Oracle User Messaging Service for SOA in the Configuration Wizard is not selected, leading you to think that it is not configured and that you must select and configure it. This is not the case. The basic Oracle User Messaging Service is already configured, along with a few UMS drivers.

Continue to follow the documented instructions, and disregard the fact that the Oracle User Messaging Service for SOA option is unselected.

25.2.4 Migrate Custom Business Terms After PS3 Patch

After installing the PS3 patch, you must re-create any custom-built business terms using Oracle Enterprise Manager Fusion Middleware Control. A copy of the custom-built business terms is available at: $DOMAIN_HOME/config/fmwconfig/servers/<ServerName>/applications/usermessagingserver/configuration/businessterms.xml.bak

Restart your servers after making any changes!

Note:

New, pre-seeded business terms have been introduced in this release. Do not overwrite the upgraded (PS3) file with a PS1 backup (the new terms will be lost, otherwise).

25.2.5 Use Correct SSL Trust Store When Configuring Drivers

Before configuring any User Messaging Service Driver (such as the Email Driver), to connect to a remote gateway using SSL, ensure that the SSL Trust Store is properly configured as described in "Configure Keystores" in Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.

Ensure that the value of the JVM system property (javax.net.ssl.trustStore) set in $DOMAIN_HOME/bin/setDomainEnv.sh (or Windows equivalent file) points to the correct trust store that you want to use.The Java Standard Trust Store is located at:

$JAVA_HOME/jre/lib/security/cacerts or $BEA_JAVA_HOME/jre/lib/security/cacerts

Note that with the default out-of-the-box configuration of SSL trust store, the UMS driver will not be able to connect to the Oracle Beehive Email Server over SSL. To resolve this issue, follow the instructions for using the correct SSL trust store. Replacing the DemoTrust keystore in the setDomainEnv.sh file (or Windows equivalent file) with the Java Standard SSL trust store will enable UMS email driver to connect successfully over SSL to the Oracle Beehive Email Server.

25.2.6 User Messaging Service Driver Configuration Changes Not Immediately Effective

When you change a driver's configuration and then restart the driver, the changes will not take effect until all managed connections in the pool are destroyed (900 seconds [15 minutes] by default). Take one of these actions to ensure that the connections are destroyed:

- When performing driver configuration changes, stop the driver application and wait for 15 minutes. Then re-start the driver application.

Note:

If you follow this recommendation and the wait time of 900 seconds (15 minutes) is too long, you can reduce the time using the Oracle WebLogic Server Administration Console as follows:

1. Click Deployments.

2. Select the desired User Messaging Service Driver deployment.

3. Click the Resource Adapter Type module.

4. Click Configuration > Outbound Connection Pools.

5. Click the DriverConnectionFactory group.

6. Click Connection Pool.

7. Edit the value of Shrink Frequency Seconds (for example, set to 120 seconds).

8. Click Save, and save the changes to a deployment plan file when prompted.

9. Restart the User Messaging Service driver deployment to include the new plan.

Remember that if Shrink Frequency is reduced to a short interval, it may eventually have a negative impact on the performance of the driver as idle connections will be recycled frequently.

OR

- Restart the entire Oracle WebLogic Server after performing driver configuration changes. The new changes will take effect immediately upon server re-start.

25.2.7 Email Notifications Sent Even if You Do Not Change Default Parameters in driverconfig.xml

Instructions for notification configuration include setting your outgoing server parameters. Please note that if you do not change the parameters (that is, if you leave the default setting unchanged), notifications may still be sent. This is expected behavior, but you should not rely on the default settings without verifying them. You should set your parameters to ensure that they are correct.

26 Oracle WebLogic Communication Services

This chapter describes issues associated with Oracle WebLogic Communication Services (OWLCS). It includes the following topics:

- Section 26.1, "General Issues and Workarounds"

- Section 26.2, "Configuration Issues and Workarounds"

- Section 26.3, "Documentation Errata"

26.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topics:

- Section 26.1.1, "Active SIP Session and APP Session Count Show as -1 in Clustered Configuration"

- Section 26.1.2, "Oracle WebLogic Server Pack/Unpack Tool Does Not Function in OWLCS"

- Section 26.1.3, "Oracle WebLogic Server Cloning Tool Does Not Function in OWLCS"

- Section 26.1.4, "Messages Metrics Rendered as Unavailable in the Performance Page for User Messaging Server"

26.1.1 Active SIP Session and APP Session Count Show as -1 in Clustered Configuration

In the Administration Console, the Monitoring -> General tab displays Undefined for the Active SIP Session Count and Active Application Session Count attributes when monitoring a replicated WebLogic SIP Server deployment. There is currently no workaround for this problem.

26.1.2 Oracle WebLogic Server Pack/Unpack Tool Does Not Function in OWLCS

The Pack/Unpack tool in Oracle WebLogic Server does not work in this OWLCS release. There is no workaround currently available.

26.1.3 Oracle WebLogic Server Cloning Tool Does Not Function in OWLCS

The Cloning tool in Oracle WebLogic Server does not work in this OWLCS release. There is no workaround currently available.

26.1.4 Messages Metrics Rendered as Unavailable in the Performance Page for User Messaging Server

When no metric data is found, for example when no messages have been sent or received after server setup, the Metrics Performance page will display Unavailable. This is not a problem with the software, and the Performance reporting is operating properly. As soon as Send and Receive traffic exists, the Performance page will display results normally.

26.2 Configuration Issues and Workarounds

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

- Section 26.2.1, "Launch_sash Option Error"

- Section 26.2.2, "Same User Who Installed WLS/WLSS Product Must Perform Uninstall"

- Section 26.2.3, "Uppercase Usernames Cause Reregistration and Presence Subscription Failures"

- Section 26.2.4, "Running the uninstall.sh Script in Text Mode Does Not Uninstall the Product"

- Section 26.2.5, "SIP Monitor in F5 Networks BigIP Does Not Work in UDP Mode"

- Section 26.2.6, "SIP Container Does Not Bind to IPV6 Interfaces for Listening on Windows"

- Section 26.2.7, "JAWS Unable to Read Some Install Screens"

- Section 26.2.8, "Configure VoiceXML Driver Receive URLs Correctly"

26.2.1 Launch_sash Option Error

An error has been reported when using the launch_sash command with the -e option. For example:

MW_HOME/user_projects/domains/base_domain/bin/launch_sash.sh -p 8001 -n weblogic -w welcome1 -a presenceapplication -e "xcap appusage list"

does not properly process the xcap appusage list argument because the double quote (") is mishandled.

To work around this problem, issue the command at the sash prompt directly.

26.2.2 Same User Who Installed WLS/WLSS Product Must Perform Uninstall

In order to perform a clean uninstall, ensure that the same user (privileges) who accomplished the install also accomplishes the uninstall.

26.2.3 Uppercase Usernames Cause Reregistration and Presence Subscription Failures

When a user is created with an uppercase username, then the following occurs:

- Initial registration progresses normally, resulting in successful registration with Oracle Communicator.

- Presence subscriptions fails.

- After a few minutes, Oracle Communicator displays Server Refused Registration (403).

- User's account is locked and sign-in is blocked for 30 minutes.

To work around this issue, set Trusted Authentication Hosts for the SIP Container by doing the following (from the Administration Console):

1. Click SipServer in the left pane.

2. Click the SIP Security tab.

3. In Trusted Authentication Hosts, add the IP address of your server (that is running OWLCS).

4. Save and restart OWLCS.

Note:

Using this workaround, presence functionality will fail for clients running on the same machine as the OWLCS server. Such cases (both Oracle Communicator and server running on the same machine) are mostly for demonstration and development environments. For these cases, ensure you create users with lowercase usernames.

Reregistration and presence subscription failures can also occur when users are created with privateId being different than the username part of the publicId.

For example, if privateId is test.user1 and publicId is sip:test.user1@example.com, everything works because test.user1 is the username part of the publicId sip:test.user1@example.com.

But if privateId is tuser1 and publicId is sip:test.user1@example.com, the username part of the publicId is not the same as privateId. In this case, the first registration succeeds with Oracle Communicator, but reregistrations and presence subscriptions fail. Apply the same workaround (configure trusted host as described above) to resolve this issue.

26.2.4 Running the uninstall.sh Script in Text Mode Does Not Uninstall the Product

Perform uninstallation using the Administration Console to ensure that all components are uninstalled. Ensure that you use the same user privilege as when you installed.

26.2.5 SIP Monitor in F5 Networks BigIP Does Not Work in UDP Mode

When using the F5 Networks BigIP load balancer for a cluster of SIP engines and the SIP monitor in BigIP is used for failure detection, it must be configured to operate (sending OPTIONS requests) over TCP and not UDP. UDP mode will not work (the pool will indicate that the servers are down).

26.2.6 SIP Container Does Not Bind to IPV6 Interfaces for Listening on Windows

Due to limitations in the Windows IPv6 stack, the SIP Container cannot bind to IPv6 sockets for listening.

26.2.7 JAWS Unable to Read Some Install Screens

Due to an issue with the OWLCS Core Platform CIE-based installer, the JAWS tool cannot correctly read the installation screens. To work around this issue, you must run the installer in silent mode. For information on Silent Mode installation, see Oracle WebLogic Communication Services Installation Guide.

26.2.8 Configure VoiceXML Driver Receive URLs Correctly

In a clustered (high-availability) environment with Oracle HTTP Server (OHS) configured, do not use the OHS port to configure the VoiceXML Driver Receive URLs. Using the OHS port to configure the VoiceXML Driver Receive URLs will cause a conflict with the drivers.

Each Voice XML Driver must be configured with its own WLS server's port (as described in the parameters' documentation).

26.3 Documentation Errata

This section details changes to the documentation since the last release. Topics include:

- Section 26.3.1, "Create a Basic SIP Domain"

- Section 26.3.2, "Create a Custom AUID with OCP (Presence)"

- Section 26.3.3, "Cannot Create a SIP Server Domain Using Default WebLogic Platform Components"

- Section 26.3.4, "Broken Documentation Links in Some (SIP Server) Translated Files"

- Section 26.3.5, "Missing (SIP Server) Online Help Regarding Security Providers"

26.3.1 Create a Basic SIP Domain

Directions for creating a basic SIP Domain have changed slightly in this release. Please ensure that you follow these steps:

1. Start the configuration wizard located at WLS_HOME/wlserver_10.3/common/bin/config.sh. This location has changed since the last release.

2. Select Create a New WebLogic Domain, and click Next.

3. Select Basic WebLogic SIP Server Domain, and click Next.
The rest of the process remains the same as before when creating a WLS Domain.

26.3.2 Create a Custom AUID with OCP (Presence)

Follow these steps to create custom AUIDs:

1. View the XML file for presence rules (presrules_au.xml). It is found in one of the following locations, depending on your installation:

$ORACLE_HOME/j2ee/ocms/config/sdp/xcap

$ORACLE_HOME/j2ee/home/config/sdp/xcap

The file contains the following:

- Name of the application (pres-rules)

- Mime type

- User Quota

- List of schemas associated with the application's XML files

2. Create a similar file for the new application usage

3. For all the XSD files listed in the XML file above, create the XSD files and copy them to the XCAP config location mentioned in Step 1 above.

4. cd $ORACLE_HOME/sdp/bin

5. ./launch_sash.sh -a presenceapplication

6. Provide admin credentials. At the sash prompt enter:

xcap appusage create applicationUsage=<new application usage name>
configurationFilename=<name of application usage XML file>

For instance, this command was run to create the pres-rules application usage:

xcap appusage create applicationUsage=pres-rules
configurationFilename=presrules_au.xml

7. To provision users for the new application usage, at the sash prompt enter:

xcap user add userName=<string> applicationUsage=<new application usage name>
.
<string> is of the form username@example.com (replace example.com with domain
for the deployment)

26.3.3 Cannot Create a SIP Server Domain Using Default WebLogic Platform Components

When running config.sh for SIP Server domain configuration, you can choose whether to use WebLogic Platform Components or a Custom Template. The default for Select Domain Source is to use WebLogic Platform Components. In previous releases, this selection worked, but does not in this release. You must select Custom Template in order to create a SIP Server domain.

26.3.4 Broken Documentation Links in Some (SIP Server) Translated Files

Some links to additional documentation were removed in the English language version, but broken links in translated (languages other than English) have been reported. These broken links are being addressed.

26.3.5 Missing (SIP Server) Online Help Regarding Security Providers

Online Help regarding Security Providers is not included. Oracle SIP Server, including information about security providers, is licensed and documented through OCCAS. Please consult your OCCAS documentation for more information.

Part X

Oracle Identity Management

Part X contains the following chapters:

- Chapter 28, "Oracle Access Manager"

- Chapter 27, "Oracle Adaptive Access Manager"

- Chapter 38, "Oracle Authentication Services for Operating Systems"

- Chapter 36, "Oracle Directory Integration Platform"

- Chapter 29, "Oracle Entitlements Server"

- Chapter 30, "Oracle Identity Federation"

- Chapter 31, "Oracle Identity Manager"

- Chapter 32, "Oracle Identity Navigator"

- Chapter 33, "Oracle Internet Directory"

- Chapter 34, "Oracle Platform Security Services"

- Chapter 35, "SSL Configuration in Oracle Fusion Middleware"

- Chapter 37, "Oracle Virtual Directory"

27 Oracle Adaptive Access Manager

This chapter describes issues associated with Oracle Adaptive Access Manager. It includes the following topics:

- General Issues and Workarounds

- Policy Management Issues and Workarounds

- Transaction Issues and Workarounds

- Knowledge-Based Authentication Issues and Workarounds

- Integration Issues and Workarounds

- Reporting Issues and Workarounds

- Configuration Issues and Workarounds

- Customer Care Issues and Workarounds

- Performance Issues and Workarounds

- Geolocation Data Loader Issues and Workarounds

- Multi-Language Support Issues and Workarounds

27.1 General Issues and Workarounds

This section describes general issues. It includes the following topics:

- OAAM Sessions is Not Recorded When IP Address from Header is an Invalid IP Address

- Checkpoint Boxes in Session are Displayed with Same Timestamp

- Autogenerated Agent Cases Display User Specific Data

27.1.1 OAAM Sessions is Not Recorded When IP Address from Header is an Invalid IP Address

OAAM sessions were not recorded for some header-based IP addresses.

Header based IP addresses are not accepted by default. To enabled the reading of IP addresses from the header, set vcrypt.tracker.ip.detectProxiedIP to true. When header IP addresses are enabled, only valid IP addresses are used. If the header contains an invalid IP address, the actual request IP address is used.

27.1.2 Checkpoint Boxes in Session are Displayed with Same Timestamp

The same timestamp is displayed in Checkpoint boxes in the Session Details page when multiple transactions are triggered in the same session. This bug has been fixed for OAAM Online.

27.1.3 Autogenerated Agent Cases Display User Specific Data

When an OAAM Agent Case is autogenerated from a Configurable Action, the User Details pane is populated with details of the user for the session where the case was created. An autogenerated Agent case should not contain user-specific data. Only Escalated Agent cases should display user details since they are the only cases specific to a single end user.

27.2 Policy Management Issues and Workarounds

This section describes policy management issues and workarounds. It includes the following topics:

- Rule Condition Check Current Transaction Using the Filter Conditions Cannot Be Configured for Corresponding Attributes of Two Entity Instances

- Rule Condition to Check Consecutive Transactions Fails Entity Check

- Exclude IP List Parameter for User and Device Velocity Rule Conditions

- OAAM Offline Displays Only the Last Rule Executed Overwriting Previous

- User: Check First Login Time Rule Condition Always Triggers

27.2.1 Rule Condition Check Current Transaction Using the Filter Conditions Cannot Be Configured for Corresponding Attributes of Two Entity Instances

When two instances of an entity are associated to an OAAM Transaction and a filter condition is set up to compare an attribute of one entity instance with the corresponding attribute of the other entity instance, the OAAM Administration Console can only configure a comparison between the same attribute instead of a comparison between the different attributes.

For example:

Two instances of the Address entity are associated with a Transaction, one with the instance name BillingAddr and another with the instance name ShippingAddr. If the user configures Check Current Transaction using the filter condition to compare Billing.line1 with ShippingAddr.line1, after saving the rule, the OAAM Administration Console always shows the instance --- line1 of BillingAddr in the dropdown for the attribute the user wants to compare and the dropdown for the attribute the user is comparing to.

27.2.2 Rule Condition to Check Consecutive Transactions Fails Entity Check

The rule condition TRANSACTION: Check if consecutive Transactions in given duration satisfies the filter conditions does not trigger. The condition returns False and the entity check fails with exceptions in the debug log.

27.2.3 Exclude IP List Parameter for User and Device Velocity Rule Conditions

The Exclude IP List parameter was added to the following conditions:

- Device: Velocity from last login

- User: Velocity from last login

This parameter allows you to specify a list of IP addresses to ignore. If the user's IP address belongs to that list, then this condition always evaluates to false and no action and/or alert is triggered. If the user's IP address is not in that list or if the list is null or empty, then the condition evaluates the velocity of the user or the device from the last login. If the velocity of the user or the device from the last login is more than the configured value in the rule, the condition evaluates to true and the condition is triggered.

27.2.4 OAAM Offline Displays Only the Last Rule Executed Overwriting Previous

When multiple transactions are run in the same session, only the rule triggered for the last transaction is displayed in OAAM offline. The rules from the previous transactions are overwritten. To fix this bug, you must apply the patch and update the database schema.

27.2.5 User: Check First Login Time Rule Condition Always Triggers

The User: Check first login time condition returned the same value regardless of when the user logged in.

27.3 Transaction Issues and Workarounds

This section describes OAAM Transaction issues. It includes the following topics:

- OAAM Displays Only the Last Rule Executed and Overwrites Previous Rules

- OAAM Shows Only 25 Transactions in Session Details

- Alerts Are Not Displayed Beyond 25 Transactions

- OAAM Transaction Cannot Be Created with Numeric Parameter of More than 16 Digits

- Transactions in Session Details Duplicated After 25

- Transaction ID Association with Alert Does Not Work

- OAAM Console Does Not Display Transaction Status

- Transaction Mapping Substring Error for First Character Value

- Update Time for Entity Is Updated Without Any Change in Entity Data

27.3.1 OAAM Displays Only the Last Rule Executed and Overwrites Previous Rules

When multiple transactions are triggered in the same session which result in multiple alerts and policies execution, OAAM displays only the most recent alerts and policies triggered and overwrites the alerts and policies from previous transactions.

27.3.2 OAAM Shows Only 25 Transactions in Session Details

When there are more than 25 data elements configured for a transaction, the Session Details displays only transaction details for the first 25 items. The page has no scroll bars for scrolling.

27.3.3 Alerts Are Not Displayed Beyond 25 Transactions

Alerts are not visible for transactions beyond the 25th. If there are more than 25 checkpoint boxes containing alerts, they are not visible in the Session Details, although the data is seen in the database.

27.3.4 OAAM Transaction Cannot Be Created with Numeric Parameter of More than 16 Digits

If a user defines any numeric value more than 16 digits in a transaction field, the transaction creation fails with the error on the server of ORA-01438: value larger than specified precision allowed for this column.

27.3.5 Transactions in Session Details Duplicated After 25

Transactions listed in Session Transactions section of Session Details are duplicated after 25 transactions in a session.

27.3.6 Transaction ID Association with Alert Does Not Work

Transaction ID association with Alert is not working even after passing transactionId in processRules API. The bug has been fixed for the server-side.

27.3.7 OAAM Console Does Not Display Transaction Status

Transaction status needs to be displayed in the Transaction Details page so that the Fraud team will be able to see if a transaction was attempted but did not complete. This provides information on both the behavior of customers and fraudsters and also of the functioning of the rules. The Fraud team does not believe they can do their job effectively if they cannot tell the transaction status. The workaround is to display the status value for each transaction on the Session Transactions panel along with Name, Transaction Id, Description, and Timestamp. The value displayed would be mapped from the property tracker.transaction.status.enum (e.g. 1=Success, 99=Pending).

27.3.8 Transaction Mapping Substring Error for First Character Value

When the user performs a transaction mapping of the type SubString, the first character of the value is missing from the mapping result because the oaam.transaction.mapping.startindex.min property was set to 1. Setting the property to 1 starts the substring operation from the second character of the string. A fix has been made so that this property is assigned to 0 so that the substring operation starts from the first character of the string.

27.3.9 Update Time for Entity Is Updated Without Any Change in Entity Data

When using an entity that is mapped to a Transaction Definition in a transaction, the entity's update time is updated by the OAAM Server even if no changes were made to the entity data (other fields are not updated). Database performance is impacted when this occurs.

27.4 Knowledge-Based Authentication Issues and Workarounds

This section describes Knowledge-Based Authentication issues. It includes the following topics:

- Registration Logic Page Does Not Display KBA Logic

- Answer Logic Abbreviation Resource Was Not Used

- Update KBA for FFIEC Compliance

- Closing Browser on Image and Security Phrase Registration Page

- OAAM Change Password Does Not Display Any Validation for Password Fields

- ORA-01722 Occurs During KBA Update

- Registered Questions Are Deleted and Subsequent Challenge Does Not Succeed

27.4.1 Registration Logic Page Does Not Display KBA Logic

The KBA Registration Logic page does not display KBA Logic (Question per menu, Categories per menu, Number of questions the user will register) because the previous out of the box snapshot did not contain the properties for the KBA Registration Logic page. The patch fixes this problem. To effect this fix, the new out of the box snapshot file (oaam_base_snapshot.zip) needs to be imported. Note that importing this file will overwrite the existing content in the server.

If you do not want to import the snapshot file, but want to fix the registration logic related issue, you can create the following properties (with default values as shown):

challenge.question.registration.groups.categories.count=5
challenge.question.registration.groups.count=3
challenge.question.registration.groups.minimum.questions.per.category.count=1
challenge.question.registration.groups.questions.count=5

The patch also fixes the policy overrides in such a way that when the user fails the OTP challenge, the challenge does use KBA as a fallback. If you do not want to overwrite the contents but just import the newer policies, you can import oaam_policies.zip as a policies import. Importing the policies does not fix the registration logic related bug.

27.4.2 Answer Logic Abbreviation Resource Was Not Used

Answer Logic checks if the answer provided by the user matches closely to the ones provided during registration. Answer Logic relies abbreviations.

An updated Answer Logic abbreviations resource bundle is available in OAAM 11.1.1.5. In the new resource bundle, the following are considered a match:

Registered Answer

Given Answer

Missus

Mrs

Mister

Mr

Sergeant

Sgt

Mrs

Missus

Mr

Mister

Sgt

Sergeant

27.4.3 Update KBA for FFIEC Compliance

The following KBA questions from previous releases were deleted from the kba_questions.zip (English) file and oaam_base_snapshot.zip file for Federal Financial Institutions Examination Council (FFIEC) compliance:

Children Category

Delete or deactivate the following 10 questions:

- What year was your oldest child born?

- What year did your oldest child start school?

- What year did your youngest child start school?

- What is your eldest child's middle name?

- What is the first name of your youngest child?

- What year was your youngest child born?

- What is the first name of your oldest child?

- What is your youngest child's birthday?

- What is your youngest child's middle name?

- What is your oldest child's birthday?

Education Category

Delete or deactivate the following 18 questions:

- What year did you graduate from high school?

- What year did you graduate from junior high school?

- What city was your high school in?

- What were your college colors?

- What year did you graduate from grade school?

- What was the mascot of your college?

- What were your high school colors?

- What was the mascot of your high school?

- What is the name of a college you applied to but did not attend?

- In what city was your first elementary school?

- What year did you start high school?

- What year did you start junior high school?

- What year did you start grade school?

- What year did you graduate from college?

- What year did you start college?

- What was your major in college?

- What was the first school you ever attended?

- What city was your college in?

Miscellaneous Category

Delete or deactivate the following 2 questions:

- What is the first name of your closest childhood friend?

- What is your height?

Parents, Grandparents, Siblings Category

Delete or deactivate the following 17 questions:

- What year was your father born?

- What is your father's birthday?

- What is your oldest sibling's nickname?

- In which city was your father born?

- In which city was your mother born?

- What is your parent's current street address number?

- What is your parent's current street name?

- What is your youngest sibling's nickname?

- What is your parent's current ZIP code?

- What year was your mother born?

- What are the last 4 digits of your parent's phone number?

- What is your maternal grandmother's first name?

- What is your paternal grandmother's first name?

- What is the first name of your youngest sibling?

- What is your paternal grandfather's first name?

- What is your mother's birthday?

- What is the first name of your eldest sibling?

Significant Other Category

Delete or deactivate the following 18 questions:

- Where did you go on your honeymoon?

- What year did you get married?

- What year was your significant other born?

- What is your significant other's birthday?

- What date is your wedding anniversary?

- In what city did you meet your spouse for the first time?

- What city was your significant other born in?

- What is the first name of your significant other's mother?

- What is the first name of your significant other's father?

- What is the last name of your significant other's eldest sibling?

- What is the first name of your significant other's youngest sibling?

- What high school did your significant other attend?

- What was the last name of your best man or maid of honor?

- What was the first name of your best man or maid of honor?

- Name of the place where your wedding reception was held.

- What is your spouse's nickname?

- What state was your significant other born in?

- What is the last name of your significant other's youngest sibling?

Sports Category

Delete or deactivate the following 4 questions:

- What is the mascot of your favorite sports team?

- What are the colors of your favorite sports team?

- What team is the biggest rival of your favorite sports team?

- What is your all time favorite sports team?

Your Birth Category

Delete or deactivate the following 9 questions:

- What is the ZIP code where you grew up?

- Who was the US President when you were born?

- How old was your father when you were born?

- How old was your mother when you were born?

- What is the name of the hospital you were born in?

- What is the ZIP code of your birthplace?

- What is the holiday closest to your birthday?

- What state were you born in?

- What city were you born in?

27.4.4 Closing Browser on Image and Security Phrase Registration Page

If the user tries to register his security image and phrase for the first time and during the process, he closes his browser window on the registration and user preferences pages or returns to the login page, the last image and phrase presented are accepted as the default even if he has not explicitly chosen them by clicking the Continue button.

A fix has been made so that the image and phrase registration only saves the image and phrase after the user clicks Continue on the registration and user preferences pages.

27.4.5 OAAM Change Password Does Not Display Any Validation for Password Fields

The OAAM Change Password page in an OAAM and OIM integration does not display any validation for the Password field. The issues are as follows:

- If the user does not enter a password, but clicks Submit, there is no validation that the fields are empty

- If the user enters a new password and then the confirmation password, the password is accepted regardless of whether they are the same or different

- If the user changes his password, the old password is not validated to confirm that it is correct

27.4.6 ORA-01722 Occurs During KBA Update

An ORA-01722 error can occur when adding a new challenge question.

27.4.7 Registered Questions Are Deleted and Subsequent Challenge Does Not Succeed

If a user's question set contains a deleted question and/or if a user's registered questions contain a deleted question and/or if the KBA registration logic is out of alignment with the user's registered questions and question set (the number of questions/categories and so on), when the user tries to update his question set but cancels or closes the browser window or the session times out without saving, that user's existing questions are deleted from the database. The subsequent challenge does not succeed as the existing questions have been deleted.

This issue has been fixed so that now if a user's registered questions have been deleted in the process of resetting the questions, the user will be asked to re-register new ones on the next login.

27.5 Integration Issues and Workarounds

This section describes OAAM integration issues. It includes the following topics:

- setupOAMTapIntegration.sh Does Not Set oaam.uio.oam.secondary.host.port

- OAAM Does Not Support Juniper Single Sign-On for Authentication and Forgot Password Flow

- Step Up Authentication Changes

- TAP: Incorrect Error Message

- OAAM 11g SOAP Timeout Exception Handling

- OAAM Should Call UserManager.Unlock() in the Forgot Password Workflow

27.5.1 setupOAMTapIntegration.sh Does Not Set oaam.uio.oam.secondary.host.port

The setupOAMTapIntegration.sh script does not set the secondary OAM host information (oaam.uio.oam.secondary.host.port value) during the configuration of Oracle Adaptive Access Manager for the Oracle Access Manager and Oracle Adaptive Access Manager integration. The workaround is to set the property value through the property editor.

27.5.2 OAAM Does Not Support Juniper Single Sign-On for Authentication and Forgot Password Flow

The OAAM Authentication flow is not invoked when integrated with Juniper SSL. With invoking OAAM, the integration can detect fraud and determine risk during the authentication flow and accordingly strongly authenticate the user using OAAM capabilities like Challenge, Block, and other actions. The Juniper SSL and OAAM integration flow should be as follows:

1. The user tries to access a web application or URL that is secured by Juniper SSL, and Juniper SSL detects whether the user is authenticated or not.

2. If the user is authenticated then he is allowed to proceed to the web application.

3. If the user is not authenticated, he is redirected to the OAAM Server. The OAAM Server displays the User ID page and prompts the user to enter his User ID. Once the user enters his User ID, OAAM evaluates the Pre-Authentication checkpoint policies and checks to see if the user has to be blocked.

4. OAAM then checks to see if the user has registered for an Authentication Pad. If so, it displays the registered Authentication Pad, otherwise it displays a generic text pad.

5. OAAM Server displays the Password page with the Authentication Pad and prompts the user to enter his password. Once the password is entered, it is validated against the user store (the user store can be LDAP, Active Directory, or any active user store). It also identifies the device by running the device identification process.

6. If the credentials are incorrect then OAAM displays an error page and asks the user to enter his credentials again.

7. If the credentials are correct then OAAM evaluates Post-Authentication checkpoint policies. Based on the outcome of the policy OAAM might challenge or block the user.

8. If the outcome of Post-Authentication is ALLOW then OAAM determines if the user has to be registered. Based on the types of registration, OAAM takes the user through registration pages.

9. If the outcome of Post-Authentication is CHALLENGE and if the user is already registered for at least one of the challenge mechanisms, OAAM challenges the user. If the user is able to answer the challenge then he would be allowed to continue to the next step. As the next step OAAM fetches the user attributes from the user store and then creates the SAML response, signs it and then it posts to the Juniper SSL redirection URL. Juniper SSL then takes control, validates the SAML payload, and lets the user access the web application.

10. If the outcome of Post-Authentication is BLOCK then user would be blocked and he would not be able to access the web application.

27.5.3 Step Up Authentication Changes

The Step Up Authentication feature is available with OAAM. Step Up Authentication allows users who have been authenticated by OAM at a lower level to access resources protected by OAAMTAPScheme configured at a relatively higher authentication level. When the user tries to access a protected resource that is configured at a higher level, OAAM runs policies to determine how to further authenticate the user so as to gain the required level of authentication needed for access to the protected resource. The user is not taken to the normal login flow since he is already authenticated.

The property to disable/enable Step Up Authentication mode in TAP Integration: By default the Step Up Authentication mode is enabled. However if you want to disable this feature, then set property oaam.uio.oam.integration.stepup.enabled as false.

Change in behavior for the end user: For an end user using the Access Manager-OAAM TAP Integration, the change in behavior is as follows:

If a user has already been authenticated by Access Manager and he tries to access a resource protected under TAPScheme with OAAM as the TAP partner, the user is not taken to the OAAM login flow (since the user is already authenticated). However, OAAM runs its fraud detection policies and might ask challenge questions or block the user depending on the risk evaluated by the policies.

27.5.4 TAP: Incorrect Error Message

In Access Manager-OAAM TAP integration, when an incorrect user name or password is supplied, OAAM shows following error:

There was some technical error processing your request.   Please try again

The patch fixes this problem: the error message now indicates an invalid user name or password error instead of a technical error.

27.5.5 OAAM 11g SOAP Timeout Exception Handling

The client calling Web services is not getting exceptions for timeouts. As a result the client cannot handle SOAP timeouts in a proper way because it cannot determine whether the exception is a SOAP timeout or any other faults. A fix has been implemented so that a specific error code for timeouts is passed to the client. The client can therefore handle the fault per the information contained in the exception.

The method handleException() has introduced a class VCryptSOAPGenericImpl which can be overridden to include more error codes based on business requirements. Currently it has been set for soaptimeout errors:

protected String handleException(String requestName, Exception ex, String resultXml) {

27.5.6 OAAM Should Call UserManager.Unlock() in the Forgot Password Workflow

In the Forgot Password flow executed by OAAM in an Oracle Identity Manager and Access Manager integration, the user is not unlocked when he changes his password. When OAAM executes the changePassword() API, Oracle Identity Manager does not automatically unlock the user.

The following steps are needed to enable automatic unlocking of the user on the Oracle Identity Manager side when OAAM executes the changePassword () API during the Forgot Password flow:

1. Log in to the OAAM Administration Console.

2. In the navigation pane, click Environment and double-click Properties. The Properties search page is displayed.

3. Set oaam.oim.passwordflow.unlockuser to true.
By default this property value is set to false. By setting this property to true OAAM will call the unlock API of Oracle Identity Manager in the Change Password task flow.

27.6 Reporting Issues and Workarounds

This section describes OAAM BI Publisher reports and Sessions issues and workarounds. It includes the following topics:

- Alert Message Link in Session Details Page Does Not Open the Alert Details

- OAAM Rules Breakdown Report Does Not Provide Correct Information

27.6.1 Alert Message Link in Session Details Page Does Not Open the Alert Details

When the user tries to access an alert details page from an alert message link in the Session Details page, the page fails to open.

To work around this issue, use the alert message link on the Session Search page.

27.6.2 OAAM Rules Breakdown Report Does Not Provide Correct Information

The BI Publisher Rules Breakdown report does not give a summary of the rules which have been triggered by the checkpoint and policy. The values given are not complete or accurate.

For the report to work, run the following script:

create or replace view OAAM_FIRED_RULES_VIEW as (

select actionMap.create_time, ruleMaps.rule_map_id, actionMap.request_id,

actionMap.runtime_type,

sessions.user_id, sessions.node_id, actionMap.action_list

from (select substr(attr_name, 7) ruleInstanceId, case when

length(trim(translate(attr_value, '+-.0123456789', ' '))) is null then

CAST(attr_value AS NUMBER(16)) else null end rule_map_id, fprint_id from

v_fp_map where attr_name like 'RLD_ID%') ruleMaps

inner join vt_session_action_map actionMap on actionMap.rule_trace_fp_id =

ruleMaps.fprint_id

inner join vcrypt_tracker_usernode_logs sessions on sessions.request_id =

actionMap.request_id

inner join (select substr(attr_name, 11) ruleInstanceId, case when

length(trim(translate(attr_value, '+-.0123456789', ' '))) is null then

CAST(attr_value AS NUMBER(16)) else null end attr_value, fprint_id from

v_fp_map where attr_name like 'RLD_STATUS%') ruleStatus

on ruleStatus.ruleInstanceId = ruleMaps.ruleInstanceId and

ruleStatus.fprint_id = ruleMaps.fprint_id

where ruleStatus.attr_value=1

union select ruleLogs.create_time, ruleLogs.rule_map_id,

policySetLogs.request_id, policySetLogs.runtime_type,

userNodeLogs.user_id, userNodeLogs.node_id, ruleLogs.action_list

from VR_RULE_LOGS ruleLogs

inner join VR_MODEL_LOGS modelLogs on ruleLogs.MODEL_LOG_ID =

modelLogs.MODEL_LOG_ID

inner join VR_POLICY_LOGS policyLogs on modelLogs.POLICY_LOG_ID =

policyLogs.POLICY_LOG_ID

inner join VR_POLICYSET_LOGS policySetLogs on policyLogs.POLICYSET_LOG_ID =

policySetLogs.POLICYSET_LOG_ID

inner join VCRYPT_TRACKER_USERNODE_LOGS userNodeLogs on

policySetLogs.REQUEST_ID = userNodeLogs.REQUEST_ID

where ruleLogs.status=1);

commit;

27.7 Configuration Issues and Workarounds

This section describes the following configuration issues and workarounds:

- Database Archive and Purge Scripts Missing from Installation

- Juniper Login Fails Due to Incorrect CN Value and No UID Attribute in SAML Response

27.7.1 Database Archive and Purge Scripts Missing from Installation

Case and monitor data purge scripts are missing from the oaam_db_purging_scripts.zip file.

For purging case data, the following scripts need to be included:

- create_case_purge_proc.sql
The create_case_purge_proc.sql script is required to set up the archive and purge routines for the Oracle database.

- exec_sp_purge_case_data.sql
The exec_sp_purge_case_data.sql is required to perform the archive and purge of case data.

For purging monitor data, the following scripts need to be included:

- drop_monitor_partition.sql
Customers who are using the Oracle table partitioning option and have no reporting database should run the drop_monitor_partition.sql script before setting up purging routine for monitor data.

- exec_v_monitor_purge_proc.sql
The exec_v_monitor_purge_proc.sql script calls the stored procedures to archive and purge data from device fingerprinting tables.

- create_v_monitor_purge_proc.sql
The create_v_monitor_purge_proc.sql script creates the V_MONITOR_DATA_PURGE table and the stored procedure SP_V_MON_DATA_PURGE_PROC to archive and purge data from the transaction table.

27.7.2 Juniper Login Fails Due to Incorrect CN Value and No UID Attribute in SAML Response

After successful authentication, OAAM obtains the user attributes from the user store and sends user attributes in a SAML assertion to Juniper. Juniper is set up to look for attributes to read from the SAML assertion to match the user in its repository. Then it logs the user in to the requested target page or web application.

In this bug, the user is unable to log in to Juniper via OAAM because Juniper fails to identify the user. OAAM did not fetch the correct cn (common name) value and it did not set the uid (User ID) attribute in the SAML response.

27.8 Customer Care Issues and Workarounds

This section describes customer care and investigation issues. It includes the following topics:

- Investigator Role Overrides CSR Role When Both Roles Are Given to a User

- Scroll Bars Missing from Some Case Management Screens

- Case Search and Case Details Do Not Display Case Disposition

- Wrong User Attributed for Last Notes Added If Two Users Concurrently Update Case Notes

- Manually Created OAAM Agent Cases Cannot Be Searched by Username or User ID

- OAAM Allows Case Ownership Change and Add Notes Actions to Closed Case

- Create Agent Case Configurable Action Displays Wrong Name for Action

- KBA and OTP Failure Counter Reset and Unlock

27.8.1 Investigator Role Overrides CSR Role When Both Roles Are Given to a User

When a user is given both the Investigator and CSR Access roles, the former overrides the access permissions of the latter and the user has only Investigator access and no CSR access. Expected behavior is that a user having both Investigator and CSR access, should be able to perform Investigator and CSR tasks.

27.8.2 Scroll Bars Missing from Some Case Management Screens

Users with low resolution monitors are not able to see details in full in the Case Details page. Details refer to those available based on a user's role. The Case Details page required scroll bars so that a users with low resolution monitors can see all details.

27.8.3 Case Search and Case Details Do Not Display Case Disposition

After an OAAM Agent case is closed with a disposition of Confirmed Fraud, the agent can locate the case by searching by deposition but Confirmed Fraud is not displayed in the Case search page even after adding Disposition as a column to display. When the Case Details page of the same case is opened, the field is empty for Disposition.

27.8.4 Wrong User Attributed for Last Notes Added If Two Users Concurrently Update Case Notes

OAAM allows two agents to concurrently access a case, but if the two agents add notes to the case, OAAM saves both agents' notes; however, the second agent's notes are displayed as having been added by the first agent. Concurrent write access to cases is supported: if two agents are accessing the case at the same time, the second agent is made aware that the case is being worked on by another agent with a warning message. When the second agent continues, he is made the owner of the case. Notes are attributed to the correct agent.

27.8.5 Manually Created OAAM Agent Cases Cannot Be Searched by Username or User ID

When an OAAM Agent Case is autogenerated from the Configurable Action, the User Details panel is populated with user details for the session for which the case was created. When manually creating a case and linking to a session, user details are not populated. Subsequent searches of cases by Username or User ID only locate automatically created cases.

An enhancement has been made so that the Agent case creation page can optionally accept entry of a valid Username and/or User ID if the oaam.customercare.agent.case.allow.userinfo property is set to true. If a Username and/or User ID is entered it is mapped to the Agent case. Agent cases with a mapped Username and/or User ID are searchable by Username and/or User ID. These cases display the mapped user identifier in the Username and/or User ID column on the Cases search page. Only an Agent case that has been escalated from a CSR case displays the User Details section under the Case Details Summary tab.

27.8.6 OAAM Allows Case Ownership Change and Add Notes Actions to Closed Case

After an Agent case is closed, case ownership can still change when accessed by another user. The case owner is changed to the user who accessed the case. OAAM also allows the adding and editing of notes after a case is closed. After an Agent case is closed, no changes should be allowed.

27.8.7 Create Agent Case Configurable Action Displays Wrong Name for Action

When a Configurable Action triggers the Create Agent Case action, it is displayed as Add to IP Watch list for both the Name and Description of the action when it is added to an Action group.

27.8.8 KBA and OTP Failure Counter Reset and Unlock

Challenge failure counters are not displayed on the CSR Case Details as in the details pages. Failure counters should be displayed for KBA and OTP as well as for new or custom challenge processors. Also, the Reset action does not reset all the counters. An Unlock action should reset all counters (KBA and OTP). The following should occur for counters when the Unlock action is performed:

- Unlocking KBA resets the KBA and OTP failure counters to 0

- Unlocking OTP resets the KBA and OTP failure counters to 0

The following actions should occur for failure counters when the Reset action is performed:

- Resetting KBA resets KBA and OTP failure counters to 0. The user will be required to register challenge questions again

- Resetting CSR KBA resets KBA and OTP failure counters to 0. The user will be required to register challenge questions again

- Resetting OTP resets KBA and OTP failure counters to 0. The user will be required to register OTP again

The following enhancements have been made:

- OAAM Admin Console Case detail and details pages display failure counter, registration, and other information for KBA, OTP, and other custom challenge mechanisms

- OTP failure counters from different channels consolidate failures. For example, if multiple channels are used, the OTP status displays Locked if the combined OTP counters are above the threshold. So, if the user fails SMS twice and Email once and threshold is 3, they are locked using the consolidated OTP counter

- The Reset action resets all challenge failure counters

- The Unlock action is consolidated into an Unlock User action instead of separate actions for unlocking KBA and OTP. The Unlock User action resets all failure counters

- User name is displayed on the Case Details tab instead of or along with Case ID

- The Threshold value for failure counter can be set in the rule condition, User: Challenge Channel Failure.

27.9 Performance Issues and Workarounds

This section describes performance issues. It includes the following topic:

- Out of Memory Error Occurs Scrolling through Sessions Search in OAAM Admin

27.9.1 Out of Memory Error Occurs Scrolling through Sessions Search in OAAM Admin

Scrolling up and down on the Session search page may pass an empty or null input list, which may result in retrieving millions of rows from the database, causing the error, java.lang.OutOfMemoryError:GC overhead limit exceeded.

27.10 Geolocation Data Loader Issues and Workarounds

This section describes geolocation loader issues. It includes the following topics:

- Upload of Geolocation Data Causes Unique Constraint Violation

- IP Location Data Loader Fails If There is a Blank Line in the File

27.10.1 Upload of Geolocation Data Causes Unique Constraint Violation

When reloading the same location data file, or loading an updated location data file, the data would be loaded correctly, but the log file would show numerous warnings about unique constraint violations which degrades performance.

27.10.2 IP Location Data Loader Fails If There is a Blank Line in the File

The OAAM data loader fails to load IP location data if a blank line is in the data file and does not report the line number. The expected result is for the OAAM data loader to skip the blank line and display a warning message that include the line number.

You can work around this issue by opening the IP location data file, removing the blank line, and saving the file. This issue will be fixed in a future release.

27.11 Multi-Language Support Issues and Workarounds

This section describes multi-language support issues and limitations. It includes the following topics:

- Session or Cases Page Cannot Open if Browser Language is Italian

- Session Search and Case Search By Date Range Does Not Work in OAAM Admin Console When Browser Language is Brazilian Portuguese or Spanish

27.11.1 Session or Cases Page Cannot Open if Browser Language is Italian

When the browser language is set to Italian, the user cannot open pages with calendars in the OAAM Administration Console, such as the Session or Cases page. A pop-up window with the following error message is displayed:

java.lang.IllegalArgumentException:
Illegal pattern character 'g'

27.11.2 Session Search and Case Search By Date Range Does Not Work in OAAM Admin Console When Browser Language is Brazilian Portuguese or Spanish

Searching sessions and cases by date range does not work in the OAAM Administration Console when the browser language is set to Brazilian Portuguese or Spanish. When the user opens the calendar in the Session or Cases page in the Spanish or Brazilian Portuguese locale, the year value is always shown as 1970 and cannot be modified to the correct year. As a result, the search does not work and the expected data cannot be returned in the search results.

28 Oracle Access Manager

This chapter describes issues associated with Oracle Access Manager 11g Release 1 (11.1.1). It includes the following topics:

- Section 28.1, "Patch Requirements"

- Section 28.2, "General Issues and Workarounds"

- Section 28.3, "Configuration Issues and Workarounds"

- Section 28.4, "Oracle Security Token Service Issues and Workarounds"

- Section 28.5, "Integration and Inter-operability Issues and Workarounds"

- Section 28.6, "Oracle Access Manager with Impersonation Workarounds"

- Section 28.7, "Documentation Errata"

28.1 Patch Requirements

This section describes patch requirements for Oracle Access Manager 11g Release 1 (11.1.1). It includes the following sections:

- Section 28.1.1, "Plain Text Credentials Exposed in Diagnostic Logs when Creating an Identity Store"

See Also:

- Oracle Technology Network for details about the latest supported versions and platforms:

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

- Oracle Fusion Middleware Patching Guide for details about the latest patch set

- My Oracle Support at the following URL for the latest Oracle Access Manager 11g Release 1 (11.1.1) bundle patches and related release notes:

https://support.oracle.com/

28.1.1 Plain Text Credentials Exposed in Diagnostic Logs when Creating an Identity Store

To work around this issue:

1. Go to My Oracle Support at
http://support.oracle.com

2. Click the Patches & Updates tab, and search for bug 9824531.Download the associated patch and install it by following the instructions in the README file included with the patch.

3. On the Patches & Updates tab, search for bug 9882205. Download the associated patch and install it by following the instructions in the README file included with the patch.

28.2 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topic:

- Section 28.2.1, "Resource Protected By Federation Shown Without Authentication"

- Section 28.2.2, "Issues Registering the OSSO Plugin"

- Section 28.2.3, "Modify Authentication Scheme When Upgrading OAM 11.1.1.5 to OAM 11.1.1.7"

- Section 28.2.4, "RemoteRegistrationServerException Seen After PasteConfig IDM (T2P)"

- Section 28.2.5, "System Error Page Displayed After Login"

- Section 28.2.6, "T2P Paste Config Operation Fails With Exception"

- Section 28.2.7, "Creating Policies For Webgate 11g"

- Section 28.2.8, "Sending Valid Cookie For Embedded BI Content"

- Section 28.2.9, "Incorrect SSO Agent Date/Time Shown to User"

- Section 28.2.10, "Initial Messages After Webgate Registration Are Not Shown in the User's Locale"

- Section 28.2.11, "Single-Click to Open Child Node is Not Supported in the Navigation Tree"

- Section 28.2.12, "User Credential for Registration Tool Does Not Support Non-ASCII Characters on Native Server Locale"

- Section 28.2.13, "Turkish and Greek Character Issues on Oracle Access Manager Authentication Page"

- Section 28.2.14, "Oracle Access Manager Authentication Does Not Support Non-ASCII Passwords on Locales Other than UTF8"

- Section 28.2.15, "Error Message of Create Agent Shows as Server Locale"

- Section 28.2.16, "Referrals in LDAP Searches"

- Section 28.2.17, "Non-ASCII Resources Require OHS To Restart To Make Protection Take Effect"

- Section 28.2.18, "Non-ASCII Characters on Success/Failure URL Results in Garbled Redirect URL"

- Section 28.2.19, "Resource with Non-ASCII Characters Cannot Be Protected by an OSSO Agent"

- Section 28.2.20, "Error in Administration Server Log from Console Logins"

- Section 28.2.21, "Application Domain Subtree in the Navigation Tree Is Not Rendered and Does Not Respond to User Actions"

- Section 28.2.22, "editWebgateAgent Command Does Not Give An Error If Invalid Value is Entered"

- Section 28.2.23, "WLST Command displayWebgate11gAgent In Offline Mode Displays the Webgate Agent Entry Twice"

- Section 28.2.24, "Message Logged at Error Level Instead of at INFO When Servers in Cluster Start"

- Section 28.2.25, "Help Is Not Available for WLST Command registeroifdappartner"

- Section 28.2.26, "User Must Click Continue to Advance in Authentication Flow"

- Section 28.2.27, "OCSP-Related Fields are Not Mandatory"

- Section 28.2.28, "Database Node is Absent in the Console"

- Section 28.2.29, "Online Help Provided Might Not Be Up To Date"

- Section 28.2.30, "Oracle Access Manager Audit Report AUTHENTICATIONFROMIPBYUSER Throws a FROM Keyword Not Found Where Expected Error."

- Section 28.2.31, "Disabled: Custom Resource Types Cannot be Created"

- Section 28.2.32, "Use of a Non-ASCII Name for a Webgate Might Impact SSO Redirection Flows"

- Section 28.2.33, "Authentication Module Lists Non-Primary Identity Stores"

- Section 28.2.34, "Unable to Stop and Start OAM Server Through Identity and Access Node in Fusion Middleware Control"

- Section 28.2.35, "AdminServer Won't Start if the Wrong Java Path Given with WebLogic Server Installation"

- Section 28.2.36, "Changing UserIdentityStore1 Type Can Lock Out Administrators"

- Section 28.2.37, "Page Layouts and Locales"

- Section 28.2.38, "Some Pages Are Not Correctly Localized"

- Section 28.2.39, "Non-ASCII Query String Issues with Internet Explorer v 7, 8, 9"

- Section 28.2.40, "Oracle Virtual Directory with SSL Enabled"

- Section 28.2.41, "Query String Not Properly Encoded"

28.2.1 Resource Protected By Federation Shown Without Authentication

When accessing a page protected by the new Oracle Access Manager integrated Federation feature with the Internet Explorer browser, the browser's delete cookies option does not delete cookies and, therefore, authentication will not be requested. This is a browser specific issue.Workaround: Delete the browsing history using Tools-> Internet Options-> Browsing History (make sure Cookies is selected) and close all instances of Internet Explorer. When accessing the OAM protected page again; authentication will be requested.

28.2.2 Issues Registering the OSSO Plugin

The OSSO Plugin is for iPlanet and IIS when a customer does not wish to use OHS. It must be registered with OID/SSO 10.1.2.3 or 10.1.4.3 which have been discontinued as of 2011.

28.2.3 Modify Authentication Scheme When Upgrading OAM 11.1.1.5 to OAM 11.1.1.7

For any Oracle Access Manager customer that upgrades from OAM 11.1.1.5 to OAM 11.1.1.7 and uses a custom login page, remove the redirect=true entry from Challenge Parameters in the AnonymousScheme authentication scheme or the Login Page will not work. Details are in MOS Note 1548551.1.

28.2.4 RemoteRegistrationServerException Seen After PasteConfig IDM (T2P)

Even when pasteConfig goes through successfully, a RemoteRegistrationServerException is logged. If you can access the Oracle Access Manager console and see all the agents, this exception is benign and can be ignored.

28.2.5 System Error Page Displayed After Login

After successfully logging in to a page with a longer URL, an Oracle Access Manager system error page might be displayed; access to the same page would not have resulted in this in previous releases. Accessing the page with a longer URL a second time may clear this condition.

28.2.6 T2P Paste Config Operation Fails With Exception

When trying to complete the paste config portion of the Test to Production procedure, the following exception may occur:

javax.management.RuntimeMBeanException:
javax.management.RuntimeMBeanException: Configuration MBean not initialized.

There is currently no workaround for this issue.

28.2.7 Creating Policies For Webgate 11g

Oracle Identity Manager and Oracle Access Manager integrations support Webgate 11g. Follow this procedure to create policies for Webgate 11g.

1. Modify the value for WEBGATE_TYPE in the idmConfigTool configOAM and idmConfigTool configOIM property files.

- ohsWebgate11g (for Webgate 11)

- ohsWebgate10g (for Webgate 10)

2. Log in to the Oracle Access Manager console.

3. Select the Policy Configuration tab.

4. Expand Application Domains - IAM Suite

5. Click Resources.

6. Click Open.

7. Click New resource.

8. Provide values for the following:

- Type: HTTP

- Description: OAM Credential Collector

- Host Identifier: IAMSuiteAgent

- Resource URL: /oam

- Protection Level: Unprotected

- Authentication Policy: Public Policy

9. Click Apply.

28.2.8 Sending Valid Cookie For Embedded BI Content

When embedded BI content and Oracle Access Manager are on different physical machines or accessed from different ports on the same machine, the BI proxy on the application's container needs to authenticate itself to the Oracle Access Manager server in order to access the protected BI content. To ensure that the valid OAMAuthnCookie is sent to the Webgate, filterOAMAuthnCookie=false should be set in the User Defined Parameters section of the Webgate's configuration profile. Restart the server after the modification for the new parameter value to take effect.

28.2.9 Incorrect SSO Agent Date/Time Shown to User

The default start date on the Create OAM Agent page is based on the Oracle Access Manager server date/time. The date/time shown to the end user is based on the Oracle Access Manager server time zone rather than on the user's machine.

28.2.10 Initial Messages After Webgate Registration Are Not Shown in the User's Locale

After Webgate registration, the description fields in the initial messages for related components are not shown in the user's locale.

The description field does not support Multilingual Support (MLS).

28.2.11 Single-Click to Open Child Node is Not Supported in the Navigation Tree

Single-click to open a child node in the navigation tree is not supported, but double-click is supported.

28.2.12 User Credential for Registration Tool Does Not Support Non-ASCII Characters on Native Server Locale

The user credential for the Oracle Access Manager registration tool oamreg.sh/oamreg.bat does not support non-ASCII characters on the Linux Non-UTF8 server locale and the Windows native server.

28.2.13 Turkish and Greek Character Issues on Oracle Access Manager Authentication Page

In some cases if a user has Turkish, German, or Greek special characters in the user name and the login name only differs in the special characters, he might pass authentication because of case mappings and case-insensitivity.

Some internationalization characters should have special capitalization rule so that characters do not convert back to the lower case.

For example, there is the case with SS and ß in German, where ß only exists as a lower case character. When performing "to Upper" against ß, ß will be changed to SS. And if the upper case text is then converted back to lower case, the SS becomes ss and not the original ß.

28.2.14 Oracle Access Manager Authentication Does Not Support Non-ASCII Passwords on Locales Other than UTF8

When the server locale is not UTF-8 and using WebLogic Server embedded LDAP as an identity store, the SSO Authentication page does not support Non-ASCII passwords.

28.2.15 Error Message of Create Agent Shows as Server Locale

When an administrator creates an agent with the same name as one that already exists, the language of the error message displayed is based on the server locale rather than on the browser locale.

28.2.16 Referrals in LDAP Searches

Oracle Access Manager 11g Release 1 (11.1.1) cannot operate directly with LDAP servers returning referrals.

The workaround is to use Oracle Virtual Directory.

28.2.17 Non-ASCII Resources Require OHS To Restart To Make Protection Take Effect

When you add a resource with a non-ASCII name to the protected authentication policy, it will require the 11g OHS Server to restart to make the protection take effect, whereas in adding resources with English characters, protection takes effect in real time without having to restarting the OHS Server.

28.2.18 Non-ASCII Characters on Success/Failure URL Results in Garbled Redirect URL

If an on success or on failure URL configured for an authentication policy contains non-ASCII characters in the URL specified, then the URL specified will be garbled when it is used during a user authentication. This will happen only when the authentication scheme is Basic Authentication and the end user's browser is the Simplified Chinese version of IE8 running on the Chinese version of Windows.

28.2.19 Resource with Non-ASCII Characters Cannot Be Protected by an OSSO Agent

The OSSO Agent cannot protect a resource because it does not encode the entire resource URL to UTF-8 format.

To work around this issue, use the Webgate Agent instead of the SSO Agent.

Webgate is able to convert the entire resource URL to UTF-8 format.

28.2.20 Error in Administration Server Log from Console Logins

If you log in to the Oracle Access Manager Console as an administrator and then log in to the Console as an administrator in a new browser tab, the following error appears in the administration logs:

------------------------------------------------------------
<May 20, 2010 10:12:47 AM PDT> <Error>
<oracle.adfinternal.view.page.editor.utils.ReflectionUtility> <WCS-16178>
<Error instantiating class -
oracle.adfdtinternal.view.faces.portlet.PortletDefinitionDTFactory>
------------------------------------------------------------

The error message does not impact functionality.

28.2.21 Application Domain Subtree in the Navigation Tree Is Not Rendered and Does Not Respond to User Actions

If the Application Domain subtree on the navigation tree does not render or respond to user interface actions over a period of time, it may be the result of multiple refreshes.

To work around these issues, restart the administration server and log in to the Oracle Access Manager Console again.

28.2.22 editWebgateAgent Command Does Not Give An Error If Invalid Value is Entered

The WLST command editWebgateAgent does not give an error when a invalid value is entered for the state field in both online and offline mode. The Oracle Access Manager Console does show the state field value as neither enabled nor disabled, though it is a mandatory field.

28.2.23 WLST Command displayWebgate11gAgent In Offline Mode Displays the Webgate Agent Entry Twice

In the offline mode, the WLST command, displayWebgate11gAgent, displays the 11g Webgate Agent entry in the System Configuration tab twice.

28.2.24 Message Logged at Error Level Instead of at INFO When Servers in Cluster Start

When starting Oracle Access Manager servers in a cluster, the following message is displayed:

<Jun 22, 2010 3:59:41 AM PDT> <Error> <oracle.jps.authorization.provider.pd>
<JPS-10774> <arme can not find state.chk file.>

The correct level of the message is INFO, rather than Error.

28.2.25 Help Is Not Available for WLST Command registeroifdappartner

The Help command is not available for the WLST command, registeroifdappartner.

The online and offline command registers Oracle Identity Federation as a Delegated Authentication Protocol (DAP) Partner.

For information, refer to "registerOIFDAPPartner" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

Syntax

registerOIFDAPPartner(keystoreLocation="/scratch/keystore"
logoutURL="http://<oifhost>:<oifport>/fed/user/sploosso?doneURL=
http://<oamhost>:< oam port>/ngam/server/pages/logout.jsp",
rolloverTime="526")

Parameter Name

Definition

keystoreLocation

Location of the Keystore file. The file generated at the OIF Server. (mandatory)

logoutURL

The OIF Server's logout URL. <mandatory>

rolloverInterval

The Rollover Interval for the keys used to enc/decrypt SASSO Tokens (optional)

Example

The following invocation illustrates use of all parameters.

registerOIFDAPPartner(keystoreLocation="/scratch/keystore",
logoutURL="http://<oifhost>:<oifport>/fed/user/sploosso?doneURL=http://<oamhost>:
<oam port>/ngam/server/pages/logout.jsp", rolloverTime="526")

28.2.26 User Must Click Continue to Advance in Authentication Flow

In a native integration with Oracle Adaptive Access Manager, the resource is protected by an Oracle Access Manager policy that uses the Basic Oracle Adaptive Access Manager authentication scheme.

When a user tries to access a resource, he is presented with the username page.

After he enters his username, he must click Continue before he can proceed to the password page. He is not taken to this page automatically.

The workaround is for the user to click Continue, which might allow him to proceed to the password page.

28.2.27 OCSP-Related Fields are Not Mandatory

In the X509 authentication modules, the following OCSP-related fields are no longer mandatory:

- OCSP Server Alias

- OCSP Responder URL

- OCSP Responder Timeout

If OCSP is enabled

The OCSP-related fields should be filled in by the administrator. If they are not filled, there will not be an error from the Console side.

It is the responsibility of the administrator to provide these values.

If OCSP is not enabled

The OCSP-related fields need not be filled in this case. If there are values for these fields, they will be of no consequence/significance, as OCSP itself is not enabled.

In the default out of the box configuration, the OCSP responder URL is http://ocspresponderhost:port. If you make changes to other fields and leave this as is, you will see a validation error, since this value is still submitted to the back end and at the Console, the layer port should be a numeric field. You can either modify the field, with the port being a numeric field or delete the entire value.

28.2.28 Database Node is Absent in the Console

Under the Data Sources node of the System Configuration tab, Common Configuration section, there is no Databases node in Oracle Access Manager 11g (11.1.1.5).

28.2.29 Online Help Provided Might Not Be Up To Date

Online help is available in the Oracle Access Manager Console, but you should check OTN to ensure you have the latest information.

28.2.30 Oracle Access Manager Audit Report AUTHENTICATIONFROMIPBYUSER Throws a FROM Keyword Not Found Where Expected Error

The Oracle Access Manager audit report AuthenticationFromIPByUser uses an Oracle Database 11.2.0 feature and will not work with older versions of database. The following error is displayed if an older version is used:

ORA-00923: FROM keyword not found where expected

28.2.31 Disabled: Custom Resource Types Cannot be Created

For Oracle Access Manager 11g, creating custom resource types should not be attempted. In the initial release, the buttons to create/edit/delete resource types were available.

With Oracle Access Manager 11g (11.1.1.7) these command buttons are disabled. Oracle provided resource types include:

- HTTP (includes HTTPS)

- TokenServiceRP (Resources for representing Token Service Relying Party)

- wl_authen (Resources for representing WebLogic Authentication schemes)

28.2.32 Use of a Non-ASCII Name for a Webgate Might Impact SSO Redirection Flows

When using the OAM Server with WebGates and when the Webgate ID is registered with a non-ASCII name, the OAM Server may reject that authentication redirect as an invalid request.

To work around this redirection issue, use an ASCII name for the Webgate.

Note:

Resources are protected and error messages do not occur when the administration server and oracle access servers are started on UTF-8 locales.

The redirection issue only occurs on native server locales (Windows and Non-UTF8 Linux server locales)

28.2.33 Authentication Module Lists Non-Primary Identity Stores

In the user interface under the Authentication Module, only the primary identity store should be selected in the list since only primary identity stores can be used for authentication/authorization. Currently, the Oracle Access Manager Console allows you to select identity stores that are not primary.

28.2.34 Unable to Stop and Start OAM Server Through Identity and Access Node in Fusion Middleware Control

The following Oracle Access Manager operations are not supported through using the oam_server node under Identity and Access in Fusion Middleware Control:

- Start up

- Shut down

- View Log Messages

However, these operations are supported per the Oracle Access Manager managed server instance through using the oam_server node (for the specific server) under Application Deployments in Fusion Middleware Control.

28.2.35 AdminServer Won't Start if the Wrong Java Path Given with WebLogic Server Installation

WebLogic Server installation on Windows 64-bit platform can be successful with 32-bit JAVA_HOME (jdk1.6.0_23). On Windows 64-bit platform, the path to 32-bit JAVA_HOME (c:\program files (x86)\java\jdkxxx) is not correctly handled by the startWeblogic.cmd.

- If you launch the install shield with setup.exe, you are asked for the path of the 64-bit JAVA_HOME. If you provide the 32-bit JAVA_HOME (jdk1.6.0_24) path, the install shield is not launched.

- If you execute config.cmd from \Middleware\Oracle_IDM1\common\bin, the path to the 32-bit JAVA_HOME (jdk1.6.0_24) is used. Following successful installation, however, you cannot start AdminServer.

Workaround: Oracle recommends replacing SUN_JAVA_HOME to use the path with the shorter name (c:\progra~2\java\jdkxxxx).

- On Windows, the shorter names can be seen by executing "dir /X".

- Alternatively, you can set Windows command shell variable JAVA_HOME to path with shorter name and execute startWeblogic.cmd within that. For example:
>set JAVA_HOME=c:\progra~2\java\jdkXXX

>startweblogic.cmd

28.2.36 Changing UserIdentityStore1 Type Can Lock Out Administrators

An Identity Store that is designated as the System Store should not be edited to change the store type (from Embedded LDAP to OID, for instance) nor the connection URLs.

If you do need to change the Identity Store that is designated as the System Store should not be edited to change the store type, Oracle recommends that you create a new Identity Store and then edit that registration to mark it as your System Store.

28.2.37 Page Layouts and Locales

The layout of the single sign-on (SSO) Login Page, Impersonation Consent page, Logout Page, Impersonation Error page, and Login Error Page do not change for Arabic and Hebrew locales.

28.2.38 Some Pages Are Not Correctly Localized

The date formats of "Creation Instant" and "Last Access Time" on the Session Management Search page are not correctly localized.

28.2.39 Non-ASCII Query String Issues with Internet Explorer v 7, 8, 9

Due to a limitation with the Internet Explorer browser, resources with Non-ASCII query string when if you directly type or paste the resource URL.

28.2.40 Oracle Virtual Directory with SSL Enabled

With Oracle Virtual Directory as the user identity store, no errors are seen after changing its registration to use the SSL port, checking the SSL box, and testing the connection (Test Connection button). However, authentication fails (even though non-SSL port is fine). The first time Test Connection goes through and any subsequent time it results in Socket Timeout exception from the Oracle Virtual Directory side.

Workaround: Disable NIO for the SSL port as follows:

1. Stop Oracle Virtual Directory. For example:

$ORACLE_INSTANCE/bin/opmnctl stopproc ias-component=ovd1

2. Edit the a LDAP SSL listener section of listener.os_xml to add <useNIO>false</useNIO>, as follows:

$ORACLE_INSTANCE/config/OVD/ovd1/listener.os_xml

<ldap version="20" id="LDAP SSL Endpoint">
<port>7501</port>
<host>0.0.0.0</host>
.........
.........
<tcpNoDelay>true</tcpNoDelay>
<readTimeout>180000</readTimeout>
</socketOptions>
<useNIO>false</useNIO>
</ldap>

3. Save the file.

4. Test the connection several times to confirm this is working.

28.2.41 Query String Not Properly Encoded

There is no encoding on the query string from Webgate when % is not followed by a sequence of characters that form a valid URL escape sequence. In this case, Oracle Access Manager etains % as % in the decoded string and the following error occurs:

No message for The Access Server has returned a status that is unknown to the
Access Gate .Contact your website administrator to remedy this problem.

Workaround:

11g Webgate: To specify the '%' character in a query string, you must specify '%25' instead of '%'.

10g Webgate: The 11g Webgate workaround applies to only the anonymous scheme. For other authentication schemes, there is currently no workaround.

28.3 Configuration Issues and Workarounds

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

- Section 28.3.1, "For mod-osso Value for RedirectMethod Should be "POST""

- Section 28.3.2, "User Wrongly Directed to the Self-User Login after Logging Out of the Oracle Identity Manager Administration Console"

- Section 28.3.3, "11g Webgate Fails to Install with Compact Configuration."

- Section 28.3.4, "Auditing Does Not Capture the Information Related to Authentication Failures if a Resource is Protected Using Basic Authentication Scheme"

- Section 28.3.5, "Unable to Access Partner Information on the Production Environment"

- Section 28.3.6, "Incompatible Msvcirt.dll Files"

- Section 28.3.7, "IPv6 Support"

- Section 28.3.8, "What to Avoid or Note in Oracle Access Manager Configuration"

- Section 28.3.9, "Install Guides Do Not Include Centralized Logout Configuration Steps"

- Section 28.3.10, "NULL Pointer Exception Shown in Administration Server Console During Upgrade"

- Section 28.3.11, "Using Access SDK Version 10.1.4.3.0 with Oracle Access Manager 11g Servers"

- Section 28.3.12, "Finding and Deleting Sessions Using the Console"

- Section 28.3.13, "Non-ASCII Users with Resource Protected by Kerberos Authentication Scheme"

28.3.1 For mod-osso Value for RedirectMethod Should be "POST"

For Webgate to support long URLs, the following code sample was added under oam-config.xml:

<Setting Name="AgentConfig" Type="htf:map">
<Setting Name="OSSO" Type="htf:map">
<Setting Name="RedirectMethod"Type="xsd:string">GET</Setting>
<Setting Name="Delimiter" Type="xsd:string">AND</Setting>
</Setting>

For mod-osso, the value for RedirectMethod should be POST, however, the values shipped out of the box is GET. Follow these steps to perform the modification, as this change needs to be performed manually and there is no user interface or WLST commands available to do so.

1. Stop the Oracle Access Manager Console and managed servers.

2. Enter cd DOMAIN_HOME/config/fmwconfig

3. Enter vi oam-config.xml

4. Go to the following line in oam-config.xml:

<Setting Name="AgentConfig" Type="htf:map">
<Setting Name="OSSO" Type="htf:map">
<Setting Name="RedirectMethod"Type="xsd:string">GET</Setting>

Modify GET to POST as follows:

<Setting Name="RedirectMethod"Type="xsd:string">POST</Setting>

5. Save the changes and start the AdminServer and managed servers.

28.3.2 User Wrongly Directed to the Self-User Login after Logging Out of the Oracle Identity Manager Administration Console

The user is directed to the self-user login after logging out of the Oracle Identity Manager Administration Console.

To be redirected correctly, the logout must work properly.

The workaround for logout with 10g Webgate is to:

1. Copy logout.html (for example, from Oracle_IDM1/oam/server/oamsso/logout.html) to webgate_install_dir/oamsso.

2. Update logout URL in the file to http://oam_server:oam_server/ngam/server/logout.

3. If redirection to specific page has to occur after logout, change the logout URL to http://oam_server:oam_server/ngam/server/logout?doneURL=http://host:port/specifipage.html.

28.3.3 11g Webgate Fails to Install with Compact Configuration

A compact configuration is an installation with all identity management components on a machine with limited hardware capacity.

On trying to install the 11g Webgate with compact configuration, the following error occurs during the configure step:

Configuring WebGate...
There is an error. Please try again.
Preparing to connect to Access Server. Please wait.
Client authentication failed, please verify your WebGate ID.
cp: cannot stat
`$ORACLE_HOME/ohs/conf/aaa_key.pem':
No such file or directory
cp: cannot stat
`$ORACLE_HOME/ohs/conf/aaa_cert.pem':
No such file or directory
cp: cannot stat
`$ORACLE_HOME/ohs/conf/aaa_chain.pem':

The error occurs because the following entries were not initialized in oam-config.xml during the installation:

<Setting Name="oamproxy" Type="htf:map">
<Setting Name="sslGlobalPassphrase" Type="xsd:string">changeit</Setting>
<Setting Name="SharedSecret" Type="xsd:string">1234567812345678</Setting>
</Setting>

To initialize oam-config.xml properly:

1. Delete the OAM entry from CSF repository by performing the following steps:

1. Start the WebLogic Scripting Tool:
oracle_common/oracle_common/common/bin/wlst.sh

2. In the WLST shell, enter the command to connect to the domain and then enter the requested information.
A sample is given below.

wls:/offline> connect ()
Please enter your username [weblogic] :
Please enter your password [welcome1] :
Please enter your server URL [t3://localhost:7001] :
Connecting to t3://localhost:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'imdomain86'.

3. Change to domainRuntime.
A sample is given below.

wls:/imdomain86/serverConfig> domainRuntime ()
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.

4. Check whether an entry exists in the CSF repository with the map name as OAM and key as jks.
A sample is given below.

wls:/imdomain86/domainRuntime> listCred(map="OAM_STORE",key="jks") {map=OAM_STORE, key=jks}
Already in Domain Runtime Tree
.
[Name : jks, Description : null, expiry Date : null]
PASSWORD:1qaldrk3eoulhlcmfcqasufgj2
.

5. Delete the OAM map entry from the CSF repository.

wls:/imdomain86/domainRuntime> deleteCred(map="OAM_STORE",key="jks")
{map=OAM_STORE, key=jks}
Already in Domain Runtime Tree
.

6. Exit from wlst shell.
A sample is given below.

wls:/imdomain86/domainRuntime> exit ()
.
.
.

2. Go to DOMAIN_HOME/config/fmwconfig and delete the file .oamkeystore.
A sample [on linux] is given below.

[aime@pdrac09-5 fmwconfig]$ rm .oamkeystore
.

3. Stop the Managed Server and Admin Server.

4. Start the AdminServer.

5. Verify oam-config.xml.

6. Start Managed Server.

Steps to verify oam-config.xml:

1. Go to DOMAIN_HOME/config/fmwconfig/oam-config.xml.

2. Verify that all the WebLogic Server server instances are configured under DeployedComponent > Server > NGAMServer > Instance

3. Verify that the OAM Managed Server protocol, host and port are available at:
DeployedComponent > Server > NGAMServer > Profile > OAMServerProfile > OAMSERVER

4. Verify that the SSO CipherKey is generated and available at:
DeployedComponent > Server > NGAMServer > Profile > ssoengine > CipherKey

5. Verify that the oamproxy entries for SharedSecret and sslGlobalPassphrase is generated and available at:
DeployedComponent > Server > NGAMServer > Profile > oamproxy

SharedSecret should have a value different from 1234567812345678 and sslGlobalPassphrase different from changeit.

28.3.4 Auditing Does Not Capture the Information Related to Authentication Failures if a Resource is Protected Using Basic Authentication Scheme

Although a resource can be protected using the BASIC scheme, the WebLogic server has a feature by which it first authenticates the user and then sends it to the server.

If you add the following flag under <security-configuration> in config.xml and restart the server, you will be able to bypass WebLogic server's authentication <enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>. Once the credentials are submitted back to the OAM Server, it will be audited.

The WebLogic Server Administration Console does not display or log the enforce-valid-basic-auth-credentials setting. However, you can use WLST to check the value in a running server. You must modify this value by setting this in config.xml.

To do so, refer to "Developing Secure Web Applications" at:

http://download.oracle.com/docs/cd/E13222_01/wls/docs103/security/thin_client.html#wp1037337

28.3.5 Unable to Access Partner Information on the Production Environment

After test-to-production migration, the following steps must be performed:

1. Ensure that the production OAM Server(s) are down when the policy is imported from the test system.

2. Log in to the Oracle Access Manager Console and modify the primary /secondary server list for all agents in the production system (including the IAMSuiteAgent).

3. Copy the generated artifacts for Webgate generated for each of the Webgate agents (excluding IAMSuiteAgent).

4. Start the production OAM managed server(s).

5. Restart all the Webgate agents' OHS.

In migrating partner information from a test environment to a production one, you will not be able to access partner information if

- The migratePartnersToProd command was used. It is outdated. The following set of commands should be used instead:

- exportPartners- This command is used to export the partners from the test environment. It needs to be run from the OAM Server, from where the partners needs to be exported. This command takes the path to the temporary oam-partners file as a parameter.

exportPartners(pathTempOAMPartnerFile=', <pathTempOAMPartnerFile>')

- importPartners- This command is used to import the partners to the production environment. It needs to be run from the OAM Server to which the partners needs to be imported. This command takes the path to the temporary oam-partners file as a parameter.

importPartners(pathTempOAMPartnerFile=', <pathTempOAMPartnerFile>')

- The agent profiles were not edited after the migration to match the production system.
A Webgate Agent might be configured with a list of primary/secondary server hosts and nap ports available in the test system. The production system may not contain server instances with the same hosts and ports as configured in the test system. Since the SysConfig Agent Profile user interface obtains the server name by picking up the servers matching the host and port details of the primary/secondary server list, the server names may not be displayed in the user interface after migration. Since the primary/secondary server lists could be a subset of the list of available server instances in the production system, the agent profiles need to be edited after migration to match the production system.

28.3.6 Incompatible Msvcirt.dll Files

When you install the Oracle Access Manager 10g Webgate, do not replace the current version of msvcirt.dll with a newer version when prompted. If you do so, there may be incompatibility issues. Later, when you try to install OSSO 10g (10.1.4.3), the opmn.exe command might fail to start and the OracleCSService might time out because the required .dll file is missing.

28.3.7 IPv6 Support

The supported topology for Oracle Access Manager 11g is shown below.

Supported Topology

- WebGate10g or Webgate 11g and protected applications on IPv4 (Internet Protocol Version 4) protocol host

- OHS (Oracle HTTP Server) reverse proxy on dual-stack host

- Client on IPv6 (Internet Protocol Version 6) protocol host

Dual-stack is the presence of two Internet Protocol software implementations in an operating system, one for IPv4 and another for IPv6.

The IPv6 client can access Webgate (10g or 11g) through the reverse proxy on IPv4/IPv6 dual-stack.

28.3.8 What to Avoid or Note in Oracle Access Manager Configuration

This section contains scenarios and items to note in Oracle Access Manager Configuration

28.3.8.1 Unsupported Operations for WLST Scripts

WLST scripts for Oracle Access Manager 10g and Oracle Access Manager 11g WebGates do not support changing Agent security modes.

28.3.8.2 Unsupported Operations for Oracle Access Manager Console and WLST

Unsupported operations for the Oracle Access Manager Console and WLST are described in the following subsections.

28.3.8.2.1

OAM Server

Use Case: Concurrent Deletion and Updating

Description

1. Open an OAM Server instance in edit mode in Browser 1.

2. Using the Oracle Access Manager Console in another browser (Browser 2) or using a WLST script, delete this server instance.

3. Return to Browser 1 where the server instance is opened in edit mode.

4. In Browser 1, click the Apply button.

Current Behavior

The Oracle Access Manager Console displays the message, "Server instance server_name might be in use, are you sure you want to edit it?" along with the confirmation that the update succeeded.

On clicking Yes, the following error message pops up, as expected, and the OAM Server instance page is closed (correct behavior):

"Error while reading your_server-name OAM Server Instance Configuration."

However, the navigation tree node might continue to display the OAM Server instance until you click the Refresh command button for the navigation tree.

Use Case: Two OAM Server Instances with Same Host Cannot have the Same Proxy Port.

Description

For this use case, there are two instances of the OAM Server: oam_server1 and oam_server2.

1. Open oam_server1 in edit mode and specify a host and OAM proxy port.

2. Now open oam_server2 in edit mode and specify the same host and proxy port as oam_server1.

The changes are saved without any error message.

Current Behavior

The Oracle Access Manager Console does not display any error and allows the update.

The behavior is incorrect.

Use Case: Log Statements Detailing the Server Instance Creation, Update and Delete are not Present on the Oracle Access Manager Console

Description

If you create, edit, or delete an OAM Server instance from the Oracle Access Manager Console, the log statements corresponding to create, edit and delete are not displayed by the Console.

28.3.8.2.2

LDAP Authentication Module:

Use Case: Concurrent Deletion/Creation of User Identity Store does not Reflect in the List of Identity Stores in the LDAP Authentication Module Create and Edit

Description

1. Open create/ edit for the LDAP authentication module.
A list displays the identity stores present in the system.

2. Now create a user identity store using another tab.

3. Return to the create/edit tab for the LDAP authentication module and check the list for user identity stores.

Current Behavior

The Oracle Access Manager Console displays the error message, as expected, and closes the Authentication Module page (correct behavior):

"Error while reading module-name Authentication Module Configuration."

However, the navigation tree node might continue to display the Authentication Module node until you click the Refresh command button for the navigation tree.

28.3.8.2.3

LDAP, Kerberos and X509 Authentication Module

Use Case: Concurrent deletion and updating

Description

1. Open an LDAP/Kerberos/X509 authentication module in edit mode in Oracle Access Manager Console in Browser 1.

2. Using Oracle Access Manager Console in another browser (Browser 2) or using a WLST script, delete this authentication module.

3. Now return to Browser 1 where the authentication module is opened in edit mode.

4. Click the Apply button.

Current Behavior

The Oracle Access Manager Console updates this authentication module configuration and writes it to back end.

The behavior is incorrect.

Use Case: Log Statements Detailing the Server Instance Creation, Update and Delete are Not present on Oracle Access Manager Console side.

Description

When you create, edit or delete an authentication module from Oracle Access Manager Console, the log statements corresponding to create, edit and delete are not written by the Console.

28.3.8.2.4

OAM 11G Webgate

Use Case: Concurrent Deletion and Update

Description

1. Open an OAM 11g Webgate instance in edit mode in Oracle Access Manager Console in Browser 1.

2. Using the Oracle Access Manager Console in another browser (Browser 2) or using a WLST script, delete this OAM 11g Webgate.

3. Now return to the Browser1 where the server instance is opened in edit mode.

4. Click on the Apply button.

Current Behavior

The Oracle Access Manager Console for edit OAM11g Webgate does not change and the tab does not close.

A OAM11g Webgate configuration not found error dialog is displayed by the Oracle Access Manager Console.

However, the navigation tree is blank and attempts to perform any operation results in a javax.faces.model.NoRowAvailableException".

The behavior is incorrect.

28.3.8.2.5

OSSO Agent

Use Case: Concurrent Deletion and Update

Description

1. Open an OSSO Agent instance in edit mode in the Oracle Access Manager Console in Browser 1.

2. Using the Oracle Access Manager Console in another browser (Browser 2) or using a WLST script, delete this OSSO Agent.

3. Now return to the Browser 1 where the OSSO Agent instance is opened in edit mode.

4. Click on Apply button.

Current Behavior

Editing the OSSO Agent in the Oracle Access Manager Console results in a null pointer exception.

The behavior is incorrect.

28.3.9 Install Guides Do Not Include Centralized Logout Configuration Steps

Single-Sign On is enabled after Oracle Access Manager is installed; to complete configuration of Single-Sign On out of the box, centralized log out must be configured post-install. Configure centralized log out by following direction from these sections:

- Configuring Centralized Logout for ADF-Coded Applications with Oracle Access Manager 11g
In order for the ADF logout to work correctly, Single Sign-On Server Patch 9824531 is required. Install this patch, as described in the readme file that is included in the patch.

- Configuring Centralized Logout for the IDM Domain Agent (in the patch set this is now the IAMSuiteAgent)

28.3.10 NULL Pointer Exception Shown in Administration Server Console During Upgrade

A NULL pointer exception occurs because of the configuration events trigger when the identity store shuts down. The upgrade is successful, however, and error messages are seen in administration server console. There is no loss of service.

If the NULL pointer is seen during upgrade, there is no loss of service, you can ignore the error.

If the NULL pointer is seen during WLST command execution, you must restart the administration server.

28.3.11 Using Access SDK Version 10.1.4.3.0 with Oracle Access Manager 11g Servers

In general, the Sun Microsystems JDK 1.4.x compiler is the JDK version used with the Java interfaces of Access SDK Version 10.1.4.3.0.

As an exception, the Java interfaces of the 64-bit Access SDK Version 10.1.4.3.0, specifically for the Linux operating system platform, requires the use of Sun Microsystems JDK 1.5.x compiler.

The new Session Management Engine capability within Oracle Access Manager 11g will create a session for every Access SDK version 10.1.4.3.0 call for authentication.

This may cause issues for customers that use Access SDK to programmatically authenticate an automated process. The issue is the number of sessions in the system that is generated within Access SDK will increase dramatically and cause high memory consumption.

28.3.12 Finding and Deleting Sessions Using the Console

When session search criteria is generic (using just a wild card (*), for example), there is a limitation on deleting a session from a large list of sessions.

Oracle recommends that your session search criteria is fine-grained enough to obtain a relatively small set of results (ideally 20 or less).

28.3.13 Non-ASCII Users with Resource Protected by Kerberos Authentication Scheme

Non-ASCII users fail to access a resource protected by a Kerberos authentication scheme using WNA as a challenge method.

The exception occurs when trying to get user details to populate the subject with the user DN and GUID attributes.

28.4 Oracle Security Token Service Issues and Workarounds

This section provides the following topics:

- Section 28.4.1, "No Warnings Given If Required Details are Omitted"

- Section 28.4.2, "New Requester Pages, Internet Explorer v7, and Japanese Locale"

- Section 28.4.3, "Delete Button Not Disabled When Tables Have No Rows"

- Section 28.4.4, "Copying an Issuance Template Does Not Copy All Child Elements"

- Section 28.4.5, "Apply and Revert Buttons are Enabled"

- Section 28.4.6, "Only Generic Fault Errors Written to Oracle WSM Agent Logs"

- Section 28.4.7, "Server and Client Key Tab Files Must be the Same Version"

- Section 28.4.8, "Default Partner Profile Required for WS-Security"

- Section 28.4.9, "SAML Token Issued When NameID is Not Found"

28.4.1 No Warnings Given If Required Details are Omitted

On the Token Mapping page of a new Validation Template with the following characteristics:

- WS-Security

- Token Type SAML 1.1

- Default Partner Profile: requester profile

No warnings are given:

- If you check the box to Enable Attribute Based User Mapping if you leave empty the required User Attributes field
A new row is not saved if the User Attribute field is empty. However, it is saved if both fields are filled. Removing the value of the User Attribute field in a user-added row causes the row to be deleted when you Apply changes

- If you attempt to delete built-in Name Identifier Mapping rows
Built-in Name Identifier Mapping rows cannot be deleted.

28.4.2 New Requester Pages, Internet Explorer v7, and Japanese Locale

When using the Japanese Locale with Internet Explorer v7, the title "New Requester" is not displayed in one line on the page. The Partner, Name, Partner Type, and Partner Profile fields might wrap on the page.

This can occur whether you are creating or modifying the Partner (Requester, Relying Party, and Issuing Authority).

28.4.3 Delete Button Not Disabled When Tables Have No Rows

The Delete button is enabled even though there are no rows to be deleted in the following tables:

- The Attribute Name Mapping table (Token and Attributes page for Partner Profiles (Requester, Relying Party, Issuing Authority Profiles).

- The Value Mapping table in Issuing Authority Partner Profiles

When there are no rows in a table, the Delete button should be disabled by default.

28.4.4 Copying an Issuance Template Does Not Copy All Child Elements

Issuance Template Copy Like function does not copy nested tables (attribute mapping and filtering tables, and the custom token attribute table).

Workaround: Navigate to the desired Issuance Template, click the name in the navigation tree and click the Copy Like button. Manually enter missing information from the original: Attribute Mappings or custom attribute tables.

28.4.5 Apply and Revert Buttons are Enabled

The Apply and Revert buttons are enabled on Oracle Security Token Service pages even if there are no changes to apply or saved changes to revert to the previous version.

28.4.6 Only Generic Fault Errors Written to Oracle WSM Agent Logs

No content is written logs for the Oracle WSM agent errors. There is only a generic fault error.

Workaround: Enable message logging for the Oracle WSM agent on the host OAM Server.

1. Locate the logging.xml file in $DOMAIN/config/fmwconfig/server/oam_server1/logging.xml file.

2. Change the WSM block of the logging.xml file, to:

<logger name="oracle.wsm" level="TRACE:32" useParentHandlers="false">
<handler name="odl-handler"/>
</logger>

<logger name="oracle.wsm.msg.logging" level="TRACE:32"
useParentHandlers="false">
<handler name="owsm-message-handler"/>
<handler name="wls-domain"/>
</logger>

3. OSTS Policies: When Oracle Security Token Service policies are used (instead of Oracle-provided WSM policies) perform the following steps:

1. Locate: Oracle_IDM1/oam/server/policy

2. Unjar sts-policies.jar.

3. Change all the polices to set Enforced to true: META-INF/polices/sts.

<oralgp:Logging orawsp:name="Log Message1" orawsp:Silent="true
orawsp:Enforced="true" orawsp:category="security/logging">
<oralgp:msg-log>
<oralgp:request>all</oralgp:request>
<oralgp:response>all</oralgp:response>
<oralgp:fault>all</oralgp:fault>
</oralgp:msg-log>
</oralgp:Logging>

4. Re-jar the updated sts-policies.jar.

5. Restart the AdminServer and managed servers.

28.4.7 Server and Client Key Tab Files Must be the Same Version

An exception to authenticate the Kerberos token occurs if WebLogic 10.3.5 is configured with Sun JDK6 greater than u18.

When using the Kerberos token as an authentication token requesting the security token from Oracle Security Token Service:

- The keytab file configured in the validation template should always be the latest version from the KDC server

- The KVNO should always be the latest that is available on the server:

28.4.8 Default Partner Profile Required for WS-Security

The Oracle Access Manager Access Administration Guide states "When you toggle the Token Protocol from WS-Trust to WS-Security, options in the Token Type list do not change. However, the required "Default Partner Profile" list appears from which you must choose one profile for WS-Security."

Correction: When you toggle the Token Protocol from WS-Trust to WS-Security a required field "Default Partner Profile" will appear. You must choose a value for this field. If you again toggle back to WS-Trust without choosing a value for this field The options in the Token Type list are not updated correctly to have the WS-Trust Token Type values.

28.4.9 SAML Token Issued When NameID is Not Found

Rather than returning an error response, an assertion issued with an empty NameIdentifier field can be issued even when the NameIdentifier user attribute has a null or empty value. For example:

<saml:NameIdentifier
Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress"/>

Workaround: The "Name Identifier User Attribute" Field in the Issuance Template requires a value for the Userstore.

28.5 Integration and Inter-operability Issues and Workarounds

This section provides the following topics:

- Section 28.5.1, "WNA Authentication Does Not Function on Windows 2008"

- Section 28.5.2, "JVM Plug-in Ignores Cookies Marked 'httponly'"

28.5.1 WNA Authentication Does Not Function on Windows 2008

The default Kerberos encryption supported by Windows 2008 Server and Windows 2007 machines are "AES256-CTS-HMAC-SHA1-96", "AES128-CTS-HMAC-SHA1-96" and "RC4-HMAC".

If the clients are configured to use DES only encryption, users will not be able to access protected resources with Kerberos authentication. The error message, An incorrect username and password was specified might be displayed.

Because the initial Kerberos tokens are not present, the browser sends NTLM tokens, which the OAM Server does not recognize; therefore, the user authentication fails.

The workaround is to enable the encryption mechanisms, and follow the procedure mentioned in:

http://technet.microsoft.com/en-us/library/dd560670%28WS.10%29.aspx

28.5.2 JVM Plug-in Ignores Cookies Marked 'httponly'

Cookies set with the httponly flag are not available to Browser Side Scripts and Java Applets. The JVM plugin ignores cookies marked 'httponly.'

To resolve the issue

1. In mod_sso.conf, disable the OssoHTTPOnly off parameter.

2. Add the required OSSO cookies to the list of possible applet parameters to pass for authentication.

28.6 Oracle Access Manager with Impersonation Workarounds

This section provides the following topics:

- Section 28.6.1, "Impersonation Can Fail on Internet Explorer v 7, 8, 9"

- Section 28.6.2, "With Oracle Access Manager 11g ORA_FUSION_PREFS Cookie Domain is Three Dots"

28.6.1 Impersonation Can Fail on Internet Explorer v 7, 8, 9

Due to a limitation with the Internet Explorer browser, Impersonation can fail to go to the Consent page when the Impersonatee's userid contains Non-ASCII characters.

Impersonation goes instead to the failure_url if you directly type or paste the starting impersonation URL in the browser.

28.6.2 With Oracle Access Manager 11g ORA_FUSION_PREFS Cookie Domain is Three Dots

With Oracle Access Manager 10g the ORA_FUSION_PREFS cookie domain used the following form (2 dots):

10g Form .example.com

However, Oracle Access Manager 11g localized login accepts only the following format for the ORA_FUSION_PREFS cookie domain (3 dots):

11g Form .us.example.com

For example, if the host name is ruby.us.example.com, Oracle Access Manager 11g creates a cookie with the domain name .us.example.com.

However, the application session creates a cookie with the domain name .example.com, which causes inter-operability failure between Fusion Middleware and the application session using this cookie.

Workaround: Update the FACookieDomain parameter to correspond to 11g requirements, and increment the Version xsd:integer in the oam-config.xml, as shown in this example:

1. Back up DOMAIN_HOME/config/fmwconfig/oam-config.xml.

2. Open the file for editing and pay close attention to your changes.

3. Set FACookieDomain to your domain (with 3 dot separators):

<Setting Name="FAAppsConfig" Type="htf:map">
<Setting Name="FACookieDomain" Type="xsd:string">.us.example.com</Setting>
<Setting Name="FAAuthnLevel" Type="xsd:integer">2</Setting>
<Setting Name="consentPage" Type="xsd:string">/oam/pages/impconsent.jsp
</Setting>
</Setting>

4. Configuration Version: Increment the Version xsd:integer as shown in the next to last line of this example (existing value (26, here) + 1):
Example:

<Setting Name="Version" Type="xsd:integer">
<Setting xmlns="http://www.w3.org/2001/XMLSchema"
Name="NGAMConfiguration" Type="htf:map:>
<Setting Name="ProductRelease" Type="xsd:string">11.1.1.3</Setting>
<Setting Name="Version" Type="xsd:integer">26</Setting>
</Setting>

5. Save oam-config.xml.

28.7 Documentation Errata

This section provides documentation errata for the following guides:

- Section 28.7.1, "Oracle Fusion Middleware Administrator's Guide for Oracle Access Manager with Oracle Security Token Service"

- Section 28.7.2, "Oracle Fusion Middleware Developer's Guide for Oracle Access Manager and Oracle Security Token Service"

- Section 28.7.3, "Oracle Fusion Middleware Integration Guide for Oracle Access Manager"

28.7.1 Oracle Fusion Middleware Administrator's Guide for Oracle Access Manager with Oracle Security Token Service

There is no documentation errata for this guide.

28.7.2 Oracle Fusion Middleware Developer's Guide for Oracle Access Manager and Oracle Security Token Service

There is no documentation errata for this guide.

28.7.3 Oracle Fusion Middleware Integration Guide for Oracle Access Manager

This section contains documentation errata applicable to the Oracle Fusion Middleware Integration Guide for Oracle Access Manager, part number E15740-04 only.

The following documentation errata are included for this guide:

- Section 28.7.3.1, "Updates to Prerequisites for OAM-OIM Integration"

- Section 28.7.3.2, "Properties for configOIM Command"

- Section 28.7.3.3, "Updated Example for Integrating OIF/SP"

28.7.3.1 Updates to Prerequisites for OAM-OIM Integration

In the Oracle Fusion Middleware Integration Guide for Oracle Access Manager, part number E15740-04, Chapter 5 Integrating Oracle Access Manager and Oracle Identity Manager, Section 5.2 Prerequisites, Step 8a instructs you to prepare to configure LDAP synchronization (LDAP sync) in the domain where Oracle Identity Manager runs.

Step 8a directs you to Section 14.8.5 Completing the Prerequisites for Enabling LDAP Synchronization of the Oracle Fusion Middleware Installation Guide for Oracle Identity Management, Part Number E12002-09. This may be confusing as some steps of that section (such as creating the OIM user and group) are already complete.

Instead, Step 8a should direct you to Section 14.8.5.2 Creating Adapters in Oracle Virtual Directory of the Oracle Fusion Middleware Installation Guide for Oracle Identity Management, so that you can configure the Oracle Virtual Directory adapter for Oracle Internet Directory.

Also in Section 5.2 Prerequisites, Step 8c instructs you to run a configuration wizard to configure LDAP synchronization (LDAP sync) in the domain where Oracle Identity Manager runs. This step does not work if Oracle Identity Manager was installed without LDAP synchronization enabled.

Instead, Step 8c should direct you to Section 10.1 Enabling Postinstallation LDAP Synchronization of the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Manager, Part Number E14308-08, for the correct procedure to enable LDAP synchronization post-installation.

28.7.3.2 Properties for configOIM Command

Section 5.4, Perform Integration Tasks in Oracle Identity Manager, does not provide definitions of all the properties to be specified in the properties file when executing the -configOIM command in Step 3.

Use the following property definitions to assist you in configuring the properties file of the procedure:

Table 28-1 Properties for configOIM Command

Property

Definition

LOGINURI

URI required by OPSS. Default value is /${app.context}/adfAuthentication

LOGOUTURI

URI required by OPSS. Default value is /oamsso/logout.html

AUTOLOGINURI

URI required by OPSS. Default value is /obrar.cgi

ACCESS_SERVER_HOST

Oracle Access Manager hostname.

ACCESS_SERVER_PORT

Oracle Access Manager NAP port.

ACCESS_GATE_ID

The OAM access gate ID to which OIM needs to communicate.

OIM_MANAGED_SERVER_NAME

The name of the Oracle Identity Manager managed server. If clustered, any of the managed servers can be specified.

COOKIE_DOMAIN

Web domain on which the OIM application resides. Specify the domain in the format .cc.example.com.

COOKIE_EXPIRY_INTERVAL

Cookie expiration period. Set to -1.

OAM_TRANSFER_MODE

The security model in which the Access Servers function. Choices are OPEN or SIMPLE.

WEBGATE_TYPE

The type of WebGate agent you want to create. Set to javaWebgate if using a domain agent; set it to ohsWebgate10g if using a 10g WebGate.

SSO_ENABLED_FLAG

Flag to determine if SSO should be enabled. Set to true or false.

IDSTORE_PORT

The port number for the identity store (corresponding to the IDSTORE_DIRECTORYTYPE).

IDSTORE_HOST

The hostname of the identity store (corresponding to the IDSTORE_DIRECTORYTYPE).

IDSTORE_DIRECTORYTYPE

The type of directory for which the authenticator must be created. OID for Oracle Internet Directory; OVD for all other directories.

IDSTORE_ADMIN_USER

User with admin privileges. Note that the entry must contain the complete LDAP DN of the user.

IDSTORE_USERSEARCHBASE

The location in the directory where users are stored.

IDSTORE_GROUPSEARCHBASE

The location in the directory where groups are stored

MDS_DB_URL

The URL for the MDS database.

MDS_DB_SCHEMA_USERNAME

The schema name for the MDS database.

WLSHOST

The WebLogic server hostname.

WLSPORT

The WebLogic server port number.

WLSADMIN

The WebLogic server administrator.

DOMAIN_NAME

The Oracle Identity Manager domain name.

DOMAIN_LOCATION

The Oracle Identity Manager domain location.

28.7.3.3 Updated Example for Integrating OIF/SP

In Section 4.3 Integrate Oracle Identity Federation in SP Mode, under sub-section 4.3.2 Delegate Authentication to Oracle Identity Federation, Step 7c contains an incorrect example of how to update the OIFDAP partner block in the oam-config.xml configuration file. The correct example should be:

registerOIFDAPPartner(keystoreLocation="/scratch/keystore",
logoutURL="http(s)://oifhost:oifport/fed/user/splooam11g?doneURL=
http(s)://oamhost:oamport/oam/server/pages/logout.jsp", rolloverTime="500")

Note that oifhost and oifport refer to the Oracle Identity Federation server host and port respectively; and oamhost and oamport refer to the Oracle Access Manager server host and port respectively.

29 Oracle Entitlements Server

This chapter describes issues associated with Oracle Entitlements Server. It includes the following topics:

- Section 29.1, "General Issues and Workarounds"

- Section 29.2, "Configuration Issues and Workarounds"

- Section 29.3, "Documentation Errata"

29.1 General Issues and Workarounds

This section describes general issues and workarounds. It includes the following topic:

- Using Backslash on Oracle Internet Directory Policy Store

- Performance Tuning the Oracle Database Policy Store

- Action Bar Disappears When Using Internet Explorer 7

- Re-created Application May Not Be Distributed in Controlled Mode

- Enterprise Manager Doesn't Pick Up Newly Added Audit Events

- Attributes Passed to Authorization Request Are Treated as Case Sensitive

- Audit Schema Definitions are Incomplete

- Java Security Module on IPv6 Client Not Supported on Windows

- Validating Attribute Names in Custom Functions

29.1.1 Using Backslash on Oracle Internet Directory Policy Store

When a backslash (\) is used in a policy object name and the backslash is followed by either a pound sign (#) or two hex characters ([a-fA-f_0-9][a-fA-f_0-9]), searches for the object may not work as expected. The issue has been observed when one of either a Resource Type name or a Resource name and action association has such a value causing the query of permission sets by Resource Type, Resource name or action to fail.

WORKAROUND:

Avoid using these values in policy object names.

29.1.2 Performance Tuning the Oracle Database Policy Store

The Oracle dbms_stats package can be used to improve data migration performance on an Oracle database policy store. The exact SQL command to be executed is:

*EXEC DBMS_STATS.gather_schema_stats
('DEV_OPSS',DBMS_STATS.AUTO_SAMPLE_SIZE,no_invalidate=>FALSE);*

where DEV_OPSS is the schema owner being used for the database policy store. You can use the other two parameters as illustrated.

WORKAROUND:

You can run this DBMS_STATS call periodically using either of the options below:

- Use DBMS_JOB.

1. Copy and paste the following code to a SQL script.
In this example, the job will be executed every 10 minutes.

variable jobno number;
BEGIN
DBMS_JOB.submit
(job => :jobno,
what =>
'DBMS_STATS.gather_schema_stats(''DEV_OPSS'',DBMS_STATS.AUTO_SAMPLE_SIZE,
no_invalidate=>FALSE);',
interval => 'SYSDATE+(10/24/60)');
COMMIT;
END;
/
#end of sql script

2. Login to sqlplus as the schema owner; for example, 'DEV_OPSS' not sys_user.

3. Run the SQL script.
To find the job ID from the script you ran, execute the following:

sqlplus '/as sysdba'
SELECT job FROM dba_jobs WHERE schema_user = 'DEV_OPSS' AND what =
'DBMS_STATS.gather_schema_stats(''DEV_OPSS'',DBMS_STATS.AUTO_SAMPLE_SIZE,
no_invalidate=>FALSE);';

To remove the job, login to sqlplus as the schema owner (for example, 'DEV_OPSS' not sys_user) and run the following SQL command:

EXEC DBMS_JOB.remove(27);

- Use cron job or shell script to execute the SQL command.

# run dbms_stats periodically
./runopssstats.sh
# runopssstats.sh content is below:
# In this example, we will execute the command in every 10 minutes
#!/bin/sh

i=1
while [ $i -le 1000 ]
do
echo $i
sqlplus dev_opss/welcome1@inst1 @opssstats.sql
sleep 600
i=`expr $i + 1`
done
# end of sh

# opssstats.sql
EXEC DBMS_STATS.gather_schema_stats('DEV_OPSS',
DBMS_STATS.AUTO_SAMPLE_SIZE,no_invalidate=>FALSE);
QUIT;
# end of sql

29.1.3 Action Bar Disappears When Using Internet Explorer 7

If you are using Internet Explorer 7 and select a role or user from an Administrator Role under System Configuration -> System Administrators, the action bar disappears thus, External Role Mappings and External User Mappings can not be deleted.

WORKAROUND:

This issue is specific to Internet Explorer 7. Use Firefox 3.

29.1.4 Re-created Application May Not Be Distributed in Controlled Mode

In some cases, when the PDP Service is running in controlled mode, if one Application object is deleted from the policy store and re-created using the same name, the change may not be distributed to the PDP Service. This is because the Application in the local cache has a higher version than the one in the policy store.

WORKAROUND:

Remove the local cache files for the PDP service and restart the PDP Service instance. The oracle.security.jps.runtime.pd.client.localpolicy.work_folder configuration parameter defines the path to the cache. The default value is <SM_INSTANCE>/config/work/.

29.1.5 Enterprise Manager Doesn't Pick Up Newly Added Audit Events

component_events.xml is the audit event definition file used by configuration tools (like Enterprise Manager and WebLogic Scripting Tool) and by the audit runtime and database loader. You need to modify the component_events.xml file to insure that Enterprise Manager picks up all newly added events in the Low/Medium list.

WORKAROUND:

1. Log out of Enterprise Manager.

2. Open the component_events.xml file.
This file is located in the $IDM_OPSS_ORACLE_HOME/modules/oracle.iau_11.1.1/components/JPS/ directory.

3. Search for <FilterPresetDefinition name="Low">.

4. In the event list, change purgeDistributionStatus to PurgeDistributionStatus.
Note the capitalization.

5. Search for <FilterPresetDefinition name="Medium">.

6. In the event list, change purgeDistributionStatus to PurgeDistributionStatus.
Note the capitalization.

7. Save the file and close it.

8. Start Enterprise Manager.

29.1.6 Attributes Passed to Authorization Request Are Treated as Case Sensitive

When using the PEP API names of passed attributes, they must be in the same case as those mentioned in the policies.

29.1.7 Audit Schema Definitions are Incomplete

The IAUOES audit schema is not synchronized with Oracle Entitlements Server event definitions, so it does not contain the necessary columns for this component. Consequently, data cannot be stored in the appropriate columns and audit reports cannot be run against Oracle Entitlements Server data.

WORKAROUND - Option 1

Use this option if RCU has not yet been run. The steps are:

1. Locate JPS.sql at this location:

$RCU_HOME/rcu/integration/iauoes/scripts/JPS.sql

Modify the file permission, making the file writable.

2. Copy over the file:

$IDM_OPSS_ORACLE_HOME/modules/oracle.iau_11.1.1/sql/scripts/JPS.sql

to:

$RCU_HOME/rcu/integration/iauoes/scripts/JPS.sql

3. Run RCU to create the IAUOES schema.

WORKAROUND - Option 2

Use this option if RCU has already been run. The steps are:

1. Copy over the file:

$IDM_OPSS_ORACLE_HOME/modules/oracle.iau_11.1.1/sql/scripts/JPS.sql

to the directory from which you run sqlplus.

2. Connect to sqlplus as sysdba.

3. Run the following commands at the SQL prompt:

1. alter session set current_schema=audit_schema_user

2. drop table JPS;

3. @@JPS.sql audit_schema_user audit_schema_user_Append
audit_schema_user_Viewer;

29.1.8 Java Security Module on IPv6 Client Not Supported on Windows

Because of an issue with the JDK 1.6, the Java Security Module is not supported when using a Windows IPv6 client. We are working with the JDK development team for a resolution.

29.1.9 Validating Attribute Names in Custom Functions

When using custom function implementations, if the attribute name is invalid, the result of the authorization request could be wrong. Thus, attribute names must be validated before retrieving their values.

WORKAROUND:

Use the following code in custom function implementations to validate attribute names.

boolean isValidAttributeName(String name) {
if (name == null) return false;
return name.matches("[A-Za-z_][A-Za-z0-9_]*");
}

29.2 Configuration Issues and Workarounds

There are no configuration issues at this time.

29.3 Documentation Errata

There are no documentation errata at this time.

30 Oracle Identity Federation

This chapter describes issues associated with Oracle Identity Federation. It includes the following topics:

- Section 30.1, "General Issues and Workarounds"

- Section 30.2, "Configuration Issues and Workarounds"

- Section 30.3, "Documentation Errata"

30.1 General Issues and Workarounds

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

- Section 30.1.1, "Database Table for Authentication Engine must be in Base64 Format"

- Section 30.1.2, "Considerations for Oracle Identity Federation HA in SSL mode"

- Section 30.1.3, "Database Column Too Short error for IDPPROVIDEDNAMEIDVALUE"

30.1.1 Database Table for Authentication Engine must be in Base64 Format

When using a database table as the authentication engine, and the password is stored hashed as either MD5 or SHA, it must be in base64 format.

The hashed password can be either in the base64-encoded format or with a prefix of {SHA} or {MD5}. For example:

{SHA}qUqP5cyxm6YcTAhz05Hph5gvu9M=

30.1.2 Considerations for Oracle Identity Federation HA in SSL mode

In a high availability environment with two (or more) Oracle Identity Federation servers mirroring one another and a load balancer at the front-end, there are two ways to set up SSL:

- Configure SSL on the load balancer, so that the SSL connection is between the user and the load balancer. In that case, the keystore/certificate used by the load balancer has a CN referencing the address of the load balancer.
The communication between the load balancer and the WLS/Oracle Identity Federation can be clear or SSL (and in the latter case, Oracle WebLogic Server can use any keystore/certificates, as long as these are trusted by the load balancer).

- SSL is configured on the Oracle Identity Federation servers, so that the SSL connection is between the user and the Oracle Identity Federation server. In this case, the CN of the keystore/certificate from the Oracle WebLogic Server/Oracle Identity Federation installation needs to reference the address of the load balancer, as the user will connect using the hostname of the load balancer, and the Certificate CN needs to match the load balancer's address.
In short, the keystore/certificate of the SSL endpoint connected to the user (load balancer or Oracle WebLogic Server/Oracle Identity Federation) needs to have its CN set to the hostname of the load balancer, since it is the address that the user will use to connect to Oracle Identity Federation.

30.1.3 Database Column Too Short error for IDPPROVIDEDNAMEIDVALUE

Problem

When Oracle Identity Federation is configured to use a database store for session and message data store, the following error is seen if data for IDPPROVIDEDNAMEID is over 200 characters long:

ORA-12899: value too large for column
"WDO_OIF"."ORAFEDTMPPROVIDERFED"."IDPPROVIDEDNAMEIDVALUE" (actual: 240,
maximum: 200)\n]

Workaround

Alter table ORAFEDTMPPROVIDERFED to increase the column size for "idpProvidedNameIDValue" to 240.

30.2 Configuration Issues and Workarounds

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

- Section 30.2.1, "WLST Environment Setup when SOA and OIF are in Same Domain"

- Section 30.2.2, "Oracle Virtual Directory Requires LSA Adapter"

- Section 30.2.3, "Settings for Remote WS-Fed SP Must be Changed Dynamically"

- Section 30.2.4, "Required Property when Creating a WS-Fed Trusted Service Provider"

- Section 30.2.5, "Federated Identities Table not Refreshed After Record Deletion"

- Section 30.2.6, "Default Authentication Scheme is not Saved"

- Section 30.2.7, "Configuring 10g to Work with 11g Oracle Identity Federation using Artifact Profile"

- Section 30.2.8, "Regenerating OAM 11g Key Requires Oracle Identity Federation Upgrade Script"

30.2.1 WLST Environment Setup when SOA and OIF are in Same Domain

If your site contains Oracle SOA Suite and Oracle Identity Federation in the same domain, the WLST setup instructions in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation are insufficient for WLST to correctly execute Oracle Identity Federation commands.

This can happen if you install an IdM domain, then extend it with an Oracle SOA install; the SOA installer changes the ORACLE_HOME environment variable. This breaks the Oracle Identity Federation WLST environment, as it relies on the IdM value for ORACLE_HOME.

Take these steps to enable the use of WLST commands:

1. Execute the instructions described in Section 9.1.1, Setting up the WLST Environment, in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation.

2. Copy OIF-ORACLE_HOME/fed/script/*.py to WL_HOME/common/wlst.

3. Append the CLASSPATH environment variable with OIF-ORACLE_HOME/fed/scripts.

30.2.2 Oracle Virtual Directory Requires LSA Adapter

To use Oracle Virtual Directory as an Oracle Identity Federation user store or an authentication engine, you must configure a Local Storage Adapter, and the context root must be created as required at installation or post-install configuration time.

For details about this task, see the chapter Creating and Configuring Oracle Virtual Directory Adapters in the Oracle Fusion Middleware Administrator's Guide for Oracle Virtual Directory.

30.2.3 Settings for Remote WS-Fed SP Must be Changed Dynamically

On the Edit Federations page, the Oracle Identity Federation (OIF) settings for remote WS-Fed service provider contain a property called SSO Token Type; you can choose to either inherit the value from the IdP Common Settings page or override it here. The number of properties shown in 'OIF Settings' depends on the value of SSO Token Type.

If you choose to override SSO Token Type with a different value (for example, by changing from SAML2.0 to SAML1.1), the number of properties shown in 'OIF Settings' does not change until you click the Apply button.

Also, if you have overridden the value for Default NameID Format to 'Persistent Identifier' or 'Transient/One-Time Identifier', then changed the SSO Token Type value from 'SAML2.0' to 'SAML1.1' or 'SAML1.0', you will notice that the value for Default NameID Format is now blank. To proceed, you must reset this property to a valid value from the list.

30.2.4 Required Property when Creating a WS-Fed Trusted Service Provider

When you create a WS-Fed Trusted Service Provider, you must set the value for the 'Use Microsoft Web Browser Federated Sign-On' property with these steps:

1. In Fusion Middleware Control, navigate to Federations, then Edit Federations.

2. Choose the newly create WS-Fed Trusted Service Provider and click Edit.

3. In the 'Trusted Provider Settings' section, set the value for Use Microsoft Web Browser Federated Sign-On by checking or unchecking the check-box.

4. Click Apply.

30.2.5 Federated Identities Table not Refreshed After Record Deletion

When the federation store is XML-based, a record continues to be displayed in the federated identities table after it is deleted.

The following scenario illustrates the issue:

1. The federation data store is XML.

2. Perform federated SSO, using "map user via federated identity".

3. In Fusion Middleware Control, locate the Oracle Identity Federation instance, and navigate to Administration, then Identities, then Federated Identities.

4. Click on the created federation record and delete it.

After deletion, the federated record is still in the table. Further attempts at deleting the record result in an error.

The workaround is to manually refresh the table by clicking Search.

30.2.6 Default Authentication Scheme is not Saved

Problem

This problem is seen when you configure Oracle Access Manager in Fusion Middleware Control as a Service Provider Integration Module. It is not possible to set a default authentication scheme since the default is set to a certain scheme (say OIF-password-protected) but the radio button is disabled.

Solution

Take these steps to set the preferred default authentication scheme:

1. Check the Create check-box for the scheme that is currently set as the default but disabled.

2. Check the Create check-box(es) for the authentication scheme(s) that you would like to create.

3. Click the radio button of the scheme that you wish to set as the default.

4. Uncheck the Create check-box of the scheme in Step 1 only if you do not want to create the scheme.

5. Provide all the required properties in the page.

6. Click the Configure Oracle Access Manager button to apply the changes.

The default authentication scheme is now set to the one that you selected.

Note:

In addition, when trying to remove any authentication scheme, ensure that you do not remove the default scheme; if you must remove the scheme, change the default to another authentication scheme before you remove the scheme.

30.2.7 Configuring 10g to Work with 11g Oracle Identity Federation using Artifact Profile

In the SAML 1.x protocol, for a 10g Oracle Identity Federation server to work with an 11g Oracle Identity Federation server using the Artifact profile, you need to set up either basic authentication or client cert authentication between the two servers.

For instructions, see:

- Section 6.9 Protecting the SOAP Endpoint, in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation, 11g Release 1 (11.1.1)

- Section 6.5.13.2 When Oracle Identity Federation is an SP, in the Oracle Identity Federation Administrator's Guide, 10g (10.1.4.0.1)

30.2.8 Regenerating OAM 11g Key Requires Oracle Identity Federation Upgrade Script

In Oracle Enterprise Manager Fusion Middleware Control, when you configure the SP Integration Module for Oracle Access Manager 11g, you can regenerate the secret key by clicking the Regenerate button (Service Provider Integration Modules page, Oracle Access Manager 11g tab).

In an upgraded 11.1.1.7.0 environment, it is necessary to execute the Oracle Identity Federation upgrade script before you regenerate the OAM 11g secret key from this page. For details about how to run the script, see the Oracle Fusion Middleware Patching Guide.

30.3 Documentation Errata

This section contains documentation errata for the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation.

Note:

For documentation errata and other release notes relating to the integration of Oracle Identity Federation with Oracle Access Manager 11g , see the chapter for "Oracle Access Manager."

This section contains these topics:

- Section 30.3.1, "Incorrect Command Cited for BAE Configuration Procedure"

- Section 30.3.2, "SP Post-Processing Plug-in Properties for OAM 11g"

- Section 30.3.3, "Short Hostname Redirect Using mod_rewrite Configuration"

30.3.1 Incorrect Command Cited for BAE Configuration Procedure

In the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation, Part Number E13400-06, Section 6.8.2 Configuring the BAE Direct Attribute Exchange Profile, subsection "Set the BAE Direct Attribute Exchange Profile for a Partner", the procedure incorrectly documents the WLST command setPartnerProperty instead of the correct setFederationProperty command.

Replace the two commands mentioned in that subsection with:

setFederationProperty("PARTNER_PROVIDER_ID", "attributebaeenabled" ,
"true","boolean")

setFederationProperty("PARTNER_PROVIDER_ID", "attributebaeenabled" ,
"false","boolean")

to set and unset the BAE property, respectively.

30.3.2 SP Post-Processing Plug-in Properties for OAM 11g

In the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation, Part Number E13400-06, Section 12.5.2 Configuring Oracle Identity Federation for the Plug-in is missing the properties needed to configure Oracle Access Manager 11g.

Add the following row to the end of Table 12-3 SP Engine Configuration for Post-processing Plug-in; this row shows the properties needed for Oracle Access Manager 11g:

SP Engine

web context property

relative path property

OAM 11g

oam11g-login-context

oam11g-login

30.3.3 Short Hostname Redirect Using mod_rewrite Configuration

In the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation, Part Number E13400-06, Section 3.2.2.2 Integrate Oracle Single Sign-On with OHS (as well as earlier editions with the same section), the code in comments (lines starting with #) at the end of the section should be revised to use a mod_rewrite configuration.

Replace the text:

#
# If you would like to have short hostnames redirected to
# fully qualified hostnames to allow clients that need
# authentication via mod_osso to be able to enter short
# hostnames into their browsers uncomment out the following
# lines
#
#PerlModule Apache::ShortHostnameRedirect
#PerlHeaderParserHandler Apache::ShortHostnameRedirect

with the text:

#
# To have short hostnames redirected to fully qualified
# hostnames for clients that need authentication via
# mod_osso to be able to enter short hostnames into their
# browsers use a mod_rewrite configuration such as the following.
#
# e.g
#RewriteEngine On
#RewriteCond %{HTTP_HOST} !www.example.com
#RewriteRule î.*$ http://%{SERVER_NAME}%{REQUEST_URI} [R]
#where www.example.com is the fully qualified domain name.

31 Oracle Identity Manager

This chapter describes issues associated with Oracle Identity Manager. It includes the following topics:

- Section 31.1, "Patch Requirements"

- Section 31.2, "General Issues and Workarounds"

- Section 31.3, "Configuration Issues and Workarounds"

- Section 31.4, "Multi-Language Support Issues and Limitations"

- Section 31.5, "Documentation Errata"

31.1 Patch Requirements

This section describes patch requirements for Oracle Identity Manager 11g Release 1 (11.1.1). It includes the following sections:

- Obtaining Patches From My Oracle Support (Formerly OracleMetaLink)

- Patch Requirements for Oracle Database 11g (11.1.0.7)

- Patch Requirements for Oracle Database 11g (11.2.0.2.0)

- Patch Requirements for Segregation of Duties (SoD)

- Patch Upgrade Requirement

31.1.1 Obtaining Patches From My Oracle Support (Formerly OracleMetaLink)

To obtain a patch from My Oracle Support (formerly OracleMetaLink), go to following URL, click Patches and Updates, and search for the patch number:

https://support.oracle.com/

31.1.2 Patch Requirements for Oracle Database 11g (11.1.0.7)

Table 31-1 lists patches required for Oracle Identity Manager 11g Release 1 (11.1.1) configurations that use Oracle Database 11g (11.1.0.7). Before you configure Oracle Identity Manager 11g, be sure to apply the patches to your Oracle Database 11g (11.1.0.7) database.

Table 31-1 Required Patches for Oracle Database 11g (11.1.0.7)

Platform

Patch Number and Description on My Oracle Support

UNIX / Linux

7614692: BULK FEATURE WITH 'SAVE EXCEPTIONS' DOES NOT WORK IN ORACLE 11G

7000281: DIFFERENCE IN FORALL STATEMENT BEHAVIOR IN 11G

8327137: WRONG RESULTS WITH INLINE VIEW AND AGGREGATION FUNCTION

8617824: MERGE LABEL REQUEST ON TOP OF 11.1.0.7 FOR BUGS 7628358 7598314

Windows 32 bit

8689191: ORACLE 11G 11.1.0.7 PATCH 16 BUG FOR WINDOWS 32 BIT

Windows 64 bit

8689199: ORACLE 11G 11.1.0.7 PATCH 16 BUG FOR WINDOWS (64-BIT AMD64 AND INTEL EM64T)

Note:

The patches listed for UNIX/Linux in Table 31-1 are also available by the same names for Solaris SPARC 64 bit.

31.1.3 Patch Requirements for Oracle Database 11g (11.2.0.2.0)

If you are using Oracle Database 11g (11.2.0.2.0), make sure that you download and install the appropriate version (based on the platform) for the RDBMS Patch Number 9776940. This is a prerequisite for installing the Oracle Identity Manager schemas.

Table 31-2 lists the patches required for Oracle Identity Manager 11g Release 1 (11.1.1) configurations that use Oracle Database 11g Release 2 (11.2.0.2.0). Make sure that you download and install the following patches before creating Oracle Identity Manager schemas.

Table 31-2 Required Patches for Oracle Database 11g (11.2.0.2.0)

Platform

Patch Number and Description on My Oracle Support

Linux x86 (32-bit)

Linux x86 (64-bit)

Oracle Solaris on SPARC (64-bit)

Oracle Solaris on x86-64 (64-bit)

RDBMS Interim Patch#9776940.

Microsoft Windows x86 (32-bit)

Bundle Patch 2 [Patch#11669994] or later. The latest Bundle Patch is 4 [Patch# 11896290].

Microsoft Windows x86 (64-bit)

Bundle Patch 2 [Patch# 11669995] or later. The latest Bundle Patch is 4 [Patch# 11896292].

If this patch is not applied, then problems might occur in user and role search and manager lookup. In addition, search results might return empty result.

Note:

- Apply this patch in ONLINE mode. Refer to the readme.txt file bundled with the patch for the steps to be followed.

- In some environments, the RDBMS Interim Patch has been unable to resolve the issue, but the published workaround works. Refer to the metalink note "Wrong Results on 11.2.0.2 with Function-Based Index and OR Expansion due to fix for Bug:8352378 [Metalink Note ID 1264550.1]" for the workaround. This note can be followed to set the parameters accordingly with the only exception that they need to be altered at the Database Instance level by using ALTER SYSTEM SET <param>=<value> scope=<memory> or <both>.

31.1.4 Patch Requirements for Segregation of Duties (SoD)

Table 31-3 lists patches that resolve known issues with Segregation of Duties (SoD) functionality:

Table 31-3 SoD Patches

Patch Number / ID

Description and Purpose

Patch number 9819201 on My Oracle Support

Apply this patch on the SOA Server to resolve the known issue described in "SoD Check During Request Provisioning Fails While Using SAML Token Client Policy When Default SoD Composite is Used".

The description of this patch on My Oracle Support is "ERROR WHILE USING SAML TOKEN CLIENT POLICY FOR CALLBACK."

Patch ID 3M68 using the Oracle Smart Update utility. Requires passcode: 6LUNDUC7.

Using the Oracle Smart Update utility, apply this patch on the Oracle WebLogic Server to resolve the known issue described in "SoD Check Fails While Using Client-Side Policy in Callback Invocation During Request Provisioning".

Note:

The SoD patches are required to resolve the known issues in Oracle Identity Manager 11g Release 1 (11.1.1.3), but these patches are not required in 11g Release 1 (11.1.1.5).

31.1.5 Patch Upgrade Requirement

While applying the patch provided by Oracle Identity Manager, the following error is generated:

ApplySession failed: ApplySession failed to prepare the system.

OPatch version 11.1.0.8.1 must be upgraded to version 11.1.0.8.2 to meet the version requirement.

See "Obtaining Patches From My Oracle Support (Formerly OracleMetaLink)" for information about downloading OPatch from My Oracle Support.

31.2 General Issues and Workarounds

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

- Do Not Use Platform Archival Utility

- SPML-DSML Service is Unsupported

- Resource Object Names Longer than 100 Characters Cause Import Failure

- Status of Users Created Through the Create and Modify User APIs

- Status of Locked Users in Oracle Access Manager Integrations

- Generating an Audit Snapshot after Bulk-Loading Users or Accounts

- Browser Timezone Not Displayed

- Date Format Change in the SoD Timestamp Field Not Supported

- Bulk Loading CSV Files with UTF-8 BOM Encoding Not Supported

- Date Type Attributes are Not Supported for the Default Scheduler Job, "Job History Archival"

- Low File Limits Prevent Adapters from Compiling

- Reconciliation Engine Requires Matching Rules

- SPML Requests Do Not Report When Any Date is Specified in Wrong Format

- Logs Populated with SoD Exceptions When the SoD Message Fails and Gets Stuck in the Queue

- Underscore Character Cannot Be Used When Searching for Resources

- Assign to Administrator Action Rule is Not Supported by Reconciliation

- Some Buttons on Attestation Screens Do Not Work in Mozilla Firefox

- The maxloginattempts System Property Causes Autologin to Fail When User Tries to Unlock

- "<User not found>" Error Message Appears in AdminServer Console While Setting-Up an Oracle Identity Manager-Oracle Access Manager Integration

- Do Not Use Single Quote Character in Reconciliation Matching Rule

- Do Not Use Special Characters When Reconciling Roles from LDAP

- SoD Check During Request Provisioning Fails While Using SAML Token Client Policy When Default SoD Composite is Used

- SoD Check Fails While Using Client-Side Policy in Callback Invocation During Request Provisioning

- Error May Appear During Provisioning when Generic Technology Connector Framework Uses SPML

- Cannot Click Buttons in TransUI When Using Mozilla Firefox

- LDAP Handler May Cause Invalid Exception While Creating, Deleting, or Modifying a Role

- Cannot Reset User Password Comprised of Non-ASCII Characters

- Benign Exception and Error Message May Appear While Patching Authorization Policies

- The DateTime Pick in the Trans UI Does Not Work Correctly in the Thai Locale

- User Without Access Policy Administrators Role Cannot View Data in Access Policy Reports

- Archival Utility Throws an Error for Empty Date

- TransUI Closes with Direct Provisioning of a Resource

- Scheduler Throws "ParameterValueTypeNotSupportedException" Instead of "RequiredParameterNotSetException"

- All New User Attributes Are Not Supported for Attestation in Oracle Identity Manager 11g

- LDAP GUID Mapping to Any Field of Trusted Resource Not Supported

- User Details for Design Console Access Field Must Be Mapped to Correct Values When Reading Modify Request Results

- Cannot Create a User Containing Asterisks if a Similar User Exists

- Blank Status Column Displayed for Past Proxies

- Mapping the Password Field in a Reconciliation Profile Prevents Users from Being Created

- UID Displayed as User Login in User Search Results

- Roles/Organizations Browse Trees Disappear

- Entitlement Selection Is Not Optional for Data Gathering

- Oracle Identity Manager Server Throws Generic Exception While Deploying a Connector

- Create User API Allows Any Value for the "Users.Password Never Expires", "Users.Password Cannot Change", and "Users.Password Must Change" Fields

- Incorrect Label in JGraph Screen for the GTC

- Running the Workflow Registration Utility Generates an Error

- Native Performance Pack is Not Enabled On Solaris 64-bit JVM Install

- Error in the Create Generic Technology Connector Wizard

- DSML Profile for the SPML Web Service is Not Deployed With Oracle Identity Manager

- New Human Tasks Must Be Copied in SOA Composites

- Modify Provisioned Resource Request Does Not Support Service Account Flag

- Erroneous "Query by Example" Icon in Identity Administration Console

- The XL.ForcePasswordChangeAtFirstLogin System Property Is No Longer Used

- The tcExportOperationsIntf.findObjects(type,name) API Does Not Accept the Asterisk (*) Wilcard Character in Both Parameters

- Disabled Links on the Access Policy Summary Page Opened in Mozilla FireFox

- Benign Error is Generated on Editing the IT Resource Form in Advanced Administration

- User Account is Not Locked in iPlanet Directory Server After it is Locked in Oracle Identity Manager

- Oracle Identity Manager Does Not Support Autologin With JavaAgent

- Benign Error Logged on Opening Access Policies, Resources, or Attestation Processes

- User Locked in Oracle Identity Manager But Not in LDAP

- Reconciliation Profile Must Not Be Regenerated Via Design Console for Xellerate Organization Resource Object

- Benign Error Logged on Clicking Administration After Upgrade

- Provisioning Fails Through Access Policy for Provisioned User

- Benign Warning Messages Displayed During Oracle Identity Manager Managed Server Startup

- Benign Message Displayed When Running the Deployment Manager

- Deployment Manager Export Fails When Started Using Microsoft Internet Explorer 7 With JRE Plugin 1.6_23

- User Creation Fails in Microsoft Active Directory When Value of Country Attribute Exceeds Two Characters

- Permission on Target User Required to Revoke Resource

- Reconciliation Event Fails for Trusted Source Reconciliation Because of Missing Reconciliation Rule in Upgraded Version of Oracle Identity Manager

- XML Validation Error on Oracle Identity Manager Managed Server Startup

- Cannot View or Edit Adapter Mapping in the Data Object Manager Form of the Design Console

- Role Memberships for Assign or Revoke Operations Not Updated on Enabling or Disabling Referential Integrity Plug-in

- Reconciliation Data Displays Attributes That Are Not Modified

- Benign Errors Displayed on Starting the Scheduler Service When There are Scheduled Jobs to be Recovered

- Trusted Source GTC Reconciliation Mapping Cannot Display Complete Attribute Names

- Benign Error Logged for Database Connectivity Test

- MDS Validation Error When Importing GTC Provider Through the Deployment Manager

- Encrypted User-Defined Field (UDF) Cannot be Stored with Size of 4000 Characters or More

- Request Approval Fails With Callback Service Failure

- Localized Display Name is Not Reconciled Via User/Role Incremental Reconciliation with iPlanet Directory Server

- LDAP Role Hierarchy and Role Membership Reconciliation With Non-ASCII Characters Does Not Reconcile Changes in Oracle Identity Manager

- Import of Objects Fails When All Objects Are Selected for Export

- Benign Audit Errors Logged After Upgrade

- Connector Upgrade Fails if Existing Data is Bigger in Size Than New Column Length

- Connector Artifacts Count Increases in the Deployment Manager When File is Not Imported

- Uploading JAR Files By Using the Upload JAR Utility Fails

- Oracle Identity Manager Data and MT Upgrade Fails Because Change of Database User Password

- Reverting Unsaved UDFs Are Not Supported in the Administration Details Page for Roles and Organizations

- Resources Provisioned to User Without Checking Changes in User Status After Request is Submitted

- Config.sh Command Fails When JRockit is Installed With Data Samples and Source

- Unexpected Memory Usage in Oracle Identity Manager 11g Release 1(11.1.1)

- Reports Link No Longer Exists in the Administrative and User Console

- Not Allowing to Delete a Role Whose Assigned User Members are Deleted

- Roles and Organizations Do Not Support String UDFs of Password Type

- Manage Localizations Dialog Box Does Not Open After Modifying Roles

- Not Allowing to Create User With Language-Specific Display Name Values

- SoD Check Results Not Displayed for Requests Created by Users for the PeopleSoft Resource

- The XL.UnlockAfter System Property and the Automatically Unlock User Scheduled Job Do Not Take Effect

- Resetting Password on Account Lockout Does Not Unlock User

- Incremental and Full Reconciliation Jobs Cannot Be Run Together

- Incorrect Content in the ScheduleTask Jars Loaded and Third Party Jars Tables in the MT Upgrade Report

- Scroll Bar Not Available on the Select Connector Objects to Be Upgraded Page of the Connector Management - Upgrading Wizard

- Adapter Import Might Display Adapter Logic if Compilation Fails Because of Incorrect Data

- XIMDD Tests Fail in Oracle Identity Manager

- Error While Installing Oracle Identity Manager

31.2.1 Do Not Use Platform Archival Utility

Currently, the Platform Archival Utility is not supported and should not be used.

To work around this issue, use the predefined scheduled task named Orchestration Process Cleanup Task to delete all completed orchestration processes and related data.

31.2.2 SPML-DSML Service is Unsupported

Oracle Identity Manager's SPML-DSML Service is currently unsupported in 11g Release 1 (11.1.1). However, you can manually deploy the spml-dsml.ear archive file for Microsoft Active Directory password synchronization.

31.2.3 Resource Object Names Longer than 100 Characters Cause Import Failure

If a resource object name is more than 100 characters, an error occurs in the database and the resource object is not imported. To work around this issue, change the resource object's name in the XML file so the name is less than 100 characters.

31.2.4 Status of Users Created Through the Create and Modify User APIs

You cannot create users in Disabled State. Users are always created in Active State.

The Create and Modify User APIs do not honor the Users.Disable User attribute value. If you pass a value to the Users.Disable User attribute when calling the Create API, Oracle Identity Manager ignores this value and the USR table is always populated with a value of 0, which indicates the user's state is Active.

Use the Disable API to disable a user.

31.2.5 Status of Locked Users in Oracle Access Manager Integrations

When Oracle Access Manager locks a user account in an Oracle Identity Manager-Oracle Access Manager integration, it may take approximately five minutes, or the amount of time defined by the incremental reconciliation scheduled interval, for the status of the locked account to be reconciled and appear in Oracle Identity Manager. However, if a user account is locked or unlocked in Oracle Identity Manager, the status appears immediately.

31.2.6 Generating an Audit Snapshot after Bulk-Loading Users or Accounts

The GenerateSnapshot.[sh|bat] option does not work correctly when invoked from the Bulk Load utility. To work around this issue and generate a snapshot of the initial audit after bulk loading users or accounts, you must run GenerateSnapshot.[sh|bat] from the $OIM_HOME/bin/ directory.

31.2.7 Browser Timezone Not Displayed

Due to an ADF limitation, the browser timezone is currently not accessible to Oracle Identity Manager. Oracle Identity Manager bases the timezone information in all date values on the server's timezone. Consequently, end users will see timezone information in the date values, but the timezone value will display the server's timezone.

31.2.8 Date Format Change in the SoD Timestamp Field Not Supported

The date-time value that end users see in the Segregation of Duties (SoD) Check Timestamp field on the SoD Check page will always display as "YYYY-MM-DD hh:mm:ss" and this format cannot be localized.

To work around this localization issue, perform the following steps:

1. Open the "Oracle_eBusiness_User_Management_9.1.0.1.0/xml/Oracle-eBusinessSuite-TCA-Main-ConnectorConfig.xml" file.

2. In the EBS Connector import xml, locate the SoDCheckTimeStamp field for the Process Form. Change <SDC_FIELD_TYPE> to 'DateFieldDlg' and change <SDC_VARIANT_TYPE> to 'Date' as shown in the following example:

<FormField name = "UD_EBST_USR_SODCHECKTIMESTAMP">
<SDC_UPDATE>!Do not change this field!</SDC_UPDATE>
<SDC_LABEL>SoDCheckTimestamp</SDC_LABEL>
<SDC_VERSION>1</SDC_VERSION>
<SDC_ORDER>23</SDC_ORDER>
<SDC_FIELD_TYPE>DateFieldDlg</SDC_FIELD_TYPE>
<SDC_DEFAULT>0</SDC_DEFAULT>
<SDC_ENCRYPTED>0</SDC_ENCRYPTED>
<!--SDC_SQL_LENGTH>50</SDC_SQL_LENGTH-->
<SDC_VARIANT_TYPE>Date</SDC_VARIANT_TYPE>
</FormField>

3. Import the Connector.

4. Enable SoD Check.

5. Provision the EBS Resource with entitlements to trigger an SoD Check.

6. Check the SoDCheckTimeStamp field in Process Form to confirm it is localized like the other date fields in the form.

31.2.9 Bulk Loading CSV Files with UTF-8 BOM Encoding Not Supported

Bulk loading a CSV file for which UTF-8 BOM (byte order mark) encoding is specified causes an error. However, bulk-loading UTF-8 encoded CSV files works as expected if you specify "no BOM" encoding.

To work around this issue,

- If you want to load non-ASCII data, you must change your CSV file encoding to "UTF-8 no BOM" before loading the CSV file.

- If your data is stored in CSV files with "UTF-8 BOM" encoding, you must change them to "UTF-8 no BOM" encoding before running the bulkload script.

31.2.10 Date Type Attributes are Not Supported for the Default Scheduler Job, "Job History Archival"

The default Scheduler job, "Job History Archival," does not support date type attributes.

The "Archival Date" attribute parameter in "Job History Archival" only accepts string patterns such as "ddMMyyyy" and "MMM DD, yyyy."

When you run a Scheduler job, the code checks the date format. If you enter the wrong format, an error similar to the following example, displays in the execution status list and in the log console:

<IAM-1020063> <Incorrect format of Archival Date parameter. Archival Date is expected in DDMMYYYY or UI Date format.>

The job cannot run successfully until you input the correct Archival Date information.

31.2.11 Low File Limits Prevent Adapters from Compiling

On machines where the file limits are set too low, trying to create and compile an entity adapter causes a "Too many open files" error and the adapter will not compile.

To work around this issue, change the file limits on your machine to the following (located in /etc/security/limits.conf) and then restart the machine:

- soft nofile 4096

- hard nofile 4096

31.2.12 Reconciliation Engine Requires Matching Rules

Currently, Oracle Identity Manager's Reconciliation Engine in 11g Release 1 (11.1.1) requires you to define a matching rule to identify the users for every connector in reconciliation. Errors will occur during reconciliation if you do not define a matching rule to identify users.

31.2.13 SPML Requests Do Not Report When Any Date is Specified in Wrong Format

When any date, such as activeStartDate, hireDate, and so on, is specified in an incorrect format, the Web server does not pass those values to the SPML layer. Only valid dates are parsed and made available to SPML. Consequently, when any SPML request that contains an invalid date format, the invalid date format from the request is ignored and is not available for that operation. For example, if you specify the HireDate month as "8" instead of "08," the HireDate will not be populated after the Create request is completed and no error message is displayed.

The supported date format is:

yyyy-MM-dd hh:mm:ss.fffffffff

No other date format is supported.

31.2.14 Logs Populated with SoD Exceptions When the SoD Message Fails and Gets Stuck in the Queue

SoD functionality uses JMS-based processing. Oracle Identity Manager submits a message to the oimSODQueue for each SoD request. If for some reason an SoD message always results in an error, Oracle Identity Manager never processes the next message in the oimSODQueue. Oracle Identity Manager always picks the same error message for processing until you delete that message from the oimSODQueue.

To work around this issue, use the following steps to edit the queue properties and to delete the SoD message in oimSODQueue:

1. Log on to the WebLogic Admin Console at http://<hostname>:<port>/console

2. From the Console, select Services, Messaging, JMS Modules.

3. Click OIMJMSModule. All queues will be displayed.

4. Click oimSODQueue.

5. Select the Configurations, Delivery Failure tabs.

6. Change the retry count so that the message can only be submitted a specified number of times.

7. Change the default Redelivery Limit value from -1 (which means infinite) to a specific value. For example, if you specify 1, the message will be submitted only once.

8. To review and delete the SoD error message, go to the Monitoring tab, select the message, and delete it.

31.2.15 A Backslash (\) Cannot Be Used in a weblogic.properties File

If you are using the WeblogicImportMetadata.cmd utility to import data to MDS, then do not use a backslash (\) character in a path in the weblogic.properties file, or an exception will occur.

To work around this issue, you must use a double backslash (\\) or a forward slash (/) on Microsoft Windows. For example, change metadata_from_loc=C:\metadata\file to metadata_from_loc=C:\\metadata\\file in the weblogic.properties file.

31.2.16 Underscore Character Cannot Be Used When Searching for Resources

When you are searching for a resource object, do not use an underscore character (_) in the resource name. The search feature ignores the underscore and consequently does not return the expected results.

31.2.17 Assign to Administrator Action Rule is Not Supported by Reconciliation

Reconciliation does not support the Assign to Administrator Action rule.

To work around this issue, change the Assign to Administrator to None in the connector XML before importing the connector. However, after changing the value to None, you cannot revert to Assign to Administrator.

31.2.18 Some Buttons on Attestation Screens Do Not Work in Mozilla Firefox

If you are creating attestations in a Mozilla Firefox Web browser and you click certain buttons, nothing happens.

To work around this issue, click the Refresh button to refresh the page.

31.2.19 The maxloginattempts System Property Causes Autologin to Fail When User Tries to Unlock

WLS Security Realm has a default lock-out policy that locks out users for some time after several unsuccessful login attempts. This policy can interfere with the locking and unlocking functionality of Oracle Identity Manager.

To prevent the WLS Security Realm lock-out policy from affecting the lock/unlock functionality of Oracle Identity Manager, you must set the 'Lockout Threshold' value in the WLS 'User Lockout Policy' to at least 5 more than the value in Oracle Identity Manager. For example, if the value in Oracle Identity Manager is set to 10, you must set the WLS 'Lockout Threshold' value to 15.

To change the default values for the 'User lockout Policy,' perform the following steps:

1. Open the WebLogic Server Administrative Console.

2. Select Security Realms, REALM_NAME.

3. Select the User Lockout tab.

4. If configuration editing is not enabled, then click the Lock and Edit button to enable configuration editing.

5. Change the value of lockout threshold to the required value.

6. Click Save to save the changes.

7. Click Activate to activate your changes.

8. Restart all the servers in the domain.

31.2.20 "<User not found>" Error Message Appears in AdminServer Console While Setting-Up an Oracle Identity Manager-Oracle Access Manager Integration

When you set up Oracle Identity Manager-Oracle Access Manager Integration with a JAVA agent and log into the Admin Server Console, a "<User not found>" error message is displayed. This message displays even when the login is successful.

31.2.21 Do Not Use Single Quote Character in Reconciliation Matching Rule

If the single quote character (') is used in reconciliation data (for example, 'B'1USER1'), then target reconciliation will fail with an exception.

31.2.22 Do Not Use Special Characters When Reconciling Roles from LDAP

Due to a limitation in the Oracle SOA Infrastructure, do not use special characters such as commas (,) in role names, group names, or container descriptions when reconciling roles from LDAP. Oracle Identity Manager's internal code uses special characters as delimiters. For example, Oracle Identity Manager uses commas (,) as approver delimiters and the SOA HWF-level global configuration uses commas as assignee delimiters.

31.2.23 SoD Check During Request Provisioning Fails While Using SAML Token Client Policy When Default SoD Composite is Used

SoD check fails and the following error is displayed on the SOA console when SoD check is performed during request provisioning only when the Default SoD Check composite is used:

SEVERE: FabricProviderServlet.handleException Error during retrieval of test page or composite resourcejavax.servlet.ServletException: java.lang.NullPointerException

This happens when Callback is made from Oracle Identity Manager to SOA with the SoDCheck Results.

To resolve this issue, apply patch 9819201 on the SOA server. You can obtain patch 9819201 from My Oracle Support. The description of this patch on My Oracle Support is "ERROR WHILE USING SAML TOKEN CLIENT POLICY FOR CALLBACK."

For more information, refer to:

- Obtaining Patches From My Oracle Support (Formerly OracleMetaLink).

- Patch Requirements for Segregation of Duties (SoD)

31.2.24 SoD Check Fails While Using Client-Side Policy in Callback Invocation During Request Provisioning

SoD check fails and following error is displayed on the Oracle Identity Manager Administrative and User Console when SoD check is performed during request provisioning only when the Default SoD Check composite is used:

<Error> <oracle.wsm.resources.policymanager><WSM-02264> <"/base_domain/oim_server1/oim/unknown/iam-ejb.jar/WEBSERVICECLIENTs/SoDCheckResultService/PORTs/ResultPort" is not a recognized resource pattern.>
<Error> <oracle.iam.sod.impl> <IAM-4040002><Error getting Request Service : java.lang.IllegalArgumentException: WSM-02264 "/base_domain/oim_server1/oim/unknown/iam-ejb.jar/WEBSERVICECLIENTs/SoDCheckResultService/PORTs/ResultPort" is not a recognized resource pattern.>

To resolve this issue, use the Oracle Smart Update utility to apply patch ID 3M68, which requires passcode of 6LUNDUC7, on Oracle WebLogic Server. For more information, refer to:

- The Oracle Smart Update Installing Patches and Maintenance Packs documentation.

- Patch Requirements for Segregation of Duties (SoD)

31.2.25 Error May Appear During Provisioning when Generic Technology Connector Framework Uses SPML

When using the generic technology connector framework uses SPML, during provisioning, the following error may appear:

<SPMLProvisioningFormatProvider.formatData :problem with Velocity Template Unable
to find resource 'com/thortech/xl/gc/impl/prov/SpmlRequest.vm'>

If the error occurs, it blocks provisioning by using the predefined SPML GTC provisioning format provider. Restarting the Oracle Identity Manager server prevents the error from appearing again.

31.2.26 Cannot Click Buttons in TransUI When Using Mozilla Firefox

When using the Mozilla Firefox browser, in certain situations, some buttons in the legacy user interface, also known as TransUI, cannot be clicked. This issue occurs intermittently and can be resolved by using Firefox's reload (refresh) function.

31.2.27 LDAP Handler May Cause Invalid Exception While Creating, Deleting, or Modifying a Role

If an LDAP handler causes an exception when you create, modify, or delete a role, an invalid error message, such as System Error or Role does not exist, may appear.

To work around this issue, look in the log files, which will display the correct error message.

31.2.28 Cannot Reset User Password Comprised of Non-ASCII Characters

If a user's password is comprised of non-ASCII characters, and that user tries to reset the password from either the My Profile or initial login screens in the Oracle Identity Manager Self Service interface, the reset will fail with the following error message:

Failed to change password during the validation of the old password

Note:

This error does not occur with user passwords comprised of only ASCII characters.

To work around this issue, perform the following steps:

1. Set the JVM file encoding to UTF8, for example: -Dfile.encoding=UTF-8

Note:

On Windows systems, this may cause the console output to appear distorted, though output in the log files appear correctly.

2. Restart the Oracle WebLogic Server.

31.2.29 Benign Exception and Error Message May Appear While Patching Authorization Policies

When patches are applied to the Authorization Polices that are included with Oracle Identity manager and the JavaSE environment registers the Oracle JDBC driver, java.security.AccessControlException is reported and the following error message appears:

Error while registering Oracle JDBC Diagnosability MBean

You can ignore this benign exception, as the Authorization Policies are seeded successfully, despite the exception and error messages.

31.2.30 The DateTime Pick in the Trans UI Does Not Work Correctly in the Thai Locale

When locale is set to th_TH in Microsoft Windows Internet Explorer Web browser, the datetime in Oracle Identity Manager follows the Thai Buddhist calendar. In the Create Attestation page of the Administrative and User Console, when you select a date for start time, the year is displayed according to the Thai Buddhist calendar, for example, 2553. After you click OK, the equivalent year according to the Gregorian calendar, which is 2010, is displayed in the start time field. But when you click Next to continue creating the attestation, an error message is displayed stating that the start time of the process must not belong to the past.

To workaround this issue, perform any one of the following:

- Specify the datetime manually.

- Use Mozilla Firefox Web browser, which uses the Gregorian calendar.

31.2.31 User Without Access Policy Administrators Role Cannot View Data in Access Policy Reports

OIM user without the ACCESS POLICY ADMINISTRATORS role cannot view data in the following reports:

- Access Policy Details

- Access Policy List by Role

To workaround this issue:

1. Assign the ACCESS POLICY ADMINISTRATORS role to an OIM user.

2. Create a BI Publisher user with the same username in Step 1. Assign appropriated BI Publisher role to view reports.

3. Login as the BI Publisher user mentioned in step 2. View the Access Policy Details and Access Policy List by Role reports. All access policies are displayed.

31.2.32 Archival Utility Throws an Error for Empty Date

In case of empty date, archival utility throws an error message, but proceeds to archive data by mapping to the current date. Currently, no workaround exists for this issue.

31.2.33 TransUI Closes with Direct Provisioning of a Resource

TransUI closes while doing a direct provisioning if user defined field (UDF) is created with the default values. To work around this issue, you need to create a Lookup Code for the INTEGER/DOUBLE type UDF in the LKU/LKV table.

31.2.34 Scheduler Throws "ParameterValueTypeNotSupportedException" Instead of "RequiredParameterNotSetException"

On AIX platform, when a required parameter is missing during the creation of a scheduler job, instead of throwing "RequiredParameterNotSetException" with the error message "The value is not set for required parameters of a scheduled task.", it throws "ParameterValueTypeNotSupportedException" with the error message "Parameter value is not set properly". Currently, no workaround exists for this issue.

31.2.35 All New User Attributes Are Not Supported for Attestation in Oracle Identity Manager 11g

New user attributes are added in Oracle Identity Manager 11g. Not all of them are available for Attestation while defining user-scope. However, Attestation has been enhanced to include the following user attributes:

- USR_COUNTRY

- USR_LDAP_ORGANIZATION

- USR_LDAP_ORGANIZATION_UNIT

- USR_LDAP_GUID

Currently, no workaround exists for this issue.

31.2.36 LDAP GUID Mapping to Any Field of Trusted Resource Not Supported

Update fails in LDAP, if LDAP GUID is mapped to any field of trusted resource in LDAP-SYNC enabled installation. To work around this issue, Oracle does not recommend mapping for LDAP GUID field while creating reconciliation field mapping for a trusted resource.

31.2.37 User Details for Design Console Access Field Must Be Mapped to Correct Values When Reading Modify Request Results

When a Modify Request is raised, "End-User" and "End-User Administrator" values are displayed for the "Design Console Access" field. These values must be mapped to False/True while interpreting the user details.

31.2.38 Cannot Create a User Containing Asterisks if a Similar User Exists

If you try to create a user that contains an asterisk (*) after creating a user with a similar name, the attempt will fail. For example, if you create user test1test, followed by test*test, test*test will not be created.

It is recommended to not create users with asterisks in the User Login field.

31.2.39 Blank Status Column Displayed for Past Proxies

The Status field on the Post Proxies page is blank. However, active proxies are displayed correctly on Current Proxies page.

Currently, no workaround exists for this issue.

31.2.40 Mapping the Password Field in a Reconciliation Profile Prevents Users from Being Created

The Password field is available to be mapped with a reconciliation profile, but it should not be used. Attempting to map this field will generate a reconciliation event that will not create users. (The event ends in "No Match Found State".) In addition, you will not be able to re-evaluate or manually link this event.

31.2.41 UID Displayed as User Login in User Search Results

Although you can select the UID attribute from the Search Results Table Configuration list on the Search Configuration page of the Advanced Administration, the search results table for advanced search for users displays the User Login field instead of the UID field.

31.2.42 Roles/Organizations Browse Trees Disappear

After you delete an organization, the Browse trees for organizations and roles might not be displayed.

To work around this issue, click the Search Results tab, then click the Browse tab. The roles and organizations browse trees display correctly.

31.2.43 Entitlement Selection Is Not Optional for Data Gathering

Entitlement (Child Table) selection during data gathering on the process form, for the "Depends On (Depended)" attribute is not optional. During data gathering, if dependent lookups are configured, then the user has to select the parent lookup value so that filtering happens on the child lookup and thus user gets a final list of entitlements to select . Currently, no workaround exists to directly filter the values based on the child lookup.

31.2.44 Oracle Identity Manager Server Throws Generic Exception While Deploying a Connector

Generic exceptions are shown in server logs every time deployment manager import happens or profile changes manually or profile changes via design console. This is because "WLSINTERNAL" is not an authorized user of Oracle Identity Manager. "WLSINTERNAL" is an internal user of WebLogic Server, and MDS uses it to invoke MDS listeners if there is a change in XMLs stored in MDS. Currently, no workaround exists for this issue.

31.2.45 Create User API Allows Any Value for the "Users.Password Never Expires", "Users.Password Cannot Change", and "Users.Password Must Change" Fields

Create User API allows the user to set any value between 0 and 9 instead of 0 or 1 for "Users.Password Never Expires", "Users.Password Cannot Change" and "Users.Password Must Change" fields. However, any value other than 0 is considered as TRUE and 0 is considered as FALSE, and the flag is set accordingly for the user being created. Currently, no workaround exists for this issue.

31.2.46 Incorrect Label in JGraph Screen for the GTC

The User Type label on the JGraph screen is displayed incorrectly as Design Console Access. To display User Type, add the line Xellerate_Type=User Type to the OIM_HOME/server/customResources/customResources.properties file.

31.2.47 Running the Workflow Registration Utility Generates an Error

When the workflow registration utility is run in a clustered deployment of Oracle Identity Manager, the following error is generated:

[java] oracle.iam.platform.utils.NoSuchServiceException:
java.lang.reflect.InvocationTargetException

Ignore the error message.

31.2.48 Native Performance Pack is Not Enabled On Solaris 64-bit JVM Install

For Oracle Identity Manager JVM install on a Solaris 64-bit computer, Oracle WebLogic log displays the following error:

Unable to load performance pack. Using Java I/O instead. Please ensure that a native performance library is in:

To workaround this issue, perform the following to ensure that JDK picks up the 64-bit native performance:

1. In a text editor, open the MIDDLEWARE_HOME/wlserver_10.3/common/bin/commEnv.sh file.

2. Replace the following:

SUN_ARCH_DATA_MODEL="32"

With:

SUN_ARCH_DATA_MODEL="64"

3. Save and close the commEnv.sh file.

4. Restart the application server.

31.2.49 Error in the Create Generic Technology Connector Wizard

If you enter incorrect credentials for the database on the Create Generic Technology Connector wizard, a system error window is displayed. You must close this window and run the wizard again.

31.2.50 DSML Profile for the SPML Web Service is Not Deployed With Oracle Identity Manager

The DSML profile for the SPML Web service is not deployed by default with Oracle Identity Manager 11g Release 1 (11.1.1). SPML-DSML binaries are bundled with the Oracle Identity Manager installer to support Microsoft Active Directory Password Synchronization. You must deploy the spml-dsml.ear file manually.

31.2.51 New Human Tasks Must Be Copied in SOA Composites

When you add a new human task to an existing SOA composite, you must ensure that all the copy operations for the attributes in the original human task are added to the new human task. Otherwise, an error could be displayed on the View Task Details page.

31.2.52 Modify Provisioned Resource Request Does Not Support Service Account Flag

A regular account cannot be changed to a service account, and similarly, a service account cannot be changed to a regular account through a Modify Provisioned Resource request.

31.2.53 Erroneous "Query by Example" Icon in Identity Administration Console

In the Identity Administration console, when viewing role details from the Members tab, an erroneous icon with the "tooltip" (mouse-over text) of "Query By Example" appears. This "Query By Example" icon is non-functional and should be ignored.

31.2.54 The XL.ForcePasswordChangeAtFirstLogin System Property Is No Longer Used

The XL.ForcePasswordChangeAtFirstLogin system property is no longer used in Oracle Identity Manager 11g Release 1 (11.1.1.1). Therefore, forcing the user to change the password at first login cannot be configured. By default, the user must change the password:

- When the new user, other than self-registered users, is logging in to Oracle Identity Manager for the first time

- When the user is logging in to Oracle Identity Manager for the first time after the password has been reset

31.2.55 The tcExportOperationsIntf.findObjects(type,name) API Does Not Accept the Asterisk (*) Wilcard Character in Both Parameters

The tcExportOperationsIntf.findObjects(type,name) API accepts the asterisk (*) wildcard character only for the second parameter, which is name. For type, a category must be specified. For example, findObjects("Resource","*") is a valid call, but findObjects("*","*") is not valid.

31.2.56 Disabled Links on the Access Policy Summary Page Opened in Mozilla FireFox

In the Verify Information for this Access Policy page of the Create/Modify Access Policy wizards opened in Mozilla Firefox Web browser, you click Change for resource to be provisioned by the access policy, and then click Edit to edit the process form data for the resources to be provisioned. If you click the Close button on the Edit form, then the change links for any one of the access policy information sections, such as resources to be provisioned by the access policy, resources to be denied by the access policy, or roles for the access policy, do not work.

To workaround this issue, click Refresh. All the links in the Verify Information for this Access Policy page are enabled.

31.2.57 Benign Error is Generated on Editing the IT Resource Form in Advanced Administration

When you click the Edit link on the IT Resource form in the Advanced Administration, the following error message is logged:

<Error> <XELLERATE.APIS> <BEA-000000>
<Class/Method: tcFormDefinitionOperationsBean/getFormFieldPropertyValue encounter some problems: Property 'Column Names' has not defined for the form field '-82'>

The error message is benign and can be ignored because there is no loss of functionality.

31.2.58 User Account is Not Locked in iPlanet Directory Server After it is Locked in Oracle Identity Manager

After reaching the maximum login attempts, a user is locked in Oracle Identity Manager. But in iPlanet DS/ODSEE, the user is not locked. The orclAccountLocked feature is not supported because the backend iPlanet DS/ODSEE does not support account unlock by setting the Operational attribute. Account is unlocked only with a password reset. The nsaccountlock attribute is available for administrative lockout. The password policies do not use this attribute, but you can use this attribute to independently lock an account. If the password policy locks the account, then nsaccountlock locks the user even after the password policy lockout is gone.

31.2.59 Oracle Identity Manager Does Not Support Autologin With JavaAgent

In an Oracle Access Manager (OAM) integrated deployment of Oracle Identity Manager with JavaAgent, when a user created in Oracle Identity Manager tries to login to the Oracle Identity Manager Administrative and User Console for the first time, the user is forced to reset password and set challenge questions. After this, the user is not logged in to Oracle Identity Manager automatically, but is redirected to the OAM login page. This is because Oracle Identity Manager does not support autologin when JavaAgent is used.

31.2.60 Benign Error Logged on Opening Access Policies, Resources, or Attestation Processes

As a delegated administrator, when you open the page to display the details of an access policy, resource, or attestation process, the following error is logged:

Error> <org.apache.struts.tiles.taglib.InsertTag> <BEA-000000>
<Can't insert page '/gc/EmptyTiles.jsp' : Write failed: Broken pipe  java.net.SocketException: Write failed: Broken pipe

The error is benign and can be ignored because there is no loss of functionality.

31.2.61 User Locked in Oracle Identity Manager But Not in LDAP

In a LDAP-enabled deployment of Oracle Identity Manager in which the directory servers are Microsoft Active Directory (AD) or Oracle Internet Directory (OID), when a user is manually locked in Oracle Identity Manager by the administrator, the user is not locked in LDAP if a password policy is not configured in LDAP. The configurable password policy in LDAP can either be the default password policy that is applicable to all the LDAP users, or it can be a user-specific Password Setting Object (PSO).

31.2.62 Reconciliation Profile Must Not Be Regenerated Via Design Console for Xellerate Organization Resource Object

By default, the Xellerate Organization resource object does not have reconciliation to Oracle Identity Manager field mappings and any matching/action rule information. As a result, when reconciliation profile for Xellerate Organization resource object is updated via Design Console, it corrupts the existing reconciliation configuration for that resource object, and reconciliation fails with empty status.

To workaround this issue, do not generate the reconciliation profile/configuration via the Design Console. Instead, export the Xellerate Organization profile from Meta Data Store (MDS) and edit it manually, and import it back into Oracle Identity Manager. If the profile changes include modification of the reconciliation fields, then the corresponding changes must be made in the horizontal table schema and its entity definition as well.

31.2.63 Benign Error Logged on Clicking Administration After Upgrade

After upgrading Oracle Identity Manager from Release 9.1.0.1 to 11g Release 1 (11.1.1), on clicking the Administration link on the Administrative and User Console, the following error is logged:

<Error> <oracle.adfinternal.view.page.editor.utils.ReflectionUtility>
<WCS-16178> <Error instantiating class - oracle.adfdtinternal.view.faces.portlet.PortletDefinitionDTFactory>

This error is benign and can be ignored because there is no loss of functionality.

31.2.64 Provisioning Fails Through Access Policy for Provisioned User

When a user is already provisioned and you try to assign a role to the user that triggers provisioning to the target domain, the provisioning is not started. However, if the user is not provisioned already and you assign a role to the user, then the provisioning occurs successfully.

To workaround this issue:

1. Open the connector-specific user form in the Design Console.

2. Create a new version of the connector, and select Edit.

3. Click the Properties tab, and then click server (ITResourceLookupField). Click Add Property.

4. Add Required for the property and specify true. Click Make Version Active, and then click Save.

5. Login to Oracle Identity Manager Administrative and User Console.

6. Navigate to System Property. Search for the 'Allows access policy based provisioning of multiple instances of a resource' system property. Change the value of this property to TRUE.

7. Restart Oracle Identity Manager.

Try provisioning a provisioned user to provision through access policy of the same IT Resource Type, and the provisioning is successful.

31.2.65 Benign Warning Messages Displayed During Oracle Identity Manager Managed Server Startup

Several messages resembling the following are logged during Oracle Identity Manager managed server startup:

<Mar 30, 2011 6:51:01 PM PDT> <Warning> <oracle.iam.platform.kernel.impl>
<IAM-0080071>
<Preview stage is not supported in kernel and found an event handler with name ProvisionAccountPreviewHandler implemented by the class oracle.iam.accesspolicy.impl.handlers.provisioning.ProvisionAccountPreviewHandlerfor this stage. It will be ignored.>

These warning messages are benign and can be ignored because there is no loss of functionality.

31.2.66 Benign Message Displayed When Running the Deployment Manager

When running the Deployment Manager, a message with header ' XUL SYNTAX: ID Conflict' is displayed.

This message is benign and can be ignored because there is no loss of functionality. Close the message and continue.

31.2.67 Deployment Manager Export Fails When Started Using Microsoft Internet Explorer 7 With JRE Plugin 1.6_23

After upgrading Oracle Identity Manager from an earlier release to 11g Release 1 (11.1.1), when you use the Microsoft Internet Explorer 7 Web browser with JRE plugin 1.6_23 to open the Administrative and User Console and try to export files by using the Deployment Manager, an error is generated and you cannot proceed with the export.

To workaround this issue, use a combination of the following Web browsers and plugins:

- Mozilla Firefox 3.6 and JRE version 1.6_23 on 64-bit computer

- Microsoft Internet Explorer 7 and JRE version 1.5

- Microsoft Internet Explorer 8 and JRE version 1.6_18

- Microsoft Internet Explorer 7 and JRE version 1.6_24

31.2.68 User Creation Fails in Microsoft Active Directory When Value of Country Attribute Exceeds Two Characters

In a LDAP-enabled deployment of Oracle Identity Manager, user creation fails in the Microsoft Active Directory (AD) server if the value of the Country attribute exceeds two characters. AD mandates two characters for the Country attribute, for example US, based on the ISO 3166 standards.

31.2.69 Deployment Manager Import Fails if Scheduled Job Entries Are Present Prior To Scheduled Task Entries in the XML File

In Oracle Identity Manager 11g Release 1 (11.1.1), schedules job has a dependency on scheduled task. Therefore, scheduled task must be imported prior to scheduled job.

As a result, if a XML file has scheduled job entries prior to scheduled task entries, then importing the XML file using Deployment Manager fails with the following error message:

[exec] Caused By: oracle.iam.scheduler.exception.SchedulerException: Invalid ScheduleTask definition
[exec] com.thortech.xl.ddm.exception.DDMException

To workaround this issue, open the XML file and move all scheduled task entries above the scheduled job entries.

31.2.70 Permission on Target User Required to Revoke Resource

When you login to the Administrative and User Console with Identity User Administrators and Resource Administrators roles, direct provision a resource to a user, and attempt to revoke the resource from the user, an error message is displayed.

To workaround this issue, you (logged-in user) must have the write permission on the target user (such as user1). To achieve this:

1. Create a role, such as role1, and assign self to this role.

2. Create an organization, such as org1, and assign role1 as administrative group.

3. Modify the user user1 and change its organization to org1. You can now revoke the resource from user1.

31.2.71 Reconciliation Event Fails for Trusted Source Reconciliation Because of Missing Reconciliation Rule in Upgraded Version of Oracle Identity Manager

When Oracle Identity Manager is upgraded from an earlier release to 11g Release 1 (11.1.1), for trusted source reconciliation, such as trusted source reconciliation using GTC, the reconciliation event fails with the following error message because of a missing reconciliation rule:

<Mar 31, 2011 6:27:41 PM CDT> <Info> <oracle.iam.reconciliation.impl>
<IAM-5010006> <The following exception occurred: {0}
oracle.iam.platform.utils.SuperRuntimeException:
Error occurred in XL_SP_RECONEVALUATEUSER while processing Event No 3
Error occurred in XL_SP_RECONUSERMATCH while processing Event No 3
One or more input parameter passed as null

To workaround this issue:

1. Create a reconciliation rule for the resource object.

2. In the Resource Object form of the Design Console, click Create Reconciliation Profile.

31.2.72 XML Validation Error on Oracle Identity Manager Managed Server Startup

The following error message is logged at the time of Oracle Identity Manager Managed Server startup:

<Mar 29, 2011 2:49:31 PM PDT> <Error> <oracle.iam.platform.kernel.impl>
<IAM-0080075> <XML schema validation failed for XML/metadata/iam-features-callbacks/event_configuration/EventHandlers.xml and it will not be loaded by kernel. >

<Mar 29, 2011 2:49:32 PM PDT> <Error> <oracle.iam.platform.kernel.impl>
<IAM-0080075> <XML schema validation failed for XML/metadata/iam-features-OIMMigration/EventHandlers.xml and it will not be loaded by kernel. >

This error message is benign and can be ignored because there is no loss of functionality.

31.2.73 Cannot View or Edit Adapter Mapping in the Data Object Manager Form of the Design Console

When you click Map on the Map Adapters tab in the Data Object Manager form of the Design Console, a dialog box is displayed that allows you to edit the individual entity adapter mappings. But the list with fields on the user object to map is displayed as empty. As a result, you cannot view or edit the individual entity adapter mappings.

Use of entity adapters is deprecated in Oracle Identity Manager 11g Release 1 (11.1.1), although limited support is still provided for backward compatibility only. Event handlers must be used for all new or changed scenarios.

31.2.74 Role Memberships for Assign or Revoke Operations Not Updated on Enabling or Disabling Referential Integrity Plug-in

In a multi-directory deployment, the secondary server must be OID. The primary server can be OID or AD. For example, users can be stored in the OID or AD primary server, and roles can be stored in the OID secondary server. Enabling of disabling the referential integrity plug-in does not update the role memberships for assign or revoke operations.

31.2.75 Deployment Manager Import Fails if Data Level for Rules is Set to 1

An entry in the Oracle Identity Manager database cannot be updated if data level is set to 1. When you try to import a Deployment Manager XML, the following error is displayed:

Class/Method: tcTableDataObj/updateImplementation Error :The row cannot be updated.
[2011-04-06T07:25:36.583-05:00] [oim_server1] [ERROR] []
[XELLERATE.DDM.IMPORT] [tid: [ACTIVE].ExecuteThread: '6' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid:
cad00d8aeed4d8fc:-67a4db1a:12f2abbac4b:-8000-000000000000018e,0] [APP:
oim#11.1.1.3.0] The security level for this data item indicates that it cannot be updated.

To workaround this issue, open the XML file and change the data level for rules from 1 to 0, as shown:

<RUL_DATA_LEVEL>0</RUL_DATA_LEVEL>

31.2.76 Reconciliation Data Displays Attributes That Are Not Modified

In an Oracle Identity Manager deployment with LDAP synchronization enabled and Microsoft Active Directory (AD) as the directory server, the Reconciliation Data tab of the Event Management page in the Administrative and User Console displays all the attributes of the reconciled user instead of displaying only the modified attributes. This is because of the way AD changelogs are processed, in which the entire entry is marked as updated when any attribute is changed. Therefore, Oracle Virtual Directory (OVD) returns the full entry. There is no way to figure out which attribute has been modified as a result of reconciliation.

31.2.77 Benign Errors Displayed on Starting the Scheduler Service When There are Scheduled Jobs to be Recovered

When the Scheduler service is started and there are some scheduled jobs that have not been recovered, the following error might be logged in the oim_diagnostic log:

Caused by: java.lang.NullPointerException
at
org.quartz.SimpleTrigger.computeNumTimesFiredBetween(SimpleTrigger.java:800)
at org.quartz.SimpleTrigger.updateAfterMisfire(SimpleTrigger.java:514)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.doUpdateOfMisfiredTrigger(JobStor
eSupport.java:944)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.recoverMisfiredJobs(JobStoreSuppo
rt.java:898)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.recoverJobs(JobStoreSupport.java:
780)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport$2.execute(JobStoreSupport.java:75
2)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport$40.execute(JobStoreSupport.java:3
628)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStor
eSupport.java:3662)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStor
eSupport.java:3624)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.recoverJobs(JobStoreSupport.java:
748)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.schedulerStarted(JobStoreSupport.
java:573)

This error is benign and can be ignored because there is no loss of functionality.

In an upgrade environment, the next time when some scheduled jobs will be triggered is not defined. This results in a null input for Quartz code, which is not handled gracefully in earlier versions of Quartz. This has been fixed in Quartz version 1.6.3, and therefore, this error is not generated when you upgrade to that version of Quartz.

31.2.78 Trusted Source GTC Reconciliation Mapping Cannot Display Complete Attribute Names

When creating a trusted GTC (for example, flat file), the right-hand column under OIM User is not wide enough to display the complete names for many attributes. For example, two entries are displayed as 'LDAP Organizati', whereas the attribute names are 'LDAP Organization' and 'LDAP Organization Unit'.

To workaround this issue, click the Mapping button for the attribute. The Provide Field Information dialog box is displayed with the complete attribute name.

31.2.79 Benign Error Logged for Database Connectivity Test

When running the database connectivity test in XIMDD, the following error is logged multiple times:

<Apr 10, 2011 7:45:20 PM PDT> <Error> <Default> <J2EE JMX-46335> <MBean attribute access denied.
MBean: oracle.logging:type=LogRegistration
Getter for attribute Application
Detail: Access denied. Required roles: Admin, Operator, Monitor, executing
subject: principals=[REQUEST TEMPLATE ADMINISTRATORS, SYSTEM ADMINISTRATORS, APPROVAL POLICY ADMINISTRATORS, oimusers, xelsysadm, PLUGIN ADMINISTRATORS]
java.lang.SecurityException: Access denied. Required roles: Admin, Operator, Monitor, executing subject: principals=[REQUEST TEMPLATE ADMINISTRATORS, SYSTEM ADMINISTRATORS, APPROVAL POLICY ADMINISTRATORS, oim users, xelsysadm, PLUGIN ADMINISTRATORS]

Each time the error occurs in the log, the name of the bean is different, but the error is same. In spite of these errors, the test passes. These errors are benign and can be ignored because there is no loss of functionality.

31.2.80 MDS Validation Error When Importing GTC Provider Through the Deployment Manager

An MDS validation error is generated when you import the GTC provider by using the Deployment Manager.

To workaround this issue, do not import the GTC provider through the Deployment Manager. If the Deployment Manager XML file contains tags for GTC provider, then remove it and import the rest of the XML by using the Deployment Manager. Import the XML file with the GTC provider tags separately by using the MDS import utility. To do so:

1. If the XML file being imported through the Deployment Manager contains <GTCProvider> tags, then remove these tags along with everything under them.
The following is an example of the original XML file to be imported:

<?xml version = '1.0' encoding = 'UTF-8'?>
<xl-ddm-data version="2.0.1.0" user="XELSYSADM"
database="jdbc:oracle:thin:@localhost:5521:myps12"
exported-date="1302888552341" description="sampleGTC"><GTCProvider
repo-type="MDS" name="InsertIntoTargetList"
mds-path="/db/GTC/ProviderDefinitions"
mds-file="InsertIntoTargetListProvTransport.xml"><completeXml><Provider><Provi
der>
<Provisioning>
<ProvTransportProvider
class="provisioningTransportProvider.InsertIntoTargetList"
name="InsertIntoTargetList">
<Configuration>
<Parameter datatype="String" name="targetServerName"
type="Runtime" encrypted="NO" required="YES"/>
<Response code="FUNCTIONALITY_NOT_SUPPORTED"
description="Functionality not supported"/>
<Response code="TARGET_SERVER_NAME_MISSING" description="Target
server name is missing"/>
<Response code="TARGET_SERVER_NAME_STARTSWITH_A"
description="Target server name starts with A, from XML"/>
<Response code="PROBLEM_WHILE_INITIALIZAING" description="Problem
occured while intializing Provider instance"/>
</Configuration>
</ProvTransportProvider>
</Provisioning>
</Provider></Provider></completeXml></GTCProvider><GTCProvider
repo-type="MDS" name="PrepareDataHMap" mds-path="/db/GTC/ProviderDefinitions"
mds-file="PrepareDataHMapProvFormat.xml"><completeXml><Provider><Provider>
<Provisioning>
<ProvFormatProvider class="provisioningFormatProvider.PrepareDataHMap"
name="PrepareDataHMap">
<Configuration>
<DefaultAttribute datatype="String" name="testField" size="40"
encrypted="NO"/>
<Response code="INCORRECT_PROCESS_DATA" description="Incorrect
process data received from GTC provisioning framework"/>
<Response code="PROCESSING_ISSUE" description="Processing issue
in Preparing provisioning input, check logs"/>
</Configuration>
</ProvFormatProvider>
</Provisioning>
</Provider></Provider></completeXml></GTCProvider><GTCProvider
repo-type="MDS" name="IsValidOrgInOIM" mds-path="/db/GTC/ProviderDefinitions"
mds-file="IsValidOrgInOIM.xml"><completeXml><Provider><Provider>
<Validation>
<ValidationProvider class="validationProvider.IsValidOrgInOIM"
name="IsValidOrgInOIM">
<Configuration>
<Parameter datatype="String" name="maxOrgSize"/>
</Configuration>
</ValidationProvider>
</Validation>
</Provider></Provider></completeXml></GTCProvider><GTCProvider
repo-type="MDS" name="ConvertToUpperCase"
mds-path="/db/GTC/ProviderDefinitions"
mds-file="ConvertToUpperCase.xml"><completeXml><Provider><Provider>
<Transformation>
<TransformationProvider
class="transformationProvider.ConvertToUpperCase" name="ConvertToUpperCase">
<Configuration>
<Parameter type="Runtime" datatype="String" required="YES"
encrypted="NO" name="Input"/>
<Response code="errorRespNullInput" description="Input String is
Missing"/>
</Configuration>
</TransformationProvider>
</Transformation>
</Provider></Provider></completeXml></GTCProvider><Resource repo-type="RDBMS"
name="SAMPLEGTC_GTC">....</Resource><Process repo-type="RDBMS"
name="SAMPLEGTC_GTC">
...........
</Process><Form repo-type="RDBMS" name="UD_SAMPLEGT" subtype="Process
Form">.....
</Form>....</xl-ddm-data>

2. Import the rest of the XML file through the Deployment Manager.
The following is the XML file after removing the <GTCProvider> tags from the original XML file. Import this XML file by using the Deployment Manager.

<?xml version = '1.0' encoding = 'UTF-8'?>
<xl-ddm-data version="2.0.1.0" user="XELSYSADM"
database="jdbc:oracle:thin:@localhost:5521:myps12"
exported-date="1302888552341" description="sampleGTC"><Resource
repo-type="RDBMS" name="SAMPLEGTC_GTC">....</Resource><Process
repo-type="RDBMS" name="SAMPLEGTC_GTC">
...........
</Process><Form repo-type="RDBMS" name="UD_SAMPLEGT" subtype="Process
Form">.....
</Form>....</xl-ddm-data>

The following is the removed XML content:

<GTCProvider
repo-type="MDS" name="InsertIntoTargetList"
mds-path="/db/GTC/ProviderDefinitions"
mds-file="InsertIntoTargetListProvTransport.xml"><completeXml><Provider><Provider>
<Provisioning>
<ProvTransportProvider
class="provisioningTransportProvider.InsertIntoTargetList"
name="InsertIntoTargetList">
<Configuration>
<Parameter datatype="String" name="targetServerName"
type="Runtime" encrypted="NO" required="YES"/>
<Response code="FUNCTIONALITY_NOT_SUPPORTED"
description="Functionality not supported"/>
<Response code="TARGET_SERVER_NAME_MISSING" description="Target
server name is missing"/>
<Response code="TARGET_SERVER_NAME_STARTSWITH_A"
description="Target server name starts with A, from XML"/>
<Response code="PROBLEM_WHILE_INITIALIZAING" description="Problem
occured while intializing Provider instance"/>
</Configuration>
</ProvTransportProvider>
</Provisioning>
</Provider></Provider></completeXml></GTCProvider>

<GTCProvider
repo-type="MDS" name="PrepareDataHMap" mds-path="/db/GTC/ProviderDefinitions"
mds-file="PrepareDataHMapProvFormat.xml"><completeXml><Provider><Provider>
<Provisioning>
<ProvFormatProvider class="provisioningFormatProvider.PrepareDataHMap"
name="PrepareDataHMap">
<Configuration>
<DefaultAttribute datatype="String" name="testField" size="40"
encrypted="NO"/>
<Response code="INCORRECT_PROCESS_DATA" description="Incorrect
process data received from GTC provisioning framework"/>
<Response code="PROCESSING_ISSUE" description="Processing issue
in Preparing provisioning input, check logs"/>
</Configuration>
</ProvFormatProvider>
</Provisioning>
</Provider></Provider></completeXml></GTCProvider>

<GTCProvider
repo-type="MDS" name="IsValidOrgInOIM" mds-path="/db/GTC/ProviderDefinitions"
mds-file="IsValidOrgInOIM.xml"><completeXml><Provider><Provider>
<Validation>
<ValidationProvider class="validationProvider.IsValidOrgInOIM"
name="IsValidOrgInOIM">
<Configuration>
<Parameter datatype="String" name="maxOrgSize"/>
</Configuration>
</ValidationProvider>
</Validation>
</Provider></Provider></completeXml></GTCProvider>

<GTCProvider
repo-type="MDS" name="ConvertToUpperCase"
mds-path="/db/GTC/ProviderDefinitions"
mds-file="ConvertToUpperCase.xml"><completeXml><Provider><Provider>
<Transformation>
<TransformationProvider
class="transformationProvider.ConvertToUpperCase" name="ConvertToUpperCase">
<Configuration>
<Parameter type="Runtime" datatype="String" required="YES"
encrypted="NO" name="Input"/>
<Response code="errorRespNullInput" description="Input String is
Missing"/>
</Configuration>
</TransformationProvider>
</Transformation>
</Provider></Provider></completeXml></GTCProvider>

3. Separate the removed XML content based on the <GTCProvier> tags. The following is an example of the first <GTCProvider> tag:

<GTCProvider repo-type="MDS" name="InsertIntoTargetList"
mds-path="/db/GTC/ProviderDefinitions"
mds-file="InsertIntoTargetListProvTransport.xml"><completeXml><Provider><Provi
der>
<Provisioning>
<ProvTransportProvider
class="provisioningTransportProvider.InsertIntoTargetList"
name="InsertIntoTargetList">
<Configuration>
<Parameter datatype="String" name="targetServerName"
type="Runtime" encrypted="NO" required="YES"/>
<Response code="FUNCTIONALITY_NOT_SUPPORTED"
description="Functionality not supported"/>
<Response code="TARGET_SERVER_NAME_MISSING" description="Target
server name is missing"/>
<Response code="TARGET_SERVER_NAME_STARTSWITH_A"
description="Target server name starts with A, from XML"/>
<Response code="PROBLEM_WHILE_INITIALIZAING" description="Problem
occured while intializing Provider instance"/>
</Configuration>
</ProvTransportProvider>
</Provisioning>
</Provider></Provider></completeXml></GTCProvider>
Resultant xml after removal of tags surronding inner <Provider> tag:
<Provider>
<Provisioning>
<ProvTransportProvider
class="provisioningTransportProvider.InsertIntoTargetList"
name="InsertIntoTargetList">
<Configuration>
<Parameter datatype="String" name="targetServerName"
type="Runtime" encrypted="NO" required="YES"/>
<Response code="FUNCTIONALITY_NOT_SUPPORTED"
description="Functionality not supported"/>
<Response code="TARGET_SERVER_NAME_MISSING" description="Target
server name is missing"/>
<Response code="TARGET_SERVER_NAME_STARTSWITH_A"
description="Target server name starts with A, from XML"/>
<Response code="PROBLEM_WHILE_INITIALIZAING" description="Problem
occured while intializing Provider instance"/>
</Configuration>
</ProvTransportProvider>
</Provisioning>
</Provider>

4. From the removed <GTCProvider> tags, remove everything surrounding the inner <Provider> tag. In other words, keep the content inside the inner <Provider> tag. For each <Provider> tag, create a separate XML file. This results in multiple XML files with each <Provider> tag as the root element.
The following is the resultant XML content after removal of tags surrounding the inner <Provider> tag:

<Provider>
<Provisioning>
<ProvTransportProvider
class="provisioningTransportProvider.InsertIntoTargetList" name="InsertIntoTargetList">
<Configuration>
<Parameter datatype="String" name="targetServerName" type="Runtime" encrypted="NO" required="YES"/>
<Response code="FUNCTIONALITY_NOT_SUPPORTED" description="Functionality not supported"/>
<Response code="TARGET_SERVER_NAME_MISSING" description="Target server name is missing"/>
<Response code="TARGET_SERVER_NAME_STARTSWITH_A" description="Target server name starts with A, from XML"/>
<Response code="PROBLEM_WHILE_INITIALIZAING" description="Problem occured while intializing Provider instance"/>
</Configuration>
</ProvTransportProvider>
</Provisioning>
</Provider>

5. Name the resultant XML files, which have the <Provider> tag as the root element, with the mds-file attribute value from the <GTCProvider> tag. For example, name the first XML file with the first <GTCProvider> tag as InsertIntoTargetListProvTransport.xml. The file name must be the value of the mds-file attribute.

6. Similarly, create other GTC provider XML files. There must be one XML file for each <GTCProvider> tag.

7. Import the GTC Provider XML files by using the MDS utility.

31.2.81 Encrypted User-Defined Field (UDF) Cannot be Stored with Size of 4000 Characters or More

An encrypted UDF cannot be stored with size of 4000 characters or more. This is because encryption automatically increases the column width by 1.5 times approximately, and the size of the attribute exceeds the maximum allowable width of 4000. As a result, the UDF is automatically type-promoted to a CLOB data type. Oracle Identity Manager 11g Release 1 (11.1.1) does not intercept this as an exception and might subsequently show errors. This is likely to be addressed in the next patch release.

However, an encrypted attribute that does not exceed the final width of 4000 characters can be stored. The specified width must factor in the increment of 1.5 times, which means that it must not exceed approximately 2500 characters.

31.2.82 Request Approval Fails With Callback Service Failure

In an environment where SSL is enabled in the OAAM server but not in Oracle Identity Manager and SOA server, when you create a request, the request-level approval is successful on the SOA side, but the operational-level approval is not displayed anywhere in the UI. When the SOA composite that provides approval workflow for the Oracle Identity Manager request tries to invoke the request callback Web service to indicate whether the workflow is approved or rejected, the Web service invocation fails with the following error:

Unable to dispatch request to
http://slc402354.mycompany.com:14000/workflowservice/CallbackService due to exception[[
javax.xml.ws.WebServiceException:
oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-06162
PolicyReference The policy referenced by URI
"oracle/wss11_saml_token_with_message_protection_client_policy" could not be
retrieved as connection to Policy Manager cannot be established at
"t3s://slc402354:14301" due to invalid configuration or inactive state.

The error indicates that OWSM is not able to connect to the Policy Manager on the specified port. This port is for the OAAM server in SSL mode, which is shut down. The issue occurs because SSL is enabled in the OAAM server but not on Oracle Identity Manager and SOA server, and the Policy Manager is also targeted on that server. If there is an SSL-enabled Policy Manager, then OWSM does not use the non-SSL ports anymore. In this setup, SSL is enabled only for OAAM and not for others. Therefore, the only usable WSM Policy Manager is on OAAM. Because the OAAM server is down, the connection to the Policy Manager is not established, and as a result, the call fails.

To workaround this issue, start the OAAM server and then create the request.

Note:

This issue does not occur if:

- OAAM server is not SSL-enabled.

- SSL is enabled on any other server that is up and running, such as Oracle Identity Manager or SOA server.

31.2.83 Localized Display Name is Not Reconciled Via User/Role Incremental Reconciliation with iPlanet Directory Server

In an Oracle Identity Manager deployment with LDAP synchronization enabled in which iPlanet is the directory server, the following issues occur:

- The localized Display Name is not reconciled into Oracle Identity Manager via user/role incremental reconciliation.

- The localized value of the Display Name attribute is returned to Oracle Identity Manager, but the original base value of Display Name is lost and is replaced by the localized value that is received from iPlanet.

31.2.84 LDAP Role Hierarchy and Role Membership Reconciliation With Non-ASCII Characters Does Not Reconcile Changes in Oracle Identity Manager

LDAP role hierarchy and role membership reconciliation jobs with non-ASCII characters do not bring in role hierarchy and role membership changes into Oracle Identity Manager. This issue is applicable to incremental reconciliation only.

31.2.85 Import of Objects Fails When All Objects Are Selected for Export

In an upgraded environment of Oracle Identity Manager 11g Release 1 (11.1.1), the import of objects can fail when you select the Select All option to export the objects. When you select all the objects to be exported, the corresponding XML file grows in size. If it exceeds 2.5 million records, then it does not remain valid. As a result, the import fails. However, selecting all objects works if the data is small and the generated XML file does not exceed 2.5 million records.

To workaround this issue, select the objects to be exported in smaller logical units. For example, if there are 20 resource objects in the system, then select four or five resource objects with all dependencies and children objects in a XML file, and export. Then select another five resource objects into a new XML file. Similarly, for all other objects, such as GTC or adapters, export in small logical units in separate XML files. Examples of logical unit grouping are:

- Resource objects, process definition forms, adapters, IT resources, lookup definitions, and roles

- Organizations, attestation, and password policies

- Access policies and rules

- GTC and resource objects

31.2.86 Benign Audit Errors Logged After Upgrade

After upgrading from Oracle Identity Manager Release 9.1.0 to 11g Release 1 (11.1.1), audit errors are logged. An example of such an audit error is:

IAM-0050001
oracle.iam.platform.async.TaskExecutionException: java.lang.Exception: Audit
handler failed
at com.thortech.xl.audit.engine.jms.XLAuditMessage.execute(XLAuditMessage.java:59)

These errors are benign and can be ignored because there is no loss of functionality.

31.2.87 Connector Upgrade Fails if Existing Data is Bigger in Size Than New Column Length

In the current release of some connectors, the sizes of some process form fields have been reduced. For example, the length of the UD_ADUSER_MNAME field in the Microsoft Active Directory connector release 9.1.1.5 has been reduced to 6 characters from 80 characters in release 9.0.4.16 of the connector. The length of the existing data in these columns or fields are already bigger in size than the new column length. As a result, the connector upgrade fails, and the following error is logged:

<Apr 16, 2011 4:52:37 PM GMT+05:30> <Error> <XELLERATE.DATABASE> <BEA-000000>
<ALTER TABLE UD_ADUSER MODIFY UD_ADUSER_MNAME VARCHAR2(6) java.sql.SQLException: ORA-01441: cannot decrease column length because some value is too big

To workaround this issue:

1. Make sure that you create a backup of the database.

2. Restore the backed up database.

3. Check the logs to locate the 'ORA-01441: cannot decrease column length because some value is too big' exception. Note the form field name, such as UD_ADUSER_MNAME.

4. Open the Deployment Manager XML file that you are using for upgrade. Search for the form field in the <SDC_SQL_LENGTH> tag, and change the length to the base version length. You can get the base version length in the Deployment Manager XML of the base connector.

5. Retry the upgrade.

31.2.88 Connector Artifacts Count Increases in the Deployment Manager When File is Not Imported

When you upgrade a connector, map the connector artifacts between the base and latest versions, select the connector objects to be upgraded, and exit the upgrade without importing the objects by using the Deployment Manager, the connector artifacts count in the left panel displays more than the actual count. When this process is repeated, the artifacts count continues increasing. This is a known issue, and there is no loss of functionality.

31.2.89 Uploading JAR Files By Using the Upload JAR Utility Fails

When SSL is enabled for Oracle Identity Manager, uploading the JAR files by using the Upload JAR utility fails with the following error:

Error occurred in performing the operation:
Exception in thread "main" java.lang.NullPointerException at oracle.iam.platformservice.utils.JarUploadUtility.main(JarUploadUtility.java:229)

With SSL enabled in Oracle Identity Manager, the server URL must contain the exact host name or IP address. If localhost is used as the host name, then the error is generated.

To workaround this issue, use the exact server URL.

31.2.90 Oracle Identity Manager Data and MT Upgrade Fails Because Change of Database User Password

If you are NOT upgrading the original Oracle Identity Manager Release 9.x database, but choose to export/import to a new database, then you must make sure that the database connection setting, schema name, and password in the OIM_HOME/xellerate/config/xlconfig.xml file used for the upgrade is correct.

To workaround this issue, change the Oracle Identity Manager database information in the xlconfig.xml file. You must create a backup of this file before updating it. To update the file with the new database information, modify the information of the loaction where the database has been imported in the <URL>, <username>, and <Password ...> tags, as shown:

<DirectDB>
<driver>oracle.jdbc.driver.OracleDriver</driver>
<url>jdbc:oracle:thin:@localhost:1522:oimdb</url>
<username>oimadm</username>
<password encrypted="false"><NEW_PASSWORD_FOR_OIM_DB_USER></password>
<maxconnections>5</maxconnections>
<idletimeout>360</idletimeout>
<checkouttimeout>1200</checkouttimeout>
<maxcheckout>1000</maxcheckout>
</DirectDB>

31.2.91 Reverting Unsaved UDFs Are Not Supported in the Administration Details Page for Roles and Organizations

The Administration Details pages for roles and organizations in the Administrative and User Console do not support reverting unsaved UDF attribute values. Therefore, if you modify the UDF attribute values for a role or organization and then do not want to save the changes to these attributes, then perform one of the following:

- Close the tab with the modified role or organization. A warning message is displayed asking if you want to continue. Clicking Yes cancels all unsaved changes.

- You can manually edit the modified attributes to their original state. Saving the entity applies any other desired changes made.

31.2.92 Resources Provisioned to User Without Checking Changes in User Status After Request is Submitted

After submission of a request, if the user associated with the request, such as beneficiary, requester, or approver, is disabled or deleted, then the resources are provisioned to the user without checking for user status, such as Disabled or Deleted, after the request is approved.

31.2.93 Config.sh Command Fails When JRockit is Installed With Data Samples and Source

When you install jrockit-jdk1.6.0_24-R28.1.3-4.0.1-linux-x64.bin with demo samples and source, and install Oracle WebLogic Server using wls1035_generic.jar on a Linux 64-bit computer, and run Oracle Identity Manager configuration wizard by running the config.sh command from the $ORACLE_HOME/bin/ directory, the Oracle universal installer does not start and the following error message is displayed:

config.sh: line 162:  9855 Segmentation fault $INSTALLER_DIR/runInstaller-weblogicConfig ORACLE_HOME="$ORACLE_HOME" -invPtrLoc$ORACLE_HOME/oraInst.loc -oneclick $COMMANDLINE -Doracle.config.mode=true

31.2.94 Unexpected Memory Usage in Oracle Identity Manager 11g Release 1(11.1.1)

On running scheduled tasks that perform user orchestration in bulk, such as EndDateSchedulerTask and StartDateSchedulerTask, Oracle Identity Manager 11g Release 1 (11.1.1) might consume large memory space. This can cause Out of Memory issues.

This is a known issue, and a workaround is not available for this in the current release.

31.2.95 Reports Link No Longer Exists in the Administrative and User Console

Under the Administration tab of the Advanced Administration in the Administrative and User Console, the Reports link to generate BI Publisher Reports has been removed, even though BIP has been selected while installing Oracle Identity Manager.

31.2.96 Not Allowing to Delete a Role Whose Assigned User Members are Deleted

If the user members of a role have been deleted before revoking the role memberships, then the role cannot be deleted. Therefore, you must revoke the user role memberships that have been explicitly assigned before deleting the user.

31.2.97 Roles and Organizations Do Not Support String UDFs of Password Type

Creating a String UDF of password type for roles and organizations is not supported. If you try to create such a UDF, then the Administrative and User Console does not allow you create roles and organizations.

31.2.98 Manage Localizations Dialog Box Does Not Open After Modifying Roles

After a role is modified, the Manage Localizations dialog box is not opening on clicking the Manage Localizations button in the role details page.

To open the Manage Localizations dialog box after modifying a role, close the role details page and open it again.

31.2.99 Not Allowing to Create User With Language-Specific Display Name Values

In an Oracle Identity Manager deployment with Microsoft Active Directory (AD) as the LDAP server, localized display name values are supported when you specify the oimLanguage parameter values in the UserManagement plugin adapter for AD via OVD. However, a user cannot be created when a language-specific value for the Display Name attribute is specified in Canadian French or Latin American Spanish, even if these languages have been specified in oimLanguage. In addition, when you create a user without language-specific Display Name, and then modify the user to add Canadian French or Latin American Spanish Display Name values, the same issue persists.

31.2.100 SoD Check Results Not Displayed for Requests Created by Users for the PeopleSoft Resource

SoD check results are not displayed for the requests created by users for the PeopleSoft (PSFT) resource.

To workaround this issue:

1. Open the PSFT connector XML file.

2. Under the <ITResource name = "PSFT Server"> tag, add the following:

<ITResourceAdministrator>
<SUG_READ>1</SUG_READ>
<SUG_UPDATE>1296129050000</SUG_UPDATE>
<UGP_KEY UserGroup = "ALL USERS"/>
</ITResourceAdministrator>

3. Save the PSFT connector XML file.

4. Manually add or assign the ALL USERS role with Read permission to the PSFT Server IT resource.

31.2.101 The XL.UnlockAfter System Property and the Automatically Unlock User Scheduled Job Do Not Take Effect

The XL.UnlockAfter system property determines the unlock time for the locked user accounts after the specified time. If the user account is locked because of the maximum login attempt failure with invalid credentials, then the account is automatically unlocked after the time (in minutes) as configured in the XL.UnlockAfter system property. By default, the value of this system property is 0, which implies that the locked user is never unlocked automatically.

The Automatically Unlock User scheduled job is responsible for unlocking such users. This scheduled job is configured to run after every 24 hours (1 day).

Therefore, even after the maximum time of Oracle WebLogic lockout threshold and expiry of the time specified for the XL.UnlockAfter system property, the locked users might not be able to login unless the Automatically Unlock User scheduled job is run.

If you are changing the default value of the XL.UnlockAfter system property, then it is recommended to change the frequency of the Automatically Unlock User scheduled task so that both the values are in sync. This ensures that the scheduled task gets triggered at the appropriate interval, and the users are unlocked successfully and are able to login in to Oracle Identity Manager.

31.2.102 Resetting Password on Account Lockout Does Not Unlock User

In a Oracle Identity Manager deployment with LDAP synchronization enabled and integrated with Oracle Access Manager (OAM), a user is locked on entering incorrect password more than the maximum allowed limit. However, the user is not allowed to unlock by resetting the password until after reconciliation is run.

31.2.103 Incremental and Full Reconciliation Jobs Cannot Be Run Together

Both incremental and full reconciliation jobs cannot be run at the same time. Incremental reconciliation jobs are enabled and run in periodic intervals of 5 minutes. At the same time, when full reconciliation job is run, an error is generated.

To workaround this issue, if full reconciliation needs to be run, then disable the incremental reconciliation jobs before running the full reconciliation jobs. After full reconciliation completes successfully, re-enable the incremental reconciliation jobs.

31.2.104 Incorrect Content in the ScheduleTask Jars Loaded and Third Party Jars Tables in the MT Upgrade Report

When Oracle Identity Manager release 9.1.x is upgraded to Oracle Identity Manager 11g Release 1 (11.1.1), the contents of the ScheduleTask Jars Loaded and Third Party Jars tables in the CRBUpgradeReport.html page generated by MT upgrade are not correct. The original scheduled task JARs are not displayed in the ScheduleTask Jars Loaded table. Therefore, you must run the SQL query query to know the scheduled task JARs. In addition, the third-party JARs are incorrectly placed in the ScheduleTask Jars Loaded table.

However, this does not result in any loss of functionality.

31.2.105 Scroll Bar Not Available on the Select Connector Objects to Be Upgraded Page of the Connector Management - Upgrading Wizard

If the Connector Management - Upgrading wizard is opened by using Microsoft Internet Explorer, then all the fields and buttons on the Step 13: Select Connector Objects to Be Upgraded page might not be visible. There is no scroll bar available in this page. Therefore, maximize the window to display all the controls in the page.

31.2.106 Adapter Import Might Display Adapter Logic if Compilation Fails Because of Incorrect Data

If you import a process task adapter by using the Design Console and the adapter compilation fails because of incorrect data, then the error displays the entire code for the adapter.

This is a known issue, and a workaround is not available for this in the current release.

31.2.107 XIMDD Tests Fail in Oracle Identity Manager

After you deploy the Diagnostic Dashboard in Oracle Identity Manager, failures are encountered when you perform the following tests:

- Test OWSM setup by submitting a request with OWSM header information

- Test SPML to Oracle Identity Manager request invocation

The failures might occur because the Diagnostic Dashboard is not capable of performing tests when the wss1_saml_or_username_token_policy is attached to the SPML XSD Web services.

To workaround this issue, set the Web service to use the XIMDD supported policy. To configure the policies for the SPML XSD Web service:

1. Login to Fusion Middleware Control.

2. Navigate to Application Deployments, spml-xsd.

3. For a clustered deployment of Oracle Identity Manager, expand and select a node.

4. From the Application Deployment menu, select Web Services.

5. Click the Web Service Endpoint tab, and then click the SPMLServiceProviderSOAP link.

6. Click the Policies tab, and then click Attach/Detach.

7. Detach the default policy: oracle/wss11_saml_or_username_token_with_message_protection_service_policy.

8. Under Available Policies, select oracle/wss_username_token_service_policy. Otherwise, select the SSL version of the same policy if SSL is in use.

9. Click Attach, and then click OK.

10. For a clustered deployment of Oracle Identity Manager, repeat step 3 through step 9 for each managed node listed for SPML XSD.

11. Restart the application servers.

31.2.108 Error While Installing Oracle Identity Manager

While installing Oracle Identity Manager 11g Release 1 (11.1.1.7.0), the following error message is displayed when a non-root user tries to access the /var/sadm/patch folder:

chmod: WARNING: can't change /var/sadm/patch

The workaround is to ignore the error message as there is no loss in functionality.

31.3 Configuration Issues and Workarounds

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

- Configuring UDFs to be Searchable for Microsoft Active Directory Connectors

- Creating or Modifying Role Names When LDAP Synchronization is Enabled

- ADF Issue Causes Oracle Identity Manager to Fail on the Sun JDK

- Nexaweb Applet Does Not Load In an Oracle Identity Manager and Oracle Access Manager Integrated Environment

- Packing a Domain With managed=false Option

- Option Not Available to Specify if Design Console is SSL-Enabled

- Nexaweb Applet Does Not Load in JDK 1.6.0_20

- Oracle Identity Manager and Design Console Must be Installed in Different Directory Paths

- Error on Adding Organization to User in Windows Explorer 8

31.3.1 Configuring UDFs to be Searchable for Microsoft Active Directory Connectors

A Microsoft Active Directory connector installation automatically creates a UDF: USR_UDF_OBGUID. When you add a new user-defined field (UDF), the "searchable" property will be false by default unless you provide a value for that property. After installing an Active Directory connector, you must perform the following steps to make the user-defined field searchable:

1. Using the Advanced Administration console (user interface), change the "searchable" UDF property to true by performing the following steps:

1. Click the Advanced tab.

2. Select User Configuration and then User Attributes.

3. Modify the USR_UDF_OBGUID attribute in the Custom Attributes section by changing the "searchable" property to true.

2. Using the Identity Administration console (user interface), create a new Oracle Entitlement Server policy that allows searching the UDF by performing the following steps:

1. Click the Administration tab and open the Create Authorization policy.

2. Enter a Policy Name, Description, and Entity Name as User Management.

3. Select Permission, then View User Details, and then Search User.

4. Edit the Attributes for View User Details and select all of the attributes.

5. Select the SYSTEM ADMINSTRATOR role name.

6. Click Finish.

31.3.2 Creating or Modifying Role Names When LDAP Synchronization is Enabled

When LDAP synchronization is enabled and you attempt to create or modify a role, entering a role name comprised of approximately 1,000 characters prevents the role from being created or modified and causes a Decoding Error to appear. To work around this issue, use role names comprised of fewer characters.

31.3.3 ADF Issue Causes Oracle Identity Manager to Fail on the Sun JDK

Due to an ADF issue, using the Oracle Identity Manager application with the Sun JDK causes a StringIndexOutOfBoundsException error. To work around this issue, add the following option to the DOMAIN_HOME/bin/setSOADomainEnv.sh or the setSOADomainEnv.cmd file:

1. Open the DOMAIN_HOME/bin/setSOADomainEnv.sh or setSOADomainEnv.cmd file.

2. Add the -XX:-UseSSE42Intrinsics line to the JVM options.

3. Save the setSOADomainEnv.sh or setSOADomainEnv.cmd file.

Note:

This error does not occur when you use JRockit.

31.3.4 Nexaweb Applet Does Not Load In an Oracle Identity Manager and Oracle Access Manager Integrated Environment

In an Oracle Identity Manager and Oracle Access Manager (OAM) integrated environment, when you login to the Oracle Identity Manager Administrative and User Console and click a link that opens the Nexaweb applet, the applet does not load.

To workaround this issue, configure loading of the NexaWeb Applet in an Oracle Identity Manager and OAM integrated environment. To do so:

1. Login to the Oracle Access Manager Console.

2. Create a new Webgate ID. To do so:

1. Click the System Configuration tab.

2. Click 10Webgates, and then click the Create icon.

3. Specify values for the following attributes:
Name: NAME_OF_NEW_WEBGATE_ID

Access Client Password: PASSWORD_FOR_ACCESSING_CLIENT

Host Identifier: IDMDomain

4. Click Apply.

5. Edit the Webgate ID, as shown:
set 'Logout URL' = /oamsso/logout.html

6. Deselect the Deny On Not Protected checkbox.

3. Install a second Oracle HTTP Server (OHS) and Webgate. During Webgate configurations, when prompted for Webgate ID and password, use the Webgate ID name and password for the second Webgate that you provided in step 2c.

4. Login to the Oracle Access Manager Console. In the Policy Configuration tab, expand Application Domains, and open IdMDomainAgent.

5. Expand Authentication Policies, and open Public Policy. Remove the following URLs in the Resources tab:
/xlWebApp/.../*

/xlWebApp

/Nexaweb/.../*

/Nexaweb

6. Expand Authorization Policies, and open Protected Resource Policy. Remove the following URLs in the Resources tab:
/xlWebApp/.../*

/xlWebApp

/Nexaweb/.../*

/Nexaweb

7. Restart all the servers.

8. Update the obAccessClient.xml file in the second Webgate. To do so:

1. Create a backup of the SECOND_WEBGATE_HOME/access/oblix/lib/ObAccessClient.xml file.

2. Open the DOMAIN_HOME/output/WEBGATE_ID_FOR_SECOND_WEBGATE/ObAccessClient.xml file.

Note:

Ensure that the DenyOnNotProtected parameter is set to 0.

3. Copy the DOMAIN_HOME/output/WEBGATE_ID_FOR_SECOND_WEBGATE/ObAccessClient.xml file to the SECOND_WEBGATE_HOME/access/oblix/lib/ directory.

9. Copy the mod_wls_ohs.conf from the FIRST_OHS_INSTANCE_HOME/config/OHS_NAME/directory to the SECOND_OHS_INSTANCE_HOME/config/OHS_NAME/ directory. Then, open the mod_wls_host.conf of the second OHS to ensure the WebLogicHost and WeblogicPort are still pointing to Oracle Identity Manager managed server host and port.

10. Remove or comment out the following lines in the SECOND_OHS_INSTANCE_HOME/config/OHS_NAME/httpd.conf file:

<LocationMatch "/oamsso/*">
Satisfy any
</LocationMatch>

11. Copy the logout.html file from the FIRST_WEBGATE_HOME/access/oamsso/ directory to the SECOND_WEBGATE_HOME/access/oamsso/ directory. Then, open the logout.html file of the second Webgate to ensure that the host and port setting of the SERVER_LOGOUTURL variable are pointing to the correct OAM host and port.

12. Login to Oracle Access Manager Console. In the Policy Configuration tab, expand Host Identifiers, and open the host identifier that has the same name as the second Webgate ID name. In the Operations section, verify that the host and port for the second OHS are listed. If not, then click the add icon (+ sign) to add them. Then, click Apply.

13. Use the second OHS host and port in the URL for the OAM login page for Oracle Identity Manager. The URL must be in the following format:
http://SECOND_OHS_HOST:SECOND_OHS_PORT/admin/faces/pages/Admin.jspx

31.3.5 Packing a Domain With managed=false Option

When a domain is packed with the managed=false option and unpacked on the another computer, Oracle Identity Manager Authentication Provider is not recognized by WebLogic and basic administrator authentication fails when the Oracle Identity Manager managed server is started.

The following workaround can be applied for performing successful authentication via Oracle Identity Manager Authentication Provider:

1. Login in to the Oracle WebLogic Administrative Console by using the following URL:
http://HOST_NAME:ADMIN_PORT/console

2. Navigate to Security Realms, Realm(myrealm), and then to Providers.

3. Delete OIMAuthenticationProvider.

Note:

Make sure that you note the provider-specific details, such as the database URL, password, and driver, before deleting the provider.

4. Restart the WebLogic Administrative Server.

5. Navigate to Security Realms, Realm(myrealm), and then to Providers.

6. Create a new Authentication Provider of type OIMAuthenticationProvider.

7. Enter the provider specific details and mark the control flag as SUFFICIENT.

8. Restart the WebLogic Administrative Server.

9. Restart Oracle Identity Manager and other servers, if any.

31.3.6 Option Not Available to Specify if Design Console is SSL-Enabled

While configuring Oracle Identity Manager Design Console, you cannot specify if Design Console is SSL-enabled.

To workaround this issue after installing Oracle Identity Manager Design Console, edit the OIM_HOME/designconsole/config/xlconfig.xml file to change the protocol in the Oracle Identity Manager URL from t3 to t3s.

31.3.7 Nexaweb Applet Does Not Load in JDK 1.6.0_20

Deployment Manager and Workflow Visualizer might not work if the client browser has JDK/JRE installed on it whose version is 1.6.0_20. To workaround this issue, uninstall the JDK/JRE version 1.6.0_20 from the client browser and reinstall the JDK/JRE version 1.6.0_15.

31.3.8 Oracle Identity Manager and Design Console Must be Installed in Different Directory Paths

Oracle recommends to install Oracle Identity Manager and the Design Console in different directory paths.

31.3.9 Error on Adding Organization to User in Windows Explorer 8

In Microsoft Windows Internet Explorer 8 web browser, when you find and select an organization in the popup window from the Create User page, clicking the Add button displays the following error:

popup is null or not an object

To workaround this issue, make sure that the Display a notification about every script error option is not selected in the Advanced tab of the Internet Options dialog box.

31.4 Multi-Language Support Issues and Limitations

This section describes multi-language issues and limitations. It includes the following topics:

- Multi-language Valued Attributes in SPML and Oracle Identity Manager Do Not Match

- Login Names with Some Special Characters May Fail to Register

- The Create Role, Modify Role, and Delete Role Request Templates are Not Available for Selection in the Request Templates List

- Parameter Names and Values for Scheduled Jobs are Not Translated

- Bidirectional Issues for Legacy User Interface

- Localization of Role Names, Role Categories, and Role Descriptions Not Supported

- Localization of Task Names in Provisioning Task Table Not Supported

- Localization of Search Results of Scheduled Tasks Not Supported

- Searching for User Login Names Containing Certain Turkish Characters Causes an Error

- Localization of Notification Template List Values for Available Data Not Supported

- Searching for Entity Names Containing German "ß" (Beta) Character Fails in Some Features

- Special Asterisk (*) Character Not Supported

- Translated Error Messages Are Not Displayed in UI

- Reconciliation Table Data Strings are Hard-coded on Reconciliation Event Detail Page

- Translated Password Policy Strings May Exceed the Limit in the Background Pane

- Date Format Validation Error in Bi-Directional Languages

- Mistranslation on the Create Job page

- E-mail Notification for Password Expiration Cannot Be Created With Arabic Language Setting

- Translated Justification is Not Displayed in Access Policy-Based Resource Provisioning Request Detail

- Additional Single Quotes Displayed in GTC Reconciliation Mapping Page for French UI

- Not Allowing to Enter Design Console Password When Server Locale is Set to Simple Chinese, Traditional Chinese, Japanese, or Korean

- Bidirectional Text Not Supported in Nexaweb Pages

- Do Not Modify Oracle Identity Manager Predefined System Properties in Non-English Locale

- Error Generated When Translated String for System Property Name Exceeds Maximum Allowed Length in PTY_NAME Column

- Password Notification is Not Sent if User Login Contains Special Characters

- Reset Password Fails if User Login Contains Lowercase Special Characters

- Email Notification Not Send Per Preferred Locale

- Help Contents Displayed in English on Non-English Browsers

31.4.1 Multi-language Valued Attributes in SPML and Oracle Identity Manager Do Not Match

Oracle Identity Manager supports only the Display Name attribute for multi-language values. SPML specifies additional attributes, such as commonName and surname, as multi-language valued in the PSO schema. When multiple locale-values are specified in an SPML request for one of these attributes, only a single value is picked and passed to Oracle Identity Manager. The request will not fail and a warning message identifying the attributes and the value that was passed to Oracle Identity Manager is provided in the response.

31.4.2 Login Names with Some Special Characters May Fail to Register

In Oracle Identity Manager, the user login name is case-insensitive. When a user is created, the login name is converted to upper case and saved in the database. But the password is always case-sensitive. However, some special characters may encounter an error while registering to Oracle Identity Manager:

- Both the Greek characters &#963; (sigma) and &#962; (final sigma) maps to the &#931; character.

- Both English character i and Turkish character &#305; maps to the I character.

- Both German character ß and English string SS maps to the SS string.

This means that two user login names containing these special characters when the other characters in the login names are same cannot be created. For example, the user login names Johnß and JohnSS maps to the same user login name. If Johnß already exists, then creation of JohnSS is not allowed because both the ß character and the SS string maps to the SS string.

31.4.3 The Create Role, Modify Role, and Delete Role Request Templates are Not Available for Selection in the Request Templates List

The Create Role, Modify Role, and Delete Role request templates are not available in the Request Templates list of the Create Request wizard. This is because request creation by using any request template that are based on the Create Role, Modify Role, and Delete Role request models are supported from the APIs, but not in the UI. However, you can search for these request templates in the Request Templates tab. In addition, the Create Role, Modify Role, and Delete Role request models can be used to create approval policies and new request templates.

31.4.4 Parameter Names and Values for Scheduled Jobs are Not Translated

In the Create Job page of Oracle Identity Manager Advanced Administration, the fields in the Parameter section and their values are not translated. The parameter field names and values are available only in English.

31.4.5 Bidirectional Issues for Legacy User Interface

The following are known issues in the legacy user interface, also known as TransUI, contained in the xlWebApp war file:

- Hebrew bidirectional is not supported

- Workflow designer bidirectional is not supported for Arabic and Hebrew

31.4.6 Localization of Role Names, Role Categories, and Role Descriptions Not Supported

Localization of role names, categories, and descriptions is not supported in this release.

31.4.7 Localization of Task Names in Provisioning Task Table Not Supported

All Task Name values in the Provisioning Task table list are hard-coded and these pre-defined process task names are not localized.

31.4.8 Localization of Search Results of Scheduled Tasks Not Supported

When you search Scheduler Tasks using a Simple or Advanced search, the search results are not localized.

31.4.9 Searching for User Login Names Containing Certain Turkish Characters Causes an Error

On the Task Approval Search page, if you select "View Tasks Assigned To", then "Users You Manage", and then choose a user whose login name contains a Turkish Undotted "&#305" or a Turkish dotted "&#304" character, a User Not Found error will result.

31.4.10 Localization of Notification Template List Values for Available Data Not Supported

Localizing Notification Template Available Data list values is not supported in this release. Oracle Identity Manager depends upon the Velocity framework to merge tokens with actual values, and Velocity framework does not allow a space in token names.

31.4.11 Searching for Entity Names Containing German "ß" (Beta) Character Fails in Some Features

When you search for entity names containing the special German "ß" (beta) character from the Admin Console, the search fails in the following features:

- System Configuration

- Request Template

- Approve Policy

- Notification

In these features, the "ß" character matches to "ss" instead of itself. Consequently, the Search function cannot find entity names that contain the German beta character.

31.4.12 Special Asterisk (*) Character Not Supported

Although special characters are supported in Oracle Identity Manager, using the asterisk character (*) can cause some issues. You are advised not to use the asterisk character when creating or modifying user roles and organizations.

31.4.13 Translated Error Messages Are Not Displayed in UI

Oracle Identity Manager does not support custom resource bundles for Error Message display in user interfaces. Currently, there is no workaround for this issue.

31.4.14 Reconciliation Table Data Strings are Hard-coded on Reconciliation Event Detail Page

Some of the table data strings on the Reconciliation Event Detail page are hard-coded, customized field names. These strings are not localized.

31.4.15 Translated Password Policy Strings May Exceed the Limit in the Background Pane

Included as per bug# 9539501

The password policy help description may run beyond the colored box in some languages and when the string is too long. Currently, there is no workaround for this issue.

31.4.16 Date Format Validation Error in Bi-Directional Languages

When Job Detail page is opened in bi-directional languages, you cannot navigate away from this page because of "Date Format Validation Error". To work around this issue, select a value for the "Start Date" using the date-time control and then move to another page.

31.4.17 Mistranslation on the Create Job page

On the Japanese locale (LANG=ja_JP.UTF-8), "Fourth Wednesday" is mistranslated as "Fourth Friday" on the Create Job page when "Cron" is selected as the Schedule Type and "Monthly on given weekdays" is selected as the Recurring Interval.

31.4.18 E-mail Notification for Password Expiration Cannot Be Created With Arabic Language Setting

When the server locale is set to ar_AE.utf8 and values for user.language and user.region system properties are ar and AE respectively, if you create a password expiration warning e-mail notification in the Design Console, the value AE is not available for selection in the Region field. As a result, the email notification message cannot be created.

To workaround this issue:

1. Open the Lookup Definitions form in the Design Console.

2. Search for 'Global.Lookup.Region'.

3. Add an entry with Code key and Decode value as 'AE'. You can now create an e-mail definition with language ar and region AE.

31.4.19 Translated Justification is Not Displayed in Access Policy-Based Resource Provisioning Request Detail

When an access policy with approval is created, it generates a resource provisioning request that is subject to approval. In the request details page in Self Service or Advanced Administration, the translated request justification according to the locale setting by the user is not displayed. The justification is displayed in the default server locale.

31.4.20 Additional Single Quotes Displayed in GTC Reconciliation Mapping Page for French UI

When you set the Oracle Identity Manager Administrative and User Console locale to French, select the Provisioning and Reconciliation checkboxes while creating a Generic Technology Connector (GTC), and map the reconciliation fields in the page for modifying mapping fields, a message is displayed with two single quotes. You can ignore the single quotes because this is benign and has no effect on functionality.

31.4.21 Not Allowing to Enter Design Console Password When Server Locale is Set to Simple Chinese, Traditional Chinese, Japanese, or Korean

When you set the server locale to Simple Chinese, Traditional Chinese, Japanese, or Korean, and start the Design Console, you are not allowed to enter the password to login to the Design Console.

To workaround this issue:

1. Kill all scim processes. To do so, run the following command:

kill `pgrep scim`

2. Edit the scim config file. To do so:

1. Search for the following line:
/FrontEnd/X11/Dynamic = ......

2. Enter true as the value, as shown:
/FrontEnd/X11/Dynamic = true

Note:

If this line does not exist, then enter:

/Frontend/X11/Dynamic = true

3. Save the file.

3. Log out of the VNC viewer.

4. Restart the VNC server and log in again. You can now enter the password for the Design Console.

31.4.22 Bidirectional Text Not Supported in Nexaweb Pages

The Nexaweb pages that open from the Oracle Identity Manager Administrative and User Console do not support bidirectional text. For example, when you select any of the languages that are written from right to left, such as Arabic or Hebrew, and click Install Connector on the Welcome page, search for a connector, click Upgrade, and then proceed to step 13 of the Connector Upgrade wizard, the text in the page is not displayed from right to left.

31.4.23 Do Not Modify Oracle Identity Manager Predefined System Properties in Non-English Locale

When the user preference language for the Administrative and User Console is not English, and you update the value of a predefined system property in Oracle Identity Manager, translated property name and keyword are written in the PTY table. Therefore, on searching for system properties in the Administrative and User Console, this system property is not found.

31.4.24 Error Generated When Translated String for System Property Name Exceeds Maximum Allowed Length in PTY_NAME Column

When you try to set the value of a system property in a Western language UI, such as French, and if the translation string length exceeds the maximum allowed length, which is 80 characters, in the PTY_NAME column of the PTY table, then an error is generated.

31.4.25 Password Notification is Not Sent if User Login Contains Special Characters

For a user entity created with valid e-mail address in LDAP, if the User Login contains the German beta character, then the notification message is not sent on running LDAP user create/update full reconciliation.

31.4.26 Reset Password Fails if User Login Contains Lowercase Special Characters

In a Oracle Identity Manage deployment with LDAP synchronization enabled, if the User Login contains special characters such as Turkis dotted I, dotless i, German beta, and Greek sigma in lowercase format, then the reset password does not work.

To workaround this issue, use uppercase User Login to reset password because User Login is not case-sensitive in Oracle Identity Manager.

31.4.27 Email Notification Not Send Per Preferred Locale

When provisioning a resource to a user, the provisioned user and the user's manager receive the email notification in the locale as specified for user.language and user.country instead of their preferred locale.

31.4.28 Help Contents Displayed in English on Non-English Browsers

On non-English Web browsers, clicking the Help link on the top-right corner of the Oracle Identity Manager Self Service, Identity Administration, or Advanced Administration opens the help window, but always displays the on-line help contents in English.

31.5 Documentation Errata

Documentation Errata: Currently, there are no documentation issues to note.

32 Oracle Identity Navigator

This chapter describes issues associated with Oracle Identity Navigator. It includes the following topics:

- Section 32.1, "General Issues and Workarounds"

- Section 32.2, "Configuration Issues and Workarounds"

- Section 32.3, "Documentation Errata"

32.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topics:

- Section 32.1.1, "Avoid Selecting Reset Page in Dashboard Edit Mode"

- Section 32.1.2, "How to Navigate Product Registration Using the Keyboard"

- Section 32.1.3, "How to Navigate Product Discovery When Using the Keyboard"

- Section 32.1.4, "Color Contrast is Inadequate for Some Labels in Edit Mode"

- Section 32.1.5, "No Help Topic in Dashboard Edit Mode"

- Section 32.1.6, "Customization Problem in Internet Explorer 7"

- Section 32.1.7, "Discovery Problem in Internet Explorer 7"

- Section 32.1.8, "How to Navigate BI Publisher Configuration When Using the Keyboard"

- Section 32.1.9, "User Missing From Common Admin Role Search Results"

- Section 32.1.10, "Unable to View Users After Log in Or Log In Fails In Oracle Identity Manager Environment"

- Section 32.1.11, "Horizontal Scroll-bar Missing in Discovery Wizard"

32.1.1 Avoid Selecting Reset Page in Dashboard Edit Mode

If you select Customize to personalize the Dashboard, then click Reset Page, expect an error message. Reload Oracle Identity Navigator to recover from this error.

32.1.2 How to Navigate Product Registration Using the Keyboard

In the Product Registration section of the Administration screen, after you enter data into all the fields in the right pane, you must enter many Tab strokes to reach the Test, Save, or Cancel button. As a workaround, you can use Shift-Tab to move in the opposite direction.

You cannot use the Tab key alone to navigate the left pane of the Product Registration section. Use the Tab to move focus to the first category, then click the left or right arrow keys to expand and collapse the tree. Use the up and down arrow keys to navigate the nodes.

32.1.3 How to Navigate Product Discovery When Using the Keyboard

When you use Product Discovery to discover consoles, you enter a Host and Port, then click Next. Then, in the Add Products pane, you enter a Display Name for each of the products. If you want to change the display name, you must delete the entire name to retype it. Alternatively, you can enter the F2 key to switch to insert mode, then use left and right arrow keys to move around the display name characters.

You cannot use the arrow keys alone to navigate through the Category list on the Add Products pane. Inside the editable table, use the F2 key to focus on a field, then use up and down arrows to make a selection within the field.

32.1.4 Color Contrast is Inadequate for Some Labels in Edit Mode

After clicking Customize to change the layout of the Dashboard, some users might find certain labels, such as + Add Content, difficult to read, due to poor contrast.

32.1.5 No Help Topic in Dashboard Edit Mode

If you select Customize to personalize the Dashboard, then click the? icon for Oracle Composer Help, the help page displays Topic Not Found.

See "Personalizing Oracle Identity Navigator" in Oracle Fusion Middleware Administrator's Guide for Oracle Identity Navigator for more information about personalizing the Dashboard.

32.1.6 Customization Problem in Internet Explorer 7

If you enter Edit mode by clicking Customize in the global navigation links on the Dashboard in IE7, you will not be able to edit the page because the toolbar is hidden. As a workaround, use a different browser. If you use Internet Explorer 8, do not use compatibility mode.

32.1.7 Discovery Problem in Internet Explorer 7

Intermittently, when you use product discovery in Internet Explorer 7, buttons might disappear in the product discovery wizard. Refresh the browser to correct this problem.

32.1.8 How to Navigate BI Publisher Configuration When Using the Keyboard

When you use keyboard navigation to configure BI Publisher, when the Component Path dialogue box opens, use the Tab key along with the arrow keys to navigate in tree structure.

32.1.9 User Missing From Common Admin Role Search Results

The last user assigned the Application Configuration role may not appear in the Common Admin Roles search results list. This can occur if a search for Common Admin Roles is performed in the Access Privileges page immediately after assigning this role.

To workaround this issue, click another role type in the Role Name pane, then click Application Configuration role. The user last assigned the Application Configuration role displays in the Access Privileges list.

32.1.10 Unable to View Users After Log in Or Log In Fails In Oracle Identity Manager Environment

This issue can affect environments configured to use both Oracle Identity Manager and Oracle Identity Navigator. After log in to Oracle Identity Navigator using the bootstrap administrator credentials, users may not be visible in Access Privileges page. Or the log in attempt will fail. Issue is caused if the identity store entry in jps-config.xml is changed from the default value, <serviceInstanceRef ref="idstore.ldap"/>, to <serviceInstanceRef ref="idstore.oim"/>.

To verify this entry, check the value in <Extended_Domain_Home>/config/fmwconfig/jps-config.xml as follows:

1. Search for the jpscontexts section, with the name default, in the file. The section looks like the following:

<jpsContext name="default">
<serviceInstanceRef ref="credstore"/>
<serviceInstanceRef ref="keystore"/>
<serviceInstanceRef ref="policystore.xml"/>
<serviceInstanceRef ref="audit"/>
<serviceInstanceRef ref="idstore.oim"/>
</jpsContext>

2. To change the entry, perform steps 1 through 11 as detailed in "Post-Configuration Steps" in Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management.
Oracle Authorization Policy Manager does not need to be installed in your environment to perform this procedure.

32.1.11 Horizontal Scroll-bar Missing in Discovery Wizard

The full URL may not be viewable in the second page of the Discovery Wizard when viewed in a browser window.

To workaround this issue, collapse the left pane to view the full URL.

32.2 Configuration Issues and Workarounds

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

- Section 32.2.1, "No Oracle Icon is Visible in HTML Reports"

- Section 32.2.2, "Problems with Administration Screen When Using JAWS Screen Reader"

- Section 32.2.3, "SSO-Protected Consoles Must Be Configured by Name and Domain"

32.2.1 No Oracle Icon is Visible in HTML Reports

If you choose HTML as the format type when adding a report from the Dashboard screen, when you view the report, the words An Image appear in the report in place of the Oracle icon.

32.2.2 Problems with Administration Screen When Using JAWS Screen Reader

When you use a screen reader such as JAWS with the Administration screen in accessibility mode, and you bring up the list of combo boxes using the INS+CTRL+C JAWS keystroke, the combo boxes on the screen are listed as:

*Required Category(Required) Combo box

*Required Type(Required) Combo box

With this naming convention, keyboard shortcuts such as C for Category or T for Type do not work. Use the up and down arrow keys to navigate to fields within and between the two combo boxes.

32.2.3 SSO-Protected Consoles Must Be Configured by Name and Domain

Sometimes, when you use product discovery to find a console, even if you provide the host by name, the discovered address that fills in contains an IP address instead of the host and domain names.

If the console is protected by SSO, replace the IP address with the host.domain address that is known to SSO. For example, use an address such as http://myhost.mycompany.com:7005/odsm rather than http://130.35.10.10:7005/odsm. If you do not replace the IP address with the host and domain, single sign-on will not occur. That is, when users attempt to access the console from Oracle Identity Navigator, they will be prompted for their login name and password.

In some browsers, a redirection or connection error occurs.

32.3 Documentation Errata

This section describes documentation errata. It includes the following topic:

- Section 32.3.1, "IPv4/IPv6 Translation Issues"

32.3.1 IPv4/IPv6 Translation Issues

The following statement appears in the Troubleshooting section in Chapter 2 and in a note in Chapter 3 of Oracle Fusion Middleware Administrator's Guide for Oracle Identity Navigator:

In a dual-stack, IPv4 and IPv6 environment, some URLs might be inaccessible from your browser. Consult your network administrator for more information.

Actually, in a correctly configured dual-stack environment, all URLs are accessible. For more information about IPv4/IPv6 Translation Issues, see Framework for IPv4/IPv6 Translation draft-ietf-behave-v6v4-framework-09 at: http://www.ietf.org/

33 Oracle Internet Directory

This chapter describes issues associated with Oracle Internet Directory. It includes the following topics:

- Section 33.1, "General Issues and Workarounds"

- Section 33.2, "Configuration Issues and Workarounds"

- Section 33.3, "Documentation Errata"

33.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topics:

- Section 33.1.1, "Cloned Oracle Internet Directory Instance Fails or Runs Slowly"

- Section 33.1.2, "Oracle Internet Directory Fails to Start on Solaris SPARC System Using ISM"

- Section 33.1.3, "Custom Audit Policy Settings Fail When Set Through Enterprise Manager"

- Section 33.1.4, "Deleting Mandatory attributeTypes Referenced by objectClass is Successful"

- Section 33.1.5, "Oracle Unified Directory 11.1.2.0 orclguid Attribute is Not Mapped for Server Chaining"

- Section 33.1.6, "ODSM is Not Displaying Online Help Correctly in Internet Explorer 11"

- Section 33.1.7, "ODSM Browser Window Becomes Unusable"

- Section 33.1.8, "In ldapdelete Command -V Should Be The Last Parameter"

- Section 33.1.9, "Upgrading from 10.1.2.0.2 Infrastructure to Application Server 11g Infrastructure"

- Section 33.1.10, "Bulkmodify Might Generate Errors"

- Section 33.1.11, "Turkish Dotted I Character is Not Handled Correctly"

- Section 33.1.12, "OIDCMPREC Might Modify Operational Attributes"

- Section 33.1.13, "OIDREALM Does Not Support Realm Removal"

- Section 33.1.14, "Apply Patch to Oracle Database 11.2.0.1.0 to Fix Purge Job Problem"

- Section 33.1.15, "SQL of OPSS ldapsearch Might Take High %CPU"

- Section 33.1.16, "If you Start the Replication Server by Using the Command Line, Stop it Using the Command Line"

- Section 33.1.17, "ODSM Problems in Internet Explorer 7"

33.1.1 Cloned Oracle Internet Directory Instance Fails or Runs Slowly

In a cloned Oracle Internet Directory environment, undesired host names can cause errors, failures, or performance degradation.

This problem can occur when you clone an Oracle Internet Directory instance and the cloned target instance gets undesired host names from the source instance. Some of these hosts might be outside of a firewall or otherwise inaccessible to the target instance.

The cloned Oracle Internet Directory instance assumes it is in a clustered environment and tries to access the undesired hosts for notifications and other changes. However, the cloned instance cannot access some of the hosts and subsequently fails, returns errors, or runs slowly.

For example, this problem can occur during the following operations for a cloned Oracle Internet Directory target instance:

- Running the faovmdeploy.sh createTopology command to create an Oracle Virtual Machine (VM)

- Deploying Enterprise Manager agents in different Oracle Virtual Machines

To fix this problem, remove the undesired host names from the cloned Oracle Internet Directory instance, as follows:

1. Set the required environment variables. For example:

export ORACLE_INSTANCE=/u01/oid/oid_inst
export ORACLE_HOME=/u01/oid/oid_home
export PATH=$ORACLE_HOME/bin:$ORACLE_INSTANCE/bin:$PATH
export TNS_ADMIN=$ORACLE_INSTANCE/config

2. Connect to the Oracle Database and delete the entries with the undesired Oracle Internet Directory host names. For example, in the following queries, substitute the undesired host name for sourceHostname:

sqlplus ods@oiddb
delete from ods_shm where nodename like '%sourceHostname%';
delete from ods_shm_key where nodename like '%sourceHostname%';
delete from ods_guardian where nodename like '%sourceHostname%';
delete from ods_process_status where hostname like '%sourceHostname%';
commit;

3. Stop and then restart the cloned Oracle Internet Directory component. For example:

opmnctl stopproc ias-component=oid1
opmnctl startproc ias-component=oid1

4. Find the cn entries with the undesired Oracle Internet Directory host names. For example:

ldapsearch -h oid_host -p oid_port -D cn=orcladmin -w admin_password -b
"cn=subregistrysubentry" -s sub "objectclass=*" dn
cn=oid1_1_hostName1,cn=osdldapd,cn=subregistrysubentry
cn=oid1_1_hostName2,cn=osdldapd,cn=subregistrysubentry
cn=oid1_1_myhost.example.com,cn=osdldapd,cn=subregistrysubentry

5. From the results in the previous step, remove the entries with the undesired host names. For example:

ldapdelete h oid_host -p oid_port -D cn=orcladmin -w admin_password
"cn=oid1_1_hostName1,cn=osdldapd,cn=subregistrysubentry"
ldapdelete h oid_host -p oid_port -D cn=orcladmin -w admin_password
"cn=oid1_1_hostName2,cn=osdldapd,cn=subregistrysubentry"

6. Verify that the undesired host names are removed. For example:

ldapsearch h oid_host -p oid_port -D cn=orcladmin -w admin_password -b
"cn=subregistrysubentry" -s sub "objectclass=*" dn
cn=oid1_1_myhost.example.com,cn=osdldapd,cn=subregistrysubentry

See Also:

"Cloning Oracle Fusion Middleware" in the Oracle Fusion Middleware Administrator's Guide.

33.1.2 Oracle Internet Directory Fails to Start on Solaris SPARC System Using ISM

Oracle Internet Directory fails to start on the following Oracle Solaris SPARC system using Intimate Shared Memory (ISM): 5.11 11.1 sun4v sparc sun4v

As a workaround for this problem, set the following values, as shown in the next procedure:

- Set the total amount of operating system physical locked memory allowed (project.max-locked-memory) for Oracle Internet Directory to 2 GB or higher so that the value aligns with the supported page sizes. The pagesize -a command lists all the supported page sizes on Solaris systems.

- Set the orclecachemaxsize attribute to less than the project.max-locked-memory and ensure that the value aligns with the OS supported page sizes. For example, set the value to 256 MB.

In the following procedure, it is assumed that the Oracle Internet Directory services are managed by an operating system user named "oracle":

1. Log in to the Solaris SPARC system as the root user.

2. Check the project membership of the OID user.
If the OID user belongs to the default project:

1. Create a new project with the value of maximum locked memory set to 2 GB or higher, and associate the OID user with the newly created project. On Solaris 10 and 11, project id 3 represents the default project. For example:

# id -p oracle
uid=2345(oracle) gid=529(dba) projid=3(default)
# projadd -p 150 -K "project.max-locked-memory=(priv,2G,deny)" oidmaxlkmem
# usermod -K project=oidmaxlkmem oracle

2. Verify that the value for the resource control project.max-locked-memory was set to 2 GB, as expected. For example:

# su - oracle

$ id -p oracle
uid=2345(oracle) gid=529(dba) projid=150(oidmaxlkmem)

$ prctl -n project.max-locked-memory -i project 150
project: 150: oidmaxlkmem
NAME    PRIVILEGE       VALUE    FLAG   ACTION                   RECIPIENT
project.max-locked-memory
privileged      2.00GB      -   deny                             -
system          16.0EB    max   deny                             -

If the OID user belongs to a non-default project:

1. Modify the corresponding project to include the project.max-locked-memory resource control and set the value to 2 GB or higher. For example:

# id -p oracle
uid=2345(oracle) gid=529(dba) projid=125(oraproj)

# projmod -a -K "project.max-locked-memory=(priv,2G,deny)" oraproj

2. Verify that the value for the resource control project.max-locked-memory was set to 2 GB, as expected. For example:

# projects -l oraproj
oraproj
projid : 125
comment: ""
users  : (none)
groups : (none)
attribs: project.max-locked-memory=(priv,2147483648,deny)
project.max-shm-memory=(priv,34359738368,deny)

# su - oracle
$ id -p
uid=2345(oracle) gid=529(dba) projid=125(oraproj)

$ prctl -n project.max-locked-memory -i project 125
project: 125: oraproj
NAME    PRIVILEGE       VALUE    FLAG   ACTION                   RECIPIENT
project.max-locked-memory
privileged      2.00GB      -   deny                             -
system          16.0EB    max   deny                             -

3. Set the entry cache maximum size (orclecachemaxsize attribute) to a value that is less than the maximum locked memory size allowed by the OS and that aligns with the OS supported page sizes.
For example, using SQL*Plus, set the value to 256 MB:

sqlplus ods@oiddb
update ds_attrstore set attrval='256m'
where entryid=940 and attrname='orclecachemaxsize';
commit;

4. Run the config.sh script to configure Oracle Internet Directory.

33.1.3 Custom Audit Policy Settings Fail When Set Through Enterprise Manager

If you set custom Audit Policy Settings for Oracle Internet Directory through 11g Oracle Enterprise Manager Fusion Middleware Control and select audit Custom events with Failures Only, no audit logs are generated and the audit process for failure events fails. Subsequently, other audit events are not logged later, even if the Audit Policy Settings are changed to a different value such as Low, Medium, or High.

To make auditing function again through Enterprise Manager, select a default policy or a policy with custom events other than All Failures and then recycle the Oracle Internet Directory server processes.

Alternatively, you can set custom audit policies using LDAP command-line tools such as ldapmodify. For more information, see Section 23.4, "Managing Auditing from the Command Line" in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

33.1.4 Deleting Mandatory attributeTypes Referenced by objectClass is Successful

If you delete a mandatory attributeTypes under the Oracle Internet Directory schema that is referenced by an objectClass in the schema, no error is returned and the attributeTypes is deleted successfully.This problem also occurs for a DN entry created using the objectClass that uses the mandatory attributeTypes. The mandatory attribute is missing from the DN entry without any notice when it is deleted from the schema.

33.1.5 Oracle Unified Directory 11.1.2.0 orclguid Attribute is Not Mapped for Server Chaining

If you configure Oracle Internet Directory server chaining for Oracle Unified Directory 11.1.2.0 and then search for users, the orclguid attribute is missing from the search results.

The orclguid attribute is missing because Oracle Unified Directory uses the iplanet default mapping (cn=oidsciplanet,cn=oid server chaining,cn=subconfigsubentry), and the default iplanet mapping does not have orclguid mapped.

33.1.6 ODSM is Not Displaying Online Help Correctly in Internet Explorer 11

In Internet Explorer 11, the Oracle Directory Services Manager (ODSM) online Help does not display properly. Instead of showing the left pane with the navigation tree and the right pane with the Help contents, ODSM displays only links.

33.1.7 ODSM Browser Window Becomes Unusable

Under certain circumstances, after you launch ODSM from Fusion Middleware Control, then select a new ODSM task, the browser window might become unusable. For example, the window might refresh repeatedly, appear as a blank page, fail to accept user input, or display a null pointer error.

As a workaround, go to the URL: http://host:port/odsm, where host and port specify the location where ODSM is running, for example, http://myserver.example.com:7005/odsm. You can then use the ODSM window to log in to a server.

33.1.8 In ldapdelete Command -V Should Be The Last Parameter

For certain platforms command ldapdelete considers everything after -v, as parameter. A typical ldapdelete command looks like this:

ldapdelete -h hostname  -p portname  -v 's' -D cn=orcladmin -w welcome1

For Linux x86-64 and Microsoft Windows x64 the command mentioned here works fine. However, for Solaris Operating System (SPARC 64-Bit), AIX Based Systems (64-Bit), HP-UX PA-RISC (64-Bit), HP-UX Itanium platforms the above command fails.

Workaround

Use the flag -v as the last parameter when running the ldapdelete command. For example:

ldapdelete -h hostname  -p portname -D cn=orcladmin -w welcome1   -v 's'

33.1.9 Upgrading from 10.1.2.0.2 Infrastructure to Application Server 11g Infrastructure

33.1.10 Bulkmodify Might Generate Errors

If Oracle Internet Directory is using Oracle Database 11g Release 1 (11.1.0.7.0), you might see ORA-600 errors while performing bulkmodify operations. To correct this problem, apply the fixes for Bug 7019313 and Bug 7614692 to the Oracle Database.

33.1.11 Turkish Dotted I Character is Not Handled Correctly

Due to a bug, Oracle Internet Directory cannot handle the upper-case dotted I character in the Turkish character set correctly. This can cause problems in Oracle Directory Services Manager and in command-line utilities.

33.1.12 OIDCMPREC Might Modify Operational Attributes

By default, the oidcmprec tool excludes operational attributes during comparison.That is, oidcmprec does not compare the operational attributes values in source and destination directory entries. During reconciliation of user defined attributes however, operational attributes might be changed.

33.1.13 OIDREALM Does Not Support Realm Removal

The oidrealm tool supports creation, but not deletion, of a realm. A procedure for deleting a realm is provided in Note 604884.1, which is available on My Oracle Support at https://support.oracle.com/.

33.1.14 Apply Patch to Oracle Database 11.2.0.1.0 to Fix Purge Job Problem

If you use Oracle Database 11.2.0.1.0 with Oracle Internet Directory, apply Patch 9952216 (11.2.0.1.3 PSU) to the Oracle Database after you install Oracle Internet Directory:

Without the patch, a purge jobs operation does not function properly, and these symptoms can occur:

- Oracle Internet Directory change logs do not get purged, and the purge log shows ORA-23421 errors.

- Executing change log purge jobs with orclpurgenow set to 1 hangs.

33.1.15 SQL of OPSS ldapsearch Might Take High %CPU

The SQL of an OPSS one level ldapsearch operation, with filter "orcljaznprincipal=value" and required attributes, might take unreasonably high %DB CPU. If this search performance impacts the overall performance of the machine and other processes, you can alleviate the issue by performing the following steps in the Oracle Database:

1. Log in to the Oracle Database as user ODS and execute the following SQL:

BEGIN
DBMS_STATS.GATHER_TABLE_STATS(OWNNAME=>'ODS',
TABNAME=>'CT_ORCLJAZNPRINCIPAL',
ESTIMATE_PERCENT=>DBMS_STATS.AUTO_SAMPLE_SIZE,
CASCADE=>TRUE);
END;
/

2. Flush the shared pool by using the ALTER SYSTEM statement, as described in the Oracle Database SQL Language Reference.

33.1.16 If you Start the Replication Server by Using the Command Line, Stop it Using the Command Line

If you start the replication server by using the command line, stop it by using the command line. If you attempt to stop it by using Oracle Enterprise Manager Fusion Middleware Control, the attempt fails.

See Also:

Note 1313395.1 on My Oracle Support (formerly MetaLink): https://support.oracle.com

33.1.17 ODSM Problems in Internet Explorer 7

The ODSM interface might not appear as described in Internet Explorer 7.

For example, the Logout link might not be displayed.

If this causes problems, upgrade to Internet Explorer 8 or 9 or use a different browser.

33.2 Configuration Issues and Workarounds

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

- Section 33.2.1, "Re-Create Wallet After Moving Oracle Internet Directory from Test to Production"

33.2.1 Re-Create Wallet After Moving Oracle Internet Directory from Test to Production

If you configure Oracle Internet Directory to use SSL in server authentication mode or mutual authentication mode on your test machine, and then move Oracle Internet Directory to a production machine, re-create the Oracle Internet Directory wallet on the production machine.

The old wallet contains the host name of the original machine as the DN in the certificate. This host name in the DN is not changed during the test to production move. Re-create the wallet on the production machine to avoid SSL communication issues.

33.3 Documentation Errata

This section describes documentation errata. It includes the following topics:

- Section 33.3.1, "Description of the orclrevpwd Attribute Needs Clarification"

- Section 33.3.2, "LDAP Commands Do Not Support the -k|-K Option"

- Section 33.3.3, "Description of the orclOIDSCExtGroupContainer Attribute Needs Clarification"

- Section 33.3.4, "Setting Up LDAP Replication Needs Clarification"

- Section 33.3.5, "Password Expired Response Control is Not Documented"

- Section 33.3.6, "Configuring the SSO Server for ODSM Integration Needs Clarification"

- Section 33.3.7, "Determining Expired Users in Oracle Internet Directory"

- Section 33.3.8, "New Superuser Account Must be Direct Member of DirectoryAdminGroup Group"

- Section 33.3.9, "SSL Authentication Mode 1 and Anonymous SSL Ciphers Need Clarification"

- Section 33.3.10, "Documentation of Replication Server Control and Failover is Incomplete"

- Section 33.3.11, "Server Restart After Adding an Encrypted Attribute is Not Documented"

- Section 33.3.12, "PASSWORD_VERIFY_FUNCTION Must be Set to NULL to Work with RCU is Not Documented"

- Section 33.3.13, "Setting Up Oracle Internet Directory SSL Mutual Authentication"

- Section 33.3.14, "Replication Instructions in Tutorial for Identity Management are Incomplete"

33.3.1 Description of the orclrevpwd Attribute Needs Clarification

In the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory, the description of the orclrevpwd attribute in the "Managing Password Verifiers " chapter needs clarification. The "Introduction to Password Verifiers for Authenticating to the Directory" section should include the following information.

Oracle Internet Directory stores the user password in a reversible encrypted format in the orclrevpwd configuration attribute. The orclrevpwd attribute is generated only if the orclpwdencryptionenable attribute in the password policy entry is set to 1.

The orclrevpwd attribute is maintained securely within Oracle Internet Directory server and cannot be queried, even if you modify the attribute's access control policies (ACIs). Oracle Directory Integration Platform, however, is allowed to query the orclrevpwd attribute so that password synchronization can function.

33.3.2 LDAP Commands Do Not Support the -k|-K Option

In the Oracle Fusion Middleware Reference for Oracle Identity Management, Chapter 3, "Oracle Internet Directory Data Management Tools," documents the -k|-K option for LDAP commands. However, this option is not valid for the LDAP commands and should not be used.

33.3.3 Description of the orclOIDSCExtGroupContainer Attribute Needs Clarification

In the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory, the description of the orclOIDSCExtGroupContainer attribute in the "Configuring Server Chaining" chapter needs clarification.

The description states that this attribute "is optional if the external user container and the external group container are the same." However, the attribute is required, and the description should include the following information:

If the external user container and the external group container are the same (that is, groups in the external directory server are stored in the same container as the users), the value for the orclOIDSCExtGroupContainer attribute must be the same as the value used for the user container (orclOIDSCExtUserContainer attribute).

33.3.4 Setting Up LDAP Replication Needs Clarification

The Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory, Chapter 40, "Setting Up Replication," does not document the following requirements.

To setup replication for a directory that has more than 100,000 entries, you must use the command-line tools (ldifwrite and bulkload). Use the Replication Wizard in Oracle Enterprise Manager Fusion Middleware Control (automatic bootstrapping method) only for a directory that has fewer than 100,000 entries.

If you have a deployment with a combination of Oracle Internet Directory 10g nodes and 11gR1 nodes, replication from the 10g node to an 11gR1 node must be setup before replication between the 11gR1 nodes is setup. For example, consider a deployment as follows:

- Two Oracle Internet Directory 10g nodes with a supplier node and consumer node

- Two new Oracle Internet Directory 11gR1 nodes (nodes 1 and 2) with LDAP multimaster replication

To setup replication for this deployment:

1. Setup LDAP one-way replication from one of the 10g nodes to 11gR1 node 1.

2. Setup replication bootstrap (if fewer than 100,000 entries) and then start the replication server on the 11gR1 node 1. (If the diretory has more than 100,000 entries, use the command-line tools.)

3. When the replication is complete, setup LDAP multimaster replication between 11gR1 node 1 and node 2.

4. Setup the replication bootstrap (if fewer than 100,000 entries) on 11gR1 node 2 and then start the replication server.

33.3.5 Password Expired Response Control is Not Documented

Both the Oracle Fusion Middleware Reference for Oracle Identity Management and the Oracle Fusion Middleware Application Developer's Guide for Oracle Identity Management do not document the Oracle Internet Directory password expired response control:

- Object Identifier: 2.16.840.1.113894.1.8.20

- Name: OID_PWDEXPIRED_CONTROL

- Description: Password policy control. The response control that the server sends when the password has expired, there are no grace logins remaining, and the client sends a request control.

33.3.6 Configuring the SSO Server for ODSM Integration Needs Clarification

In the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory, Section 7.4.3, "Configuring the SSO Server for ODSM Integration," does not document that to improve performance for SSO-ODSM integration, you should configure the ODSM URLs as follows:

- Protected: /odsm/odsm-sso.jsp

- Unprotected: /odsm/faces/odsm.jspx

- Excluded: /odsm/.../

Setting the CSS, JavaScript, and graphics (/odsm/.../) files to excluded prevents these files from being validated by Oracle Access Manager, which can improve the performance of your deployment.

33.3.7 Determining Expired Users in Oracle Internet Directory

The Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory does not fully explain the concept of expired users and how to determine if a user is in the expired state.

In some situations, you might want to determine expired users and then take a specific action, such as deleting those users from the directory.

Note:

Oracle Internet Directory expired users are not indicated by a specific attribute. An expired user is in a transient state that depends on the system time, the maximum inactive time allowed, and the user's last successful login time. The expired state is determined during a bind or password compare operation for the user.

To determine the expired users, your Oracle Internet Directory deployment must be configured as follows:

- The tracking of each user's last successful login time must be enabled by setting the orclPwdTrackLogin attribute to 1.

- The orclpwdmaxinactivitytime attribute must be set to a value other than 0 (the default). This attribute specifies the inactive time in seconds before a user's account is automatically considered to be expired.

To determine if a user's account is considered to be expired:

1. Determine the time stamp of the user's last successful login from the orcllastlogintime attribute.

2. Subtract the user's orcllastlogintime value from the current system time. If the result is greater than the orclpwdmaxinactivitytime value, then the user is considered to be in the expired state.

3. If you wish, delete the expired user from the directory.

For more information, see the "Managing Password Policies" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

33.3.8 New Superuser Account Must be Direct Member of DirectoryAdminGroup Group

In the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory, Section 12.6, "Creating Another Account With Superuser Privileges," does not mention that a new superuser account must be a direct member of the DirectoryAdminGroup group to use all Oracle Directory Services Manager (ODSM) features.

To use all ODSM features including the Security and Advanced tabs, a new superuser account must be a direct member of the DirectoryAdminGroup group. The new superuser account cannot be a member of a group that is in turn a member of the DirectoryAdminGroup group. In this configuration, the superuser would be able to access only the ODSM Home, Schema, and Data Browser tabs.

33.3.9 SSL Authentication Mode 1 and Anonymous SSL Ciphers Need Clarification

In the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory, the first bullet of the note in Section 27.1.3, "SSL Authentication Modes," mentions that you must have at least one Oracle Internet Directory server instance configured for the default authentication mode and anonymous SSL ciphers. This statement is true only for specific deployments.

The first bullet of the note should be revised as follows:

- By default, the SSL authentication mode is set to 1 (encryption only, no authentication).
If you are using Oracle Delegated Administration Services 10g or other client applications such as legacy versions of Oracle Forms and Oracle Reports that expect to communicate with Oracle Internet Directory on an encrypted SSL port configured for anonymous SSL ciphers, then at least one Oracle Internet Directory server instance must be configured for this default authentication mode.

Otherwise, authentication mode 1 and anonymous SSL ciphers are not required for Oracle Internet Directory to function. The type of SSL ports that are made available and the ciphers that the SSL port will accept depend on your specific deployment requirements.

33.3.10 Documentation of Replication Server Control and Failover is Incomplete

The Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory does not fully describe the replication server (oidrepld) process control and failover in an Oracle Maximum Availability Architecture (MAA), including how to enable failover by setting the orclfailoverenabled attribute.

The orclfailoverenabled attribute is an OID Monitor configuration entry ("cn=configset,cn=oidmon,cn=subconfigsubentry") that configures failover.

This attribute specifies the failover time in minutes before the OID Monitor will start failed processes on a surviving node. The default failover time is 5 minutes. A value of zero (0) disables failover for Oracle Internet Directory processes.

Additional information is provided in Note 1538250.1, which is available on My Oracle Support at:

https://support.oracle.com/

See Also:

The "Understanding Process Control of Oracle Internet Directory Components" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

33.3.11 Server Restart After Adding an Encrypted Attribute is Not Documented

The Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory does not document that if you add an encrypted attribute to the list of sensitive attributes, you must restart the Oracle Internet Directory server instance for the new attribute to be added to the new list of sensitive attributes and recognized by the server.

Note:

The attributes in Table 28-1 "Sensitive Attributes Stored in orclencryptedattributes" in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory are intended for use only by Oracle. Do not add to or modify the attributes shown in this table unless you are requested to do so by Oracle Support.

For more information, see the "Configuring Data Privacy" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

33.3.12 PASSWORD_VERIFY_FUNCTION Must be Set to NULL to Work with RCU is Not Documented

The Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory does not document that for Oracle Internet Directory to work with the Repository Creation Utility (RCU) for Oracle database version 11.2.x, the default PASSWORD_VERIFY_FUNCTION clause in the database must be set to NULL (which is the default value).

33.3.13 Setting Up Oracle Internet Directory SSL Mutual Authentication

Neither the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory nor the Oracle Fusion Middleware Administrator's Guide describes how to set up Oracle Internet Directory SSL Client and Server Authentication. This information is provided in Note 1311791.1, which is available on My Oracle Support at:

https://support.oracle.com/

33.3.14 Replication Instructions in Tutorial for Identity Management are Incomplete

In the Tutorial for Identity Management, which is linked from Getting Started with Oracle Identity Management, Chapter 3, "Setting up Oracle Internet Directory Replication," is missing important information.

Specifically, the instructions do not work unless the new consumer node is empty.

For more information, see Section 40.1.7, "Rules for Configuring LDAP-Based Replication," in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

34 Oracle Platform Security Services

This chapter describes notes on topics associated with Oracle Platform Security Services (OPSS), in the following sections:

- Section 34.1, "Configuration Issues and Workarounds"

- Section 34.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

34.1 Configuration Issues and Workarounds

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

- Section 34.1.1, "Oracle Fusion Middleware Audit Framework"

- Section 34.1.2, "Trailing '\n' Character in Bootstrap Key"

- Section 34.1.3, "Users with Same Name in Multiple Identity Stores"

- Section 34.1.4, "Script listAppRoles Outputs Wrong Characters"

- Section 34.1.5, "Propagating Identities over the HTTP Protocol"

- Section 34.1.6, "Pool Configuration Missing in Identity Store"

34.1.1 Oracle Fusion Middleware Audit Framework

This section describes configuration issues for the Oracle Fusion Middleware Audit Framework. It contains these topics:

- Section 34.1.1.1, "Configuring Auditing for Oracle Access Manager"

- Section 34.1.1.2, "Audit Reports do not Display Translated Text in Certain Locales"

- Section 34.1.1.3, "Audit Reports Always Display in English"

- Section 34.1.1.4, "Audit Store Does not Support Reassociation through EM"

- Section 34.1.1.5, "OWSM Audit Events not Audited"

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

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

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

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

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

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

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

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

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

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

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

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

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

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

34.2 Documentation Errata

This section contains corrections to documentation errors. It includes the topic:

- Section 34.2.1, "Updated Configuration for Role Category"

- Section 34.2.2, "Correct setAuditRepository Command Reference Example"

- Section 34.2.3, "Demo CA Certificate not for Production Use"

- Section 34.2.4, "Incorrect Link to ILM Content"

- Section 34.2.5, "Incorrect Table Title in Appendix C"

- Section 34.2.6, "Clarification of Note in Appendix C"

- Section 34.2.7, "Notes Regarding Need for Server Restarts"

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

34.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'.

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

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

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

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

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

35 SSL Configuration in Oracle Fusion Middleware

This chapter describes issues associated with SSL configuration in Oracle Fusion Middleware. It includes the following topic:

- Section 35.1, "General Issues and Workarounds"

35.1 General Issues and Workarounds

This section describes general issues and workarounds. It includes the following topic:

- Section 35.1.1, "Incorrect Message or Error when Importing a Wallet"

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

36 Oracle Directory Integration Platform

This chapter describes issues associated with Oracle Directory Integration Platform. It includes the following topics:

- Section 36.1, "General Issues and Workarounds"

- Section 36.2, "Configuration Issues and Workarounds"

- Section 36.3, "Documentation Errata"

36.1 General Issues and Workarounds

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

- Enabling the Domain-Wide Administration Port on Oracle WebLogic Server Prevents use of the DIP Command Line Interface

- The AttrMapping Rule dnconvert() function is not Working During Directory Synchronization

- The Oracle Password Filter for Microsoft Active Directory is not Certified for use With Oracle Unified Directory or Oracle Directory Server Enterprise Edition

- LDIF Files That Contain Non-ASCII Characters Will Cause the testProfile Command Option to Fail if the LDIF File has Native Encoding

- Some Changes May Not Get Synchronized Due to Race Condition in Heavily-Loaded Source Directory

- Synchronization Continues After Stopping Oracle Directory Integration Platform

- PKCS11 Exception in DIP Server Log File

- Certain Queries and Provisioning Profile Functionality may Fail on JDK 1.6 u 21

36.1.1 Enabling the Domain-Wide Administration Port on Oracle WebLogic Server Prevents use of the DIP Command Line Interface

Be aware that enabling the domain-wide administration port on any WebLogic server running Directory Integration Platform will prevent you from using the DIP command line interface using a standard administrator account. Entering DIP commands will result in an error similar to the following:

User: "weblogic", failed to be authenticated

Administrators can still use the Enterprise Manager (EM) GUI to configure and manage Oracle Directory Integration Platform.

36.1.2 The AttrMapping Rule dnconvert() function is not Working During Directory Synchronization

During directory synchronization, the AttrMapping Rule dnconvert() function does not properly apply the attribute mapping rule. The dnconvert() function is supposed to take a dnvalue as its only argument and transform the value based on the domain mapping rule. Instead, no transformation is taking place.

For example:

DomainRules
cn=users,dc=ADdomain,dc=com:cn=users,dc=OIDdomain,dc=com:cn=%,dc=OIDdomain,c=com

###
AttributeRules
# attribute rule common to all objects
objectguid:
:binary:top:orclobjectguid:string:orclADObject:bin2b64(objectguid)
ObjectSID: :binary:user:orclObjectSID:string:orclADObject:bin2b64(ObjectSID)
distinguishedName: : :top:orclSourceObjectDN: :orclADObject:
samaccountname:::user:cn::person:
manager:::organizationalperson:manager::inetorgperson:dnconvert(manager)

In this example, the new entry from Active Directory to Oracle Internet Directory does not pull the samAccountName value but rather the DN value for the manager.

36.1.3 The Oracle Password Filter for Microsoft Active Directory is not Certified for use With Oracle Unified Directory or Oracle Directory Server Enterprise Edition

To use the Oracle Password Filter for Microsoft Active Directory, your Oracle back-end directory must be Oracle Internet Directory. The Oracle Unified Directory back-end directory and the Oracle Directory Server Enterprise Edition back-end directory do not support integration with the Oracle Password Filter for Microsoft Active Directory.

36.1.4 LDIF Files That Contain Non-ASCII Characters Will Cause the testProfile Command Option to Fail if the LDIF File has Native Encoding

When running DIP Tester from a command-line, the manageSyncProfiles testProfile command will fail if the -ldiffile option is specified and the LDIF file contains non-ASCII characters.

Note that LDIF files with UTF-8 encoding are not impacted by this limitation. If an LDIF file containing multibyte characters cannot be saved with UTF-8 encoding, then use the following workaround:

1. From a command-line, add the entry using the ldapadd command and include the -E option to specify the locale. See the Oracle Fusion Middleware User Reference for Oracle Identity Management for the required command syntax.

2. Get the specific changeNumber for the last add operation.

3. Execute the testProfile command using the changeNumber from the previous step.

For more information, see "Section 7.1.5.2, Running DIP Tester From the WLST Command-Line Interface" in the Administrator's Guide for Oracle Directory Integration Platform.

36.1.5 Some Changes May Not Get Synchronized Due to Race Condition in Heavily-Loaded Source Directory

If the source directory is heavily-loaded, a race condition may occur where database commits cannot keep pace with updates to the lastchangenumber. If this race condition occurs, Oracle Directory Integration Platform may not be able to synchronize some of the changes.

To work around this issue, perform the following steps to enable database commits to keep pace with the lastchangenumber:

1. Increase the value of the synchronization profile's Scheduling Interval.

2. Control the number of times the search is performed on the source directory during a synchronization cycle by setting the searchDeltaSize parameter in the profile. Oracle suggests starting with a value of 10, then adjusting the value as needed.

36.1.6 Synchronization Continues After Stopping Oracle Directory Integration Platform

If you stop the Oracle Directory Integration Platform application during synchronization, the synchronization process that the Quartz scheduler started will continue to run.

To work around this issue, restart the Oracle WebLogic Managed Server hosting Oracle Directory Integration Platform or redeploy the Oracle Directory Integration Platform application.

36.1.7 PKCS11 Exception in DIP Server Log File

If the Oracle Directory Integration Platform (DIP) server is configured with Sun JDK version 1.6.0_16+ or BEA JRockit version 1.6.0_14+, you may see the following PKCS11 exceptions intermittently in the wls_ods1.out log files under DIP server logs directory:

Exception in thread "Thread-236" java.security.ProviderException: doFinal() failed
at sun.security.pkcs11.P11Cipher.implDoFinal(P11Cipher.java:720)
at sun.security.pkcs11.P11Cipher.engineDoFinal(P11Cipher.java:488)

Caused by: sun.security.pkcs11.wrapper.PKCS11Exception: CKR_OPERATION_NOT_INITIALIZED
at sun.security.pkcs11.wrapper.PKCS11.C_DecryptFinal(Native Method)
at sun.security.pkcs11.P11Cipher.implDoFinal(P11Cipher.java:713)

Exception in thread "Thread-88" java.security.ProviderException: update() failed
at sun.security.pkcs11.P11Cipher.implUpdate(P11Cipher.java:548)
at sun.security.pkcs11.P11Cipher.engineUpdate(P11Cipher.java:448)

Caused by: sun.security.pkcs11.wrapper.PKCS11Exception: CKR_OPERATION_NOT_INITIALIZED
at sun.security.pkcs11.wrapper.PKCS11.C_EncryptUpdate(Native Method)
at sun.security.pkcs11.P11Cipher.implUpdate(P11Cipher.java:501)

You can safely ignore these exception messages. They do not affect any functionality.

36.1.8 Certain Queries and Provisioning Profile Functionality may Fail on JDK 1.6 u 21

LDAP JNDI filter processing has been updated to be stricter in JDK 1.6 u21. Consequently, certain queries performed by Oracle Directory Integration Platform may fail on JDK 1.6 u21 and provisioning profile functionality may also be affected. To fix this issue, download and apply patch 10631569, which is available for download on My Oracle Support (formerly MetaLink). Access My Oracle Support at https://support.oracle.com.

Oracle strongly recommends that you download and apply patch 10631569 for Identity Management 11.1.1.4.0.

36.2 Configuration Issues and Workarounds

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

- Update the Mapping Rule for Novell eDirectory

- Do not use localhost as Oracle Internet Directory Hostname When Configuring Oracle Directory Integration Platform

- You may Need to Restart the Directory Integration Platform After Running dipConfigurator Against Oracle Unified Directory

- When Configuring a Profile, you may Need to Scroll Past a Section of Whitespace to View Mapping Rules

- Resource Usage Charts will not Display if Multiple IDM Domains are Running on the Same Host

36.2.1 Update the Mapping Rule for Novell eDirectory

If Directory Integration Platform is integrated with Novell eDirectory, or if you plan to integrate with Novell eDirectory later, edit the mapping rules in the eDir profile, otherwise the installation program will return this error message:

Map rules "orclodipattributemappingrules" have the following errors:
Attribute rule "0" has error: Invalid destination attribute's type: Expecting
'binary'; found 'string'.

If you have not yet integrated with Novell eDirectory, update the mapping file in the default template before registering a new profile.

Note:

Refer to the "Updating Mapping Rules" section in the Administrator's Guide for Oracle Directory Integration Platform for information about how to modify an entry in a mapping rule file.

1. Update the mapping rules in the existing profile or new profile for the following entry:

guid:1:binary:top:orclndsobjectguid:string:orclndsobject:bin2b64(guid)

Replace it with this mapping:

guid:1:binary:top:orclndsobjectguid:binary:orclndsobject:bin2b64(guid)

2. Save your changes.

36.2.2 Do not use localhost as Oracle Internet Directory Hostname When Configuring Oracle Directory Integration Platform

When configuring Oracle Directory Integration Platform against an existing Oracle Internet Directory—using either the installer's Install and Configure installation option or the Oracle Identity Management 11g Release 1 (11.1.1) Configuration Wizard—you must specify the hostname for Oracle Internet Directory using only its fully qualified domain name (such as myhost.example.com). Do not use localhost as the Oracle Internet Directory hostname even if Oracle Directory Integration Platform and Oracle Internet Directory are collocated on the same host.

If you use localhost as the Oracle Internet Directory hostname, you will not be able to start the Oracle WebLogic Managed Server hosting Oracle Directory Integration Platform.

36.2.3 You may Need to Restart the Directory Integration Platform After Running dipConfigurator Against Oracle Unified Directory

After running dipConfigurator against an Oracle Unified Directory (OUD) endpoint, if you are unable to open the Directory Integration Platform (DIP) UI in Enterprise Manger, stop and start DIP to fix the UI problem.

36.2.4 When Configuring a Profile, you may Need to Scroll Past a Section of Whitespace to View Mapping Rules

If you are using Internet Explorer to view the Directory Integration Platform (DIP) UI, you may need to scroll past a large blank space to see the profile mapping rules section. This issue is not known to affect other browsers.

36.2.5 Resource Usage Charts will not Display if Multiple IDM Domains are Running on the Same Host

If two IDM domains on the same host share the same Oracle home and are both configured to use wls_ods1 managed servers, then the DIP home page will not display the resource usage charts if both instances are running at the same time.

36.3 Documentation Errata

There are no known documentation issues at this time.

37 Oracle Virtual Directory

This chapter describes issues associated with Oracle Virtual Directory. It includes the following topics:

- Section 37.1, "General Issues and Workarounds"

- Section 37.2, "Configuration Issues and Workarounds"

- Section 37.3, "Documentation Errata"

37.1 General Issues and Workarounds

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

- Section 37.1.1, "Oracle Virtual Directory Fails to Start When Unsupported Ciphersuite for Listener SSL Config is Selected in Enterprise Manager"

- Section 37.1.2, "EUS Adapter Creation Failed"

- Section 37.1.3, "Manually Edit adapters.os_xml File When Creating DB Adapter For Sybase"

- Section 37.1.4, "ODSM Version Does Not Change in Enterprise Manager after Patching ODSM to 11.1.1.6.0"

- Section 37.1.5, "ODSM Bug Requires Editing of odsmSkin.css File"

- Section 37.1.6, "Oracle Directory Services Manager Browser Window is Not Usable"

- Section 37.1.7, "Exceptions May Occur in Oracle Directory Services Manager When Managing Multiple Oracle Virtual Directory Components and One is Stopped"

- Section 37.1.8, "Identifying the DN Associated with an Access Control Point in Oracle Directory Services Manager"

- Section 37.1.9, "Issues With Oracle Virtual Directory Metrics in Fusion Middleware Control"

- Section 37.1.10, "Using a Wildcard when Performing an LDAPSEARCH on a TimesTen Database Causes an Operational Error"

- Section 37.1.11, "ODSM Version 11.1.1.4.0 Does Not Support OVD Versions 11.1.1.2.0 or 11.1.1.3.0"

- Section 37.1.12, "ODSM Version 11.1.1.5.0 Does Not Support OVD Versions 11.1.1.2.0, 11.1.1.3.0, or 11.1.1.4.0"

- Section 37.1.13, "ODSM Version 11.1.1.6.0 Does Not Support OVD Versions 11.1.1.2.0, 11.1.1.3.0, 11.1.1.4.0, or 11.1.1.5.0"

- Section 37.1.14, "Users with Non-ASCII Names Might Encounter Problems when Using ODSM with SSO"

- Section 37.1.15, "Creating an Attribute/Object Class Throws NPE Error"

- Section 37.1.16, "Patch Required to Enable Account Lockout Feature"

- Section 37.1.17, "ODSM Problems in Internet Explorer 7"

- Section 37.1.18, "Strings Related to New Enable User Account Lockout Feature on EUS Wizard Are Not Translated"

- Section 37.1.19, "All Connections Created In ODSM 11.1.1.1.0 Are Lost After Upgrading to OVD or OID Version 11.1.1.7.0"

- Section 37.1.20, "Incorrect ODSM Version Displays in Enterprise Manager Console After OVD Upgrade"

- Section 37.1.21, "Connection Issues to OVD"

- Section 37.1.22, "ODSM Version 11.1.1.70 Does Not Support OVD Versions 11.1.1.2.0, 11.1.1.3.0, 11.1.1.4.0, 11.1.1.5.0, or 11.1.1.6.0"

- Section 37.1.23, "Modify Completes When Updating a Mandatory Attribute to Null"

37.1.1 Oracle Virtual Directory Fails to Start When Unsupported Ciphersuite for Listener SSL Config is Selected in Enterprise Manager

When you create an Oracle LDAP listener in Enterprise Manager, and then edit the listener's Change SSL setting by selecting Enable SSL for any SSL authorization, Enterprise Manager selects the ciphersuite TLS_DHE_RSA_WITH_AES_128_CBC_SHA256. If this ciphersuite is selected, then Oracle Virtual Directory will fail to start-up entirely.

Oracle Virtual Directory supports the following protocols:

- TLSv1

- SSLv2Hello

- SSLv3

Note:

For a complete list of the supported ciphers for each protocol, refer to the following location:

http://www.openssl.org/docs/apps/ciphers.html

To work around this issue, manually uncheck all of the ciphers listed for Enterprise Manager when configuring the ciphersuites.

37.1.2 EUS Adapter Creation Failed

When creating an EUS adapter using the wizard in Oracle Directory Services Manager, an error message periodically displays stating the adapters and ACLs were not created successfully.

To work around this issue, proceed as follows:

- If the error occurred while you were loading ACLs, and only partial ACLs were loaded during EUS configuration, then you can manually load the remaining ACLs by running this command:

$ORACLE_HOME/bin/ldapmodify -c -v -h <ovd_host> -p <ovd_port> -D cn=orcladmin -w <orcladmin_password> -f
$ORACLE_HOME/ovd/eus/eusACLTemplate.ldif

- If the error occurred during any other step, then manually clean up the partial configuration from Oracle Virtual Directory by using the following steps, and then reconfigure Oracle Virtual Directory for EUS.

1. Delete all of the Local Store and LDAP EUS adapters created.

2. Delete the LSA EUS adapter data files from the local file system.

3. Undeploy the EUS py mapping based on your directory type (if it exists).

4. Click the EUS wizard icon again to reconfigure.

37.1.3 Manually Edit adapters.os_xml File When Creating DB Adapter For Sybase

Creating a Database Adapter with Sybase as back-end causes Oracle Virtual Directory to fail with an Invalid Database Connection error.

To work around this issue, you can manually edit the adapters.os_xml file using the same Database connection information.

37.1.4 ODSM Version Does Not Change in Enterprise Manager after Patching ODSM to 11.1.1.6.0

The Oracle Directory Services Manager version shown in Enterprise Manager is the application version, which does not change when you patch Oracle Directory Services Manager.

The Oracle Lifecycle team requires all Enterprise Manager components to retain the same application version. However, because customers want to know which Oracle Directory Services Manager version they are using, Oracle Directory Services Manager maintains the actual (patch) version and Enterprise Manager maintains the application version, which causes this mismatch.

This issue is a known issue, starting with version 11.1.1.3.0.

37.1.5 ODSM Bug Requires Editing of odsmSkin.css File

Due to a misplaced comment in the file odsmSkin.css, some labels on the Oracle Directory Services Manager home page are not displayed correctly. Specifically, the labels in the diagram on the right are misplaced or missing.

To work around this issue, proceed as follows:

1. Stop the wls_ods1 managed server and the WebLogic Administration server.

2. Edit the file:

MW_HOME/user_projects/domains/DOMAIN_HOME/servers/MANAGED_SERVER_NAME/tmp/_WL_user/ODSM_VERSION_NUMBER/RANDOM_CHARACTERS/war/skins/odsmSkin.css

For example:

wlshome/user_projects/domains/base_domain/servers/wls_ods1/tmp/_WL_user/odsm_11.1.1.2.0/z5xils/war/skins/odsmSkin.css

Before editing, the odsmSkin.css file looks like this:

@agent ie /*========== Fix for bug#7456880 ==========*/
{
af|commandImageLink::image,
af|commandImageLink::image-hover,
af|commandImageLink::image-depressed
{
vertical-align:bottom;
}
}

Move the comment:

/*========== Fix for bug#7456880 ==========*/

so that it is above the line

@agent ie

After editing, the file should look like this:

/*========== Fix for bug#7456880 ==========*/
@agent ie
{
af|commandImageLink::image,
af|commandImageLink::image-hover,
af|commandImageLink::image-depressed
{
vertical-align:bottom;
}
}

3. Restart the WebLogic Administration server and the wls_ods1 managed server.

37.1.6 Oracle Directory Services Manager Browser Window is Not Usable

In some circumstances, after you launch Oracle Directory Services Manager from Fusion Middleware Control, then select a new Oracle Directory Services Manager task, the browser window might become unusable. For example, the window might refresh repeatedly, appear as a blank page, fail to accept user input, or display a null pointer error.

As a work around, go to the URL: http://host:port/odsm, where host and port specify the location where Oracle Directory Services Manager is running, for example, http://myserver.example.com:7005/odsm. You can then use the Oracle Directory Services Manager window to log in to a server.

37.1.7 Exceptions May Occur in Oracle Directory Services Manager When Managing Multiple Oracle Virtual Directory Components and One is Stopped

Under certain circumstances, when managing multiple Oracle Virtual Directory components from the same Oracle Directory Services Manager session, exception or error messages may appear if you stop one of the Oracle Virtual Directory components. For example, you are managing Oracle Virtual Directory components named ovd1 and ovd2 from the same Oracle Directory Services Manager session. Both ovd1 and ovd2 are configured and running. If you stop ovd1, an exception or Target Unreachable message may appear when you try to navigate Oracle Directory Services Manager.

To work around this issue, exit the current Oracle Directory Services Manager session, close the web browser, and then reconnect to Oracle Virtual Directory components in a new Oracle Directory Services Manager session.

37.1.8 Identifying the DN Associated with an Access Control Point in Oracle Directory Services Manager

When you create an Access Control Point (ACP) using Oracle Directory Services Manager, the Relative Distinguished Name (RDN) of the DN where you created the ACP appears in the navigation tree on the left side of the screen. For example, if you create an ACP at the DN of cn=ForExample,dc=us,dc=sales,dc=west, then cn=ForExample appears in the navigation tree. After clicking an ACP in the navigation tree, its settings appear in the right side of the screen and the RDN it is associated with appears at the top of the page.

To identify the DN associated with an ACP, move the cursor over ("mouse-over") the ACP entry in the navigation tree. The full DN associated with the ACP will be displayed in a tool-tip dialog box.

Mousing-over ACPs in the navigation tree is useful when you have multiple ACPs associated with DNs that have identical RDNs, such as:

ACP 1 = cn=ForExample,dc=us,dc=sales,dc=west

ACP 2 = cn=ForExample,dc=us,dc=sales,dc=east

37.1.9 Issues With Oracle Virtual Directory Metrics in Fusion Middleware Control

This topic describes issues with Oracle Virtual Directory metrics in Fusion Middleware Control, including:

- Configuring Operation-Specific Plug-Ins to Allow Performance Metric Reporting in Fusion Middleware Control After Upgrading to 11g Release 1 (11.1.1)

37.1.9.1 Configuring Operation-Specific Plug-Ins to Allow Performance Metric Reporting in Fusion Middleware Control After Upgrading to 11g Release 1 (11.1.1)

If you upgraded an Oracle Virtual Directory Release 10g installation with plug-ins configured to execute on specific operations, such as add, bind, get, and so on, to 11g Release 1 (11.1.1), you may have to update those operation-specific plug-ins before you can use Fusion Middleware Control to view performance metrics.

After upgrading to 11g Release 1 (11.1.1) and performing some initial operations to verify the upgrade was successful, check the Oracle Virtual Directory home page in Fusion Middleware Control. You should see data for the Current Load and Average Response Time and Operations metrics.

If you do not see any data for these metrics, you must update the plug-ins configured to execute on specific operations. The work-around is to add the Performance Monitor plug-in to the operation-specific plug-in's configuration chain.

Perform the following steps to add the Performance Monitor plug-in to the operation-specific plug-in's configuration chain:

1. If the operation-specific plug-in is a Global-level plug-in, edit the server.os_xml file located in the ORACLE_INSTANCE/config/OVD/NAME_OF_OVD_COMPONENT/ directory.
If the operation-specific plug-in is an adapter-level plug-in, edit the adapters.os_xml file located in the ORACLE_INSTANCE/config/OVD/NAME_OF_OVD_COMPONENT/ directory.

Note:

If multiple adapters are configured, you must perform steps 2 and 3 for every adapter configuration in the adapters.os_xml file.

2. Locate the pluginChains element in the file. For example, if the Dump Transactions plug-in is configured to execute on the get operation, you will see something similar to the following:

Example 37-1 Dump Transactions Plug-In Configured for get Operation

<pluginChains xmlns="http://xmlns.oracle.com/iam/management/ovd/config/plugins">
<plugins>
<plugin>
<name>Dump Transactions</name>
<class>com.octetstring.vde.chain.plugins.DumpTransactions.DumpTransactions</class>
<initParams>
<param name="loglevel" value="info"/>
</initParams>
</plugin>
<plugin>
<name>Performance Monitor</name>
<class>com.octetstring.vde.chain.plugins.performance.MonitorPerformance</class>
<initParams/>
</plugin>
</plugins>
<default>
<plugin name="Performance Monitor"/>
</default>
<get>
<plugin name="Dump Transactions">
<namespace>ou=DB,dc=oracle,dc=com </namespace>
</plugin>
</get>
</pluginChains>

3. Add the following Performance Monitor plug-in element within the operation-specific configuration chain:

<plugin name="Performance Monitor"/>

For example:

Example 37-2 Adding the Performance Monitor to the Operation-Specific Plug-In Configuration Chain

<pluginChains xmlns="http://xmlns.oracle.com/iam/management/ovd/config/plugins">
<plugins>
<plugin>
<name>Dump Transactions</name>
<class>com.octetstring.vde.chain.plugins.DumpTransactions.DumpTransactions</class>
<initParams>
<param name="loglevel" value="info"/>
</initParams>
</plugin>
<plugin>
<name>Performance Monitor</name>
<class>com.octetstring.vde.chain.plugins.performance.MonitorPerformance</class>
<initParams/>
</plugin>
</plugins>
<default>
<plugin name="Performance Monitor"/>
</default>
<get>
<plugin name="Dump Transactions">
<namespace>ou=DB,dc=oracle,dc=com </namespace>
</plugin>
<plugin name="Performance Monitor"/>
</get>
</pluginChains>

4. Save the file.

5. Restart Oracle Virtual Directory.

37.1.10 Using a Wildcard when Performing an LDAPSEARCH on a TimesTen Database Causes an Operational Error

Currently, a TimesTen bug is preventing wildcard searches (such as "cn=t*") from working in a Database adapter with TimesTen.

To work around this problem, enable the Case Insensitive Search option and create the necessary linguistic indexes for any database columns used in the search.

For more information, see the related TimesTen Enhancement Request, Bug# 9885055 and Section 12.2.2 "Creating Database Adapters for Oracle TimesTen In-Memory Database" in the Oracle® Fusion Middleware Administrator's Guide for Oracle Virtual Directory.

37.1.11 ODSM Version 11.1.1.4.0 Does Not Support OVD Versions 11.1.1.2.0 or 11.1.1.3.0

Oracle Directory Services Manager Version 11.1.1.4.0 does not support Oracle Virtual Directory Versions 11.1.1.2.0 or 11.1.1.3.0.

Changes introduced in Oracle Directory Services Manager Version 11.1.1.4.0 improve configuration auditing, and these changes require that you use Oracle Virtual Directory 11.1.1.4.0.

37.1.12 ODSM Version 11.1.1.5.0 Does Not Support OVD Versions 11.1.1.2.0, 11.1.1.3.0, or 11.1.1.4.0

Oracle Directory Services Manager Version 11.1.1.5.0 does not support Oracle Virtual Directory Versions 11.1.1.2.0, 11.1.1.3.0, or 11.1.1.4.0.

Changes introduced in Oracle Directory Services Manager Version 11.1.1.5.0 improve configuration auditing, and these changes require that you use Oracle Virtual Directory 11.1.1.5.0.

37.1.13 ODSM Version 11.1.1.6.0 Does Not Support OVD Versions 11.1.1.2.0, 11.1.1.3.0, 11.1.1.4.0, or 11.1.1.5.0

Oracle Directory Services Manager Version 11.1.1.6.0 does not support Oracle Virtual Directory Versions 11.1.1.2.0, 11.1.1.3.0, 11.1.1.4.0, or 11.1.15.0.

Changes introduced in Oracle Directory Services Manager Version 11.1.1.6.0 improve configuration auditing, and these changes require that you use Oracle Virtual Directory 11.1.1.6.0.

37.1.14 Users with Non-ASCII Names Might Encounter Problems when Using ODSM with SSO

When Oracle Directory Services Manager is configured to use Oracle Access Manager 11g Release 1 (11.1.1.2) for single sign-on, a user whose name contains non-ASCII characters might observe the following issues after logging in:

- The user name displayed on the Home page is garbled.

- Single sign-on connections to Oracle Virtual Directory servers do not appear in the list of connections.

37.1.15 Creating an Attribute/Object Class Throws NPE Error

After upgrading Oracle Directory Services Manager, creating an attribute or an objectclass causes an NPE error.

Workaround:

Refresh the entries by clicking Refresh every time the creation fails.

37.1.16 Patch Required to Enable Account Lockout Feature

An additional Patch 10365116 is required to enable the Account Lockout functionality.

In addition, Oracle Virtual Directory may not update the AD badpasswdcount until the account is fully locked out, which means AD badpasswdcount shows the correct number when it reaches the bad password count setting in AD.

37.1.17 ODSM Problems in Internet Explorer 7

The Oracle Directory Services Manager interface might not appear as described in Internet Explorer 7.

For example, the Logout link might not be displayed.

If this causes problems, upgrade to Internet Explorer 8 or 9 or use a different browser.

37.1.18 Strings Related to New Enable User Account Lockout Feature on EUS Wizard Are Not Translated

The new Enable User Account Lockout feature (and related messages) provided in the Oracle Virtual Directory EUS wizard have not been translated.

37.1.19 All Connections Created In ODSM 11.1.1.1.0 Are Lost After Upgrading to OVD or OID Version 11.1.1.7.0

Due to some deployment changes made to Oracle Directory Services Manager version 11.1.1.2.0, any connections created in Oracle Directory Services Manager version 11.1.1.1.0 will be lost when you upgrade to Oracle Virtual Directory version 11.1.1.7.0 or Oracle Internet Directory version 11.1.1.7.0.

Oracle Directory Services Manager resumes caching connection details the first time you connect again after upgrading to Oracle Virtual Directory version 11.1.1.7.0 or Oracle Internet Directory version 11.1.1.7.0.

37.1.20 Incorrect ODSM Version Displays in Enterprise Manager Console After OVD Upgrade

The Oracle Directory Services Manager version automatically displays as 11.1.1.2.0 in the Enterprise Manager console for all patch set releases. This Oracle Directory Services Manager version number does not increment to match the patch set version when you upgrade.

37.1.21 Connection Issues to OVD

In non-Linux environments, if you have any issues connecting to Oracle Virtual Directory from Oracle Directory Services Manager, LDAP tools, or any other applications, you must disable NIO in the non-SSL listener by using the following steps:

1. From a command window, stop Oracle Virtual Directory:

$ORACLE_INSTANCE/bin/opmnctl stopproc ias-component=ovd1

2. Edit the $ORACLE_INSTANCE/config/OVD/ovd1/listeners.os_xml file as follows:

1. Locate this LDAP non-SSL listener section:

<ldap id="LDAP Endpoint" version="0">
<port>6501</port>
<host>0.0.0.0</host>
.........
.........
<tcpNoDelay>true</tcpNoDelay>
<readTimeout>0</readTimeout>
</socketOptions>
</ldap>

2. Modify the section by adding <useNIO>false</useNIO>, as indicated:

<ldap id="LDAP Endpoint" version="0">
<port>6501</port>
<host>0.0.0.0</host>
.........
.........
<tcpNoDelay>true</tcpNoDelay>
<readTimeout>0</readTimeout>
</socketOptions>
<useNIO>false</useNIO>
</ldap>

3. Start Oracle Virtual Directory:

$ORACLE_INSTANCE/bin/opmnctl startproc ias-component=ovd1

This modification should resolve the connection issues.

37.1.22 ODSM Version 11.1.1.70 Does Not Support OVD Versions 11.1.1.2.0, 11.1.1.3.0, 11.1.1.4.0, 11.1.1.5.0, or 11.1.1.6.0

Oracle Directory Services Manager Version 11.1.1.7.0 does not support Oracle Virtual Directory Versions 11.1.1.2.0, 11.1.1.3.0, 11.1.1.4.0, 11.1.1.5.0, or 11.1.1.6.0.

Changes introduced in Oracle Directory Services Manager Version 11.1.1.7.0 improve configuration auditing, and these changes require that you use Oracle Virtual Directory 11.1.1.7.0.

37.1.23 Modify Completes When Updating a Mandatory Attribute to Null

If a modify operation adds an attribute with an empty value, and the attribute type does not allow empty values, the operation no longer returns an error. For example, ldapmodify ADD sn with an empty value previously returned an Invalid Syntax error and now it does not return any errors. Other modify operation failures are properly reported.

37.1.24 Online Help Section is Not Working

The Oracle Directory Services Manager online help section does not work in Internet Explorer 10 (IE10) web browsers.

37.2 Configuration Issues and Workarounds

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

- Section 37.2.1, "Configuring an OVD/OID Adapter For SSL Mutual Authentication"

37.2.1 Configuring an OVD/OID Adapter For SSL Mutual Authentication

Neither Oracle Fusion Middleware Administrator's Guide for Oracle Virtual Directory nor Oracle Fusion Middleware Administrator's Guide describes how to set up an Oracle Virtual Directory/Oracle Internet Directory adapter for SSL Mutual Authentication. This information is provided in Note 1449118.1 and Note 1311791.1, which are available on My Oracle Support at:

https://support.oracle.com/

37.3 Documentation Errata

This section describes documentation errata in the Administrator's Guide for Oracle Virtual Directory. It includes the following topics:

- Deploying Oracle Unified Directory with Oracle Virtual Directory

37.3.1 Deploying Oracle Unified Directory with Oracle Virtual Directory

You can deploy Oracle Unified Directory as an LDAP data source with Oracle Virtual Directory. For information about how to deploy Oracle Unified Directory with Oracle Virtual Directory, see "Creating LDAP Adapters" in the Oracle® Fusion Middleware Administrator's Guide for Oracle Virtual Directory.

38 Oracle Authentication Services for Operating Systems

This chapter describes issues associated with Oracle Product. It includes the following topics:

- Section 38.1, "What is New with Oracle Authentication Services for Operating Systems 11.1.1.3 ?"

- Section 38.2, "General Issues and Workarounds"

38.1 What is New with Oracle Authentication Services for Operating Systems 11.1.1.3 ?

Oracle Fusion Middleware Release 11g R1 patchset 2 (11.1.1.3) is the first 11g release to include Oracle Authentication Services for Operating Systems. This product is also available as a download from http://www.oracle.com/technology/.

The following features and capabilities have been added to Oracle Authentication Services for Operating Systems since the 10g release:

- Full integration with Fusion Middleware Release 11g R1 patchset 2 (11.1.1.3). OAS4OS was not available with FMW 11g R1 or FMW 11g R1 patchset 1.

- Extended client platform support. For a full list see: http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html.

- New configuration scripts to enable PAM proxy user-based access to Oracle Internet Directory for enhanced security.

- Easy configuration of Oracle Internet Directory SSL using customer provided certificates for production deployments, or use of self signed certificates to test OID SSL connections.

- Restricting client access based on IP address.

- Easy reset of client configuration to support testing.

38.2 General Issues and Workarounds

For up-to-date information about product bugs and updates, see Note 1064891.1: Oracle Authentication Services for Operating Systems Documentation Addendum (11.1.1.3). This document is available on My Oracle Support at https://support.oracle.com/.

Part XI

Oracle Portal, Forms, Reports and Discoverer

Part XI contains the following chapters:

- Chapter 39, "Oracle Business Intelligence Discoverer"

- Chapter 40, "Oracle Forms"

- Chapter 42, "Oracle Portal"

- Chapter 41, "Oracle Reports"

39 Oracle Business Intelligence Discoverer

This chapter describes issues associated with Oracle Business Intelligence Discoverer. It includes the following topics:

Note:

This product is not supported on Oracle Solaris on x86-64 (64-Bit).

- Section 39.1, "General Issues"

- Section 39.2, "Issues Specific to Oracle BI Discoverer Plus Relational"

- Section 39.3, "Issues Specific to Oracle BI Discoverer Plus OLAP"

- Section 39.4, "Issues Specific to Oracle BI Discoverer Portlet Provider"

- Section 39.5, "Issues Specific to Oracle BI Discoverer Viewer"

- Section 39.6, "Issues Specific to Oracle BI Discoverer EUL Command Line for Java"

- Section 39.7, "Issues Specific to Oracle BI Discoverer Administrator"

39.1 General Issues

This section describes general issues that affect more than one Discoverer component. It includes the following topics:

- Section 39.1.1, "Error while Accessing a Discoverer Menu Option in Enterprise Manager"

- Section 39.1.2, "Issues with Metadata Repository and Oracle Database 10g Release 1"

- Section 39.1.3, "Compatibility Issues with Required Support Files"

- Section 39.1.5, "Additional Fonts Required for Non-ASCII Data When Exporting to PDF"

- Section 39.1.4, "Serif Font Issue in Worksheets"

- Section 39.1.6, "Query Prediction Requires the Majority of the Query Time"

- Section 39.1.7, "Word Wrapping Behavior with Oracle BI Discoverer Plus and Oracle BI Discoverer Viewer"

- Section 39.1.8, "Applet Appears Behind Browser Window"

- Section 39.1.9, "Issues with Mac OS X Browser and Oracle BI Discoverer Plus"

- Section 39.1.10, "Issues with Turkish Regional Settings"

- Section 39.1.11, "Multibyte Characters Rendered as Square Boxes in Exported PDF and Other Formats"

- Section 39.1.12, "Java Plug-in Not Downloaded Automatically on Firefox"

- Section 39.1.13, "HTTP 404 Error While Accessing Discoverer on a Remote Machine"

- Section 39.1.14, "Error While Launching Discoverer Plus Applet on an IPv6 Environment"

- Section 39.1.15, "Error While Updating the Discoverer Web Services Configuration Parameter"

- Section 39.1.16, "Exception Logged for Discoverer Web-Based Applications in an Extended Domain"

- Section 39.1.17, "Issue with Discoverer Application URL in Fusion Middleware Control after a Backup Recovery"

- Section 39.1.18, "Incorrect Version Number for Discoverer in Fusion Middleware Control 11g"

- Section 39.1.19, "Oracle BI Discoverer Startup Fails after Shutdown"

- Section 39.1.20, "The Database Export and Import Utility does not Work with Applications Mode EUL"

- Section 39.1.21, "Install-level Scripts are not Updated in Existing Instances after Patching"

- Section 39.1.22, "Oracle Business Intelligence Sessions Fail to Start"

39.1.1 Error while Accessing a Discoverer Menu Option in Enterprise Manager

In Enterprise Manager 11g Fusion Middleware Control, if you select the Catalog > Install from the Discoverer drop down menu, the following ADF error occurs:

ADFC-06003:EL expression
#{viewScope.general_info_dialog.model.regionBound}' for a region TaskFlowId
in binding 'genRegion' evaluated to null, a non-value must be specified"

Workaround

Select Catalog > Manage from the Discoverer menu and then select Catalog > Install. The Install Catalog page appears without any error.

39.1.2 Issues with Metadata Repository and Oracle Database 10g Release 1

When using Oracle Database 10g Release 1 (10.1.x) for the Metadata Repository or after upgrading the Metadata Repository to Oracle Database 10g Release 1, you might see the following error on the Oracle BI Discoverer Plus Connection pages, the Oracle BI Discoverer Viewer Connection pages, and the Public Connection definition page in Fusion Middleware Control:

The connection list is currently unavailable.
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "ORASSO.WWSSO_API_PRIVATE," line 258
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "ORASSO.WWSSO_UTL" line 728
ORA-28231: no data passed to obfuscation toolkit
ORA-06512: at line 1 Unable to retrieve connection list

To resolve this issue, make the following changes in the Metadata Repository database:

1. Edit the init%ORACLE_SID%.ora file. This file exists either in the dbs folder or the database folder. For example, in Windows, this file is located in the DB_install_home/database/ folder.

2. Add the following line to this file:
event="10946 trace name context forever, level 36"

3. If an spfile%ORACLE_SID%.ora exists in either the dbs folder or the database folder, rename the file to spfile%ORACLE_SID%.bak. Changes to init%ORACLE_SID%.ora are not loaded if the database server finds an spfile.

4. Log in as a sysadmin.

5. At the SQL prompt, shut down then start up the database server.

6. Restart the Oracle BI Discoverer server using the command opmnctl restartall.

39.1.3 Compatibility Issues with Required Support Files

The Oracle Database and other Oracle database client software (for example, SQL*Plus, the database export utility) use Oracle Required Support Files (RSF).

Oracle BI Discoverer also uses Oracle Required Support Files (RSF), specifically RSF version 11.1.0.7. This version of the Oracle Required Support Files is installed during Oracle BI Discoverer installation.

Note that the Required Support Files version 11.1.0.7 is incompatible with earlier versions of Oracle Database 10g. So if the machine on which you install Oracle BI Discoverer already has a version of Oracle Database 10g or database client software that is earlier than 11.1.0.7, there will be compatibility issues. For example, if you install Oracle BI Discoverer and attempt to run a version of SQL*Plus earlier than 11.1.0.7, then the following error is displayed:

ORA-12557 TNS: protocol adapter not loadable

To avoid the compatibility issues, upgrade Oracle Database 10g or database client software on the machine to the same version (11.1.0.7) as the version of the Required Support Files that were installed with Oracle BI Discoverer.

This issue does not exist for Oracle9i Database Server.

39.1.4 Serif Font Issue in Worksheets

You might notice unsightly font issues when using a non-English locale such as Czech. For example, when a worksheet uses a serif font, text in that worksheet might be displayed incorrectly on the screen and in printouts.

To work around this issue, update the file that maps the serif fonts. The name of this file differs depending on the locale in use. When you use Oracle BI Discoverer Plus Relational or Plus OLAP in English, the file is named file.properties. If you use Oracle BI Discoverer in a non-English locale, then the file name includes the code for the locale, such as file.properties.cs for Czech.

Update the mapping file with the following information:

serif.0=Times New Roman,EASTEUROPE_CHARSET serif.1=WingDings,SYMBOL_CHARSET,NEED_CONVERTED serif.2=Symbol,SYMBOL_CHARSET,NEED_CONVERTED

Consult the following Sun Web site for additional information about fonts:

http://java.sun.com/j2se/1.3/docs/guide/intl/addingfonts.html

39.1.5 Additional Fonts Required for Non-ASCII Data When Exporting to PDF

If you are running Oracle BI Discoverer Plus Relational or Plus OLAP on a Macintosh or Linux client machine, you must add the appropriate font files to your client machine to allow exported PDF files to display non-ASCII data correctly.

These font files include Albany fonts with names such as ALBANWTJ.TTF and ALBANWTK.TTF. The files are stored in the /utilities/fonts directory on the CD-ROM or DVD for the Oracle Application Server Metadata Repository Upgrade Assistant.

To install the additional required fonts:

1. Navigate to the /utilities/fonts directory on the CD-ROM or DVD for the OracleAS Metadata Repository Upgrade Assistant.

2. Copy the appropriate Albany TTF file from the /utilities/fonts directory to the plug-in directory in the $jdk/jre/lib/fonts directory on the Macintosh or Linux client machine.

39.1.6 Query Prediction Requires the Majority of the Query Time

When using Oracle BI Discoverer with a relational data source, you can predict the time that is required to retrieve information by setting the value of the QPPEnable preference to 1. However, in some circumstances, the majority of the time taken to retrieve information is consumed by the prediction activity itself.

To work around this issue, set the value of the QPPObtainCostMethod preference to 0 (use the EXPLAIN PLAN statement to predict query times) rather than to 1 (use dynamic views to predict query times).

For more information about setting preferences, see the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

39.1.7 Word Wrapping Behavior with Oracle BI Discoverer Plus and Oracle BI Discoverer Viewer

To use word wrap settings correctly, you must understand how they are designed for Oracle BI Discoverer:

- Oracle BI Discoverer Plus: Word wrap settings that you make in Oracle BI Discoverer Plus are saved in the worksheet and affect the display of worksheets in Oracle BI Discoverer Plus and when printing to PDF.

- Oracle BI Discoverer Viewer: Word wrap settings that you see in the Print Settings dialog work as follows:

- The word wrap settings do not affect the display of worksheets in Oracle BI Discoverer Viewer.

- For relational data:

- The word wrap settings do affect the printing of worksheets to PDF.

- If the Always wrap text when size exceeds column width box is checked, then the print settings in Oracle BI Discoverer Viewer do override the settings made in a worksheet in Oracle BI Discoverer Plus Relational for printing to PDF.

- If the Always wrap text when size exceeds column width box is not checked, then the print settings in Oracle BI Discoverer Viewer do not override the settings made in a worksheet in Oracle BI Discoverer Plus Relational for printing to PDF.

- For OLAP data:

- The word wrap settings do not affect the printing of worksheets to PDF.

- Regardless of whether the Always wrap text when size exceeds column width check box is selected, the print settings in Oracle BI Discoverer Viewer never override the settings made in a worksheet in Oracle BI Discoverer Plus OLAP for printing to PDF.

39.1.8 Applet Appears Behind Browser Window

When you use Microsoft Internet Explorer, the Oracle BI Discoverer Plus Relational or Plus OLAP applet initialization and download dialog appears behind the browser window from which it was launched. After the applet is downloaded and initialized, it appears in front of the browser window from which it was launched.

To work around this issue:

- Use a browser other than Internet Explorer, such as Netscape Navigator or Mozilla Firefox.

- Use the Oracle BI Discoverer Plus URL parameter _plus_popup=false, which is documented in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

39.1.9 Issues with Mac OS X Browser and Oracle BI Discoverer Plus

The following are issues that you might encounter when you use the Safari browser on Mac OS X with Oracle BI Discoverer Plus Relational or Plus OLAP:

- If you resize the browser window in the applet, then some parts of the content might be clipped. To work around this problem, always maximize the browser window for the applet when working with Mac OS X.

- Keyboard combinations (also known as mnemonics) do not work in Oracle BI Discoverer Plus Relational and Plus OLAP.
For example, you cannot press Alt+F to access the File menu.

- In the Share Workbooks dialog of Oracle BI Discoverer Plus Relational, the leading characters of the "Shared:" list are clipped. In other words, the left edge of the list is truncated. For example, if you shared a workbook with DISCODEV, then you will only see SCODEV in the list. The title for the list is also truncated such that you see only the vertical line of the "d" in "Shared" and the colon (that is, "l:").
The dialog continues to work as expected, but you might have difficulty reading the names in the "Shared:" list.

This issue has no workaround.

39.1.10 Issues with Turkish Regional Settings

Because of Sun JRE 1.4 bug 4688797, you might encounter issues when connecting to a database schema from a computer that has Turkish regional settings. You will encounter the issue when you attempt to connect to a database schema with a user name that contains certain letters, such as the letter 'I' or 'i', for example, in "bibdemo". See the Sun JRE bug for information on the letters that are affected.

To work around this issue, either do not use Turkish regional settings or use a user name that does not contain the affected letters.

39.1.11 Multibyte Characters Rendered as Square Boxes in Exported PDF and Other Formats

When you export a workbook to PDF and other formats, multibyte characters (for example, Korean, Japanese, and Chinese characters) appear as square boxes.

To work around this issue, copy the following Albany fonts from ORACLE_HOME/jdk/jre/lib/fonts to the fonts folder of your JDK (Oracle JRockit or Sun) within the MW_HOME directory. For example, if you are using Sun JDK, you must copy the fonts to MW_HOME/jre/jdk160_11/lib/fonts.

- AlbanWTJ.ttf

- AlbanWTK.ttf

- AlbanWTS.ttf

- AlbanWTT.ttf

- ALBANYWT.ttf

39.1.12 Java Plug-in Not Downloaded Automatically on Firefox

When you attempt to connect to Discoverer Plus by using the Mozilla Firefox browser on a machine that does not have Java 1.6 installed, the browser does not download the JRE 1.6 plug-in automatically. Instead, the browser displays the following message:

Additional plugins are required to display this page...

You must download the JRE 1.6 plug-in (by clicking the Install Missing Plugin link) and install it manually.

39.1.13 HTTP 404 Error While Accessing Discoverer on a Remote Machine

When you attempt to connect to Discoverer Plus, occasionally, the browser returns an HTTP 404 (File Not Found) error.

The page loads correctly when you refresh the browser a few times.

39.1.14 Error While Launching Discoverer Plus Applet on an IPv6 Environment

If the Web tier is on an IPv6 machine, when you start Discoverer Plus, the following error message might be displayed:

Attempt1. RMI protocol over JRMP transport: Connection refused to host: DiscoServerMahcineName;nested exception is:
@ java.net.ConnectionException: Connection timed out

To work around this issue, in the System MBean Browser of Fusion Middleware Control, change the TransportProtocols attribute of the Plus Config MBean to "jrmp,http" (or "jrmp,https" if Discoverer Plus is accessed by using secure HTTP).

39.1.15 Error While Updating the Discoverer Web Services Configuration Parameter

When you update the web services configuration parameter (Maximum Sessions) using the Discoverer Web Services Configuration page of Fusion Middleware Control and click Apply, the following error message is displayed:

Applying changes - Failed.
Exception caught:

You can ignore the error message because the changes are applied even if the exception is thrown. Alternatively, you can update the MaxSessions attribute of the WebServicesConfig MBean in the System MBean Browser of Fusion Middleware Control.

39.1.16 Exception Logged for Discoverer Web-Based Applications in an Extended Domain

When you extend a domain and add Discoverer application in a remote machine, you may see the following exception in the WebLogic Server log:

java.lang.IllegalArgumentException: ODL-52057: The handler 'disco-server-handler' is not defined.

To work around this issue, modify the log_handlers and loggers elements in the logging.xml file located in the DOMAIN_HOME/config/fmwconfig/servers/WLS_DISCO folder of the machine where the domain exists.

In the log_handlers section, add the handlers as follows:

<log_handler name='discoverer-handler'
class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='path'
value='${domain.home}/servers/${weblogic.Name}/logs/discoverer/diagnostic.log'
/>
<property name='maxFileSize' value='1048576'/>
<property name='maxLogSize' value='10485760'/>
<property name='format' value='ODL-Text'/>
<property name='useSourceClassAndMethod' value='false'/>
</log_handler>

<log_handler name='disco-server-handler'
class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='path'
value='${domain.home}/servers/${weblogic.Name}/logs/discoverer/server/diagnost
ic.log'/>
<property name='maxFileSize' value='1048576'/>
<property name='maxLogSize' value='10485760'/>
<property name='format' value='ODL-Text'/>
</log_handler>

In the loggers sections, add the following elements:

<logger name='ORACLE.DISCOVERER.VIEWER' level='TRACE:32'
useParentHandlers='false'>
<handler name='discoverer-handler'/>
<handler name='odl-handler'/>
</logger>
<logger name='ORACLE.DISCOVERER.PORTLET_PROVIDER' level='TRACE:32'
useParentHandlers='false'>
<handler name='discoverer-handler'/>
<handler name='odl-handler'/>
</logger>
<logger name='ORACLE.DISCOVERER.MODEL' level='TRACE:32'
useParentHandlers='false'>
<handler name='discoverer-handler'/>
<handler name='odl-handler'/>
</logger>
<logger name='ORACLE.DISCOVERER.WEB_SERVICES' level='TRACE:32'
useParentHandlers='false'>
<handler name='discoverer-handler'/>
<handler name='odl-handler'/>
</logger>
<logger name='ORACLE.DISCOVERER.SERVER' level='TRACE:32'
useParentHandlers='false'>
<handler name='disco-server-handler'/>
<handler name='odl-handler'/>
</logger>

After adding these elements, save the logging.xml file, and restart the Administration Server and Discoverer Managed Servers.

39.1.17 Issue with Discoverer Application URL in Fusion Middleware Control after a Backup Recovery

When you recover the Oracle BI Discoverer middle tier from a backup, the Discoverer application URL in the Discoverer Home page of Fusion Middleware Control point to a wrong location.

You must configure the application URLs that appear on the Oracle BI Discoverer Home page in Fusion Middleware Control after recovering the Oracle BI Discoverer middle tier from a backup.

For more information, see "How to configure application URLs displayed on the Fusion Middleware Control Discoverer Home page" in the Oracle Business Intelligence Discoverer Configuration Guide.

39.1.18 Incorrect Version Number for Discoverer in Fusion Middleware Control 11g

In Fusion Middleware Control 11g, the Enterprise Manager Fusion Middleware Control pages display wrong version number (11.1.1.2.0) for the Oracle BI Discoverer application. The correct version number for Oracle BI Discoverer is 11.1.1.4.0.

39.1.19 Oracle BI Discoverer Startup Fails after Shutdown

When you first start up the Discoverer application from Oracle Enterprise Manager Fusion Middleware Control or Oracle WebLogic Administration Console after shutting down the application instance, the startup fails with error logs.

To work around this issue, start the Discoverer application again. The second time the application starts without any error message.

39.1.20 The Database Export and Import Utility does not Work with Applications Mode EUL

You cannot use the standard database export and import utilities to export or import the database, EUL tables and database objects referenced by the Applications Mode EUL definitions. The standard database export and import utility can be used only for standard EUL definitions.

To work around this issue, use the Discoverer Export Wizard in Discoverer Administrator to export EUL objects to an EUL export file (*.EEX). After exporting the EUL objects, you can import the .EEX file using the Discoverer Import Wizard.For more information, see "Creating and Maintaining End User Layers" in Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Discoverer.

39.1.21 Install-level Scripts are not Updated in Existing Instances after Patching

When you upgrade Oracle Discoverer 11gR1 PS1 to 11gR1 PS2 or 11gR1 PS3, the patch will be installed in the ORACLE_HOME folder. Therefore, script changes in the new patch set will not be available for existing Oracle Discoverer instances, which are located in the ORACLE_INSTANCE folder. However, new instances that are created after the patch upgrade will be updated.

To work around this issue, after a patch upgrade manually copy the new scripts to the existing ORACLE_INSTANCE folders. For example, copy the new discenv.sh script file from ORACLE_HOME to the ORACLE_INSTANCE/Discoverer/Discoverer_instance-name/util/ folder.

For more information about Discoverer file locations, see "Oracle BI Discoverer Configuration Files" in Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

39.1.22 Oracle Business Intelligence Sessions Fail to Start

Oracle Business Intelligence Discoverer Plus and Oracle Business Intelligence Discoverer Viewer sessions fail to start after Oracle Business Intelligence 11g Release 1 (11.1.1.7.0) is installed on Oracle Solaris 11 on SPARC (64-bit) systems and display one of the following error messages:

From the command line:

dis51ws process is dumping core

From the graphical user interface (GUI):

A connection error.
Attempt 1. CORBA protocol : 0 of 1 processes started.

Workaround:

Complete the following steps for a workaround:

1. Log in to the system as the root user.

2. Open the /etc/security/policy.conf file.

3. Add the proc_priocntl privilege to the PRIV_DEFAULT parameter as follows:

PRIV_DEFAULT=basic,proc_priocntl

4. Save and close the file.

5. Restart the system.

6. Log in to the system as a non-root user and run the sessions for Oracle Business Intelligence Discoverer Plus and Oracle Business Intelligence Discoverer Viewer.

39.2 Issues Specific to Oracle BI Discoverer Plus Relational

This section describes issues that are specific to Oracle BI Discoverer Plus Relational. It includes the following topics:

- Section 39.2.1, "Text Appearing Truncated or Clipped"

- Section 39.2.2, "Non-ASCII Characters Not Saved Correctly in Title or Text Area"

- Section 39.2.3, "Canceling Query Causes Discoverer to Hang"

- Section 39.2.4, "Nonaggregable Values Not Displayed for Scheduled Workbooks"

- Section 39.2.5, "Migrating Oracle BI Discoverer Plus Relational Worksheets from Oracle BI Discoverer Desktop"

39.2.1 Text Appearing Truncated or Clipped

When you run Oracle BI Discoverer Plus Relational with Sun Java Plug-in 1.4.2_06, the Browser Look and Feel, and an Asian language (such as Korean or Chinese), you might notice that static text and text in buttons in the user interface appears truncated or clipped. To work around this issue, do one of the following:

- Change the Look and Feel to either Plastic or System.

- Use JInitiator 1.3.1.17 instead of the Sun Java Plug-in.

- Install Sun Java Plug-in version 1.4.2_10 or higher.

39.2.2 Non-ASCII Characters Not Saved Correctly in Title or Text Area

When you save a new workbook in Oracle BI Discoverer Plus, any text characters beyond the standard ASCII characters are not saved correctly when all the conditions that are described in the following list are met:

- You are logged in as an Oracle e-Business Suite user.

- The language for the computer is not English.

- Oracle BI Discoverer Plus is running against an Oracle e-Business Suite database that does not have that non-English language installed.

This issue has no workaround.

39.2.3 Canceling Query Causes Discoverer to Hang

If you cancel a query that is running in Oracle BI Discoverer Plus Relational, then you are prompted to either choose YES to undo the changes or NO to show a blank sheet. If you choose YES, then Oracle BI Discoverer Plus Relational hangs and you must close the window and restart.

To work around this issue, choose NO to show a blank worksheet. You can then refresh the sheet and continue working.

39.2.4 Nonaggregable Values Not Displayed for Scheduled Workbooks

Oracle BI Discoverer Plus Relational does not display nonaggregable values for scheduled workbooks. In other words, Oracle BI Discoverer Plus Relational processes scheduled workbooks as if you selected the Show values that cannot be aggregated as: <Non-aggregable label> option in the Worksheet Properties dialog: Aggregation tab.

Nonaggregable values include those based on the following SQL functions:

- A CASE SQL statement

- A DECODE SQL statement

- A PL/SQL function

- A DISTINCT SQL statement

- An analytic function

39.2.5 Migrating Oracle BI Discoverer Plus Relational Worksheets from Oracle BI Discoverer Desktop

If you use Oracle BI Discoverer Plus Relational to open a worksheet that was created using Oracle BI Discoverer Desktop Version 9.0.4 (or earlier), the size of the title area for that worksheet defaults to two lines in height. A title height of two lines might be a problem if a worksheet title requires more than or less than two lines. If you want to change the size of the title area, you must resize the title area manually and save the worksheet.

To resize the title area for a worksheet, open the worksheet and drag the bar at the bottom of the title area pane up or down.

39.3 Issues Specific to Oracle BI Discoverer Plus OLAP

This section describes issues that are specific to Oracle BI Discoverer Plus OLAP. It includes the following topics:

- Section 39.3.1, "Issues with Applet Download"

- Section 39.3.2, "Disabled Netscape and Mozilla Browsers"

- Section 39.3.3, "Tabbing Fails to Synchronize Menus"

- Section 39.3.4, "Esc Key Fails to Close Certain Dialogs"

- Section 39.3.5, "Link Tool Works Incorrectly in Some Locales"

- Section 39.3.6, "Memory Issues when Exporting Extremely Large Graphs"

- Section 39.3.7, "Issue While Printing Worksheets with Large Data Values"

- Section 39.3.8, "Issues with Titles and Text Areas"

- Section 39.3.9, "Errors with JAWS and Format Dialogs"

39.3.1 Issues with Applet Download

There may be Oracle Business Intelligence Discoverer Plus applet download issues when caching has been enabled in the Sun Java Plug-In.

To avoid these issues, disable caching in the plug-in.

39.3.2 Disabled Netscape and Mozilla Browsers

When you are running Netscape 7.x or Mozilla browsers, the Netscape and Mozilla Mail clients and Web browser may become disabled when Oracle BI Discoverer Plus OLAP modal dialogs are displayed.

Dismissing the Oracle BI Discoverer Plus OLAP dialogs resumes normal operation for the Netscape and Mozilla tools.

39.3.3 Tabbing Fails to Synchronize Menus

When you use the Tab key to select items in a worksheet, the menus do not always synchronize to reflect the currently selected item.

This issue has no workaround.

39.3.4 Esc Key Fails to Close Certain Dialogs

The Esc key does not close the following dialogs: Totals, New Total, Parameter, and Manage Catalog.

Instead of using the Esc key, click the Close or OK button.

39.3.5 Link Tool Works Incorrectly in Some Locales

The Link tool, which enables users to drill out to external URLs from a crosstab cell, might not work correctly in all locales due to URL encoding issues.

This issue has no workaround.

39.3.6 Memory Issues when Exporting Extremely Large Graphs

Exporting extremely large graphs can cause memory issues, requiring a restart of the Oracle BI Discoverer Plus OLAP session.

This issue has no workaround.

39.3.7 Issue While Printing Worksheets with Large Data Values

When printing a worksheet that contains large numbers in the data cells, the string ####### may be printed instead of the actual numbers.

This issue has no workaround.

39.3.8 Issues with Titles and Text Areas

The following issues exist with titles and text areas:

- Nonempty titles and text areas are printed even if they are hidden in the worksheet.
This issue has no workaround.

- When you set the title or text area background to green and export the worksheet to an HTML file, the background is incorrectly set to red in the exported file.
This issue has no workaround.

39.3.9 Errors with JAWS and Format Dialogs

When you use JAWS, you will notice errors when you attempt to format graphs and crosstabs using the Format dialogs.

This issue has no workaround.

39.4 Issues Specific to Oracle BI Discoverer Portlet Provider

This section describes issues that are specific to Oracle BI Discoverer Portlet Provider. It includes the following topics:

- Section 39.4.1, "Inability to Turn Off Display of Range Min and Max as Labels"

- Section 39.4.2, "Issues with Discoverer Portlets in WebCenter"

- Section 39.4.3, "Issue while Publishing Discoverer WSRP Portlets in Portals Other than Oracle Portal and Oracle WebCenter"

- Section 39.4.4, "Issue with Portlet Titles in Discoverer WSRP Portlets Published on IBM WebSphere"

- Section 39.4.5, "Issue with Color and Date Pickers in Discoverer WSRP Portlets"

- Section 39.4.6, "Worksheet Parameter LOV is not Displayed in Discoverer WSRP Portlets on IBM WebSphere Portal"

- Section 39.4.7, "Issue with Worksheet Parameter LOV Pop-Up Window in Discoverer WSRP Portlets"

39.4.1 Inability to Turn Off Display of Range Min and Max as Labels

In the Display Options of a gauge portlet, the Minimum Value and Maximum Value range labels are selected but are also disabled so that you cannot deselect the display of those values. The values for the minimum and the maximum appear at the ends of every gauge in the set except for those gauges where the value to be gauged is out of the range of the minimum and the maximum values. For those gauges where the value to be displayed exceeds the range of the minimum and the maximum values, the gauge will automatically adjust to accommodate the value.

This issue has no workaround.

39.4.2 Issues with Discoverer Portlets in WebCenter

The following issues exist for Discoverer portlets displayed in Oracle WebCenter.

- When a Worksheet portlet is displayed in Oracle WebCenter, the links to navigate to the next set of records does not work.

- When a List of Worksheets portlet is displayed in Oracle WebCenter, the Expand All Icons link does not work.

To work around these issues, set the RenderPortletInIFrame attribute of the portlet tag to TRUE. For more information, see "Setting Attribute Values for the Portlet Tag" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

39.4.3 Issue while Publishing Discoverer WSRP Portlets in Portals Other than Oracle Portal and Oracle WebCenter

When you publish Discoverer WSRP Portlets in portals other than Oracle Portal and Oracle WebCenter (such as Oracle WebLogic Portal and IBM WebSphere Portal), the pop-up windows for input selection will have the same page layout as the portal page with all navigation options. If you select any of these navigation options, the current portlet state will be lost. You might need to start publishing the portlet from the beginnng.

The issue has no workaround.

39.4.4 Issue with Portlet Titles in Discoverer WSRP Portlets Published on IBM WebSphere

You cannot dynamically change the portlet title of a Discoverer WSRP portlet in IBM WebSphere after it is published. Static title is rendered in the portal for each portlet instance.

To work around this issue, set a meaningful title for the portlet by editing the title using the Set Title or Description option in the WebSphere portal. For more information about changing the title of a portlet, see WebSphere documentation.

39.4.5 Issue with Color and Date Pickers in Discoverer WSRP Portlets

The Color and Date pickers in Discoverer WSRP Portlets do not work on portals other than Oracle WebCenter.

On portals such as Oracle Portal, Oracle WebLogic Portal and IBM WebSphere, to workaround this issue, set the value of the configuration parameter useInlineUIXPicker to true. The default value of this parameter is false. When you set the useInlineUIXPicker parameter to true, set the color and date as follows:

- Inline color pickers are enabled in the Gauges Selection page and you can select a color from the palette.

- You cannot select the color using the Format option of the Personalize menu of the worksheet. Use the Analyze option in the portlet window to change the color.

- The Date picker in the Refresh option will not be available. Enter the date manually.

39.4.6 Worksheet Parameter LOV is not Displayed in Discoverer WSRP Portlets on IBM WebSphere Portal

The Worksheet Parameter LOV icon is not displayed when you publish Discoverer WSRP portlets in IBM WebSphere portal.To work around this issue, enter parameter values manually.

39.4.7 Issue with Worksheet Parameter LOV Pop-Up Window in Discoverer WSRP Portlets

In Oracle Portal and Oracle WebLogic Portal, when you select values from the parameter LOV from a worksheet portlet published by using the Discoverer WSRP Portlet producer, the pop-up window is not getting closed on selection of values.You must explicitly close the pop-up window after selection of values.

39.5 Issues Specific to Oracle BI Discoverer Viewer

This section describes issues that are specific to Oracle BI Discoverer Viewer. It includes the following topics:

- Section 39.5.1, "Drill Icons Cannot Be Hidden in Oracle BI Discoverer Viewer"

- Section 39.5.2, "Error Displaying Page for Multiple SSO Users"

- Section 39.5.3, "Inability to Disable the Display of Row Numbers"

- Section 39.5.4, "Issues with Oracle BI Discoverer Viewer Embedded in Frames"

- Section 39.5.5, "Issue Exporting to PDF Under Certain Circumstances"

- Section 39.5.6, "Issue When Changing Colors for Oracle BI Discoverer Viewer in Fusion Middleware Control on Mac OS X"

- Section 39.5.7, "Discoverer Catalog Items Not Visible From UNIX Servers"

- Section 39.5.8, "Known Bug with JAWS Prevents Drilling Using the Enter Key"

- Section 39.5.9, "JAWS Does Not Read Asterisks that Precede Fields"

- Section 39.5.10, "Oracle BI Discoverer Viewer Pages are not Cached by Oracle Web Cache"

39.5.1 Drill Icons Cannot Be Hidden in Oracle BI Discoverer Viewer

The pref.txt file contains a setting called ShowDrillIcon, which is not functioning properly. If you set ShowDrillIcon to False, then drill icons are still displayed in Oracle BI Discoverer Viewer.

The issue has no workaround.

39.5.2 Error Displaying Page for Multiple SSO Users

When an Oracle Single Sign-On (SSO) user tries to view a worksheet from a List of Worksheets Portlet by using the same browser window that is already being used by an SSO user to view that worksheet, the second user sees the following error message: "The page cannot be displayed".

To work around this issue, start a new browser session and view the worksheet.

39.5.3 Inability to Disable the Display of Row Numbers

Oracle BI Discoverer Viewer no longer offers the ability to disable the display of row numbers in a tabular worksheet.

39.5.4 Issues with Oracle BI Discoverer Viewer Embedded in Frames

Users might see JavaScript errors such as "Access Denied" or other unexpected behavior when both of the following conditions are met:

- When Oracle BI Discoverer Viewer is embedded in an IFRAME tag.

- When the domain of the server that hosts the HTML page with the IFRAME tag is different from the domain of the Oracle BI Discoverer server that is running Oracle BI Discoverer Viewer.

Use one of the following workarounds for this issue:

- Run the Oracle BI Discoverer server and the server that hosts the HTML page with the IFRAME tag in the same domain.

- Alter the Common2_2_20.js file on the Oracle BI Discoverer server using the following steps:

1. Use Fusion Middleware Control to stop all services on the middle tier for Oracle Business Intelligence.

2. Make a backup copy of the Common2_2_20.js file from the following directory:
domain\servers\managed_server\stage\discoverer\release\discoverer\discoverer.war\cabo\jsLib

domain is the path of directory that contains the domain.

managed_server is the name of the managed server on which the Discoverer application is deployed.

release is the release number of Discoverer. For example, 11.1.1.1.0.

3. Edit the Common2_2_20.js file and replace all occurrences of "parent._pprSomeAction" with "window._pprSomeAction".

4. Use Fusion Middleware Control to start all services on the middle tier for Oracle Business Intelligence.

5. Clear the browser cache on the client machine so that the new Common2_2_20.js file will be used.

39.5.5 Issue Exporting to PDF Under Certain Circumstances

If you are using Oracle BI Discoverer Viewer with Microsoft Internet Explorer, you might encounter an error message when you try to export to PDF a worksheet that is named with non-ASCII characters, a space, and a number. The export fails and you will see a message similar to the following one:

No %PDF- in a file header

Use one of the following methods to work around this issue:

- Use a browser other than Internet Explorer, such as one from Netscape or Mozilla.

- Remove the space between the non-ASCII characters and the number, or remove the number altogether.

- Continue to use Internet Explorer and leave the space in the worksheet name, but follow these steps:

1. Start the Adobe Reader.

2. From the Edit menu, choose Preferences, then click Internet.

3. Clear the Display PDF in browser box.

39.5.6 Issue When Changing Colors for Oracle BI Discoverer Viewer in Fusion Middleware Control on Mac OS X

You can use Fusion Middleware Control to change the look and feel of Oracle BI Discoverer Viewer. That page contains a color chooser, or palette. If you use Fusion Middleware Control on Mac OS X with the Safari browser, then the page does not correctly enter the color code when you select a color from the palette.

To work around this issue, you can either use the Firefox browser or you can enter a color code directly.

The color codes are standard HTML hexadecimal color codes. You can enter one of the 49 colors that are available in the color palette, or you can enter any valid HTML hexadecimal color code.

The following list provides examples of colors with their codes:

white #FFFFFF
grey #CCCCCC
black #000000
pink #FFCCCC
red #FF0000
light yellow #FFFFCC
yellow #FFFF00
light green #99FF99
dark green #00CC00
light blue #66FFFF
dark blue #3333FF
lavender #FF99FF
purple #CC33CC

39.5.7 Discoverer Catalog Items Not Visible From UNIX Servers

You might encounter issues when trying to see items in the Discoverer Catalog when using Oracle BI Discoverer Viewer with OLAP data on UNIX servers.

You can resolve this issue on the middle-tier machine where Oracle BI Discoverer runs by performing the following steps.

To check whether the time zone variable is set:

1. Open a shell prompt.

2. Type echo $TZ to display the time zone setting.

If no value is displayed, then the time zone has not been set.

To set the time zone variable:

1. Open a shell prompt.

Note:

The UNIX user that sets the TZ variable must be the same UNIX user that installed Oracle Business Intelligence.

2. If you do not know which shell you are using, type $echo $SHELL to display the name of the current shell.

3. Set the time zone as appropriate.
For example, to set the time zone variable for US/Pacific time:

- For the Bourne, Bash, or Korn shell, type export TZ=US/Pacific

- For the C shell, type setenv TZ US/Pacific

Note:

Consult the shell documentation for the appropriate values.

39.5.8 Known Bug with JAWS Prevents Drilling Using the Enter Key

Oracle BI Discoverer can be used in conjunction with assistive technologies such as the JAWS screen reader. However, a bug in JAWS prevents the drilling feature from working correctly in Oracle BI Discoverer Viewer when querying a relational data source.

Assume that you use the keyboard to navigate to the drill icon beside an item in the worksheet header. When you press the Enter key to drill on that header item, the Drill page should be displayed as described in the "Worksheet Display page: (Page level tools and controls)" topic in the Help system and the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Discoverer Viewer).

However, when JAWS is running, the Drill page is not displayed. Instead, the Drill popup menu is displayed. It is not possible to select items from this popup menu by using the keyboard, and JAWS does not read the items on the popup menu.

This issue has no workaround.

39.5.9 JAWS Does Not Read Asterisks that Precede Fields

In Oracle BI Discoverer Viewer, an asterisk that precedes a text field indicates that the user is required to enter a value into that text field. The JAWS screen reader does not read an asterisk that precedes a required text field and does not otherwise indicate that the field is required.

This issue has no workaround.

39.5.10 Oracle BI Discoverer Viewer Pages are not Cached by Oracle Web Cache

When using Oracle BI Discoverer with Oracle Web Cache, note the following:

- When Oracle Single Sign-On is enabled, Oracle Web Cache does not cache Oracle BI Discoverer Viewer pages, regardless of whether they are accessed using a public connection or a private connection.

- If an Oracle BI Discoverer Viewer page is accessed directly through a URL and the URL contains URL parameters that specify login details (for example, user name, database name), then Oracle Web Cache does not cache the page. For example, Oracle Web Cache does not cache worksheet "Sheet 1" in workbook "Workbook 2" that is displayed by using the following URL:
http://<host.domain>:<port>/discoverer/viewer?us=video5&db=db1&eul=VIDEO5&wbk=Workbook+2&ws=Sheet+1

Note:

In the example above, us= specifies the database user name, and db= specifies the database name.

However, Oracle Web Cache does cache worksheet "Sheet 1" in workbook "Workbook 2" if a user logs in manually to Oracle BI Discoverer Viewer by using the same login details, and navigates to the worksheet.

- You must increase the delays for Oracle BI Discoverer Viewer by at least 60 seconds for Oracle BI Discoverer Viewer to properly cache workbooks with Oracle Web Cache.
For more information, see "How to configure Discoverer Viewer to enable maximum caching" in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

39.6 Issues Specific to Oracle BI Discoverer EUL Command Line for Java

This section describes issues that are specific to Oracle BI Discoverer EUL Command Line for Java.

39.6.1 Issue with Exported Non-ASCII Data

When you export multibyte or Eastern European data (such as the names of items and business areas in Japanese or Russian characters) from Oracle BI Discoverer EUL Command Line for Java on a platform other than Windows, the exported data is corrupted.

To work around this issue, edit the discwb.sh file that is located in the ORACLE_HOME/discoverer directory before exporting. Change the character set value in the NLS_LANG variable to UTF8.

For example, if the original setting of the variable is:

NLS_LANG="GERMAN_GERMANY.WE8ISO8859P1"

Change the setting to:

NLS_LANG="GERMAN_GERMANY.UTF8"

39.7 Issues Specific to Oracle BI Discoverer Administrator

This section describes issues that are specific to Oracle BI Discoverer Administrator. It includes the following topic:

- Section 39.7.1, "Issue with Installation of Video Stores Tutorial"

39.7.1 Issue with Installation of Video Stores Tutorial

Before installing the video stores tutorial in Oracle Database 10g Enterprise Edition Release 2 (version 10.2.0.1 and higher), you must manually create the VIDEO5 user. If you attempt to install the video stores tutorial in Oracle Database 10g Enterprise Edition Release 2, then the installation will fail if the VIDEO5 user does not already exist. To work around this issue:

1. Create the VIDEO5 user manually by completing these steps:

1. Access Oracle Database 10g with SQL*Plus, Enterprise Manager, or any SQL command line tool.

2. Create the VIDEO5 user.

3. Grant CONNECT and RESOURCE privileges to the VIDEO5 user.

For more information about creating users and granting privileges, see the Oracle Database SQL Reference or your DBA

2. Connect to Discoverer Administrator as the EUL owner and install the tutorial. You must enter the VIDEO5 user password during installation.
For information about installing the video stores tutorial, see the Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Discoverer.

40 Oracle Forms

This chapter describes issues associated with Oracle Forms. It includes the following topics:

Note:

This product is not supported on Oracle Solaris on x86-64 (64-Bit).

- Section 40.1, "General Issues and Workarounds"

- Section 40.2, "Configuration Issues and Workarounds"

- Section 40.3, "Documentation Errata"

40.1 General Issues and Workarounds

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

- Section 40.1.1, "Backwards Compatibility with Earlier Releases"

- Section 40.1.2, "Linux/UNIX Issues and Workarounds"

40.1.1 Backwards Compatibility with Earlier Releases

For information about upgrading from Forms 6i, see the "Upgrading to Oracle Forms Services 11g" chapter in Oracle Fusion Middleware Forms Services Deployment Guide. For information about changed or obsolete features, see the Oracle Forms Upgrading Oracle Forms 6i to Oracle Forms 11g Guide.

For upgrading from Oracle Forms 10g and prior releases, you can use the Upgrade Assistant. For more information, see the Oracle Fusion Middleware Upgrade Planning Guide and Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer.

Additional information about backwards compatibility is included in My Oracle Support Note 113987.1 at: http://myoraclesupport.oracle.com

Regardless from which version of Oracle Forms you are upgrading, you will need to recompile your applications and restart Oracle Forms.

Before restarting the Oracle WebLogic managed server, all the JVM Controller processes (dejvm) started by that server must be stopped. Otherwise, WLS_FORMS will not restart after a shutdown.

When two Oracle instances with Forms Services are configured, using a single ORACLE_HOME on a Windows machine, then the FORMS_ORACLE_INSTANCE registry entry of the second ORACLE_INSTANCE takes precedence. It is recommended that the Forms Builder component is configured in the second ORACLE_INSTANCE.

40.1.2 Linux/UNIX Issues and Workarounds

This section describes issues related to Oracle Forms and Linux/UNIX. It includes the following topics:

- Section 40.1.2.1, "LD_PRELOAD Setting Required for Signal Chaining Facility"

- Section 40.1.2.2, "Check the Reports Engine Logs for FRM-41214"

- Section 40.1.2.3, "Changing User Permissions"

40.1.2.1 LD_PRELOAD Setting Required for Signal Chaining Facility

The LD_PRELOAD setting in default.env is required for the working of signal chaining facility in JVM version 1.5 and later. If you are creating or using other environment files, the setting in the environment file for LD_LIBRARY_PATH and LD_PRELOAD must be the same as in default.env.

40.1.2.2 Check the Reports Engine Logs for FRM-41214

If you encounter the Forms error FRM-41214:Unable to run report when trying to run Reports from a Forms session, check the Reports engine logs for more details on the error.

40.1.2.3 Changing User Permissions

The 11g installation sets the permissions of the files so that only the user who installed 11g can run the executables. For more information, refer to Installing as a Non-Default User on Unix Operating Systems in Oracle Fusion Middleware Forms and Reports System Requirements and Specifications guide.

40.2 Configuration Issues and Workarounds

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

- Section 40.2.1, "Non-Internet Explorer Browser Proxy Settings when Using One-Button-Run"

- Section 40.2.2, "WebUtil Client Files Allow Configuration of Destination Directory"

- Section 40.2.3, "webutil.properties Files Renamed for Different Libraries"

- Section 40.2.4, "Forms does not Work with JDK 1.6.0_12 on Client with WinRunner"

- Section 40.2.5, "JavaScript Communication Does not Work in IE for Framed HTML File"

- Section 40.2.6, "JavaScript Events Calling Forms Applications in a Safari 5 Browser Do not Work"

40.2.1 Non-Internet Explorer Browser Proxy Settings when Using One-Button-Run

If you encounter a FORBIDDEN error when using One-Button-Run with any of the supported browsers other than Internet Explorer, verify if 127.0.0.1 (localhost) is in the proxy settings for your browser. If 127.0.0.1 is not in the exceptions list, then add it. This ensures that the browser will bypass the proxy server.

40.2.2 WebUtil Client Files Allow Configuration of Destination Directory

WebUtil downloads install.syslib libraries into the bin directory of the JRE or JVM on Windows and into the lib directory of JRE on Linux. This location can be specified in the parameter install.syslib.location.client.<OS> = <Path on client machine> (where <Path on client machine> represents the path to the location where libraries used on the client by WebUtil are stored and is either absolute or relative to client user home) in webutil.cfg.

40.2.3 webutil.properties Files Renamed for Different Libraries

When install.syslib libraries are downloaded, WebUtil creates the webutil.properties file which is located in the client user home. Different webutil.properties files are maintained on client side to allow different servers to download and manage their libraries on client. The files are named webutil.<HOST>.<CONFIG>.properties on the client, where HOST is the server computer name and CONFIG is the name of configuration section in formsweb.cfg.

40.2.4 Forms does not Work with JDK 1.6.0_12 on Client with WinRunner

Forms does not run when using JDK 1.6.0_12 and later versions on a client that also has WinRunner installed.

As a workaround, rename the two environment variables _JAVA_OPTIONS and JAVA_TOOLS_OPTIONS. For example, rename them to test_JAVA_OPTIONS and test_JAVA_TOOLS_OPTIONS. This will disable WinRunner but allows Forms to run.

40.2.5 JavaScript Communication Does not Work in IE for Framed HTML File

JavaScript communication does not work in framed HTML file that is opened in Internet Explorer 7, or in Internet Explorer 8 with file:// protocol.

As a workaround, use the IP address instead of the machine name in the URL for the frame. For example in testform.htm, change:

<frame noresize="noresize"
src="http://testform.us.example.com:8888/forms/java/js2frm1.html" name="fr2"
frameborder="0">
<frame noresize="noresize"
src="http://testform.us.example.com:8888/forms/frmservlet?play=&record=forms&
form=js2frm1&userid=scott/tiger@adt10220" name="fr1" frameborder="0">

to

<frame noresize="noresize"
src="http://<IP address>:8888/forms/java/js2frm1.html" name="fr2"
frameborder="0">
<frame noresize="noresize"
src="http://<IP address>:8888/forms/frmservlet?play=&record=forms&form=js2fr
m1&userid=scott/tiger@adt10220" name="fr1" frameborder="0">

40.2.6 JavaScript Events Calling Forms Applications in a Safari 5 Browser Do not Work

When using JavaScript integration with a Forms application in a Safari 5 browser on Windows, the communication from Forms to JavaScript running in the browser works; however, the calls to the applet from JavaScript do not work.

As a workaround, perform the following:

1. Ensure you are using base.htm.

2. In base.htm, delete the <NOSCRIPT></NOSCRIPT> tags that are wrapping the <APPLET> tag.

40.3 Documentation Errata

This section describes documentation errata. It includes the following topics:

- Section 40.3.1, "Passing userid in Secure Mode"

- Section 40.3.2, "JDAPI Programming Example"

- Section 40.3.3, "Changes and workarounds affecting the number of characters that can be typed into an item"

40.3.1 Passing userid in Secure Mode

The following information on passing userid in secure mode must be added to Oracle Forms Builder online help.

Passing userid as an argument when using the Forms compiler (frmcmp or frmcmp_batch) may lead to security risks. In addition to the interactive dialog mode already available, the compiler can now accept the connect string via standard input. To pass the userid in a secure mode, perform the following:

1. Set the environment variable FORMS_STDIN_PASSWORD to 1.

2. Run the compiler without any connect string. Enter the connect string after the compiler has started.

3. Run the compiler using redirection to pass the password to the compiler. (This is especially useful in compiling several Forms in a script.) For example:

#!/bin/sh
echo "Enter userid"
read -s myuserid
for i in 'ls *.fmb'
do
echo Compiling Form $i ....
frmcmp_batch.sh batch=yes module=$i module_type=form compile_all=yes <<<
"$myuserid"
done

Note that this script is a sample that tries to protect the password, but on some platforms and configurations it may still lead to security risks.

40.3.2 JDAPI Programming Example

The JDAPI Programming Example in the Forms Developer Online Help must be updated to the following code:

import java.io.File;
import java.io.PrintWriter;
import java.io.FileWriter;
import java.text.MessageFormat;

import oracle.forms.jdapi.*;

/**
* Dumps passed forms JdapiObjects to an output stream as text.
*
* Set command line options for more output, else only the
* basic form tree structure will be dumped.
*
* See printUsage for command line options.
*/
public class FormDumper
{
/**
* Need this to parse the command line options
*
* The string represents valid command options as detailed in the
* Getopt class
*/

boolean m_dumpAllProps = false;
boolean m_dumpBoolProps = false;
boolean m_dumpNumProps = false;
boolean m_dumpTextProps = false;
boolean m_dumpPropNames = false;
String m_dumpPath = null;
/**
* Output stream, default to STDOUT */
private PrintWriter m_out = new PrintWriter(System.out, true);

/**
* Use this to indent children
*/
private String m_indentation = "";

/**
* Constructor
*/
public FormDumper()
{

}

/**
* Special constructor that does not take command line arguments.
*
* @param out The output writer where to send dump information.
*/
public FormDumper(PrintWriter out)
{
m_out = out;
m_dumpAllProps = true;
m_dumpBoolProps = true;
m_dumpNumProps = true;
m_dumpTextProps = true;
m_dumpPropNames = true;
}

/**
* Set the dump path.
*
* @param path The file where the dumper must send the information
*/
public void setDumpPath(String path)
{
m_dumpPath = path;
}

/**
* Indirect output
*/
public void println(String s)
{
m_out.println(s);
}

/**
* Dump a form to the output stream
*/
public void dumpForm(String filename)
throws Exception
{
FormModule fmb = FormModule.open(filename);
System.out.println("Dumping module " + fmb.getName());

if (m_dumpPath != null)
{
// use this form's FILE name to name the dump file
String thisFormName = new File(filename).getName();
thisFormName = thisFormName.substring(0, (thisFormName.length()-4));
StringBuffer dmpFilename = new StringBuffer();
dmpFilename.append(m_dumpPath);

if (!dmpFilename.toString().endsWith("/"))
{
dmpFilename.append("/");
}
dmpFilename.append(thisFormName);

m_out = new PrintWriter(new FileWriter(dmpFilename.toString()), true);
}

// Call the actual 'dump' method
dump(fmb);

// Dump the coordinate system used by the module
m_indentation = " ";
dump(new Coordinate(fmb));
m_indentation = "";
println("Dumped " + fmb.getName());

// Close the module
fmb.destroy();
}

/**
* Recursively dump a forms JdapiObject and its children to the output stream
*/
protected void dump(JdapiObject jo)
{
String className = jo.getClassName();

// print out a context line for the JdapiObject
// If it is a coordinate system, it does not have a name

if(className.equals("Coordinate"))
{
println(m_indentation + "Coordinate System ");
}
else
{
println(m_indentation + className + " " + jo.getName());
}

// Property classes need special treatment
if(className.equals("PropertyClass"))
{
dumpPropertyClass((PropertyClass)jo);
}
else // Generically dump the required property types only
{
if (m_dumpTextProps)
{
dumpTextProps(jo);
}
if (m_dumpBoolProps)
{
dumpBoolProps(jo);
}

if (m_dumpNumProps)
{
dumpNumProps(jo);
}
// Additionally, dump any Item list elements
if(className.equals("Item"))
{
dumpListElements((Item)jo);
}
}

// use Form's metadata to get a list of all the child JdapiObjects this
JdapiObject can have
JdapiMetaObject meta = JdapiMetadata.getJdapiMetaObject(jo.getClass());
JdapiIterator props = meta.getChildObjectMetaProperties();
JdapiMetaProperty prop = null;
JdapiIterator iter = null;
JdapiObject child = null;

// loop through every possible kind of child JdapiObject this JdapiObject
//can have
while(props.hasNext())
{
prop = (JdapiMetaProperty)props.next();
// only bother if we can access these JdapiObjects
if(!prop.allowGet())
{
continue;
}

// get the actual values for the current child JdapiObject type,
// e.g. get the Items on a Block
iter = jo.getChildObjectProperty(prop.getPropertyId());

// null is returned if there are no property values
if(iter != null)
{
// loop over every child value
while(iter.hasNext())
{
child = (JdapiObject)iter.next();
// recursively navigate to it
m_indentation += " ";
dump(child);
if(m_indentation.length()>2)
m_indentation = m_indentation.substring(0, m_indentation.length()-2)
;
}
}
}
}
/**
* Dump list elements
*
* The JdapiObject is an item; if it is a list item,
* dump the list elements.
*
* @param item
*/
private void dumpListElements(Item item)
{
if( item.getItemType() == JdapiTypes.ITTY_LS_CTID)
{
if (m_dumpPropNames)
{
println(m_indentation + "dumping list elements");
}
for(int i = 1; i <= item.getListElementCount(); i++)
{
String label = item.getElementLabel(i);
String value = item.getElementValue(i);
println( m_indentation + " " + i + ": '" + label + "' '" + value + "'");
}
}
}
/**
* Dump the property class properties
*/
private void dumpPropertyClass(PropertyClass pc)
{
String propertyVal = null;

// test for every single possible property
// this is a bit hacky :)
for(int propertyId = 1; propertyId < JdapiTypes.MAXIMUM_PTID; ++propertyId)
{
if(!pc.hasProperty(propertyId))
{
continue; // this property is not in the set
}
if(pc.hasDefaultedProperty(propertyId) && !m_dumpAllProps)
{
continue;
}
Class pt = JdapiMetaProperty.getPropertyType(propertyId);
if(pt == Boolean.class)
{
if(m_dumpBoolProps)
{
propertyVal = String.valueOf(pc.getBooleanProperty(propertyId));
}
}
else if(pt == Integer.class)
{
if(m_dumpNumProps)
{
propertyVal = String.valueOf(pc.getIntegerProperty(propertyId));
}
}
else if(pt == String.class)
{
if(m_dumpTextProps)
{
propertyVal = pc.getStringProperty(propertyId);
}
}
if(null != propertyVal)
{
if (m_dumpPropNames)
{
println(m_indentation + " " + JdapiMetaProperty.getPro
pertyName(propertyId) + " " +
propertyVal);
}
else
{
println(m_indentation + propertyVal);
}
propertyVal = null;
}
} // End loop over every property
}
/**
* Dump the source JdapiObject text properties
*/
private void dumpTextProps(JdapiObject jo)
{
JdapiMetaObject meta = JdapiMetadata.getJdapiMetaObject(jo.getClass());
JdapiIterator props = meta.getStringMetaProperties();
// for each text property
while(props.hasNext())
{
JdapiMetaProperty prop = (JdapiMetaProperty) props.next();
int propertyId = prop.getPropertyId();
String propertyVal = null;
try
{
propertyVal = jo.getStringProperty(propertyId);
}
catch(Exception e)
{
println(m_indentation + "Could_not_get_property " +
JdapiMetaProperty.getPropertyName(propertyId));
continue;
}
if ( jo.hasProperty(propertyId)
&& (m_dumpAllProps || !(jo.hasDefaultedProperty(propertyId)) ) )
{
if(m_dumpPropNames)
{
println( m_indentation + " " + JdapiMetaProperty.
getPropertyName(propertyId) + " " +
propertyVal);
}
else
{
println(m_indentation + propertyVal);
}
}
}
}
/**
* Dump the source JdapiObject boolean properties
*/
private void dumpBoolProps(JdapiObject jo)
{
JdapiMetaObject meta = JdapiMetadata.getJdapiMetaObject(jo.getClass());
JdapiIterator props = meta.getBooleanMetaProperties();
// for each boolean property
while(props.hasNext())
{
JdapiMetaProperty prop = (JdapiMetaProperty) props.next();
int propertyId = prop.getPropertyId();
boolean propertyVal = false;
try
{
propertyVal = jo.getBooleanProperty(propertyId);
}
catch(Exception e)
{
println(m_indentation + "Could_not_get_property " +
JdapiMetaProperty.getPropertyName(propertyId));
continue;
}
if ( jo.hasProperty(propertyId)
&& (m_dumpAllProps ) )
{
if(m_dumpPropNames)
{
println(m_indentation + " " + JdapiMetaProperty.
getPropertyName(propertyId) + " " +
propertyVal);
}
else
{
println(m_indentation + propertyVal);
}
}
}
}
/**
* Dump the source JdapiObject numeric properties
*/
private void dumpNumProps(JdapiObject jo)
{
JdapiMetaObject meta = JdapiMetadata.getJdapiMetaObject(jo.getClass());
JdapiIterator props = meta.getIntegerMetaProperties();
// for each numeric property
while(props.hasNext())
{
JdapiMetaProperty prop = (JdapiMetaProperty) props.next();
int propertyId = prop.getPropertyId();
int propertyVal = 0;
try
{
propertyVal = jo.getIntegerProperty(propertyId);
}
catch(Exception e)
{
println(m_indentation + "Could_not_get_property " +
JdapiMetaProperty.getPropertyName(propertyId));
continue;
}
if ( jo.hasProperty(propertyId)
&& (m_dumpAllProps || !(jo.hasDefaultedProperty(propertyId)) ) )
{
if (m_dumpPropNames)
{
println(m_indentation + " " + JdapiMetaProperty.getPropertyName(pr
opertyId) + " " +
propertyVal);
}
else
{
println(m_indentation + propertyVal);
}
}
}
}
/**
* Output usage info to STDOUT
*/
public void printUsage()
{
System.out.println("");
System.out.println("Jdapi Form Dumper Utility");
System.out.println("Valid arguments:");
System.out.println("-a : dump all properties, not just overridden ones");
System.out.println("-b : dump boolean properties");
System.out.println("-n : dump numeric properties");
System.out.println("-t : dump text properties");
System.out.println("-p : dump property names, not just values");
System.out.println("-o : file path to output to");
}
/**
* Main method
*/
public static void main(String[] args)
throws Exception
{
FormDumper dmp = new FormDumper();
for (int i = 0; i < args.length; i++)
{
dmp.dumpForm(args[i]);
}
System.out.println("");
System.out.println("Dumps complete");
System.out.println("");
}
}

40.3.3 Changes and workarounds affecting the number of characters that can be typed into an item

The following information must be added to Oracle Forms Builder online help.

1. When a form is created using the Form builder (frmbld), the item property Query Length defaults to zero. When the form was compiled in releases prior to 11g, this value (zero) caused the Query Length to default to the value of the Maximum Length property. In Oracle Forms 11g, the Query Length defaults to two plus the value of the Maximum Length property. If the behavior of prior releases is desired, then you must set the environment variable FORMS_QUERY_LENGTH_DELTA to '0' when the form is compiled.

2. The DATE format masks determine the number of characters that can be typed into a text item or combo box. In general, this number is the maximum of the number of characters required for the "output" format mask and for any allowable "input" format mask. Refer to "About Format Elements for Dates" for information about how "input" and "output" format masks are selected for a combo box, or for a text item whose format mask is not set. Note that the FORMS_USER_DATE_FORMAT or FORMS_USER_DATETIME_FORMAT environment variable may specify multiple input format masks. Also note that for any input format mask that does not contain FX, alternate format masks are also allowable, as documented in "String-to-Date Conversion Rules" in section "Format Models" in the SQL Reference in the Oracle Forms Builder Online Help.
Note one exception to the rules spelled out above. The behavior described in "String-to-Date Conversion Rules" allow a fully spelled-out month to be entered in place of a numeric month (MM form mask element) or abbreviated month (MON form mask element). However, in this case, the number of characters that can be typed into a text item or combo box allows only enough room for an abbreviated month.

Prior to 11gR1, input DATE format masks were not taken into account. In 10gR2 (10.1.2), the number of characters the end user was allowed to type into a DATE item was determined solely from the output format mask. In Forms 6i (6.0.8), the Maximum Length property of the DATE item was also taken into account.

Workarounds

The changes in behavior documented above may affect users who have set the Auto-Skip property for a DATE item. The end user may now be allowed to type more characters into a specific DATE item, in which case auto-skip will not occur in cases where it did occur prior to 11gR1. To ensure that auto-skip occurs, add the FX modifier to the format mask that will be used for the item, for example, FXYYYY/MM/DD. If there is no item-specific format mask (that is, no format mask is set either in the item's property palette or programmatically), then the item's format mask will be derived from environment variables. The FORMS_USER_DATE_FORMAT and FORMS_USER_DATETIME_FORMAT environment variables are recommended as they take precedence over any NLS environment variables that might affect DATE format masks.

Note that specifying the FX modifier will disallow the alternate format masks that are documented in "String-to-Date Conversion Rules" in section "Format Models" of the SQL Reference. Also note that the FORMS_USER_DATE_FORMAT and FORMS_USER_DATETIME_FORMAT environment variables can explicitly specify alternate format masks, separated by vertical bars, for example, FXDD-MON-YYYY|FXMON-DD-YYYY. [If the FORMS_OUTPUT_DATE_FORMAT and FORMS_OUTPUT_DATETIME_FORMAT environment variables are not set, the output format masks are derived from the first format mask specified in each of the FORMS_USER_DATE_FORMAT and FORMS_USER_DATETIME_FORMAT environment variables.]

41 Oracle Reports

This chapter describes issues associated with Oracle Reports. It includes the following topics:

Note:

This product is not supported on Oracle Solaris on x86-64 (64-Bit).

- Section 41.1, "General Issues and Workarounds"

41.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topic:

- Section 41.1.1, "Mapping Users and Roles to Reports Application"

- Section 41.1.2, "Reports Weblayout not Supported on SUSE 10"

41.1.1 Mapping Users and Roles to Reports Application

In Oracle Fusion Middleware 11g Release 1 (11.1.1.3.0) installations, roles and users are not added to the Reports application, by default. To run a report using JPS security, you must add roles and users to the Reports application.

For more information, see:

- "Managing Application Roles" in the Oracle Fusion Middleware Security Guide

- "Managing Users and Security Policies" in the Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services manual

41.1.2 Reports Weblayout not Supported on SUSE 10

As Mozilla Firefox is not supported on SUSE 10, Reports WebLayout is not certified with SUSE 10.

42 Oracle Portal

This chapter describes issues associated with Oracle Portal. It includes the following topics:

Note:

This product is not supported on Oracle Solaris on x86-64 (64-Bit).

- Section 42.1, "Before You Begin"

- Section 42.2, "General Issues and Workarounds"

- Section 42.3, "Upgrade Issues and Workarounds"

- Section 42.4, "Interoperability Issues and Workarounds"

- Section 42.5, "User Interface Issue and Workaround"

- Section 42.6, "Export and Import Issues and Workarounds"

- Section 42.7, "Portlet and Provider Issues and Workarounds"

- Section 42.8, "PDK Issue and Workaround"

- Section 42.9, "Globalization Support Issues and Workarounds"

42.1 Before You Begin

In addition to the known problems and workarounds described in this document, Oracle recommends that you read the My Oracle Support note 834615.1 - Oracle Fusion Middleware 11g Portal (11.1.1) Support Status and Alerts. This article contains known issues that were discovered after the release of Oracle Portal 11g Release 1 (11.1.1).

42.2 General Issues and Workarounds

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

- Section 42.2.1, "Editing a Database Link Requires Password"

- Section 42.2.2, "Moving Content When Approval Is Enabled Does Not Require Approval"

- Section 42.2.3, "Firefox and Safari Browsers Do Not Display Tooltips on Oracle Portal Screens"

- Section 42.2.4, "Non-ASCII URLs Cannot be Decoded in Some Scenarios"

- Section 42.2.5, "Adding a Zip File with a Non-ASCII Character Name"

- Section 42.2.6, "Manual Changes to Oracle Portal Default Schema Objects"

- Section 42.2.7, "Error When Creating RCU Portal Schema"

- Section 42.2.8, "Portal Throws Discoverer Provider is Busy Error Message"

- Section 42.2.9, "Error When Adding Sample RSS Portlets to a Page"

- Section 42.2.10, "Internal Error when Using Portal Search With Oracle Text Enabled to Search for Pages"

- Section 42.2.11, "Issue After Creating a Oracle Portal Schema"

- Section 42.2.12, "Updating Database Tables"

42.2.1 Editing a Database Link Requires Password

If the database where the portal schema is installed is version 10.2 or later, then users must re-enter the remote user's password when they rename or edit a database link from the Portal Navigator's Database Objects tab. This is applicable only for those database links that are created with the Specific User option.

42.2.2 Moving Content When Approval Is Enabled Does Not Require Approval

Moving content between pages or between regions of the same page does not trigger approvals. For example, when a target page is configured with an approval process and a contributor moves content from a source page to the target page, the moved content does not trigger the approval process on the target page, even when approval is required for all users.

42.2.3 Firefox and Safari Browsers Do Not Display Tooltips on Oracle Portal Screens

Firefox and Safari browsers do not support the display of tooltip text, which is set using the ALT attribute for image descriptions.

As a workaround, you can download and install browser-specific add-ons, such as Popup ALT Attribute for Firefox (see https://addons.mozilla.org/en-US/firefox/addon/1933).

42.2.4 Non-ASCII URLs Cannot be Decoded in Some Scenarios

If the JVM default character encoding is set to ISO8859-1, the Portal repository database character set must match with the JVM default character encoding. If this condition is not satisfied, non-ASCII URLs may become inaccessible.

42.2.5 Adding a Zip File with a Non-ASCII Character Name

If you are adding a zip file to a page under a pagegroup using non-ascii character name, and when you unzip the file, it throws the following exception:

IllegalArgumentException: null and unzip will be failed.

To avoid this exception, you must use ascii character as the zip file name.

42.2.6 Manual Changes to Oracle Portal Default Schema Objects

Any manual changes to Oracle Portal default objects, such as tables, views, packages, or indexes are not supported. Such changes may render Oracle Portal unusable. Note that the internal structure of Portal objects can change between versions.

For more information, see the 403179.1 My Oracle Support note.

42.2.7 Error When Creating RCU Portal Schema

If RCU portal schema creation fails with the error message ORA-24246: empty access control list (ACL) not allowed, do the following:

1. Connect to the database as a SYS user.

2. At the SQL prompt, run the following command:

BEGIN
DBMS_NETWORK_ACL_ADMIN.drop_acl (
acl         => '/sys/acls/portal-permissions.xml');
COMMIT;
END;
/

42.2.8 Portal Throws Discoverer Provider is Busy Error Message

Portal throws an error message The Discoverer Provider is busy, please try again later. This occurs when you perform the following steps:

1. Click Edit Portlet defaults

2. Click Update for Database section

3. Change selection for User not logged sub-section

4. Click Next to fetch worksheet list

Workaround

To workaround this issue perform the following steps:

1. Add stall timeout to $DOMAIN_HOME/servers/WLS_PORTAL/
stage/portal/portal/configuration/appConfig.xml

For example: <stall>200</stall>

2. Restart WebLogic Server Portal

42.2.9 Error When Adding Sample RSS Portlets to a Page

When you try to add the sample Scrolling RSS Portlet or the sample Simple RSS portlet to a Portal page, an error message is displayed.

The error occurs because the RSS used by the sample portlets are no longer available.

Currently, there is no workaround for this problem.

42.2.10 Internal Error when Using Portal Search With Oracle Text Enabled to Search for Pages

If you have Oracle Text enabled, the following internal server error may occur when you are searching for Pages:

Internal error (WWC-00006)
An unexpected error has occurred (WWS-32100)
Unknown Exception (WWC-45131)
User-Defined Exception (WWV-11230)
Unexpected error - ORA-00600: internal error code, arguments:
[qkeIsExprReferenced1], [], [], [], [], [], [], [] (WWC-35000)

If this error occurs, you must download and install the patch ID 7041059 from https://support.oracle.com/

42.2.11 Issue After Creating a Oracle Portal Schema

After creating the Oracle Portal schema, you may get the following error:

checkinstall2=Add ACL for network packages if DB is 11.1 or higher...
old   4:     schema varchar2(2000)   := upper('&&1');
new   4:     schema varchar2(2000)   := upper('CLASSIC17_PORTAL');
Package DBMS_NETWORK_ACL_ADMIN exists, assign ACL if not already assigned
Removing dangling principals,if any from the ACL privilege list ...
ERROR: when assigning network ACL
declare
*
ERROR at line 1:
ORA-24246: empty access control list (ACL) not allowed
ORA-06512: at "SYS.DBMS_NETWORK_ACL_ADMIN", line 421
ORA-06512: at line 1
ORA-01403: no data found
ORA-06512: at line 83

To fix this error, you must create a schema with a different prefix, and then run the following command to clean out the dangling ACL:

begin
DBMS_NETWORK_ACL_ADMIN.DELETE_PRIVILEGE('portal-permissions.xml','PREFIX_PORTA
L');
end;

PREFIX_PORTAL is replaced with the schema prefix used in the schema that was dropped.

You must run the Repository Creation Utility to install the new schema.

42.2.12 Updating Database Tables

In Oracle Portal database object, if you insert one row data which has MB character and then update the row, the update will not work. You must manually update the table and view in the database to avoid this issue and update the table and view successfully.

42.2.13 Apply Patch to Address Performance Issue

After install, you must apply the patch referred to in KM Note 1087226.1. This patch contains a fix to address a serious performance issue that can occur while opening or saving HTML documents using the rich text editor. As this task is performed frequently, it's important to apply this patch to avoid a significant loss in productivity.

42.3 Upgrade Issues and Workarounds

This section describes the upgrade issues and workarounds. It discusses the following topics:

- Section 42.3.1, "Upgrading Portal 10g SSL Environment to Oracle Portal 11g Release 1 (11.1.1)"

42.3.1 Upgrading Portal 10g SSL Environment to Oracle Portal 11g Release 1 (11.1.1)

When you upgrade SSL environment from Oracle Portal 10g to Oracle Portal 11g Release 1 (11.1.1), you will not able to login to Oracle Portal, when you have SSO and Portal Midtier on the same hostname. Internet Explorer has a problem redirecting back and forth on the same hostname between two different ports under SSL mode. As a workaround, you can use Mozilla Firefox.

42.4 Interoperability Issues and Workarounds

This section describes the interoperability issues and workarounds. It discusses the following topics:

- Section 42.4.1, "Interoperability Between Oracle Portal 11g Release 1 (11.1.1) with Secured Enterprise Search (SES) 10.1.8.3"

- Section 42.4.2, "Interoperability Between Oracle Portal 11g Release 1 (11.1.1) with Secured Enterprise Search (SES) 10.1.8.4"

- Section 42.4.3, "Creating Webproviders in the Oracle Portal 11g Release 1 (11.1.1) Midtier Interoperability with Oracle Portal Repository 10g Release"

42.4.1 Interoperability Between Oracle Portal 11g Release 1 (11.1.1) with Secured Enterprise Search (SES) 10.1.8.3

For this interoperability scenario to work, you must download and install the patch ID 7685124 from https://support.oracle.com/and see note 816929.1 in My Oracle Support.

42.4.2 Interoperability Between Oracle Portal 11g Release 1 (11.1.1) with Secured Enterprise Search (SES) 10.1.8.4

For this interoperability scenario to work, you must download and install the patch ID 7971335 from https://support.oracle.com/

42.4.3 Creating Webproviders in the Oracle Portal 11g Release 1 (11.1.1) Midtier Interoperability with Oracle Portal Repository 10g Release

In Portal 11g 1 (11.1.1), you cannot create webproviders when you are using 11g midtier with 10g portal repository.

42.5 User Interface Issue and Workaround

This section describes issue and workaround related to the Oracle Portal user interface. It includes the following topic:

Cannot Set Privileges Using List View on Pages Inheriting Privileges from Parent or Template

If you use the List View to set access privileges for one or more pages, then privileges will not be set on pages inheriting privileges from a parent page or template. As a workaround, change the privileges for such pages individually, that is, using the Access tab for the subpage.

42.6 Export and Import Issues and Workarounds

This section describes issues and workarounds related to export and import in Oracle Portal. This section includes the following topics:

- Section 42.6.1, "Export and Import Does Not Support Reports Server Components"

- Section 42.6.2, "Saving the Transport Set"

- Section 42.6.3, "Error when importing a page group"

42.6.1 Export and Import Does Not Support Reports Server Components

If you include Reports Server Components within a transport set, then they are deleted on export and import. In addition, do not configure the Oracle Reports item type in any page groups intended for export and import. If you do, then the following error is displayed when you try to configure item types in the imported page group (by clicking the Content Type and Classifications Edit link on the Configure tab for the page group):

Internal error (WWC-00006)
Unexpected error - User-Defined Exception (WWC-35000)
Unexpected error - ORA-01403: no data found (WWC-35000)

42.6.2 Saving the Transport Set

After you complete the transport set transfer, click Display Manifest to display the transport set manifest. Ensure that you save the transport set before performing the precheck of the transferred data. This step takes the manifest changes.

42.6.3 Error when importing a page group

Importing a page group may fail with the following error message:

[Error:  (WWU-80338)] context = Schema Validation user =
ORCLADMIN There were some inconsistencies found and hence import process is aborted.Check the debug log for further details.Fix those inconsistencies, by running schema validation in cleanup mode to proceed

This problem might occur after deleting a page group containing shared portlets. You must run SVU in cleanup mode to ensure a smooth export or import process.

42.7 Portlet and Provider Issues and Workarounds

This section describes issues and workarounds related to OmniPortlet, Web Clipping, Simple Parameter Form, Page portlet, and WSRP providers. This section includes the following topics:

- Section 42.7.1, "Issue When Accessing Page Portlet Using Federated Portal Adapter"

- Section 42.7.2, "Error in JPS Portlet After Redeployment"

- Section 42.7.3, "SSL Support for Oracle Portal Integration Solutions (Microsoft Exchange)"

42.7.1 Issue When Accessing Page Portlet Using Federated Portal Adapter

The Federated Portal Adapter enables you to display remote portal pages in your portal. However, if both portal instances do not share the same Oracle Single Sign-On server, then you cannot display a remote portal page as a page portlet, even if the remote page is public. A message is displayed instead of the page portlet, as shown in the following example:

Portlet 257,75057 responded with content-type text/plain when the client was requesting content-type text/html

As a workaround, configure both portal instances to use the same Oracle Single Sign-On server.

42.7.2 Error in JPS Portlet After Redeployment

When you redeploy your portlets to the portlet container, all existing sessions between the producer and all of its consumers are lost. If a consumer tries to reuse an existing producer session, then it may receive an error message the first time it tries to contact the producer after redeployment, as shown in the following example:

Error: Could not get markup. The cookie or session is invalid or there is a runtime exception.

To reestablish the producer's session, refresh the portal page. You will not see this error message if you are reaccessing the portlet from a new browser session because it automatically establishes a new producer session.

42.7.3 SSL Support for Oracle Portal Integration Solutions (Microsoft Exchange)

SSL support is not available for Oracle Portal Integration Solutions (Microsoft Exchange). This is a known limitation.

42.8 PDK Issue and Workaround

Oracle Portal Developer Kit (PDK) version 10.1.2 is included with the Portal and Wireless installation. Release notes for the PDK-Java and PDK-PL/SQL can be found at the following middle-tier ORACLE_HOME locations:

- PDK-Java: ORACLE_HOME/portal/pdkjava/v2/pdkjava.v2.releasenotes.html

- PDK-PL/SQL: ORACLE_HOME/portal/pdkjava/v2/pdkplsql.release.notes.html

Latest Version of Oracle PDK

New versions of the Oracle PDK are released periodically providing new features, new APIs, and additional documentation. To take advantage of all the latest features, download the latest PDK from the PDK downloads page on the Oracle Technology Network (OTN) at http://www.oracle.com/technology/products/ias/portal/pdk.html.

Release notes for the latest Oracle PDK version are available on Oracle Portal on OTN and also in these PDK download locations:

- pdk\plsql\pdkplsql.release.notes.html

- pdk\jpdk\v2\pdkjava.v2.release.notes.html

42.9 Globalization Support Issues and Workarounds

This section describes issues and workarounds related to Globalization Support in Oracle Portal. It includes the following topics:

- Section 42.9.1, "Text Entry Always Right to Left in BiDi Languages"

- Section 42.9.2, "Non-ASCII Character Limitations in Oracle Portal"

- Section 42.9.3, "Multibyte Characters in Log Files"

42.9.1 Text Entry Always Right to Left in BiDi Languages

The direction of all text areas and fields is right to left (RTL). However, you may want some text areas to work left to right (LTR). Internet Explorer users can change this by pressing the left hand side Ctrl and Shift keys.

42.9.2 Non-ASCII Character Limitations in Oracle Portal

When you copy and paste an item URL containing non-ASCII characters from one browser Location or Address field into another, you may not be able to access the item if your login credentials have not been authenticated through OracleAS Single Sign-On.

As a workaround, log in to the portal before you access the item and copy the item URL.

42.9.3 Multibyte Characters in Log Files

In some scenarios, multibyte characters in log files may get corrupted.

For example, when the WLS_PORTAL managed server is started from the Oracle WebLogic Server Administration Console, multibyte characters, such as username, password, and is starting, may get corrupted.

Workarounds:

- Change -Dfile.encoding=iso-8859-1 to -Dfile.encoding=utf8 in the WLS_PORTAL start-up parameter through the Oracle WebLogic Server Administration Console.

- Change -Dfile.encoding=iso-8859-1 to -Dfile.encoding=utf8 in the setDomainEnv.sh file (Located at MW_HOME/user_projects/domains/DomainName/bin).

For more information, see note 403179.1.

Part XII

Oracle Data Integrator

Part XII contains the following chapters:

- Chapter 43, "Oracle Data Integrator"

43 Oracle Data Integrator

This chapter describes issues associated with Oracle Data Integrator. It includes the following topics:

- Section 43.1, "Configuration Issues and Workarounds"

- Section 43.2, "Design-Time Environment Issues and Workarounds"

- Section 43.3, "Oracle Data Integrator Console Issues and Workarounds"

- Section 43.4, "Technologies and Knowledge Modules Issues and Workarounds"

- Section 43.5, "Oracle Data Profiling and Oracle Data Quality Issues and Workarounds"

43.1 Configuration Issues and Workarounds

This section describes the following issues and their workarounds:

- Section 43.1.1, "Generated Templates Including a Datasource With an Oracle RAC URL Fail to Deploy"

- Section 43.1.2, "Generated Templates Including Datasources Fail to Deploy"

- Section 43.1.3, "Setting Test Queries on WLS Datasources"

- Section 43.1.4, "Oracle Web Service Manager (OWSM) Integration with ODI Web Services Not Available on IBM WebSphere Platform"

43.1.1 Generated Templates Including a Datasource With an Oracle RAC URL Fail to Deploy

Oracle WebLogic Configuration Wizard does not support Oracle RAC URLs for datasources. When a datasource is included in a Java EE Agent template that has been generated using Oracle Data Integrator Studio, this template fails to deploy, and raises the following exception is raised:

com.oracle.cie.wizard.WizardController - Uncaught Exception
java.lang.NullPointerException
atcom.oracle.cie.domain.jdbc.DatasourceXBeanAspectHelper.decomposeURL

As a workaround, do not include this datasource definition in the generated template and deploy the datasource from Oracle Data Integrator Studio.

43.1.2 Generated Templates Including Datasources Fail to Deploy

As the Oracle WebLogic Configuration Wizard uses specific code for parsing the URL and exposing its parameters in a user friendly format, it only supports a predefined set of JDBC URLs. If a JavaEE Agent template that has been generated using Oracle Data Integrator Studio contains a datasource with a URL or driver not included in this set, the Wizard fails to use this template with the following exception:

com.oracle.cie.wizard.WizardController - Uncaught Exception
java.lang.NullPointerException
atcom.oracle.cie.domain.jdbc.DatasourceXBeanAspectHelper.decomposeURL

As a workaround, do not include this datasource definition in the generated template, and deploy the datasource from Oracle Data Integrator Studio.

43.1.3 Setting Test Queries on WLS Datasources

The Clean Stale Sessions feature of the Agent relies on the stale or dead connections of the connection pool to be automatically cleaned up either through expiration or connection validations tests done by the connection pool implementation.

If the stale connections are not removed out by the connection pool, then the Clean Stale Sessions feature does not work even after the database has been restarted. None of the other requests of the agent will work after the database restart if the agent itself is not restarted.

In a WebLogic Server container, connections are validated every few seconds using a test query. It is recommended to verify and provide the table name used by the database to run the test query: select count(*) from <test_table_name>.

For Master Repositories and Work Repositories, datasources use SNP_LOC_REP and SNP_LOC_REPW as the test tables.

Alternatively, you can use the DUAL table for an Oracle repository.

43.1.4 Oracle Web Service Manager (OWSM) Integration with ODI Web Services Not Available on IBM WebSphere Platform

The ability to view policies attached to an ODI Web service on IBM WebSphere through Fusion Middleware Control is not supported in this release.

43.2 Design-Time Environment Issues and Workarounds

This section describes the following issues and their workarounds:

- Section 43.2.1, "For File Datastores, the View Data operation always looks for global context"

- Section 43.2.2, "Quick Edit Editor deletes incorrect Joins when sorted"

- Section 43.2.3, "Quick Edit Editor displays a Source as removed regardless of the Selection made in the Warning Dialog"

- Section 43.2.4, "Inconsistent Behavior when Refreshing Load Plans"

- Section 43.2.5, "User Parameters are not Taken into Account by the Runtime Agents"

- Section 43.2.6, "Incorrect Non-ASCII File Names in Zip Export Files"

- Section 43.2.7, "Non-ASCII Characters Incorrectly Converted to Underscore Characters"

43.2.1 For File Datastores, the View Data operation always looks for global context

Within ODI Studio, when viewing data from within a data store, there must be a global context defined for the datastore.

com.sunopsis.core.SnpsInexistantSchemaException: ODI-17523: There is no connection for this logical schema / context pair: lg1 / GLOBAL.

As a workaround, define a global context for the datastore.

43.2.2 Quick Edit Editor deletes incorrect Joins when sorted

Within ODI Studio Quick Edit, when deleting a join, the incorrect join may be deleted if a join is selected and then the list of joins is sorted.As a workaround sort the join list prior to deleting the join with Quick Edit.

43.2.3 Quick Edit Editor displays a Source as removed regardless of the Selection made in the Warning Dialog

Within ODI Studio Quick Edit, when deleting a source, the source will appear as removed even if "No" is selected from the warning before the deletion.

As a workaround, refresh ODI Studio and open Quick Edit, the source will still be available.

43.2.4 Inconsistent Behavior when Refreshing Load Plans

Within ODI Studio, when refreshing Load Plan to pick latest Scenario reference in the Load Plan, the latest scenario is determined by the Scenario Creation timestamp. During ODI agent execution, the latest scenario is determined by alphabetical ascending order of the Scenario Version string value.

43.2.5 User Parameters are not Taken into Account by the Runtime Agents

The runtime agents do not take into account the user parameter values specified in the userpref.xml file. The default values are always used instead.

There is no generic workaround at this time.

43.2.6 Incorrect Non-ASCII File Names in Zip Export Files

Non-ASCII file names are incorrectly generated in Zip export files. Non-ASCII characters in these file names are replaced with underscores. Setting the Never transform non ASCII characters to underscores user parameter to Yes has no effect. As a workaround, export the files in a folder and compress this folder.

43.2.7 Non-ASCII Characters Incorrectly Converted to Underscore Characters

Non-ASCII characters are handled incorrectly in the following situations, even if the Never transform non ASCII characters to underscores user parameter is set to Yes:

- Non-ASCII characters are replaced with underscores in the Alias field of a column when using the fixed file reverse-engineering wizard.

- Non-ASCII characters from the header line are replaced with underscores in column names when doing a delimited file reverse-engineering.

As a workaround, manually modify the column definitions after the reverse process.

43.3 Oracle Data Integrator Console Issues and Workarounds

This section describes the following issues and their workarounds:

- Section 43.3.1, "Oracle Data Integrator Console Page Task Flow Resets When Another Tab Is Closed."

- Section 43.3.2, "Enterprise Manager Logout Does Not Propagate to Oracle Data Integrator Console"

- Section 43.3.3, "Standalone Agent Target Does Not Show Current Status"

- Section 43.3.4, "Basic Configuration Cannot Be Done Through FMW Console"

- Section 43.3.5, "Error with Variable Handling in Sequences in ODI Studio"

43.3.1 Oracle Data Integrator Console Page Task Flow Resets When Another Tab Is Closed.

When the tab containing a page is closed in Oracle Data Integrator Console, all the tabs after this one reset their task flows (the navigation actions that were made). The pages in these tabs reset to the original object that was opened.

There is no workaround for this issue at this time.

43.3.2 Enterprise Manager Logout Does Not Propagate to Oracle Data Integrator Console

When Enterprise Manager Fusion Middleware Control (EM) is used in conjunction with Oracle Data Integrator Console with Single Sign-On (SSO) activated, a user logging out from SSO in Enterprise Manager might still be able to access Oracle Data Integrator Console pages from the same browser window by typing a direct URL.

This issue is caused by a cookie that is created by Oracle Data Integrator Console not being invalidated by the Enterprise Manager logout action.

As a workaround:

- Administrators should configure their Enterprise Manager and Oracle Data Integrator Console servers for access fronted by a gateway. The gateway automatically redirects the user that is not logged into SSO to the SSO Login page.

- If you're accessing Oracle Data Integrator Console or Enterprise Manager from a shared or public computer, close the session by logging out. For additional security, close the browser session.

43.3.3 Standalone Agent Target Does Not Show Current Status

On Oracle WebTier and OPMN deployed on IBM WebSphere, the status for the Standalone Agent target (managed through OPMN) on FMW Console does not update to indicate when the application is running or is shut down. The state "Status Pending" is displayed at all times.

43.3.4 Basic Configuration Cannot Be Done Through FMW Console

On Oracle WebTier and OPMN deployed on IMB WebSphere, the Basic Configuration dialog (select StandAloneAgent, right click and select ODI Console Administration) containing host and port information does not display and therefore cannot be used to make changes to these values.

43.3.5 Error with Variable Handling in Sequences in ODI Studio

Specific sequences do not handle variables correctly in WHERE clause. The initial save works, but after saving the second time, an error occurs.

43.4 Technologies and Knowledge Modules Issues and Workarounds

This section describes the following issues and their workarounds:

- Section 43.4.1, "For Microsoft Excel Target Datastores, column names must be in upper case"

- Section 43.4.2, "For File Datastores, reverse-engineering process cannot be canceled"

- Section 43.4.3, "SQL Keywords are not imported when importing a Technology in Duplication Mode"

- Section 43.4.4, "SQL Exception "Unknown Token" appears when using Complex File or XML as Staging Area"

- Section 43.4.5, "Adding Subscribers fails for Consistent Set JKMs when the Model Code Contains Non-ASCII Characters"

- Section 43.4.6, "IKM and LKM SQL Incremental Update (Row by Row) fail with Non-ASCII Characters"

- Section 43.4.7, "IKM SQL Incremental Update (Row by Row) Cannot Target Japanese Tables"

43.4.1 For Microsoft Excel Target Datastores, column names must be in upper case

When using Microsoft Excel as a target, column names must be in upper case.

[Microsoft][ODBC Excel Driver]COUNT field incorrect

As a workaround, rename column names within Microsoft Excel.

43.4.2 For File Datastores, reverse-engineering process cannot be canceled

Within ODI Studio, when reverse engineering new columns to an existing datastore, after reverse new columns are automatically saved when answering "No" to "<datastore> has been modified. Save changes?"

43.4.3 SQL Keywords are not imported when importing a Technology in Duplication Mode

Within ODI Studio, when importing a technology in duplication mode, the SQL Keywords are not imported.As as workaround, manually add the SQL Keywords to the technology properties.

43.4.4 SQL Exception "Unknown Token" appears when using Complex File or XML as Staging Area

When running interfaces and using a XML or Complex File schema as the staging area, the "Unknown Token" error appears. This error is caused by the updated HSQL version (2.0). This new version of HSQL requires that table names containing a dollar sign ($) are surrounded by quotes. Temporary tables (Loading, Integration, and so forth) that are created by the Knowledge Modules do not meet this requirement on Complex Files and HSQL technologies.

As a workaround, edit the Physical Schema definitions to remove the dollar sign ($) from all the Work Tables Prefixes. Existing scenarios must be regenerated with these new settings.

43.4.5 Adding Subscribers fails for Consistent Set JKMs when the Model Code Contains Non-ASCII Characters

When the Model code contains non-ASCII characters, adding subscribers does not work for Consistent Set Journalizing KMs. This applies to all Consistent Set JKMs. The Session completes successfully but no subscriber is added. Note that this issue does not occur when the Model code contains exclusively ascii characters.

There is no generic workaround at this time.

43.4.6 IKM and LKM SQL Incremental Update (Row by Row) fail with Non-ASCII Characters

When the source datastore contains non-ascii characters the interface using the IKM or LKM SQL Incremental Update (Row by Row) fails at the step Insert flow into I$ table with the following error message:

org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):  File "<string>", line 149, in <module>
UnicodeEncodeError: 'ascii' codec can't encode characters in position 6-7:
ordinal not in range(128)

There is no generic workaround at this time.

43.4.7 IKM SQL Incremental Update (Row by Row) Cannot Target Japanese Tables

IKM SQL Incremental Update (Row by Row) fails on task Flag rows for update if the target table name contains Japanese characters. In the generated code, the integration table name appears as "I$_??????" where "?" characters replaces a Japanese character.

As a workaround, replace this IKM with another IKM suitable for the technology. For example, 'IKM Oracle Incremental Update' for Oracle.

43.5 Oracle Data Profiling and Oracle Data Quality Issues and Workarounds

This section describes the following issues and their workarounds:

- Section 43.5.1, "ODIDQ fails to Create Loader Connection when Server is Installed on Linux 64 bits"

- Section 43.5.2, "Unable to Connect the Client to a Data Quality Server on UNIX"

- Section 43.5.3, "Menus Are in English When Starting the Client Using a .tss File."

43.5.1 ODIDQ fails to Create Loader Connection when Server is Installed on Linux 64 bits

When trying to create loader connections with ODQ installed on Linux 64 bits server, ODQ Client installed on Windows machine, and the Metabase Host set as the Linux Server, the loader connection is not created and no error message or warning is displayed.

As a workaround, download the patch 11775170 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 11775170.

4. Download the patch.

43.5.2 Unable to Connect the Client to a Data Quality Server on UNIX

When connecting from the Oracle Data Quality Client to a Data Quality Server installed on a UNIX machine the following error message may appear: "No support for client application "Admin" version 12.0.1".

To solve this issue re-install the metabase definitions using the following steps:

1. On the UNIX server go to the following directory:ODQ_HOME/oracledi/odp/Client/SvrSide

2. Run ./setup

3. At the prompt, enter the Metabase Installation location: ODQ_HOME/oracledq/metabase_server/

4. Enter the metabase admin user and password.

5. When the metabase definitions installation completes, restart the Scheduler service using the following command: ODQ_HOME/oracledq/metabase_server/metabase/bin/scheduler -restart

43.5.3 Menus Are in English When Starting the Client Using a .tss File.

When starting Oracle Data Quality Client by double-clicking on a saved .tss file, the menus appear in English independently of the client machine's locale.

As a workaround, open the client from the shortcut menu, then open the .tss file.

Part XIII

Oracle Business Intelligence

Part XIII contains the following chapters:

- Chapter 44, "Oracle Business Intelligence"

- Chapter 45, "Oracle Business Intelligence Applications and Data Warehouse Administration Console"

- Chapter 46, "Oracle Real-Time Decisions"

44 Oracle Business Intelligence

This chapter describes issues associated specifically with Oracle Business Intelligence, including issues related to installation, upgrade, analyses and dashboards, Oracle BI Mobile, Oracle BI Publisher, metadata repository development, system administration, integration and API, and localization.

See Also:

Added as per bug 14572081

Before you install Oracle Business Intelligence 11g Release 1 (11.1.1), review the following sections under "System Requirements for UNIX Operating Systems" in Oracle Fusion Middleware System Requirements and Specifications guide:

- For Oracle Solaris, refer to the "Supported Solaris Operating System Versions, Packages, and Patches", "Open File Limit", and "Applying Solaris Patches in Non-Global Zones" sections.

This chapter includes the following sections:

- Section 44.1, "Patch Requirements"

- Section 44.2, "Oracle Business Intelligence Issues and Workarounds Identified or Changed Since the Last Revision"

- Section 44.3, "Which Releases Are Covered by These Release Notes?"

- Section 44.4, "Oracle Business Intelligence General Issues and Workarounds"

- Section 44.5, "Oracle Business Intelligence Installation Issues and Workarounds"

- Section 44.6, "Oracle Business Intelligence Upgrade Issues and Workarounds"

- Section 44.7, "Oracle Business Intelligence Installation Guidelines for 64-Bit Platforms"

- Section 44.8, "Oracle Business Intelligence Analyses and Dashboards Issues and Workarounds"

- Section 44.9, "Oracle Business Intelligence Mobile Issues and Workarounds"

- Section 44.10, "Oracle Business Intelligence Mobile App Designer Issues and Workarounds"

- Section 44.11, "Oracle Business Intelligence Publisher Reporting and Publishing Issues and Workarounds"

- Section 44.12, "Oracle Business Intelligence Metadata Repository Development Issues and Workarounds"

- Section 44.13, "Oracle Business Intelligence System Administration Issues and Workarounds"

- Section 44.14, "Oracle Business Intelligence Integration and API Issues and Workarounds"

- Section 44.15, "Oracle Business Intelligence Localization Issues and Workarounds"

- Section 44.16, "Oracle Business Intelligence Documentation Errata"

Depending on your Oracle Fusion Middleware implementation, some information in other chapters of this document might also be relevant, including:

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

- Chapter 3, "Upgrade"

- Chapter 4, "Oracle Fusion Middleware Administration"

- Chapter 5, "Oracle Enterprise Manager Fusion Middleware Control"

- Chapter 6, "Oracle Fusion Middleware High Availability and Enterprise Deployment"

Sometimes, there can be a delay before revised Release Notes are published on the Oracle Technology Network (OTN). To get access to Oracle Business Intelligence Release Note items as soon as they are available, go to the Oracle BI Documentation wiki at https://wikis.oracle.com/display/oraclebidocumentation/Home

44.1 Patch Requirements

This section describes patch requirements for Oracle Business Intelligence. It includes the following topic:

- Section 44.1.1, "Obtaining Patches from My Oracle Support"

44.1.1 Obtaining Patches from My Oracle Support

Periodically, Oracle Business Intelligence patches are released. Some patches are mandatory; other patches are optional.

To see the patches that are available, go to My Oracle Support (formerly OracleMetaLink) using the following URL:

http://support.oracle.com

To obtain a patch, see Section 1.6, "Downloading and Applying Required Patches."

44.2 Oracle Business Intelligence Issues and Workarounds Identified or Changed Since the Last Revision

The issues and workarounds related to Oracle Business Intelligence that have been identified or changed since the last revision of the Release Notes include:

- Section 44.16.8.19, "Incorrect Commands to Start and Stop Administration Server on a Windows Environment"
Impacted Releases: 11.1.1.7

44.3 Which Releases Are Covered by These Release Notes?

These release notes identify known issues in the following major releases of Oracle BI EE 11g:

- 11.1.1.3

- 11.1.1.5

- 11.1.1.6, including the following patchsets:

- 11.1.1.6.2

- 11.1.1.6.2 (BP1)

- 11.1.1.7, including the following patchset:

- 11.1.1.7.10

These release notes do not identify known issues in other patchset releases (for example, 11.1.1.6.4) or individual patches. For information regarding known issues identified in other patchsets and individual patches, refer to the readme file that accompanies each patchset or patch.

44.3.1 Oracle Business Intelligence Issues and Workarounds that Apply Only to Release 11.1.1.3

A number of issues and workarounds related to Oracle Business Intelligence Release 11.1.1.3 were identified prior to the January 2011 revision of the Release Notes. To find out more about those issues and workarounds, see the Oracle Business Intelligence chapter in the Oracle Fusion Middleware Release Notes for 11g Release 1 (11.1.1) at:

http://download.oracle.com/docs/cd/E14571_01/relnotes.htm

Other issues and workarounds related to Oracle Business Intelligence that apply only to Release 11.1.1.3. are described in this chapter as well as issues and workarounds that apply to subsequent Oracle Business Intelligence releases and are also known to apply to Release 11.1.1.3.

44.4 Oracle Business Intelligence General Issues and Workarounds

This section describes general issues and workarounds related to Oracle Business Intelligence. It includes the following topics:

- Section 44.4.1, "Oracle BI Disconnected Analytics Not Included in Oracle Business Intelligence 11g, Releases 11.1.1.5 and Later"

- Section 44.4.2, "Oracle Hyperion Smart View for Office Not Supported in Oracle Business Intelligence 11g, Releases 11.1.1.5, 11.1.1.6.0, and 11.1.1.6.2"

- Section 44.4.3, "Issue with JAR File Size When Moving from a Test to a Production Environment"

- Section 44.4.4, "Adobe Flash Player Version 10.1 or Later Required to View Graphs and Scorecards"

- Section 44.4.5, "Recommended Page Size Setting on Oracle Solaris"

- Section 44.4.6, "Siteminder Not Supported with Full-Text Catalog Search with Oracle Secure Enterprise Search"

- Section 44.4.7, "Full-Text Search Not Finding BI Publisher Reports by Report Column"

- Section 44.4.8, "Out of Memory Error When Crawling the Catalog"

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

- Section 44.4.10, "Graph Subtypes Are Not Refreshed in BI Composer"

- Section 44.4.11, "Dashboards and Scorecards Whose Paths Contain Multibyte Characters Do Not Display on ADF Pages"

- Section 44.4.12, "Characters Supported in Folder Names by BI Presentation Services Not Supported by BI Publisher"

- Section 44.4.13, "Configuring SSO for Essbase and Hyperion Financial Management Data Sources with Oracle Business Intelligence 11.1.1.3"

- Section 44.4.14, "Configuring SSO for Essbase and Hyperion Financial Management Data Sources With Oracle Business Intelligence 11.1.1.5, 11.1.1.6, and 11.1.1.6.2"

- Section 44.4.15, "Patch Available to Hide Selected Consistency Check Warnings"

- Section 44.4.16, "Issues with WebLogic LDAP User Passwords"

- Section 44.4.17, "Configuring the GUID Attribute in the Identity Store"

- Section 44.4.18, "Rendering Issues Might Occur in Presentation Services When Using Microsoft Internet Explorer 9.x"

- Section 44.4.19, "Links Fail to Open in PDF Format of the Briefing Book"

- Section 44.4.20, "Poor Performance Starting Up WebLogic Server"

- Section 44.4.21, "Analysis State Is Not Maintained for Breadcrumbs"

- Section 44.4.22, "Enhancements to Accessibility Features"

- Section 44.4.23, "Using Non-Native Characters In ODBC Data Source Administrator Wizard"

44.4.1 Oracle BI Disconnected Analytics Not Included in Oracle Business Intelligence 11g, Releases 11.1.1.5 and Later

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Oracle Business Intelligence Enterprise Edition 10g included the Oracle BI Disconnected Analytics component. The Oracle BI Disconnected Analytics component is not shipped in (and cannot be used with) Oracle Business Intelligence Enterprise Edition 11g, Releases 11.1.1.5 and later.

If you currently use Oracle BI Disconnected Analytics 10g and want to continue to do so, then do not install or upgrade to Oracle Business Intelligence Enterprise Edition 11g, Release 11.1.1.6.

44.4.2 Oracle Hyperion Smart View for Office Not Supported in Oracle Business Intelligence 11g, Releases 11.1.1.5, 11.1.1.6.0, and 11.1.1.6.2

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

Oracle Hyperion Smart View for Office, which provides analytic capabilities within a Microsoft Office environment, supports a set of capabilities based on Oracle BI EE. This feature allows end users to query directly against an Oracle BI Server, create ad-hoc interactions, and use Microsoft Office based reporting. This feature is not available in Oracle BI EE 11g Releases 11.1.1.5, 11.1.1.6.0, and 11.1.1.6.2.

Starting with Release 11.1.1.7, a new version of Oracle Hyperion Smart View for Office is available for download from the Home page in Oracle Business Intelligence Enterprise Edition.

44.4.3 Issue with JAR File Size When Moving from a Test to a Production Environment

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

This issue is applicable when moving from a test environment to a production environment. The Oracle Business Intelligence installation creates a JAR file of approximately 5 GB. JDK version 6 (or earlier) has a file size limit of 4 GB. Therefore, when you un-jar the file using the AS command pasteBinary, a crash occurs.

The workaround is to force either the pasteBinary command to use JRockit, which does not have a file size limit, or use JDK version 7. For instructions, see Oracle Fusion Middleware Administrator's Guide.

44.4.4 Adobe Flash Player Version 10.1 or Later Required to View Graphs and Scorecards

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

The Adobe Flash Player is a cross-platform browser-based application runtime environment and is required for rendering graphs and scorecard objects in a browser.

Users must have Adobe Flash Player version 10.1 or later installed on their browsers to correctly view all graphs and scorecards that are generated by Oracle BI EE. Users can obtain information about the version of the Adobe Flash Player that is running on their browser by going to http://www.adobe.com/software/flash/about/.

44.4.5 Recommended Page Size Setting on Oracle Solaris

For better Oracle Business Intelligence scalability, the page size must be set to 256M on Oracle Solaris.

44.4.6 Siteminder Not Supported with Full-Text Catalog Search with Oracle Secure Enterprise Search

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

The full-text catalog search feature of Oracle BI EE when configured with Oracle Secure Enterprise Search is not supported with Single Sign-On in Siteminder.

44.4.7 Full-Text Search Not Finding BI Publisher Reports by Report Column

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

You can use the full-text catalog search feature to locate objects in the catalog. If you search for BI Publisher reports by report column names, then you might obtain no results.

To work around this issue when you use Secure Enterprise Search Version 11.1.2.2.0, add the following line to the ORACLE_HOME/search/data/config/crawler.dat file:

MIMEINCLUDE application/octet-stream

If you encounter this issue when you use Oracle Endeca Server, then this issue has no workaround.

44.4.8 Out of Memory Error When Crawling the Catalog

Impacted Releases: 11.1.1.7

In certain situations, you might experience an out-of-memory issue while crawling or data loading the Oracle BI Presentation Catalog for full-text searching. This issue can occur if the catalog is large or has a deep folder structure.

To work around this issue, you can segment the crawl or data load into smaller pieces:

- For the Oracle Endeca Server, create multiple agents to handle each smaller data load. Ensure that each agent has its own "Start Location" and "Exclude Paths" values.

- For Oracle Secure Enterprise Search, perform the following steps:

1. Open the BISearchConfig.properties file for editing.

2. Change the "RootNode" value to specify the start location.

3. Change the "ExcludePaths" value to specify the folders to exclude.

4. Save the changes and close the file.

For example, suppose that the catalog has the following folder structure:

/users
/shared
/shared/Reports
/shared/Dashboards

Create agents to crawl or data load the following paths:

/users folder structure
/shared (excluding all sub-folders)
/shared/Reports
/shared/Dashboards

44.4.9 Problems Installing in Thai and Turkish Locales

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Turkish and Thai users are recommended to install and run Oracle Business Intelligence using the English locale. Due to instability that might be encountered, the Turkish and Thai locales are not supported on the server side. Oracle Business Intelligence does support Turkish and Thai locales as clients.

44.4.10 Graph Subtypes Are Not Refreshed in BI Composer

Impacted Releases: 11.1.1.5

When you select a non-default graph subtype in the BI Composer Wizard: Create Analysis: Edit Graph panel and later change the view to a different graph type in the BI Composer Wizard: Create Analysis: Select Views panel, the graph subtype does not get refreshed.

The workaround is to select the first option in the Subtype box in the BI Composer Wizard: Create Analysis: Edit Graph panel. (The first option is the default subtype for the new graph type.)

44.4.11 Dashboards and Scorecards Whose Paths Contain Multibyte Characters Do Not Display on ADF Pages

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Dashboards and scorecards whose paths contain multibyte characters do not display on ADF pages.

This issue has no workaround.

44.4.12 Characters Supported in Folder Names by BI Presentation Services Not Supported by BI Publisher

Impacted Releases: 11.1.1.5

Oracle BI Presentation Services supports a set of characters for catalog folder names that BI Publisher does not support. Characters not supported by BI Publisher are:

~, !, #, $, %, î, &, *, +, `, |, :, ", \\, <, >, ?, ,, /

Folders named with these characters might exhibit unexpected behavior if you log in directly to BI Publisher; for example, the folder might not be visible, the folder might not expand properly, or the name might appear garbled.

To work around this issue, do not use these characters in folder names.

44.4.13 Configuring SSO for Essbase and Hyperion Financial Management Data Sources with Oracle Business Intelligence 11.1.1.3

Impacted Releases: 11.1.1.3

Note:

This issue first appeared in the Oracle Business Intelligence chapter of the Oracle Fusion Middleware Release Notes for 11g Release 1 (11.1.1) at:

http://download.oracle.com/docs/cd/E14571_01/relnotes.htm

The text in the originally published release note is incorrect. The correct text appears in this section.

If you want to use Essbase or Hyperion Financial Management as a data source for the Oracle BI Server, and you want to authenticate using a shared token rather than configuring shared credentials in the connection pool, you must first enable compatibility for shared tokens using the steps provided in this section. If you enable compatibility for shared tokens, do not select Shared logon in the connection pool. Note that the Oracle Business Intelligence user and the Enterprise Performance Management user must use the same identity store.

If you do not enable compatibility for shared tokens, and you also do not provide shared credentials in the connection pool, then the Oracle BI Server attempts to authenticate using the pass-through user credentials (in other words, the user name and password used to log on to Oracle Business Intelligence).

Before you begin, ensure that you have the database connection information available for the Oracle Business Intelligence database where you populated the BI Platform schemas using RCU. For example, ensure that you have the host name, port, SID, user name, and password for the database.

To enable CSS token generation for single sign-on from the Oracle BI Server to Essbase or Hyperion Financial Management data sources:

1. In the Oracle Business Intelligence environment, open setDomainEnv.sh (or setDomainEnv.bat on Windows) for editing. You can find this file at:

DOMAIN_HOME/bin

For example:

MW_HOME/user_projects/domains/bifoundation_domain/bin

2. Add the following entry:

ExtraJavaProperties=-DEPM_ORACLE_INSTANCE= ORACLE_INSTANCE

For example:

ExtraJavaProperties=-DEPM_ORACLE_INSTANCE= C:\My_MW_Home\instances\instance1

3. Save and close the file.

4. Download the patch for bug 10263740 from My Oracle Support to obtain the utility. See Section 44.1.1, "Obtaining Patches from My Oracle Support" for more information.

5. Extract the contents of the archive to:

ORACLE_INSTANCE/config/foundation/11.1.2.0

Create this directory if it does not already exist.

6. Edit epm_components_creation.sh (or epm_components_creation.bat on Windows) to provide required values for ORACLE_HOME, ORACLE_INSTANCE, and JAVA_HOME as appropriate for your environment.

7. On Linux systems, make epm_components_creation.sh executable using the following command:

chmod +x epm_components_creation.sh

8. Run the executable epm_components_creation.sh (or epm_components_creation.bat on Windows), and provide the database host name, port, SID, user name, and password as command-line arguments. For example:

epm_components_creation.sh db_hostname db_port sid db_user db_pwd

The following output is displayed:

Writing credentials to reg.properties file.
Credentials written to reg.properties file.
Creating Component Types.
Component Types Created.
Creating Basic Components
Basic Components Created
All tasks successfully completed.

9. To validate that the data was successfully populated in the EPM Registry, execute epm_components_creation.sh (or epm_components_creation.bat on Windows) and provide "validate" as a command-line argument. For example:

epm_components_creation.sh validate

The following output is displayed:

Following required properties are available for SHARED_SERVICES_PRODUCT in EPM Registry:-
mode=FUSIONAPPS
COMPATIBILITY=11120-

10. Restart the BI domain, including the Administration Server and Managed Servers.

44.4.14 Configuring SSO for Essbase and Hyperion Financial Management Data Sources With Oracle Business Intelligence 11.1.1.5, 11.1.1.6, and 11.1.1.6.2

Impacted Releases: 11.1.1.5, 11.1.1.6, 11.1.1.6.2, 11.1.1.7

If you want to use Essbase or Hyperion Financial Management as a data source for the Oracle BI Server, and you want to authenticate using a shared token rather than configuring shared credentials in the connection pool, then you must first enable compatibility for shared tokens using the steps provided in this section. Note that the Oracle Business Intelligence user and the Enterprise Performance Management user must use the same identity store.

The steps to configure SSO for Essbase and Hyperion Financial Management data sources are different, depending on which release of Enterprise Performance Management you are using. This section contains the following topics:

- Section 44.4.14.1, "Configuring SSO for Essbase and Hyperion Financial Management Release 11.1.2.1 or Later"

- Section 44.4.14.2, "Configuring SSO for Essbase and Hyperion Financial Management Release 11.1.2.0 or Earlier"

44.4.14.1 Configuring SSO for Essbase and Hyperion Financial Management Release 11.1.2.1 or Later

To configure the Oracle BI Server for shared token generation for Essbase and Hyperion Financial Management Release 11.1.2.1 or later (installed with the EPM System Installer), you first run the runRegSyncUtil utility, and then you run an epmsys_registry command. When these steps are complete, you can select SSO using CSS Token in the data source connection pool in the Oracle BI Repository to designate an SSO connection.

To configure SSO for Essbase and Hyperion Financial Management Release 11.1.2.1 or later:

1. Locate the regSyncUtil_OBIEE-TO-EPM.zip file under BI_ORACLE_HOME/common/CSS/11.1.2.0 and extract it to the same location.

Note:

For Oracle Business Intelligence Release 11.1.1.5 only, you must first obtain regSyncUtil_OBIEE-TO-EPM.zip by downloading patch 14606665. See Section 44.1.1, "Obtaining Patches from My Oracle Support" for more information about downloading patches.

2. Copy the reg.properties file from:

EPM_ORACLE_INSTANCE/config/foundation/11.1.2.0

to:

BI_ORACLE_HOME/common/CSS/11.1.2.0/regSyncUtil/src

3. On Linux systems, make runRegSyncUtil.sh executable using the following command:

chmod +x runRegSyncUtil.sh

4. Open runRegSyncEditUtil.sh (or runRegSyncEditUtil.bat on Windows systems) for editing. You can find the runRegSyncEditUtil file in BI_ORACLE_HOME/common/CSS/11.1.2.0/regSyncUtil.

5. In the file, update the ORACLE_HOME and ORACLE_INSTANCE environment variables as appropriate for the given Oracle Business Intelligence environment. Note that ORACLE_HOME should be equivalent to MW_HOME/Oracle_BI1 and ORACLE_INSTANCE should be equivalent to MW_HOME/instances/instancen.

6. Save and close the file.

7. Run the utility. The following example shows how to run the utility on Linux:

BI_ORACLE_HOME/common/CSS/11.1.2.0/regSyncUtil/runRegSyncUtil.sh

8. Run following epmsys_registry.sh command:

BI_ORACLE_INSTANCE/config/foundation/11.1.2.0/epmsys_registry.sh removeproperty
SHARED_SERVICES_PRODUCT/@applicationId

9. Restart the BI Domain, including the Administration and Managed Servers.

10. Restart all OPMN processes.

After these steps are complete, you can select SSO using CSS Token in the General tab of the connection pool object that corresponds to the Essbase or Hyperion Financial Management data source in the Oracle BI repository. You should also select the Virtual Private Database option in the corresponding database object to protect cache entries.

44.4.14.2 Configuring SSO for Essbase and Hyperion Financial Management Release 11.1.2.0 or Earlier

To configure the Oracle BI Server for shared token generation for Essbase and Hyperion Financial Management Release 11.1.2.0 or earlier (installed with the EPM System Installer), you first run an epmsys_registry command, and then you select SSO using CSS Token in the data source connection pool in the Oracle BI Repository.

To configure SSO for Essbase and Hyperion Financial Management Release 11.1.2.1 or later, run the following command from the Oracle Business Intelligence environment:

BI_ORACLE_INSTANCE/config/foundation/11.1.2.0/epmsys_registry.sh/cmd
updateproperty SHARED_SERVICES_PRODUCT/@COMPATIBILITY 11120-

After this step is complete, you can select SSO using CSS Token in the General tab of the connection pool object that corresponds to the Essbase or Hyperion Financial Management data source in the Oracle BI repository. You should also select the Virtual Private Database option in the corresponding database object to protect cache entries.

44.4.15 Patch Available to Hide Selected Consistency Check Warnings

Impacted Releases: 11.1.1.3

You can download and apply patch 11810367 to hide selected warnings from the Consistency Check Manager. After applying the patch, the following warnings are hidden by default: 39009, 39054, 39055, 39057, and 39059. See Section 44.1.1, "Obtaining Patches from My Oracle Support" for more information about downloading patches.

To make these warnings visible again in the Consistency Check Manager, follow these steps:

1. Click the Options button in the Consistency Check Manager to open the Consistency Check Warnings dialog.

2. Deselect the warnings that you want the Consistency Check Manager to display.

3. Click OK.

You can also add additional warnings to the exclusion list in the Consistency Check Warnings dialog. To do this:

1. Go to the following directory:

ORACLE_INSTANCE/config/OracleBIServerComponent/coreapplication_obisn

2. In that directory, create a text file called warn_off.ini. This file must be in ASCII format.

3. Populate the file with contents similar to the following, listing the warning numbers that you want to add to the exclusion list in the Consistency Check Warnings dialog:

[CCOptions]
CC_WARNINGS_LIST = 39024,39077

Note the following:

- All excluded warnings must be on one line and can be separated by a comma, a semicolon, or a space.

- You cannot exclude errors. You can only exclude warnings from the Consistency Check Manager.

- If you add warning numbers from the default exclusion list (39009, 39054, 39055, 39057, and 39059), they are ignored.

4. Save and close the file.

5. Close and then re-open the Consistency Check Manager. The new warnings are displayed in the Consistency Check Warnings dialog and are selected by default, meaning that those warnings are excluded from consistency checks.

44.4.16 Issues with WebLogic LDAP User Passwords

Impacted Releases: 11.1.1.3

If you experience issues with WebLogic LDAP user passwords that contain non-ascii characters, please contact Oracle Support and reference bug 9929485 for details of a patch.

44.4.17 Configuring the GUID Attribute in the Identity Store

Impacted Releases: 11.1.1.3

If you configure an alternative authentication provider such as Oracle Application Server or Active Directory, and you change the GUID attribute from its default value, then you must ensure that the value that you use in the Identity Store matches the changed value that you are using in the alternative authentication provider.

For example, if you use Oracle Internet Directory and have changed the default value of the GUID attribute from orclguid to newvalue, then you must set the value to newvalue in both the Identity Store and the authentication provider.

To configure the GUID attribute in the Identity Store:

1. In Fusion Middleware Control, navigate to \Weblogic domain\bifoundation_domain in the navigation pane.

2. Right-click bifoundation_domain and select Security, then Security Provider Configuration to display the Security Provider Configuration page.

3. In the Identity Store Provider area, click Configure to display the Identity Store Configuration page.

4. In the Custom Properties area, use the Add option to create a Custom Property called PROPERTY_ATTRIBUTE_MAPPING with a new value for the GUID attribute (for example, GUID=newvalue).

Table 44-1 Custom Properties

Property Name

Value

PROPERTY_ATTRIBUTE_MAPPING

Specify the GUID attribute value that is set in the authentication provider. For example, if the GUID attribute is set to newvalue in the authentication provider, then set this value to GUID=newvalue.

5. Click OK to save the changes.

6. Restart the Administration Server, Managed Server(s), and BI components.

44.4.18 Rendering Issues Might Occur in Presentation Services When Using Microsoft Internet Explorer 9.x

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

If you are using Internet Explorer Version 9.x, you might see the following issues when running Presentation Services:

- Truncate option does not truncate the title

- Deleting the Conditional property enlarges the screen

- Bars drop down when using the magnifying glass to zoom

- Graph title does not show in a graph view

- Graph views have a black background

- Event Channels area in the Map Properties dialog is not empty as it should be by default

- Some arrow down keys do not line up correctly in the dialogs that are used for Business Intelligence formatting

- Some dialogs that are used for Business Intelligence formatting are oversized

- When hovering the mouse pointer in the right corner of the Filters section, you cannot see the toolbar

- The New Filter dialog does not display in the browser

44.4.19 Links Fail to Open in PDF Format of the Briefing Book

The links to Oracle Business Intelligence content fail to open in the PDF format of the briefing book.

Workaround

Use the links in the Bookmarks section of the PDF document.

44.4.20 Poor Performance Starting Up WebLogic Server

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

If you are running BI Publisher using a shared catalog with Oracle BI Enterprise Edition, you might experience a prolonged delay when restarting the WebLogic server using either the "Activate Changes" button in the WebLogic console, or using the WebLogic.sh script.

To improve startup performance, you can move or delete the following sets of folders from the <DOMAIN_HOME>/config/bi publisher/repository. Removing these folders has an impact during runtime, therefore ensure that you understand the impact before moving or removing the folders.

- Tools - this folder contains the BI Publisher Desktop Tools executable binary files that are available from the user Home page Tools download links. These links no longer function when the Tools directory is removed. No other BI Publisher functionality is affected. The BI Publisher Desktop Tools are also available from the install media and from the Oracle Technology Network (OTN).

- Reports/Samples - the Samples folder contain the sample reports and data models delivered with BI Publisher.

If English is the only language required for your system, then you can also remove the following:

- Admin/Translation - these folders contain the translation files for languages other than English.

44.4.21 Analysis State Is Not Maintained for Breadcrumbs

Impacted Releases: 11.1.1.7

If you are navigating within an analysis (for example, performing drilling) when the analysis is opened from the Home or Catalog pages or from an action link, then the state for the analysis is not maintained by the breadcrumb trail. However, the dashboard page state is maintained including navigating within an analysis on a dashboard page.

44.4.22 Enhancements to Accessibility Features

Impacted Releases: 11.1.1.7

The following enhancements have been added to the accessibility features:

- Enhanced markup support for defined column interaction and navigation in accessibility mode.

- A new predefined presentation variable, @{session.accessibility}, to indicate whether accessibility mode is enabled for the current user session.
This variable is helpful, for example, to control dashboard section visibility by changing what content gets displayed, depending on whether the user is running in regular mode or accessibility mode.

44.4.23 Using Non-Native Characters In ODBC Data Source Administrator Wizard

Impacted Releases: All 11.1.1.6.x and 11.1.1.7.x releases.

In ODBC Data Source Administrator wizard, you cannot create a System DSN for Oracle BI Server 11g if the Name that you specify contains non-Native characters.

In addition, if you specify a Name with Native characters and a Description with non-Native characters, then you can save the DSN, but when you edit the DSN the Description is displayed as question mark characters (that is, '?').

Examples of non-Native characters:

- Surrogate characters on CCJK Windows.

- Asian or Arabic characters on European Windows.

Workaround

Use Native characters to specify a Name and Description.

44.5 Oracle Business Intelligence Installation Issues and Workarounds

This section describes issues and workarounds related to installing Oracle Business Intelligence. It includes the following topics:

- Section 44.5.1, "Error When Installing Oracle Business Intelligence Against a SQL Server Database"

- Section 44.5.2, "Scale-Out Scenarios Are Not Supported on OS with Different Patch Levels"

- Section 44.5.3, "Need to Correctly Create the Oracle Central Inventory in a UNIX Environment"

- Section 44.5.4, "Oracle Business Intelligence Installer Stops at Administrator User Details Screen"

- Section 44.5.5, "Installing Oracle Business Intelligence on a Shared Drive Might Fail"

- Section 44.5.6, "Configuring DB2 to Support Multibyte Data"

- Section 44.5.7, "Using Multibyte Data Causes Issues with Microsoft SQL Server 2005/2008 Driver in Oracle BI Scheduler"

- Section 44.5.8, "Missing Locale Causes Oracle Business Intelligence Installation to Fail on UNIX"

- Section 44.5.9, "Ignore FAT File System Error Message When Performing an Enterprise Installation"

- Section 44.5.10, "Financial Reporting Print Server Not Enabled"

- Section 44.5.11, "Oracle Hyperion Calculation Manager does not work correctly without Adobe Flash Player"

- Section 44.5.12, "Oracle Universal Installer Incorrectly Reports "No IPv4 Network Interfaces Found""

- Section 44.5.13, "Oracle Business Intelligence Configuration Error with Multiple Instances"

- Section 44.5.14, "Managed Server Starts with Low Memory Settings"

Depending on your Oracle Fusion Middleware implementation, some information in Chapter 2, "Installation, Patching, and Configuration" might also be relevant.

44.5.1 Error When Installing Oracle Business Intelligence Against a SQL Server Database

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

If you are using an MS SQL Server database when installing Oracle Business Intelligence, then the mds-owsm and bip_datasource JDBC data sources has an invalid test table. This stops the WebLogic Server automatic connection testing from functioning. For example, if the database stops, WebLogic Server does not recognize a hanging or invalid connection.

The workaround is to edit the Test Table Name parameter to allow a SQL string to be executed to test the connection. To do so, set the parameter in the WebLogic Server Administration Console to SQL select 1.

44.5.2 Scale-Out Scenarios Are Not Supported on OS with Different Patch Levels

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

Scale-out scenarios of the BI domain are not supported on computers that have the same operating system but different patch levels. All computers must have the same operating system patch level.

This constraint continues to apply to later releases and has been added to the Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

44.5.3 Need to Correctly Create the Oracle Central Inventory in a UNIX Environment

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

When installing Oracle Business Intelligence on a computer running a supported UNIX operating system with no other Oracle software, ensure that you create the Oracle central inventory correctly. This action ensures correct patching functionality.

44.5.4 Oracle Business Intelligence Installer Stops at Administrator User Details Screen

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

If you attempt to install on a Windows system that is using DHCP, does not have a primary DNS suffix, and does not have a loopback adapter configured, then the Oracle Business Intelligence installer stops at the screen that prompts for the Administrator user details. This is displayed as a red cross in the tree on the left-hand side of the installer. This issue is caused by the installer not being able to resolve the IP address to a host name.

The workaround is to configure a loopback adapter or primary DNS suffix.

44.5.5 Installing Oracle Business Intelligence on a Shared Drive Might Fail

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Attempting to install Oracle Business Intelligence on a shared drive might fail, resulting in the following error message:

Installation Failed. Prepare Session failed You may not have enough space on your drive for a successful install. Do you still want to continue?

To avoid this issue when installing Oracle Business Intelligence on a shared drive, start the Oracle Business Intelligence installer from the command line using the ignoreDiskWarning option. For example, on Linux, use the following command:

./runInstaller -ignoreDiskWarning

44.5.6 Configuring DB2 to Support Multibyte Data

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When installed with an IBM DB2 database, the Oracle Business Intelligence installer configures the system with an ODBC 2.0 driver. In such systems, issues occur if multibyte data is used. To avoid this issue, use Oracle Enterprise Manager to configure the Oracle Business Intelligence system to use the native DB2 CLI driver instead.

To configure Oracle Business Intelligence to use DB2 CLI driver with IBM DB2:

1. Install the DB2 client software on the machines where Oracle Business Intelligence resides, and create a data source to the scheduler database.

2. After you install Oracle Business Intelligence, log into the system through Oracle Enterprise Manager.

3. Navigate to the Scheduler tab for the Oracle Business Intelligence server.

4. Click Lock and Edit Configuration.

5. Click the Call Interface drop-down list and select DB2 CLI - Unicode.

6. In the Data Source field, enter the data source name.

7. Click Apply, and then Activate Changes.

44.5.7 Using Multibyte Data Causes Issues with Microsoft SQL Server 2005/2008 Driver in Oracle BI Scheduler

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When installed with a Microsoft SQL Server 2005/2008 database, the Oracle Business Intelligence installer configures Oracle BI Scheduler with a SQL Server 2005/2008 driver. If multibyte data is used, scheduled jobs might fail. To avoid this issue, use Oracle Enterprise Manager to configure the Oracle Business Intelligence system to use a SQL Server 7.0/2000 driver instead.

To configure Oracle BI Scheduler to use the SQL Server 7.0/2000 driver with Microsoft SQL Server 2005/2008:

1. After you install Oracle Business Intelligence, log into the system through Oracle Enterprise Manager.

2. Navigate to the Scheduler tab for the Oracle Business Intelligence server.

3. Click Lock and Edit Configuration.

4. Click the Database drop-down list and select SQL Server 7.0/2000.

5. Click Apply.

44.5.8 Missing Locale Causes Oracle Business Intelligence Installation to Fail on UNIX

Impacted Releases: 11.1.1.5

The Oracle Business Intelligence installation fails on UNIX if the locale en_US.UTF-8 does not exist on the installation computer. To avoid this issue, ensure that the locale en_US.UTF-8 exists on the installation computer before you install Oracle Business Intelligence.

44.5.9 Ignore FAT File System Error Message When Performing an Enterprise Installation

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When performing an Enterprise Installation, under certain circumstances, you might see the error message "Middleware Home Location is in FAT file system". This message can occur when you install on an NTFS file system. You can click Yes to safely proceed with the installation.

44.5.10 Financial Reporting Print Server Not Enabled

Impacted Releases: 11.1.1.7

When installed on an Oracle Business Intelligence instance, the Financial Reporting print server is unable to print.

To enable the Financial Reporting print server, apply the configuration template by performing the following steps:

1. Ensure that all processes in the domain are stopped, including all Oracle instances, the Administration Server, all Managed Servers, and Node Manager.

2. Start the Configuration Wizard.
On UNIX operating systems:

cd BI_ORACLE_HOME/common/bin

./config.sh

On Windows operating systems:

cd BI_ORACLE_HOME\common\bin

config.bat

3. On the Welcome screen, select Extend an existing WebLogic domain.

4. On the Select a WebLogic Domain Directory screen, select the location of the existing Oracle BI domain.

5. On the Select Extension Source screen, select Extend my domain using an existing extension template and select the following:
On UNIX operating systems:

ORACLE_HOME/common/templates/applications/oracle.frprintserver_template_11.1.1.jar

On Windows operating systems:

ORACLE_HOME\common\templates\applications\oracle.frprintserver_template_11.1.1.jar

6. Continue with the remainder of the Configuration Wizard screens to apply this template.

7. After the template is applied, restart all Oracle Instances, the Administration Server, Managed Servers, and Node Manager.

44.5.11 Oracle Hyperion Calculation Manager does not work correctly without Adobe Flash Player

Impacted Releases 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When installed as a component of Oracle Business Intelligence, the Rule Designer and the Template Designer in Oracle Hyperion Calculation Manager do not open if Adobe Flash Player (version 10.1 or higher) is not already installed on the computer from where Oracle Hyperion Calculation Manager is being accessed.

If the Adobe Flash Player is not installed already, go to http://get.adobe.com/flashplayer and follow the instructions to download and install the latest version of Adobe Flash Player for the platform.

44.5.12 Oracle Universal Installer Incorrectly Reports "No IPv4 Network Interfaces Found"

Impacted Releases 11.1.1.7

On some environments, the Oracle Universal Installer (OUI) incorrectly reports "no IPv4 network interfaces found" and does not allow installation to proceed.

If you confirm that IPv4 network interfaces are available, then restart the installer with the extra parameter DISABLE_IPV4_CHECK=true

For example, on Linux, enter the following command:

./runInstaller "DISABLE_IPV4_CHECK=true"

44.5.13 Oracle Business Intelligence Configuration Error with Multiple Instances

When more than one instance of Oracle Business Intelligence 11g Release 1 (11.1.1.7.0) is configured on a computer, the second instance fails on dual IP systems, if you select the Auto Port Configuration option. The following error is seen in the nqscheduler.log file located in the ORACLE_INSTANCE/diagnostics/logs/OracleBISchedulerComponent/coreapplication_obisch1 directory:

Scheduler Error: [nQSError: 12002] Socket communication error atcall=bind: (Number=125) Address already in use

As a workaround, you must set the custom port values for Oracle Business Intelligence. Refer to Section 4.2.8, "Setting Custom Port Values for Oracle Business Intelligence" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence for more information.

44.5.14 Managed Server Starts with Low Memory Settings

Due to the Bourne shell limitations on Oracle Solaris 10 systems, the value for SVR_GRP parameter in the BI Domain Home/servers/bi_server1/logs/bi_server1.out file is set to null. Therefore, the Managed Server, bi_server1 starts with low memory settings.

As a workaround, perform the following steps:

1. Change /bin/sh to /bin/bash in the following files located in the BI Domain Home/bin directory:

- setDomainEnv.sh

- startWeblogic.sh

- stopWeblogic.sh

- secureWeblogic.sh

2. Restart the BI Domain, the Administration Server, and the Managed Server instances from the Admin Console.

44.6 Oracle Business Intelligence Upgrade Issues and Workarounds

This section describes issues and workarounds related to upgrading Oracle Business Intelligence from previous releases. It includes the following topics:

- Section 44.6.1, "General Upgrade Issues and Workarounds"

- Section 44.6.2, "Security-related Upgrade Issues and Workarounds"

Depending on your Oracle Fusion Middleware implementation, some information in Chapter 3, "Upgrade" might also be relevant.

44.6.1 General Upgrade Issues and Workarounds

This section describes general issues and workarounds related to upgrading Oracle Business Intelligence from previous releases. It includes the following topics:

- Section 44.6.1.1, "Conditional Formatting Might Not Work After Upgrading from Oracle Business Intelligence Release 10g to Release 11g"

- Section 44.6.1.2, "Issues Exporting Large Data Sets to Microsoft Excel"

- Section 44.6.1.3, "Managed Server for Oracle BI Encounters Issues After Upgrade from Release 11.1.1.3"

- Section 44.6.1.4, "MapViewer Runtime Failure After Upgrading from Release 11.1.1.6 to Release 11.1.1.7"

44.6.1.1 Conditional Formatting Might Not Work After Upgrading from Oracle Business Intelligence Release 10g to Release 11g

Impacted Releases: 11.1.1.5

If an attribute column's Value Suppression setting (in the Column Format tab of the Column Properties dialog) is not set to Repeat, then the measure is aggregated to the grain as defined by the position of the column with the format defined. This might cause a change in the conditional formatting after upgrading from Oracle Business Intelligence Release 10g to Release 11g. If the Value Suppression setting is set to Repeat, then the measure column that the conditional format is based on always uses the detail grain of the table view, in which case the conditional formatting works as expected.

This issue continues to apply to later releases and has been added to the Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

44.6.1.2 Issues Exporting Large Data Sets to Microsoft Excel

Impacted Releases: 11.1.1.7

In Oracle Business Intelligence Release 10g, you might have been accustomed to exporting large data sets (that is, those over 10000 rows) to Excel format. In Release 11g, while it is still possible to export directly to an Excel format, you might notice greater performance when exporting large numbers of rows if you export first to CSV, then import that file into Excel. If Oracle Business Intelligence is installed on a computer with a 32-bit operating system, then you should export to CSV format for greater performance.

If you must export a large data set without using the CSV format on a computer with a 64-bit operating system, then you might experience an out-of-memory error. If you see this error message, then you must likely increase the heap size for the JavaHost service. The default heap size is 1024MB. Depending on the available memory on the computer, you might want to increase the heap size for the JavaHost service using the procedure that is described in Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

44.6.1.3 Managed Server for Oracle BI Encounters Issues After Upgrade from Release 11.1.1.3

Impacted Releases: 11.1.1.7

After you upgrade from Release 11.1.1.3, you might find that the Managed Server for Oracle Business Intelligence encounters issues. For example, the Managed Server might not start or might time out. Use the following list to diagnose the issue:

- Do you see an out-of-memory error message related to "'PermGen Space" in the following file:
MW_HOME\user_projects\domains\bifoundation_domain\servers\bi_server1\logs\bi_server1-diagnostics.log

- Have you checked if the appropriate memory settings are in effect?
Open the following file in a text editor:

MW_HOME\user_projects\domains\bifoundation_domain\bin\bi_server1.out

At the top of the file, look for a line that provides the Java memory settings that are used when the system starts. If you see the following line:

MEM_ARGS="-Xms256m -Xmx1024m -XX:MaxPermSize=256m"

then the settings are incorrect.

To work around these issues, you must edit a file called setOBIDomainEnv.cmd on Windows or setOBIDomainEnv.sh on UNIX. Ensure that you do not edit the similarly named setDomainEnv.cmd and setDomainEnv.sh files. The specifications in the setOBIDomainEnv file overwrite those in the setDomainEnv file.

1. Change to the following directory and locate the setup script (setOBIDomainEnv.cmd or setOBIDomainEnv.sh) for the Managed Server environment:
MW_HOME\user_projects\domains\bifoundation_domain\bin\

2. Make a backup copy of the setOBIDomainEnv file.

3. Open the setOBIDomainEnv file for editing in a text editor.

4. Locate the following line:
MEM_ARGS="-Xms256m -Xmx1024m -XX:MaxPermSize=256m"

and replace it with this text:

MEM_ARGS="-Xms256m -Xmx1024m -XX:MaxPermSize=512m"

5. Save the changes and close the file.

6. Restart the Node Manager and the Managed Server, as described in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

7. Rerun the Configuration Assistant to update the Oracle BI Domain.

8. Perform these steps for each Managed Server in the cluster.

44.6.1.4 MapViewer Runtime Failure After Upgrading from Release 11.1.1.6 to Release 11.1.1.7

Impacted Releases: 11.1.1.7

After upgrading from Release 11.1.1.6 to Release 11.1.1.7, the MapViewer component is in an invalid state which causes a ERROR 500 when the MapViewer URL is accessed. (Note that this is not an issue for Release 11.1.1.7 installations that have not been upgraded from Release 11.1.1.6.)

The symptoms of this issue are:

- Accessing the MapViewer URL (http://hostname:port/mapviewer), returns an Error 500 Internal Server Error.

- In the managed server log (MW_HOME/user_projects/domains/bifoundation_domain/servers/bi_server1/logs/bi_server1-diagnostic.log), the following error is recorded at start up:
[ERROR] [] [javax.enterprise.resource.webcontainer.jsf.application] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'][userId: <anonymous>] [ecid: 0000Jvu4dî5FKAW5Hzt1if1He7Tî000002,0] [APP: mapviewer#11.1.1] JSF1030: The specified InjectionProvider implementation 'com.bea.faces.WeblogicInjectionProvider' cannot be loaded.

The workaround is to manually remove a number of files from the MapViewer deployment and to delete the WebLogic internal cache of the MapViewer application. To do so:

1. Stop the Managed Server (for example, bi_server1).

2. If Release 11.1.1.7.1 patches:

- Will be applied, skip this step.

- Will not be applied, delete the following files from the MapViewer deployment (for example, MW_HOME/Oracle_BI1/bifoundation/jee/mapviewer.ear

- web.war/WEB-INF/lib/adf-faces-api.jar

- web.war/WEB-INF/lib/adf-faces-impl.jar

- web.war/WEB-INF/lib/commons-digester.jar

- web.war/WEB-INF/lib/commons-logging-1.1.jar

- web.war/WEB-INF/lib/jsf-api.jar

- web.war/WEB-INF/lib/jsf-impl.jar

- web.war/WEB-INF/lib/jsr173_1.0_api.jar

- web.war/WEB-INF/lib/mvutil.jar

- web.war/WEB-INF/lib/xdb.jar

- web.war/WEB-INF/adf-faces-config.xml

- web.war/WEB-INF/orion-web.xml

3. Recursively delete the following directory:
MW_HOME/user_projects/domains/bifoundation_domain/servers/bi_server1/tmp/_WL_user/mapviewer_11.1.1

4. Restart the Managed Server.

44.6.2 Security-related Upgrade Issues and Workarounds

This section describes issues and workarounds related to security when upgrading Oracle Business Intelligence from previous releases. It includes the following topics:

- Section 44.6.2.1, "Warnings Might Be Reported When Upgrading an RPD with Non-English User or Group Names"

- Section 44.6.2.2, "Users or Groups With Names Containing Invalid Characters Are Not Upgraded"

- Section 44.6.2.3, "RPD Upgrade Process Fails If the 10g Administrator UserID or Password Contains any Non-Native Characters"

- Section 44.6.2.4, "Errors Might Be Reported In Upgraded Analyses that Contain EVALUATE_ Database Analytic Function"

- Section 44.6.2.5, "Configuration Assistant for Update BI Domain Steps Incorrectly Reports an OCM Configuration Error at 91% Complete when Moving from Earlier 11g Releases"

- Section 44.6.2.6, "SSL Configured in Oracle BI EE 11.1.1.5.x or 11.1.1.6.x Fails After Upgrading to 11.1.1.7"

44.6.2.1 Warnings Might Be Reported When Upgrading an RPD with Non-English User or Group Names

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When upgrading a repository with non-English user or group names, warnings might be reported in the log file, such as "Group name ??? isn't valid in WLS/LDAP : not migrating this group" or "User name ??? isn't valid in WLS/LDAP : not migrating this user" (where ??? is garbled text).

The workaround is to manually create the users or groups. To do so, see the following instructions in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition:

- For a group:

- Create the group as described in Section 2.3.4, "Creating a Group in the Embedded WebLogic LDAP Server."

- Create an Application Role as described in Section 2.4.2, "Creating Application Roles Using Fusion Middleware Control."

- Add the group to the application role as described in Section 2.4.2.2, "Creating an Application Role."

If the repository group was a member of another repository group, then create the same Group and Application Role hierarchy.

- For a user:

- Create the user as described in Section 2.3.3, "Creating a New User in the Embedded WebLogic LDAP Server."

- Assign the user to the required groups as described in Section 2.3.5, "Assigning a User to a Group in the Embedded WebLogic LDAP Server."

44.6.2.2 Users or Groups With Names Containing Invalid Characters Are Not Upgraded

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When upgrading a repository, users or groups with names that contain the following invalid characters are not upgraded:

- ,

- +

- =

- "

- \

- <

- >

- ;

The workaround is to manually create the users or groups after upgrade is complete, with new names that do not contain the invalid characters. Note that the new names must not contain invalid characters under any circumstances. Failure to follow this instruction requires you to re-install Oracle Business Intelligence.

44.6.2.3 RPD Upgrade Process Fails If the 10g Administrator UserID or Password Contains any Non-Native Characters

Impacted Release: 11.1.1.5

The repository upgrade process from Oracle Business Intelligence 10g to Oracle Business Intelligence 11g fails if the 10g Administrator user ID or password contains any non-native characters, and the operating system is Windows or Non-UTF8 Linux. For example, "Administrator/bi10g-éíô" fails to upgrade. The upgrade utility might run to completion, but with error messages, and users cannot log on if you try to run the system using the upgraded repository. You must change the Administrator user ID, password, or both the user ID and password to one that uses only native characters before running the repository upgrade command line utility or Upgrade Assistant wizard.

44.6.2.4 Errors Might Be Reported In Upgraded Analyses that Contain EVALUATE_ Database Analytic Function

Impacted Release: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

To ensure system security, the ability to use the following database analytic functions in analyses is disabled by default:

- EVALUATE

- EVALUATE_ANALYTIC

- EVALUATE_AGGR

- EVALUATE_PREDICATE

Use of these functions in analyses is governed by the setting of the EVALUATE_SUPPORT_LEVEL parameter in the NQSConfig.INI file.

When upgrading systems that previously provided support for these functions in Oracle BI Answers, you must manually add the EVALUATE_SUPPORT_LEVEL parameter to the NQSConfig.INI file and set it appropriately. See Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition for information about the EVALUATE_SUPPORT_LEVEL parameter.

Note the following:

- The EVALUATE_SUPPORT_LEVEL parameter in the NQSConfig.INI file controls the use of the EVALUATE family of database functions within analyses. Oracle recommends leaving EVALUATE_SUPPORT_LEVEL set to its default value of 0 to prevent the use of these functions within analyses. Setting EVALUATE_SUPPORT_LEVEL to a value of 1 or 2 enables users to insert arbitrary SQL expressions into an analysis using the Analysis editor, which potentially compromises data access security. See Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition for information about the EVALUATE_SUPPORT_LEVEL parameter.

- The EVALUATE_SUPPORT_LEVEL parameter in the NQSConfig.INI file does not control use of the EVALUATE family of database functions within the metadata repository.

44.6.2.5 Configuration Assistant for Update BI Domain Steps Incorrectly Reports an OCM Configuration Error at 91% Complete when Moving from Earlier 11g Releases

Impacted Release: 11.1.1.7

When you run the Configuration Assistant and select the Update BI Domain option to move from an earlier 11g release to Release 11.1.1.7, an error might be reported during OCM configuration. The reported error occurs during the Configuring OCM step, when the Configuration Assistant shows 91% complete. However, the error is reported unnecessarily, because OCM is already correctly configured. You can therefore ignore the error message.

44.6.2.6 SSL Configured in Oracle BI EE 11.1.1.5.x or 11.1.1.6.x Fails After Upgrading to 11.1.1.7

Impacted Releases: 11.1.1.7

When SSL is configured in Oracle BI EE 11.1.1.5.x or 11.1.1.6.x, and you upgrade to Oracle BI EE 11.1.1.7 using a software only install and the Configuration Assistant, upgrade fails.

To ensure that SSL configured in Oracle BI EE 11.1.1.5.x or 11.1.1.6.x does not fail after upgrading to 11.1.1.7:

Note:

Before performing these steps, Oracle BI EE 11.1.1.5.x or 11.1.1.6.x must be working in SSL mode, with the non SSL ports disabled.

1. Log in to the WebLogic Server Administration Console and enable the non-SSL listening ports for the Administration Server and Managed Server.
For more information, see Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.

2. Restart WebLogic Server, and make sure that the WebLogic Server Administration Console, Fusion Middleware Control, and Oracle Business Intelligence all work on non-SSL listening ports.
For more information, see "Starting and Stopping Oracle Business Intelligence" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

3. Run the Oracle Business Intelligence 11.1.1.7 installer and perform for example, a software only install in the 11.1.1.5.x Oracle home.
For more information, see Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

4. Run the Configuration Assistant to update the BI Domain on the same installation.
The BI Domain must be updated successfully.

For more information, see "Running the Configuration Assistant to Update the Domain" in Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

5. Log in to the WebLogic Server Administration Console and disable the non-SSL ports for the Administration Server and Managed Server.
For more information, see "Configuring Oracle WebLogic Server to Use Only the HTTPs Protocol by Disabling Non-SSL Listen Ports" in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.

6. Restart WebLogic Server, and make sure that the WebLogic Server Administration Console, Fusion Middleware Control, and Oracle Business Intelligence all work only on SSL ports.

44.7 Oracle Business Intelligence Installation Guidelines for 64-Bit Platforms

- Section 44.7.1, "Prerequisites for Software Only Installation on 64-Bit Platforms"

- Section 44.7.2, "Supported Installation Types for Oracle Business Intelligence on 64-Bit Platforms"

- Section 44.7.3, "Considerations and Limitations of Enterprise Install Type for Scaling Out Existing Installations"

44.7.1 Prerequisites for Software Only Installation on 64-Bit Platforms

Impacted Releases: 11.1.1.3

Prior to performing an Oracle Business Intelligence software only installation, you must install the latest Oracle WebLogic Server wls1033_generic.jar in MW_Home with 64-bit JDK. Then install Oracle Business Intelligence in the same MW_Home.

44.7.2 Supported Installation Types for Oracle Business Intelligence on 64-Bit Platforms

Different types of installation options available for Oracle Business Intelligence are as follows:

- Simple Install
Impacted Releases: 11.1.1.3

This installs 32-bit JVM and 32-bit Oracle WebLogic Server. Oracle Business Intelligence Server is a 64-bit system on 64-bit platforms. Simple Install is supported on the following 64-bit Platforms only:

- Linux x86-64

- Windows x86-64

However, for production the recommended installation type is software only install with 64-bit Oracle WebLogic Server and 64-bit JDK.

- Software Only Install
This installs software binary files in an Oracle home for later configuration as part of the Oracle Fusion Middleware deployment process. This installation type is required if you want to install Oracle Business Intelligence with a 64-bit JVM on a supported 64-bit operating system.

Recommended installation steps for 64-bit platforms are as follows:

- Install 64-bit Oracle WebLogic Server with 64-bit JDK.

- Choose Oracle Business Intelligence Software Only Install option.

- Once software only install process is complete, select Configure.

- Enterprise Install
Since 11.1.1.6.0 release, Enterprise Install for Oracle Business Intelligence is supported on 64-bit systems. For details, refer to Section 4.5.2, "Enterprise Install for New Installations" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

44.7.3 Considerations and Limitations of Enterprise Install Type for Scaling Out Existing Installations

To scale out an existing installation with a 64-bit JVM on a supported 64-bit operating system, do not select the Enterprise Install type option. Select the Software Only Install type instead.

For details, refer to Section 4.4.4, "Software Only Install" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

44.8 Oracle Business Intelligence Analyses and Dashboards Issues and Workarounds

This section describes issues and workarounds related to Oracle Business Intelligence analyses and dashboards. It includes the following topics:

- Section 44.8.1, "General Analyses and Dashboards Issues and Workarounds"

- Section 44.8.2, "Actions Issues and Workarounds"

- Section 44.8.3, "Scorecards and KPI Issues and Workarounds"

- Section 44.8.4, "Agents Issues and Workarounds"

- Section 44.8.5, "Microsoft Office Integration Issues and Workarounds"

44.8.1 General Analyses and Dashboards Issues and Workarounds

This section describes general issues and workarounds related to Oracle Business Intelligence analyses and dashboards. It includes the following topics:

- Section 44.8.1.1, "Existing Dashboard Prompts Based on Columns Renamed in the Business Model Do Not Work"

- Section 44.8.1.2, "Gauge Views Might Be Cut Off and Not Visible Under Certain Conditions"

- Section 44.8.1.3, "Numerical Units on a Dashboard Prompt Slider Might Not Be Translated Correctly"

- Section 44.8.1.4, "After Printing a Dashboard Page Using the Safari Browser on Windows, the Page No Longer Responds to Certain Left Clicks"

- Section 44.8.1.5, "Scorecard Diagrams on Dashboard Pages Might Print as Tables"

- Section 44.8.1.6, "Using Maps with Column Selectors"

- Section 44.8.1.7, "Issue with Wrap-Around Feature for Maps"

- Section 44.8.1.8, "Inability to Delete Map Tiles in MapViewer"

- Section 44.8.1.9, "Support for Rendering Small Form-Factor Graphs"

- Section 44.8.1.10, "Analyses Whose Paths Contain Latin Supplement Characters Fail to Open on Dashboard Pages"

- Section 44.8.1.11, "In Selection Steps Search for Members in Hierarchical Columns That Are Non-Text Yields No Results"

- Section 44.8.1.12, "Interactions on Right-Click Menus Are Not Translated"

- Section 44.8.1.13, "Issues with the Alignment of Trellis Views"

- Section 44.8.1.14, "Characters in Trellis Title Display Incorrectly in Certain Languages"

- Section 44.8.1.15, "Export to Excel 2007+ and Export to PDF Do Not Support Custom CSS Styles"

- Section 44.8.1.16, "Items Not Supported When Using Custom Print Layouts"

- Section 44.8.1.17, "Grand Total Shows Zero in Reports After Applying BI 11.1.1.7.1 Patch"

44.8.1.1 Existing Dashboard Prompts Based on Columns Renamed in the Business Model Do Not Work

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

If a column is renamed in the Business Model, then existing dashboard prompts based on that column do not work with newly created analyses.

The workaround is to use Catalog Manager to rename the column in the catalog.

44.8.1.2 Gauge Views Might Be Cut Off and Not Visible Under Certain Conditions

Impacted Releases: 11.1.1.5

Under certain conditions, if the size of the canvas assigned to a gauge view is very small, and the legend is set to display on the left, then some of the gauges in the gauge view might be cut off and not visible.

The workaround is to edit the gauge view and change the Legend position to Right, Top, or Bottom. Alternatively, you can increase the size of the gauge view canvas so that all gauges display.

44.8.1.3 Numerical Units on a Dashboard Prompt Slider Might Not Be Translated Correctly

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

The numerical units (such as million or billion) that are displayed on a dashboard prompt slider might not be translated correctly.

The workaround is to modify the obiprp.promptcomponents.xml file as follows:

1. Open the obiprp.promptcomponents.xml file for editing. You can find the file here:
ORACLE_INSTANCE\bifoundation\web\msgdb\l_XX\messages\uicmsgs

2. Ensure that each entry for a numerical unit (such as tag name kmsgSliderBillion, kmsgSliderMillion, or kmsgSliderDecillion) is translated correctly.

3. Restart the Managed Servers, the Administration Server and all Oracle Business Intelligence Java components, and the Oracle Business Intelligence system components. For information on how to restart the Managed Servers, the Administration Server and all Oracle Business Intelligence Java components, and the Oracle Business Intelligence system components, see Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

44.8.1.4 After Printing a Dashboard Page Using the Safari Browser on Windows, the Page No Longer Responds to Certain Left Clicks

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

After you print a dashboard page in PDF or HTML format using the Safari browser on Windows, the dashboard page no longer responds to certain left clicks, for example, a left click to print again or to change tabs.

The workaround is to exit and reopen the dashboard page. Alternatively, press and hold down the Ctrl key and then left-click.

44.8.1.5 Scorecard Diagrams on Dashboard Pages Might Print as Tables

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When you print a dashboard page that contains multiple scorecard diagrams (for example a strategy tree, strategy map, custom view, and cause & effect map) in PDF or HTML format, some of the diagrams might print as tables rather than diagrams.

The workaround is to scroll down the page and wait until all the diagrams have fully rendered before printing.

44.8.1.6 Using Maps with Column Selectors

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

If you want to use a column selector view with map views, then ensure that you add all map views to the analysis before you add the column selector view.

44.8.1.7 Issue with Wrap-Around Feature for Maps

Impacted Releases: 11.1.1.6.2

Release 11.1.1.6.2, Bundle Patch 1 includes the wrap-around feature in map views. This feature allows you to pan the map to a point where lines on the map are unbroken, such as when showing an airline flight path from San Francisco to Tokyo. If you use this feature, then you might notice that the portion of the map that has been wrapped might not render correctly when printing or exporting the view. This issue has no workaround.

44.8.1.8 Inability to Delete Map Tiles in MapViewer

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

You might see an error message when trying to delete a tile layer from the Manage Map Tiles page of Oracle MapViewer. To work around this issue, either directly delete the tile layer from the database, or delete it using the Map Builder tool.

This bug affects all versions of Oracle BI EE that use MapViewer version "Ver11_1_1_7_B120531". You can see the version of MapViewer that the Oracle BI EE installation is using by opening the MapViewer page in a browser and clicking the Home tab. Find the version number at the bottom-left corner of the page.

44.8.1.9 Support for Rendering Small Form-Factor Graphs

Impacted Releases: 11.1.1.5

This release includes support for rendering small form-factor graphs, for example, graphs that are 75 pixels X 25 pixels or 68 pixels X 18 pixels. Small form-factor graphs are also referred to as micrographs.

To render a small form-factor graph:

1. Edit the analysis.

2. Edit the graph.

3. Click the Edit graph properties toolbar button to display the Graph Properties dialog.

4. In the General tab, make the following settings:

- In the Legend Location box, select None.

- Deselect the Animate graph on Display box.

5. Click the Style tab and make the following settings:

- In the Style box in the Graph Data area, select Default.

- In the Plot area, select the Specify option for Gridlines.

- For Major Grid, deselect the Horizontal Lines and Vertical Lines boxes.

- For Minor Grid, deselect the Horizontal Lines box.

- In the Legend area, deselect the Transparent box.

- In the Canvas Colors and Borders area, deselect the Gradient box.

6. Click the Titles and Labels tab and make the following settings:

- In the Graph Title area, deselect the Use measure name as graph title box.

- In the Axis titles area, deselect the following boxes:

- Use measure name as axis title for Vertical Axis 1 Title

- Use measure name as axis title for Vertical Axis 2 Title

- Use column name as axis title for Horizontal Axis Title

7. Click OK to close the Graph Properties dialog.

8. Click Done to close the Graph editor.

9. Click the Analysis editor: Advanced tab.

10. Save a copy of the existing XML in the XML Code box as a backup.

11. In the XML Code box in the Analysis XML area, add the following attribute to the display element for the graph that you want to render as a small form-factor graph:

useAutoLayout="false"

For example:

<saw:display type="line" subtype="default" renderFormat="flash" mode="online" xAxisLiveScrolling="false" yAxisLiveScrolling="false" clientEventEnabled="false"  animateOnDisplay="false" useAutoLayout="false">

Important:

Do not use this setting for a graph that is a reasonable size, such as, a graph that is 400 pixels X 300 pixels. Doing so might result in undesirable graph behavior or loss of information.

12. Click Apply XML.

13. Click Save Analysis.

44.8.1.10 Analyses Whose Paths Contain Latin Supplement Characters Fail to Open on Dashboard Pages

Impacted Releases: 11.1.1.5, 11.1.1.6

Analyses whose paths contain Latin Supplement characters fail to open on dashboard pages when the locale is Chinese, Japanese, Korean, Hebrew, or Arabic and you are using Internet Explorer 7 as the Web browser.

The workaround is to append &charset=utf-8 to the URL.

44.8.1.11 In Selection Steps Search for Members in Hierarchical Columns That Are Non-Text Yields No Results

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When working with selection steps, if you search for members in hierarchical columns that are non-text (for example, date or time), then the search yields no results.

This issue has no workaround.

44.8.1.12 Interactions on Right-Click Menus Are Not Translated

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2

The interactions on right-click menus for table views and pivot table views are not translated.

44.8.1.13 Issues with the Alignment of Trellis Views

Impacted Releases: 11.1.1.6.2, 11.1.1.7

If you notice any issues with the alignment of trellis views, then you can manually edit a configuration file to adjust the alignment.

Locate the xdo.cfg file in the following directory:

config/OracleBIJavahostComponent/coreapplication_objh1

and increase the value of the fo-chunk-size setting.

44.8.1.14 Characters in Trellis Title Display Incorrectly in Certain Languages

Impacted Releases: 11.1.1.7

In certain instances, characters in the horizontal or vertical axis title of a trellis are displayed as square boxes. This situation can occur when the Oracle BI Server runs on a Windows platform and when the language is Simplified Chinese, Traditional Chinese, Japanese, Korean.

This issue has no workaround.

44.8.1.15 Export to Excel 2007+ and Export to PDF Do Not Support Custom CSS Styles

Impacted Releases: 11.1.1.7

Export to Excel 2007+ and export to PDF do not support custom CSS styles. When you export an analysis for which a custom CSS style or custom CSS class has been specified to Excel 2007+ or to PDF, the customization is lost. (You specify a custom CSS style or custom CSS class for an analysis using the Custom CSS Style Options (HTML Only) component in the Column Properties dialog: Style tab.)

44.8.1.16 Items Not Supported When Using Custom Print Layouts

Impacted Releases: 11.1.1.7

The following items are not supported in BI Publisher when using a custom print layout to print a dashboard page:

- Column Selector views.

- Create Segment views.

- Create Target List views.

- Funnel graph views.

- Legend views.

- Logical SQL views.

- Map views.

- Narrative views.

- Performance Tile views.

- Ticker views.

- Trellis views, including microcharts.

- View Selector views.

- These types of gauge views:

- Bulb.

- Vertical Bar.

- Horizontal Bar.

- These types of graph views:

- Pie graphs with multiple measures; instead a separate pie is displayed for each measure.

- Time Series Line graphs.

- Scatter graphs.

- Waterfall graphs.

- These graph settings in the Graph Properties dialog:

- In the General tab: Zoom and Scroll.

- In the Style tab: conditional formatting settings.

- In the Scale tab: all settings.

- In the Titles and Labels tab, the following formatting settings:

- Truncate in the Font Format: Item dialog: Display Options tab for the graph title and axis titles.

- Treat Numbers As, Negative Format, and Use 1000's Separator in the Format: Item dialog: Number Format tab for vertical axis labels and data markers and Decimal Places in the Format Item dialog: Number Format tab for vertical axis labels.

- Label Orientation in the Format: Item dialog: Display Options tab for vertical axis labels and horizontal axis labels and Abbreviate in the Format: Item dialog: Display Options tab for vertical axis labels.

- Hierarchical columns.

- Dashboard column formatting.

- Dashboard prompts.

- Pivot table or table prompts.

- Prompt edge on a view.

- Dashboard columns that have been frozen.
You use the Freeze Column option in the Column Properties menu to freeze a column at an edge (top or left) of a dashboard layout. For more information, see "Properties Buttons for Objects" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition.

- A fixed size specified for a dashboard column or section.
You specify a fixed size by setting the Size option in the Additional Formatting Options area of the Section Properties dialog and the Column Properties dialog. For more information, see "Section Properties dialog" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition.

- Fixed headers of rows and columns in a table or pivot table.
You specify fixed headers by selecting Fixed headers with scrolling content as the method to use to browse data. For more information, see "Table Properties dialog: Style tab," "Pivot Table Properties dialog," and "Trellis Properties dialog: General tab" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition.

- The grouping functionality for bubble graphs (achieved by the Bubbles drop target), scatter graphs (achieved by the Points drop target), and pie graphs (achieved by the Pies drop target).

You also need to be aware of the following expected object behavior in BI Publisher: pivot tables are expanded.

44.8.1.17 Grand Total Shows Zero in Reports After Applying BI 11.1.1.7.1 Patch

Impacted Releases: 11.1.1.7.1 and 11.1.1.7.10.

After applying the BI 11.1.1.7.1 Patch, some reports display grand totals that are calculated as zeros when values are expected. This is due to the fact that prior to applying the BI 11.1.1.7.1 Patch, the order of operations enforced by parentheses in an expression like 100*(FILTER("Bug DB"."Facts"."# Bugs" USING (("Bug DB"."Bug Header"."Test Status" ='A')))/"Bug DB"."Facts"."# Bugs") was not performed correctly.

Workaround

1. In Oracle BI EE Answers, open the report that contains the invalid grand totals, and edit the SQL Statement.

2. Search for the expression.
For example:

100*(FILTER("Bug DB"."Facts"."# Bugs"USING (("Bug DB"."Bug Header"."Test Status" ='A')))/"Bug DB"."Facts"."# Bugs")

3. Remove the first opening parenthesis '(' and the final closing parenthesis ')'.
For example, after removing the parentheses, the example query statement in step 2 would be:

100*FILTER("Bug DB"."Facts"."# Bugs"USING (("Bug DB"."Bug Header"."Test Status" ='A')))/"Bug DB"."Facts"."# Bugs"

4. Save the changes.

44.8.2 Actions Issues and Workarounds

This section describes issues and workarounds related to actions. It includes the following topic:

- Section 44.8.2.1, "EJBs in Action Framework Must Be Deployed to the WebLogic Managed Server"

44.8.2.1 EJBs in Action Framework Must Be Deployed to the WebLogic Managed Server

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

A limitation currently exists in the Action Framework functionality when creating actions to invoke Java methods in EJBs. Only EJBs deployed within the same J2EE container as the Action Framework services (by default the WebLogic Managed Server) are available to the Action Framework.

The workaround is to invoke a target EJB. To do so, implement one of the following methods:

- Deploy the target EJB to the WebLogic Managed Server in the BI domain (adhering to any license restrictions for WebLogic Server).

- Deploy a gateway EJB/Web service on the WebLogic Managed Server specifically to invoke the remote EJB.

- Expose the remote EJB as a Web service.

- Deploy a gateway Web service on the remote location to invoke the EJB.

44.8.3 Scorecards and KPI Issues and Workarounds

This section describes issues and workarounds related to scorecards and KPIs. It includes the following topics:

- Section 44.8.3.1, "No Results Returned When Searching in the Related Documents of Scorecards or Scorecard Components"

- Section 44.8.3.2, "Accessing a Smart Watchlist from the Oracle Secure Enterprise Search Results Page Causes an Error"

- Section 44.8.3.3, "Item Stale Error When Editing a Shared Scorecard in Parallel"

- Section 44.8.3.4, "Scorecard Pie Chart and Gauge Labels are Not Readable in Chrome"

44.8.3.1 No Results Returned When Searching in the Related Documents of Scorecards or Scorecard Components

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

You can use the full-text catalog search functionality to search in most catalog objects and related documents. Currently, the full-text catalog search functionality searches in scorecards themselves and in the names of related documents, but it does not search in the content of related documents for scorecards.

44.8.3.2 Accessing a Smart Watchlist from the Oracle Secure Enterprise Search Results Page Causes an Error

Impacted Releases: 11.1.1.6.2, 11.1.1.7

If Oracle BI Enterprise Edition is configured with Oracle Secure Enterprise Search, and from the search results page you attempt to open a smart watchlist, an error occurs and the following error message displays:

doPost.searchServletDisabled :To test the feed servlet using a browser, run servlet with '-Doracle.ecsf.crawl.mode.debug=true'

There is no workaround for this issue.

44.8.3.3 Item Stale Error When Editing a Shared Scorecard in Parallel

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When using a shared Oracle BI Presentation Catalog and a scaled-out configuration of Oracle BI Presentation Services, users might see "Item Stale : <scorecard path>" errors, when they edit a shared scorecard in parallel.

The workaround to prevent this error is to turn off the Oracle BI Presentation Services Catalog Attribute Cache. To do so, set the following in the instanceconfig.xml file:

<ps:Cache xmlns:ps="oracle.bi.presentation.services/config/v1.1">
<ps:CatalogAttributes>
<ps:Enabled>false</ps:Enabled>
</ps:CatalogAttributes>
</ps:Cache>

For more information on the cache, see Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

44.8.3.4 Scorecard Pie Chart and Gauge Labels are Not Readable in Chrome

Impacted Releases: 11.1.1.6.2 (BP1), 11.1.1.7

You might have font issues when using the Google Chrome browser.

The workaround for this issue is to update the Flash player to version 11.5 or higher because there is a known Chrome bug. Refer to http://code.google.com/p/chromium/issues/detail?id=140415 for additional information.

44.8.4 Agents Issues and Workarounds

This section describes issues and workarounds related to agents. It includes the following topics:

- Section 44.8.4.1, "Agent Deliveries Fail with Microsoft Active Directory and Oracle Virtual Directory"

- Section 44.8.4.2, "Agent Incorrectly Delivers Content to Active Delivery Profile When Only the Home Page and Dashboard Option Is Selected"

44.8.4.1 Agent Deliveries Fail with Microsoft Active Directory and Oracle Virtual Directory

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

If you are using Microsoft Active Directory and Oracle Virtual Directory, then agent deliveries fail.

The workaround is to apply the Oracle Virtual Directory Patch Number 9904956 - GUID Returned for AD User Cannot Be Used in Search Filter.

44.8.4.2 Agent Incorrectly Delivers Content to Active Delivery Profile When Only the Home Page and Dashboard Option Is Selected

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When you specify that an agent is to deliver content only to the Home page and dashboard pages by selecting the Home Page and Dashboard option and deselecting the Devices option in the Destination tab of the Agent editor, there is a known issue where the agent delivers content to the active delivery profile even though the Devices option is deselected.

The workaround is to set the priority of the agent so that it does not match an existing delivery profile.

44.8.5 Microsoft Office Integration Issues and Workarounds

This section describes issues and workarounds related to the integration between Oracle Business Intelligence and Microsoft Office. It includes the following topics:

- Section 44.8.5.1, "Using Microsoft Office 2007 with Oracle BI Add-in for Microsoft Office"

- Section 44.8.5.2, "Server Connections Are Not Automatically Shared by Microsoft Excel and PowerPoint"

- Section 44.8.5.3, "Previous Installation of Oracle BI Add-in for Microsoft Office Must Be Manually Uninstalled"

- Section 44.8.5.4, "Errors in the Online Help for Oracle BI Add-In for Microsoft Office"

- Section 44.8.5.5, "Refreshing Table or Pivot Table Views with Double Columns in Page Edge Might Result in Error"

- Section 44.8.5.6, "Double Column Cascading Results in Incorrect Display Values"

- Section 44.8.5.7, "Intermittent Timeout Errors"

- Section 44.8.5.8, "Lack of Support for Vary Color By Target Area"

- Section 44.8.5.9, "Measure Column Labels Might Display Incorrectly When Inserted into Microsoft Excel"

- Section 44.8.5.10, "Stacked Graphs Do Not Display Negative Values"

- Section 44.8.5.11, "Scatter Graphs with Lines Display as Default Scatter Graphs in Excel and PowerPoint"

- Section 44.8.5.12, "Graphs With Section Edges Are Not Supported Starting With Release 11.1.1.6.x"

- Section 44.8.5.13, "Refreshing Table Views in Arabic or German Versions of Excel Result in Incorrect Data Values"

- Section 44.8.5.14, "Inserting a View With a Grand Total Column or Row into Microsoft Office Might Cause Issues"

- Section 44.8.5.15, "Time Displayed in Table or Pivot View Title Might Be Incorrect after Insertion"

- Section 44.8.5.16, "Graphs Might Be Displayed Differently After Insertion into Microsoft Office"

- Section 44.8.5.17, "Legends in Bubble and Scatter Graphs Might Display Differently After Insertion into Microsoft Office"

- Section 44.8.5.18, "Help System Does Not Work When Running Oracle BI Office for PowerPoint in Norwegian or Polish"

- Section 44.8.5.19, "Protected Worksheet Causing Incorrect Message When Inserting View in Oracle BI Add-in for Microsoft Office"

- Section 44.8.5.20, "Column Data in Section Edge Is Not Obtained"

Note:

Many of the issues and associated workarounds described in this section on integration between Oracle Business Intelligence and Microsoft Office do not apply or have been addressed when using Smart View to integrate with Microsoft Office. While you can continue to download Oracle Business Intelligence Add-in for Microsoft Office to integrate with Microsoft Office, it is strongly recommended that you download Smart View instead.

44.8.5.1 Using Microsoft Office 2007 with Oracle BI Add-in for Microsoft Office

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

If you use Microsoft Office 2007 with Oracle BI Add-in for Microsoft Office, then ensure that Office 2007 SP1 at minimum is installed. If you do not, you might encounter file interchangeability issues between Microsoft Office 2007 and Microsoft Office 2003.

For more detailed information on versions, see the certification document available on Oracle Technology Network (OTN):

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

44.8.5.2 Server Connections Are Not Automatically Shared by Microsoft Excel and PowerPoint

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Microsoft Excel and PowerPoint on the same computer share Oracle BI Add-in for Microsoft Office connections. If you create a connection in Excel, then that connection is also available in PowerPoint. However, if you create an Oracle BI Add-in for Microsoft Office connection in Excel while PowerPoint is open, then the connection is not displayed in PowerPoint, and vice versa.

The workaround to create a connection to be shared between Excel and PowerPoint is to ensure that the other Microsoft Office application is closed. Alternatively, you can close both Excel and PowerPoint, and reopen them as needed in order to see connections available in both Excel and PowerPoint.

44.8.5.3 Previous Installation of Oracle BI Add-in for Microsoft Office Must Be Manually Uninstalled

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

The Oracle BI Add-in for Microsoft Office 11g installer does not uninstall previous versions of Oracle BI Add-in for Microsoft Office. Therefore, you must manually uninstall any previous Oracle BI Add-in for Microsoft Office installations before installing Oracle BI Add-in for Microsoft Office.

For more information on installing Oracle BI Add-in for Microsoft Office, see Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition.

44.8.5.4 Errors in the Online Help for Oracle BI Add-In for Microsoft Office

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

The following errors are in the online help for Oracle BI Add-in for Microsoft Office:

- In the "Creating a Connection to the Oracle BI Office Server" topic, in Step 1, "From the ribbon, select New" is incorrect. The correct instruction for Step 1 is "From the Ribbon, select Preferences. From Preferences, select the New tab." (This applies to Excel and PowerPoint.)

- In the "Changing the Default Style Template" topic, in Step 1, the location given for the default template is valid only for Windows 32-bit installations. In Windows 64-bit installations, the default location is <BI Office installation directory>\ BIOfficeExcel|Template. (This applies to Excel.)

- The "Setting Log Levels" topic should state that users must have proper access permission to the log file location. (This applies to Excel and PowerPoint.)

44.8.5.5 Refreshing Table or Pivot Table Views with Double Columns in Page Edge Might Result in Error

Impacted Releases: 11.1.1.5

In Oracle BI Add-in for Microsoft Excel, you cannot refresh table views or pivot table views with double columns in the page edge. To work around this issue, ensure that double columns are not in the page edge (also called table prompt in table views and the pivot prompt in pivot table views).

44.8.5.6 Double Column Cascading Results in Incorrect Display Values

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

If double columns are used in cascaded prompts for both columns, then you might see code being displayed instead of the correct display values.

44.8.5.7 Intermittent Timeout Errors

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

If the BI Office Server is configured to connect to Presentation Services through Oracle HTTP Server (OHS), then you might see intermittent error messages that are caused by the timeout of a request. To work around this issue, increase the Keepalive timeout value for OHS to 15 seconds or more.

44.8.5.8 Lack of Support for Vary Color By Target Area

Impacted Releases: 11.1.1.5

If you use the Vary Color By target area for graph views when creating analyses in Oracle BI EE, then you might find that the results are displayed incorrectly in Microsoft Excel and PowerPoint.

44.8.5.9 Measure Column Labels Might Display Incorrectly When Inserted into Microsoft Excel

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Measure column labels in the section edge or the page edge (also called table prompt in table views and the pivot prompt in pivot table views) of table and pivot table views might display incorrectly when inserted into Microsoft Excel.

The workaround is to not use measure columns in the section edge or page edge.

44.8.5.10 Stacked Graphs Do Not Display Negative Values

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Stacked graphs do not display negative values when they are inserted into Microsoft Excel or PowerPoint. This happens because the default Microsoft graph engine, which governs these graphs, does not display negative values.

44.8.5.11 Scatter Graphs with Lines Display as Default Scatter Graphs in Excel and PowerPoint

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When you select the scatter graph with lines graph style to insert into Microsoft Excel or PowerPoint, the default scatter graph (without lines) is displayed instead. This happens because Microsoft does not support scatter graphs with lines.

44.8.5.12 Graphs With Section Edges Are Not Supported Starting With Release 11.1.1.6.x

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Release 11.1.1.6.x of Oracle BI Add-In for Microsoft Office Release does not support graphs with section edges. Therefore, if a graph with section edges was inserted using Release 11.1.1.5.0 of Oracle BI Add-In for Microsoft Office Release, an error is returned when it is refreshed in Release 11.1.1.6.0.

44.8.5.13 Refreshing Table Views in Arabic or German Versions of Excel Result in Incorrect Data Values

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

In German or Arabic Versions of Microsoft Excel 2007 or 2010, number formatting might be lost after table views that have been secured are refreshed.

44.8.5.14 Inserting a View With a Grand Total Column or Row into Microsoft Office Might Cause Issues

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Views that use the "before" location to show row-level grand totals overwrite values in the first column of the analysis when they are inserted into Microsoft Excel.

Views that use the "before" location to show column-level grand totals return errors when they are inserted into Microsoft PowerPoint.

The workaround is to use the "after" location instead.

44.8.5.15 Time Displayed in Table or Pivot View Title Might Be Incorrect after Insertion

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

If "Display time to be shown in the title" is selected for a table or pivot view, the time shown in the title after the table or pivot is inserted into Microsoft Office might be incorrect.

44.8.5.16 Graphs Might Be Displayed Differently After Insertion into Microsoft Office

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Graphs that are inserted into Microsoft Office might be plotted differently in Microsoft Office than they are in Oracle BI EE. In horizontal bar graphs, the horizontal-axis series might be displayed in reverse order. In stacked graphs, the stack order might be reversed. This is caused by the Microsoft graph engine.

44.8.5.17 Legends in Bubble and Scatter Graphs Might Display Differently After Insertion into Microsoft Office

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Legends in bubble and scatter graphs displayed in Microsoft Office do not include coordinate values on the horizontal axis. This means that the number of legends as well as the colors displayed for each data series might not match those displayed in Oracle BI EE.

This issue has no workaround.

44.8.5.18 Help System Does Not Work When Running Oracle BI Office for PowerPoint in Norwegian or Polish

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When running Oracle BI Office for PowerPoint in Norwegian or Polish, clicking Oracle BI Help has no effect. The expected behavior is to display the help system in English.

The workaround is as follows:

1. Navigate to the <Oracle BI Office installation folder>\BIOfficePowerPoint\Help directory. For example, C:\Program Files\Oracle\BIOfficePowerPoint\Help.

2. Copy powerpointaddin_help.chm, paste it twice, and rename one powerpointaddin_helpno.chm and the other powerpointaddin_helppl.chm.

44.8.5.19 Protected Worksheet Causing Incorrect Message When Inserting View in Oracle BI Add-in for Microsoft Office

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

When inserting a view in Excel using Oracle BI Add-in for Microsoft Office (BI Office), users might get an incorrect "template not found" message. This can happen even though the template file is present at the correct location (<Oracle BI Office installation folder>\Oracle\BIOfficeExcel\Template). The error message might be displayed if the current workbook or worksheet is protected.

In BI Office release 11.1.1.6.0 and later, when a BI Office operation is performed on a protected worksheet or workbook, the error message is displayed correctly as: "Merge styles failed."

The workaround is as follows:

1. Unprotect the workbook before performing any BI Office-related operations.

44.8.5.20 Column Data in Section Edge Is Not Obtained

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

For table views and pivot table views, when there are columns in the section edge, the data pertaining to the section edge columns is not obtained.

The workaround is, for table views and pivot table views, to move the columns from the section edge into the row edge or page edge. Alternatively, for table views only, use the "Insert As List" command to obtain all the data.

44.9 Oracle Business Intelligence Mobile Issues and Workarounds

Issues and workarounds related to Oracle BI Mobile are described in Oracle Fusion Middleware Release Notes for Oracle Business Intelligence Mobile for Apple iOS and Google Android, which is available at

http://docs.oracle.com/cd/E52471_01/bi.1111/e52669/toc.htm

These release notes include the following products:

- Oracle Business Intelligence Mobile for Apple iOS

- Oracle Business Intelligence Mobile for Google Android

44.10 Oracle Business Intelligence Mobile App Designer Issues and Workarounds

Issues and workarounds related to Oracle BI Mobile App Designer are described in Oracle Business Intelligence Mobile App Designer Release Notes, which is available at

http://docs.oracle.com/cd/E52471_01/bi.1111/e48551/toc.htm

44.11 Oracle Business Intelligence Publisher Reporting and Publishing Issues and Workarounds

This section describes issues and workarounds related to Oracle BI Publisher. It includes the following topics:

- Section 44.11.1, "General Oracle BI Publisher Issues and Workarounds"

- Section 44.11.2, "Oracle BI Publisher Security Issues and Workarounds"

- Section 44.11.3, "Oracle BI Publisher Delivery Manager Issues and Workarounds"

- Section 44.11.4, "Oracle BI Publisher Scheduler Issues and Workarounds"

- Section 44.11.5, "Oracle BI Publisher RTF Template Issues and Workarounds"

- Section 44.11.6, "Oracle BI Publisher Excel Template Issues and Workarounds"

- Section 44.11.7, "Oracle BI Publisher Desktop Tools Issues and Workarounds"

- Section 44.11.8, "Oracle BI Publisher Layout Editor Issues and Workarounds"

- Section 44.11.9, "Oracle BI Publisher Data Model Issues and Workarounds"

- Section 44.11.10, "Oracle BI Publisher Report Building Issues and Workarounds"

- Section 44.11.11, "Oracle BI Publisher Documentation Errata"

44.11.1 General Oracle BI Publisher Issues and Workarounds

This section describes general issues and workarounds related to Oracle BI Publisher. It includes the following topics:

- Section 44.11.1.1, "JDBC Driver Throws Unsupported Function for setBigDecimal"

- Section 44.11.1.2, "Searching the Catalog from the Oracle BI Publisher User Interface Does Not Work When BI Publisher Is Integrated with Oracle BI Enterprise Edition"

- Section 44.11.1.3, "Data Source List in BI Publisher Administration Page Includes Data Sources That Are Not Supported"

- Section 44.11.1.4, "Menu Items Do Not Display When Using Internet Explorer 7 or 8 with a Bidirectional Language Preference"

- Section 44.11.1.5, "Data Source Definition for Microsoft SQL Server 2008 Analysis Services Does Not Get Saved"

- Section 44.11.1.6, "Issues with Viewing Some Report Formats on Apple iPad"

- Section 44.11.1.7, "BI Publisher Objects Exhibit Unexpected Behavior When Located Inside a Folder Named with a Single Quote Character"

- Section 44.11.1.8, "Components Folder Missing from SampleApp Lite Web Catalog"

- Section 44.11.1.9, "Boilerplate Templates in the Components Folder Do Not Display Table Borders Properly in Chrome Browsers"

- Section 44.11.1.10, "Local Policy Attachments (LPAs) Removed from Web Services in Release 11.1.1.5"

- Section 44.11.1.11, "Oracle BI Publisher Requires Oracle WebLogic Server to Run in en_US Locale"

- Section 44.11.1.12, "Search Might Return Incorrect Number of Results"

- Section 44.11.1.13, "Schedule Report Option Is Not Displayed Correctly for Non-Administrator Users"

- Section 44.11.1.14, "Additional Setup for BI Publisher Desktop Tools in 11.1.1.6.2"

- Section 44.11.1.15, "Oracle Endeca Search Does Not Work from /xmlpserver URL"

- Section 44.11.1.16, "Older Version of Adobe Flash Player Packaged with the Google Chrome Browser Might Cause Unexpected Behavior in the Interactive Viewer"

- Section 44.11.1.17, ""Failed to Add" Error When Adding Report Objects to Favorites"

- Section 44.11.1.18, "Cannot Add Reports with Multibyte Character Names to Favorites Using the Catalog Task Option"

- Section 44.11.1.19, "Excel Analyzer and Online Analyzer Deprecated in Release 11.1.1.7"

44.11.1.1 JDBC Driver Throws Unsupported Function for setBigDecimal

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Data models that include a link between a data set of SQL query type against an Oracle database and a data set of SQL query type against the BI Server based on a numeric database column (used to create a parent-child hierarchical XML data structure with the SQL query against the Oracle database as the parent data set) fail to execute and return the following error: "Java.sql.SQLException: unsupported function at oracle.bi.jdbc.AnaJdbcPreparedStatement.setBigDecimal."

44.11.1.2 Searching the Catalog from the Oracle BI Publisher User Interface Does Not Work When BI Publisher Is Integrated with Oracle BI Enterprise Edition

Impacted Releases: 11.1.1.5

When Oracle BI Publisher is installed in integrated mode with Oracle BI EE, searching the catalog from the BI Publisher user interface (that is, the URL is of the form "http://<host>:<port>/xmlpserver/...") does not work and the following message is returned:

Result Not found
Your search - <search criteria> - did not match any documents.

The workaround is to search the catalog from the Oracle BI EE user interface (that is, the URL is of the form "http://<host>:<port>/analytics/...").

44.11.1.3 Data Source List in BI Publisher Administration Page Includes Data Sources That Are Not Supported

Impacted Releases: 11.1.1.5

When configuring a JDBC data source connection or an OLAP connection, the list provided in the BI Publisher Add Data Source page might include data sources that are not supported in this release. For the most current list of supported data sources, refer to the "System Requirements and Supported Platforms for Oracle Business Intelligence Suite Enterprise Edition 11gR1." The system requirements document is available from this link:

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

It is listed with the documents grouped under the Product Area "Additional Oracle Fusion Middleware 11g Release 1 (11.1.1.x) Certifications."

44.11.1.4 Menu Items Do Not Display When Using Internet Explorer 7 or 8 with a Bidirectional Language Preference

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

If you are using Internet Explorer 7 as the Web browser and you have selected a bidirectional language for your user interface preference (such as Arabic or Hebrew), then the menu options from the global header do not display.

To work around this problem using Internet Explorer 8: On the Tools menu select Compatibility View Settings; clear the "Display intranet sites in Compatibility View" check box. Or, use another supported Web browser.

44.11.1.5 Data Source Definition for Microsoft SQL Server 2008 Analysis Services Does Not Get Saved

Impacted Releases: 11.1.1.3, 11.1.1.5

When you create an OLAP data source connection to a Microsoft SQL Server 2008 Analysis Services data source in the BI Publisher Administration interface, the data source is not saved after you click the Apply button, even though the connection test succeeds.

To work around this issue, select "Microsoft SQL Server 2005 Analysis Services" as the OLAP Type from the list. Enter the same connection information and click Apply.

44.11.1.6 Issues with Viewing Some Report Formats on Apple iPad

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

The Apple iPad does not provide a default viewer for the following output formats:

- MHTML (impacts Excel and PowerPoint)

- RTF

The viewer provided for PowerPoint 2007 might distort the layout of characters.

The default PDF viewer has the following issues:

- Form fields are ignored
The iPad PDF reader cannot support editable PDF form fields, however, you can still generate the report with static text in the fields. To generate the report with static text, set the report property "Remove PDF fields from output" to True. For information on setting report properties see "Configuring Report Properties" in Oracle Fusion Middleware Report Designer's Guide for Oracle Business Intelligence Publisher.

- Secured PDF files do not display at all

- Signature fields are ignored

- Bookmarks are ignored

- Attachments are ignored

- Flush does not work

- "Read Out Loud" accessibility feature does not work

Note that these issues are limitations of the provided iPad file readers and cannot be resolved by Oracle.

44.11.1.7 BI Publisher Objects Exhibit Unexpected Behavior When Located Inside a Folder Named with a Single Quote Character

Impacted Releases: 11.1.1.3, 11.1.1.5

In the Oracle BI Presentation Catalog, if a folder name contains the single quote character (') BI Publisher reports that reside in that folder do not run and data models might throw unexpected errors. The behavior varies depending on the Web browser.

To work around this issue, do not include single quotes in the names of folders that contain BI Publisher objects.

44.11.1.8 Components Folder Missing from SampleApp Lite Web Catalog

Impacted Releases: 11.1.1.5

Version 11.1.1.5 of the SampleApp Lite Web catalog is missing the Components folder. As a result, shared boilerplates are unavailable when user creates a new BI Publisher type layout for a BI Publisher report. To work around this issue:

1. Log in with administrator credentials and navigate to the BI Publisher Administration > Server Configuration page.

2. Under the Catalog region, ensure that the BI Publisher Repository field points to the default path:
<Install_Home>/user_projects/domains/bifoundation_domain/config/bipublisher/repository

Then click the Upload to BI Presentation Catalog button.

3. Navigate to the Catalog page and verify that the Components folder is present under Shared Folders.

Note that this also installs additional BI Publisher sample reports included in the Samples folder. Many of these reports require that the Demo JDBC connection to the OE sample schema, included in Oracle Database, is configured.

44.11.1.9 Boilerplate Templates in the Components Folder Do Not Display Table Borders Properly in Chrome Browsers

Impacted Releases: 11.1.1.6

Several of the Boilerplate templates in the Components folder included in version 11.1.1.6 of the SampleApp Lite OBIEE Web catalog, when used as the starting point to create an XPT layout, do not display table borders properly in Chrome Browsers. To correct this behavior, replace the Components folder in SampleApp Lite OBIEE Web catalog with the one included with the BI Publisher standalone repository. To do so:

1. Log in with administrator credentials and navigate to the BI Publisher Administration > Server Configuration page.

2. Under the Catalog region, ensure that the BI Publisher Repository field points to the default path:
<Install_Home>/user_projects/domains/bifoundation_domain/config/bipublisher/repository

Then click the Upload to BI Presentation Catalog button.

3. Navigate to the Catalog page and verify that the Components folder is present under Shared Folders.

Note that this also installs additional BI Publisher sample reports included in the Samples folder. Many of these reports require that the Demo JDBC connection to the OE sample schema, included in Oracle Database, is configured.

44.11.1.10 Local Policy Attachments (LPAs) Removed from Web Services in Release 11.1.1.5

Impacted Releases: Upgrades from 11.1.1.3 to 11.1.1.6

In Release 11.1.1.5, the local policy attachments were removed from the BI Publisher Web services. If you were using the BI Publisher Web services in Release 11.1.1.3 and you upgrade to 11.1.1.5, then you must perform the following to add a Global Policy Attachment (GPA):

1. Log in to Oracle Enterprise Manager Fusion Middleware Control.

2. In the left pane, click WebLogic Domain, and then click bifoundation_domain.

3. In the right pane, click the WebLogic Domain menu and select Web Services and then Policy Sets.

4. Click Create to create a new policy set.

5. Enter the following general information:

- Name - enter any name you choose

- Enabled - select this box

- Type of Resources - Web Service Endpoint

- Description: This GPA is applied for all JRF-based Web services
Click Next.

6. Enter "*" for the Domain Name value. Click Next.

7. Select the following policy, then click Attach:
oracle/wss11_saml_or_username_token_with_message_protection_service_policy

8. Click Next, then click Save. Wait for WebLogic Server to pick up the changes.

9. In a browser, enter the following URL to verify that the policy you entered is available in the WSDL:
http://server:port/xmlpserver/services/PublicReportWSSService?wsdl

44.11.1.11 Oracle BI Publisher Requires Oracle WebLogic Server to Run in en_US Locale

Impacted Release: 11.1.1.3

The XDK used by Oracle BI Publisher requires the JVM of the Oracle WebLogic Server to run in en-US locale. Otherwise, functions (such as sum) generate values that cannot be formatted with its number format functions.

To work around this problem, in the script startWebLogic.cmd add the following line to set the required options:

set JAVA_OPTIONS=-Dfile.encoding=UTF-8 -Duser.language=en -Duser.region=US %JAVA_OPTIONS%

For information on setting Java options in the Oracle WebLogic Server Administration Console, see the topic "Set Java options for servers started by Node Manager" in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.

44.11.1.12 Search Might Return Incorrect Number of Results

Impacted Release: 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Searching for catalog items might yield more results than there actually are. For example, a search on all types of catalog items using "Salary" might show well over 100 results on the first page of the search results, even though there are far fewer actual results.

To find the correct set of results, click the Next button at the bottom of the Result page, then page through the results to find the item that you want.

44.11.1.13 Schedule Report Option Is Not Displayed Correctly for Non-Administrator Users

Impacted Release: 11.1.1.6.0, 11.1.1.6.2

Users with a role other than Administrator (for example: BI Author and BI Consumer) do not see the Schedule action link under report entries in the catalog; nor do they see the Schedule option under the Action menu when viewing a report.

To work around this issue, users can schedule report jobs by using the "New" menu from the global header or by selecting "Report Job" under the Create section on the Home page.

Alternatively, if an application role is granted the oracle.bi.publisher.scheduleReport permission you can also work around this issue as follows:

1. Log in to Oracle Business Intelligence as an Administrator.

2. Navigate to the catalog and select "Shared Folders."

3. In the Tasks region, select Permissions.

4. In the Permissions dialog, select the role and explicitly add the permission "Schedule Publisher Report." Select both cascading options.

44.11.1.14 Additional Setup for BI Publisher Desktop Tools in 11.1.1.6.2

Impacted Release: 11.1.1.6.2

The BI Publisher Desktop Tools executable delivered under the bi_foundation_domain location is not the latest version.

To work around this issue, copy the BIPublisherDesktop.exe from the clients/bipublisher/repository/Tools location to the bifoundation_domain/config/bipublisher/repository/Tools location

This step is also documented in the 11.1.1.6.2 Read Me file.

44.11.1.15 Oracle Endeca Search Does Not Work from /xmlpserver URL

Impacted Release: 11.1.1.7

Search does not work from the BI Publisher URL (that is, .../xmlpserver) when BI Publisher is integrated with Oracle BI Enterprise Edition and Oracle BIEE is configured to use the Endeca Server as the search engine. To work around this issue, perform searches for BI Publisher objects from the Oracle BI EE URL (that is, ../analytics).

44.11.1.16 Older Version of Adobe Flash Player Packaged with the Google Chrome Browser Might Cause Unexpected Behavior in the Interactive Viewer

Impacted Release: 11.1.1.7

You might experience user interface issues when using the Google Chrome browser if you do not update the version of the Adobe Flash Player that is packaged with the Chrome browser.

To work around this issue, update the Adobe Flash player to version 11.4.402.278 or later. To obtain information about the version of the Adobe Flash Player that is running on the browser go to http://www.adobe.com/software/flash/about/.

44.11.1.17 "Failed to Add" Error When Adding Report Objects to Favorites

Impacted Release: 11.1.1.7

When adding reports or data models to the Favorites region you might receive a "Failed to Add" error after dragging and dropping a report to the Favorites region or after clicking the "Add to Favorites" link on the More menu in the catalog. The error is inaccurate. When you navigate back to the Home page, the reports have been added to the Favorites region.

44.11.1.18 Cannot Add Reports with Multibyte Character Names to Favorites Using the Catalog Task Option

Impacted Release: 11.1.1.7

Reports with multibyte character names cannot be added to the Favorites region using the Add to Favorites task available from the More menu in the catalog.

To work around this issue, use the Manage Favorites function in the Home page and drag and drop the report to the Favorites region. See also Section 44.11.1.17, ""Failed to Add" Error When Adding Report Objects to Favorites."

44.11.1.19 Excel Analyzer and Online Analyzer Deprecated in Release 11.1.1.7

Impacted Release: 11.1.1.7

The Excel Analyzer and Online Analyzer are deprecated in 11.1.1.7. To build new templates using Excel, use Excel Templates. To build new reports with interactive output use the BI Publisher layout editor.

44.11.2 Oracle BI Publisher Security Issues and Workarounds

This section describes issues and workarounds related to Oracle BI Publisher security. It includes the following topics:

- Section 44.11.2.1, "Limitations for Administrator Username in LDAP Security Model"

- Section 44.11.2.2, "Oracle E-Business Suite Security Requires the BI Publisher Server Operating System Language to Match an E-Business Suite Enabled Language"

44.11.2.1 Limitations for Administrator Username in LDAP Security Model

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

If you are using LDAP security model for standalone BI Publisher, the LDAP Administrator Username that you enter on the BI Publisher Security Configuration page must be one of the following.

- Admin User defined under "Distinguished Name for Users"

- Admin User with only cn (like cn=Directory Manager) without dc=...

If the Administrator Username entered is not one of the supported options, then scheduled jobs fail with an impersonation error.

44.11.2.2 Oracle E-Business Suite Security Requires the BI Publisher Server Operating System Language to Match an E-Business Suite Enabled Language

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

When Oracle BI Publisher is configured to use Oracle E-Business Suite security, the user authentication process checks the Oracle BI Publisher operating system language against the languages defined in fnd_responsibility_tl. If the BI Publisher operating system language is not found in the list, no responsibilities are returned for the user in the BI Publisher user interface, and the user cannot perform actions in BI Publisher.

To work around this issue, ensure that the BI Publisher operating system language is present in the fnd_responsibility_tl.

44.11.3 Oracle BI Publisher Delivery Manager Issues and Workarounds

This section describes issues and workarounds related to Oracle BI Publisher Delivery Manager.

There are no known issues at this time.

44.11.4 Oracle BI Publisher Scheduler Issues and Workarounds

This section describes issues and workarounds related to Oracle BI Publisher Scheduler. It includes the following topics:

- Section 44.11.4.1, "Scheduler Does Not Support Multibyte Characters When Schema Installed on Microsoft SQL Server"

- Section 44.11.4.2, "URL in E-mail Notification of Recurring or Future-Dated Jobs Might Fail to Display Job History for the Job"

- Section 44.11.4.3, "After Editing an Existing Job, Immediately Creating a New Job Using "Submit as New" Overwrites the Original Job"

44.11.4.1 Scheduler Does Not Support Multibyte Characters When Schema Installed on Microsoft SQL Server

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

If you are using Microsoft SQL Server as the BI Publisher scheduler database, using multibyte characters in the Schedule Report Job page might result in a garbled character display. To work around this issue, do not use multibyte characters in the Schedule Report Job submission page.

44.11.4.2 URL in E-mail Notification of Recurring or Future-Dated Jobs Might Fail to Display Job History for the Job

Impacted Releases: 11.1.1.6, 11.1.1.6.2, 11.1.1.7

During upgrade, the data in the 10g scheduler schema is migrated to the 11g scheduler schema. If a report was scheduled in 10g as a recurring job or as a future-dated job and the e-mail notification was set for this job for successful completion/completion with warning/failure, then, after upgrade, the e-mail notification View History URL still points to the 10g server. Clicking the URL in the notification fails to display job history for the job.

To work around this issue:

1. After invoking the browser to display the View History page, manually edit the server name and port in the browser address bar to point to the 11g environment and then press Enter.

2. Log in to the 11g server when prompted to view the report history.

44.11.4.3 After Editing an Existing Job, Immediately Creating a New Job Using "Submit as New" Overwrites the Original Job

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

This issue applies to the following scenario: You wish to edit an existing job and also create a new job based on the original job. To edit the existing schedule job you locate the job in the Manage Report Jobs page and click Edit. Then in the Schedule Report Job page you make the changes and click Submit. If you then immediately make additional edits and click Submit as New (to create the new job) the job that you just edited is no longer displayed in the Manage Report Jobs page.

To work around this issue: After editing the existing job and clicking Submit, then click Return. Choose the job again for editing, make your edits, and then click Submit as New to create the new job.

44.11.5 Oracle BI Publisher RTF Template Issues and Workarounds

This section describes issues and workarounds related to Oracle BI Publisher RTF templates. It includes the following topic:

- Section 44.11.5.1, "RTF Templates in 11g Require Number Conversion on String Expressions"

44.11.5.1 RTF Templates in 11g Require Number Conversion on String Expressions

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

The XPath expression in 10g RTF templates that uses XDK 10g allows automatic type conversion for number to string conversion and for string to number conversion. The XPath expression in 11g RTF templates that uses XDK 11g has disabled the automatic type conversion as per the W3C specifications of XSL 2.0. Therefore, expressions that worked in 10g might not work in 11g.

Example 1:

In 10g the following expression returns the expected results:

concat(((ceiling(substring(Order_Date,6,2) div 3) * 3) - 2), '/',   substring(Order_Date,1,4))

In 11g, this expression fails for the following reasons:

- The XPath "substring(Order_Date,6,2) div 3" is invalid in XSL 2.0 because the value from substring(...) is a string type, and the DIV operator cannot operate on a string value.

- The result of XPath "((ceiling(substring(Order_Date,6,2) div 3) * 3) - 2)" is a number type. The concat(...) function expects a list of string type parameters

To achieve the desired results in 11g, enter the following instead:

concat(string((ceiling(number(substring(Order_Date,6,2)) div 3) * 3) - 2),   '/', substring(Order_Date,1,4))

Example 2:

The following functions return a string data type and any calculation in 10g works on these functions:

xdoxslt:minimum(...)
xdoxslt:maximum(...)

In 11g, to perform a calculation on these functions, you must convert them into a number data type as follows:

number(xdoxslt:minimum(...))
number(xdoxslt:maximum(...))

44.11.6 Oracle BI Publisher Excel Template Issues and Workarounds

This section describes issues and workarounds related to Oracle BI Publisher Excel templates. It includes the following topic:

- Section 44.11.6.1, "Limitations for Excel Template Output on Apple iPad"

44.11.6.1 Limitations for Excel Template Output on Apple iPad

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Due to limitations with the native Excel reader on the Apple iPad, Excel template output documents have the following limitations when viewed on the iPad:

- Formulas intended to dynamically calculate in the output do not work

- Macros do not execute

- Pivot tables cannot be refreshed

- Hyperlinks do not work

- Workbook headers and footers are not displayed

- If using the Oracle Business Intelligence Mobile application on an iPad, the parameters do not show. However, if accessing the report via the Safari browser, the parameters are displayed.

44.11.7 Oracle BI Publisher Desktop Tools Issues and Workarounds

This section describes issues and workarounds related to Oracle BI Publisher desktop tools. It includes the following topics:

- Section 44.11.7.1, "Oracle BI Publisher's Template Builder for Microsoft Word Is Not Compatible with Microsoft Office Live Add-in"

44.11.7.1 Oracle BI Publisher's Template Builder for Microsoft Word Is Not Compatible with Microsoft Office Live Add-in

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Oracle BI Publisher´s Template Builder for Microsoft Word is not compatible with Microsoft Office Live Add-in. The presence of Microsoft Office Live Add-in might cause errors when attempting to install the Template Builder or other unexpected behavior.

To work around this issue, uninstall Microsoft Office Live Add-in.

44.11.8 Oracle BI Publisher Layout Editor Issues and Workarounds

This section describes issues and workarounds related to Oracle BI Publisher layout editor. It includes the following topics:

- Section 44.11.8.1, "Editing an XPT Layout and Clicking Return in Layout Editor Results in Exception"

- Section 44.11.8.2, "Interactive Viewer Might Return Unexpected Results from Formula Columns"

- Section 44.11.8.3, "Interactive Viewer Returns Incorrect Results for Data Aggregation Functions When the Data Set Is Not a Single, Flat Data Set"

- Section 44.11.8.4, "Division Results Rounded Inconsistently When Used with the #,##0 Custom Format Mask"

44.11.8.1 Editing an XPT Layout and Clicking Return in Layout Editor Results in Exception

Impacted Releases: 11.1.1.3, 11.1.1.5

When viewing a report using a layout that is not set as the Default Layout, and you select Edit Layout from the Report Viewer's action drop-down menu to open the layout in the layout editor, and then you click Return, you might encounter the following issue: The Report Viewer tries to open the report using the default output format (PDF, HTML, and so on) specified for the default layout. This might cause the report to fail with the following error if the default output format for the default layout is not one of the output formats allowed for the selected layout:

The report cannot be rendered because of an error, please contact the administrator. Error Detail oracle.xdo.servlet.data.DataException: Invalid format requested: html

44.11.8.2 Interactive Viewer Might Return Unexpected Results from Formula Columns

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

The Oracle JDBC driver does not contain a valid data type code for FORMULA columns in SQL. As a result, the data model shows these columns as INTEGER, even when the column is of another type.

The new interactive viewer engine introduced in 11.1.1.6 tries to convert the data to INTEGER. In most cases this results in "null" values for the formula data field (unless the INTEGER data type is appropriate). The new engine does not display any data for these values.

To work around this issue: In most cases switching to the backwards compatibility mode enables the interactive viewer to render the data.

To switch to backwards compatibility mode: Choose Edit Report and then click Properties. On the Properties dialog, click the Formatting tab and scroll down to the All Outputs group. Set Use 11.1.1.5 compatibility mode to True.

44.11.8.3 Interactive Viewer Returns Incorrect Results for Data Aggregation Functions When the Data Set Is Not a Single, Flat Data Set

Impacted Release: 11.1.1.6.0

This issue is fixed in release 11.1.1.6.2.

In the interactive viewer, data aggregation functions return an incorrect value when the base data set is not a single, flat data set. Note that other output types (HTML, PDF, and so on) are not affected.

To work around this issue: Switch to the backwards compatibility to render the correct results.

To switch to backwards compatibility mode: Choose Edit Report and then click Properties. On the Properties dialog, click the Formatting tab and scroll down to the All Outputs group. Set Use 11.1.1.5 compatibility mode to True.

44.11.8.4 Division Results Rounded Inconsistently When Used with the #,##0 Custom Format Mask

Impacted Releases: 11.1.1.5.0, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Division results for calculated columns created in Layout Editor are rounded inconsistently when the custom format mask #,##0 is applied to the column results. For example, 7/3 = 3.5 is rounded to 4. But 9/5 = 4.5 is rounded to 4.

44.11.9 Oracle BI Publisher Data Model Issues and Workarounds

This section describes issues and workarounds related to Oracle BI Publisher data models. It includes the following topics:

- Section 44.11.9.1, "Data Model Is Not Editable When Created by Upgrade Assistant"

- Section 44.11.9.2, "Issues with Upgraded 10g Data Models That Include Ref Cursors and Stored Procedures"

- Section 44.11.9.3, "After Editing a View Object Data Set, the Elements Are Duplicated"

- Section 44.11.9.4, "Excel Workbooks Used as Data Sources Cannot Contain Ampersand (&) in the Sheet Name"

44.11.9.1 Data Model Is Not Editable When Created by Upgrade Assistant

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

A report that is upgraded from Release 10g to 11g will have a report and a data model that are created by the Upgrade Assistant. The upgraded data model when seen in the data model editor will not show diagram, data structure and the equivalent code for the data structure. Moreover, the developer or administrator cannot edit the data structure. This means that the data model will not allow the developer or administrator to use the Release 11g features editable XML View and Business View.

The workaround is as follows:

1. Open the data model for editing.

2. Copy the SQL query statement from the data set.

3. Create a new data set in the same data model. The following warning is displayed:
"Adding this type of Data Set may break layouts that refer to this data model."

4. Click OK.

5. Paste the SQL query into the new data set dialog.

6. Enter a name for the dataset.

7. Click OK.

8. Delete the original data set. The following warning is displayed:
"This item is set as main dataset. Do you want to delete this item?"

9. Click OK.

10. Change the data structure in XML View to reflect ROWSET/ROW structure of XML.

11. Save the data model.

44.11.9.2 Issues with Upgraded 10g Data Models That Include Ref Cursors and Stored Procedures

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Data models in Release 10g that use ref cursors as a data source can be upgraded to Release 11g and continue to work; however, editing these data models is not supported. If you attempt to edit them, then they cease to work.

Data models in 10g that include stored procedures cannot be upgraded to 11g.

Fixes for both these issues are planned for a future release.

44.11.9.3 After Editing a View Object Data Set, the Elements Are Duplicated

Impacted Releases: 11.1.1.3, 11.1.1.5

This issue is fixed in 11.1.1.6.0.

In the data model editor if you edit a data set of the type View Object, then after you click OK, all the elements in the data set are duplicated.

To work around this issue, you must delete the data set and recreate it.

44.11.9.4 Excel Workbooks Used as Data Sources Cannot Contain Ampersand (&) in the Sheet Name

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Excel workbooks used as data sources for BI Publisher reports cannot contain the ampersand character (&) in the sheet name. If a sheet name in the Excel workbook includes an ampersand, when you attempt to load the workbook the sheet name list might appear empty or you might encounter an error when you attempt to upload the file.

To work around this issue, rename the sheet without the ampersand character.

44.11.10 Oracle BI Publisher Report Building Issues and Workarounds

This section describes issues and workarounds related to building reports with Oracle BI Publisher. It includes the following topics:

- Section 44.11.10.1, "Use Oracle BI Publisher Conversion Assistant to Convert Oracle Reports to Oracle BI Publisher 11g"

- Section 44.11.10.2, ""Enable Bursting" Report Property Displays Enabled State When Disabled"

44.11.10.1 Use Oracle BI Publisher Conversion Assistant to Convert Oracle Reports to Oracle BI Publisher 11g

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6, 11.1.1.6.2, 11.1.1.7

All releases of xxx can use the Oracle Reports to BI Publisher Conversion Assistant to convert Oracle Reports to Oracle BI Publisher xxx reports. See http://www.oracle.com/technetwork/middleware/bi-publisher/converttobip-1599273.html

for more information.

If you do not wish to use the Oracle Reports to BI Publisher Conversion Assistant, follow the two step process:

1. Convert the Oracle Reports report to an Oracle BI Publisher 10g report following the instructions in Oracle Business Intelligence Publisher Report Designer's Guide (10g):
http://download.oracle.com/docs/cd/E12844_01/doc/bip.1013/e12187/T518230T518393.htm

2. Upgrade Oracle BI Publisher 10g to Oracle BI Publisher 11g following the instructions in Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence 11g Release 1 (11.1.1).

44.11.10.2 "Enable Bursting" Report Property Displays Enabled State When Disabled

Impacted Releases: 11.1.1.5, 11.1.1.6, 11.1.1.6.2

When a report references a data model that includes a bursting definition, you can choose to enable a specific bursting definition for a report in the Report Properties dialog. If you choose to disable bursting by clearing the Enable Bursting check box, the check box is still displayed as enabled the next time that you open the Report Properties dialog. However, the actual state of the check box is disabled. You can verify the state by creating a schedule job for the report. If the Output tab of the Schedule Report Job page includes the option "Use Bursting Definition to Determine Output & Delivery Destination" then the report property is enabled. If this option is not visible, then the property is disabled.

If the Enable Bursting check box displays as enabled, but the actual state is disabled and you wish to re-enable bursting, clear the check box, then select it again, and click OK.

44.11.11 Oracle BI Publisher Documentation Errata

This section describes Oracle BI Publisher documentation errata. It includes the following topics:

- Section 44.11.11.1, "Oracle Fusion Middleware Report Designer's Guide for Oracle Business Intelligence Publisher"

- Section 44.11.11.2, "Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher"

44.11.11.1 Oracle Fusion Middleware Report Designer's Guide for Oracle Business Intelligence Publisher

This section describes documentation errata in Oracle Fusion Middleware Report Designer's Guide for Oracle Business Intelligence Publisher. It includes the following topics:

- Section 44.11.11.1.1, "Syntax Error in "Column Formatting" Section of the "Creating an RTF Template" Chapter"

- Section 44.11.11.1.2, "Required Location of ICC Profile Data File for PDF/X and PDF/A Output Incorrectly Documented"

- Section 44.11.11.1.3, "Support for Dynamic Links in Layout Editor Not Documented"

- Section 44.11.11.1.4, "Link to "Advanced Barcode Font Formatting" Points to Wrong Guide"

- Section 44.11.11.1.5, "Report Designer's Guide Incorrectly States Support for Hindi"

44.11.11.1.1 Syntax Error in "Column Formatting" Section of the "Creating an RTF Template" Chapter

Impacted Releases: 11.1.1.3, 11.1.1.5

In the "Creating an RTF Template" chapter, under the topic "Conditional Formatting," and subtopic "Column Formatting," the example contains a syntax error.

In the table that begins on page 74-68 of the PDF version of the book, the second "IF" statement entry (that precedes the entry "20") incorrectly shows the Form Field Entry as <?if@column:/items/@type="PRIVATE"?>

The correct entry is:

<?if@cell:/items/@type="PRIVATE"?>

44.11.11.1.2 Required Location of ICC Profile Data File for PDF/X and PDF/A Output Incorrectly Documented

Impacted Release: 11.1.1.6.0

BI Publisher includes a set of run-time properties to configure the new output types PDF/A and PDF/X. The PDF/X output type requires the setting of the property "PDF/X ICC Profile Data". For PDF/A, the setting of "PDF/A ICC Profile Data" is optional. The description of these properties in the "Setting Report Processing and Output Document Properties" chapter incorrectly states that the value of each property must be the path to the profile data file. Instead, the profile data file must be placed under <bi publisher repository>/Admin/Configuration and the value of the property must be the file name. Table 44-2 provides a detailed revision of the two required PDF/X properties: PDF/X ICC Profile Data and PDF/X output condition identifier.

Table 44-2 PDF/X Output Properties

Property Name

Description

PDF/X ICC Profile Data

Default: None

Description: (Required) The name of the ICC profile data file, for example: CoatedFOGRA27.icc.

The ICC (International Color Consortium) profile is a binary file describing the color characteristics of the intended output device. (For more information, see the article at http://en.wikipedia.org/wiki/ICC_profile). For production environments, the color profile might be provided by the print vendor or by the printing company that prints the generated PDF/X file. The file must be placed under <bi publisher repository>/Admin/Configuration.

Profile data is also available from Adobe (http://www.adobe.com/support) or colormanagement.org (http://www.colormanagement.org/).

Internal Name: pdfx-dest-output-profile-data

PDF/X output condition identifier

Default: None

Description: (Required) The name of one of the standard printing conditions registered with ICC (International Color Consortium). The list of standard CMYK printing conditions to use with PDF/X-1a is provided on the following ICC website: http://www.color.org/chardata/drsection1.xalter. The value that you enter for this property is a valid "Reference name," for example: FOGRA43.

Choose the appropriate value for the intended printing environment. This name is often used to guide automatic processing of the file by the consumer of the PDF/X document, or to inform the default settings in interactive applications.

Internal Name: pdfx-output-condition-identifier

For PDF/A output, if you choose to set the "PDF/A ICC Profile Data" property, the ICC profile data file must also be placed under <bi publisher repository>/Admin/Configuration and the value of the property must be the file name.

44.11.11.1.3 Support for Dynamic Links in Layout Editor Not Documented

Impacted Releases: 11.1.1.6.0

In the "Creating BI Publisher Layout Templates" chapter, the procedure for adding a dynamic hyperlink to a field in a table column is not documented.

To add a dynamic hyperlink a table column:

1. Select the table column.

2. Click Properties. The column properties include an option to enter a URL.

3. In the URL field, enter the static portion of the URL and embed the absolute path to the element that provides the dynamic portion of the URL within curly braces {}. For example:
http://example.com/show_page?id={/DATA/GROUP1/ELEMENT_NAME}

where http://example.com/show_page?id= is the static portion of the URL and {/DATA/GROUP1/ELEMENT_NAME} is the absolute path to the element in the data that supplies the dynamic portion.

44.11.11.1.4 Link to "Advanced Barcode Font Formatting" Points to Wrong Guide

Impacted Releases: 11.1.1.5, 11.1.1.6.0

In the "Creating RTF Templates" chapter, the section "Implementing Custom Barcode Formats" incorrectly states that the topic "Advanced Barcode Font Formatting" is found in the Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher. The topic is instead found in the Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Publisher.

44.11.11.1.5 Report Designer's Guide Incorrectly States Support for Hindi

Impacted Releases: 11.1.1.7

Section 15.1.3, "About Supported Languages" of the E22254-03 version of the Report Designer's Guide states:

"BI Publisher does support Arabic and Hindi."

The statement should read:

"BI Publisher does support Arabic and Hebrew."

BI Publisher does not support Hindi in this release.

44.11.11.2 Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher

This section describes documentation errata in Oracle Fusion Middleware Administrator's and Developer's Guide for Oracle Business Intelligence Publisher.

There are no known issues at this time.

44.12 Oracle Business Intelligence Metadata Repository Development Issues and Workarounds

This section describes issues and workarounds related to developing Oracle Business Intelligence metadata repositories. It includes the following topics:

- Section 44.12.1, "General Metadata Repository Development Issues and Workarounds"

- Section 44.12.2, "Oracle BI Server Issues and Workarounds"

- Section 44.12.3, "Oracle BI Administration Tool Issues and Workarounds"

44.12.1 General Metadata Repository Development Issues and Workarounds

This section describes general issues and workarounds related to developing Oracle Business Intelligence metadata repositories. It includes the following topics:

- Section 44.12.1.1, "Use of NQClient (BI ODBC Client) Utility Is Deprecated"

- Section 44.12.1.2, "Update Logical Table Source Modeling when Using paint.rpd for Testing"

- Section 44.12.1.3, "FIRST and LAST Aggregation Rules Cause Inconsistent Sorting for Time Dimensions"

- Section 44.12.1.4, "Oracle OLAP Jars on JavaHost Computer Must Be Updated When Using Oracle OLAP 11.2.x"

- Section 44.12.1.5, "Using the BIServerT2PProvisioner.jar Utility to Change Connection Pool Passwords"

- Section 44.12.1.6, "Configuring a Servlet for Oracle BI Server Communication with Oracle OLAP"

- Section 44.12.1.7, "Enhancing Performance of Aggregates with TimesTen Release 11.2.2.3 or Later"

- Section 44.12.1.8, "Performing Merges on Repositories That Contain System-Generated Tables Can Cause Loss of Metadata"

- Section 44.12.1.9, "Create Aggregates Operations Can Time Out for TimesTen Targets"

- Section 44.12.1.10, "Logical Display Folders Are Deleted During MUD Publish"

44.12.1.1 Use of NQClient (BI ODBC Client) Utility Is Deprecated

Impacted Releases: 11.1.1.5

The NQClient (BI ODBC Client) utility was fully deprecated in Release 11g (11.1.1.3) and should not be used. Instead, use the nqcmd utility or one of the many widely available third-party ODBC/JDBC tools to satisfy previous NQClient functionality.

44.12.1.2 Update Logical Table Source Modeling when Using paint.rpd for Testing

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

In paint.rpd, aggregated data at different levels is stored in the same fact table, which means that the same physical fact table is mapped to the logical table at different levels. To ensure that only rows from one level are returned, WHERE clause filters such as LEVELX = 'MONTH' or LEVELX = 'YEAR' exist in the logical table sources.

In releases prior to Oracle BI EE 11g Release 1 (11.1.1.3), if two logical table sources for the same logical table were mapped to the same physical table, and both logical table sources were used in a query, and both logical table sources had a WHERE clause filter, then the filter from only one of the logical table sources was applied. The other WHERE clause filter was ignored.

Starting with Oracle BI EE 11g Release 1 (11.1.1.3), in this situation, the WHERE clause filters from both logical table sources are applied to the query. Because of this, when paint.rpd queries select attributes from multiple levels, then the query hits multiple logical table sources, and the WHERE clause filters added to the query contradict one another. For example, the following condition is always false because LEVELX cannot be both MONTH and YEAR at the same time:

T863.LEVELX = 'MONTH' and T863.LEVELX = 'YEAR'

If you use paint.rpd for testing, then use one of the following methods to correct the modeling:

- Use physical table aliases to ensure that the same physical table is not mapped to the logical table at different levels.

- Disable the higher-level logical table source so that the query hits only the detailed logical table source.

Note that paint.rpd is not optimized for this release of Oracle BI EE and should not be used as a basis for any repositories in production environments. Consider using SampleApp.rpd instead. You can find the full version of SampleApp.rpd at:

http://oracle.com/technetwork/middleware/bi-foundation/obiee-samples-167534.html

44.12.1.3 FIRST and LAST Aggregation Rules Cause Inconsistent Sorting for Time Dimensions

Impacted Releases: 11.1.1.3, 11.1.1.5

The FIRST and LAST aggregation rules always use the primary level key to determine the sort order of the dimension members. This might cause inconsistent sort order for time dimensions, because the primary level key is used for the sort rather than the chronological key.

To work around this issue, specify the same column used for the chronological key as the primary level key.

44.12.1.4 Oracle OLAP Jars on JavaHost Computer Must Be Updated When Using Oracle OLAP 11.2.x

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

Currently, Oracle BI EE includes the 11.1.x version of the OLAP API jar file (olap_api.jar). If you are using Oracle OLAP version 11.2.x as a data source for Oracle BI EE, you must update the OLAP API jar file on all computers running the JavaHost process to version 11.2.x.

To update the olap_api.jar file used by Oracle Business Intelligence Enterprise Edition to version 11.2.x:

1. Back up the current olap_api.jar file used by Oracle Business Intelligence Enterprise Edition at:

ORACLE_BI_EE_HOME/bifoundation/javahost/lib/obisintegration/aw/11g

2. Copy the olap_api.jar file from the Oracle Database home at:

ORACLE_DB_HOME/product/11.2.0/dbhome_1/olap/api/lib

3. Paste the copied jar to the Oracle BI EE location:

ORACLE_BI_EE_HOME/bifoundation/javahost/lib/obisintegration/aw/11g

As an alternative to performing the steps in this section, you can configure the Oracle BI Server to use a servlet for Oracle OLAP communication instead of the JavaHost. See Section 44.12.1.6, "Configuring a Servlet for Oracle BI Server Communication with Oracle OLAP" for more information.

44.12.1.5 Using the BIServerT2PProvisioner.jar Utility to Change Connection Pool Passwords

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When moving the Oracle BI repository from test to production (T2P), you often need to change connection pool information for data sources, because the connection information in test environments is typically different from the connection information in production environments.

Connection pool passwords are encrypted and stored inside the encrypted repository file. Because of this, plain-text passwords must first be encrypted before they can be applied to an Oracle BI repository.

You can use the BIServerT2PProvisioner.jar utility to programmatically change and encrypt connection pool passwords in a repository. Note that the utility only works with repositories in RPD format; you cannot use the utility with MDS XML-format repositories. In addition, the utility requires JDK 1.6.

To use the BIServerT2PProvisioner.jar utility to change connection pool passwords:

1. Download patch 13093027 to obtain BIServerT2PProvisioner.jar. See Section 44.1.1, "Obtaining Patches from My Oracle Support" for more information about downloading patches.

2. Copy BIServerT2PProvisioner.jar into the ORACLE_HOME/bifoundation/server/bin directory on the computer where the Oracle BI Server is running.

3. Run bi-init to launch a command prompt or shell window that is initialized to the Oracle instance. You can find bi-init in:

ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreapplication/setup

See "Running bi-init to Launch a Shell Window Initialized to Your Oracle Instance" in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition for more information.

4. Run BIServerT2PProvisioner.jar using the -generate option to generate a template file where you can input the new passwords, as follows:

java -jar ORACLE_HOME/bifoundation/server/bin/BIServerT2PProvisioner.jar -generate repository_name -output password_file

Where:

repository_name is the name and path of the Oracle BI repository that contains the connection pools for which you want to change passwords.

password_file is the name and path of the output password text file. This file contains the connection pool names from the specified repository.

Then, enter the repository password when prompted.

For example:

java -jar BIServerT2PProvisioner.jar -generate original.rpd –output
inputpasswords.txt
Enter the repository password: My_Password

5. Edit the password file to replace <Change Password> with the updated password for each connection pool. A sample password file might contain text such as following:

"SQLDB_UsageTracking"."UTCP" = <Change Password>
"SQLDB_Data"."Db Authentication Pool" = <Change Password>

Tip: Ensure that you edit only the text to the right of the equals sign. If you change the text to the left of the equals sign, then the syntax for the connection pool names is incorrect.

Save and close the password file when your edits are complete.

6. Run BIServerT2PProvisioner.jar again with the -passwords option, as follows:

java -jar BIServerT2PProvisioner.jar -passwords password_file
-input input_repository -output output_repository

Where:

password_file is the name and path of the text file that specifies the connection pools and their corresponding changed passwords.

input_repository is the name and path of the Oracle BI repository where you want to apply the changed passwords.

output_repository is the name and path of the output repository that contains the updated passwords.

Then, enter the repository password when prompted.

For example:

java -jar BIServerT2PProvisioner.jar -passwords inputpasswords.txt -input
original.rpd -output updated.rpd
Enter the repository password: My_Password

7. Oracle does not recommend leaving clear-text passwords available on the system. Instead, either delete the input password file completely, or encrypt it so that it cannot be viewed.

44.12.1.6 Configuring a Servlet for Oracle BI Server Communication with Oracle OLAP

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2

You can optionally use a servlet for communication between the Oracle BI Server and Oracle OLAP data sources rather than relying on the JavaHost service. This approach avoids the issues described in the following sections:

- Section 44.12.1.4, "Oracle OLAP Jars on JavaHost Computer Must Be Updated When Using Oracle OLAP 11.2.x"

To deploy the biadminservlet for BI Server/Oracle OLAP communication:

1. Log on to the Oracle WebLogic Server Administration Console at:

http://weblogic_server_host:port/console

2. In the Change Center, click Lock & Edit.

3. Click Deployments in the Domain Structure window.

4. Click Install.

5. Select the biadminservlet.war file at:

ORACLE_HOME/bifoundation/javahost/lib/obisintegration

6. Accept all the defaults on the subsequent screens and then click Finish.

7. In the Change Center, click Activate Changes.
Upon successful deployment, biadminservlet is displayed in the Deployments table.

8. Download patch 13085711 to obtain the Enable Servlet.reg file. See Section 44.1.1, "Obtaining Patches from My Oracle Support" for more information about downloading patches.

9. Save the Enable Servlet.reg file to the desktop, then double-click it. Confirm that you want to make changes to the registry.
This file enables the servlet in the Administration Tool. If the Administration Tool is open, you must restart it after performing this step.

10. In the Administration Tool, provide the URL of the servlet when importing from Oracle OLAP sources in the Select Data Source page of the Import Metadata Wizard. The name of the servlet is services. For example, enter a string similar to the following in the URL field:

http://localhost:9704/biadminservlet/services

Note that the servlet must be up and running in order to use it. If you receive an import error, then check the status of the servlet in the Administration Console. You can also refer to the Administration Server diagnostic log and the Domain log.

44.12.1.7 Enhancing Performance of Aggregates with TimesTen Release 11.2.2.3 or Later

Impacted Releases: 11.1.1.6.2

The Oracle BI Server includes performance enhancements for creating aggregates in TimesTen Release 11.2.2.3. If the repository uses TimesTen Release 11.2.2.3 or later as the target database for creating aggregates, then you can use the following features to improve its performance:

- Disable Redo Logging

- Create Indexes in Parallel

- Perform database checkpoints in the background

To enable these features:

1. Open opmn.xml for editing. You can find opmn.xml at:

ORACLE_INSTANCE/config/OPMN/opmn/opmn.xml

2. Locate the ias-component tag for the Oracle BI Server process. For example:

<ias-component id="coreapplication_obis1" inherit-environment="true>

3. Under the <environment> subtag, update the following TimesTen variables:

<variable id="ORACLE_BI_TT_DISABLE_REDO_LOGGING" value="1"/>
<!-- This disables redo-logging, enabling faster creation of aggregates.
'0' if you wish to disable this feature. -->
<variable id="ORACLE_BI_TT_PARALLEL_INDEX_CREATION" value="1"/>
<!-- This enables AggrPersist to create indexes in parallel, making
creation of aggregates faster. '0' if you wish to create TimesTen indexes
sequentially. -->
<variable id="ORACLE_BI_TT_BACKGROUND_CHECKPOINT_INTERVAL" value="10"/>
<!-- This changes how often TimesTen will flush its data to disk. If this
element is missing, the default is every 10 seconds. If explicitly set, it
will flush to disk every N seconds, 10 in this example. '0' will disable
background flushing. Enabling background flushing speeds up creation of
aggregates, by avoiding a large blocking flush at the end of the aggregate
creation process. -->

4. Save and close the file.

5. Restart OPMN.

6. Repeat these steps on each computer that runs the BI Server process. If you are running multiple BI Server instances on the same computer, then be sure to update the ias-component tag appropriately for each instance in opmn.xml (for example, ias-component id="coreapplication_obis1", ias-component id="coreapplication_obis2", and so on).

44.12.1.8 Performing Merges on Repositories That Contain System-Generated Tables Can Cause Loss of Metadata

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

Repository merge operations performed on repositories that contain system-generated physical tables, such as the physical tables created by the aggregate persistence engine, can cause loss of metadata on those objects. This loss of metadata can cause errors during subsequent aggregate persistence operations against the repository.

To avoid this issue, remove the aggregate tables from both the metadata and back-end databases using the Delete aggregates specification before performing repository merges. See Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition for more information about using the delete aggregates specification.

44.12.1.9 Create Aggregates Operations Can Time Out for TimesTen Targets

Impacted Releases: 11.1.1.6.2, 11.1.1.7

In Release 11.1.1.6.2, Bundle Patch 1, creating aggregates in TimesTen using a 'create aggregates' script can sometimes cause the process to run for a long time and produces an error. If this occurs, open nqquery.log and search for the key words 'Timed Out'. You might find an error message similar to the following:

[nQSError: 16001] ODBC error state: 08S01 code: 0 message: [TimesTen][TimesTen
11.2.2.3.0 CLIENT]Communication link failure. System call select() failed with OS
error 10060. This operation has Timed Out. Try increasing your ODBC timeout
attribute or check to make sure the target TimesTen Server is running.]]

This error usually occurs in one of the following two situations:

- You used SQL Developer to connect to the TimesTen database instance before starting the 'create aggregates' process.

- You ran many queries against TimesTen (using Oracle BI Presentation Services or nqcmd) before starting the 'create aggregates' process.

To work around this issue, perform the steps as described for each use case.

To resolve time-outs related to using SQL Developer:

1. In SQL Developer, in the Tools menu, select Preferences, then select Database, then select Advanced.

2. Select the AutoCommit option.

3. Shut down SQL Developer.

4. Delete the aggregates you have created. See "Troubleshooting Aggregate Persistence" in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition for more information on deleting aggregates.

5. Re-run the "create aggregates" script.

To resolve time-outs related to running many queries against TimesTen using Presentation Services or nqcmd:

1. Open the RPD in the Administration Tool in online mode.

2. Expand every TimesTen database in the Physical layer of the Oracle BI repository.

3. For each associated connection pool object, perform the following steps:

1. Right-click the connection pool and select Properties.

2. When asked to check out objects, select Yes.

3. On the General tab, deselect Enable connection pooling.

4. Select the Connection Scripts tab.

5. In the Execute on connect box, delete the following entries (and duplicates, if they exist):

call ttoptsetflag('rowlock',0)
call ttoptsetflag('tbllock',1)
call ttoptsetflag('mergejoin',0)
call ttoptsetflag('nestedloop',1)

6. In the Execute before query box, add the following four entries:

call ttoptsetflag('rowlock',0)
call ttoptsetflag('tbllock',1)
call ttoptsetflag('mergejoin',0)
call ttoptsetflag('nestedloop',1)

7. In the Execute after query box, add the following single entry:

commit;

Be sure to repeat steps a through g for every TimesTen connection pool in the RPD.

4. Select File, then select Check In Changes. When asked to check Global Consistency, select No.

5. Select File, then select Save.

6. Still in the Administration Tool, for every connection pool object associated with a TimesTen database, perform the following steps:

1. Right-click the connection pool and select Properties.

2. When asked to check out objects, select Yes.

3. On the General tab, select Enable connection pooling.

Be sure to repeat steps a through c for every TimesTen connection pool in the RPD.

7. Select File, then select Check In Changes. When asked to check Global Consistency, select No.

8. Select File, then select Save.

9. Open opmn.xml for editing. You can find this file at:

ORACLE_INSTANCE/config/OPMN/opmn/opmn.xml

10. Locate the ias-component tag for the Oracle BI Server process. For example:

<ias-component id=" coreapplication_obis1">

11. Under the environment tag, insert the following element:

<variable id="TIMESTEN_DISABLE_CONNECITONPOOL_HINT" value="1"/>

Note: The misspelling in the id argument is intentional.

12. Save and close the file.

13. Delete the aggregates you have created. See "Troubleshooting Aggregate Persistence" in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition for more information on deleting aggregates.

14. Re-run the "create aggregates" script.

44.12.1.10 Logical Display Folders Are Deleted During MUD Publish

Impacted Release: 11.1.1.7

When a developer working in a multiuser development (MUD) environment publishes changes involving the business model into the master repository, the logical display folders in the Business Model and Mapping layer are deleted.

There is no workaround for this issue.

44.12.2 Oracle BI Server Issues and Workarounds

This section describes issues and workarounds related to the Oracle BI Server.

It includes the following topics:

- Section 44.12.2.1, "Configuration Required for Microsoft SQL Server and Oracle BI Summary Advisor"

44.12.2.1 Configuration Required for Microsoft SQL Server and Oracle BI Summary Advisor

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2

When using Microsoft SQL Server with Oracle BI Summary Advisor, you must perform the proper configuration to connect from Oracle BI to the Microsoft SQL Server database.

To configure Microsoft SQL Server with Oracle BI Summary Advisor:

1. In the Physical layer of the Administration Tool, double click the Microsoft SQL Server database's connection pool.

2. In the Connection Pool dialog, select Require fully qualified table names.

3. Save the changes and close the dialog.

4. In the Physical layer, double-click the database.

5. In the Database dialog, click the Features tab.

6. In the Features tab, locate the NESTED_ORDERBY_SUPPORTED feature and disable it by deselect its Value option.

7. Save the changes and close the dialog.

8. Open the odbc.ini file. You can find this file at:
ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreapplication/setup/odbc.ini

9. Locate the SQLSERVER_DB entry and modify it as follows:

- If you are using the DataDirect 5.3 driver, then set QuoteID=Yes

- If you are using the DataDirect 7.0.1 driver, then set EnableQuotedIdentifiers=1

10. Save and close the odbc.ini file.

44.12.3 Oracle BI Administration Tool Issues and Workarounds

This section describes issues and workarounds related to the Oracle BI Administration Tool. It includes the following topics:

- Section 44.12.3.1, "Administration Tool Incorrectly Displays Option for Generate Deployment File"

- Section 44.12.3.2, "Issue with Online Import Object Checkout"

- Section 44.12.3.3, "Ignore RPD Consistency Warnings Related to Required Database Feature Changes for Oracle OLAP"

- Section 44.12.3.4, "Select Nullable Option for Root Member of Parent-Child Hierarchies from OLAP Sources"

- Section 44.12.3.5, "Oracle BI Repository Can Become Corrupt When Objects Are Deleted in MUD Environments"

- Section 44.12.3.6, "Model Checker Not Enabled in Release 11.1.1.6.2"

- Section 44.12.3.7, "Publishing a Duplicate Dimension Object in a MUD Environment"

44.12.3.1 Administration Tool Incorrectly Displays Option for Generate Deployment File

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

The Administration Tool provides an option in the Tools > Utilities window for Generate Deployment File. This option is displayed in error and should not be used.

44.12.3.2 Issue with Online Import Object Checkout

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When using the Administration Tool to import objects in online mode, related objects are not properly checked out. This can lead to repository corruption.

The workaround is to check out all objects before performing the import in online mode. To check out all objects, from the menu bar, select Tools, then select Check Out All.

44.12.3.3 Ignore RPD Consistency Warnings Related to Required Database Feature Changes for Oracle OLAP

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When using Oracle OLAP as a data source, the database type is set to Oracle 11g. However, Oracle OLAP data sources might require changes to the default set of database features for Oracle 11g, such as setting ISDESCENDANT_SUPPORTED to YES to enable parent-child hierarchies.

When the set of database features is changed from the default set, RPD consistency warnings occur when running the Consistency Checker. These warnings should be ignored.

44.12.3.4 Select Nullable Option for Root Member of Parent-Child Hierarchies from OLAP Sources

Impacted Releases: 11.1.1.5

For parent-child hierarchies in the Physical layer from OLAP data sources, you must manually select the Nullable option in the Physical Cube Column dialog for the root member. This option must be selected for the root member for parent-child hierarchies (also called value-based hierarchies) to work correctly.

Alternatively, you can download and apply patch 12897870 as an alternative to manually setting the Nullable option. See Section 44.1.1, "Obtaining Patches from My Oracle Support" for more information about downloading patches.

44.12.3.5 Oracle BI Repository Can Become Corrupt When Objects Are Deleted in MUD Environments

Impacted Releases: 11.1.1.6.0

If you use the multiuser development (MUD) environment, be aware that an issue has been identified that causes the Oracle BI repository to become corrupt when MUD objects are deleted. The corruption manifests itself as crashes during consistency checks and when certain utilities are run, such as extractprojects.

To resolve this issue, download and apply patch 13560202. See Section 44.1.1, "Obtaining Patches from My Oracle Support" for more information about downloading patches.

44.12.3.6 Model Checker Not Enabled in Release 11.1.1.6.2

Impacted Releases: 11.1.1.6.2

This issue is fixed in Release 11.1.1.6.2, Bundle Patch 1.

Although the Model Checker Manager dialog is visible in the Oracle BI Administration Tool and described in the documentation, Model Check Manager is not enabled in 11.1.1.6.2.

44.12.3.7 Publishing a Duplicate Dimension Object in a MUD Environment

Impacted Releases: 11.1.1.6.2, 11.1.1.7

When a developer working in a multiuser development (MUD) environment performs a checkout that does not include a Dimension object in the master repository, there will be an issue if the developer subsequently creates the same Dimension object in the subset. When the developer publishes the changes, the existing Dimension object is overwritten with the newly created Dimension object. The correct behavior is for the system to publish a new Dimension object with "#1" appended to the name.

There is no workaround for this issue.

44.13 Oracle Business Intelligence System Administration Issues and Workarounds

This section describes issues and workarounds related to Oracle Business Intelligence system administration. It includes the following topics:

- Section 44.13.1, "General System Administration Issues and Workarounds"

- Section 44.13.2, "Configuration Issues and Workarounds"

- Section 44.13.3, "Deployment, Availability, and Capacity Issues and Workarounds"

- Section 44.13.4, "Sign-in and Security Issues and Workarounds"

- Section 44.13.5, "Oracle BI Scheduler Issues and Workarounds"

- Section 44.13.6, "Oracle Essbase Suite Issues and Workarounds"

Depending on your Oracle Fusion Middleware implementation, some information in Chapter 4, "Oracle Fusion Middleware Administration" and Chapter 5, "Oracle Enterprise Manager Fusion Middleware Control" might also be relevant.

44.13.1 General System Administration Issues and Workarounds

This section describes general issues and workarounds related to Oracle Business Intelligence system administration.

There are no known issues at this time.

44.13.2 Configuration Issues and Workarounds

This section describes issues and workarounds related to configuring Oracle Business Intelligence components (including Answers, Dashboards, Agents, and the Oracle BI Presentation Catalog). It includes the following topic:

- Section 44.13.2.1, "Removal of DefaultImageType and HardenXSS Elements"

44.13.2.1 Removal of DefaultImageType and HardenXSS Elements

Impacted Releases: 11.1.1.5

In Release 11.1.1.5, the following elements are no longer supported and should be removed from the instanceconfig.xml file:

- DefaultImageType element

- HardenXSS element

If the instanceconfig.xml file includes the HardenXSS element when a user starts Oracle BI EE, then an error message is displayed. The error log file states that startup was affected by the inclusion of the HardenXSS element.

The workaround is to remove the HardenXSS element from the instanceconfig.xml file.

44.13.3 Deployment, Availability, and Capacity Issues and Workarounds

This section describes issues and workarounds related to enterprise deployments of Oracle Business Intelligence where high availability, capacity, and performance are typically a priority.

These issues are described in Chapter 6, "Oracle Fusion Middleware High Availability and Enterprise Deployment" of this document.

44.13.4 Sign-in and Security Issues and Workarounds

This section describes issues and workarounds related to security and signing in to Oracle Business Intelligence.

Note:

If you are experiencing security-related issues after upgrading from an earlier release, then also refer to Section 44.6.2, "Security-related Upgrade Issues and Workarounds".

This section includes the following topic:

- Section 44.13.4.1, "Permission Required to Open Catalog Manager in Online Mode"

44.13.4.1 Permission Required to Open Catalog Manager in Online Mode

Impacted Releases: 11.1.1.5

Only users with the OPSS permission oracle.bi.presentation.catman.manageCatalog can open the Catalog Manager in online mode.

44.13.5 Oracle BI Scheduler Issues and Workarounds

This section describes issues and workarounds related to Oracle BI Scheduler.

There are no known issues at this time.

44.13.6 Oracle Essbase Suite Issues and Workarounds

This section describes issues and workarounds related to the system administration of Oracle Essbase Suite when installed as a component of Oracle Business Intelligence. For more information, see "Introduction to Using Oracle Essbase and Associated Components in Oracle Business Intelligence" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

This section contains the following topics:

- Section 44.13.6.1, "Ensure that the Installation Uses a JDK Installed into a Folder that Does Not Contain Spaces"

- Section 44.13.6.2, "Essbase SQL Interface Using Oracle Call Interface (OCI) to Connect to Oracle Requires Oracle Instant Client"

- Section 44.13.6.3, "Options to Set Accessibility Preferences When Using Workspace Are Not Available"

- Section 44.13.6.4, "Issue with Dashboards Menu in EPM Workspace"

- Section 44.13.6.5, "Merant 6.1 ODBC Drivers Are Not Configured on Linux"

44.13.6.1 Ensure that the Installation Uses a JDK Installed into a Folder that Does Not Contain Spaces

Impacted Releases: 11.1.1.7

Installing a Java JDK is a prerequisite for a Software Only install. The particular JDK to use is one of the selections when installing Oracle WebLogic Server prior to installing Oracle Business Intelligence. The same JDK is used by Essbase when installed with Oracle Business Intelligence. On Windows, the default path when installing Java is into the Program Files folder. This location causes an issue for Essbase installed with Oracle Business Intelligence due to the spaces in the folder name. Therefore, on all platforms, ensure that when performing a Software Only installation of Oracle Business Intelligence, you point to a Java JDK that is installed into a path that does not include spaces in the folder name.

44.13.6.2 Essbase SQL Interface Using Oracle Call Interface (OCI) to Connect to Oracle Requires Oracle Instant Client

Impacted Releases: 11.1.1.7

To enable you to use the Oracle Call Interface (OCI) to source data for Essbase, you must install the Oracle Instant Client and configure Essbase to use it.

To install the Oracle Instant Client and configure Essbase to use it:

1. Download and install Oracle Instant Client on the server where Essbase is installed with Oracle Business Intelligence.
For more information, see:

http://www.oracle.com/technetwork/database/features/instant-client/index-100365.html

2. Open the opmn.xml file for editing in the following location:
MW_HOME/instances/instancen/config/OPMN/opmn/opmn.xml

3. Add the install location of the Instant Client to the LD_LIBRARY_PATH (Linux) or PATH (Windows) as follows:

...
</ias-component><ias-component id="essbaseserver1">
<process-type id="Essbase" module-id="ESS">
<environment>
..
<variable append="true" id="LD_LIBRARY_PATH"
value="$HYPERION_HOME/common/ODBC/Merant/6.0/lib$:$ORACLE_HOME/bifoundation/server/bin$:Oracle_Home/jdk/jre/lib/amd64/server:$ESSBASEPATH/bin:/<Oracle Instant Client Install path>/instantclient_11_2"/>
<variable append="true" id="PATH" value="$ARBORPATH/bin$:$ESSBASEPATH/bin$:/<Oracle Instant Client Install path>/instantclient_11_2"/>
...

Replace <Oracle Instant Client Install path> with the path to the Oracle Instant Client.

4. Save the opmn.xml file.

44.13.6.3 Options to Set Accessibility Preferences When Using Workspace Are Not Available

Impacted Releases: 11.1.1.7

In order to view Workspace content in accessibility mode, add the accessibility parameter to the Workspace URL as follows:

http://<host>:<port>/workspace/index.jsp?accessibilityMode=true

44.13.6.4 Issue with Dashboards Menu in EPM Workspace

Impacted Releases: 11.1.1.7

When Oracle Business Intelligence Release 11.1.1.7 is integrated with EPM Workspace Release 11.1.2.2 or 11.1.2.3, you might find that the Dashboards menu fails when switching tabs in Workspace. To work around this issue, close and reopen the Dashboards tab in Workspace.

44.13.6.5 Merant 6.1 ODBC Drivers Are Not Configured on Linux

Impacted Releases: 11.1.1.7

After you install Oracle Business Intelligence 11.1.1.7, the Merant 6.1 drivers are not fully configured.

To use these drivers you must manually edit the associated odbc.ini file located in:

MW_HOME/Oracle_BI1/common/ODBC/Merant/6.1/odbc.ini

Update the <install_location> element with the appropriate location of the drivers.

44.14 Oracle Business Intelligence Integration and API Issues and Workarounds

This section describes issues and workarounds related to integrating Oracle Business Intelligence with other products, including the use of Oracle Business Intelligence APIs. It includes the following topics:

- Section 44.14.1, "General Integration Issues and Workarounds"

- Section 44.14.2, "Oracle Business Intelligence API Issues and Workarounds"

44.14.1 General Integration Issues and Workarounds

This section describes general issues and workarounds related to integrating Oracle Business Intelligence with other products.

There are no known issues at this time.

44.14.2 Oracle Business Intelligence API Issues and Workarounds

This section describes issues and workarounds related to the use of Oracle Business Intelligence APIs.

There are no known issues at this time.

44.15 Oracle Business Intelligence Localization Issues and Workarounds

This section describes issues and workarounds related to integrating Oracle Business Intelligence with other products, including the use of Oracle Business Intelligence APIs. It includes the following topics:

- Section 44.15.1, "Product Localization Issues and Workarounds"

- Section 44.15.2, "Help System Localization Issues and Workarounds"

44.15.1 Product Localization Issues and Workarounds

This section describes issues and workarounds related to the localization of Oracle Business Intelligence products. It includes the following topics:

- Section 44.15.1.1, "Unable to Save Strings with Multibyte Characters to an External File Using ANSI Encoding"

- Section 44.15.1.2, "BI Publisher User Interface Components Do Not Support Supplementary Characters"

- Section 44.15.1.3, "Non-English Log Files Displayed Incorrectly in Fusion Middleware Control"

- Section 44.15.1.4, "Error Messages in BI Publisher Data Model Editor Honor Server Locale Setting"

- Section 44.15.1.5, "Incorrect Layout in Tables and Pivot Tables in PDF Files and PowerPoint Presentations When Locale for BI Server Is Arabic or Hebrew"

- Section 44.15.1.6, "Excel2007 Output in BI Publisher Does Not Honor Locale Settings for Number and Date Format"

- Section 44.15.1.7, "Excel2007 Output in BI Publisher Supports Gregorian Calendar Only"

- Section 44.15.1.8, "Template Builder for Microsoft Word Chart Wizard Does Not Format Dates"

- Section 44.15.1.9, "Number and Date Format Issues with Charts in BI Publisher Layout Templates"

- Section 44.15.1.10, "BI Publisher Report Creation Wizard "Select Columns" Step Does Not Render Properly When UI Language Is Francais"

- Section 44.15.1.11, "Albany Fonts Delivered with BI Publisher for PDF Output Do Not Support Bold and Italic for Multibyte Characters"

44.15.1.1 Unable to Save Strings with Multibyte Characters to an External File Using ANSI Encoding

Impacted Releases: 11.1.1.5

When trying to export externalized strings that contain multibyte characters, the option to save the file using ANSI encoding does not work properly.

To work around this problem, save the file using UTF-8 or Unicode encoding.

44.15.1.2 BI Publisher User Interface Components Do Not Support Supplementary Characters

Impacted Releases: 11.1.1.3, 11.1.1.5

BI Publisher does not support supplementary characters in object names in the user interface, for example, report name, data model name, layout name, and so on. The data model editor does not support supplementary characters in SQL queries. The scheduler does not support supplementary characters in input fields such as e-mail subject and message fields.

To work around this issue, do not use supplementary characters in the BI Publisher user interface. If the database table and column names already include supplementary characters, then you cannot use the data model editor to retrieve the data from these.

44.15.1.3 Non-English Log Files Displayed Incorrectly in Fusion Middleware Control

Impacted Releases: 11.1.1.5

You might have log files for Presentation Services, Oracle BI Scheduler, and Cluster Controller that have been translated to languages other than English. You might find that the content of these log files is not displayed correctly in the Diagnostic Log table and in tooltips in Fusion Middleware Control.

To work around this issue, enter the following property for logreader in the component-logs.xml file in the ORACLE_INSTANCE/config directory:

<property name="encoding" value="UTF-8"/>

Add the property in the component-logs.xml file in the following subdirectories: OracleBIPresentationServicesComponent, OracleBISchedulerComponent, and OracleBIClusterControllerComponent.

44.15.1.4 Error Messages in BI Publisher Data Model Editor Honor Server Locale Setting

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Error messages invoked while working in the BI Publisher data model editor might display according to the server locale setting rather than the user interface locale setting.

This issue has no workaround.

44.15.1.5 Incorrect Layout in Tables and Pivot Tables in PDF Files and PowerPoint Presentations When Locale for BI Server Is Arabic or Hebrew

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

If the locale for the Oracle BI Server is Arabic or Hebrew, then no matter what the client locale for Presentation Services is, you notice the following issues with tables and pivot tables in PDF files and PowerPoint presentations:

- The printed layout for tables and pivot tables is always Right to Left.

- Digit glyphs (such as number/date values) are always displayed as Arabic characters for Arabic only.

To work around this issue, perform the following steps:

1. Update the opmn.xml file in the following directory:
MWHOME/instances/instance1/config/OPMN/opmn/opmn.xml

2. Locate the XML node called <ias-component id="coreapplication_obijh1">.
The node should contain an XML node called

<process-type id="OracleBIJavaHostComponent" module-id="CUSTOM">

3. Under this process-type node, modify the value attribute of the node:
<data id="start-args" value="-server...

Add the following to the value attribute:

-Duser.language=en -Duser.region=US

4. Save your changes to the file and restart the JavaHost component.

44.15.1.6 Excel2007 Output in BI Publisher Does Not Honor Locale Settings for Number and Date Format

Impacted Releases: 11.1.1.5

The Excel2007 output format does not honor locale settings for some number and date fields coded to be locale-sensitive in the layout template.

44.15.1.7 Excel2007 Output in BI Publisher Supports Gregorian Calendar Only

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

The following calendars are not supported for Excel 2007 output format. The report output reverts to use the GREGORIAN calendar.

- ARABIC_HIJRAH

- ENGLISH_HIJRAH

- JAPANESE_IMPERIAL

- THAI_BUDDHA

- ROC_OFFICIAL (Taiwan)

44.15.1.8 Template Builder for Microsoft Word Chart Wizard Does Not Format Dates

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When you drag and drop a date type value (for example: "1900-12-31T14:15:16.178-04:00") to the label of a chart, the value is not formatted according to the locale setting; instead, the value displays as given (that is, 1900-12-31T14:15:16.178-04:00").

To work around this issue, format the date in the data model; or, if you are familiar with XSL-T, manually change the date field using the function, for example: xdoxslt:xdo_format_date($_XDOXSLTCTX, (.//date)[1], 'MEDIUM')

44.15.1.9 Number and Date Format Issues with Charts in BI Publisher Layout Templates

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

When editing a BI Publisher layout template, if you add a number type column to the y-axis of a chart (for example, a vertical bar chart), the number format does not reflect the UI language. At runtime, the proper locale is displayed in the Report Viewer.

When you add a date column to the x-axis, the raw data is displayed in the chart (that is, no format is applied at all). At run time, the date does respect the report locale for output types other than interactive and PowerPoint.

44.15.1.10 BI Publisher Report Creation Wizard "Select Columns" Step Does Not Render Properly When UI Language Is Francais

Impacted Release: 11.1.1.6.0, 11.1.1.6.2

When the UI language setting is Francais, the Report Creation Wizard dialog for the step "Select Columns" does not render the navigation buttons properly. To work around this issue, at Step 2 of the Report Creation Wizard, select Use Report Editor to bypass the Select Columns step.

44.15.1.11 Albany Fonts Delivered with BI Publisher for PDF Output Do Not Support Bold and Italic for Multibyte Characters

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Bold and italic for multibyte characters (for example, Simplified Chinese, Traditional Chinese, Japanese and Korean) do not display well in PDF output. This is because the Albany fonts delivered with BI Publisher do not support bold and italic for multibyte characters.

To work around this issue, install a font that does support the required emphasis (for example, the bold Japanese font Meiryo Bold (meiryob.ttc)). Then use BI Publisher font mapping to map the font so BI Publisher can find it at run time. For more information about font mapping, see "Defining Font Mappings" in the Oracle Fusion Middleware Report Designer's Guide for Oracle Business Intelligence Publisher.

44.15.2 Help System Localization Issues and Workarounds

This section describes issues and workarounds related to the localization of Oracle Business Intelligence help systems. It includes the following topic:

- Section 44.15.2.1, "Oracle Business Intelligence Help Systems Are Not Translated"

44.15.2.1 Oracle Business Intelligence Help Systems Are Not Translated

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

In Release 11.1.1.3 and Release 11.1.1.5, none of the Oracle Business Intelligence help systems are translated.

In Release 11.1.1.6.0 and 11.1.1.6.2, the following Oracle Business Intelligence help systems are translated:

- Oracle BI Presentation Services Online Help

- Oracle Marketing Segmentation Online Help

- Oracle BI Add-in for Microsoft Office Online Help

For details of the languages into which the help systems have been translated, refer to the Oracle Business Intelligence certification document at:

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

44.16 Oracle Business Intelligence Documentation Errata

This section describes errata in Oracle Business Intelligence documentation and help systems. It includes the following topics:

- Section 44.16.1, "General Oracle Business Intelligence Documentation Errata"

- Section 44.16.2, "Oracle Fusion Middleware Quick Installation Guide for Oracle Business Intelligence"

- Section 44.16.3, "Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence"

- Section 44.16.4, "Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence Enterprise Edition"

- Section 44.16.5, "Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition"

- Section 44.16.6, "Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Mobile"

- Section 44.16.7, "Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition"

- Section 44.16.8, "Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition"

- Section 44.16.9, "Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition"

- Section 44.16.10, "Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence"

- Section 44.16.11, "Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition"

- Section 44.16.12, "Oracle Fusion Middleware Integrator's Guide for Oracle Business Intelligence Enterprise Edition"

- Section 44.16.13, "Oracle Fusion Middleware XML Schema Reference for Oracle Business Intelligence Enterprise Edition"

- Section 44.16.14, "Oracle Business Intelligence Help System Errata"

44.16.1 General Oracle Business Intelligence Documentation Errata

This section describes general errata in the Oracle Business Intelligence documentation.

There are no known issues at this time.

44.16.2 Oracle Fusion Middleware Quick Installation Guide for Oracle Business Intelligence

This section describes documentation errata in Oracle Fusion Middleware Quick Installation Guide for Oracle Business Intelligence.

There are no known issues at this time.

44.16.3 Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence

This section describes documentation errata in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence. It includes the following topics:

- Section 44.16.3.1, "Installation Guide Contains Misinformation About Installing the Client Tools"

- Section 44.16.3.2, "Installation Guide Contains Misinformation About pasteBinary Script"

- Section 44.16.3.3, "Installation Guide Contains Misinformation About Installing on a Hardened Database"

44.16.3.1 Installation Guide Contains Misinformation About Installing the Client Tools

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence (E10539-03).

Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence contains the following misinformation in regard to installing the Oracle Business Intelligence clients:

- Section 5.1.1, "About Oracle Business Intelligence Client Tools," states:
"32-bit versions of the Oracle Business Intelligence client tools are installed automatically when you install Oracle Business Intelligence on a computer running a 32- or 64-bit Windows operating system."

The previous statement incorrectly implies that the Oracle Business Intelligence xxx Installer always installs 32-bit versions of the client tools. Rather, 32-bit versions of the Oracle Business Intelligence xxx Installer install 32-bit versions of the client tools, while 64-bit versions of the Oracle Business Intelligence xxx Installer install 64-bit versions of the client tools.

- Section 5.1.2, "Considerations for Installing Oracle Business Intelligence Client Tools" states:
"The Oracle Business Intelligence Enterprise Edition Plus Client Installer installs 32-bit versions of the client tools."

The previous statement incorrectly implies that the Oracle Business Intelligence Enterprise Edition Plus Client Installer always installs all of the available client tools. Rather, it installs just two client tools—the Oracle Business Intelligence Administration Tool and Oracle Business Intelligence Job Manager. It does not install the Oracle Business Intelligence Catalog Manager. Only the Windows version of the Oracle Business Intelligence xxx Installer installs all three client tools.

Therefore, if you want or require the Oracle Business Intelligence Catalog Manager, you must install the client tools using the Oracle Business Intelligence xxx Installer, and not the Oracle Business Intelligence Enterprise Edition Plus Client Installer.

44.16.3.2 Installation Guide Contains Misinformation About pasteBinary Script

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2

Chapter 4 includes two sections "Considerations and Limitations of Enterprise Install Type for New Installations" and "Software Only Install" that include mention of the pasteBinary script not being supported with Oracle Business Intelligence installations that were installed on 64-bit operating systems using the Enterprise Installation type. This lack of support has been lifted and the script can be used in this case. Therefore, these mentions must be removed from the guide.

44.16.3.3 Installation Guide Contains Misinformation About Installing on a Hardened Database

Impacted Releases: 11.1.1.3, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Chapter 4, Section 4.1: Before You Install Oracle Business Intelligence, contains points to keep in mind before you install Oracle Business Intelligence. The seventh point in the list is to ensure that the database is not hardened for security purposes as installing Oracle Business Intelligence against a hardened database is no supported, which is incorrect. The point should read as follows:

Oracle does not support installing Oracle Business Intelligence against a hardened database. You can, however, harden the database after you install Oracle Business Intelligence. To enable RCU and Oracle Business Intelligence xxx Installer to connect to a hardened database, perform one of the following actions:

- Temporarily enable a non-encrypted port that is behind a firewall.

- Use network-level VPN or another secure network environment instead of the application-level secure sockets layer (SSL).

44.16.4 Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence Enterprise Edition

This section describes documentation errata in Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence. It includes the following topics:

- Section 44.16.4.1, "Incorrect Information on Aggregation"

- Section 44.16.4.2, "Incorrect Information on Database Authentication"

44.16.4.1 Incorrect Information on Aggregation

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

This issue is fixed in Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence (E10541-06).

Appendix B includes a table that describes possible changes with Oracle BI EE content after an upgrade from 10g to 11g. One row in the table describes a change to the aggregate rule for running aggregates after upgrade. The row states the following:

RSUM(), RCOUNT() = Aggregation Rule: Sum

which is incorrect. The line should read as follows:

RSUM(), RCOUNT() = Aggregation Rule: Max

44.16.4.2 Incorrect Information on Database Authentication

Impacted Releases: 11.1.1.7.0, 11.1.1.7.1, and 11.1.1.7.10

This issue is fixed in Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence (E16452-08).

Chapter 5 section 5.5.1 "Before Running Upgrade Assistant" step 2 mentions that if you used the nqsconfig.ini file parameter AUTHENTICATION_TYPE = DATABASE in the 10g system for database authentication, then you must copy it to the 11g version of the file. This is incorrect as 11g does not support database authentication using nqsconfig.ini.

Step 2 should read as follows:

If you configured the nqsconfig.ini file in the 10g system for database authentication, then in the 11g system you must follow the instructions in "Configuring an Oracle Database as the Security Store"in the Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.

44.16.5 Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition

This section describes documentation errata in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition. It includes the following topics:

- Section 44.16.5.1, "Oracle BI Mobile: Embedding a Dashboard or Answers Report Link in an E-mail"

- Section 44.16.5.2, "Oracle BI Mobile: Easy Access to Dashboards"

- Section 44.16.5.3, "Information about Oracle Hyperion Smart View for Office Must Be Ignored"

- Section 44.16.5.4, "Columns from Multiple Subject Areas Included in a Single Query Must Be Compatible"

- Section 44.16.5.5, "Error in the "How Will Prompts Created in Previous Versions Be Upgraded?" Topic in Chapter 6, "Prompting in Dashboards and Analyses""

- Section 44.16.5.6, "Content Missing from Appendix E, "User Interface Reference," "Edit Page Settings dialog" Topic, Prompt Buttons Field"

- Section 44.16.5.7, "Incorrect Default Pixel Value Specified in Chapter 6, "Prompting in Dashboards and Analyses" and Appendix E, "User Interface Reference""

- Section 44.16.5.8, "Error in the "Actions that Invoke Operations, Functions or Processes in External Systems" Topic in Chapter 10, "Working with Actions""

- Section 44.16.5.9, "Error in the "Show More Columns dialog" Topic in Appendix E, "User Interface Reference""

- Section 44.16.5.10, "Error in the "New Filter dialog" Topic in Appendix E, "User Interface Reference""

- Section 44.16.5.11, "Information on View Latest Version Feature in Error"

- Section 44.16.5.12, "Changes to the Instructions for Installing and Configuring BI Composer"

- Section 44.16.5.13, "Mentions of the KPI Editor: Data Input Security Page Must Be Ignored"

- Section 44.16.5.14, "Breadcrumbs Disabled for Embedded Objects in ADF"

- Section 44.16.5.15, "Note on Fixed Headers with Scrolling Content Is Incorrect"

- Section 44.16.5.16, "Misinformation About Adding HTML Code in Prompt Labels"

- Section 44.16.5.17, "Enable on Totals for Action Links Not Described"

- Section 44.16.5.18, "Use of Multiple Values in Presentation Variable on Dashboards Not Described"

44.16.5.1 Oracle BI Mobile: Embedding a Dashboard or Answers Report Link in an E-mail

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Mobile (E25318-02).

The Oracle Business Intelligence Mobile application allows you to e-mail a link to the BI content you are viewing. When viewing an Answers report or a dashboard page, tap the Email icon to launch an e-mail window; a link to the Answers report or Dashboard is then embedded in the body of the e-mail.

On the iPad, the Email icon is displayed at the bottom of the Oracle BI Mobile application. On the iPhone, tap the Actions icon to access the Email icon.

This feature works only if you have set up an e-mail account on the iPhone or iPad device.

44.16.5.2 Oracle BI Mobile: Easy Access to Dashboards

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Mobile (E25318-02).

When you tap the Catalog icon in the Oracle Business Intelligence Mobile application on the iPad or iPhone, you see two tabs at the top of the screen: a Catalog tab and a Dashboards tab. Tap the Dashboards tab to display a list of top-level dashboards you have access to. This list is identical to the list of dashboards you see when logged into Oracle BI EE with the desktop application.

44.16.5.3 Information about Oracle Hyperion Smart View for Office Must Be Ignored

Impacted Releases: 11.1.1.5, 11.1.1.6.0

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-04).

Various sections of Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition include mention of Oracle Hyperion Smart View for Office. All mentions of Smart View must be ignored, as described in Section 44.4.2, "Oracle Hyperion Smart View for Office Not Supported in Oracle Business Intelligence 11g, Releases 11.1.1.5, 11.1.1.6.0, and 11.1.1.6.2."

44.16.5.4 Columns from Multiple Subject Areas Included in a Single Query Must Be Compatible

Impacted Releases: 11.1.1.3, 11.1.1.5

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-03).

The following additional information is available for the topic "What Are Subject Areas and Columns?" in Chapter 2, "Creating Analyses:"

Typically, when you query a single subject area, all the columns exposed in that subject area are compatible with all the dimensions exposed in the same subject area. However, when you combine columns and dimensions from multiple subject areas, you must ensure that you do not include combinations of columns and dimensions that are incompatible with one another.

For example, a column in one subject area might not be dimensioned by Project. If columns from the Project dimension from another subject area are added to the request along with the columns that are not dimensioned by Project, then the query might fail to return results, or cause the Oracle BI Server error "No fact table exists at the requested level of detail: XXXX."

44.16.5.5 Error in the "How Will Prompts Created in Previous Versions Be Upgraded?" Topic in Chapter 6, "Prompting in Dashboards and Analyses"

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-03).

The "How Will Prompts Created in Previous Versions Be Upgraded?" topic in Chapter 6, "Prompting in Dashboards and Analyses" contains an incorrect reference to the Text Field Width field. This topic should instead reference the Choice List Value field. The revised paragraph should read as follows:

The Choice List Value field located in the "New Prompt dialog" is set by default to 120 pixels. Note that this value is different if the Administrator modified the default pixel value in the Oracle BI EE configuration file.

44.16.5.6 Content Missing from Appendix E, "User Interface Reference," "Edit Page Settings dialog" Topic, Prompt Buttons Field

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-03).

Information that describes the Prompt Buttons field is missing from the "Edit Page Settings dialog" topic. The following paragraph includes information about the field:

Prompt Buttons

Use this field to specify if you want the Apply and Reset buttons to display beside the prompt field or above the prompt field.

44.16.5.7 Incorrect Default Pixel Value Specified in Chapter 6, "Prompting in Dashboards and Analyses" and Appendix E, "User Interface Reference"

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-03).

In the "How Will Prompts Created in Previous Versions Be Upgraded?" topic in Chapter 6, "Prompting in Dashboards and Analyses," the default pixel value specified for the Choice List Width field and for the Set width of all prompts to field is incorrect. The default pixel value is 120, not 250.

In Appendix E, "User Interface Reference," the default pixel value specified for the Choice List Width field in the "New Prompt dialog" topic and for the Set width of all prompts to field in the "Edit Page Settings" dialog is incorrect. The default pixel value is 120, not 250.

44.16.5.8 Error in the "Actions that Invoke Operations, Functions or Processes in External Systems" Topic in Chapter 10, "Working with Actions"

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-03).

The "Actions that Invoke Operations, Functions, or Processes in External Systems" topic in Chapter 10, "Working with Actions" includes a Note referencing the USERSCRIPT.ADFAction function. This Note, which is included in the bullet that describes the Invoke a Browser Script action, is in error. The USERSCRIPT.ADFAction function is not supported in this release.

44.16.5.9 Error in the "Show More Columns dialog" Topic in Appendix E, "User Interface Reference"

Impacted Releases: 11.1.1.3, 11.1.1.5

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-03).

The definitions of Variance and % Variance in Table E-7, Commonly Used KPI Data Columns in the "Show More Columns dialog" topic in Appendix E, "User Interface Reference" contain an error and need to be corrected (the example variance should be -50,000, not 50,000 and the example % variance should be -7.7%, not 7.7%).

The definitions should read as follows:

- Variance: Displays the value by which the KPI's actual value differs from its target value. For example if the actual value for a Net Profit KPI is 600,000 and its target is 650,000, then the variance is -50,000.

- % Variance: Displays the percent by which the KPI's actual value differs from its target value. For example if the actual value for a Net Profit KPI is 600,000 and its target is 650,000, then the variance as a percent is -7.7%

44.16.5.10 Error in the "New Filter dialog" Topic in Appendix E, "User Interface Reference"

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-03).

The "New Filter dialog" topic requires the following corrections: The topic states that if the repository is configured for double columns, then you can specify to display code values if you use the "is between" operator. This statement is incorrect. You cannot display or select code values nor can you filter by code values with the "is between" operator. You can display, select, and filter by only display values with that operator.

The topic includes mention of the Select by Code Column and Filter by Code Column fields. These fields are not available with the "is between" operator.

44.16.5.11 Information on View Latest Version Feature in Error

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

The "BI Publisher Report Properties dialog" topic in Appendix E, "User Interface Reference" and the "Selecting a BI Publisher Report for a Dashboard Page" topic in Chapter 4, "Building and Using Dashboards" provide information on the View Latest Version feature in error. This feature is not currently available.

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-04).

44.16.5.12 Changes to the Instructions for Installing and Configuring BI Composer

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-03).

In the topic "Installing and Configuring BI Composer for Oracle BI EE" in Appendix C, "Accessibility Features," note the following changes need to be made to the instructions:

- Update Step 4.c.to read as follows:
In System MBean Browser, expand oracle.adf.share.connections, expand Application:bicomposer, expand ADFConnections, expand ADFConnections, expand BISoapConnection, and then click bi-default.

- Add in step 4.d. that the correct value for Port is 9704.

- Add a step 6 that reads as follows:
Restart the Oracle WebLogic Server and Oracle Business Intelligence. For more information on restarting the Oracle WebLogic Server, see Oracle Fusion Middleware Administrator's Guide. For more information on restarting Oracle Business Intelligence, see Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

Also note that in release 11.1.1.5 of Oracle BI EE, BI Composer is available only in accessibility mode.

44.16.5.13 Mentions of the KPI Editor: Data Input Security Page Must Be Ignored

Impacted Release: 11.1.1.6.2

This issue is present in the 11.1.1.6.2 Bundle Patch 1 version of the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-04).

All mentions of using the KPI Editor: Data Input Security page to assign slice-level security to KPIs with target settings must be ignored. The sections "What Are Target Settings?" and "Creating KPIs" in Chapter 11 "Using KPIs and KPI Watchlists" and the topics "KPI editor," "KPI editor: General Properties page," and "KPI editor: Data Input Security page" in Appendix E "User Interface Reference" include mentions of the KPI Editor: Data Input Security page.

44.16.5.14 Breadcrumbs Disabled for Embedded Objects in ADF

Impacted Release: 11.1.1.7

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-06).

The "Navigating With Breadcrumbs" topic in Appendix A, "Basic Information to Tell Your Users" contains the following misinformation about navigational breadcrumbs: "Breadcrumbs display at the bottom of the page in Presentation Services or from Fusion Applications or ADF applications where BI objects have been embedded" Disregard "or ADF applications." Breadcrumbs are disabled for embedded objects in ADF.

44.16.5.15 Note on Fixed Headers with Scrolling Content Is Incorrect

Impacted Releases: 11.1.1.7

The following note included in the description of the Fixed Headers with scrolling content component in the Table Properties dialog: Style tab and the Trellis Properties dialog: General tab is incorrect:

Note: Tables and pivot tables that use the scrolling method to browse data do not render properly in Microsoft's Internet Explorer browser version 7 or 8. As a result, when Microsoft's Internet Explorer browser version 7 or 8 is detected, the table or pivot table is rendered using paging controls instead, unless the administrator specifically allows the scrolling method to be used with these browser versions. For information on allowing the scrolling method, see "Manually Configuring to Allow the Scrolling Method to Be Used in Microsoft's Internet Explorer Browser Version 7 or 8" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

Instead, the Note should read as follows:

Note: The scrolling method is not supported or thoroughly tested in Microsoft's Internet Explorer browser version 8. As a result, when Microsoft's Internet Explorer's browser version 8 is detected, the table or pivot table is rendered using paging controls instead.

Also, the scrolling method is not supported on Microsoft's Internet Explorer browser version 7 and, if this version is detected, the table or pivot table is rendered using paging controls.

44.16.5.16 Misinformation About Adding HTML Code in Prompt Labels

Impacted Release: 11.1.1.3, 11.1.1.5, 11.1.1.6, 11.1.1.6.2, 11.1.1.6.2 (BP1), 11.1.1.7

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-06).

The "Creating a Column Prompt," "Creating a Currency Prompt," "Creating an Image Prompt," and "Creating a Variable Prompt" topics in Chapter 6, and the "New Prompt dialog" topic in Appendix E, "User Interface Reference" contain the following misinformation in regards to using HTML when creating a prompt: "You can include HTML markup tags in the caption, such as <b>, <font>, and <table>." Disregard this statement. You cannot use HTML markup tags.

44.16.5.17 Enable on Totals for Action Links Not Described

Impacted Release: 11.1.1.7

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-06).

The "Adding Actions to Analyses" topic in Chapter 10 and "Column Properties dialog: Interactions tab" topic in Appendix E, "User Interface Reference" omitted information regarding the Enable on Totals check box for action links. The description should be: "Select the Enable on Totals check box when your analysis contains a total or grand total, and the associated attribute or measure column contains an action link or a conditional action link and you want the action link (or conditional action link) to be applied to both the column and the total or grand total. This does not apply to column heading action links and by default, this behavior is turned off."

44.16.5.18 Use of Multiple Values in Presentation Variable on Dashboards Not Described

Impacted Release: 11.1.1.5, 11.1.1.6, 11.1.1.6.2, 11.1.1.7

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-06).

The "What Is the Syntax for Referencing Variables?" topic in Chapter 2, omitted information regarding the use of multiple values for presentation variables on the dashboard. The information in Table 2-1 "Syntax for Referencing Tables" for presentation or request variables should read as follows:

Type of Variable

Syntax

Example

Presentation or request

@{variables.variablename}[format]{defaultvalue}

or

@{scope.variables['variablename']}

where:

- variablename is the name of the presentation or request variable, for example, MyFavoriteRegion.

- (optional) format is a format mask dependent on the data type of the variable, for example #,##0, MM/DD/YY hh:mm:ss. (Note that the format is not applied to the default value.)

- (optional) defaultvalue is a constant or variable reference indicating a value to be used if the variable referenced by variablename is not populated.

- scope identifies the qualifiers for the variable. You must specify the scope when a variable is used at multiple levels (analyses, dashboard pages, and dashboards) and you want to access a specific value. (If you do not specify the scope, then the order of precedence is analyses, dashboard pages, and dashboards.)

Note: When using a dashboard prompt with a presentation variable that can have multiple values, the syntax differs depending on the column type. Multiple values are formatted into comma-separated values and therefore, any format clause is applied to each value before being joined by commas.

@{variables.MyFavoriteRegion}{EASTERN REGION}

or

@{MyFavoriteRegion}

or

@{dashboard.variables['MyFavoriteRegion']}

or

(@{myNumVar}[#,##0]{1000})

or

(@{variables.MyOwnTimestamp}[YY-MM-DD hh:mm:ss]{)

or

(@{myTextVar}{A, B, C})

The information in Table 2-2 for "Guidelines for Referencing Variables in Expressions" for presentation or request variables should read as follows:

Type of Variable

Guidelines

Example

Presentation

- Use this syntax:

@{variablename}{defaultvalue}

where variablename is the name of the presentation variable and defaultvalue (optional) is a constant or variable reference indicating a value to be used if the variable referenced by variablename is not populated.

- To type-cast (that is, convert) the variable to a string, enclose the entire syntax in single quotes, for example:

'@{user.displayName}'

Note: If the @ sign is not followed by a {, then it is treated as an @ sign.

When using a dashboard prompt with a presentation variable that can have multiple values, the syntax differs depending on the column type.

Use the following syntax in SQL for the specified column type in order to generate valid SQL statements:

- Text — (@{variablename}['@']{'defaultvalue'})

- Numeric — (@{variablename}{defaultvalue})

- Date-time — (@{variablename}{timestamp 'defaultvalue'})

- Date (only the date) — (@{variablename}{date 'defaultvalue'})

- Time (only the time) — (@{variablename}{time 'defaultvalue'})

"Market"."Region"=@{MyFavoriteRegion}{EASTERN REGION}

or

"Products"."P4 Brand"=(@{myTextVar}['@']{BizTech})

or

"Products"."PO Product Number"=(@{myNumVar}{1000})

or

"Sales Person"."E7 Hire Date"=(@{myDateTimeVar}{timestamp '2013-05-16 00:00:01'})

or

"Time"."Total Fiscal Time"=(@{myDateVar}{date '2013-05-16'})

or

"Time"."Time Right Now"=(@{myTimeVar}{time '00:00:01'})

For multiple values (in specified data types) when using SQL:

If the column type is Text and variablename is passing val1, val2, and val3, the resultant is ('val1', 'val2', 'val3').
or

If the column type is Date and variablename is passing 2013-08-09 and 2013-08-10, the resultant is (date '2013-08-09', date '2013-08-10').
or

If the column type is Date-time and variablename is passing 2013-08-09 00:00:00 and 2013-08-10 00:00:00, the resultant is (timestamp '2013-08-09 00:00:00', timestamp '2013-08-10 00:00:00').

44.16.6 Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Mobile

Documentation errata in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Mobile are described in Oracle Fusion Middleware Release Notes for Oracle Business Intelligence Mobile for Apple iOS and Google Android, which is available at

http://docs.oracle.com/cd/E52471_01/bi.1111/e52669/toc.htm

These release notes include the following products:

- Oracle Business Intelligence Mobile for Apple iOS

- Oracle Business Intelligence Mobile for Google Android

44.16.7 Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition

This section describes documentation errata in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition. It includes the following topics:

- Section 44.16.7.1, "Manual opmn.xml Edits Needed to Use Teradata as a Data Source"

- Section 44.16.7.2, "Updates to Text for Consistency Check Warnings 39009 and 39059"

- Section 44.16.7.3, "Other Changes to List of New Consistency Check Warnings"

- Section 44.16.7.4, "Select the Virtual Private Database Option when Authenticating Against Essbase or Hyperion Financial Management Using a Shared Token"

- Section 44.16.7.5, "Manually Updating the Master MUD Repository"

- Section 44.16.7.6, "Initialization Block Failure at Server Start-Up Causes Connection Pool to be Blacklisted"

- Section 44.16.7.7, "Merge Local Changes Step Does Not Lock the Master Repository"

- Section 44.16.7.8, "Information Now Available for All Import Metadata Wizard Screens"

- Section 44.16.7.9, "Remove Smart View Mention in Appendix C"

- Section 44.16.7.10, "Explicitly Check Out Projects to Add Objects in a Multiuser Development Environment"

- Section 44.16.7.11, "Changes to DataDirect Drivers and Directories"

- Section 44.16.7.12, "Additional Information Available on SCM Configuration Template Files"

- Section 44.16.7.13, "Statement on Aggregate Creation Failure is Incorrect"

- Section 44.16.7.14, "Prefer Optimizer Estimates Option Available for Summary Advisor in Release 11.1.1.6.2, Bundle Patch 1"

44.16.7.1 Manual opmn.xml Edits Needed to Use Teradata as a Data Source

Impacted Releases: 11.1.1.3, 11.1.1.5

This issue is fixed in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (E10540-03).

The following section should have appeared in the topic "Performing Data Source Preconfiguration Tasks" in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition:

Setting Up Teradata Data Sources To use Teradata as a data source for Oracle Business Intelligence on Windows systems, you must manually edit opmn.xml on each computer running the Oracle BI Server to include required Teradata variables.

To update opmn.xml to include Teradata variables on Windows:

1. Open opmn.xml for editing. You can find opmn.xml at:

ORACLE_INSTANCE/config/OPMN/opmn/opmn.xml

2. Locate the ias-component tag for the Oracle BI Server process. For example:

<ias-component id="coreapplication_obis1" inherit-environment="true">

3. Under the Oracle BI Server ias-component tag, add the required Teradata variables TERA_HOME, TERAGSS_HOME, and TERAICU_HOME, and also update the PATH variable, as shown in the following example. Replace the example values with the installed location for the Teradata client:

<ias-component id="coreapplication_obis1" inherit-environment="true">
<environment>
...
<variable id="TERA_HOME" value="C:/Progra~1/Teradata/Client/13.10/
ODBCDR~1" />
<variable id="TERAGSS_HOME" value="C:/Progra~1/Teradata/TERADA~1/nt-i386/
131000~1.02" />
<variable id="TERAICU_HOME" value="C:/Progra~1/Teradata/Client/13.10/
SHARED~1" />
<variable id="PATH" value="$TERA_HOME/lib$:$TERAICU_HOME/lib$:$TERAGSS_
HOME/bin$:$ORACLE_HOME/bifoundation/server/bin$:$ORACLE_HOME/
bifoundation/web/bin$:$ORACLE_HOME/clients/epm/Essbase/EssbaseRTC/
bin$:" append="true" />
...
</environment>

Important:

If you use the default location when installing the Teradata client, then the PATH variable might exceed the 1024 character limit imposed by Windows. To avoid this issue, install the Teradata client in a directory with a shortened path name (such as C:\TD), or use shortened 8.3 file names (such as "C:\PROGRA~1\Teradata\Client\13.10\ODBCDR~1\Bin" instead of "C:\Program Files\Teradata\Client\13.10\ODBC Driver for Teradata\Bin").

To determine the correct 8.3 file names, run "dir /x" from the appropriate directory. For example:

C:\>dir /x
Volume in drive C has no label.
Volume Serial Number is 0000-XXXX
Directory of C:\
08/25/2008  03:36 PM   <DIR>    DATAEX~1    DataExplorer
04/20/2007  01:38 PM   <DIR>                dell
08/28/2010  10:49 AM   <DIR>    DOCUME~1    Documents and Settings
07/28/2008  04:50 PM   <DIR>    ECLIPS~2    EclipseWorkspace
09/07/2007  11:50 AM   <DIR>                Ora92
09/07/2007  11:50 AM   <DIR>                oracle
05/21/2009  05:15 PM   <DIR>                OracleBI
05/21/2009  05:12 PM   <DIR>    ORACLE~1    OracleBIData
03/02/2011  04:51 PM   <DIR>    PROGRA~1    Program Files

4. Save and close the file.

5. Restart OPMN.

6. Repeat these steps on each computer that runs the Oracle BI Server process. If you are running multiple Oracle BI Server instances on the same computer, be sure to update the ias-component tag appropriately for each instance in opmn.xml (for example, ias-component id="coreapplication_obis1", ias-component id="coreapplication_obis2", and so on).

44.16.7.2 Updates to Text for Consistency Check Warnings 39009 and 39059

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (E10540-03).

In the section "New Features for Oracle BI EE xxx Release 1 (11.1.1.3)" in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition, a list of new consistency check warnings is provided. Note the following changes for warnings 39009 and 39059 in Release 11.1.1.5:

- The information about the consistency check warning 39009 is valid for Release 11.1.1.3, but does not apply to Release 11.1.1.5. This warning no longer occurs due to underlying changes in the code.

- In Release 11.1.1.5, the description for the consistency check warning 39059 should read as follows:
"Even though this fact logical table source has an aggregate grain set in this dimension, no join was found that connects to any logical table source in this dimension (or a potentially invalid join was found).

This means that either no join exists at all, or it does exist but is potentially invalid because it connects a higher-level fact source to a lower-level dimensional source. Such joins are potentially invalid because if followed, they might lead to double counting in query answers.

For example, consider Select year, yearlySales. Even if a join exists between monthTable and yearlySales table on yearId, it should not be used because such a join would overstate the results by a factor of 12 (the number of months in each year).

If you get a 39059 warning after upgrade, verify that the join is as intended and does not result in incorrect double counting. If the join is as intended, then ignore the 39059 warning."

44.16.7.3 Other Changes to List of New Consistency Check Warnings

Impacted Releases: 11.1.1.3, 11.1.1.5

This issue is fixed in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (E10540-03).

In the section "New Features for Oracle BI EE xxx Release 1 (11.1.1.3)," a list of new consistency check warnings is provided. Note the following changes to this list. These changes apply to Release 11.1.1.3 and Release 11.1.1.5:

- The consistency check warning 39055 should appear in its own row in the table, with the following description:
"This warning indicates that there is a physical join between the given fact and dimension sources, but there is not a corresponding logical join between the fact table and the dimension table."

- The description for consistency check errors 38012 and 38001 should read as follows:
"Logical columns that are not mapped to any logical table source are reported as consistency errors, because the logical table source mappings are invalid and would cause queries to fail.

Both of the given validation rules are related to the same issue."

- The description for consistency check warning 39003 should read as follows:
"This warning indicates that the given column is only mapped to logical table sources that are disabled. The warning brings this issue to the repository developer's attention in case the default behavior is not desired."

44.16.7.4 Select the Virtual Private Database Option when Authenticating Against Essbase or Hyperion Financial Management Using a Shared Token

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (E10540-03).

This additional information applies when you authenticate against Essbase or Hyperion Financial Management data sources using a shared token. After selecting SSO using CSS Token in the data source connection pool in the Oracle BI repository, you should also select the Virtual Private Database option in the corresponding database object to protect cache entries.

44.16.7.5 Manually Updating the Master MUD Repository

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (E10540-03).

During the course of Oracle BI repository development in a Multiuser Development (MUD) environment, it might be necessary to make manual changes to the master repository. Because of the highly controlled nature of the MUD process, you must be careful when performing any manual steps because there is accounting information stored in the MUD history log (.mhl) file. To manually work on the master repository, you must work on the repository in a separate directory from the MUD directory. Then, you must replace both the master RPD and the latest versioned repository in the MUD directory.

For example, follow these steps to manually update a repository named master.rpd:

1. Copy the master repository (master.rpd) out of the MUD directory into a local directory.

2. Use the Oracle BI Administration Tool to make the changes necessary to the local copy of the master repository (master.rpd).

3. When manual edits are complete, copy master.rpd to the MUD directory as master.rpd. For example:

copy c:\local\master.rpd c:\mud\master.rpd

4. In the MUD directory, identify the latest repository with a version number. For example, master.7011.

5. Copy master.rpd to the MUD directory and overwrite the latest versioned repository. For example:

copy c:\local\master.rpd c:\mud\master.7011

44.16.7.6 Initialization Block Failure at Server Start-Up Causes Connection Pool to be Blacklisted

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (E10540-03).

During Oracle BI Server start-up, if an initialization block fails for a particular connection pool, no more initialization blocks using that connection pool are processed. Instead, the connection pool is blacklisted and subsequent initialization blocks for that connection pool are skipped. This behavior ensures that the Oracle BI Server starts in a timely manner, even when a connection pool has a large number of associated initialization blocks or variables.

If this occurs, a message similar to the following is displayed in the server log:

[OracleBIServerComponent] [ERROR:1] [43143] Blacklisted connection pool conn_pool_name

If you see this error, then check the initialization blocks for the given connection pool to ensure that they are correct.

44.16.7.7 Merge Local Changes Step Does Not Lock the Master Repository

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (E10540-03).

In Release 11.1.1.5, when working in a multiuser development environment, the master repository is not locked when you merge local changes. Instead, the master repository is locked during the Publish to Network step. This change reduces the total time that the master repository is locked to avoid lock contention issues.

With this change, the publish step now checks that no other developer published changes to the master between the time you merged local changes and the time you published to network. If the MUD logic discovers that another repository developer published to the network in this time period, then the system automatically performs again the merge with the master. To redo the merge, the system must roll back to the RPD version that you used for the Merge Local Changes step, and then merges it with the new master.

Because of this change, you must always merge all local changes before publishing to the network. Otherwise, you might lose any changes that you made between merge and publish if a rollback becomes necessary for a merge redo.

44.16.7.8 Information Now Available for All Import Metadata Wizard Screens

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (E10540-03).

The description for the Map to Logical Model and Publish to Warehouse screens of the Import Metadata Wizard in the Administration Tool states that these screens are reserved for a future release. This is no longer correct. Instead, refer to Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (Oracle Fusion Applications Edition) in the Oracle Fusion Applications Technology Library for information about these screens.

44.16.7.9 Remove Smart View Mention in Appendix C

Impacted Releases: 11.1.1.5, 11.1.1.6.0

This issue is fixed in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (E10540-04).

The opening paragraphs of Appendix C, "Logical SQL Reference" mention Oracle Hyperion Smart View for Office as a client for the Oracle BI Server. All mentions of Smart View must be ignored, as described in Section 44.4.2, "Oracle Hyperion Smart View for Office Not Supported in Oracle Business Intelligence 11g, Releases 11.1.1.5, 11.1.1.6.0, and 11.1.1.6.2."

44.16.7.10 Explicitly Check Out Projects to Add Objects in a Multiuser Development Environment

Impacted Releases: 11.1.1.6.0

This issue is fixed in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (E10540-04).

The following additional information is available for Chapter 3, "Setting Up and Using the Multiuser Development Environment:"

In previous releases, objects that were part of the master repository, but that did not belong to a currently checked-out project, could be added between the merge and publish steps, because the entire repository was locked until publishing was complete. Now that the merge and publish steps are combined in a single Publish to Network step, you must explicitly check out a project that contains the desired object to add it to the currently open project.

For example, suppose that you want to add fact table "A" that is part of project "Other Project" to your own project, "My Project." To do this, you must check out both "Other Project" and "My Project." Then, add Fact Table "A" to "My Project" and publish the changes to the network. The next time that you check out "My Project", the fact table is part of the repository subset.

44.16.7.11 Changes to DataDirect Drivers and Directories

Impacted Releases: 11.1.1.5, 11.1.1.6.0

This issue is fixed in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (E10540-04).

The "Using DataDirect Connect ODBC Drivers on Linux and UNIX" section provides information on DataDirect Connect ODBC drivers and their directories. The driver and directory names are incorrect and must be updated as follows:

SEase23.so to ARase23.so (for Sybase)

SEifcl23.so to ARifcl23.so (for Informix)

SEmsss23.so to ARmsss23.so (for MS SQL Server)

Oracle_BI1/bifoundation/odbc/lib

to

Oracle_BI1/common/ODBC/Merant/5.3/lib/

44.16.7.12 Additional Information Available on SCM Configuration Template Files

Impacted Releases: 11.1.1.6.2

The following additional information is available for Step 4 in the section "Creating an SCM Configuration File:"

The SCM configuration template files are called scm-conf-ade.template.xml and scm-conf-svn.template.xml. In addition to being available in the ORACLE_INSTANCE location indicated, they are also available on the Oracle Technology Network (OTN) at:

http://www.oracle.com/technetwork/middleware/bi-foundation/downloads/obieescmconfigfiles-1568980.zip

44.16.7.13 Statement on Aggregate Creation Failure is Incorrect

Impacted Releases: 11.1.1.6.2

In the section "About Aggregate Persistence Errors," the following incorrect statement is displayed:

"If there is an error in the creation of any aggregate, then the entire aggregate request is terminated and subsequent aggregates are not created. Aggregates that are already created and checked in remain checked in."

Instead, the section should read as follows:

"When a series of aggregates are being created, and the creation of one aggregate fails, the aggregate persistence engine skips creation of the failed aggregate and its dependencies and proceeds to the next aggregate in the list. Check the log files to identify failed aggregates.

If there are errors, you must remove them at the time of the error or at the next ETL run in one of the following ways:

- Manually remove the aggregates from the metadata and the database. To identify the aggregate metadata, you can query the repository using the IsSystemGenerated filter for physical tables and logical table sources. See "Querying the Repository" for more information.

- Automatically remove the failed aggregates using the Delete Aggregates specification. In particular, use this technique to remove any orphan aggregate dimensions (those not joined to any other fact table)."

44.16.7.14 Prefer Optimizer Estimates Option Available for Summary Advisor in Release 11.1.1.6.2, Bundle Patch 1

Impacted Releases: 11.1.1.6.2

The following additional information is available for Step 11 in the section "Using the Oracle BI Summary Advisor Wizard:"

For its algorithm to work correctly, Oracle BI Summary Advisor needs to obtain row counts (cardinality) for certain queries on the data sources. Summary Advisor issues count queries to the back-end data sources to obtain these row counts, which can sometimes take a long time to execute.

In Release 11.1.1.6.2, Bundle Patch 1, you can optionally select Prefer Optimizer Estimates in the Miscellaneous screen of the Summary Advisor Wizard to improve performance during the Summary Advisor process. Selecting this option enables Summary Advisor to use cardinality estimates that originate out of the database query optimizer (also known as the Explain query plan) whenever possible, rather than issuing actual count queries.

This feature is only available for Oracle Database data sources. In addition, for Summary Advisor to use database query optimizer estimates, the statistics on the concerned database objects must be available and up-to-date.

44.16.8 Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition

This section describes documentation errata in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition. It includes the following topics:

- Section 44.16.8.1, "Event Polling Tables Must Be Created Using the Repository Creation Utility (RCU)"

- Section 44.16.8.2, "Use of ps: Prefix in Elements Is Unnecessary"

- Section 44.16.8.3, "Lowercase for Boolean Values for Configuration Elements"

- Section 44.16.8.4, "Removal of Section 11.5, "Configuring to Download Oracle Hyperion Smart View for Office""

- Section 44.16.8.5, "Issue Copying a Jar File when Registering with EPM Workspace Release 11.2.3.00"

- Section 44.16.8.6, "Incomplete Information in "Validating the Catalog" Section"

- Section 44.16.8.7, "Missing Privilege for Using the Full-Text Catalog Search"

- Section 44.16.8.8, "Error for Configuring the Data Source for the Full-Text Catalog Search"

- Section 44.16.8.9, "Removal of Section 19.7.2.6, "Including Links with Analyses on Dashboards""

- Section 44.16.8.10, "MaxColumns Element Not Supported"

- Section 44.16.8.11, "Error in Section 22.3.2, "Specifying Defaults for Styles and Skins""

- Section 44.16.8.12, "Clarification of CaseInsensitiveMode Element"

- Section 44.16.8.13, "Updates of Information About the Catalog"

- Section 44.16.8.14, "Section on Manually Configuring for Interactions In Views Does Not Apply"

- Section 44.16.8.15, "Omission of Enabled Element in Custom Links Section"

- Section 44.16.8.16, "Omission of Section on Updating Java Development Kit (JDK)"

- Section 44.16.8.17, "Remove Mention of pasteBinary Script"

- Section 44.16.8.18, "Parameter Descriptions Missing or Inaccurate in NQSConfig.INI File Configuration Settings Appendix"

- Section 44.16.8.19, "Incorrect Commands to Start and Stop Administration Server on a Windows Environment"

44.16.8.1 Event Polling Tables Must Be Created Using the Repository Creation Utility (RCU)

Impacted Releases: 11.1.1.3, 11.1.1.5

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-03).

Section 7.8.1, "Setting Up Event Polling Tables on the Physical Databases," explains that you can manually create event polling tables using CREATE TABLE statements. This statement is incorrect.

Instead, to create an event polling table, run the Repository Creation Utility (RCU) to create the Business Intelligence Platform (BIPLATFORM) schemas in the physical database. RCU creates an event polling table called S_NQ_EPT. See Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence for information about running the Repository Creation Utility.

44.16.8.2 Use of ps: Prefix in Elements Is Unnecessary

Impacted Releases: 11.1.1.5, 11.1.1.6.0

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-04).

The guide includes four sections that contain code examples to show how to edit the instanceconfig.xml file for the Catalog element. In these examples, the ps: prefix is included before element names, which is unnecessary. The guide must be updated to not include the string "ps:" in tags, and the Catalog element should begin with the <Catalog> tag.

44.16.8.3 Lowercase for Boolean Values for Configuration Elements

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

Various chapters of the guide provide examples and descriptions of values for configuration elements in the instanceconfig.xml file. When you specify values, you must ensure that you specify the appropriate case for the letters. All Boolean values must be lowercase. In the guide, Boolean values are sometimes shown with an initial capital letter. The guide must be updated to ensure that all Boolean values are presented in all lowercase.

44.16.8.4 Removal of Section 11.5, "Configuring to Download Oracle Hyperion Smart View for Office"

Impacted Releases: 11.1.1.5, 11.1.1.6.0

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-04).

Section 11.5, "Configuring to Download Oracle Hyperion Smart View for Office," must be ignored, as described in Section 44.4.2, "Oracle Hyperion Smart View for Office Not Supported in Oracle Business Intelligence 11g, Releases 11.1.1.5, 11.1.1.6.0, and 11.1.1.6.2."

44.16.8.5 Issue Copying a Jar File when Registering with EPM Workspace Release 11.2.3.00

Impacted Releases: 11.1.1.7

Section 11.5 describes how to configure Oracle Business Intelligence for integration with EPM Workspace. Section 11.5.2 "Step 2: Copying a JAR File" describes how to copy a JAR file as part of the integration. The procedure for copying the JAR file does not work as described there when you integrate with EPM Workspace 11.1.2.3.00. Oracle Business Intelligence 11.1.1.7 and the EPM System 11.1.2.3.00 have incompatible INTEROP-SDK.JAR and css.jar files.

Therefore, before registering Oracle Business Intelligence with EPM Workspace, you must backup the INTEROP-SDK.JAR and css.jar from Oracle Business Intelligence and replace them with files from the EPM Workspace instance. After completing the registration process, you then restore the backed-up Oracle Business Intelligence INTEROP-SDK.JAR and css.jar files. The steps are described in this section.

To copy the JAR files for EPM Workspace Releases Earlier than 11.1.2.3.00:

1. Change to the following directory in the Oracle Business Intelligence installation and make a backup copy of the INTEROP-SDK.JAR file:
ORACLE_BI1\common\SharedServices\11.1.2.0\lib

2. Copy the INTEROP-SDK.JAR file in the following directory of the EPM Workspace installation.
ORACLE_HOME\Middleware\EPMSystem11R1\common\SharedServices\11.1.2.0\lib

3. Paste the INTEROP-SDK.JAR file from the EPM Workspace installation to overwrite the version in the Oracle Business Intelligence installation.

To copy the JAR files for EPM Workspace Release 11.1.2.3.00 or later:

Note:

This approach applies only when registering Oracle Business Intelligence with EPM Workspace 11.1.2.3.00. It is incompatible with Essbase and associated components (release 11.1.2.2) that you install with Oracle Business Intelligence 11.1.1.7.

To copy the JAR files:

1. Change to the following directory in the Oracle Business Intelligence installation and make a backup copy of the INTEROP-SDK.JAR file:
ORACLE_BI1\common\SharedServices\11.1.2.0\lib

2. Copy the INTEROP-SDK.JAR file in the following directory of the EPM Workspace installation:
ORACLE_HOME\Middleware\EPMSystem11R1\common\SharedServices\11.1.2.0\lib

3. Paste the INTEROP-SDK.JAR file from the EPM Workspace installation to overwrite the version in the Oracle Business Intelligence installation.

4. Change to the following directory in the Oracle Business Intelligence installation and make a backup copy of the css.JAR file:
ORACLE_BI1\common\CSS\11.1.2.0\lib

5. Copy the css.JAR file in the following directory of the EPM Workspace installation:
ORACLE_HOME\Middleware\EPMSystem11R1\ common\CSS\11.1.2.0\lib

6. Paste the css.JAR file from the EPM Workspace installation to overwrite the version in the Oracle Business Intelligence installation.

7. Change to the following directory and make a backup copy of the registry-api.jar file:
ORACLE_HOME\Middleware\EPMSystem11R1\ common\jlib\11.1.2.0

8. Paste the registry-api.jar file from the EPM Workspace installation to overwrite the version in the Oracle Business Intelligence installation.
ORACLE_BI1\common\jlib\11.1.2.0

To restore the Oracle Business Intelligence JAR files:

1. Change to the following directory in the Oracle Business Intelligence installation and copy the backed-up INTEROP-SDK.JAR file:
ORACLE_BI1\common\SharedServices\11.1.2.0\lib

2. Change to the following directory in the Oracle Business Intelligence installation and copy the backed-up css.JAR file:
ORACLE_BI1\common\CSS\11.1.2.0\lib

3. Change to the following directory and copy the backed-up registry-api.jar file:
ORACLE_HOME\Middleware\EPMSystem11R1\ common\jlib\11.1.2.0

44.16.8.6 Incomplete Information in "Validating the Catalog" Section

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-03).

Section 17.2.4 "Validating the Catalog," includes incomplete information for performing the validation. Complete and correct information is provided in Section 17.2.5 of the Release 11.1.1.6 documentation and is still applicable to Release 11.1.1.5. The updated section is available at the following location:

http://docs.oracle.com/cd/E23943_01/bi.1111/e10541/prescatadmin.htm#BAJBJEFA

44.16.8.7 Missing Privilege for Using the Full-Text Catalog Search

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Section 17.14.1 includes a procedure that lists the privileges that the BISystem role must be granted for searching the catalog. The "Access SOAP" privilege is missing from the list and must be added.

44.16.8.8 Error for Configuring the Data Source for the Full-Text Catalog Search

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-03).

Section 17.11.4.4 describes how to configure the data source for the full-text catalog search. Step 5 of that procedure describes how to specify the Display URL Prefix. The step includes an incorrect line for Secure Enterprise Search 11.2.1 or later. The line should read as follows:

http://host:port/bisearch/urlbuilder/ (for Secure Enterprise Search 11.2.1, 11.1.2.2, or later)

44.16.8.9 Removal of Section 19.7.2.6, "Including Links with Analyses on Dashboards"

Impacted Releases: 11.1.1.3

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-02).

Chapter 19, "Configuring and Managing Analyses and Dashboards" of the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition, Release 11.1.1.3 includes Section 19.7.2.6, "Including Links with Analyses on Dashboards." This section is not applicable and must be removed from the guide.

44.16.8.10 MaxColumns Element Not Supported

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-03).

Chapter 20, "Configuring Advanced Options for Mapping and Spatial Information," includes descriptions of the MaxColumns element. This element is not supported. If this element is included in the instanceconfig.xml file, then you might see an error message when trying to start Presentation Services.

44.16.8.11 Error in Section 22.3.2, "Specifying Defaults for Styles and Skins"

Impacted Releases: 11.1.1.3

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-02).

Section 22.3.2, "Specifying Defaults for Styles and Skins" in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition, Release 11.1.1.3 contains sample code from the instanceconfig.xml file for working with the DefaultStyle and DefaultSkin elements. The parent element for these elements should be UI, so the sample code should read as follows:

<ServerInstance>
<UI>
<DefaultStyle>myStyle</DefaultStyle>
<DefaultSkin>mySkin</DefaultSkin>
</UI>
</ServerInstance>

44.16.8.12 Clarification of CaseInsensitiveMode Element

Impacted Releases: 11.1.1.3

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-02).

Appendix E in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition, Release 11.1.1.3 provides an example of the section of the instanceconfig.xml file in which you can include the CaseInsensitiveMode element. The correct parent element of QueryManager is missing for CaseInsensitiveMode. The proper syntax is as follows:

<ServerInstance>
<QueryManager>
<CaseInsensitiveMode>false</CaseInsensitiveMode>
</QueryManager>
</ServerInstance>

44.16.8.13 Updates of Information About the Catalog

The following sections provide information for inclusion in Chapter 18, "Configuring and Managing the Oracle BI Presentation Catalog" in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition, Release 11.1.1.3:

- Section 44.16.8.13.1, "Guidelines for Object Names"

- Section 44.16.8.13.2, "Handling Users of the Catalog"

- Section 44.16.8.13.3, "Handling Heterogeneous Nodes"

- Section 44.16.8.13.4, "Handling Catalog Files on Various Platforms"

- Section 44.16.8.13.5, "Known Issues with Catalog Files"

- Section 44.16.8.13.6, "Validating the Catalog"

- Section 44.16.8.13.7, "Performing a Basic Validation of the Catalog"

- Section 44.16.8.13.8, "Specifying the Elements for Validating the Catalog"

- Section 44.16.8.13.9, "Updates for XML Files and Text Strings"

44.16.8.13.1 Guidelines for Object Names

Impacted Releases: 11.1.1.3

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-02).

Each object in the catalog is stored in its own file. For example, an analysis called Analysis 1 is stored in a file named Analysis1. The object name that is visible to users, such as Analysis 1, is referred to as the logical object name.

The following list provides guidelines for object names:

- No restrictions exist on which characters are allowed in the logical name of an object in the catalog, as long as the characters are valid Unicode characters. The following are valid logical names:

Hello World
Profit / Loss
% Sales * $ Cost ~~ $ "Expense"?

- The length of the logical object name must not exceed 256 Unicode characters.
For more information on Unicode, see Section 44.16.8.13.4, "Handling Catalog Files on Various Platforms."

- The length of the logical path name for an object must not exceed 16000 Unicode characters.

- The number of directory segments in a logical path name for an object must be not exceed 255 segments.
For example, a directory with a name such as /n1/n2/n3/n4/…./n253/n254/n255 is acceptable, while a name such as /n1/n2/n3/n4/…./n254/n255/n256 is unacceptable.

- When you pass the path name of an object using SOAP, you must escape the following characters:

Forward slash (/)
Backward slash (\)
Tilde (~)
Asterisk (*)
Question mark (?)

The following logical path names are all valid:

/shared/test/Hello World
/shared/test/Profit \/ Loss
/shared/test/% Sales \* $ Cost \~\~ $ "Expense"\?

Use care when building a catalog path. It is very common to see code that assumes the forward slash (/) is always a path separator. Always verify your path code with an object name such as "Profit / Loss".

- When you pass a catalog search filter using SOAP, you must escape the following characters:

Forward slash (/)
Backward slash (\)
Tilde (~)
Asterisk (*)
Question mark (?)
Caret (î)
Dollar sign (?)

The following search filters are all valid:

Hello World
Profit \/ Loss
% Sales \* \$ Cost \~\~ \$ "Expense"\?

44.16.8.13.2 Handling Users of the Catalog

Impacted Releases: 11.1.1.3

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-02).

The catalog is designed to scale to thousands of concurrent users. To achieve this, the catalog adheres to the following guidelines:

- The average user typically only reads from the catalog and rarely, if ever, writes to it. In Release 11g, each user is constantly and automatically updating his or her Most Recently Used file, but each user's "read" operations still far outweigh the user's "writes" operations. Therefore, the read-to-write ratio is typically at least 100 to 1.

- While a locking mechanism guarantees that only one user can write to an object at a time, it is rare for multiple users to attempt to write simultaneously to the same object. A feature called "lazy locking" allows users to continue reading an object even when another user is updating that object.

- Modern file systems cache "small" files directly inside the directory record, such that reading any information on a directory simultaneously loads all small files directly into the operating system's memory cache. Therefore, it is good practice to keep files in the catalog "small," especially the frequently "read" .atr metadata files. When these metadata files remain small, then all the .atr files in a directory are loaded into memory with one physical hard disk read. Every file that exceeds the "small" threshold adds another physical hard disk read, which can cause a 100% degradation for each large file. In other words, use care when considering storing arbitrary "Properties" in .atr files.

- Reading an object's .atr metadata file using NFS is far slower than reading it directly from a local disk. For this reason, Presentation Services additionally caches all .atr files internally. This cache can become briefly "stale" when another node in the cluster writes data to the file that is newer than the data that is cached by the current node. Therefore, all nodes are refreshed as per the MaxAgeMinutes element in the instanceconfig.xml file, whose default for a cluster is 5 minutes. This default setting commonly achieves the best trade-off between the possibility of stale data and the known performance impact. (The default for an environment without clusters is 60 minutes.)

44.16.8.13.3 Handling Heterogeneous Nodes

Impacted Releases: 11.1.1.3

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-02).

To allow heterogeneous nodes in a cluster, the catalog adheres to the following guidelines:

- The maximum length for the name of an object on disk is 256 bytes, which is 64 Unicode characters. The logical name is restricted to 256 Unicode characters. To adhere to this restriction, logical names greater than 32 characters are hashed.

- The maximum length for the name of a path on disk is 32KB, which is 8000 Unicode characters. The logical path is restricted to 16000 Unicode characters.

- All path names on disk are all lowercase. The logical path name allows mixed case, but is still case-insensitive.

- Certain characters are not allowed for path names on disk, while the logical path name allows all characters. For example, Windows systems disallow certain characters such as the colon (:), so those characters are mapped using standard HTML escape sequences. For example, the period character (.) becomes "%2e".

- Certain file names are not allowed on disk, while the logical object name has no restrictions. For example, Windows systems disallow certain file names such as COM, so those names are mapped using standard HTML escape sequences. For example, "com" becomes "co%6d".

44.16.8.13.4 Handling Catalog Files on Various Platforms

Impacted Releases: 11.1.1.3

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-02).

Keep the following points in mind when handling catalog files on various platforms:

- For UNIX Platforms: UNIX kernels must commonly be configured to allow more than 4000 subdirectories per directory. See Chapter 18 for information on the HashUserHomeDirectories element.

- For Windows Platforms:
When users want to navigate catalog files using a tool such as Microsoft Windows Explorer, then they want the catalog structure based on a short path name such as c:/obi/demo, rather than the long default path name. Note that such navigation is not recommended.

- FAT is not supported, and NTFS is required.

- Performance on Windows platforms degrades noticeably when more than 8000 files exist in a single directory. Because each catalog object has two files (the data file and the .atr metadata file), it is strongly recommended that you not store more than 4000 catalog objects in a single directory. See Chapter 18 for information on the HashUserHomeDirectories element.

- Windows Explorer does not handle long path names properly, and it is recommended to not Windows Explorer to navigate the internal structure of the catalog. While the file system can handle path names as long as 32KB and Presentation Services is not negatively affected, you cannot use Windows Explorer with any path name that is longer than approximately 2KB.
Because a single Unicode character can require as many as 4 bytes, you might be unable to use Windows Explorer with path names of only 500 Unicode characters. This limitation does not affect Presentation Services. Because of this limitation, place the catalog in a top-level directory, such as c:\mycatalog\sales.

44.16.8.13.5 Known Issues with Catalog Files

Impacted Releases: 11.1.1.3

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-02).

The following issues are known when working with catalog files:

- Locking across NFS systems is difficult, but Presentation Services provides an effective locking mechanism in recent patches. Obtain key patches to update older versions of Oracle BI EE as necessary.
For more information, see Section 44.16.8.13.6, "Validating the Catalog."

- Various third-party FTP programs have issues handling '%' escape sequences, which often results in a renamed file that is doubly escaped. For example, a file that is named sa%2epaint (whose logical name is SA.Paint) is incorrectly renamed to sa%252epaint (whose logical name is SA%2ePaint).
Avoid using an FTP program directly against a catalog. Instead, download and use the 7-Zip utility to compress the catalog files, then use an FTP program to transfer the resulting compressed file.

44.16.8.13.6 Validating the Catalog

Impacted Releases: 11.1.1.3

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-02).

Over time, inconsistencies can develop in the catalog as links are broken, users are deleted, or NFS file system issues are encountered. These inconsistencies can eventually lead to incorrect behavior, such as the inability to edit an agent's recipient list. You can periodically take the production system offline and validate the catalog, to be informed of and to take corrective action on inconsistencies.

44.16.8.13.7 Performing a Basic Validation of the Catalog

Impacted Releases: 11.1.1.3

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-02).

Use the following procedure to perform a basic validation of the catalog.

To validate the catalog:

1. Stop Presentation Services.
For information, see Chapter 4 of the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition, Release 11.1.1.3.

2. Refresh the user GUIDs for the catalog. See Chapter 3 of the Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition, Release 11.1.1.3 for information

Caution:

Ensure that you regenerate the user GUIDs before validating the catalog. Failure to do so can result in the removal of all accounts, permissions, and privileges from the catalog.

3. Back up the catalog by using the 7-Zip utility to create a compressed file for it.

4. Create a backup copy of the instanceconfig.xml file.

5. Edit the instanceconfig.xml file so that it contains the appropriate elements for performing the validation.
For information on these elements, see Section 44.16.8.13.8, "Specifying the Elements for Validating the Catalog."

6. Start Presentation Services to run the validation according to the values that you specified in the instanceconfig.xml file.

7. Stop Presentation Services.

8. Create a backup copy of the instanceconfig.xml file in which you added the validation elements, renaming the file similar to instanceconfig_validate.xml. In this way, you have a version of the file to use as a starting point for subsequent validations.

9. Restore the backup version of the instanceconfig.xml that you created earlier to use as the current version.

10. Start Presentation Services.

44.16.8.13.8 Specifying the Elements for Validating the Catalog

Impacted Releases: 11.1.1.3

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-02).

As part of the process of validating the catalog, you include elements in the instanceconfig.xml file that run the validation when you restart Presentation Services. The following procedure describes how to edit the instanceconfig.xml file to include these elements.

To specify the element for validating the catalog:

1. Open the instanceconfig.xml file for editing.

2. Locate the Catalog section in which you must add the elements that are described in Table 44-3.

3. Include the elements and their ancestor element as appropriate, as shown in the following example. In this example, the validation runs when Presentation Services starts. Inconsistent accounts (for example, deleted users), links, and objects are removed. Inconsistent users' home directory names are logged but directories are not removed.

<ServerInstance>
<ps:Catalog xmlns:ps="oracle.bi.presentation.services/config/v1.1">
<ps:Validate>OnStartupAndExit</ps:Validate>
<ps:ValidateAccounts>Clean</ps:ValidateAccounts>
<ps:ValidateHomes>Report</ps:ValidateHomes>
<ps:ValidateItems>Clean</ps:ValidateItems>
<ps:ValidateLinks>Clean</ps:ValidateLinks>
</ps:Catalog>
</ServerInstance>

Caution:

Include only one Catalog element in the instanceconfig.xml file or unexpected results might occur. Unless expressly noted, include most nodes in an XML document only once.

4. Save your changes and close the file.

Table 44-3 Elements for Validating the Catalog

Element

Description

Default Value

Validate

Performs the validation of the catalog according to the values of the other Validate-related elements in this section. Values are described in the following list:

- None — Performs no validation.

- OnStartup — Performs the validation when Presentation Services starts.

- OnStartupAndExit — Performs the validation when Presentation Services both starts and stops. This value allows re-running of the validation, performing as many cycles of Report and Clean until the catalog is as clean as appropriate.

If this value is not None, then all privileges and each object's ACLs in the entire catalog are cleaned of dead accounts, regardless of the settings of the other Validate-related elements.

None

ValidateAccounts

Verifies that all information about users, roles, and groups in the catalog is consistent. Values are described in the list after this table.

None

ValidateHomes

Verifies that all information about home directories in the catalog is consistent. Values are described in the list after this table.

None

ValidateItems

Verifies that all information about objects in the catalog is consistent. Values are described in the list after this table.

None

ValidateLinks

Verifies that all information about links in the catalog is consistent. Values are described in the list after this table.

None

The elements have the values that are described in the following list:

- None — Specifies that no validation is performed.

- Report — Specifies that details about each inconsistent object are written to the sawlog.log file.

- Clean — Specifies that details about each inconsistent object are written to the sawlog.log file and that each object is removed from the catalog.

44.16.8.13.9 Updates for XML Files and Text Strings

Impacted Releases: 11.1.1.3

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-02).

Section 18.8.2.1 "XML File Format for Searching for and Replacing Text Strings" in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition, Release 11.1.1.3 must be replaced with the following text.

In the search and replace XML file, you use an action element to identify each text string to search for and replace. The action elements are contained in a commands element.

The action element has the following attributes:

- command — Specifies the text to replace. The valid value is:

- textReplace — Replaces all the text that matches in an XML file, such as a column name.

- oldValue — Specifies the text string to search for.
When you specify this attribute for the textReplace command for the search and replace XML file, you must use the full Java regex syntax, which is not like a normal string.

To replace a string, you must do the following:

1. Escape any special Java regex characters (such as brackets, parentheses, dollar signs, and carets).

2. Escape any special "normal" string characters (such as backslashes and quotes).

3. Because you are working in an XML file, escape any special HTML characters (such as quotes and ampersands).

The full Java regex syntax is described in the following document: http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html.

Table 44-4 provides sample strings for use with the regex syntax in search criteria.

Table 44-4 Using regex Syntax in Search Criteria

Search String Entered

Result

a

Adds wildcards before and after the search string (for example, *a*), enabling the search to return results that contain the letter "a".

îa

Adds a wildcard after the search string (for example, a*), enabling the search to return results that begin with the letter "a".

a$

Adds a wildcard before the search string (for example, *a), enabling the search to return results that end with the character "a".

a\*

Searches explicitly for strings containing a character followed by an asterisk (*) for example, "a*".

?

Use a question mark (?) with a character and an asterisk (*) to return zero (0) or more occurrences of a character. For example ?a* returns zero or more occurrences of the character "a".

- newValue — Specifies the replacement text.

- ignoreCase — Ignores case when set to true, but becomes case-sensitive when set to false. The default value is false.

The following is a partial example of an XML file for searching for and replacing a text string:

<?xml version="1.0" encoding="utf-8"?>
<actions>
<action command="textReplace" oldValue="boots" newValue="HoleyShoes" ignoreCase="true"/>
</actions>

44.16.8.14 Section on Manually Configuring for Interactions In Views Does Not Apply

Impacted Releases: 11.1.1.6.0; 11.1.1.6.2

Section 18.3.4 "Manually Configuring for Interactions In Views" does not apply to Release 11.1.1.6.0 and Release 11.1.1.6.2, but does apply to Release 11.1.1.6.2, Bundle Patch 1 onwards.

44.16.8.15 Omission of Enabled Element in Custom Links Section

Impacted Releases: 11.1.1.6.0

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-04).

Section 18.5.2.2 "Adding the CustomLinks Element" describes how to edit the instanceconfig.xml file to display custom links on the Oracle BI Home page. The procedure incorrectly omits the Enabled element. You must include the Enabled element set to true within the CustomLinks element to display custom links.

44.16.8.16 Omission of Section on Updating Java Development Kit (JDK)

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6, 11.1.1.6.2

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-06).

After you install and configure Oracle Business Intelligence, you might need to update the JDK for the instance; for example, if an update is required per the policy of your organization. Before deciding to update the JDK, ensure that you use an appropriate version. For detailed information on versions, see the certification document available on Oracle Technology Network (OTN):

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

To update the JDK for the instance of Oracle Business Intelligence:

1. Stop all services for Oracle Business Intelligence.

2. Download the appropriate JDK version from the Oracle Java web site and copy it to the ORACLE_HOME directory.

3. Rename the existing jdk directory to jdk.OLD.

4. Run the JDK Installer, which unzips the distribution into the jdkversion-num directory.

5. Rename the directory from jdkversion-num to jdk, to ensure that all existing configuration references remain valid.

6. Restart the services for Oracle Business Intelligence.

44.16.8.17 Remove Mention of pasteBinary Script

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2

This issue is fixed in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (E10541-05).

Chapter 24, "Moving Between Environments," includes mention of the pasteBinary script not being supported with Oracle Business Intelligence installations that were installed on 64-bit operating systems using the Enterprise Installation type. This lack of support has been lifted and the script can be used in this case. Therefore, this mention must be removed from the guide.

44.16.8.18 Parameter Descriptions Missing or Inaccurate in NQSConfig.INI File Configuration Settings Appendix

Impacted Releases: 11.1.1.7

Appendix A describes the parameters in the NQSConfig.INI file and requires the following corrections and additions:

CACHE_FILE_BUFFER_SIZE

This parameter must be added to the appendix with this description:

Specifies the amount of memory used to temporarily store the cache file when writing to the disk. The default value is 128 KB.

Example: CACHE_FILE_BUFFER_SIZE = 128 KB;

ESSBASE_STUDIO_URL

The description of this parameter must be changed to the following:

Specifies the URL of the Essbase Studio servlet that aggregate persistence in the Oracle BI Server uses to connect to Essbase Studio, which helps to create the Essbase cube. Before including the port number in the URL, verify whether the HTTP port number (server.httpPort) is explicitly defined in the server.properties file, which Essbase Studio references. If the port number is explicitly defined in the file, then ensure that the port number that is specified in the URL for the Essbase Studio servlet matches the value of the HTTP port number in the server.properties file. Otherwise, specify the default value of 9080 in the URL of the Essbase Studio servlet. The server.properties file is located in the following directory:

$ORACLE_INSTANCE/EssbaseStudio/$COMPONENT_NAME/bin

The default value is "http://localhost:9080/dma/dmaservlet"

Example: ESSBASE_STUDIO_URL = "http://localhost:9080/dma/dmaservlet"

EVALUATE_SUPPORT_LEVEL

The description of this parameter must be amended with the following text:

Note the following:

- The EVALUATE_SUPPORT_LEVEL parameter controls the use of the EVALUATE family of database functions within analyses. Oracle recommends leaving EVALUATE_SUPPORT_LEVEL set to its default value of 0 to prevent the use of these functions within analyses. Setting EVALUATE_SUPPORT_LEVEL to a value of 1 or 2 enables users to insert arbitrary SQL expressions into an analysis using the Analysis editor, which potentially compromises data access security.

- The EVALUATE_SUPPORT_LEVEL parameter does not control use of the EVALUATE family of database functions within the metadata repository.

SSL_VERIFY_CLIENTS

This parameter must be added to the appendix with this description:

Note: The SSL_VERIFY_CLIENTS parameter is centrally managed by Fusion Middleware Control and cannot be changed by manually editing NQSConfig.INI, unless all configuration through Fusion Middleware Control has been disabled (not recommended).

Specifies whether to verify client certificates when acting as a server (that is, when the BI Server is receiving calls from clients such as Presentation Services). The default value is NO.

Example: SSL_VERIFY_CLIENTS=NO;

SSL_VERIFY_SERVERS

This parameter must be added to the appendix with this description:

Note: The SSL_VERIFY_SERVERS parameter is centrally managed by Fusion Middleware Control and cannot be changed by manually editing NQSConfig.INI, unless all configuration through Fusion Middleware Control has been disabled (not recommended).

Specifies whether to verify server certificates when acting as a client (that is, when the BI Server is calling the BI Security Service). The default value is YES.

Example: SSL_VERIFY_SERVERS=YES;

SSL_VERIFY_PEERS

The description of this parameter must be changed to the following:

This parameter has been deprecated. The SSL_VERIFY_CLIENTS and SSL_VERIFY_SERVERS parameters replace comparable functionality previously controlled by the SSL_VERIFY_PEER parameter. See Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence for more information.

44.16.8.19 Incorrect Commands to Start and Stop Administration Server on a Windows Environment

Impacted Releases: 11.1.1.7

Section 4.7, "Starting and Stopping the Administration Server and All Oracle Business Intelligence Java Components on Windows and UNIX" contains the following incorrect commands to start and stop the Administration Server on Windows:

- The command startWebLogic.cmd -start to start the Administration Server is incorrect and should be replaced with the command startWebLogic.cmd.

- The command stopWebLogic.cmd -stop to stop the Administration Server is incorrect and should be replaced with the command stopWebLogic.cmd.

44.16.9 Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition

This section describes documentation errata in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition. It includes the following topics:

- Section 44.16.9.1, "SASchInvoke Always Prompts for the Password in 11.1.1.5"

- Section 44.16.9.2, "Setup Multiple Authentication Providers"

- Section 44.16.9.3, "Error in Code Example for Refreshing User GUIDs"

- Section 44.16.9.4, "Adding UserName Attribute Properties user.login.attr and username.attr to Identity Store is Not Applicable"

- Section 44.16.9.5, "Removal of Invalid LDAP Configuration Properties when Setting Up SSL"

- Section 44.16.9.6, "Error in Code Example for Configuring a Database Adaptor"

- Section 44.16.9.7, "Error in Code Example for Configuring the WebLogic Server Environment"

44.16.9.1 SASchInvoke Always Prompts for the Password in 11.1.1.5

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition (E10543-05).

Section 5.5.1 "Using SASchInvoke When BI Scheduler is SSL-Enabled" in revision E10543-03 describes using the SASchInvoke command to invoke the BI Scheduler when SSL is enabled. A caution paragraph suggested that a password prompt is displayed when you run the command under SSL, but a password prompt is displayed regardless of SSL-enablement. The caution was confusing and has been removed for the E10543-04 revision.

44.16.9.2 Setup Multiple Authentication Providers

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition (E10543-05).

Chapter 3 did not explain how to configure multiple authentication providers, so a new section 3.2.3.3 "Configuring BI with Multiple Authentication Providers" was created for revision E10543-03. Chapter 5 did not explain how to set up SSL when multiple authenticators are configured, so a new section 5.6.6, "Configuring SSL When Using Multiple Authenticators" was created for revision E10543-04.

44.16.9.3 Error in Code Example for Refreshing User GUIDs

Impacted Releases: 11.1.1.5, 11.1.1.6.0

This issue is fixed in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition (E10543-06).

Section 3.8 "Refreshing User GUIDs" includes Step 3b on updating the Catalog element. The sample code for updating the element must be modified as follows:

<Catalog>
<UpgradeAndExit>false</UpgradeAndExit>
<UpdateAccountGUIDs>UpdateAndExit</UpdateAccountGUIDs>
</Catalog>

44.16.9.4 Adding UserName Attribute Properties user.login.attr and username.attr to Identity Store is Not Applicable

Impacted Releases: 11.1.1.6

This issue is fixed in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition (E10543-07).

The issue concerns information about adding the properties user.login.attr and username.attr to the identity store, which is not applicable.

In section 3.5.1 "Configuring the User Name Attribute in the Identity Store," disregard the following content:

- the note that begins with the text:
"For the UserName Attribute only; ..."

- the task entitled:
"To configure the User Name attribute in the identity store:"

- the note that begins with the text:
"Ensure that the users and groups from your authentication provider..."

44.16.9.5 Removal of Invalid LDAP Configuration Properties when Setting Up SSL

Impacted Releases: 11.1.1.7

These issues are fixed in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition (E10543-08).

The issues concern additional steps that you must complete when setting up SSL, if you modify the LDAP provider directory server configuration.

In Section 5.3.4 "Configuring Oracle WebLogic Server to Use Only the HTTPs Protocol by Disabling Non-SSL Listen Ports," Step 2, after you complete sub-step f (Click Ok), you must also complete the following steps:

1. Open the jps-config-jse.xml file for editing in:
mwhome/user_projects/domains/bifoundation_domain/config/fmwconfig/jps-config-jse.xml

2. Comment out the following entry, as shown:
<!-- <property value="oracle.security.jps.wls.internal.idstore.WlsLdapIdStoreConfigProvider" name="idstore.config.provider"/> -->

Note:

If the environment uses a security mechanism other than the WebLogic LDAP directory server (for example OAM or OID), you must also comment out the following entry in the jps-config-jse.xml file:

<!-- <serviceInstanceRef ref="idstore.ldap"/>-->

3. Save the jps-config-jse.xml file.

4. Restart JavaHost using the OPMN command line.

5. Complete the remaining steps as described in the documentation.

44.16.9.6 Error in Code Example for Configuring a Database Adaptor

Impacted Releases: 11.1.1.6

This issue is fixed in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition (E10543-07).

Section 3.4.3.4.2 "Configuring a Database Adaptor" includes Step 2 about ensuring that the adapter_template_usergroup1.xml file contains the following sample code. The guidAttribute is incorrectly shown as containing two letter t's. You must change it to guidAtribute, with a single letter t, as follows:

<initParams>
<param name="guidAtribute" value="orclguid"/>
</initParams>

44.16.9.7 Error in Code Example for Configuring the WebLogic Server Environment

Impacted Releases: 11.1.1.7

Section 5.3.3 "Manually Configuring the WebLogic Server Environment" includes Step 3 about adding the passwords identified in step 2 to the JAVA_OPTIONS properties, and provides example code for Linux. The paths to DemoTrust.jks and DemoIdentity.jks use escape characters (\") incorrectly. You must remove the incorrect escape characters around the paths as follows:

Code example showing incorrect escape characters:

JAVA_OPTIONS="${JAVA_OPTIONS} -Djavax.net.ssl.trustStore=\"MW_Home/wlserver_10.3/server/lib/DemoTrust.jks\" -Djavax.net.ssl.DemoTrustKeyStorePassphrase=\"password\" -Djavax.net.ssl.keyStore=\"MW_Home/wlserver_10.3/server/lib/DemoIdentity.jks\" -Djavax.net.ssl.keyStorePassword=\"DemoIdentityKeyStorePassPhrase\""
export JAVA_OPTIONS

Code example showing correct escape characters:

JAVA_OPTIONS="${JAVA_OPTIONS} -Djavax.net.ssl.trustStore=MW_Home/wlserver_10.3/server/lib/DemoTrust.jks -Djavax.net.ssl.DemoTrustKeyStorePassphrase=\"password\" -Djavax.net.ssl.keyStore=MW_Home/wlserver_10.3/server/lib/DemoIdentity.jks -Djavax.net.ssl.keyStorePassword=\"DemoIdentityKeyStorePassPhrase\""
export JAVA_OPTIONS

44.16.10 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence

This section describes documentation errata in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence.

These issues are described in Section 6.4.3, "Documentation Errata for the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence" of this document.

44.16.11 Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition

This section describes documentation errata in Oracle Fusion Middleware Enterprise Developer's Guide for Oracle Business Intelligence Enterprise Edition. It includes the following topic:

- Section 44.16.11.1, "Error in the "Passing Business Intelligence Content with the Oracle BI EE Contextual Event Action" Topic in Chapter 1, "Embedding Business Intelligence Objects in ADF Applications""

44.16.11.1 Error in the "Passing Business Intelligence Content with the Oracle BI EE Contextual Event Action" Topic in Chapter 1, "Embedding Business Intelligence Objects in ADF Applications"

Impacted Releases: 11.1.1.5

This issue is fixed in Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition (E10545-03).

The following sentence in the "Passing Business Intelligence Content with the Oracle BI EE Contextual Event Action" topic is incorrect: "At design time, the analysis designer determines which column should contain the Oracle BI EE contextual event action, adds an Invoke a Browser Script action type to the column, and browses for and selects USERSCRIPT.ADFAction."

Instead, this sentence should read: "At design time, the analysis designer determines which column should contain the Oracle BI EE contextual event action and from the New Action Link menu, selects ADF Contextual Event."

The "Passing Business Intelligence Content with the Oracle BI EE Contextual Event Action" topic should also state that the Administer must modify Oracle BI EE's instanceconfig.xml file so that the ADF Contextual Event option displays in the New Action Link menu within Presentation Services. To enable the action type to display in the New Action Link menu, the Administrator must add the ActionLinks setting to the <ServerInstance> tag as follows:

<ActionLinks>
<Enable EnableADFContextualEvent>true</EnableADFContextualEvent>
</ActionLinks>

44.16.12 Oracle Fusion Middleware Integrator's Guide for Oracle Business Intelligence Enterprise Edition

This section describes documentation errata in Oracle Fusion Middleware Integrator's Guide for Oracle Business Intelligence Enterprise Edition. It includes the following topic:

- Section 44.16.12.1, "Addendum to the "Overview of Integrating with Oracle Business Intelligence" Topic in Chapter 10, "Integrating Other Clients with Oracle Business Intelligence""

44.16.12.1 Addendum to the "Overview of Integrating with Oracle Business Intelligence" Topic in Chapter 10, "Integrating Other Clients with Oracle Business Intelligence"

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0

This issue is fixed in Oracle Fusion Middleware Integrator's Guide for Oracle Business Intelligence Enterprise Edition (E16364-04).

After the first paragraph in the "Overview of Integrating with Oracle Business Intelligence" topic, the following note should be included:

"Oracle generally does not confirm or test third-party client tool compatibility with the Oracle BI Server ODBC interface. Check the Oracle BI EE certification document for any specific certification information on third-party tools and the Oracle BI Server ODBC interface. For more information about the certification document, see "System Requirements and Certification"."

44.16.13 Oracle Fusion Middleware XML Schema Reference for Oracle Business Intelligence Enterprise Edition

This section describes documentation errata in Oracle Fusion Middleware XML Schema Reference for Oracle Business Intelligence Enterprise Edition.

There are no known issues at this time.

44.16.14 Oracle Business Intelligence Help System Errata

This section describes errata in the Oracle Business Intelligence help systems. It includes the following topics:

- Section 44.16.14.1, "Addendum to the Oracle BI Server DSN Configuration Wizard Help"

44.16.14.1 Addendum to the Oracle BI Server DSN Configuration Wizard Help

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6

In the Oracle BI Server DSN configuration Wizard online help, in the "ODBC Concepts" topic, the following statement should be included:

"Note that Oracle generally does not confirm or test third-party client tool compatibility with the Oracle BI Server ODBC interface. Check the Oracle BI EE certification document for any specific certification information on third-party tools and the Oracle BI Server ODBC interface."

45 Oracle Business Intelligence Applications and Data Warehouse Administration Console

This chapter includes details about patch requirements and Release Notes for Oracle Business Intelligence Applications and Oracle Business Intelligence Data Warehouse Administration Console (DAC) for Releases 11.1.1.5.x, 11.1.1.6.x, and 11.1.1.7.0.

Note: Beginning with release 11.1.1.7.1, release notes for Oracle Business Intelligence Applications are located on the Oracle BI Applications documentation library on the Oracle Technology Network. You can locate the appropriate Oracle BI Applications documentation library from the Oracle Business Intelligence Applications Documentation page at this URL: http://www.oracle.com/technetwork/middleware/bi-foundation/documentation/bi-apps-098545.html.

This chapter includes the following sections:

- Section 45.1, "Patch Requirements"

- Section 45.2, "Oracle Business Intelligence Applications Release Notes"

- Section 45.3, "Oracle Business Intelligence Data Warehouse Administration Console (DAC) Platform Release Notes"

Note:

Issues relating to DAC metadata are located in Section 45.2, "Oracle Business Intelligence Applications Release Notes". Issues relating to DAC platform are located in Section 45.3, "Oracle Business Intelligence Data Warehouse Administration Console (DAC) Platform Release Notes".

Sometimes, there can be a delay before revised Release Notes are published on the Oracle Technology Network (OTN). To get access to Oracle Business Intelligence Release Note items as soon as they are available, go to the Oracle BI Documentation wiki at https://wikis.oracle.com/display/oraclebidocumentation/Home

45.1 Patch Requirements

This section describes patch requirements for Oracle Business Intelligence Applications.

45.1.1 Obtaining Patches from My Oracle Support

Periodically, Oracle Business Intelligence patches are released. Some patches are mandatory, other patches are optional.

To see the patches that are available, go to My Oracle Support (formerly OracleMetaLink) using the following URL:

http://support.oracle.com.

To obtain a patch, see Section 1.6, "Downloading and Applying Required Patches".

45.2 Oracle Business Intelligence Applications Release Notes

This section describes issues associated specifically with Oracle Business Intelligence Applications, and includes the following sections:

- Section 45.2.1, "Oracle Business Intelligence Applications Issues and Workarounds Identified Since the Previous Revision"

- Section 45.2.2, "General Issues and Workarounds for Oracle Business Intelligence Applications"

- Section 45.2.3, "Installation Issues and Workarounds for Oracle Business Intelligence Applications"

- Section 45.2.4, "Upgrade Issues and Workarounds for Oracle Business Intelligence Applications"

- Section 45.2.5, "Oracle Business Intelligence Applications Offering/Module-specific Issues"

- Section 45.2.8, "Oracle Business Intelligence Applications Configuration Manager and FSM Issues"

- Section 45.2.9, "Security-related Issues for Oracle Business Intelligence Applications"

- Section 45.2.10, "Oracle Business Intelligence Applications Documentation Errata"

45.2.1 Oracle Business Intelligence Applications Issues and Workarounds Identified Since the Previous Revision

The issues and workarounds related to Oracle Business Intelligence that have been identified since the previous revision of the Release Notes include:

- Section 45.2.2.9, "Instructions to Change Create Navigate Actions and Create Invoke Actions to BI Author"

- Section 45.2.2.10, "Extracting Fusion Descriptive Flexfield (DFF) Information Into Oracle Business Analytics Warehouse"

- Section 45.2.5.5.1, "ETL Failure in SDE_FUSION_PRM_PartnerResourceHelper Task"

45.2.2 General Issues and Workarounds for Oracle Business Intelligence Applications

This section describes general issues and workarounds related to Oracle Business Intelligence Applications.

45.2.2.1 Patch Installation Instructions for Informatica Repository in Oracle BI Applications Release 11.1.1.5.2

This issue applies to Release 11.1.1.5.2.

Oracle Business Intelligence, Oracle Transactional Business Intelligence, and Oracle BI Applications patches for Release 11.1.1.5.2 are provided in the RUP Installer for Fusion Applications 11.1.2. The Fusion Applications media pack on Oracle Delivery Cloud includes the RUP installer. Run this installer by following instructions documented in the Oracle Fusion Applications Patching Guide 11g Release 1 (11.1.2), Chapter 5, "Installing Release Update Patches".

Oracle Business Intelligence, Oracle Transactional Business Intelligence, and Oracle BI Applications patches are applied automatically. An Oracle BI Applications patch for the Informatica Repository is not applied automatically but must be applied manually using OPatch. This patch is located at:

<your Repository root>/installers/biappsshiphome/metadata/12937967

Apply the patch and instructions following instructions documented in the Reference Guide for Oracle Business Intelligence Applications > Chapter 5, "Oracle BI Applications Patching". Before applying this patch, shut down the Administration Server and Managed Server in the BI Domain. Shut down OPMN processes. Informatica Services must be running. Running of this patch requires input of following information:

#Informatica Home Directory (under which server/bin/pmrep lives)
#infa.home = The location of the Informatica Home directory. This is the path to the Informatica binaries located under server/bin/pmrep. Example, /Informatica8.6.1.

#Informatica Repository Name
#infa.repo.name = The name of the Informatica Repository Service which manages the Informatica Repository. The name of the Informatica Repository Service can be viewed through Informatica Administration Console.

#Informatica Repository Domain
#infa.repo.domain = The name of the Informatica Domain. The name of the Informatica Domain can be viewed through Informatica Administration Console.

#Informatica Repository Username
#infa.repo.username = The Informatica Repository User that has appropriate privileges to execute workflows (for example, Administrator).

#Informatica Repository Password
#infa.repo.password = The Informatica Repository user password.

#Informatica Repository Hostname
#infa.repo.hostname = The name of the machine where Informatica Services has been installed (Informatica Gateway host name).

#Informatica Repository Server Port (default is 6001)
#infa.repo.port = Informatica Gateway port number. For example, 6001.

45.2.2.2 About Issues For Both Oracle Fusion Transactional Business Intelligence and Oracle Business Intelligence Applications

Some issues that apply to Oracle Fusion Transactional Business Intelligence may also apply to Oracle Business Intelligence Applications. Such issues and their workarounds, if any, are documented in the Oracle Fusion Applications release notes and not in this chapter. To quickly locate issues that apply to both Oracle Fusion Transactional Business Intelligence and Oracle Business Intelligence Applications, you can search the Oracle Fusion Applications release notes for the text string "This issue also applies to Oracle Business Intelligence Applications."

45.2.2.3 CONFIGURE_RPD.PY Script Does Not Set Connection Pool for Oracle BI Applications Configuration Manager

This issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2.

The setup script configure_rpd.py does not configure the connection pool for Oracle BI Applications Configuration Manager in the Oracle BI Applications RPD file. You must configure the connection pool manually, as described in the workaround below.

Workaround

1. Use Oracle BI Administration Tool to open the repository.

2. From the Manage menu, select Variables.

3. Locate and provide values for the variables CM_DSN and CM_USER.

1. For CM_DSN, provide the complete connect string in the Default Initializer box.

2. For CM_USER, provide the same information as the Data Warehouse Schema user in the Default Initializer box, enclosed in single quotation marks.

4. In the Physical layer, navigate to and click on BI Applications Configuration Data Source, and then click on Catalog.

5. Provide the password of the Configuration Manager schema user in the dialog that opens.

45.2.2.4 Using Multiple Execution Plans Using Different Source Connection Names But Running On The Same BI Server

This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6.

In DAC, if you have multiple Execution Plans using different source connection names but running on the same BI Server, then DAC should first run a Full load, then an Incremental load for common dimensions. In Releases 11.1.1.5.1 and 11.1.1.5.2, this will not execute correctly if you have specified a different Physical Data Source value in the DAC Connectivity Parameters for the Execution Plans.

Workaround

Specify the same Physical Data Source value in the DAC Connectivity Parameters for the Execution Plans. For example, when you create the Execution Plans, you must do the following:

1. Specify the Connectivity Parameters tab, and locate the parameter named DBConnection_OLTP.

2. Make sure that the Value is the same as for the other Execution Plans (for example, FUSION_V1_FSCM or FUSION_V1_CRM).

45.2.2.5 NLS:SDE_FUSION_DOMAINGENERAL_SALESINVOICESOURCE_FULL Failed With Syntax Error

This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6.

When you run ETL, the Task SDE_FUSION_DomainGeneral_SalesInvoiceSource_FULL in the Execution Plan 'Domains – Fusion 1.0' fails with a syntax error. This error occurs because the $$LANGUAGE_LIST's precision is defined as 4 in mplt_BC_FUSION_DomainGeneral_SalesinvoiceSource. The $$LANGUAGE_LIST's precision should be corrected to 255.

Workaround

1. In Informatica Mapping Designer, check out the Mapplet 'mplt_BC_FUSION_DomainGeneral_SalesinvoiceSource".

2. From the Mapplets menu, choose 'Parameters and Variables'.

3. Select the $$LANGUAGE_LIST parameter (it will have the a precision value set to 4), and change the value to 255.

4. Save the mapplet and 'Check in'.

5. In Informatica Workflow Designer, check out the following session tasks, then Refresh and validate the maps:

- SDE_FUSION_DomainGeneral_SalesInvoiceSource_FULL.

- SDE_FUSION_DomainGeneral_SalesInvoiceSource.

6. Check in both the Session Tasks.

45.2.2.6 Informatica License Dis-associating After Installation

If the Informatica PowerCenter license is dis-associated after installation and an error is reported by WCA, then you need to re-associate the license and manually create a Repository Service. This issue is an intermittent issue in Informatica PowerCenter V9.1.

This issue applies to Release 11.1.1.6.2.

The WCA error log will report an error similar to the following:

Error log:
[exec] Using INFA_HOME:       /scratch/aime/work/Informatica/Infa910
[echo] Now creating the repository: repservice for license:
[exec] Result: 255
BUILD FAILED
...
...

Workaround

1. Delete the Repository Service created by WCA (if it exists).
This Repository Service is not associated with a license and therefore should be deleted. You can do this using Informatica Administrator, by right clicking on the Repository Service name and selecting the delete option.

2. Add license to the node using Informatica Administrator (that is, choose Action, then New, then License).
For example, add the license '910_License_<HostName>42571'.

3. Use Informatica Administrator to manually create a repository with exactly the same name specified in wca_params.properties (by the INFA_RS_NAME parameter value).
Use the license name specified in Step 2.

4. Remove any create_Repository_service.err files from in wca/logs/ folder, and create a file named create_Repository_service.succ.

5. Restart WCA.

45.2.2.7 JAZN File Not Translated

This issue applies to Release 11.1.1.6.2.

The JAZN file is not translated in this release. There is no work-around for this issue.

45.2.2.8 Duplicate Rows in GL Account Segment Hierarchy Tables

This issue applies to Release 11.1.1.6.3.

Trees containing nodes with multiple parents cannot be used for reporting. The SILO mappings to populate the following tables potentially fail when such tree nodes exist:

- W_COST_CENTER_DH

- W_BALANCING _SEGMENT_DH

- W_NATURAL_ACCOUNT_SEGMENT_DH

- W_GL_SEGMENT_DH

Workaround

To workaround this issue, remove the trees from the hierarchy tables in the Oracle Business Analytics Warehouse.

1. Back up the DH table.

2. Delete the trees with duplicate rows, using the following SQL statement:

DELETE FROM <DH Table>
WHERE (hierarchy_id, hierarchy_version, datasource_num_id) in (
SELECT hierarchy_id, hierarchy_version, datasource_num_id
FROM <DH table>
GROUP BY
integration_id, hierarchy_version, datasource_num_id
HAVING COUNT (1) > 1
);

45.2.2.9 Instructions to Change Create Navigate Actions and Create Invoke Actions to BI Author

The default BI Author role does not have BI Privileges to allow users to create an action link for 'Navigate to a Web page'. To enable this BI Privilege, you must follow the Workaround below.

Workaround

1. Log in to Oracle BI Presentation Services as a user with Administrator privileges.

2. From the Home page in Presentation Services, select Administration.
Note: If you log in as a user without Administrator privileges, the Administration option is not displayed.

3. In the Security area, click Manage Privileges to display the Manage Privileges page.

4. Find the Create Navigate Actions privilege that you want to change and click on the application role next to it (in this case BI Administrator).

5. Use the Privilege dialog to add application roles to the list of permissions, and grant and revoke permissions from application roles.
For example, to grant the selected privilege to an application role, you must add the application role to the Permissions list.

6. Add BI Author role to the Permissions list, as follows:

1. Click Add Users/Roles.

2. Select BI Author from the list and click Search.

3. Select the BI Author from the results list.

4. Use the shuttle controls to move the application role to the Selected Members list.

5. Click OK.

7. Delete BI Administrator role from the list.

8. Save your changes.

9. Repeat steps 4 to 8 for Create Invoke Actions privilege.

45.2.2.10 Extracting Fusion Descriptive Flexfield (DFF) Information Into Oracle Business Analytics Warehouse

This issue applies to Releases 11.1.1.5 to 11.1.1.6.4.

To find out how to extract Fusion Descriptive Flexfield (DFF) information into Oracle Business Analytics Warehouse, refer to the following Tech Note that is available on My Oracle Support:

'OBIA 11g: Steps to extract the Fusion descriptive Flexfield (DFF) information into the Oracle BI application (OBIA) Warehouse', (Tech Note ID 1533519.1).

45.2.3 Installation Issues and Workarounds for Oracle Business Intelligence Applications

This section describes issues and workarounds related to installing Oracle Business Intelligence.

45.2.3.1 Installing Informatica PowerCenter 8.6.1 On Mount Points with Free Disk Space in Terabytes

This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6 (for UNIX and Linux) with Informatica PowerCenter 8.6.1 Hot Fix 11.

The Informatica PowerCenter Services installation requires 1,386 MB of free space. If the free disk space size is in the order of Terabytes, then the Installer does not recognize the free space and the following message on installation is received:

The installation requires 1,386 MB of free disk space, but there are only 0 MB available at: /Informatica/PowerCenter8.6.1. Free at least 1,386 MB to continue with the installation. Type 'Quit' to cancel this installation.

Workaround

Reduce the free space on the mount point to ~ 200 GB or less.

45.2.3.2 Restarting Components After Completing The Post-Installation Setup Steps

This issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2.

After completing the high-level setup tasks as described in Section 4.2.4 Overview of Tasks for Setting Up Oracle Business Intelligence Applications (Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications), before you start ETL processes you must start or restart the following components: Node Manager, Admin Server, Managed Server, and BI services (that is, OPMN).

45.2.3.3 Customer Cost Lines and Product Cost Lines Configuration is Missing From FSM Tasks for Oracle Financial Analytics

This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2 and 11.1.1.6.

The following steps are required if you would like to enable and use the Customer Cost Lines and Product Cost Lines feature in Profitability Analytics. On installation, Oracle provides default configuration files and the sample data for Customer Cost lines and Product Cost lines in CSV files. The content of data CSV files need to be replaced with your actual cost line data.

To configure the Customer Costs Lines and Product Costs Lines:

1. Copy the following configuration and sample data files from the ORACLE_HOME\biapps\etl\biapps_etl\data_files\universal_sample_data folder to the INFA_HOME\server\infa_shared\SrcFiles folder on the Informatica Server machine.

file_customer_cost_line.csv
file_product_cost_line.csv
file_xact_type.csv
file_chnl_type.csv
FILE_DOMAIN.csv

You can omit this step if the configuration files have already been copied to the INFA_HOME\server\infa_shared\SrcFiles folder on the Informatica Server machine.

2. Open the file_customer_cost_line.csv file in the INFA_HOME\server\infa_shared\SrcFiles folder.

3. Replace and fill in the customer costing transactions that you want to load into the Customer Cost fact table, and save the file.

4. Open the file_product_cost_line.csv file in the INFA_HOME\server\infa_shared\SrcFiles folder.

5. Replace and fill in the product costing transactions that you want to load into the Product Cost fact table, and save the file.
The other files file_xact_type.csv, file_chnl_type.csv, and FILE_DOMAIN.csv file contain the default values of transaction types, channel types, and related domain values. You can leave these files untouched unless you want to customize the values.

Note: These CSV files are the source data for the Customer / Product Cost Line mappings in SDE_Universal_Adaptor. If the above configuration steps are not completed, then the mappings will fail.

45.2.4 Upgrade Issues and Workarounds for Oracle Business Intelligence Applications

This section describes issues and workarounds related to upgrading Oracle Business Intelligence from previous releases.

There are no known issues at this time.

45.2.5 Oracle Business Intelligence Applications Offering/Module-specific Issues

This section describes issues and workarounds related to specific Offerings or Modules in Oracle Business Intelligence. It includes the following topics:

- Section 45.2.5.1, "Issues for Oracle Customer Data Management Analytics Offering"

- Section 45.2.5.2, "Issues for Oracle Financial Analytics Offering"

- Section 45.2.5.3, "Issues for Oracle Human Resources Analytics Offering"

- Section 45.2.5.4, "Issues for Oracle Marketing Analytics Offering"

- Section 45.2.5.5, "Issues for Oracle Partner Analytics Offering"

- Section 45.2.5.6, "Issues for Oracle Product Information Management Analytics Offering"

- Section 45.2.5.7, "Issues for Oracle Procurement and Spend Analytics Offering"

- Section 45.2.5.8, "Issues for Oracle Project Analytics Offering"

- Section 45.2.5.9, "Issues for Oracle Sales Analytics Offering"

- Section 45.2.5.10, "Issues for Oracle Supply Chain and Order Management Analytics Offering"

45.2.5.1 Issues for Oracle Customer Data Management Analytics Offering

This section describes issues and workarounds related to Oracle Customer Data Management Analytics Offering.

There are no known issues at this time.

45.2.5.2 Issues for Oracle Financial Analytics Offering

This section describes issues and workarounds related to Oracle Financial Analytics Offering.

45.2.5.2.1 Overlapping Aging Bucket Ranges in AP/AR Aging

This issue applies to Releases 11.1.1.5.0 and 11.1.1.5.2.

Oracle Financial Analytics Fusion Edition does not support overlapping aging bucket ranges. When you set up aging buckets in Fusion Applications, you must use only non-overlapping aging buckets for AP and AR aging analysis in Financial Analytics. Also, when buckets are defined to separate out due and overdue amounts in different buckets, make sure that the days_from value and days_to value for a bucket are defined so that it takes either due or overdue transactions, but not both. To do this, make sure the days_from for overdue buckets start from 1 or a positive number, not from 0 or a negative number. Here are few examples to illustrate the supported aging bucket ranges.

Supported:

a) -60 days to -31 days
b) -30 days to -11 days
c) -10 days to 0 days
d) 1 days to 10 days
e) 11 days to 30 days
f) 31 days to 60 days and so on.

In this example, a/b/c are 'due' buckets and d/e/f are 'overdue' buckets. The bucket ranges are defined correctly with no overlaps and all overdue buckets start from 1 or above.

Not Supported:

a) -60 days to -31 days
b) -30 days to -11 days
c) -10 days to -1 days
d) 0 days to 10 days
e) 9 days to 30 days
f) 31 days to 60 days and so on.

In this example, the bucket ranges are not defined correctly. Note that bucket d starts from 0. So this bucket could hold some invoices that are due and some that are overdue. Thus a report that shows only overdue buckets could include some invoices that are not overdue. Furthermore, buckets d and e are overlapping. Therefore, some invoices could be reported in both buckets, thus making the total outstanding amount appear larger than it is.

Not Supported:

a) -60 days to -31 days
b) -30 days to -11 days
c) -10 days to -6 days
d) -5 days to 5 days
e) 6 days to 30 days
f) 31 days to 60 days and so on.

In this example, the bucket ranges are not defined correctly. Here, bucket d starts from a negative number and ends with a positive number. Similar to the previous example, this bucket could hold some invoices that are due and some that are overdue.

Workaround

There is no workaround for this issue. Defining aging buckets in any of these "Not Supported" patterns could show misleading numbers in aging reports that use these aging buckets.

45.2.5.3 Issues for Oracle Human Resources Analytics Offering

This section describes issues and workarounds related to Oracle Human Resources Analytics Offering.

45.2.5.3.1 Incorrect Metrics Showing Current Year

This issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2.

The following metrics are incorrectly showing the current year, not the prior year value:

Length of Service (Years) YAGO

Average Length of Service (Years) YAGO

% Change Average Length of Service (Years) YAGO

Workaround

There is no workaround for this issue.

45.2.5.3.2 Member Mappings Not Displayed For FSM Tasks Relating to Ranged Domains

This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2 and 11.1.1.6.

In FSM, if you click Go to Task for a Task that is related to a ranged Domain for the first time in a browser session, then the Domain Member Mappings are not displayed, and the message 'No rows returned' is displayed. For example, in Human Resources Analytics Fusion Edition, the Task 'Manage Domains and Member Mappings for Age Band Dimension'.

Workaround

Close the Manage Domain and Mappings dialog, then re-select the Task in FSM by clicking Go to Task.

45.2.5.4 Issues for Oracle Marketing Analytics Offering

This section describes issues and workarounds related to Oracle Marketing Analytics Offering.

There are no known issues at this time.

45.2.5.5 Issues for Oracle Partner Analytics Offering

This section describes issues and workarounds related to Oracle Partner Analytics Offering.

There are no known issues at this time.

45.2.5.5.1 ETL Failure in SDE_FUSION_PRM_PartnerResourceHelper Task

During ETL, the task SDE_FUSION_PRM_PartnerResourceHelper fails.

Workaround

1. In Informatica PowerCenter Workflow Manager, connect to the repository and open the SDE_FUSION_V1_Adaptor.

2. Edit the workflow SDE_FUSION_PRM_PartnerResourceHelper_Full.

3. On the Mapping Tab, click Sources on the left menu, and navigate to the Properties on the right.

4. Click the Value field 'downward arrow icon' for the Attribute 'Sql Query'.

5. Make sure that the SQL statement matches the following correct SQL statement.
Correct SQL statement:

SELECT PartnerAccountResourcePEOCreatedBy,
PartnerAccountResourcePEOCreationDate,
PartnerAccountResourcePEOLastUpdateDate,
PartnerAccountResourcePEOLastUpdatedBy,
PartnerAccountResourcePEOPAcctResourceId,
PartnerAccountResourcePEOResourceId,
PartnerAccountResourcePEOResourceOrgId,
PartnerAccountPEOPartnerPartyId,
'0' as X_CUSTOM
from "$$CRMPILLAR"..."CrmAnalyticsAM.PartnerCenterAnalyticsAM.PartnerAccountResourcePVO" PartnerAccountResourcePVO
WHERE PartnerAccountResourcePVO.PartnerAccountResourcePEOCreationDate >
$$INITIAL_EXTRACT_DATE

For example, the original SQL statement might have more than one VO in the query, as in the following incorrect SQL statement.

Example incorrect SQL statement:

SELECT
PartnerAccountResourcePEOCreatedBy,
PartnerAccountResourcePEOCreationDate,
PartnerAccountResourcePEOLastUpdateDate,
PartnerAccountResourcePEOLastUpdatedBy,
PartnerAccountResourcePEOPAcctResourceId,
PartnerAccountResourcePEOResourceId,
PartnerAccountResourcePEOResourceOrgId,
PartnerAccountPEOPartnerPartyId,
UserGuid,
'0' as X_CUSTOM
from
"$$CRMPILLAR"..."CrmAnalyticsAM.PartnerCenterAnalyticsAM.PartnerAccountResourcePVO",
"$$CRMPILLAR"..."CrmAnalyticsAM.PartiesAnalyticsAM.PartyPerson"
WHERE
PartnerAccountResourcePEOResourceId = PartyId

45.2.5.6 Issues for Oracle Product Information Management Analytics Offering

This section describes issues and workarounds related to Oracle Product Information Management Analytics Offering.

There are no known issues at this time.

45.2.5.7 Issues for Oracle Procurement and Spend Analytics Offering

This section describes issues and workarounds related to Oracle Procurement and Spend Analytics Offering.

45.2.5.7.1 Null Values Included In Level-Based Metric Report

This issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2.

If you create a report that includes a level-based metric, then the report might include null records. For example, when reporting the level-based metric 'Agreed Amount at Header Level' with 'Product Name', the filter of "Product Name" LIKE '%zBIA%' does not filter out the records with Product Name as null.

Workaround

Add an extra filter IS NOT NULL to exclude null records. For example, if you report against the level based metric 'Agreed Amount at Header Level' with 'Product Name', add the following filter:

...
WHERE (("Product"."Product Name" LIKE '%zBIA%') AND ("Product"."Product Name" IS NOT NULL))
...

45.2.5.8 Issues for Oracle Project Analytics Offering

This section describes issues and workarounds related to Oracle Project Analytics Offering.

There are no known issues at this time.

45.2.5.9 Issues for Oracle Sales Analytics Offering

This section describes issues and workarounds related to Oracle Sales Analytics Offering.

There are no known issues at this time.

45.2.5.10 Issues for Oracle Supply Chain and Order Management Analytics Offering

This section describes issues and workarounds related to Oracle Supply Chain and Order Management Analytics Offering.

- Obsolete Task in Supply Chain and Order Management Analytics Fusion Edition in Releases 11.1.1.5.1 and 11.1.1.5.2.
In Functional Setup Manager for Oracle BI Applications, the "Supply Chain and Order Management Analytics Fusion Edition" task list > "Order Management Functional Area Specific Configurations" task list displays the following task:

"Configure Reporting Parameters for Default Aging Method displayed in AR Aging Reports"

This task is obsolete and should be ignored. No functional configuration is required for this task. Invoking this task via the 'Go to Task' button displays the Reporting Parameters UI with no rows.

45.2.6 Translated Content in Non-English Reports and Dashboards

This issue applies to Release 11.1.1.7.0.

If you are using Oracle BI Applications reports and dashboards in non-English languages, then some repository and catalog strings are not translated.

Workaround

There is no workaround for this issue.

45.2.7 Error in Execution of Task SDE_FUSION_PayrollRunBalanceDetailFact

This issue applies to Release 11.1.1.7.0.

If the task SDE_FUSION_PayrollRunBalanceDetailFact does not execute, then you must disable the post connection script for the HCM_OLTP database, as specified in the Workaround.

Workaround

Using Oracle BI Administration Tool, specify the following two SQL Bypass statements for the HCM_OLTP database:

alter session set "_with_subquery"='inline';
alter session set cursor_sharing='FORCE';

45.2.8 Oracle Business Intelligence Applications Configuration Manager and FSM Issues

This section describes issues and workarounds related to Oracle Business Intelligence Applications Configuration Manager.

- The following tasks in FSM for Oracle BI Applications are not translated:
This issue applies to Release 11.1.1.6.

- For language FINNISH (Finland) LANGUAGE_CODE = 'SF', un-translated FSM task name - 'Manage Domains and Member Mappings for Employee Dimension', description - 'Manage Domains and Member Mappings for Employee Dimension'.

- For language CZECH (Czech Republic) LANGUAGE_CODE = 'CS', un-translated FSM task name - 'How to Integrate Procurement and Spend Analytics with Spend Classification' , description - 'How to Integrate Procurement with Spend Analytics with Spend Classification'.

- For language BRAZILLIAN PORTUGUESE (Brazil) LANGUAGE_CODE = 'PTB', un-translated FSM task name - 'Manage Domains and Member Mappings for Employee Dimension' , description - 'Manage Domains and Member Mappings for Employee Dimension'.

- For language TURKISH (Turkey) LANGUAGE_CODE = 'TR', un-translated FSM task name - 'Manage Domains and Member Mappings for Transaction Type Dimension' and description = 'Configure Domain and Member Mappings for Transaction Type Dimension'.

- For language NORWEGIAN (Norway) LANGUAGE_CODE = 'N', un-translated FSM task name - 'Manage Domains and Member Mappings for Employee Dimension' and description = 'Manage Domains and Member Mappings for Employee Dimension'.

- For language HEBREW (Israel) LANGUAGE_CODE = 'IW', un-translated FSM task name - 'Overview of Human Resources Analytics Fusion Edition' and description = 'Overview of Human Resources Analytics Fusion Edition'.

- For language GREEK (Greece) LANGUAGE_CODE = 'EL', un-translated FSM filter name - 'Payroll Functional Area' and description = 'Enables Payroll Functional Area'.

- On First Login Task Pane Options Are Inactive When Overview Page Is Loading
This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6.

When a user first user logs into Oracle BI Applications Configuration Manager, the options on the Tasks pane are inactive while the Overview page is loading.

Workaround

There is no workaround for this issue.

However, once a user is logged in and navigates back to the Overview page, the options on the Task pane are active while the Overview page is loading.

- Cancel Option On Export and Import Dialog Does Not Cancel The Process
This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6.

This issue affects the Setup Data Export\Export Setup Data option and the Setup Data Export\Import Setup Data option that are available on the Tasks pane. If you click Cancel on the Export Data dialog after first clicking Export, then the dialog is cancelled but the Export process continues. If you click Cancel on the Import Data dialog after first clicking OK, then the dialog is cancelled but the Import process continues.

Workaround

There is no workaround for this issue.

- Edit Icon Enabled Without Parameter Selection on Data Load Parameters Dialog
This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6.

Clicking the 'Go to Task' icon for a Task for Data Load Parameters in Functional Setup Manager (FSM) displays the Task pane with the Data Load Parameters displayed in the master table. A Parameter row in the Master table is not selected by default but the Edit icon is enabled. On clicking the Edit Icon, the Edit dialog is launched with no parameter details.

Workaround

Before clicking the Edit icon, select a parameter in the Master table.

- Import Of Incorrect Zip File Reports No Error
This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6.

This issue applies to the Setup Data Export and Import\Import Setup Data option on the Tasks bar of Oracle BI Applications Configuration Manager. Importing a zip file that is not related to export/import data does not result in an error message.

Workaround

Before you import Setup Data, make sure the Zip file that you import contains valid Setup Data.

- Duration (ms) Column For Import/Export Dialogs Not Formatted With Browser Language Setting
This issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2.

This issue affects the Setup Data Export\Export Setup Data option and the Setup Data Export\Import Setup Data option that are available on the Tasks pane. The Export Duration (ms) column on the Export Setup Data page and Import Duration (ms) column on the Import Setup Data page are not formatted as per current browser language settings.

Workaround

There is no workaround for this issue.

- Search Pane Dropdown Selection List If Dropdown List Is Still Refreshing
This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6.

On the Search pane of BI Applications Configuration Manager, when you select a BI Application in the BI Application drop-down list, you can still select options in other search fields while those fields are being refreshed, even though the busy hour glass cursor is displayed.

Workaround

Oracle recommends that you always wait for fields to refresh before selecting values.

- Date Format On Manage Data Load Parameter Does Not Honor Browser Language Setting
This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6.

This issue affects the Manage Data Load Parameters option on the Tasks bar. The Date format for Date parameters on the Manage Date Load Parameters" dialog always displays as "yyyy-mm-dd" irrespective of current browser language settings.

Workaround

There is no workaround for this issue.

45.2.9 Security-related Issues for Oracle Business Intelligence Applications

This section describes issues and workarounds related to upgrading Oracle Business Intelligence from previous releases.

There are no known issues at this time.

45.2.10 Oracle Business Intelligence Applications Documentation Errata

This section describes errata in Oracle Business Intelligence documentation and help systems. It includes the following topics:

- Section 45.2.10.1, "General Oracle Business Intelligence Documentation Errata"

- Section 45.2.10.2, "Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications"

- Section 45.2.10.3, "Oracle BI Applications Configuration Manager Help System"

- Section 45.2.10.4, "Oracle Fusion Middleware Reference Guide for Oracle Business Intelligence Applications"

45.2.10.1 General Oracle Business Intelligence Documentation Errata

This section describes general errata in the Oracle Business Intelligence documentation.

There are no known issues at this time.

45.2.10.2 Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications

This section describes documentation errata in Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications.

Note: In Release 11.1.1.5.2, the equivalent guide is named Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications.

- This issue applies to Releases 11.1.1.5.2, 11.1.1.6.0, and 11.1.1.6.2 and to the Oracle Business Intelligence Applications Configuration Manager and Functional Setup Manager Help for those releases.
Section B.27.1 Configuring the BI Extender includes an erroneous cross-reference to Oracle Business Intelligence Server Administration Guide. This cross-reference should link to the Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (Oracle Fusion Applications Edition).

- In Release 11.1.1.6.2 of the Oracle Business Intelligence Applications Installation Guide, content is missing from Appendix A, Section 7.3, Locations of Installation Files for Informatica PowerCenter and Hotfix 2. After the sentence "The PowerCenter folder contains the following files:" the following four points were omitted from the documentation.

- Informatica PowerCenter Services Version 9.1 Hotfix 2 (OS-specific files).

- Informatica PowerCenter Services Version 9.1 Hotfix 2 (Windows only).

- Informatica Documentation.

- Informatica License Key.

- In Section 3.4.8.1 'How to Install DAC Client', the location of the Oracle BI Applications Client Installer is stated as <BI Oracle Home>/clients/biappsclients. This location should be:
- On Windows, in the folder <Install Repository>\biappsshiphome\shiphome.

- On Linux and UNIX. in the folder <Install Repository>/biappsshiphome/dist/stage/clients/biappsclients.

- In Section 3.4.2.1 'Creating Oracle BI Applications Schemas Using Oracle BI Applications RCU', Step 10 should read as follows:
10. In the Schema Passwords screen, specify and confirm a password for the schemas.

Note: It is not necessary to select the Use same password for all schemas option.

- In Section 3.4.8.3 'How to log into DAC Client for the first time', Step 7 should read as follows:
7. Use the User name and Password fields to specify the credentials of a user that has been granted the role 'BI Applications Administrator Duty'.

Note: Users are set up with appropriate roles in step Section 3.4.7, "Setup Step: Grant User Access to Oracle BI Applications Components".

- In Section 4.2.4 Overview of Tasks for Setting Up Oracle Business Intelligence Applications, after completing the high-level tasks in this section, before you start ETL processes you must start or restart the following components: Node Manager, Admin Server, Managed Server, and BI services (that is, OPMN).

- Section 4.3.2.1 'Creating Oracle BI Applications Schemas Using Oracle BI Applications RCU' should include the following information about the location of the Oracle BI Applications RCU zip file:
The Oracle BI Applications RCU zip file named rcuHomeBIApps.zip is located in the Fusion Applications software repository under installers/biapps_rcu/<OS - either Linux or Window>. (The Fusion Applications software repository is obtained when you download and unzip the Oracle Fusion Applications 11g parts available in the Oracle Fusion Applications Media Pack on the Oracle Software Delivery Cloud.) Extract this zip file into a folder, for example, BIA_RCU_HOME.

- Section 4.3.4.2 'Locations of Installation Files for Informatica PowerCenter and Hotfix 11' should read as follows:
The Informatica PowerCenter 8.6.1 and HotFix 11 installation files, license key, and user documentation are provided as zip files. These zip files are located in the Fusion Applications software repository under /installers/powercenter. (The Fusion Applications software repository is obtained when you download and unzip the Oracle Fusion Applications 11g parts available in the Oracle Fusion Applications Media Pack on the Oracle Software Delivery Cloud.)

The powercenter folder contains four Informatica PowerCenter zip files. Informatica PowerCenter 8.6.1 Client Tools install files are available in V22464-01_1of2.zip. The HotFix 11 files for PowerCenter Client Tools are available in V22464-01_2of2.zip. The other two zip files contain the operating system-specific files for Informatica PowerCenter Services. The first of these zip files in each media pack (1of2.zip) includes the Informatica PowerCenter Services 8.6.1 install files. The second of the zip files (2of2.zip) includes the Informatica documentation, the license key, and the HotFix 11 installation file for PowerCenter Services.

- Section 4.3.5 'Step 5: Install Oracle BI Administration Tool', should include the following information about the location of the Oracle BI Client Installer executable:
You install Oracle BI Administration Tool using the Oracle Business Intelligence Enterprise Edition Plus Client Installer. The Oracle BI Client Installer executable is named biee_client_install.exe and this file is available in the installed BI Middleware Home: bi/clients/biserver.

- This issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2.
Section 4.3.9 'Step 9: Create a User for ETL' refers erroneously to FUSION_APPS_OBIA_BIEE_APPID as a User instead of a Group, and should read as follows:

The Extract Transform and Load (ETL) process must be run by a user with appropriate data security privileges granted on the Fusion Application tables from which data is extracted into Oracle Business Analytics Warehouse. For this purpose, the Group named FUSION_APPS_OBIA_BIEE_APPID is provisioned during install with the appropriate ETL security privileges (by default, this Group is mapped to the Duty Role named OBIA_EXTRACT_TRANSFORM_LOAD_DUTY).

To create a user for ETL:

1. Use Oracle Identity Management (or an appropriate security tool) to create a new user and password.
For example, you might create a new user named OBIA_ETL_USER.

2. Make the user a member of the Group FUSION_APPS_OBIA_BIEE_APPID.
For example, you might assign the user OBIA_ETL_USER to the group FUSION_APPS_OBIA_BIEE_APPID.

3. Make a note of the user's credentials.
These credentials are used to configure connections in DAC and Informatica later in the setup process.

- Section 4.3.12 'Step 12: Install DAC Client' should include the following information about the location of the Oracle BI Applications Client installer:
Step 1 should be: Download the part for the Oracle BI Applications Client Installer from the Oracle Fusion Applications Media Pack on Oracle Software Delivery Cloud.

- In Section 4.3.7 Step 7: Configure the Oracle BI Repository File (RPD), the description for the DW_DB_CONNECT value includes a JDBC string as an example. This example should include the following OCI/TNS string:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl)))

- The issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2.
In Section 4.5.8 Extending the BI Domain, the parameter descriptions for MDS_DB_SCHEMA and MDS_DB_URL for the install_dwtools.py script should refer to the Fusion Applications schema, not the platform MDS schema. These parameter descriptions should read:

MDS_DB_SCHEMA is the schema for the Fusion Applications schema (that is, not the platform MDS schema). This schema was created during the provisioning of Oracle Business Intelligence, as part of the Oracle Fusion Applications installation process. For example, DEV11G_MDS.

MDS_DB_URL is the connection string for the Fusion Applications schema (that is, not the platform MDS schema). This schema was created during the provisioning of Oracle Business Intelligence, as part of the Oracle Fusion Applications installation process. For example, machine12345.company.com.example:1521:BIA11G.

45.2.10.3 Oracle BI Applications Configuration Manager Help System

This section describes documentation errata in the Oracle BI Applications Configuration Manager Help System.

There are no known issues at this time.

45.2.10.4 Oracle Fusion Middleware Reference Guide for Oracle Business Intelligence Applications

This section describes documentation errata in Oracle Fusion Middleware Reference Guide for Oracle Business Intelligence Applications.

- Section B.27.1 Configuring the BI Extender includes an erroneous cross-reference to Oracle Business Intelligence Server Administration Guide. This cross-reference should link to the Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (Oracle Fusion Applications Edition).
This issue applies to Releases 11.1.1.5.2, 11.1.1.6.0, and 11.1.1.6.2 and to the Oracle Business Intelligence Applications Configuration Manager and Functional Setup Manager Help for those releases.

- In Release 11.1.1.6.2 of the Oracle Business Intelligence Applications Installation Guide, content is missing from Appendix A, Section 7.3, Locations of Installation Files for Informatica PowerCenter and Hotfix 2. After the sentence "The PowerCenter folder contains the following files:" the following four points were omitted from the documentation.

- Informatica PowerCenter Services Version 9.1 Hotfix 2 (OS-specific files).

- Informatica PowerCenter Services Version 9.1 Hotfix 2 (Windows only).

- Informatica Documentation.

- Informatica License Key.

- In Section 3.4.8.1 'How to Install DAC Client', the location of the Oracle BI Applications Client Installer is stated as <BI Oracle Home>/clients/biappsclients. This location should be:
- On Windows, in the folder <Install Repository>\biappsshiphome\shiphome.

- On Linux and UNIX. in the folder <Install Repository>/biappsshiphome/dist/stage/clients/biappsclients.

- In Section 3.4.2.1 'Creating Oracle BI Applications Schemas Using Oracle BI Applications RCU', Step 10 should read as follows:
10. In the Schema Passwords screen, specify and confirm a password for the schemas.

Note: It is not necessary to select the Use same password for all schemas option.

- In Section 3.4.8.3 'How to log into DAC Client for the first time', Step 7 should read as follows:
7. Use the User name and Password fields to specify the credentials of a user that has been granted the role 'BI Applications Administrator Duty'.

Note: Users are set up with appropriate roles in step Section 3.4.7, "Setup Step: Grant User Access to Oracle BI Applications Components".

- In Section 4.2.4 Overview of Tasks for Setting Up Oracle Business Intelligence Applications, after completing the high-level tasks in this section, before you start ETL processes you must start or restart the following components: Node Manager, Admin Server, Managed Server, and BI services (that is, OPMN).

- Section 4.3.2.1 'Creating Oracle BI Applications Schemas Using Oracle BI Applications RCU' should include the following information about the location of the Oracle BI Applications RCU zip file:
The Oracle BI Applications RCU zip file named rcuHomeBIApps.zip is located in the Fusion Applications software repository under installers/biapps_rcu/<OS - either Linux or Window>. (The Fusion Applications software repository is obtained when you download and unzip the Oracle Fusion Applications 11g parts available in the Oracle Fusion Applications Media Pack on the Oracle Software Delivery Cloud.) Extract this zip file into a folder, for example, BIA_RCU_HOME.

- Section 4.3.4.2 'Locations of Installation Files for Informatica PowerCenter and Hotfix 11' should read as follows:
The Informatica PowerCenter 8.6.1 and HotFix 11 installation files, license key, and user documentation are provided as zip files. These zip files are located in the Fusion Applications software repository under /installers/powercenter. (The Fusion Applications software repository is obtained when you download and unzip the Oracle Fusion Applications 11g parts available in the Oracle Fusion Applications Media Pack on the Oracle Software Delivery Cloud.)

The powercenter folder contains four Informatica PowerCenter zip files. Informatica PowerCenter 8.6.1 Client Tools install files are available in V22464-01_1of2.zip. The HotFix 11 files for PowerCenter Client Tools are available in V22464-01_2of2.zip. The other two zip files contain the operating system-specific files for Informatica PowerCenter Services. The first of these zip files in each media pack (1of2.zip) includes the Informatica PowerCenter Services 8.6.1 install files. The second of the zip files (2of2.zip) includes the Informatica documentation, the license key, and the HotFix 11 installation file for PowerCenter Services.

- Section 4.3.5 'Step 5: Install Oracle BI Administration Tool', should include the following information about the location of the Oracle BI Client Installer executable:
You install Oracle BI Administration Tool using the Oracle Business Intelligence Enterprise Edition Plus Client Installer. The Oracle BI Client Installer executable is named biee_client_install.exe and this file is available in the installed BI Middleware Home: bi/clients/biserver.

- Section 4.3.12 'Step 12: Install DAC Client' should include the following information about the location of the Oracle BI Applications Client installer:
Step 1 should be: Download the part for the Oracle BI Applications Client Installer from the Oracle Fusion Applications Media Pack on Oracle Software Delivery Cloud.

- This issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2.
Section 4.3.9 'Step 9: Create a User for ETL' refers erroneously to FUSION_APPS_OBIA_BIEE_APPID as a User instead of a Group, and should read as follows:

The Extract Transform and Load (ETL) process must be run by a user with appropriate data security privileges granted on the Fusion Application tables from which data is extracted into Oracle Business Analytics Warehouse. For this purpose, the Group named FUSION_APPS_OBIA_BIEE_APPID is provisioned during install with the appropriate ETL security privileges (by default, this Group is mapped to the Duty Role named OBIA_EXTRACT_TRANSFORM_LOAD_DUTY).

To create a user for ETL:

1. Use Oracle Identity Management (or an appropriate security tool) to create a new user and password.
For example, you might create a new user named OBIA_ETL_USER.

2. Make the user a member of the Group FUSION_APPS_OBIA_BIEE_APPID.
For example, you might assign the user OBIA_ETL_USER to the group FUSION_APPS_OBIA_BIEE_APPID.

3. Make a note of the user's credentials.
These credentials are used to configure connections in DAC and Informatica later in the setup process.

- In Section 4.3.7 Step 7: Configure the Oracle BI Repository File (RPD), the description for the DW_DB_CONNECT value includes a JDBC string as an example. This example should include the following OCI/TNS string:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl)))

- The issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2.
In Section 4.5.8 Extending the BI Domain, the parameter descriptions for MDS_DB_SCHEMA and MDS_DB_URL for the install_dwtools.py script should refer to the Fusion Applications schema, not the platform MDS schema. These parameter descriptions should read:

MDS_DB_SCHEMA is the schema for the Fusion Applications schema (that is, not the platform MDS schema). This schema was created during the provisioning of Oracle Business Intelligence, as part of the Oracle Fusion Applications installation process. For example, DEV11G_MDS.

MDS_DB_URL is the connection string for the Fusion Applications schema (that is, not the platform MDS schema). This schema was created during the provisioning of Oracle Business Intelligence, as part of the Oracle Fusion Applications installation process. For example, machine12345.company.com.example:1521:BIA11G.

- The section A.7.3 'Locations of Installation Files for Informatica PowerCenter and Hotfix 2' is missing the following information after the sentence "The PowerCenter folder contains the following files:":

- OS-specific Server install file - 910HF2_Server_Installer_<OS.zip or tar>

- 910HF2_Client_Installer_win32-x86.zip (Windows only)

- Informatica Documentation (Infa91Docs.zip)

- Informatica License Key

Note:

The Informatica PowerCenter installer for Services and Client installs both version 9.1 and HotFix 2.

45.3 Oracle Business Intelligence Data Warehouse Administration Console (DAC) Platform Release Notes

This section describes issues associated specifically with Oracle Business Intelligence Data Warehouse Administration Console platform. It includes the following sections:

- Section 45.3.1, "DAC Issues and Workarounds Identified Since the Previous Revision"

- Section 45.3.2, "DAC General Issues and Workarounds"

- Section 45.3.3, "DAC Installation Issues and Workarounds"

- Section 45.3.4, "DAC Upgrade Issues and Workarounds"

- Section 45.3.5, "DAC Documentation Errata"

45.3.1 DAC Issues and Workarounds Identified Since the Previous Revision

There are no known issues identified since the previous revision.

45.3.2 DAC General Issues and Workarounds

This section describes general issues and workarounds related to DAC.

There are no known issues at this time.

45.3.3 DAC Installation Issues and Workarounds

This section describes issues and workarounds related to installing DAC.

There are no known issues at this time.

45.3.4 DAC Upgrade Issues and Workarounds

This section describes issues and workarounds related to upgrading DAC from previous releases.

There are no known issues at this time.

45.3.5 DAC Documentation Errata

This section describes errata in DAC documentation and help systems. It includes the following topics:

- Section 45.3.5.1, "Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console"

- Section 45.3.5.2, "DAC Client Help System"

45.3.5.1 Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console

This section describes documentation errata in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.

Accessing the DAC Server Using the Command Line

This issue applies to release 11.1.1.6.x and 11.1.1.7.0.

- In the section "Setting Up the Command Line to Access the DAC Server," step 2 should read as follows:
Copy the following files from the <Domain_Home> directory to a local directory:

- dac\lib

- dac\DAWSystem.jar

- dac\dac.properties

- dac\dacCmdLine.bat or dacCmdLine.sh

- dac\config.bat or config.sh

- dac\dac_env.cmd

- In the section "Using the Command Line to Access the DAC Server," the ETLStatus method requires an execution plan name to be specified.

45.3.5.2 DAC Client Help System

This section describes documentation errata in DAC Client Help System.

There are no known issues at this time.

46 Oracle Real-Time Decisions

This chapter describes issues associated with Oracle Real-Time Decisions (Oracle RTD), including issues related to Decision Studio, integration, and security.

This chapter includes the following topics:

- Section 46.1, "Oracle RTD General Issues and Workarounds"

- Section 46.2, "Oracle RTD Installation Issues and Workarounds"

- Section 46.3, "Oracle RTD Upgrade Issues and Workarounds"

- Section 46.4, "Oracle RTD Configuration Issues and Workarounds"

- Section 46.5, "Oracle RTD Security Issues and Workarounds"

- Section 46.6, "Oracle RTD Administration Issues and Workarounds"

- Section 46.7, "Oracle RTD Integration Issues and Workarounds"

- Section 46.8, "Oracle RTD Decision Studio Issues and Workarounds"

- Section 46.9, "Oracle RTD Decision Center Issues and Workarounds"

- Section 46.10, "Oracle RTD Performance Monitoring Issues and Workarounds"

- Section 46.11, "Oracle RTD Externalized Objects Management Issues and Workarounds"

- Section 46.12, "Oracle RTD Localization Issues and Workarounds"

- Section 46.13, "Oracle RTD Documentation Errata"

- Section 46.14, "Oracle RTD Third-Party Software Information"

Depending on your Oracle Fusion Middleware implementation, some information in other chapters of this document might also be relevant, including:

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

- Chapter 3, "Upgrade"

- Chapter 4, "Oracle Fusion Middleware Administration"

- Chapter 5, "Oracle Enterprise Manager Fusion Middleware Control"

- Chapter 6, "Oracle Fusion Middleware High Availability and Enterprise Deployment"

46.1 Oracle RTD General Issues and Workarounds

This section describes general issues and workarounds related to Oracle RTD. It includes the following topics:

- Section 46.1.1, "Transient Likelihood Problems"

- Section 46.1.2, "Use Development Deployment State Only"

- Section 46.1.3, "Error Deploying Inline Services from Command Line if Inline Service Uses Certain Functions"

- Section 46.1.4, "Ensuring Unique Batch Names Across a Cluster"

- Section 46.1.5, "Safari and Chrome Accessibility Items"

- Section 46.1.6, "Learning Service May Skip Processing of Some Learning Records if SDDB is on Oracle RAC Database"

- Section 46.1.7, "External Rule Editor Does Not Work in Mozilla Firefox Version 16"

46.1.1 Transient Likelihood Problems

There are cases where non-mature predictive models will return an actual likelihood rather than NaN during the early life of a model. There are also some cases where mature predictive models will return NaN as opposed to actual likelihoods when the Randomize Likelihood option is enabled for a model. These situations are transient in nature and, in the latter case, do not outweigh the benefits of the Randomize Likelihood feature.

46.1.2 Use Development Deployment State Only

Deployment states will be deprecated in a future release. Until then, do not use any deployment state other than Development.

46.1.3 Error Deploying Inline Services from Command Line if Inline Service Uses Certain Functions

An Inline Service that uses one or more of the built-in functions Days Since Last Event, Days Since Last Event on Channel, Number of Recent Events, or Number of Recent Events on Channel cannot be deployed using the command-line deployer.

The workaround is as follows:

1. Navigate to the unzipped RTDdeploytool folder, for example, C:\<myDir>\OracleBI\RTDdeploytool.

2. Copy the includes folder from RTD_HOME\eclipse\plugins\com.sigmadynamics.studio_11.1.1.5.0 (for example, C:\OracleBI\RTD\eclipse\plugins\com.sigmadynamics.studio_11.1.1.5.0\includes) into the unzipped RTDdeploytool folder.

46.1.4 Ensuring Unique Batch Names Across a Cluster

It is a standard requirement for Inline Service names and batch names to be unique within a cluster.

After an Inline Service is copied within a cluster, batch names registered in the Inline Service can be changed manually to achieve uniqueness. This manual step is not required if the batch registration code in the Inline Service automatically generates the batch name from the new Inline Service name, as in the following generic examples:

batchAgent.registerBatch(
batchAgent.getInlineService().getName() + ".FeedBackBatchJob",
"com.<mycompany>.rtd.batch.FeedBackBatchJob",
FeedBackBatchJob.description,
FeedBackBatchJob.paramDescriptions,
FeedBackBatchJob.paramDefaults);

or

batchAgent.registerBatch(
Application.getApp().getName() + ".FeedBackBatchJob",
"com.<mycompany>.rtd.batch.FeedBackBatchJob",
FeedBackBatchJob.description,
FeedBackBatchJob.paramDescriptions,
FeedBackBatchJob.paramDefaults);

Note that all programs that may call the batch need to be made aware of the new batch name.

46.1.5 Safari and Chrome Accessibility Items

1. Special Safari Setting Must be Selected for Proper Keyboard Operation
After Safari has been installed, ensure that the following property is selected:

- Preferences > Advanced > Press Tab to highlight each item on a web page

If this property is not selected, some Rule Editor tabbing operations in a rule editor built with Oracle Application Development Framework and the External Rules Deployment Helper rule editor will not function correctly.

2. Unexpected Results for Alt + Down Arrow in Combo Boxes in Chrome and Safari browsers
The expected actions for Alt + Down Arrow in combo boxes (as found in Internet Explorer 9 and Firefox 10.0.5) are:

1. The combo box shows an expanded list of values.

2. The combo box allows Up and Down Arrow movement through the options, and the selection of a value from the list.

3. The screen does not update until the Enter key is depressed.

The following results were found for Chrome for Alt + Down Arrow in a combo box:

1. The combo box is not extended.

2. Using Up and Down Arrows changes the combo box value in place.

3. The screen updates with a combo box value change as the arrow keys are used.

The following results were found for Safari 5.1.7 for Alt + Down Arrow in a combo box:

1. The combo box is not extended.

2. Using Up and Down Arrows changes the combo box value in place.

3. The screen does not update until the value is selected and the Enter key is depressed.

3. JAWS May Not Work in Safari on Windows
For more information, refer to Freedom Scientific and Safari documentation.

4. JAWS Refresh Keys in Safari and Chrome
JAWS users should use <JAWS KEY> + escape and <JAWS KEY> + 3 to clear and input page object actions, especially with the Chrome and Safari browsers.

5. Chrome and Safari do not natively support Windows high contrast
Chrome needs an extension to support high contrast.

Safari needs a style sheet to support high contrast.

46.1.6 Learning Service May Skip Processing of Some Learning Records if SDDB is on Oracle RAC Database

The Oracle RTD database sequence SDLEARNING_SEQ definition does not impose strict order. In a RAC environment, this could mean gaps in the values for the sequence, which leads to possible Learning Service failures in properly processing the learning records.

The workaround for this case is to impose the Order option on the sequence SDLEARNING_SEQ. Specifically, a database user with the ALTER ANY SEQUENCE system privilege should issue the following command against the SDDB schema:

- ALTER SEQUENCE SDLEARNING_SEQ ORDER;

46.1.7 External Rule Editor Does Not Work in Mozilla Firefox Version 16

Impacted Release: 11.1.1.7

With Mozilla Firefox version 16 and later, the External Rule Editor does not work as documented. For example, selecting a left operand when creating a new rule causes a JavaScript error. The workaround for this issue is to use another supported browser.

46.2 Oracle RTD Installation Issues and Workarounds

There are no known issues at this time.

46.3 Oracle RTD Upgrade Issues and Workarounds

There are no known issues at this time.

46.4 Oracle RTD Configuration Issues and Workarounds

There are no known issues at this time.

46.5 Oracle RTD Security Issues and Workarounds

This section describes general issues and workarounds related to Oracle RTD and security. It includes the following topic:

- Section 46.5.1, "Decision Center Logout Not Redirected Correctly for Oracle Access Manager (OAM) 11g Form-Based Authentication"

46.5.1 Decision Center Logout Not Redirected Correctly for Oracle Access Manager (OAM) 11g Form-Based Authentication

When Webgate 10g against Oracle Access Manager (OAM) 11g is configured as the SSO provider for Oracle RTD Decision Center access, logging out of, then back into Decision Center should ask users for their user name and password credentials on the re-login. To ensure that this occurs correctly, you must configure the following Oracle RTD Decision Center resources in OAM/Webgate as public (unprotected or anonymous access): 1. Decision Center logout URI /ui/do/logout 2. Decision Center images /ui/images/*

For information on how to perform the configuration, see the topic "Managing Policies to Protect Resources and Enable SSO" in Oracle Fusion Middleware Administrator's Guide for Oracle Access Manager at the location:

http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15478/app_domn.htm#CHEIDJAF

46.6 Oracle RTD Administration Issues and Workarounds

There are no known issues at this time.

46.7 Oracle RTD Integration Issues and Workarounds

This section describes issues and workarounds related to Oracle RTD integration. It includes the following topic:

- Section 46.7.1, "Java Smart Client Run Configuration Changes Required for Different Properties Files"

46.7.1 Java Smart Client Run Configuration Changes Required for Different Properties Files

When setting up the Java Smart Client example, depending on the properties file you are using, you must make some changes to the run configuration in Decision Studio before you run the example.

Note:

<RTD_HOME> refers to the directory where you installed the client-side files, for example, C:\RTD_Tools.

The changes you must make in the Arguments tab require you to enter an explicit, full path name. Make sure that you replace <RTD_HOME> with the exact name of your client-side files installation directory.

If you are using sdclient.properties for your properties file, perform the following change:

- In the Arguments tab, add the following in the Program arguments box, replacing <RTD_HOME> with the exact name of your client-side files installation directory:

- -u "<RTD_HOME>\client\Client Examples\Java Client Example\lib\sdclient.properties"

If you are using sdjrfclient.properties for your properties file, perform the following changes:

- In the Arguments tab, add the following in the Program arguments box, replacing <RTD_HOME> with the exact name of your client-side files installation directory:

- -u "<RTD_HOME>\client\Client Examples\Java Client Example\lib\sdjrfclient.properties"

If you are using clientHttpEndPoints.properties for your properties file, perform the following changes:

- In the Arguments tab, add the following in the Program arguments box, replacing <RTD_HOME> with the exact name of your client-side files installation directory:

- -u "<RTD_HOME>\client\Client Examples\Java Client Example\lib\clientHttpEndPoints.properties"

- In the Classpath tab:

- Remove the existing project

- Add the following jar files: commons-code.jar, commons-httpclient.jar, commons-logging.jar, j2ee-client.jar, and rtd-ds-client.jar (if not already present).

- Add the project with defaults

46.8 Oracle RTD Decision Studio Issues and Workarounds

This section describes issues and workarounds related to Oracle RTD Decision Studio. It includes the following topics:

- Section 46.8.1, "Mapping Array Attributes in a Multi-Level Entity Hierarchy"

- Section 46.8.2, "Issues When Trying to Enable Caching for Some Entities"

- Section 46.8.3, "Terminate Active Sessions in Cluster Works Only on Decision Server Receiving Deployment Request"

46.8.1 Mapping Array Attributes in a Multi-Level Entity Hierarchy

A "parent-child" entity hierarchy is typically defined with the child entity as an attribute of the parent entity. When the child entity is an Array attribute, be careful to map the child Array attribute to its data source in the direct parent entity only. Assume, for example, a Customer with many Accounts, each of which has many Contracts. In Decision Studio, the Customer entity's Mapping tab may display the complete hierarchy as follows: - The Customer entity contains the Account entity as an Array attribute - The Account attribute contains the Contract entity as an Array attribute The Account entity's Mapping tab contains the Contract entity as an Array attribute.With this example, only map the Contract attribute in the Account entity's Mapping tab. Do not map the Contract attribute in the Customer entity's Mapping tab.

46.8.2 Issues When Trying to Enable Caching for Some Entities

There are known issues, which may result in compilation and runtime errors, with enabling entity caching where a number of design factors coincide:

- You have a multi-level entity hierarchy, and a child entity is an array attribute of a parent entity

- The data source for the child entity has no Input column defined

- You want to enable caching on the child entity

If possible, simplify the structure of the child entity, specifically the attributes that are mapped to the sources. If this is not possible, contact Oracle Support with details of your particular design configuration.

46.8.3 Terminate Active Sessions in Cluster Works Only on Decision Server Receiving Deployment Request

Deploying an Inline Service to a cluster with the "Terminate active sessions" option selected will terminate sessions on only the Decision Server that receives the Inline Service deployment request.

46.9 Oracle RTD Decision Center Issues and Workarounds

There are no known issues at this time.

46.10 Oracle RTD Performance Monitoring Issues and Workarounds

There are no known issues at this time.

46.11 Oracle RTD Externalized Objects Management Issues and Workarounds

There are no known issues at this time.

46.12 Oracle RTD Localization Issues and Workarounds

There are no known issues at this time.

46.13 Oracle RTD Documentation Errata

This section describes errata in Oracle RTD documentation and help systems. It includes the following topic:

- Section 46.13.1, "Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions"

- Section 46.13.2, "Oracle Fusion Middleware Platform Developer's Guide for Oracle Real-Time Decisions"

46.13.1 Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions

There are no known documentation errata at this time in the Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions.

46.13.2 Oracle Fusion Middleware Platform Developer's Guide for Oracle Real-Time Decisions

This section describes documentation errata in the Oracle Fusion Middleware Platform Developer's Guide for Oracle Real-Time Decisions. It includes the following topic:

- Section 46.13.2.1, "External Rules Development Helper Mismatch between Code and Manual Description"

- Section 46.13.2.2, "Save Choice IDs in Inline Services Rather Than Choices"

46.13.2.1 External Rules Development Helper Mismatch between Code and Manual Description

The External Rules Development Helper, currently released with the DC_Demo Inline Service, does not function as described in Section 17.2.8, "Setting Up the External Interface and Embedded Rule Editor" and Section 17.3, "Example of End to End Development Using Dynamic Choices and External Rules."

46.13.2.2 Save Choice IDs in Inline Services Rather Than Choices

The Getting Started tutorial chapters within Oracle Fusion Middleware Platform Developer's Guide for Oracle Real-Time Decisions store choices in session-tied entities. It is recommended that configurations only save IDs of choices instead of the full choice objects.

46.14 Oracle RTD Third-Party Software Information

This section provides third-party software information. It includes the following topic:

- Section 46.14.1, "Displaytag Download Location"

46.14.1 Displaytag Download Location

The third-party package Displaytag can be downloaded from http://displaytag.sourceforge.net.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, 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.