41 Oracle Business Intelligence

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

Impacted Releases: 11.1.1.5

If an attribute column's Value Suppression setting (in the Column Format tab of the Column Properties dialog) is not set to Repeat, then the measure is aggregated to the grain as defined by the position of the column with the format defined. This might cause a change in the conditional formatting after upgrading from Oracle Business Intelligence Release 10g to Release 11g. If the Value Suppression setting is set to Repeat, then the measure column that the conditional format is based on always uses the detail grain of the table view, in which case the conditional formatting works as expected.

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

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

41.6.2.2 Users or Groups With Names Containing Invalid Characters Are Not Upgraded

Impacted Releases: 11.1.1.5, 11.1.1.6

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.

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

Impacted Releases: 11.1.1.5, 11.1.1.6

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.

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

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.

41.7.1.2 Gauge Views May Be Cut Off and Not Visible Under Certain Conditions

Impacted Releases: 11.1.1.5

Under certain conditions, if the size of the canvas assigned to a gauge view is very small, and the legend is set to display on the left, then some of the gauges in the gauge view may 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.

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

Impacted Releases: 11.1.1.5, 11.1.1.6

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.

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

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.

41.7.1.5 Scorecard Diagrams on Dashboard Pages May Print as Tables

Impacted Releases: 11.1.1.5, 11.1.1.6

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.

41.7.1.6 Using Maps with Column Selectors

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6

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.

41.7.1.7 Support for Rendering Small Form-Factor Graphs

Impacted Releases: 11.1.1.5

This release includes support for rendering small form-factor graphs, for example, graphs that are 75 pixels X 25 pixels or 68 pixels X 18 pixels. Small form-factor graphs are also referred to as micrographs.

To render a small form-factor graph:

1. Edit the analysis.

2. Edit the graph.

3. Click the Edit graph properties toolbar button to display the Graph Properties dialog.

4. In the General tab, make the following settings:

   • In the Legend Location box, select None.

   • Deselect the Animate graph on Display box.

5. Click the Style tab and make the following settings:

   • In the Style box in the Graph Data area, select Default.

   • In the Plot area, select the Specify option for Gridlines.

   • For Major Grid, deselect the Horizontal Lines and Vertical Lines boxes.

   • For Minor Grid, deselect the Horizontal Lines box.

   • In the Legend area, deselect the Transparent box.

   • In the Canvas Colors and Borders area, deselect the Gradient box.

6. Click the Titles and Labels tab and make the following settings:

   • In the Graph Title area, deselect the Use measure name as graph title box.

   • In the Axis titles area, deselect the following boxes:

     • Use measure name as axis title for Vertical Axis 1 Title

     • Use measure name as axis title for Vertical Axis 2 Title

     • Use column name as axis title for Horizontal Axis Title

7. Click OK to close the Graph Properties dialog.

8. Click Done to close the Graph editor.

9. Click the Analysis editor: Advanced tab.

10. Save a copy of the existing XML in the XML Code box as a backup.

11. In the XML Code box in the Analysis XML area, add the following attribute to the display element for the graph that you want to render as a small form-factor graph:

    useAutoLayout="false"
    

    For example:

    <saw:display type="line" subtype="default" renderFormat="flash" mode="online" xAxisLiveScrolling="false" yAxisLiveScrolling="false" clientEventEnabled="false"  animateOnDisplay="false" useAutoLayout="false"> 
    

    Important:

    Do not use this setting for a graph that is a reasonable size, such as, a graph that is 400 pixels X 300 pixels. Doing so may result in undesirable graph behavior or loss of information.

12. Click Apply XML.

13. Click Save Analysis.

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

Impacted Releases: 11.1.1.5, 11.1.1.6

Analyses whose paths contain Latin Supplement characters fail to open on dashboard pages when the locale is Chinese, Japanese, Korean, Hebrew, or Arabic and you are using Internet Explorer 7 as the Web browser.

The workaround is to append &charset=utf-8 to the URL.

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

Impacted Releases: 11.1.1.6

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 will yield no results.

This issue has no workaround.

41.7.1.10 Interactions on Right-Click Menus Are Not Translated

Impacted Releases: 11.1.1.6

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

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

Impacted Releases: 11.1.1.5, 11.1.1.6

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.

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

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.

41.7.3.2 Item Stale Error When Editing a Shared Scorecard in Parallel

Impacted Releases: 11.1.1.5, 11.1.1.6

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.

41.7.4.1 Agent Deliveries Fail with Microsoft Active Directory and Oracle Virtual Directory

Impacted Releases: 11.1.1.5, 11.1.1.6

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.

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

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.

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

Impacted Releases: 11.1.1.5, 11.1.1.6

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

41.7.5.2 Server Connections Are Not Automatically Shared by Microsoft Excel and PowerPoint

Impacted Releases: 11.1.1.5, 11.1.1.6

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.

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

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.

41.7.5.4 Install a Language Pack for Non-English Languages

Impacted Releases: 11.1.1.3, 11.1.1.5

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

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

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

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

Impacted Releases: 11.1.1.5

In Oracle BI Add-in for Microsoft Excel, you cannot refresh table views or pivot table views with double columns in the page edge. To work around this issue, ensure that double columns are not in the page edge (also called table prompt in table views and the pivot prompt in pivot table views).

41.7.5.7 Double Column Cascading Results in Incorrect Display Values

Impacted Releases: 11.1.1.5, 11.1.1.6

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

41.7.5.8 Intermittent Timeout Errors

Impacted Releases: 11.1.1.5, 11.1.1.6

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.

41.7.5.9 Lack of Support for Vary Color By Target Area

Impacted Releases: 11.1.1.5

If you use the Vary Color By target area for graph views when creating analyses in Oracle BI EE, then you might find that the results are displayed incorrectly in Microsoft Excel and PowerPoint.

41.7.5.10 Measure Column Labels May Display Incorrectly When Inserted into Microsoft Excel

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6

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 may display incorrectly when inserted into Microsoft Excel.

The workaround is to not use measure columns in the section edge or page edge.

41.7.5.11 Stacked Graphs Do Not Display Negative Values

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6

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.

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

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.

41.7.5.13 Graphs With Section Edges Are Not Supported in Release 11.1.1.6.0

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6

Release 11.1.1.6.0 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 will be returned when it is refreshed in Release 11.1.1.6.0.

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

In German or Arabic Versions of Microsoft Excel 2007 or 2010, number formatting may be lost after table views that have been secured are refreshed.

41.7.5.15 Inserting a View With a Grand Total Column or Row into Microsoft Office May Cause Issues

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6

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.

41.7.5.16 Time Displayed in Table or Pivot View Title May Be Incorrect after Insertion

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6

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 may be incorrect.

41.7.5.17 Graphs May Be Displayed Differently After Insertion into Microsoft Office

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6

Graphs that are inserted into Microsoft Office may be plotted differently in Microsoft Office than they are in Oracle BI EE. In horizontal bar graphs, the horizontal-axis series may be displayed in reverse order. In stacked graphs, the stack order may be reversed. This is caused by the Microsoft graph engine.

41.7.5.18 Legends in Bubble and Scatter Graphs May Display Differently After Insertion into Microsoft Office

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6

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 may not match those displayed in Oracle BI EE.

This issue has no workaround.

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

Impacted Releases: 11.1.1.6

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.

41.9.1.1 JDBC Driver Throws Unsupported Function for setBigDecimal

Impacted Releases: 11.1.1.5, 11.1.1.6

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

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

Impacted Releases: 11.1.1.5

When Oracle BI Publisher is installed in integrated mode with Oracle BI EE, searching the catalog from the BI Publisher user interface (that is, the URL is of the form "http://<host>:<port>/xmlpserver/...") does not work and the following message is returned:

Result Not found
Your search - <search criteria> - did not match any documents.

The workaround is to search the catalog from the Oracle BI EE user interface (that is, the URL is of the form "http://<host>:<port>/analytics/...").

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

Impacted Releases: 11.1.1.5

When configuring a JDBC data source connection or an OLAP connection, the list provided in the BI Publisher Add Data Source page may 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."

41.9.1.4 Menu Items Do Not Display When Using Internet Explorer 7 with a Bidirectional Language Preference

Impacted Releases: 11.1.1.5, 11.1.1.6

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, use Internet Explorer 8 or another supported Web browser.

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

Impacted Releases: 11.1.1.3, 11.1.1.5

When you create an OLAP data source connection to a Microsoft SQL Server 2008 Analysis Services data source in the BI Publisher Administration interface, the data source is not saved after you click the Apply button, even though the connection test succeeds.

To work around this issue, select "Microsoft SQL Server 2005 Analysis Services" as the OLAP Type from the list. Enter the same connection information and click Apply.

41.9.1.6 Issues with Viewing Some Report Formats on Apple iPad

Impacted Releases: 11.1.1.5, 11.1.1.6

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.

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

Impacted Releases: 11.1.1.3, 11.1.1.5

In the Oracle BI Presentation Catalog, if a folder name contains the single quote character (') BI Publisher reports that reside in that folder do not run and data models might throw unexpected errors. The behavior varies depending on the Web browser.

To work around this issue, do not include single quotes in the names of folders that contain BI Publisher objects.

41.9.1.8 Components Folder Missing from SampleApp Lite Web Catalog

Impacted Releases: 11.1.1.5

Version 11.1.1.5 of the SampleApp Lite Web catalog is missing the Components folder. As a result, shared boilerplates are unavailable when user creates a new BI Publisher type layout for a BI Publisher report. To work around this issue:

1. Log in with administrator credentials and navigate to the BI Publisher Administration > Server Configuration page.

2. Under the Catalog region, ensure that the BI Publisher Repository field points to the default path:

   <Install_Home>/user_projects/domains/bifoundation_domain/config/bipublisher/repository

   Then click the Upload to BI Presentation Catalog button.

3. Navigate to the Catalog page and verify that the Components folder is present under Shared Folders.

Note that this also installs additional BI Publisher sample reports included in the Samples folder. Many of these reports require that the Demo JDBC connection to the OE sample schema, included in Oracle Database, is configured.

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

Impacted Releases: 11.1.1.6

Several of the Boilerplate templates in the Components folder included in version 11.1.1.6 of the SampleApp Lite OBIEE Web catalog, when used as the starting point to create an XPT layout, do not display table borders properly in Chrome Browsers. To correct this behavior, replace the Components folder in SampleApp Lite OBIEE Web catalog with the one included with the BI Publisher standalone repository. To do so:

1. Log in with administrator credentials and navigate to the BI Publisher Administration > Server Configuration page.

2. Under the Catalog region, ensure that the BI Publisher Repository field points to the default path:

   <Install_Home>/user_projects/domains/bifoundation_domain/config/bipublisher/repository

   Then click the Upload to BI Presentation Catalog button.

3. Navigate to the Catalog page and verify that the Components folder is present under Shared Folders.

Note that this also installs additional BI Publisher sample reports included in the Samples folder. Many of these reports require that the Demo JDBC connection to the OE sample schema, included in Oracle Database, is configured.

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

Impacted Releases: Upgrades from 11.1.1.3 to 11.1.1.6

In Release 11.1.1.5, the local policy attachments were removed from the BI Publisher Web services. If you were using the BI Publisher Web services in Release 11.1.1.3 and you upgrade to 11.1.1.5, then you must perform the following to add a Global Policy Attachment (GPA):

1. Log in to Oracle Enterprise Manager Fusion Middleware Control.

2. In the left pane, click WegLogic 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 will be 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

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

Impacted Release: 11.1.1.3

The XDK used by Oracle BI Publisher requires the JVM of the Oracle WebLogic Server to run in en-US locale. Otherwise, functions (such as sum) generate values that cannot be formatted with its number format functions.

To work around this problem, in the script startWebLogic.cmd add the following line to set the required options:

set JAVA_OPTIONS=-Dfile.encoding=UTF-8 -Duser.language=en -Duser.region=US %JAVA_OPTIONS% 

For information on setting Java options in the Oracle WebLogic Server Administration Console, see the topic "Set Java options for servers started by Node Manager" in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.

41.9.1.12 Search May Return Incorrect Number of Results

Impacted Release: 11.1.1.6

Searching for catalog items may yield more results than there actually are. For example, a search on all types of catalog items using "Salary" may 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.

41.9.1.13 Schedule Report Option Does Not Appear Correctly for Non-Admin Users

Impacted Release: 11.1.1.6

Users with a role other than Administrator (for example: BI Author and BI Consumer) will not see the Schedule action link under report entries in the catalog; nor will 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.

41.9.2.1 Limitations for Administrator Username in LDAP Security Model

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6

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, scheduled jobs will fail with an impersonation error.

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

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.

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

Impacted Releases: 11.1.1.6

During upgrade, the data in 10g scheduler schema will be migrated to 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 will fail 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.

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

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 may 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 will fail 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 will work 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(...))

41.9.6.1 Limitations for Excel Template Output on Apple iPad

Impacted Releases: 11.1.1.5, 11.1.1.6

Due to limitations with the native Excel reader on the Apple iPad, Excel template output documents will have the following limitations when viewed on the iPad:

• Formulas intended to dynamically calculate in the output will not work

• Macros will not execute

• Pivot tables cannot be refreshed

• Hyperlinks will not work

• Workbook headers and footers will not display

• If using the Oracle Business Intelligence Mobile application on an iPad, the parameters will not show. However, if accessing the report via the Safari browser, the parameters will display.

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

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.

41.9.7.2 Excel Analyzer Does Not Support 64-Bit Windows Platform

Impacted Releases: 11.1.1.6

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.

41.9.8.1 Editing an XPT Layout and Clicking Return in Layout Editor Results in Exception

Impacted Releases: 11.1.1.3, 11.1.1.5

When viewing a report using a layout that is not set as the Default Layout, and you select Edit Layout from the Report Viewer's action drop-down menu to open the layout in the layout editor, and then you click Return, you might encounter the following issue: The Report Viewer tries to open the report using the default output format (PDF, HTML, and so on) specified for the default layout. This might cause the report to fail with the following error if the default output format for the default layout is not one of the output formats allowed for the selected layout:

The report cannot be rendered because of an error, please contact the administrator. Error Detail oracle.xdo.servlet.data.DataException: Invalid format requested: html 

41.9.9.1 Data Model Is Not Editable When Created by Upgrade Assistant

Impacted Releases: 11.1.1.5, 11.1.1.6

A report that is upgraded from Release 10g to 11g will have a report and a data model 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 will not be able to 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.

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

Impacted Releases: 11.1.1.3, 11.1.1.5

In the data model editor if you edit a data set of the type View Object, after you click OK, all the elements in the data set will be duplicated.

To work around this issue, you must delete the data set and recreate it.

41.9.10.1 No Direct Conversion Between Oracle Reports and Oracle BI Publisher 11g

Impacted Releases: 11.1.1.5, 11.1.1.6

There is no direct conversion between Oracle Reports and Oracle BI Publisher 11g. To convert a report created in Oracle Reports to an Oracle BI Publisher report, 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).

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

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

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

41.10.2.1 Removal of DefaultImageType and HardenXSS Elements

Impacted Releases: 11.1.1.5

In Release 11.1.1.5, the following elements are no longer supported and should be removed from the instanceconfig.xml file:

• DefaultImageType element

• HardenXSS element

If the instanceconfig.xml file includes the HardenXSS element when a user starts Oracle BI EE, then an error message is displayed. The error log file will state that startup was affected by the inclusion of the HardenXSS element.

The workaround is to remove the HardenXSS element from the instanceconfig.xml file.

41.10.4.1 Permission Required to Open Catalog Manager in Online Mode

Impacted Releases: 11.1.1.5

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

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

Impacted Releases: 11.1.1.5

When trying to export externalized strings that contain multibyte characters, the option to save the file using ANSI encoding does not work properly.

To work around this problem, save the file using UTF-8 or Unicode encoding.

41.13.1.2 BI Publisher User Interface Components Do Not Support Supplementary Characters

Impacted Releases: 11.1.1.3, 11.1.1.5

BI Publisher does not support supplementary characters in object names in the user interface, for example, report name, data model name, layout name, and so on. The data model editor does not support supplementary characters in SQL queries. The scheduler does not support supplementary characters in input fields such as e-mail subject and message fields.

To work around this issue, do not use supplementary characters in the BI Publisher user interface. If your database table and column names already include supplementary characters, you cannot use the data model editor to retrieve the data from these.

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

Impacted Releases: 11.1.1.5

You might have log files for Presentation Services, Oracle BI Scheduler, and Cluster Controller that have been translated to languages other than English. You might find that the content of these log files is not displayed correctly in the Diagnostic Log table and in tooltips in Fusion Middleware Control.

To work around this issue, enter the following property for logreader in the component-logs.xml file in the ORACLE_INSTANCE/config directory:

<property name="encoding" value="UTF-8"/>

Add the property in the component-logs.xml file in the following subdirectories: OracleBIPresentationServicesComponent, OracleBISchedulerComponent, and OracleBIClusterControllerComponent.

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

Impacted Releases: 11.1.1.5, 11.1.1.6

Error messages invoked while working in the BI Publisher data model editor may display according to the server locale setting rather than the user interface locale setting.

This issue has no workaround.

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

If the locale for the Oracle BI Server is Arabic or Hebrew, then no matter what the client locale for Presentation Services is, you will 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.

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

Impacted Releases: 11.1.1.5

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

41.13.1.7 Excel2007 Output in BI Publisher Supports Gregorian Calendar Only

Impacted Releases: 11.1.1.5, 11.1.1.6

The following calendars are not supported for Excel 2007 output format. The report output will revert to use the GREGORIAN calendar.

• ARABIC_HIJRAH

• ENGLISH_HIJRAH

• JAPANESE_IMPERIAL

• THAI_BUDDHA

• ROC_OFFICIAL (Taiwan)

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

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

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

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

41.13.2.1 Oracle Business Intelligence Help Systems Are Not Translated

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6

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, 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/technology/software/products/ias/files/fusion_certification.html

41.14.3.1 Installation Guide Contains Misinformation About Installing the Client Tools

Impacted Releases: 11.1.1.5

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 11g Installer always installs 32-bit versions of the client tools. Rather, 32-bit versions of the Oracle Business Intelligence 11g Installer install 32-bit versions of the client tools, while 64-bit versions of the Oracle Business Intelligence 11g 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 11g 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 11g Installer, and not the Oracle Business Intelligence Enterprise Edition Plus Client Installer.

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

Impacted Releases: 11.1.1.5

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 appears 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 your iPhone or iPad device.

41.14.5.2 Oracle BI Mobile: Easy Access to Dashboards

Impacted Releases: 11.1.1.5

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.

41.14.5.3 Information about Oracle Hyperion Smart View for Office Must Be Ignored

Impacted Releases: 11.1.1.5, 11.1.1.6

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 41.4.2, "Oracle Hyperion Smart View for Office Not Supported in Oracle Business Intelligence 11g, Releases 11.1.1.5 and Later."

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

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

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

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 your Administrator modified the default pixel value in the Oracle BI EE configuration file.

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

Impacted Releases: 11.1.1.5

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.

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

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.

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

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.

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

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%

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

Impacted Releases: 11.1.1.5

The "New Filter dialog" topic requires the following corrections: The topic states that if your 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.

41.14.5.11 Information on View Latest Version Feature in Error

Impacted Releases: 11.1.1.3, 11.1.1.5, 11.1.1.6

The "BI Publisher Report Properties dialog" topic and the "Selecting a BI Publisher Report for a Dashboard Page" topic in Appendix E, "User Interface Reference" provide information on the View Latest Version feature in error. This feature is not currently available.

41.14.7.1 Important Changes to Essbase Preconfiguration Instructions

Impacted Releases: 11.1.1.3, 11.1.1.5

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

41.14.7.2 Updates to Text for Consistency Check Warnings 39009 and 39059

Impacted Releases: 11.1.1.5

In the section "New Features for Oracle BI EE 11g 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."

41.14.7.3 Other Changes to List of New Consistency Check Warnings

Impacted Releases: 11.1.1.3, 11.1.1.5

In the section "New Features for Oracle BI EE 11g 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."

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

Impacted Releases: 11.1.1.5

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

41.14.7.5 Manually Updating the Master MUD Repository

Impacted Releases: 11.1.1.5

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 need to 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 your 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
   

41.14.7.6 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

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.

41.14.7.7 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

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

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

Impacted Releases: 11.1.1.5

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 appears in the server log:

[OracleBIServerComponent] [ERROR:1] [43143] Blacklisted connection pool conn_pool_name

If you see this error, check the initialization blocks for the given connection pool to ensure that they are correct.

41.14.7.9 Merge Local Changes Step Does Not Lock the Master Repository

Impacted Releases: 11.1.1.5

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, the system will automatically redo the merge with the master. To redo the merge, the system must roll back to the RPD version you used for the Merge Local Changes step, and will then merge 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 you made between merge and publish if a rollback becomes necessary for a merge redo.

41.14.7.10 Information Now Available for All Import Metadata Wizard Screens

Impacted Releases: 11.1.1.5

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.

41.14.7.11 Remove Smart View Mention in Appendix C

Impacted Releases: 11.1.1.5, 11.1.1.6

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 41.4.2, "Oracle Hyperion Smart View for Office Not Supported in Oracle Business Intelligence 11g, Releases 11.1.1.5 and Later."

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

Impacted Releases: 11.1.1.3, 11.1.1.5

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

41.14.8.2 Use of ps: Prefix in Elements Is Unnecessary

Impacted Releases: 11.1.1.5, 11.1.1.6

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.

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

Impacted Releases: 11.1.1.5, 11.1.1.6

Section 11.5, "Configuring to Download Oracle Hyperion Smart View for Office," must be ignored, as described in Section 41.4.2, "Oracle Hyperion Smart View for Office Not Supported in Oracle Business Intelligence 11g, Releases 11.1.1.5 and Later."

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

Impacted Releases: 11.1.1.5

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)

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

Impacted Releases: 11.1.1.3

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.

41.14.8.6 MaxColumns Element Not Supported

Impacted Releases: 11.1.1.5

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.

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

Impacted Releases: 11.1.1.3

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>

41.14.8.8 Clarification of CaseInsensitiveMode Element

Impacted Releases: 11.1.1.3

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>

41.14.8.9 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 41.14.8.9.1, "Guidelines for Object Names"

• Section 41.14.8.9.2, "Handling Users of the Catalog"

• Section 41.14.8.9.3, "Handling Heterogeneous Nodes"

• Section 41.14.8.9.4, "Handling Catalog Files on Various Platforms"

• Section 41.14.8.9.5, "Known Issues with Catalog Files"

• Section 41.14.8.9.6, "Validating the Catalog"

• Section 41.14.8.9.7, "Performing a Basic Validation of the Catalog"

• Section 41.14.8.9.8, "Specifying the Elements for Validating the Catalog"

• Section 41.14.8.9.9, "Updates for XML Files and Text Strings"

<?xml version="1.0" encoding="utf-8"?>
<actions>
<action command="textReplace" oldValue="boots" newValue="HoleyShoes" ignoreCase="true"/>
</actions>

41.14.9.1 SASchInvoke Always Prompts for the Password in 11.1.1.5

Impacted Releases: 11.1.1.5

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 appears when you run the command under SSL, but a password prompt appears regardless of SSL-enablement. The caution was confusing and has been removed for the E10543-04 revision.

41.14.9.2 Setup Multiple Authentication Providers

Impacted Releases: 11.1.1.5

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.

41.14.9.3 Error in Code Example for Refreshing User GUIDs

Impacted Releases: 11.1.1.5, 11.1.1.6

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>

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

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>

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

Impacted Releases: 11.1.1.6

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.