Oracle® Fusion Middleware

Release Notes for Oracle Business Intelligence

11g Release 1 (11.1.1)

E54551-03

September 2014

Contains information about known software issues and their workarounds for this release.

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

E54551-03

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

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, 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

1 Oracle Business Intelligence

- 1.1 Patch Requirements

- 1.1.1 Obtaining Patches from My Oracle Support

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

- 1.3 Which Releases Are Covered by These Release Notes?

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

- 1.3.2 Oracle Business Intelligence Issues and Workarounds that Apply to IBM AIX, Oracle Solaris and HP-UX

- 1.4 Oracle Business Intelligence General Issues and Workarounds

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

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

- 1.4.3 IBM LDAP Based Authentication is Not Supported on Linux x86-64 and Microsoft Windows x64 (64-Bit)

- 1.4.4 Oracle BI Server Fails to Start Due to Missing Connect String in tnsnames.ora File

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

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

- 1.4.7 The Microsoft ODBC Data Source Administrator Crashes While Closing

- 1.4.8 ODBC System DSN Set With a Wrong Driver Filepath on Microsoft Windows x64 (64-Bit)

- 1.4.9 Hyperion Financial Management Data Sources Only Available for Windows Deployments

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

- 1.4.11 Windows Native Authentication Not Supported with Full-Text Catalog Search with Oracle Secure Enterprise Search

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

- 1.4.13 Specifying Folder Names for Data-Loading the Catalog

- 1.4.14 SSL Not Available when Using Full-Text Search with Oracle Endeca Server

- 1.4.15 Issue with Email Notifications on Data Loads for Searching

- 1.4.16 Stopping a Data Load for Full-Text Searching with Oracle Endeca Server

- 1.4.17 Out of Memory Error When Crawling the Catalog

- 1.4.18 Multibyte Characters Are Displayed as NCR When Using Attribute Categories

- 1.4.19 Hebrew Fonts Might Be Displayed in the Wrong Direction on Windows

- 1.4.20 Problems Installing in Thai and Turkish Locales

- 1.4.21 Graph Subtypes Are Not Refreshed in BI Composer

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

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

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

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

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

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

- 1.4.26 Patch Available to Hide Selected Consistency Check Warnings

- 1.4.27 Issues with WebLogic LDAP User Passwords

- 1.4.28 Configuring the GUID Attribute in the Identity Store

- 1.4.29 Messages Might Be Garbled When Running WebLogic Command Files

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

- 1.4.31 Poor Performance Starting Up WebLogic Server

- 1.4.32 Analysis State Is Not Maintained for Breadcrumbs

- 1.4.33 Enhancements to Accessibility Features

- 1.4.34 Incorrect DataDirect License File for DataDirect 7.0.1 Drivers on Linux

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

- 1.4.36 Excel 2003 Support to Be Removed in Future Releases

- 1.5 Oracle Business Intelligence Installation Issues and Workarounds

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

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

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

- 1.5.4 Antivirus Software Might Block the Installation in a Windows Environment

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

- 1.5.6 Issues When Installing Oracle Business Intelligence on Windows 2008

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

- 1.5.8 Configuring DB2 to Support Multibyte Data

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

- 1.5.10 Job Manager Does Not Start Due to Insufficient Permissions on Windows Operating Systems

- 1.5.11 Oracle Essbase Fails to Start on Microsoft Windows x64 (64-Bit)

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

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

- 1.5.14 Job Manager Might Fail to Launch from the Start Menu

- 1.5.15 Job Manager Cannot Launch if the Client Tools Install Path Includes Multi-Byte Characters

- 1.5.16 Error Occurs When RCU is Invoked For a Second Time to Create Only MDS/Platform Schemas on IBM DB/2

- 1.5.17 Financial Reporting Print Server Not Enabled

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

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

- 1.5.20 Oracle Business Intelligence Installation Fails to Respond

- 1.5.21 Binaries Fail to Redirect the Output to Log File

- 1.6 Oracle Business Intelligence Upgrade Issues and Workarounds

- 1.6.1 General Upgrade Issues and Workarounds

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

- 1.6.1.2 Issues Exporting Large Data Sets to Microsoft Excel

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

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

- 1.6.2 Security-related Upgrade Issues and Workarounds

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

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

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

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

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

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

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

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

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

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

- 1.8 Oracle Business Intelligence Analyses and Dashboards Issues and Workarounds

- 1.8.1 General Analyses and Dashboards Issues and Workarounds

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

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

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

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

- 1.8.1.5 Scorecard Diagrams on Dashboard Pages Might Print as Tables

- 1.8.1.6 Using Maps with Column Selectors

- 1.8.1.7 Issue with Wrap-Around Feature for Maps

- 1.8.1.8 Inability to Delete Map Tiles in MapViewer

- 1.8.1.9 Support for Rendering Small Form-Factor Graphs

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

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

- 1.8.1.12 Interactions on Right-Click Menus Are Not Translated

- 1.8.1.13 Issues with the Alignment of Trellis Views

- 1.8.1.14 Characters in Trellis Title Display Incorrectly in Certain Languages

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

- 1.8.1.16 Items Not Supported When Using Custom Print Layouts

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

- 1.8.2 Actions Issues and Workarounds

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

- 1.8.2.2 UserScripts.js File Must Be Backed Up and Reinstated After Every Patch or Upgrade

- 1.8.3 Scorecards and KPI Issues and Workarounds

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

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

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

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

- 1.8.4 Agents Issues and Workarounds

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

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

- 1.8.5 Microsoft Office Integration Issues and Workarounds

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

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

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

- 1.8.5.4 Install a Language Pack for Non-English Languages

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

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

- 1.8.5.7 Double Column Cascading Results in Incorrect Display Values

- 1.8.5.8 Intermittent Timeout Errors

- 1.8.5.9 Lack of Support for Vary Color By Target Area

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

- 1.8.5.11 Stacked Graphs Do Not Display Negative Values

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

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

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

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

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

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

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

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

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

- 1.8.5.21 Column Data in Section Edge Is Not Obtained

- 1.9 Oracle Business Intelligence Mobile Issues and Workarounds

- 1.10 Oracle Business Intelligence Mobile App Designer Issues and Workarounds

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

- 1.11.1 General Oracle BI Publisher Issues and Workarounds

- 1.11.1.1 JDBC Driver Throws Unsupported Function for setBigDecimal

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

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

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

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

- 1.11.1.6 Issues with Viewing Some Report Formats on Apple iPad

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

- 1.11.1.8 Components Folder Missing from SampleApp Lite Web Catalog

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

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

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

- 1.11.1.12 Search Might Return Incorrect Number of Results

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

- 1.11.1.14 Additional Setup for BI Publisher Desktop Tools in 11.1.1.6.2

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

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

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

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

- 1.11.1.19 Excel Analyzer and Online Analyzer Deprecated in Release 11.1.1.7

- 1.11.2 Oracle BI Publisher Security Issues and Workarounds

- 1.11.2.1 Limitations for Administrator Username in LDAP Security Model

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

- 1.11.3 Oracle BI Publisher Delivery Manager Issues and Workarounds

- 1.11.4 Oracle BI Publisher Scheduler Issues and Workarounds

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

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

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

- 1.11.5 Oracle BI Publisher RTF Template Issues and Workarounds

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

- 1.11.6 Oracle BI Publisher Excel Template Issues and Workarounds

- 1.11.6.1 Limitations for Excel Template Output on Apple iPad

- 1.11.7 Oracle BI Publisher Desktop Tools Issues and Workarounds

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

- 1.11.7.2 Excel Analyzer Does Not Support 64-Bit Windows Platform

- 1.11.8 Oracle BI Publisher Layout Editor Issues and Workarounds

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

- 1.11.8.2 Interactive Viewer Might Return Unexpected Results from Formula Columns

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

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

- 1.11.9 Oracle BI Publisher Data Model Issues and Workarounds

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

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

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

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

- 1.11.10 Oracle BI Publisher Report Building Issues and Workarounds

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

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

- 1.11.11 Oracle BI Publisher Documentation Errata

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

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

- 1.12 Oracle Business Intelligence Metadata Repository Development Issues and Workarounds

- 1.12.1 General Metadata Repository Development Issues and Workarounds

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

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

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

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

- 1.12.1.5 Must Use JDBC Connection String When Importing from Oracle OLAP

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

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

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

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

- 1.12.1.10 Create Aggregates Operations Can Time Out for TimesTen Targets

- 1.12.1.11 Logical Display Folders Are Deleted During MUD Publish

- 1.12.2 Oracle BI Server Issues and Workarounds

- 1.12.2.1 Oracle Call Interface (OCI) Issue Causes Oracle BI Server Crash on Windows when Under Heavy Load and Connecting to Oracle Database 11g

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

- 1.12.3 Oracle BI Administration Tool Issues and Workarounds

- 1.12.3.1 Administration Tool Incorrectly Displays Option for Generate Deployment File

- 1.12.3.2 Issue with Online Import Object Checkout

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

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

- 1.12.3.5 Administration Tool Fails to Launch from the Start Menu

- 1.12.3.6 Problems with Icons in Some Administration Tool Installations

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

- 1.12.3.8 Manually Map DFF VOs from ADF Data Sources into the Business Model and Mapping and Presentation Layers

- 1.12.3.9 Error Message Text Missing when Using Summary Advisor in Client Installations of the Administration Tool

- 1.12.3.10 Model Checker Not Enabled in Release 11.1.1.6.2

- 1.12.3.11 Publishing a Duplicate Dimension Object in a MUD Environment

- 1.13 Oracle Business Intelligence System Administration Issues and Workarounds

- 1.13.1 General System Administration Issues and Workarounds

- 1.13.2 Configuration Issues and Workarounds

- 1.13.2.1 Removal of DefaultImageType and HardenXSS Elements

- 1.13.3 Deployment, Availability, and Capacity Issues and Workarounds

- 1.13.4 Sign-in and Security Issues and Workarounds

- 1.13.4.1 Permission Required to Open Catalog Manager in Online Mode

- 1.13.5 Oracle BI Scheduler Issues and Workarounds

- 1.13.6 Oracle Essbase Suite Issues and Workarounds

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

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

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

- 1.13.6.4 Issue with Dashboards Menu in EPM Workspace

- 1.13.6.5 Merant 6.1 ODBC Drivers Are Not Configured on Linux

- 1.14 Oracle Business Intelligence Integration and API Issues and Workarounds

- 1.14.1 General Integration Issues and Workarounds

- 1.14.2 Oracle Business Intelligence API Issues and Workarounds

- 1.15 Oracle Business Intelligence Localization Issues and Workarounds

- 1.15.1 Product Localization Issues and Workarounds

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

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

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

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

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

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

- 1.15.1.7 Excel2007 Output in BI Publisher Supports Gregorian Calendar Only

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

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

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

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

- 1.15.2 Help System Localization Issues and Workarounds

- 1.15.2.1 Oracle Business Intelligence Help Systems Are Not Translated

- 1.16 Oracle Exalytics In-Memory Machine Issues and Workarounds

- 1.17 Oracle Business Intelligence Documentation Errata

- 1.17.1 General Oracle Business Intelligence Documentation Errata

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

- 1.17.3 Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence

- 1.17.3.1 Installation Guide Contains Misinformation About Installing the Client Tools

- 1.17.3.2 Installation Guide Contains Misinformation About pasteBinary Script

- 1.17.3.3 List of Supported Oracle BI Client Tools for Microsoft Windows x64

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

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

- 1.17.4.1 Incorrect Information on Aggregation

- 1.17.4.2 Incorrect Information on Database Authentication

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

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

- 1.17.5.2 Oracle BI Mobile: Easy Access to Dashboards

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

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

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

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

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

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

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

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

- 1.17.5.11 Information on View Latest Version Feature in Error

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

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

- 1.17.5.14 Misinformation About Oracle Endeca Server and Full-Text Search

- 1.17.5.15 Breadcrumbs Disabled for Embedded Objects in ADF

- 1.17.5.16 Note on Fixed Headers with Scrolling Content Is Incorrect

- 1.17.5.17 Misinformation About Adding HTML Code in Prompt Labels

- 1.17.5.18 Enable on Totals for Action Links Not Described

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

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

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

- 1.17.7.1 Important Changes to Essbase Preconfiguration Instructions

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

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

- 1.17.7.4 Other Changes to List of New Consistency Check Warnings

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

- 1.17.7.6 Manually Updating the Master MUD Repository

- 1.17.7.7 Configuration Required for Client Installations of the Administration Tool to Perform Offline Imports from Oracle OLAP and Hyperion Financial Management Data Sources

- 1.17.7.8 Database Client Installation Required for Client Installations of the Administration Tool when Importing from Oracle Database and Oracle OLAP Sources

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

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

- 1.17.7.11 Information Now Available for All Import Metadata Wizard Screens

- 1.17.7.12 Remove Smart View Mention in Appendix C

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

- 1.17.7.14 Changes to DataDirect Drivers and Directories

- 1.17.7.15 Additional Information Available on SCM Configuration Template Files

- 1.17.7.16 Additional Information Available on TimesTen Compressed Tables

- 1.17.7.17 Statement on Aggregate Creation Failure is Incorrect

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

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

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

- 1.17.8.2 Use of ps: Prefix in Elements Is Unnecessary

- 1.17.8.3 Lowercase for Boolean Values for Configuration Elements

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

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

- 1.17.8.6 Incomplete Information in "Validating the Catalog" Section

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

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

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

- 1.17.8.10 MaxColumns Element Not Supported

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

- 1.17.8.12 Clarification of CaseInsensitiveMode Element

- 1.17.8.13 Updates of Information About the Catalog

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

- 1.17.8.15 Omission of Enabled Element in Custom Links Section

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

- 1.17.8.17 Remove Mention of pasteBinary Script

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

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

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

- 1.17.9.1 SASchInvoke Always Prompts for the Password in 11.1.1.5

- 1.17.9.2 Setup Multiple Authentication Providers

- 1.17.9.3 Error in Code Example for Refreshing User GUIDs

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

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

- 1.17.9.6 Error in Code Example for Configuring a Database Adaptor

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

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

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

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

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

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

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

- 1.17.14 Oracle Business Intelligence Help System Errata

- 1.17.14.1 Incorrect Statement on Source Control Management and Multiuser Development in Administration Tool Online Help

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

2 Oracle Business Intelligence Applications and Data Warehouse Administration Console

- 2.1 Patch Requirements

- 2.1.1 Obtaining Patches from My Oracle Support

- 2.2 Oracle Business Intelligence Applications Release Notes

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

- 2.2.2 General Issues and Workarounds for Oracle Business Intelligence Applications

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

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

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

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

- 2.2.2.5 NLS:SDE_FUSION_DOMAINGENERAL_SALESINVOICESOURCE_FULL Failed With Syntax Error

- 2.2.2.6 Informatica License Dis-associating After Installation

- 2.2.2.7 JAZN File Not Translated

- 2.2.2.8 Duplicate Rows in GL Account Segment Hierarchy Tables

- 2.2.2.9 Rename Informatica Files With Upper Case XML Extension To Lower Case

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

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

- 2.2.3 Installation Issues and Workarounds for Oracle Business Intelligence Applications

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

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

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

- 2.2.4 Upgrade Issues and Workarounds for Oracle Business Intelligence Applications

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

- 2.2.5.1 Issues for Oracle Customer Data Management Analytics Offering

- 2.2.5.2 Issues for Oracle Financial Analytics Offering

- 2.2.5.3 Issues for Oracle Human Resources Analytics Offering

- 2.2.5.4 Issues for Oracle Marketing Analytics Offering

- 2.2.5.5 Issues for Oracle Partner Analytics Offering

- 2.2.5.6 Issues for Oracle Product Information Management Analytics Offering

- 2.2.5.7 Issues for Oracle Procurement and Spend Analytics Offering

- 2.2.5.8 Issues for Oracle Project Analytics Offering

- 2.2.5.9 Issues for Oracle Sales Analytics Offering

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

- 2.2.6 Translated Content in Non-English Reports and Dashboards

- 2.2.7 Error in Execution of Task SDE_FUSION_PayrollRunBalanceDetailFact

- 2.2.8 Oracle Business Intelligence Applications Configuration Manager and FSM Issues

- 2.2.9 Security-related Issues for Oracle Business Intelligence Applications

- 2.2.10 Oracle Business Intelligence Applications Documentation Errata

- 2.2.10.1 General Oracle Business Intelligence Documentation Errata

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

- 2.2.10.3 Oracle BI Applications Configuration Manager Help System

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

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

- 2.3.1 DAC Issues and Workarounds Identified Since the Previous Revision

- 2.3.2 DAC General Issues and Workarounds

- 2.3.3 DAC Installation Issues and Workarounds

- 2.3.4 DAC Upgrade Issues and Workarounds

- 2.3.5 DAC Documentation Errata

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

- 2.3.5.2 DAC Client Help System

3 Oracle Real-Time Decisions

- 3.1 Oracle RTD General Issues and Workarounds

- 3.1.1 Transient Likelihood Problems

- 3.1.2 Use Development Deployment State Only

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

- 3.1.4 Ensuring Unique Batch Names Across a Cluster

- 3.1.5 Safari and Chrome Accessibility Items

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

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

- 3.2 Oracle RTD Installation Issues and Workarounds

- 3.3 Oracle RTD Upgrade Issues and Workarounds

- 3.4 Oracle RTD Configuration Issues and Workarounds

- 3.5 Oracle RTD Security Issues and Workarounds

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

- 3.6 Oracle RTD Administration Issues and Workarounds

- 3.7 Oracle RTD Integration Issues and Workarounds

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

- 3.8 Oracle RTD Decision Studio Issues and Workarounds

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

- 3.8.2 Issues When Trying to Enable Caching for Some Entities

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

- 3.9 Oracle RTD Decision Center Issues and Workarounds

- 3.10 Oracle RTD Performance Monitoring Issues and Workarounds

- 3.11 Oracle RTD Externalized Objects Management Issues and Workarounds

- 3.12 Oracle RTD Localization Issues and Workarounds

- 3.13 Oracle RTD Documentation Errata

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

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

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

- 3.13.2.2 Save Choice IDs in Inline Services Rather Than Choices

- 3.14 Oracle RTD Third-Party Software Information

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

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

This chapter includes the following sections:

- Section 1.1, "Patch Requirements"

- Section 1.2, "Oracle Business Intelligence Issues and Workarounds Identified or Changed Since the Last Revision"

- Section 1.3, "Which Releases Are Covered by These Release Notes?"

- Section 1.4, "Oracle Business Intelligence General Issues and Workarounds"

- Section 1.5, "Oracle Business Intelligence Installation Issues and Workarounds"

- Section 1.6, "Oracle Business Intelligence Upgrade Issues and Workarounds"

- Section 1.7, "Oracle Business Intelligence Installation Guidelines for 64-Bit Platforms"

- Section 1.8, "Oracle Business Intelligence Analyses and Dashboards Issues and Workarounds"

- Section 1.9, "Oracle Business Intelligence Mobile Issues and Workarounds"

- Section 1.10, "Oracle Business Intelligence Mobile App Designer Issues and Workarounds"

- Section 1.11, "Oracle Business Intelligence Publisher Reporting and Publishing Issues and Workarounds"

- Section 1.12, "Oracle Business Intelligence Metadata Repository Development Issues and Workarounds"

- Section 1.13, "Oracle Business Intelligence System Administration Issues and Workarounds"

- Section 1.14, "Oracle Business Intelligence Integration and API Issues and Workarounds"

- Section 1.15, "Oracle Business Intelligence Localization Issues and Workarounds"

- Section 1.16, "Oracle Exalytics In-Memory Machine Issues and Workarounds"

- Section 1.17, "Oracle Business Intelligence Documentation Errata"

Depending on your Oracle Fusion Middleware implementation, some information in other chapters of Oracle Fusion Middleware Infrastructure Release Notes 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

1.1 Patch Requirements

This section describes patch requirements for Oracle Business Intelligence. It includes the following topic:

- Section 1.1.1, "Obtaining Patches from My Oracle Support"

1.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 "Downloading and Applying Required Patches" in Oracle Fusion Middleware Infrastructure Release Notes.

1.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 1.5.20, "Oracle Business Intelligence Installation Fails to Respond" has been reinstated in this document, after having been incorrectly removed from the Solaris-specific version of the Oracle Fusion Middleware Release Notes for 11g Release 1 (11.1.1).

- Section 1.5.21, "Binaries Fail to Redirect the Output to Log File" has been reinstated in this document, after having been incorrectly removed from the Solaris-specific version of the Oracle Fusion Middleware Release Notes for 11g Release 1 (11.1.1).

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

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

1.3.2 Oracle Business Intelligence Issues and Workarounds that Apply to IBM AIX, Oracle Solaris and HP-UX

Prior to the September 2014 revision of the Release Notes, issues and workarounds related specifically to the IBM AIX, Oracle Solaris and HP-UX ports of Oracle Business Intelligence were described in the port-specific versions of the Oracle Fusion Middleware Release Notes for 11g Release 1 (11.1.1) at:

http://download.oracle.com/docs/cd/E28280_01/index.htm

From September 2014 onwards, new issues and workarounds related to the IBM AIX, Oracle Solaris and HP-UX ports of Oracle Business Intelligence are described in this document.

1.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 1.4.1, "Oracle BI Disconnected Analytics Not Included in Oracle Business Intelligence 11g, Releases 11.1.1.5 and Later"

- Section 1.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 1.4.3, "IBM LDAP Based Authentication is Not Supported on Linux x86-64 and Microsoft Windows x64 (64-Bit)"

- Section 1.4.4, "Oracle BI Server Fails to Start Due to Missing Connect String in tnsnames.ora File"

- Section 1.4.5, "Issue with JAR File Size When Moving from a Test to a Production Environment"

- Section 1.4.6, "Adobe Flash Player Version 10.1 or Later Required to View Graphs and Scorecards"

- Section 1.4.7, "The Microsoft ODBC Data Source Administrator Crashes While Closing"

- Section 1.4.8, "ODBC System DSN Set With a Wrong Driver Filepath on Microsoft Windows x64 (64-Bit)"

- Section 1.4.9, "Hyperion Financial Management Data Sources Only Available for Windows Deployments"

- Section 1.4.10, "Siteminder Not Supported with Full-Text Catalog Search with Oracle Secure Enterprise Search"

- Section 1.4.11, "Windows Native Authentication Not Supported with Full-Text Catalog Search with Oracle Secure Enterprise Search"

- Section 1.4.12, "Full-Text Search Not Finding BI Publisher Reports by Report Column"

- Section 1.4.13, "Specifying Folder Names for Data-Loading the Catalog"

- Section 1.4.14, "SSL Not Available when Using Full-Text Search with Oracle Endeca Server"

- Section 1.4.15, "Issue with Email Notifications on Data Loads for Searching"

- Section 1.4.16, "Stopping a Data Load for Full-Text Searching with Oracle Endeca Server"

- Section 1.4.17, "Out of Memory Error When Crawling the Catalog"

- Section 1.4.18, "Multibyte Characters Are Displayed as NCR When Using Attribute Categories"

- Section 1.4.19, "Hebrew Fonts Might Be Displayed in the Wrong Direction on Windows"

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

- Section 1.4.21, "Graph Subtypes Are Not Refreshed in BI Composer"

- Section 1.4.22, "Dashboards and Scorecards Whose Paths Contain Multibyte Characters Do Not Display on ADF Pages"

- Section 1.4.23, "Characters Supported in Folder Names by BI Presentation Services Not Supported by BI Publisher"

- Section 1.4.24, "Configuring SSO for Essbase and Hyperion Financial Management Data Sources with Oracle Business Intelligence 11.1.1.3"

- Section 1.4.25, "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 1.4.26, "Patch Available to Hide Selected Consistency Check Warnings"

- Section 1.4.27, "Issues with WebLogic LDAP User Passwords"

- Section 1.4.28, "Configuring the GUID Attribute in the Identity Store"

- Section 1.4.29, "Messages Might Be Garbled When Running WebLogic Command Files"

- Section 1.4.30, "Rendering Issues Might Occur in Presentation Services When Using Microsoft Internet Explorer 9.x"

- Section 1.4.31, "Poor Performance Starting Up WebLogic Server"

- Section 1.4.32, "Analysis State Is Not Maintained for Breadcrumbs"

- Section 1.4.33, "Enhancements to Accessibility Features"

- Section 1.4.34, "Incorrect DataDirect License File for DataDirect 7.0.1 Drivers on Linux"

- Section 1.4.35, "Using Non-Native Characters In ODBC Data Source Administrator Wizard"

- Section 1.4.36, "Excel 2003 Support to Be Removed in Future Releases"

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

Platforms: All

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.

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

Platforms: All

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.

1.4.3 IBM LDAP Based Authentication is Not Supported on Linux x86-64 and Microsoft Windows x64 (64-Bit)

Impacted Releases: 11.1.1.3

Platforms: Linux x86-64, Microsoft Windows x64

IBM LDAP based authentication is not supported for Oracle Business Intelligence 11.1.1.3.0 release on Linux x86-64 and Microsoft Windows x64 (64-Bit).

To work around this issue, users must use Oracle WebLogic based authentication.

1.4.4 Oracle BI Server Fails to Start Due to Missing Connect String in tnsnames.ora File

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Platforms: Microsoft Windows (64-Bit)

Oracle Business Intelligence Server fails to start if the connect string used for the connection pool is missing in the $ORACLE_HOME/network/admin/tnsnames.ora file.

To work around this issue, ensure that a valid connect string is present in the tnsnames.ora file.

1.4.5 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

Platforms: All

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.

1.4.6 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

Platforms: All

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

1.4.7 The Microsoft ODBC Data Source Administrator Crashes While Closing

Impacted Releases: 11.1.1.3

Platforms: Microsoft Windows (32-Bit)

While closing the Microsoft Open Database Connectivity (ODBC) Data Source Administrator after editing the DSNs, the application might crash.

You can ignore this issue because the changes made to DSNs were unaffected.

1.4.8 ODBC System DSN Set With a Wrong Driver Filepath on Microsoft Windows x64 (64-Bit)

Impacted Releases: 11.1.1.3

Platforms: Microsoft Windows (64-Bit)

After installing Oracle BI EE, the ODBC System DSN is set with a wrong driver file path:

Driver=..\manualInstall64bit\Oracle_BI1\bifoundation\server\bin\NQSODBC.dll

Instead of setting the DSN driver to nqsodbc64.dll, the installer sets it to nqsodbc.dll, which does not exist on the disk.

The DSN driver setting has no functional impact and hence can be ignored.

1.4.9 Hyperion Financial Management Data Sources Only Available for Windows Deployments

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Platforms: Microsoft Windows (32-Bit)

You can use Hyperion Financial Management as a data source for Oracle BI EE only when Oracle BI EE is running in a Windows-only deployment.

1.4.10 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

Platforms: All

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.

1.4.11 Windows Native Authentication 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

Platforms: Microsoft Windows (32-Bit)

The full-text catalog search feature of Oracle BI EE when configured with Oracle Secure Enterprise Search is not supported with Windows Native Authentication. If you use this authentication and if you configure the full-text catalog search with the Active Directory plug-in and the Oracle Fusion data source, then the full-text catalog search returns no search results.

1.4.12 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

Platforms: All

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.

1.4.13 Specifying Folder Names for Data-Loading the Catalog

Impacted Releases: 11.1.1.7

Platforms: All

When you configure the Oracle Endeca Server for full-text searching with Oracle BI EE, you create an agent for data-loading the Oracle BI Presentation Catalog. As part of creating the agent, you specify the following parameters in the New Action dialog:

crawl_ibotPath
crawl_startLocation
crawl_includePaths
crawl_excludePaths

When you specify a value for these parameters, you must use the format as per the directory structure for the Oracle BI EE instance, which is not the same structure that is shown on the Catalog page. When the folder on the Catalog page is shown as /Shared Folders/folder-name, you specify /shared/folder-name. When the folder on the Catalog page is specified as /My Folders/user-name, you specify /users/user-name.

For example, on the Catalog page, if an object is stored in the /Shared Folders/common folder, then you specify the path for the agent as /shared/common.If the object is stored in the /My Folders/pedro folder, then you specify the path for the agent as /users/pedro.

1.4.14 SSL Not Available when Using Full-Text Search with Oracle Endeca Server

Impacted Releases: 11.1.1.7

Platforms: All

You cannot use Secure Socket Layers (SSL) when you use the full-text search functionality with Oracle Endeca Server. This issue has no workaround.

1.4.15 Issue with Email Notifications on Data Loads for Searching

Impacted Releases: 11.1.1.7

Platforms: All

When you use the full-text search capability with Oracle Endeca Server, you set delivery options for agents to send you an email when data loads have started and completed successfully or failed. When you use the full-text search capability on Windows and SUSE environments, emails are not sent when data loads start, finish, or fail.

To work around this issue, use Fusion Middleware Control to monitor the status of data load operations.

1.4.16 Stopping a Data Load for Full-Text Searching with Oracle Endeca Server

Impacted Releases: 11.1.1.7

Platforms: All

When you initiate a data load for full-text searching when using the Oracle Endeca Server, you can expect to see an email notification when the data load has started. This email contains a link that you can click to stop the data load. However, due to the known issue that no email notifications are sent when the Oracle Endeca Server runs on Windows and SUSE platforms, you cannot stop the data load using a link in an email.

To work around this issue, perform the following steps:

1. Stop the BISearch application using Fusion Middleware Control.

2. Recreate the data store on the Oracle Endeca Server for the full-text search.

3. Restart the BISearch application using Fusion Middleware Control.

4. Restart the data load.

1.4.17 Out of Memory Error When Crawling the Catalog

Impacted Releases: 11.1.1.7

Platforms: All

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

1.4.18 Multibyte Characters Are Displayed as NCR When Using Attribute Categories

Impacted Releases: 11.1.1.7

Platforms: All

If you display attribute categories in full-text search results from the Oracle Endeca Server, then you notice that multibyte characters are displayed as numerical character references (NCR).

This issue has no workaround.

1.4.19 Hebrew Fonts Might Be Displayed in the Wrong Direction on Windows

Impacted Releases: 11.1.1.3, 11.1.1.5

Platforms: Microsoft Windows (32-Bit)

On Windows, if you select the Install files for complex script and right-to-left languages (including Thai) option on the Languages tab of the Regional and Language Options dialog, Hebrew fonts might be displayed in the wrong direction, that is left to right rather than right to left.

The workaround is to deselect the Install files for complex script and right-to-left languages (including Thai) option as follows:

1. In the Control Panel, click the Regional & Language Options button to display the Regional and Language Options dialog.

2. Click the Languages tab.

3. Deselect the Install files for complex script and right-to-left languages (including Thai) option.

4. Click OK.

1.4.20 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

Platforms: All

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.

1.4.21 Graph Subtypes Are Not Refreshed in BI Composer

Impacted Releases: 11.1.1.5

Platforms: All

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

1.4.22 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

Platforms: All

Dashboards and scorecards whose paths contain multibyte characters do not display on ADF pages.

This issue has no workaround.

1.4.23 Characters Supported in Folder Names by BI Presentation Services Not Supported by BI Publisher

Impacted Releases: 11.1.1.5

Platforms: All

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.

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

Impacted Releases: 11.1.1.3

Platforms: All

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

1.4.25 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

Platforms: All

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 1.4.25.1, "Configuring SSO for Essbase and Hyperion Financial Management Release 11.1.2.1 or Later"

- Section 1.4.25.2, "Configuring SSO for Essbase and Hyperion Financial Management Release 11.1.2.0 or Earlier"

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

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

1.4.26 Patch Available to Hide Selected Consistency Check Warnings

Impacted Releases: 11.1.1.3

Platforms: All

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

1.4.27 Issues with WebLogic LDAP User Passwords

Impacted Releases: 11.1.1.3

Platforms: All

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.

1.4.28 Configuring the GUID Attribute in the Identity Store

Impacted Releases: 11.1.1.3

Platforms: All

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

1.4.29 Messages Might Be Garbled When Running WebLogic Command Files

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Platforms: Microsoft Windows (32-Bit)

In a Windows environment where the locale is not UTF-8, running WebLogic command files (either directly or from the Windows Start menu) on an Oracle BI EE system might garble messages that are shown in the terminal window. The fact that the messages are garbled does not affect the correct running of the system.

This issue has no workaround.

1.4.30 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

Platforms: All

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

1.4.31 Poor Performance Starting Up WebLogic Server

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

Platforms: All

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.

1.4.32 Analysis State Is Not Maintained for Breadcrumbs

Impacted Releases: 11.1.1.7

Platforms: All

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.

1.4.33 Enhancements to Accessibility Features

Impacted Releases: 11.1.1.7

Platforms: All

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.

1.4.34 Incorrect DataDirect License File for DataDirect 7.0.1 Drivers on Linux

Impacted Releases: 11.1.1.7

Platforms: Linux x86-64

The Oracle Business Intelligence installation of Linux installed on a 64-bit operating system contains the incorrect DataDirect license file for the DataDirect 7.0.1 drivers. If you want to configure Oracle BI EE to use the DataDirect 7.0.1 drivers, including the Hive driver, then obtain the correct license file by downloading and applying patch 16278897. See Section 1.1.1, "Obtaining Patches from My Oracle Support" for more information about downloading patches.

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

Platforms: All

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.

1.4.36 Excel 2003 Support to Be Removed in Future Releases

Impacted Releases: Releases after 11.1.1.7

Excel 2003 will no longer be supported in releases after Release 11.1.1.7. This means that the following features will no longer be supported:

- The ability to integrate an analysis with Excels' Internet Query (IQY) feature

- Excel 2003 in the Go URL

- Export to Excel 2003

1.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 1.5.1, "Error When Installing Oracle Business Intelligence Against a SQL Server Database"

- Section 1.5.2, "Scale-Out Scenarios Are Not Supported on OS with Different Patch Levels"

- Section 1.5.3, "Need to Correctly Create the Oracle Central Inventory in a UNIX Environment"

- Section 1.5.4, "Antivirus Software Might Block the Installation in a Windows Environment"

- Section 1.5.5, "Oracle Business Intelligence Installer Stops at Administrator User Details Screen"

- Section 1.5.6, "Issues When Installing Oracle Business Intelligence on Windows 2008"

- Section 1.5.7, "Installing Oracle Business Intelligence on a Shared Drive Might Fail"

- Section 1.5.8, "Configuring DB2 to Support Multibyte Data"

- Section 1.5.9, "Using Multibyte Data Causes Issues with Microsoft SQL Server 2005/2008 Driver in Oracle BI Scheduler"

- Section 1.5.10, "Job Manager Does Not Start Due to Insufficient Permissions on Windows Operating Systems"

- Section 1.5.11, "Oracle Essbase Fails to Start on Microsoft Windows x64 (64-Bit)"

- Section 1.5.12, "Missing Locale Causes Oracle Business Intelligence Installation to Fail on UNIX"

- Section 1.5.13, "Ignore FAT File System Error Message When Performing an Enterprise Installation"

- Section 1.5.14, "Job Manager Might Fail to Launch from the Start Menu"

- Section 1.5.15, "Job Manager Cannot Launch if the Client Tools Install Path Includes Multi-Byte Characters"

- Section 1.5.16, "Error Occurs When RCU is Invoked For a Second Time to Create Only MDS/Platform Schemas on IBM DB/2"

- Section 1.5.17, "Financial Reporting Print Server Not Enabled"

- Section 1.5.18, "Oracle Hyperion Calculation Manager does not work correctly without Adobe Flash Player"

- Section 1.5.19, "Oracle Universal Installer Incorrectly Reports "No IPv4 Network Interfaces Found""

- Section 1.5.20, "Oracle Business Intelligence Installation Fails to Respond"

- Section 1.5.21, "Binaries Fail to Redirect the Output to Log File"

Depending on your Oracle Fusion Middleware implementation, some information in Chapter 2, "Installation, Patching, and Configuration" in Oracle Fusion Middleware Infrastructure Release Notes might also be relevant.

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

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: Linux x86

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.

1.5.4 Antivirus Software Might Block the Installation in a Windows Environment

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Platforms: Microsoft Windows (32-Bit)

If you are deploying to a mapped network drive on a computer running a supported Windows operating system, then ensure that the antivirus software is not set to block the remote creation of autorun.inf files.

1.5.5 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

Platforms: All

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.

1.5.6 Issues When Installing Oracle Business Intelligence on Windows 2008

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Platforms: Microsoft Windows (32-Bit)

When you install Oracle Business Intelligence on Windows 2008, you might experience issues such as OPMN failing to start processes.

The workaround is to run the installation and configuration steps with the Run as Administrator option.

1.5.7 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

Platforms: All

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

1.5.8 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

Platforms: All

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.

1.5.9 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

Platforms: All

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.

1.5.10 Job Manager Does Not Start Due to Insufficient Permissions on Windows Operating Systems

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Platforms: Microsoft Windows (32-Bit)

If certain permission settings are insufficient, then Job Manager does not open when you attempt to start it. You can resolve this issue by changing the permission settings on the bifoundation folder. This folder can be found in the Oracle Business Intelligence Enterprise Edition Plus Client installation directory.

To resolve this issue:

1. In Windows Explorer, access the bifoundation folder, found in the directory where you installed Oracle Business Intelligence Enterprise Edition Plus Client. Typically, you can find this folder in the following directory:
C:\Program Files\Oracle Business Intelligence Enterprise Edition Plus Client\oraclebi\orainst\bifoundation

2. Right-click the bifoundation folder, and then click Properties.

3. Click the Security tab.

4. Click Edit.

5. Click Add. The Select Users, Computers, or Groups dialog window opens.

6. Click Authenticated Users, and then click OK.

7. In the Users or Groups pane, click Authenticated Users.

8. In the Permissions pane, click the Modify and Write check boxes so that check marks are displayed in them.

9. Click OK.

10. Start Job Manager either from the Start menu or the command line.

1.5.11 Oracle Essbase Fails to Start on Microsoft Windows x64 (64-Bit)

Platforms: Microsoft Windows (64-Bit)

Oracle Essbase fails to start on Microsoft Windows x64 (64-Bit) platform. It shows the following error:

Network Error [10048]: Unable to Bind Host Server Socket On Port [9501]

This error occurs when Oracle Process Management and Notification (OPMN) components are started on both the cluster nodes of Oracle Essbase cluster environment, and the Essbase component that is stopped on the active cluster node1 tries to fail over to cluster node2 or back to cluster node1.

At this time, OPMN spawns Oracle Essbase and passes two command line arguments as ports. They are as follows:

1. Its main listening port (1423 - as configured in opmn.xml).

2. A ping port, where OPMN keeps pinging Essbase.

For the second command line argument, OPMN does a port scan to find a free port from a dynamic range specified in opmn.xml file from the following attribute:

<port id="essbase-port-range" range="9500-9999"/>

The port scan reports port 9501 as a free port. This result is incorrect, as OPMN is already listening on port 9501. Thus, when OPMN sends the startup arguments to Essbase with a ping port of 9501, Essbase fails to start and shuts down.

To work around this issue, specify the range in opmn.xml file as:

<port id="essbase-port-range" range="9502-9999"/>

1.5.12 Missing Locale Causes Oracle Business Intelligence Installation to Fail on UNIX

Impacted Releases: 11.1.1.5

Platforms: Linux x86

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.

1.5.13 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

Platforms: All

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.

1.5.14 Job Manager Might Fail to Launch from the Start Menu

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Platforms: Microsoft Windows (64-Bit)

Job Manager might fail to launch from the Start menu if the client tools were installed in a default folder on a French or Korean 64-bit Windows 7 operating system. This happens because users do not have privileges to create temporary directories.

The workaround is to do one of the following:

- Create a temporary directory manually and add the current user to the Administrator group on that temporary directory.

- Install the client tools in a specific directory, not the default directory.

1.5.15 Job Manager Cannot Launch if the Client Tools Install Path Includes Multi-Byte Characters

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Platforms: All

When running the Oracle Business Intelligence Enterprise Edition Plus Client Installer, if the install path contains any multi-byte characters, then Job Manager cannot launch. To avoid this issue you must change the install path if it contains any multi-byte characters. Ensure that the install path contains only ASCII characters.

1.5.16 Error Occurs When RCU is Invoked For a Second Time to Create Only MDS/Platform Schemas on IBM DB/2

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2

Platforms: All

To prevent RCU displaying an EPM schema error when running RCU for the second time to create only MDS/BIPLATFORM schemas on IBM DB/2, you must first delete two lines of text from the ComponentInfo.xml file.

To prevent an EPM schema error occurring when using RCU for a second time to create only MDS/Platform schemas on IBM DB/2:

1. Open the file ComponentInfo.xml file which is located in rcu/config.

2. Delete the following two lines from the ComponentInfo.xml file:

<!ENTITY epm SYSTEM "../integration/epm/epm_ComponentInfo.xml">
&epm;

RCU uses these lines to display components listed in the selection tree for the Select Components page.

3. Save the ComponentInfo.xml file.

4. Run RCU for the second time.

1.5.17 Financial Reporting Print Server Not Enabled

Impacted Releases: 11.1.1.7

Platforms: All

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.

1.5.18 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

Platforms: All

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.

1.5.19 Oracle Universal Installer Incorrectly Reports "No IPv4 Network Interfaces Found"

Impacted Releases 11.1.1.7

Platforms: All

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"

1.5.20 Oracle Business Intelligence Installation Fails to Respond

Impacted Releases: 11.1.1.6.0

Platforms: Oracle Solaris

On Oracle Solaris on x64 (64-bit) systems, Oracle Business Intelligence release 11.1.1.6.0 installation may fail to respond when you run the following script:

BI_ORACLE_HOME/bifoundation/install/runsasperf.sh

To work around this issue, complete the following steps:

1. Stop the installation.

2. Log in as the root user and add the following entry in the /etc/hosts file:

local_install_machine_IP_address    stafas12

3. Install Oracle Business Intelligence.

1.5.21 Binaries Fail to Redirect the Output to Log File

Impacted Releases 11.1.1.7

Platforms: Oracle Solaris

When you run the nqsserver, nqscheduler, and nqsclustercontroller binaries on Oracle Solaris systems, the output is not redirected to the log files. For example:

$ORACLE_HOME/bifoundation/server/bin/nqsserver -v 1>/tmp/nqsserver.log 2>&1
$ORACLE_HOME/bifoundation/server/bin/nqscheduler -v 1>/tmp/nqscheduler.log 2>&1
$ORACLE_HOME/bifoundation/server/bin/nqsclustercontroller -v
1>/tmp/nqsclustercontroller .log 2>&1

Workaround:

From the command-line interface, redirect the output to the log file as follows:

- $ORACLE_HOME/bifoundation/server/bin/nqsserver -v 1>/tmp/nqsserver.log 0>&1

- $ORACLE_HOME/bifoundation/server/bin/nqscheduler -V >/tmp/nqscheduler.log 0>&1

- $ORACLE_HOME/bifoundation/server/bin/nqsclustercontroller -V >/tmp/nqsclustercontroller.log 0>&1

1.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 1.6.1, "General Upgrade Issues and Workarounds"

- Section 1.6.2, "Security-related Upgrade Issues and Workarounds"

Depending on your Oracle Fusion Middleware implementation, some information in Chapter 3, "Upgrade" in Oracle Fusion Middleware Infrastructure Release Notes might also be relevant.

1.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 1.6.1.1, "Conditional Formatting Might Not Work After Upgrading from Oracle Business Intelligence Release 10g to Release 11g"

- Section 1.6.1.2, "Issues Exporting Large Data Sets to Microsoft Excel"

- Section 1.6.1.3, "Managed Server for Oracle BI Encounters Issues After Upgrade from Release 11.1.1.3"

- Section 1.6.1.4, "MapViewer Runtime Failure After Upgrading from Release 11.1.1.6 to Release 11.1.1.7"

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

Platforms: All

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.

1.6.1.2 Issues Exporting Large Data Sets to Microsoft Excel

Impacted Releases: 11.1.1.7

Platforms: All

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.

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

Impacted Releases: 11.1.1.7

Platforms: All

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.

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

Platforms: All

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.

1.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 1.6.2.1, "Warnings Might Be Reported When Upgrading an RPD with Non-English User or Group Names"

- Section 1.6.2.2, "Users or Groups With Names Containing Invalid Characters Are Not Upgraded"

- Section 1.6.2.3, "RPD Upgrade Process Fails If the 10g Administrator UserID or Password Contains any Non-Native Characters"

- Section 1.6.2.4, "Errors Might Be Reported In Upgraded Analyses that Contain EVALUATE_ Database Analytic Function"

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

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

Platforms: All

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

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

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

1.7 Oracle Business Intelligence Installation Guidelines for 64-Bit Platforms

- Section 1.7.1, "Prerequisites for Software Only Installation on 64-Bit Platforms"

- Section 1.7.2, "Supported Installation Types for Oracle Business Intelligence on 64-Bit Platforms"

- Section 1.7.3, "Considerations and Limitations of Enterprise Install Type for Scaling Out Existing Installations"

1.7.1 Prerequisites for Software Only Installation on 64-Bit Platforms

Impacted Releases: 11.1.1.3

Platforms: Microsoft Windows (64-Bit)

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.

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

Platforms: Microsoft Windows (64-Bit)

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.

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

Platforms: Microsoft Windows (64-Bit)

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.

1.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 1.8.1, "General Analyses and Dashboards Issues and Workarounds"

- Section 1.8.2, "Actions Issues and Workarounds"

- Section 1.8.3, "Scorecards and KPI Issues and Workarounds"

- Section 1.8.4, "Agents Issues and Workarounds"

- Section 1.8.5, "Microsoft Office Integration Issues and Workarounds"

1.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 1.8.1.1, "Existing Dashboard Prompts Based on Columns Renamed in the Business Model Do Not Work"

- Section 1.8.1.2, "Gauge Views Might Be Cut Off and Not Visible Under Certain Conditions"

- Section 1.8.1.3, "Numerical Units on a Dashboard Prompt Slider Might Not Be Translated Correctly"

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

- Section 1.8.1.5, "Scorecard Diagrams on Dashboard Pages Might Print as Tables"

- Section 1.8.1.6, "Using Maps with Column Selectors"

- Section 1.8.1.7, "Issue with Wrap-Around Feature for Maps"

- Section 1.8.1.8, "Inability to Delete Map Tiles in MapViewer"

- Section 1.8.1.9, "Support for Rendering Small Form-Factor Graphs"

- Section 1.8.1.10, "Analyses Whose Paths Contain Latin Supplement Characters Fail to Open on Dashboard Pages"

- Section 1.8.1.11, "In Selection Steps Search for Members in Hierarchical Columns That Are Non-Text Yields No Results"

- Section 1.8.1.12, "Interactions on Right-Click Menus Are Not Translated"

- Section 1.8.1.13, "Issues with the Alignment of Trellis Views"

- Section 1.8.1.14, "Characters in Trellis Title Display Incorrectly in Certain Languages"

- Section 1.8.1.15, "Export to Excel 2007+ and Export to PDF Do Not Support Custom CSS Styles"

- Section 1.8.1.16, "Items Not Supported When Using Custom Print Layouts"

- Section 1.8.1.17, "Grand Total Shows Zero in Reports After Applying BI 11.1.1.7.1 Patch"

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

Platforms: All

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.

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

Impacted Releases: 11.1.1.5

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

1.8.1.7 Issue with Wrap-Around Feature for Maps

Impacted Releases: 11.1.1.6.2

Platforms: All

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.

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

Platforms: All

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.

1.8.1.9 Support for Rendering Small Form-Factor Graphs

Impacted Releases: 11.1.1.5

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

1.8.1.12 Interactions on Right-Click Menus Are Not Translated

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2

Platforms: All

The interactions on right-click menus for table views and pivot table views are not translated.

1.8.1.13 Issues with the Alignment of Trellis Views

Impacted Releases: 11.1.1.6.2, 11.1.1.7

Platforms: All

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.

1.8.1.14 Characters in Trellis Title Display Incorrectly in Certain Languages

Impacted Releases: 11.1.1.7

Platforms: All

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.

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

Impacted Releases: 11.1.1.7

Platforms: All

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

1.8.1.16 Items Not Supported When Using Custom Print Layouts

Impacted Releases: 11.1.1.7

Platforms: All

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.

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

Platforms: All

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.

1.8.2 Actions Issues and Workarounds

This section describes issues and workarounds related to actions. It includes the following topic:

- Section 1.8.2.1, "EJBs in Action Framework Must Be Deployed to the WebLogic Managed Server"

- Section 1.8.2.2, "UserScripts.js File Must Be Backed Up and Reinstated After Every Patch or Upgrade"

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

Platforms: All

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.

1.8.2.2 UserScripts.js File Must Be Backed Up and Reinstated After Every Patch or Upgrade

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6, 11.1.1.7

Platforms: All

If you are using actions to invoke a browser script, then you must backup the UserScripts.js file and reinstate it after every patch or upgrade. If you do not backup and reinstate the file, then it will be replaced with a default file and you will lose your custom JavaScript functions.

1.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 1.8.3.1, "No Results Returned When Searching in the Related Documents of Scorecards or Scorecard Components"

- Section 1.8.3.2, "Accessing a Smart Watchlist from the Oracle Secure Enterprise Search Results Page Causes an Error"

- Section 1.8.3.3, "Item Stale Error When Editing a Shared Scorecard in Parallel"

- Section 1.8.3.4, "Scorecard Pie Chart and Gauge Labels are Not Readable in Chrome"

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

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

1.8.4 Agents Issues and Workarounds

This section describes issues and workarounds related to agents. It includes the following topics:

- Section 1.8.4.1, "Agent Deliveries Fail with Microsoft Active Directory and Oracle Virtual Directory"

- Section 1.8.4.2, "Agent Incorrectly Delivers Content to Active Delivery Profile When Only the Home Page and Dashboard Option Is Selected"

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

Platforms: All

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.

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

Platforms: All

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.

1.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 1.8.5.1, "Using Microsoft Office 2007 with Oracle BI Add-in for Microsoft Office"

- Section 1.8.5.2, "Server Connections Are Not Automatically Shared by Microsoft Excel and PowerPoint"

- Section 1.8.5.3, "Previous Installation of Oracle BI Add-in for Microsoft Office Must Be Manually Uninstalled"

- Section 1.8.5.4, "Install a Language Pack for Non-English Languages"

- Section 1.8.5.5, "Errors in the Online Help for Oracle BI Add-In for Microsoft Office"

- Section 1.8.5.6, "Refreshing Table or Pivot Table Views with Double Columns in Page Edge Might Result in Error"

- Section 1.8.5.7, "Double Column Cascading Results in Incorrect Display Values"

- Section 1.8.5.8, "Intermittent Timeout Errors"

- Section 1.8.5.9, "Lack of Support for Vary Color By Target Area"

- Section 1.8.5.10, "Measure Column Labels Might Display Incorrectly When Inserted into Microsoft Excel"

- Section 1.8.5.11, "Stacked Graphs Do Not Display Negative Values"

- Section 1.8.5.12, "Scatter Graphs with Lines Display as Default Scatter Graphs in Excel and PowerPoint"

- Section 1.8.5.13, "Graphs With Section Edges Are Not Supported Starting With Release 11.1.1.6.x"

- Section 1.8.5.14, "Refreshing Table Views in Arabic or German Versions of Excel Result in Incorrect Data Values"

- Section 1.8.5.15, "Inserting a View With a Grand Total Column or Row into Microsoft Office Might Cause Issues"

- Section 1.8.5.16, "Time Displayed in Table or Pivot View Title Might Be Incorrect after Insertion"

- Section 1.8.5.17, "Graphs Might Be Displayed Differently After Insertion into Microsoft Office"

- Section 1.8.5.18, "Legends in Bubble and Scatter Graphs Might Display Differently After Insertion into Microsoft Office"

- Section 1.8.5.19, "Help System Does Not Work When Running Oracle BI Office for PowerPoint in Norwegian or Polish"

- Section 1.8.5.20, "Protected Worksheet Causing Incorrect Message When Inserting View in Oracle BI Add-in for Microsoft Office"

- Section 1.8.5.21, "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.

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

Platforms: All

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

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

Platforms: All

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.

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

Platforms: All

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.

1.8.5.4 Install a Language Pack for Non-English Languages

Impacted Releases: 11.1.1.3, 11.1.1.5

Platforms: All

To use the Oracle BI Add-in for Microsoft Office for a non-English language, you must install the appropriate language pack for Microsoft Office and set the regional language settings using the Control Panel. Go to the following URL to download and install the appropriate language pack:

http://office.microsoft.com/en-us/downloads/office-language-interface-pack-lip-downloads-HA001113350.aspx

1.8.5.5 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

Platforms: All

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

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

Impacted Releases: 11.1.1.5

Platforms: All

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

1.8.5.7 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

Platforms: All

If double columns are used in cascaded prompts for both columns, then you might see code being displayed instead of the correct display values.

1.8.5.8 Intermittent Timeout Errors

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Platforms: All

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.

1.8.5.9 Lack of Support for Vary Color By Target Area

Impacted Releases: 11.1.1.5

Platforms: All

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.

1.8.5.10 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

Platforms: All

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.

1.8.5.11 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

Platforms: All

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.

1.8.5.12 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

Platforms: All

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.

1.8.5.13 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

Platforms: All

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.

1.8.5.14 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

Platforms: All

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.

1.8.5.15 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

Platforms: All

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.

1.8.5.16 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

Platforms: All

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.

1.8.5.17 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

Platforms: All

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.

1.8.5.18 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

Platforms: All

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.

1.8.5.19 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

Platforms: All

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.

1.8.5.20 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

Platforms: All

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.

1.8.5.21 Column Data in Section Edge Is Not Obtained

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Platforms: All

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.

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

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

1.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 1.11.1, "General Oracle BI Publisher Issues and Workarounds"

- Section 1.11.2, "Oracle BI Publisher Security Issues and Workarounds"

- Section 1.11.3, "Oracle BI Publisher Delivery Manager Issues and Workarounds"

- Section 1.11.4, "Oracle BI Publisher Scheduler Issues and Workarounds"

- Section 1.11.5, "Oracle BI Publisher RTF Template Issues and Workarounds"

- Section 1.11.6, "Oracle BI Publisher Excel Template Issues and Workarounds"

- Section 1.11.7, "Oracle BI Publisher Desktop Tools Issues and Workarounds"

- Section 1.11.8, "Oracle BI Publisher Layout Editor Issues and Workarounds"

- Section 1.11.9, "Oracle BI Publisher Data Model Issues and Workarounds"

- Section 1.11.10, "Oracle BI Publisher Report Building Issues and Workarounds"

- Section 1.11.11, "Oracle BI Publisher Documentation Errata"

1.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 1.11.1.1, "JDBC Driver Throws Unsupported Function for setBigDecimal"

- Section 1.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 1.11.1.3, "Data Source List in BI Publisher Administration Page Includes Data Sources That Are Not Supported"

- Section 1.11.1.4, "Menu Items Do Not Display When Using Internet Explorer 7 or 8 with a Bidirectional Language Preference"

- Section 1.11.1.5, "Data Source Definition for Microsoft SQL Server 2008 Analysis Services Does Not Get Saved"

- Section 1.11.1.6, "Issues with Viewing Some Report Formats on Apple iPad"

- Section 1.11.1.7, "BI Publisher Objects Exhibit Unexpected Behavior When Located Inside a Folder Named with a Single Quote Character"

- Section 1.11.1.8, "Components Folder Missing from SampleApp Lite Web Catalog"

- Section 1.11.1.9, "Boilerplate Templates in the Components Folder Do Not Display Table Borders Properly in Chrome Browsers"

- Section 1.11.1.10, "Local Policy Attachments (LPAs) Removed from Web Services in Release 11.1.1.5"

- Section 1.11.1.11, "Oracle BI Publisher Requires Oracle WebLogic Server to Run in en_US Locale"

- Section 1.11.1.12, "Search Might Return Incorrect Number of Results"

- Section 1.11.1.13, "Schedule Report Option Is Not Displayed Correctly for Non-Administrator Users"

- Section 1.11.1.14, "Additional Setup for BI Publisher Desktop Tools in 11.1.1.6.2"

- Section 1.11.1.15, "Oracle Endeca Search Does Not Work from /xmlpserver URL"

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

- Section 1.11.1.17, ""Failed to Add" Error When Adding Report Objects to Favorites"

- Section 1.11.1.18, "Cannot Add Reports with Multibyte Character Names to Favorites Using the Catalog Task Option"

- Section 1.11.1.19, "Excel Analyzer and Online Analyzer Deprecated in Release 11.1.1.7"

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

Platforms: All

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

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

Platforms: All

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

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

Impacted Releases: 11.1.1.5

Platforms: All

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

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

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

1.11.1.8 Components Folder Missing from SampleApp Lite Web Catalog

Impacted Releases: 11.1.1.5

Platforms: All

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.

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

Impacted Releases: 11.1.1.6

Platforms: All

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.

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

Platforms: All

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

1.11.1.11 Oracle BI Publisher Requires Oracle WebLogic Server to Run in en_US Locale

Impacted Release: 11.1.1.3

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

1.11.1.14 Additional Setup for BI Publisher Desktop Tools in 11.1.1.6.2

Impacted Release: 11.1.1.6.2

Platforms: All

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.

1.11.1.15 Oracle Endeca Search Does Not Work from /xmlpserver URL

Impacted Release: 11.1.1.7

Platforms: All

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

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

Platforms: All

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

1.11.1.17 "Failed to Add" Error When Adding Report Objects to Favorites

Impacted Release: 11.1.1.7

Platforms: All

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.

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

Impacted Release: 11.1.1.7

Platforms: All

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 1.11.1.17, ""Failed to Add" Error When Adding Report Objects to Favorites."

1.11.1.19 Excel Analyzer and Online Analyzer Deprecated in Release 11.1.1.7

Impacted Release: 11.1.1.7

Platforms: All

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.

1.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 1.11.2.1, "Limitations for Administrator Username in LDAP Security Model"

- Section 1.11.2.2, "Oracle E-Business Suite Security Requires the BI Publisher Server Operating System Language to Match an E-Business Suite Enabled Language"

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

Platforms: All

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.

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

Platforms: All

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.

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

1.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 1.11.4.1, "Scheduler Does Not Support Multibyte Characters When Schema Installed on Microsoft SQL Server"

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

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

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

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

1.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 1.11.5.1, "RTF Templates in 11g Require Number Conversion on String Expressions"

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

Platforms: All

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

1.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 1.11.6.1, "Limitations for Excel Template Output on Apple iPad"

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

Platforms: All

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.

1.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 1.11.7.1, "Oracle BI Publisher's Template Builder for Microsoft Word Is Not Compatible with Microsoft Office Live Add-in"

- Section 1.11.7.2, "Excel Analyzer Does Not Support 64-Bit Windows Platform"

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

Platforms: All

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.

1.11.7.2 Excel Analyzer Does Not Support 64-Bit Windows Platform

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Platforms: Microsoft Windows (64-Bit)

Oracle BI Publisher´s desktop tool, the Analyzer for Excel does not support installation on Windows 64-bit platform. Support for 32-bit Windows platform is only available at this time.

1.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 1.11.8.1, "Editing an XPT Layout and Clicking Return in Layout Editor Results in Exception"

- Section 1.11.8.2, "Interactive Viewer Might Return Unexpected Results from Formula Columns"

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

- Section 1.11.8.4, "Division Results Rounded Inconsistently When Used with the #,##0 Custom Format Mask"

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

Platforms: All

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

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

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

1.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 1.11.9.1, "Data Model Is Not Editable When Created by Upgrade Assistant"

- Section 1.11.9.2, "Issues with Upgraded 10g Data Models That Include Ref Cursors and Stored Procedures"

- Section 1.11.9.3, "After Editing a View Object Data Set, the Elements Are Duplicated"

- Section 1.11.9.4, "Excel Workbooks Used as Data Sources Cannot Contain Ampersand (&) in the Sheet Name"

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

Platforms: All

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.

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

Platforms: All

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.

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

Impacted Releases: 11.1.1.3, 11.1.1.5

Platforms: All

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.

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

Platforms: All

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.

1.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 1.11.10.1, "Use Oracle BI Publisher Conversion Assistant to Convert Oracle Reports to Oracle BI Publisher 11g"

- Section 1.11.10.2, ""Enable Bursting" Report Property Displays Enabled State When Disabled"

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

Platforms: All

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

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

Platforms: All

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.

1.11.11 Oracle BI Publisher Documentation Errata

This section describes Oracle BI Publisher documentation errata. It includes the following topics:

- Section 1.11.11.1, "Oracle Fusion Middleware Report Designer's Guide for Oracle Business Intelligence Publisher"

- Section 1.11.11.2, "Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher"

1.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 1.11.11.1.1, "Syntax Error in "Column Formatting" Section of the "Creating an RTF Template" Chapter"

- Section 1.11.11.1.2, "Required Location of ICC Profile Data File for PDF/X and PDF/A Output Incorrectly Documented"

- Section 1.11.11.1.3, "Support for Dynamic Links in Layout Editor Not Documented"

- Section 1.11.11.1.4, "Link to "Advanced Barcode Font Formatting" Points to Wrong Guide"

- Section 1.11.11.1.5, "Report Designer's Guide Incorrectly States Support for Hindi"

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

Platforms: All

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

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

Platforms: All

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 1-2 provides a detailed revision of the two required PDF/X properties: PDF/X ICC Profile Data and PDF/X output condition identifier.

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

1.11.11.1.3 Support for Dynamic Links in Layout Editor Not Documented

Impacted Releases: 11.1.1.6.0

Platforms: All

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.

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

Platforms: All

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.

1.11.11.1.5 Report Designer's Guide Incorrectly States Support for Hindi

Impacted Releases: 11.1.1.7

Platforms: All

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.

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

1.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 1.12.1, "General Metadata Repository Development Issues and Workarounds"

- Section 1.12.2, "Oracle BI Server Issues and Workarounds"

- Section 1.12.3, "Oracle BI Administration Tool Issues and Workarounds"

1.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 1.12.1.1, "Use of NQClient (BI ODBC Client) Utility Is Deprecated"

- Section 1.12.1.2, "Update Logical Table Source Modeling when Using paint.rpd for Testing"

- Section 1.12.1.3, "FIRST and LAST Aggregation Rules Cause Inconsistent Sorting for Time Dimensions"

- Section 1.12.1.4, "Oracle OLAP Jars on JavaHost Computer Must Be Updated When Using Oracle OLAP 11.2.x"

- Section 1.12.1.5, "Must Use JDBC Connection String When Importing from Oracle OLAP"

- Section 1.12.1.6, "Using the BIServerT2PProvisioner.jar Utility to Change Connection Pool Passwords"

- Section 1.12.1.7, "Configuring a Servlet for Oracle BI Server Communication with Oracle OLAP"

- Section 1.12.1.8, "Enhancing Performance of Aggregates with TimesTen Release 11.2.2.3 or Later"

- Section 1.12.1.9, "Performing Merges on Repositories That Contain System-Generated Tables Can Cause Loss of Metadata"

- Section 1.12.1.10, "Create Aggregates Operations Can Time Out for TimesTen Targets"

- Section 1.12.1.11, "Logical Display Folders Are Deleted During MUD Publish"

1.12.1.1 Use of NQClient (BI ODBC Client) Utility Is Deprecated

Impacted Releases: 11.1.1.5

Platforms: All

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.

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

Platforms: All

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

1.12.1.3 FIRST and LAST Aggregation Rules Cause Inconsistent Sorting for Time Dimensions

Impacted Releases: 11.1.1.3, 11.1.1.5

Platforms: All

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.

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

Platforms: All

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 1.12.1.7, "Configuring a Servlet for Oracle BI Server Communication with Oracle OLAP" for more information.

1.12.1.5 Must Use JDBC Connection String When Importing from Oracle OLAP

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Platforms: All

Because the Administration Tool uses the JavaHost process to connect to Oracle OLAP data sources for metadata import, which uses JDBC to connect rather than OCI, you must provide a fully-qualified JDBC connection string (host:port:sid) for Data Source Name in the Import Wizard in the Administration Tool when importing from Oracle OLAP sources. Ensure that the JavaHost process can connect to the Oracle OLAP data source using this connection string.

After import is complete, you must update the connection pool object in the Physical layer for the Oracle OLAP source to change the Data Source Name to a valid OCI value, either a net service name or a full OCI connect string.

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 1.12.1.7, "Configuring a Servlet for Oracle BI Server Communication with Oracle OLAP" for more information.

1.12.1.6 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

Platforms: All

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

1.12.1.7 Configuring a Servlet for Oracle BI Server Communication with Oracle OLAP

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2

Platforms: All

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 1.12.1.4, "Oracle OLAP Jars on JavaHost Computer Must Be Updated When Using Oracle OLAP 11.2.x"

- Section 1.12.1.5, "Must Use JDBC Connection String When Importing from Oracle OLAP"

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

1.12.1.8 Enhancing Performance of Aggregates with TimesTen Release 11.2.2.3 or Later

Impacted Releases: 11.1.1.6.2

Platforms: All

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

1.12.1.9 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

Platforms: All

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.

1.12.1.10 Create Aggregates Operations Can Time Out for TimesTen Targets

Impacted Releases: 11.1.1.6.2, 11.1.1.7

Platforms: All

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 five entries:

call ttoptsetflag('rowlock',0)
call ttoptsetflag('tbllock',1)
call ttoptsetflag('mergejoin',0)
call ttoptsetflag('nestedloop',1)
call ttoptsetflag('fastprepare',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.

1.12.1.11 Logical Display Folders Are Deleted During MUD Publish

Impacted Release: 11.1.1.7

Platforms: All

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.

1.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 1.12.2.1, "Oracle Call Interface (OCI) Issue Causes Oracle BI Server Crash on Windows when Under Heavy Load and Connecting to Oracle Database 11g"

- Section 1.12.2.2, "Configuration Required for Microsoft SQL Server and Oracle BI Summary Advisor"

1.12.2.1 Oracle Call Interface (OCI) Issue Causes Oracle BI Server Crash on Windows when Under Heavy Load and Connecting to Oracle Database 11g

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2, 11.1.1.7

Platforms: Microsoft Windows (32-Bit)

Due to an issue in the Oracle Call Interface (OCI) client for the Oracle Database 11g, unexpected Oracle BI Server crashes might occur when the BI Server is running on Microsoft Windows platform and there are a significant number of concurrent users attempting to connect to the Oracle Database 11g.

The workaround is to apply a Windows patch bundle for Oracle Database Client 11.1.0.7, patch bundle 27 or higher.

1.12.2.2 Configuration Required for Microsoft SQL Server and Oracle BI Summary Advisor

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2

Platforms: All

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.

1.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 1.12.3.1, "Administration Tool Incorrectly Displays Option for Generate Deployment File"

- Section 1.12.3.2, "Issue with Online Import Object Checkout"

- Section 1.12.3.3, "Ignore RPD Consistency Warnings Related to Required Database Feature Changes for Oracle OLAP"

- Section 1.12.3.4, "Select Nullable Option for Root Member of Parent-Child Hierarchies from OLAP Sources"

- Section 1.12.3.5, "Administration Tool Fails to Launch from the Start Menu"

- Section 1.12.3.6, "Problems with Icons in Some Administration Tool Installations"

- Section 1.12.3.7, "Oracle BI Repository Can Become Corrupt When Objects Are Deleted in MUD Environments"

- Section 1.12.3.8, "Manually Map DFF VOs from ADF Data Sources into the Business Model and Mapping and Presentation Layers"

- Section 1.12.3.9, "Error Message Text Missing when Using Summary Advisor in Client Installations of the Administration Tool"

- Section 1.12.3.10, "Model Checker Not Enabled in Release 11.1.1.6.2"

- Section 1.12.3.11, "Publishing a Duplicate Dimension Object in a MUD Environment"

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

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

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

Impacted Releases: 11.1.1.5

Platforms: All

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 1.1.1, "Obtaining Patches from My Oracle Support" for more information about downloading patches.

1.12.3.5 Administration Tool Fails to Launch from the Start Menu

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2

Platforms: Microsoft Windows (64-Bit)

The Administration Tool fails to launch from Start menu in a non-English Windows 7 64-bit client installation. This is caused by the SERVER EVENT MSG MISSED.

The workaround is to launch the Administration Tool from ORACLE_HOME\bifoundation\server\bin directly as follows:

1. In Windows Explorer, go to the following location:

ORACLE_HOME/bifoundation/server/bin

2. Double-click bi-init.cmd to display a command prompt that is initialized to the Oracle instance.

3. At the command prompt, type admintool and press Enter.

1.12.3.6 Problems with Icons in Some Administration Tool Installations

Impacted Releases: 11.1.1.5, 11.1.1.6.0

Platforms: Microsoft Windows (32-Bit)

If the Administration Tool installation does not display toolbar icons correctly (for example, if the icons are displayed as empty squares), download and install the Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update appropriate for the platform. For example, download vcredist_x64.exe for 64-bit systems, or vcredist_x86.exe for 32-bit systems. After performing this task, the icons are displayed properly.

You can find the appropriate redistributable package for your system at the following link:

http://www.microsoft.com/download/en/details.aspx?&id=14431

Alternatively, you can search based on the package title. For security reasons, you should only download redistributable packages from the Microsoft Web site.

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

Impacted Releases: 11.1.1.6.0

Platforms: All

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 1.1.1, "Obtaining Patches from My Oracle Support" for more information about downloading patches.

1.12.3.8 Manually Map DFF VOs from ADF Data Sources into the Business Model and Mapping and Presentation Layers

Impacted Releases: 11.1.1.6.2

Platforms: All

When you use the Import Metadata Wizard to import DFF VOs from ADF data sources, do not use the Map to Logical Model screen of the Import Metadata Wizard to automatically map them to the Business Model and Mapping and Presentation layers. When you use the Map to Logical Model screen to automatically map DFF VOs, all presentation columns that re related to the corresponding logical tables are deleted.

To work around this issue, manually map the DFF VOs into the other layers using drag-and-drop.

1.12.3.9 Error Message Text Missing when Using Summary Advisor in Client Installations of the Administration Tool

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2

Platforms: All

This issue is fixed in Release 11.1.1.6.2, Bundle Patch 1.

If an error occurs when you are using Oracle BI Summary Advisor in client installations of the Administration Tool, only an error code is displayed. The text of the error message is missing.

This problem happens because the Oracle Business Intelligence client installer does not install the error message file for Summary Advisor. This problem does not occur in full Oracle Business Intelligence installations on Windows.

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

- Copy AggrAdvisor.xml from a full Oracle Business Intelligence installation (on any platform) to the client installation. For example, copy:

MWHOME1\Oracle_BI1\bifoundation\server\locale\l_en\AggrAdvisor.xml

to:

C:\Program Files\Oracle Business Intelligence Enterprise Edition Plus
Client\oraclebi\orahome\bifoundation\server\locale\l_en\AggrAdvisor.xml

- Install the full installation of Oracle Business Intelligence on Windows. Use the Administration Tool that is included with the full installation.

Tip:

If the NQSErrors 98033, 98038, 98039, or 98040 are displayed when Summary Advisor is launched, verify that the following elements exist and function correctly in the RPD and in NQSConfig.INI:

- Usage Tracking Table

- Usage Tracking Connection Pool

- Summary Advisor Table

See "Using Oracle BI Summary Advisor to Identify Query Candidates for Aggregation" in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition for more information. After these elements are configured correctly, Summary Advisor functions normally.

1.12.3.10 Model Checker Not Enabled in Release 11.1.1.6.2

Impacted Releases: 11.1.1.6.2

Platforms: All

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.

1.12.3.11 Publishing a Duplicate Dimension Object in a MUD Environment

Impacted Releases: 11.1.1.6.2, 11.1.1.7

Platforms: All

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.

1.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 1.13.1, "General System Administration Issues and Workarounds"

- Section 1.13.2, "Configuration Issues and Workarounds"

- Section 1.13.3, "Deployment, Availability, and Capacity Issues and Workarounds"

- Section 1.13.4, "Sign-in and Security Issues and Workarounds"

- Section 1.13.5, "Oracle BI Scheduler Issues and Workarounds"

- Section 1.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" in Oracle Fusion Middleware Infrastructure Release Notes might also be relevant.

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

1.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 1.13.2.1, "Removal of DefaultImageType and HardenXSS Elements"

1.13.2.1 Removal of DefaultImageType and HardenXSS Elements

Impacted Releases: 11.1.1.5

Platforms: All

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.

1.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" in Oracle Fusion Middleware Infrastructure Release Notes.

1.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 1.6.2, "Security-related Upgrade Issues and Workarounds".

This section includes the following topic:

- Section 1.13.4.1, "Permission Required to Open Catalog Manager in Online Mode"

1.13.4.1 Permission Required to Open Catalog Manager in Online Mode

Impacted Releases: 11.1.1.5

Platforms: All

Only users with the OPSS permission oracle.bi.presentation.catman.manageCatalog can open the Catalog Manager in online mode.

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

1.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 1.13.6.1, "Ensure that the Installation Uses a JDK Installed into a Folder that Does Not Contain Spaces"

- Section 1.13.6.2, "Essbase SQL Interface Using Oracle Call Interface (OCI) to Connect to Oracle Requires Oracle Instant Client"

- Section 1.13.6.3, "Options to Set Accessibility Preferences When Using Workspace Are Not Available"

- Section 1.13.6.4, "Issue with Dashboards Menu in EPM Workspace"

- Section 1.13.6.5, "Merant 6.1 ODBC Drivers Are Not Configured on Linux"

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

Platforms: All

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.

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

Platforms: All

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.

1.13.6.3 Options to Set Accessibility Preferences When Using Workspace Are Not Available

Impacted Releases: 11.1.1.7

Platforms: All

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

1.13.6.4 Issue with Dashboards Menu in EPM Workspace

Impacted Releases: 11.1.1.7

Platforms: All

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.

1.13.6.5 Merant 6.1 ODBC Drivers Are Not Configured on Linux

Impacted Releases: 11.1.1.7

Platforms: All

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.

1.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 1.14.1, "General Integration Issues and Workarounds"

- Section 1.14.2, "Oracle Business Intelligence API Issues and Workarounds"

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

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

1.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 1.15.1, "Product Localization Issues and Workarounds"

- Section 1.15.2, "Help System Localization Issues and Workarounds"

1.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 1.15.1.1, "Unable to Save Strings with Multibyte Characters to an External File Using ANSI Encoding"

- Section 1.15.1.2, "BI Publisher User Interface Components Do Not Support Supplementary Characters"

- Section 1.15.1.3, "Non-English Log Files Displayed Incorrectly in Fusion Middleware Control"

- Section 1.15.1.4, "Error Messages in BI Publisher Data Model Editor Honor Server Locale Setting"

- Section 1.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 1.15.1.6, "Excel2007 Output in BI Publisher Does Not Honor Locale Settings for Number and Date Format"

- Section 1.15.1.7, "Excel2007 Output in BI Publisher Supports Gregorian Calendar Only"

- Section 1.15.1.8, "Template Builder for Microsoft Word Chart Wizard Does Not Format Dates"

- Section 1.15.1.9, "Number and Date Format Issues with Charts in BI Publisher Layout Templates"

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

- Section 1.15.1.11, "Albany Fonts Delivered with BI Publisher for PDF Output Do Not Support Bold and Italic for Multibyte Characters"

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

Impacted Releases: 11.1.1.5

Platforms: All

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.

1.15.1.2 BI Publisher User Interface Components Do Not Support Supplementary Characters

Impacted Releases: 11.1.1.3, 11.1.1.5

Platforms: All

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.

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

Impacted Releases: 11.1.1.5

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

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

Impacted Releases: 11.1.1.5

Platforms: All

The Excel2007 output format does not honor locale settings for some number and date fields coded to be locale-sensitive in the layout template.

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

Platforms: All

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)

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

Platforms: All

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')

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

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

1.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 1.15.2.1, "Oracle Business Intelligence Help Systems Are Not Translated"

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

Platforms: All

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

1.16 Oracle Exalytics In-Memory Machine Issues and Workarounds

Issues and workarounds related to Oracle Exalytics In-Memory Machine are described in Oracle Exalytics Release Notes, which is included in the Oracle Exalytics Documentation Library, at http://docs.oracle.com/cd/E27027_01/doc.1/e35146/toc.htm.

1.17 Oracle Business Intelligence Documentation Errata

This section describes errata in Oracle Business Intelligence documentation and help systems. It includes the following topics:

- Section 1.17.1, "General Oracle Business Intelligence Documentation Errata"

- Section 1.17.2, "Oracle Fusion Middleware Quick Installation Guide for Oracle Business Intelligence"

- Section 1.17.3, "Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence"

- Section 1.17.4, "Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence Enterprise Edition"

- Section 1.17.5, "Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition"

- Section 1.17.6, "Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Mobile"

- Section 1.17.7, "Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition"

- Section 1.17.8, "Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition"

- Section 1.17.9, "Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition"

- Section 1.17.10, "Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence"

- Section 1.17.11, "Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition"

- Section 1.17.12, "Oracle Fusion Middleware Integrator's Guide for Oracle Business Intelligence Enterprise Edition"

- Section 1.17.13, "Oracle Fusion Middleware XML Schema Reference for Oracle Business Intelligence Enterprise Edition"

- Section 1.17.14, "Oracle Business Intelligence Help System Errata"

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

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

1.17.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 1.17.3.1, "Installation Guide Contains Misinformation About Installing the Client Tools"

- Section 1.17.3.2, "Installation Guide Contains Misinformation About pasteBinary Script"

- Section 1.17.3.3, "List of Supported Oracle BI Client Tools for Microsoft Windows x64"

- Section 1.17.3.4, "Installation Guide Contains Misinformation About Installing on a Hardened Database"

1.17.3.1 Installation Guide Contains Misinformation About Installing the Client Tools

Impacted Releases: 11.1.1.5

Platforms: All

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.

1.17.3.2 Installation Guide Contains Misinformation About pasteBinary Script

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2

Platforms: All

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.

1.17.3.3 List of Supported Oracle BI Client Tools for Microsoft Windows x64

Platforms: Microsoft Windows (64-Bit)

Section 4.6.1, "Installing Oracle Business Intelligence Client Tools" of the Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence, incorrectly lists the following as not supported on Microsoft Windows x64:

- Oracle Business Intelligence ODBC Driver

- Oracle Business Intelligence JDBC Driver

1.17.3.4 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

Platforms: All

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

1.17.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 1.17.4.1, "Incorrect Information on Aggregation"

- Section 1.17.4.2, "Incorrect Information on Database Authentication"

1.17.4.1 Incorrect Information on Aggregation

Impacted Releases: 11.1.1.5, 11.1.1.6.0, 11.1.1.6.2

Platforms: All

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

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

Platforms: All

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.

1.17.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 1.17.5.1, "Oracle BI Mobile: Embedding a Dashboard or Answers Report Link in an E-mail"

- Section 1.17.5.2, "Oracle BI Mobile: Easy Access to Dashboards"

- Section 1.17.5.3, "Information about Oracle Hyperion Smart View for Office Must Be Ignored"

- Section 1.17.5.4, "Columns from Multiple Subject Areas Included in a Single Query Must Be Compatible"

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

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

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

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

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

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

- Section 1.17.5.11, "Information on View Latest Version Feature in Error"

- Section 1.17.5.12, "Changes to the Instructions for Installing and Configuring BI Composer"

- Section 1.17.5.13, "Mentions of the KPI Editor: Data Input Security Page Must Be Ignored"

- Section 1.17.5.14, "Misinformation About Oracle Endeca Server and Full-Text Search"

- Section 1.17.5.15, "Breadcrumbs Disabled for Embedded Objects in ADF"

- Section 1.17.5.16, "Note on Fixed Headers with Scrolling Content Is Incorrect"

- Section 1.17.5.17, "Misinformation About Adding HTML Code in Prompt Labels"

- Section 1.17.5.18, "Enable on Totals for Action Links Not Described"

- Section 1.17.5.19, "Use of Multiple Values in Presentation Variable on Dashboards Not Described"

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

Impacted Releases: 11.1.1.5

Platforms: All

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.

1.17.5.2 Oracle BI Mobile: Easy Access to Dashboards

Impacted Releases: 11.1.1.5

Platforms: All

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.

1.17.5.3 Information about Oracle Hyperion Smart View for Office Must Be Ignored

Impacted Releases: 11.1.1.5, 11.1.1.6.0

Platforms: All

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

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

Platforms: All

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

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

Platforms: All

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.

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

Impacted Releases: 11.1.1.5

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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%

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

Impacted Releases: 11.1.1.5

Platforms: All

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.

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

Platforms: All

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

1.17.5.12 Changes to the Instructions for Installing and Configuring BI Composer

Impacted Releases: 11.1.1.5

Platforms: All

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.

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

Impacted Release: 11.1.1.6.2

Platforms: All

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.

1.17.5.14 Misinformation About Oracle Endeca Server and Full-Text Search

Impacted Release: 11.1.1.7

Platforms: All

This issue is fixed in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (E10544-06).

The "Searching for Objects" and "Searching for Objects in the Catalog" topics in Chapter 13, and the "Search pane" in Appendix E, "User Interface Reference" contain the following misinformation in regards to specifying a wildcard (*) character when using full-text searching in Oracle BI EE that is configured with Oracle Endeca Server:

"If you are using Oracle BI Enterprise Edition configured to use Oracle Endeca Search, then a search using the wildcard character of an asterisk (*) is not available."

Disregard this statement. You can use the wildcard character to search for objects.

1.17.5.15 Breadcrumbs Disabled for Embedded Objects in ADF

Impacted Release: 11.1.1.7

Platforms: All

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.

1.17.5.16 Note on Fixed Headers with Scrolling Content Is Incorrect

Impacted Releases: 11.1.1.7

Platforms: All

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.

1.17.5.17 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

Platforms: All

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.

1.17.5.18 Enable on Totals for Action Links Not Described

Impacted Release: 11.1.1.7

Platforms: All

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

1.17.5.19 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

Platforms: All

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

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

1.17.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 1.17.7.1, "Important Changes to Essbase Preconfiguration Instructions"

- Section 1.17.7.2, "Manual opmn.xml Edits Needed to Use Teradata as a Data Source"

- Section 1.17.7.3, "Updates to Text for Consistency Check Warnings 39009 and 39059"

- Section 1.17.7.4, "Other Changes to List of New Consistency Check Warnings"

- Section 1.17.7.5, "Select the Virtual Private Database Option when Authenticating Against Essbase or Hyperion Financial Management Using a Shared Token"

- Section 1.17.7.6, "Manually Updating the Master MUD Repository"

- Section 1.17.7.7, "Configuration Required for Client Installations of the Administration Tool to Perform Offline Imports from Oracle OLAP and Hyperion Financial Management Data Sources"

- Section 1.17.7.8, "Database Client Installation Required for Client Installations of the Administration Tool when Importing from Oracle Database and Oracle OLAP Sources"

- Section 1.17.7.9, "Initialization Block Failure at Server Start-Up Causes Connection Pool to be Blacklisted"

- Section 1.17.7.10, "Merge Local Changes Step Does Not Lock the Master Repository"

- Section 1.17.7.11, "Information Now Available for All Import Metadata Wizard Screens"

- Section 1.17.7.12, "Remove Smart View Mention in Appendix C"

- Section 1.17.7.13, "Explicitly Check Out Projects to Add Objects in a Multiuser Development Environment"

- Section 1.17.7.14, "Changes to DataDirect Drivers and Directories"

- Section 1.17.7.15, "Additional Information Available on SCM Configuration Template Files"

- Section 1.17.7.16, "Additional Information Available on TimesTen Compressed Tables"

- Section 1.17.7.17, "Statement on Aggregate Creation Failure is Incorrect"

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

1.17.7.1 Important Changes to Essbase Preconfiguration Instructions

Impacted Releases: 11.1.1.3, 11.1.1.5

Platforms: All

This issue is fixed in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (E10540-03).

Note the following changes to the topic "Setting Up Essbase Data Sources" in Chapter 4, "Importing Metadata and Working with Data Sources" in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition:

- The Administration Tool requires Essbase client libraries version 11.1.2.x. Do not use other client versions. Although other versions of the Essbase client libraries might work with the Oracle BI Server, the recommended approach for Oracle BI Server connectivity to Essbase is to use the bundled 11.1.2.x client.

- By default, Oracle Business Intelligence is configured to use the bundled version of the Essbase client libraries in ORACLE_HOME/clients/epm/Essbase/EssbaseRTC. You do not typically need to make manual changes to opmn.xml on the Oracle BI Server computer for Essbase setup. However, the bi-init.cmd changes described in the topic "Setting Up Essbase Data Sources" are still required.

- If you have installed the Administration Tool using the Client install type, you must ensure that the Essbase client is present on the Administration Tool client computer. You must then update bi-init.cmd to include required variable and path information, as described in the topic "Setting Up Essbase Data Sources."

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

Impacted Releases: 11.1.1.3, 11.1.1.5

Platforms: All

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

1.17.7.3 Updates to Text for Consistency Check Warnings 39009 and 39059

Impacted Releases: 11.1.1.5

Platforms: All

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

1.17.7.4 Other Changes to List of New Consistency Check Warnings

Impacted Releases: 11.1.1.3, 11.1.1.5

Platforms: All

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

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

Impacted Releases: 11.1.1.5

Platforms: All

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.

1.17.7.6 Manually Updating the Master MUD Repository

Impacted Releases: 11.1.1.5

Platforms: All

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

1.17.7.7 Configuration Required for Client Installations of the Administration Tool to Perform Offline Imports from Oracle OLAP and Hyperion Financial Management Data Sources

Impacted Releases: 11.1.1.5

Platforms: All

This issue is fixed in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (E10540-03).

If you install the Administration Tool using the Oracle Business Intelligence Enterprise Edition Plus Client Installer, you must perform additional configuration before you can perform offline imports from Oracle OLAP or Hyperion Financial Management data sources. To import from either of these data sources in offline mode, the Administration Tool must point to the location of a running JavaHost.

Follow these steps to point the Administration Tool at a running JavaHost:

1. Close the Administration Tool, if it is open.

2. On the same computer as the Administration Tool, open the local NQSConfig.INI file in a text editor. You can find this file at:

ORACLE_INSTANCE/config/OracleBIServerComponent/coreapplication_obisn

3. Locate the JAVAHOST_HOSTNAME_OR_IP_ADDRESSES parameter, near the bottom of the file. Update this parameter to point to a running JavaHost, using a fully-qualified host name or IP address and port number. For example:

JAVAHOST_HOSTNAME_OR_IP_ADDRESSES = "myhost.example.com:9810"

Note that in a full (non-client) Oracle Business Intelligence installation, you cannot manually edit this setting because it is managed by Oracle Enterprise Manager Fusion Middleware Control.

4. Save and close the file.

1.17.7.8 Database Client Installation Required for Client Installations of the Administration Tool when Importing from Oracle Database and Oracle OLAP Sources

Impacted Releases: 11.1.1.5

Platforms: All

This issue is fixed in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (E10540-03).

If you install the Administration Tool using the Oracle Business Intelligence Enterprise Edition Plus Client Installer, you must install the Oracle Database Client on the Administration Tool computer before you can import from Oracle Database or Oracle OLAP sources. Use either the Administrator or Runtime client install option.

If you are running a 32-bit Administration Tool, you must install the 32-bit Oracle Database Client. If you are running a 64-bit Administration Tool, you must install the 64-bit Oracle Database Client.

After installing the Oracle Database Client, create an environment variable called ORACLE_HOME and set it to the Oracle home for the Oracle Database Client. Then, create an environment variable called TNS_ADMIN and set it to the location of the TNSNAMES.ORA file (ORACLE_HOME\network\admin).

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

Impacted Releases: 11.1.1.5

Platforms: All

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.

1.17.7.10 Merge Local Changes Step Does Not Lock the Master Repository

Impacted Releases: 11.1.1.5

Platforms: All

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.

1.17.7.11 Information Now Available for All Import Metadata Wizard Screens

Impacted Releases: 11.1.1.5

Platforms: All

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.

1.17.7.12 Remove Smart View Mention in Appendix C

Impacted Releases: 11.1.1.5, 11.1.1.6.0

Platforms: All

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

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

Impacted Releases: 11.1.1.6.0

Platforms: All

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.

1.17.7.14 Changes to DataDirect Drivers and Directories

Impacted Releases: 11.1.1.5, 11.1.1.6.0

Platforms: All

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/

1.17.7.15 Additional Information Available on SCM Configuration Template Files

Impacted Releases: 11.1.1.6.2

Platforms: All

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

1.17.7.16 Additional Information Available on TimesTen Compressed Tables

Impacted Releases: 11.1.1.6.2

Platforms: All

The following additional information is available for the section "Tips for Creating Aggregates on TimesTen Sources:"

If you want to create aggregates with compressed tables in TimesTen, then turn on the database feature COMPRESSED_COLUMNS in the Features tab of the Database dialog in the Oracle BI Administration Tool.

1.17.7.17 Statement on Aggregate Creation Failure is Incorrect

Impacted Releases: 11.1.1.6.2

Platforms: All

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

1.17.7.18 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

Platforms: All

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.

1.17.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 1.17.8.1, "Event Polling Tables Must Be Created Using the Repository Creation Utility (RCU)"

- Section 1.17.8.2, "Use of ps: Prefix in Elements Is Unnecessary"

- Section 1.17.8.3, "Lowercase for Boolean Values for Configuration Elements"

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

- Section 1.17.8.5, "Issue Copying a Jar File when Registering with EPM Workspace Release 11.2.3.00"

- Section 1.17.8.6, "Incomplete Information in "Validating the Catalog" Section"

- Section 1.17.8.7, "Missing Privilege for Using the Full-Text Catalog Search"

- Section 1.17.8.8, "Error for Configuring the Data Source for the Full-Text Catalog Search"

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

- Section 1.17.8.10, "MaxColumns Element Not Supported"

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

- Section 1.17.8.12, "Clarification of CaseInsensitiveMode Element"

- Section 1.17.8.13, "Updates of Information About the Catalog"

- Section 1.17.8.14, "Section on Manually Configuring for Interactions In Views Does Not Apply"

- Section 1.17.8.15, "Omission of Enabled Element in Custom Links Section"

- Section 1.17.8.16, "Omission of Section on Updating Java Development Kit (JDK)"

- Section 1.17.8.17, "Remove Mention of pasteBinary Script"

- Section 1.17.8.18, "Parameter Descriptions Missing or Inaccurate in NQSConfig.INI File Configuration Settings Appendix"

- Section 1.17.8.19, "Incorrect Commands to Start and Stop Administration Server on a Windows Environment"

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

Impacted Releases: 11.1.1.3, 11.1.1.5

Platforms: All

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.

1.17.8.2 Use of ps: Prefix in Elements Is Unnecessary

Impacted Releases: 11.1.1.5, 11.1.1.6.0

Platforms: All

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.

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

Platforms: All

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.

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

Platforms: All

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

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

Impacted Releases: 11.1.1.7

Platforms: All

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

1.17.8.6 Incomplete Information in "Validating the Catalog" Section

Impacted Releases: 11.1.1.5

Platforms: All

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

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

Platforms: All

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.

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

Impacted Releases: 11.1.1.5

Platforms: All

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)

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

Impacted Releases: 11.1.1.3

Platforms: All

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.

1.17.8.10 MaxColumns Element Not Supported

Impacted Releases: 11.1.1.5

Platforms: All

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.

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

Impacted Releases: 11.1.1.3

Platforms: All

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>

1.17.8.12 Clarification of CaseInsensitiveMode Element

Impacted Releases: 11.1.1.3

Platforms: All

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>

1.17.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 1.17.8.13.1, "Guidelines for Object Names"

- Section 1.17.8.13.2, "Handling Users of the Catalog"

- Section 1.17.8.13.3, "Handling Heterogeneous Nodes"

- Section 1.17.8.13.4, "Handling Catalog Files on Various Platforms"

- Section 1.17.8.13.5, "Known Issues with Catalog Files"

- Section 1.17.8.13.6, "Validating the Catalog"

- Section 1.17.8.13.7, "Performing a Basic Validation of the Catalog"

- Section 1.17.8.13.8, "Specifying the Elements for Validating the Catalog"

- Section 1.17.8.13.9, "Updates for XML Files and Text Strings"

1.17.8.13.1 Guidelines for Object Names

Impacted Releases: 11.1.1.3

Platforms: All

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 1.17.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"\?

1.17.8.13.2 Handling Users of the Catalog

Impacted Releases: 11.1.1.3

Platforms: All

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

1.17.8.13.3 Handling Heterogeneous Nodes

Impacted Releases: 11.1.1.3

Platforms: All

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

1.17.8.13.4 Handling Catalog Files on Various Platforms

Impacted Releases: 11.1.1.3

Platforms: All

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.

1.17.8.13.5 Known Issues with Catalog Files

Impacted Releases: 11.1.1.3

Platforms: All

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

1.17.8.13.6 Validating the Catalog

Impacted Releases: 11.1.1.3

Platforms: All

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.

1.17.8.13.7 Performing a Basic Validation of the Catalog

Impacted Releases: 11.1.1.3

Platforms: All

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

1.17.8.13.8 Specifying the Elements for Validating the Catalog

Impacted Releases: 11.1.1.3

Platforms: All

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

1.17.8.13.9 Updates for XML Files and Text Strings

Impacted Releases: 11.1.1.3

Platforms: All

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 1-4 provides sample strings for use with the regex syntax in search criteria.

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

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

Platforms: All

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.

1.17.8.15 Omission of Enabled Element in Custom Links Section

Impacted Releases: 11.1.1.6.0

Platforms: All

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.

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

Platforms: All

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.

1.17.8.17 Remove Mention of pasteBinary Script

Impacted Releases: 11.1.1.6.0, 11.1.1.6.2

Platforms: All

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.

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

Impacted Releases: 11.1.1.7

Platforms: All

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.

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

Impacted Releases: 11.1.1.7

Platforms: All

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.

1.17.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 1.17.9.1, "SASchInvoke Always Prompts for the Password in 11.1.1.5"

- Section 1.17.9.2, "Setup Multiple Authentication Providers"

- Section 1.17.9.3, "Error in Code Example for Refreshing User GUIDs"

- Section 1.17.9.4, "Adding UserName Attribute Properties user.login.attr and username.attr to Identity Store is Not Applicable"

- Section 1.17.9.5, "Removal of Invalid LDAP Configuration Properties when Setting Up SSL"

- Section 1.17.9.6, "Error in Code Example for Configuring a Database Adaptor"

- Section 1.17.9.7, "Error in Code Example for Configuring the WebLogic Server Environment"

1.17.9.1 SASchInvoke Always Prompts for the Password in 11.1.1.5

Impacted Releases: 11.1.1.5

Platforms: All

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.

1.17.9.2 Setup Multiple Authentication Providers

Impacted Releases: 11.1.1.5

Platforms: All

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.

1.17.9.3 Error in Code Example for Refreshing User GUIDs

Impacted Releases: 11.1.1.5, 11.1.1.6.0

Platforms: All

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>

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

Impacted Releases: 11.1.1.6

Platforms: All

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

1.17.9.5 Removal of Invalid LDAP Configuration Properties when Setting Up SSL

Impacted Releases: 11.1.1.7

Platforms: All

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.

1.17.9.6 Error in Code Example for Configuring a Database Adaptor

Impacted Releases: 11.1.1.6

Platforms: All

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>

1.17.9.7 Error in Code Example for Configuring the WebLogic Server Environment

Impacted Releases: 11.1.1.7

Platforms: All

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

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

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

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

Platforms: All

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>

1.17.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 1.17.12.1, "Addendum to the "Overview of Integrating with Oracle Business Intelligence" Topic in Chapter 10, "Integrating Other Clients with Oracle Business Intelligence""

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

Platforms: All

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

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

1.17.14 Oracle Business Intelligence Help System Errata

This section describes errata in the Oracle Business Intelligence help systems. It includes the following topics:

- Section 1.17.14.1, "Incorrect Statement on Source Control Management and Multiuser Development in Administration Tool Online Help"

- Section 1.17.14.2, "Addendum to the Oracle BI Server DSN Configuration Wizard Help"

1.17.14.1 Incorrect Statement on Source Control Management and Multiuser Development in Administration Tool Online Help

Impacted Releases: 11.1.1.6.0

Platforms: All

In the Administration Tool online help, in the topic "About Using a Source Control Management System with the Administration Tool," the following statement appears:

"As an alternative to using the Multiuser Development (MUD) environment described in Chapter 3, you can instead choose to integrate the Administration Tool with a third-party source control management system, such as Subversion or Rational ClearCase."

This statement is incorrect. Integration with a source control management system can be used with MUD and complements the MUD process, but source control management integration cannot replace the advanced features of using a MUD environment.

This statement has been corrected in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition. See this book for the latest text.

1.17.14.2 Addendum to the Oracle BI Server DSN Configuration Wizard Help

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6

Platforms: All

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

2 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 2.1, "Patch Requirements"

- Section 2.2, "Oracle Business Intelligence Applications Release Notes"

- Section 2.3, "Oracle Business Intelligence Data Warehouse Administration Console (DAC) Platform Release Notes"

Note:

Issues relating to DAC metadata are located in Section 2.2, "Oracle Business Intelligence Applications Release Notes". Issues relating to DAC platform are located in Section 2.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

2.1 Patch Requirements

This section describes patch requirements for Oracle Business Intelligence Applications.

2.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 "Downloading and Applying Required Patches" in Oracle Fusion Middleware Infrastructure Release Notes.

2.2 Oracle Business Intelligence Applications Release Notes

This section describes issues associated specifically with Oracle Business Intelligence Applications, and includes the following sections:

- Section 2.2.1, "Oracle Business Intelligence Applications Issues and Workarounds Identified Since the Previous Revision"

- Section 2.2.2, "General Issues and Workarounds for Oracle Business Intelligence Applications"

- Section 2.2.3, "Installation Issues and Workarounds for Oracle Business Intelligence Applications"

- Section 2.2.4, "Upgrade Issues and Workarounds for Oracle Business Intelligence Applications"

- Section 2.2.5, "Oracle Business Intelligence Applications Offering/Module-specific Issues"

- Section 2.2.8, "Oracle Business Intelligence Applications Configuration Manager and FSM Issues"

- Section 2.2.9, "Security-related Issues for Oracle Business Intelligence Applications"

- Section 2.2.10, "Oracle Business Intelligence Applications Documentation Errata"

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

No issues and workarounds have been identified since the previous revision.

2.2.2 General Issues and Workarounds for Oracle Business Intelligence Applications

This section describes general issues and workarounds related to Oracle Business Intelligence Applications.

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

Impacted Releases: 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.

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

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

Impacted Releases: 11.1.1.5.1, 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.

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

Impacted Releases: 11.1.1.5.1, 11.1.1.5.2, 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).

2.2.2.5 NLS:SDE_FUSION_DOMAINGENERAL_SALESINVOICESOURCE_FULL Failed With Syntax Error

Impacted Releases: 11.1.1.5.1, 11.1.1.5.2, 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.

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

Impacted Releases: 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.

2.2.2.7 JAZN File Not Translated

Impacted Releases: 11.1.1.6.2

The JAZN file is not translated in this release. There is no work-around for this issue.

2.2.2.8 Duplicate Rows in GL Account Segment Hierarchy Tables

Impacted Releases: 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
);

2.2.2.9 Rename Informatica Files With Upper Case XML Extension To Lower Case

Impacted Releases: From 11.1.1.5.2 to 11.1.1.6.4 (fixed in 11.1.1.7.0)

Before you launch the BI Extender utility on Linux, you need to rename all the files in the <ORACLE_HOME>/bifoundation/javahost/lib/obisintegration/biextender/EM/RS/infa folder that have an upper case XML extension (XML) to a lower case extension (xml).

For example: The file \EM\RS\infa\INF\TP\SIL_SampleFact.XML should be renamed to \EM\RS\infa\INF\TP\SIL_SampleFact.xml.

Workaround

Rename Informatica files with upper case XML extension to lower case.

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

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

Impacted Releases: From 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).

2.2.3 Installation Issues and Workarounds for Oracle Business Intelligence Applications

This section describes issues and workarounds related to installing Oracle Business Intelligence.

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

Impacted Releases: 11.1.1.5.1, 11.1.1.5.2, 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.

2.2.3.2 Restarting Components After Completing The Post-Installation Setup Steps

Impacted Releases: 11.1.1.5.1, 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).

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

Impacted Releases: 11.1.1.5.1, 11.1.1.5.2, 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.

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

2.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 2.2.5.1, "Issues for Oracle Customer Data Management Analytics Offering"

- Section 2.2.5.2, "Issues for Oracle Financial Analytics Offering"

- Section 2.2.5.3, "Issues for Oracle Human Resources Analytics Offering"

- Section 2.2.5.4, "Issues for Oracle Marketing Analytics Offering"

- Section 2.2.5.5, "Issues for Oracle Partner Analytics Offering"

- Section 2.2.5.6, "Issues for Oracle Product Information Management Analytics Offering"

- Section 2.2.5.7, "Issues for Oracle Procurement and Spend Analytics Offering"

- Section 2.2.5.8, "Issues for Oracle Project Analytics Offering"

- Section 2.2.5.9, "Issues for Oracle Sales Analytics Offering"

- Section 2.2.5.10, "Issues for Oracle Supply Chain and Order Management Analytics Offering"

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

2.2.5.2 Issues for Oracle Financial Analytics Offering

This section describes issues and workarounds related to Oracle Financial Analytics Offering.

2.2.5.2.1 Overlapping Aging Bucket Ranges in AP/AR Aging

Impacted Releases: 11.1.1.5.0, 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.

2.2.5.2.2 Construction In Progress Integration with Fixed Assets subject area

Project - Construction in Progress is a detailed subject area that provides dimensions and metrics to report on projects where assets are constructed over a period of time.

This new subject area shares the Fixed Asset (Asset), Asset Category, and Asset Location dimensions with the Financial Analytics Fixed Assets subject area. The shared dimensions allow Fixed Assets users to drill down to Project Analytics CIP reports, using attributes such as Asset Number or Asset Book Code, to view Construction in Progress Cost, Interfaced Construction in Progress Cost and Expenses related with the projects associated with the construction of their fixed assets.

To be able to use this drill down functionality, users need to have licensed and implemented the Financial Analytics Fixed Assets and the Project Analytics Construction in Progress Subject Areas.

2.2.5.3 Issues for Oracle Human Resources Analytics Offering

This section describes issues and workarounds related to Oracle Human Resources Analytics Offering.

2.2.5.3.1 Incorrect Metrics Showing Current Year

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

2.2.5.3.2 Member Mappings Not Displayed For FSM Tasks Relating to Ranged Domains

Impacted Releases: 11.1.1.5.1, 11.1.1.5.2, 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.

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

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

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

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

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

2.2.5.7.1 Null Values Included In Level-Based Metric Report

Impacted Releases: 11.1.1.5.1, 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))
...

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

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

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

2.2.6 Translated Content in Non-English Reports and Dashboards

Impacted Releases: 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.

2.2.7 Error in Execution of Task SDE_FUSION_PayrollRunBalanceDetailFact

Impacted Releases: 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';

2.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:
Impacted Releases: 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
Impacted Releases: 11.1.1.5.1, 11.1.1.5.2, 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
Impacted Releases: 11.1.1.5.1, 11.1.1.5.2, 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
Impacted Releases: 11.1.1.5.1, 11.1.1.5.2, 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
Impacted Releases: 11.1.1.5.1, 11.1.1.5.2, 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
Impacted Releases: 11.1.1.5.1, 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
Impacted Releases: 11.1.1.5.1, 11.1.1.5.2, 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
Impacted Releases 11.1.1.5.1, 11.1.1.5.2, 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.

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

2.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 2.2.10.1, "General Oracle Business Intelligence Documentation Errata"

- Section 2.2.10.2, "Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications"

- Section 2.2.10.3, "Oracle BI Applications Configuration Manager Help System"

- Section 2.2.10.4, "Oracle Fusion Middleware Reference Guide for Oracle Business Intelligence Applications"

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

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

- Impacted Releases: 11.1.1.5.2, 11.1.1.6.0, 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.

- Impacted Releases: 11.1.1.5.1, 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)))

- Impacted Releases: 11.1.1.5.1, 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.

- Impacted Release: 11.1.1.7.0
Section B.20 'How to Integrate Project Analytics with Financial Analytics' and its associated FSM/BI Applications Configuration Manager help topic are duplicates. Refer instead to Section B.29 'How to Integrate Financial Analytics with Project Analytics'.

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

2.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).
Impacted Releases: 11.1.1.5.2, 11.1.1.6.0, 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.

- Impacted Releases: 11.1.1.5.1, 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)))

- Impacted Releases: 11.1.1.5.1, 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.

2.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 2.3.1, "DAC Issues and Workarounds Identified Since the Previous Revision"

- Section 2.3.2, "DAC General Issues and Workarounds"

- Section 2.3.3, "DAC Installation Issues and Workarounds"

- Section 2.3.4, "DAC Upgrade Issues and Workarounds"

- Section 2.3.5, "DAC Documentation Errata"

2.3.1 DAC Issues and Workarounds Identified Since the Previous Revision

There are no known issues identified since the previous revision.

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

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

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

2.3.5 DAC Documentation Errata

This section describes errata in DAC documentation and help systems. It includes the following topics:

- Section 2.3.5.1, "Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console"

- Section 2.3.5.2, "DAC Client Help System"

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

Impacted Releases: 11.1.1.6.x, 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.

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

3 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 3.1, "Oracle RTD General Issues and Workarounds"

- Section 3.2, "Oracle RTD Installation Issues and Workarounds"

- Section 3.3, "Oracle RTD Upgrade Issues and Workarounds"

- Section 3.4, "Oracle RTD Configuration Issues and Workarounds"

- Section 3.5, "Oracle RTD Security Issues and Workarounds"

- Section 3.6, "Oracle RTD Administration Issues and Workarounds"

- Section 3.7, "Oracle RTD Integration Issues and Workarounds"

- Section 3.8, "Oracle RTD Decision Studio Issues and Workarounds"

- Section 3.9, "Oracle RTD Decision Center Issues and Workarounds"

- Section 3.10, "Oracle RTD Performance Monitoring Issues and Workarounds"

- Section 3.11, "Oracle RTD Externalized Objects Management Issues and Workarounds"

- Section 3.12, "Oracle RTD Localization Issues and Workarounds"

- Section 3.13, "Oracle RTD Documentation Errata"

- Section 3.14, "Oracle RTD Third-Party Software Information"

Depending on your Oracle Fusion Middleware implementation, some information in other chapters of Oracle Fusion Middleware Infrastructure Release Notes 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"

3.1 Oracle RTD General Issues and Workarounds

This section describes general issues and workarounds related to Oracle RTD. It includes the following topics:

- Section 3.1.1, "Transient Likelihood Problems"

- Section 3.1.2, "Use Development Deployment State Only"

- Section 3.1.3, "Error Deploying Inline Services from Command Line if Inline Service Uses Certain Functions"

- Section 3.1.4, "Ensuring Unique Batch Names Across a Cluster"

- Section 3.1.5, "Safari and Chrome Accessibility Items"

- Section 3.1.6, "Learning Service May Skip Processing of Some Learning Records if SDDB is on Oracle RAC Database"

- Section 3.1.7, "External Rule Editor Does Not Work in Mozilla Firefox Version 16"

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

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

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

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

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

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

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

3.2 Oracle RTD Installation Issues and Workarounds

There are no known issues at this time.

3.3 Oracle RTD Upgrade Issues and Workarounds

There are no known issues at this time.

3.4 Oracle RTD Configuration Issues and Workarounds

There are no known issues at this time.

3.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 3.5.1, "Decision Center Logout Not Redirected Correctly for Oracle Access Manager (OAM) 11g Form-Based Authentication"

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

3.6 Oracle RTD Administration Issues and Workarounds

There are no known issues at this time.

3.7 Oracle RTD Integration Issues and Workarounds

This section describes issues and workarounds related to Oracle RTD integration. It includes the following topic:

- Section 3.7.1, "Java Smart Client Run Configuration Changes Required for Different Properties Files"

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

3.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 3.8.1, "Mapping Array Attributes in a Multi-Level Entity Hierarchy"

- Section 3.8.2, "Issues When Trying to Enable Caching for Some Entities"

- Section 3.8.3, "Terminate Active Sessions in Cluster Works Only on Decision Server Receiving Deployment Request"

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

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

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

3.9 Oracle RTD Decision Center Issues and Workarounds

There are no known issues at this time.

3.10 Oracle RTD Performance Monitoring Issues and Workarounds

There are no known issues at this time.

3.11 Oracle RTD Externalized Objects Management Issues and Workarounds

There are no known issues at this time.

3.12 Oracle RTD Localization Issues and Workarounds

There are no known issues at this time.

3.13 Oracle RTD Documentation Errata

This section describes errata in Oracle RTD documentation and help systems. It includes the following topic:

- Section 3.13.1, "Oracle Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions"

- Section 3.13.2, "Oracle Fusion Middleware Platform Developer's Guide for Oracle Real-Time Decisions"

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

3.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 3.13.2.1, "External Rules Development Helper Mismatch between Code and Manual Description"

- Section 3.13.2.2, "Save Choice IDs in Inline Services Rather Than Choices"

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

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

3.14 Oracle RTD Third-Party Software Information

This section provides third-party software information. It includes the following topic:

- Section 3.14.1, "Displaytag Download Location"

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