Skip Headers
Oracle® Business Intelligence Suite Enterprise Edition Release Notes
Release 10.1.3.4.2

Part Number E10404-34
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

2 Oracle BI EE Release Notes

The following list describes the sections of this chapter:

2.1 Oracle Business Intelligence Server

This section provides release notes for the Oracle Business Intelligence Server (Oracle BI Server). It contains the following topics:

2.1.1 Drag and Drop for XMLA Data Sources

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

On Windows systems, you can use a "drag and drop" feature in the Administration Tool for XMLA data sources (SAP/BW and Microsoft Analysis Server).

This capability allows for physical metadata objects (such as cubes) to be dragged and dropped into the Administration Tool as fully configured Business Model metadata, thus retaining metrics, attributes, and dimensions. This mitigates the need to manually redefine logical dimensional models from data sources that contain rich dimensional metadata constructs.

Enable this feature by performing the following steps:

  1. Install Oracle Business Intelligence Suite Enterprise Edition on a Windows system.

  2. Create the Windows system variable called OBIAT_XMLA_DD with a value of Yes.

  3. Restart the Administration Tool.

2.1.2 Issues with Full Outer Join and WITH Clause on Oracle Database 10g

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

If you use a version of Oracle Database 10g Release 2 before 10.2.0.3, then you might encounter an issue with a Full Outer Join that causes severe database performance issues and appears to hang the database when the BI Server sends to the database SQL queries that include WITH clauses.

To work around this issue when using Oracle Database 10g Release 1 or 2, upgrade to Oracle Database 10g Release 2 Patch Set 2 (for 10.2.0.3). For performance reasons, this is the preferred workaround.

To work around this issue without installing Patch Set 2, modify the Database Features table using the Administration Tool. This configuration prevents the Oracle BI Server from sending SQL constructs that expose the issue in an unpatched Oracle Database 10g.

To modify the Database Features table:

  1. In the Administration Tool, open the properties of the Physical Database metadata object.

  2. Navigate to the Features tab.

  3. Ensure the values for the PERF_PREFER_MINIMAL_WITH_USAGE and PERF_PREFER_INTERNAL_STITCH_JOIN entries are selected, that is, set to True.

2.1.3 Certain Combinations of Ago() Columns with Level-Based Measures Generate Oracle Database Errors

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When you use certain combinations of Ago() columns with level-based measure
columns, you might see an Oracle Database error such as "ORA-00942: table or view does not exist at OCI call OCIStmtExecute."

To work around this issue when using Oracle Database 10g Release 2, install Patch Set 2 (for 10.2.0.3) and turn on the native Full Outer Join support. For performance reasons, this is the preferred workaround.

To work around this issue without installing Patch Set 2, set "PERF_PREFER_INTERNAL_STITCH_JOIN" to True in the Database Features table, as described in Section 2.1.2, "Issues with Full Outer Join and WITH Clause on Oracle Database 10g".

2.1.4 Column Dropped When Using a Report as a Filter for Another Report

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When you use a report to constrain the results of another report and the child report has a filter on a measure, then the optimizer might eliminate the measure column from the final results. To work around this issue, add a superfluous measure filter to the parent report, such as the following one:

'measure'<>0

2.1.5 INTERVAL Data Type Is Imported as LONGVARBINARY

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When you import a database object that contains columns of data with the INTERVAL type, you find that the imported data has the LONGVARBINARY type. Oracle Business Intelligence Suite Enterprise Edition does not support the INTERVAL data type directly. The data should be imported with a data type of UNKNOWN.

To work around this issue, remove the data of type INTERVAL from the business mapping and do not include that data as part of a query request.

2.1.6 Check Boxes in Consistency Check Window Do Not Reflect the Settings in the Options Tab

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

You can disable the high-level options (that is Warnings, Errors, or Best Practices) on the Options tab in the Consistency Check window, but that disabling does not automatically uncheck the corresponding check boxes within the Messages tab. Because the system applies the settings in the Consistency Check window rather than on the Messages tab, the appropriate high-level options are disabled.

This issue has no workaround.

2.1.7 Misleading Error Messages During Import

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When you are importing from an XMLA data source, you might see one of the following error messages, which might be inappropriate or misleading:

  • [nQSError: 64001] The file not found

    This message can be inappropriately displayed when the file that you are importing does exist but is not well formed. To work around this issue, ensure that the file exists, that the file is well-formed, and that all tags in the file are in the proper order and syntax.

2.1.8 Error Message About Oracle BI Server Not Running

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

You might see an error message that the BI Server is not running under the following situation. You have been working in online mode within the Administration Tool, the BI Server is restarted without the repository or the Administration Tool being closed, and you try to reopen the repository in online mode.

To work around this issue, close the Administration Tool and reopen the repository in online mode.

2.1.9 Misleading Error Message for Timed-Out SAP/BW Connection

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When users run a query against data from SAP/BW (Business Information Warehouse) and the connection has timed out, they might see an error message. The error message might not indicate that a time out has occurred.

This issue has no workaround.

2.1.10 Potential Oracle BI Server Failure When Editing Repository in Online Mode

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

If you perform the following steps, then you might cause the BI Server to fail:

  1. Import a new physical schema into the repository.

  2. Delete all existing physical, business model, and presentation objects.

  3. Save the changes.

This issue has no workaround.

2.1.11 TIMESTAMPDIFF Function Causes Incorrect Values for IBM DB2 on OS/390 and AS/400

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

With an IBM DB2 database on the IBM OS/390 and AS/400 operating systems, the TIMESTAMPDIFF function is translated into SQL that approximates the values that the function is processing. This approximation can cause incorrect values to be returned. This issue has no workaround.

2.1.12 In HPUX Environment the Oracle BI Server Stops (or Fails to Start) if ODBC Library Name for Netezza Is Incorrect in odbc (odbc.ini) File

This issue applies to Versions 10.1.3.3.2, 10.1.3.3.3, and 10.1.3.4. It is fixed in 10.1.3.4.1.

This issue applies to Oracle Business Intelligence Enterprise Edition deployed in the HP-UX environment only.

The BI Server stops when connecting to a Netezza data source if the ODBC connection entry for Netezza is incorrect in the odbc.ini file. This stoppage is due to the incorrect name of the Netezza odbc driver (libnzsqlodbc3.sl).

To correct this issue, ensure that the following ODBC driver name is in the odbc.ini file: Driver = <path>/libnzodbc.sl.

2.2 Oracle Business Intelligence Presentation Services

This section provides release notes for Oracle Business Intelligence Presentation Services (Oracle BI Presentation Services). It contains the following topics:

2.2.1 Advanced Search Fields Might Appear Missing in Catalog Manager

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

You might notice missing fields in the Advanced Search area within Catalog Manager. This situation occurs when you toggle between the Explore mode and the Search mode after expanding the Advanced Search area. If fields appear to be missing, then click the Expand icon (a right-facing triangle) next to the Advanced Search text to display the complete option list.

This issue has no workaround.

2.2.2 Changing the Report Path for a Portlet Might Not Update the New Path Correctly

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When you set up portlets for a portal client, you must specify the report path to the content to be displayed. If you try to change the report path later, then the system might not accept a change to a previously saved portlet. To work around this issue, completely remove the existing portlet and create a new portlet with the correct report path.

2.2.3 Device Numbers for iBots Require Standard Strings

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

You can use iBots to allow users to select a device to which the system can send an alert. When a user is entering a number for a device such as a phone, pager, or handheld computer and enters characters other than numbers, the user might notice an error message. To work around this issue, users should enter numbers that contain only digits and not other characters such as periods, hyphens, and parenthesis.

2.2.4 Issue Opening Reports with Non-ASCII Names on Windows 2000 Computers

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

If you download a report that has a non-ASCII name and you attempt to open the report directly from the Save dialog, then you might see a blank report on a Windows 2000 computer. Windows 2000 might have difficulty opening the file due to the inline file name conversion.

To work around this issue, either rename the file to have a name that contains ASCII characters or save the name to the local computer first, then attempt to open the file.

2.2.5 Performance Issues with Multiple Portlets

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

A practical limit exists for the inclusion of Oracle BI portlets within a portal. A variety of factors including report complexity, server memory and CPU, and configuration affect performance. As a general rule, keep the number of distinct portlets served by Oracle Business Intelligence Suite Enterprise Edition to five or less. For the inclusion of larger blocks of content, you can incorporate entire Interactive Dashboards or individual dashboard pages into a portal as a single unit.

2.2.6 How to Deploy BI EE Portlets into WebCenter Suite

This issue applies to Versions 10.1.3.2.1 and 10.1.3.4.

The Oracle Business Intelligence Presentation Services Administration Guide does not contain specific steps to deploy Oracle BI EE ReportUI portlets into WebCenter Suite 10.1.3.2.

Oracle Support Note 427844.1 provides instructions for this deployment.

2.2.7 Bookmark Link Error on Windows with FAT32

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

Using the Bookmark Link feature in Oracle BI Enterprise Edition 10.1.3.3 might result in the following error:

Error: (Response came back as text, not xml)

An error occurred while applying your dashboard selections for this page

This happens when Presentation Services is running on a Microsoft Windows computer with a FAT32 file system. Convert the FAT volumes to NTFS. Refer to your Windows OS documentation for instructions for the file system conversion.

2.2.8 Oracle Business Intelligence Catalog Manager Unable to Open Presentation Catalog in Online Mode on Arabic Windows OS

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

On an Arabic Windows operating system, the Oracle Business Intelligence Catalog Manager cannot open a Presentation Catalog in online mode. A java exception is thrown similar to: 'Uparseable date:2007-10-15T02:42.52.000Z'.

To work around this issue, open the Presentation Catalog in Oracle BI Catalog Manager in offline mode.

2.2.9 Issue Handling Captions in Presentation Services

This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

In the Oracle Business Intelligence Presentation Services Administration Guide, the section "Localizing Presentation Catalog Captions" requires the following updates for exporting and translating captions:

  • The section states twice that you place XML files for translating captions in the following location, which is incorrect:

    SADATADIR\web\res\l_xx\Captions

    The correct location for captions is:

    SADATADIR\web\msgdb\l_<xx>\captions

    where <xx> is the appropriate language code, such as de or fr.

  • The section lists three sample XML files that the export process might create. These files have names with mixed capitalization, which is incorrect. All characters should be lowercase and read as follows:

    marketingcaptions.xml
    salescaptions.xml
    servicecaptions.xml
    
  • In addition, if you add translations in Release 10.1.3.4, you must re-run the Export Captions utility to change all catalog data from using the XML attribute named "captionId" to the attribute named "CaptionID". To run the utility, follow the procedure for exporting Presentation Catalog text strings as described in that section of the guide, with one exception. A step is missing from that procedure. Add a Step 2a as follows:

    Select the folder against which you want to run the Export Captions utility. The utility runs against the files in that folder and all its subfolders.

    In previous releases, you were not prompted to select the folder to run the utility against. If you want the utility to run against the same folder as in previous release, then select the /shared folder.

  • In the procedure for exporting Presentation Catalog text strings as described in that section of the guide, add the following step as the new Step 1 and Step 2 of that procedure:

    1. Back up the catalog before exporting from it.

    2. In Catalog Manager, open the Presentation Catalog in either offline or online mode.

  • The note at the start of the section should be rewritten as follows:

    NOTE: To export text strings, you must open the Presentation Catalog in either offline or online mode. Run the export utility against the actual catalog, not against a copy of the catalog, because the export utility changes the properties of the items in the catalog against which it runs.

2.2.9.1 Handling Duplicate Exported Text Strings

You might encounter an issue of having duplicate exported text strings from the catalog. This situation arises when the Export Captions utility is run simultaneously by multiple users or if the same user runs the utility twice in less than one minute. The following procedure describes how to address duplicate captions.

To handle duplicate exported text strings:

  1. Run the Export Captions utility.

  2. In Catalog Manager, with the catalog still open in offline mode, select the folder that contains the strings to export.

  3. From the Tools menu, select Export Captions.

  4. Click Browse to select the location in which to write the output file, then click OK.

  5. In the "What to do with duplicate captions" section, select one of the following options:

    • Create unique IDs even for identical strings — Specifies to create a unique ID for each instance of a string, even if the string is duplicated many times in the catalog. For example, suppose that a catalog includes the "Hello" string 1000 times. Use this option to specify that rather than generating one unique ID and translating the string only once, you want to instead generate 1000 unique IDs and translate the string 1000 times.

    • No, use the same ID for all identical strings — Specifies to create an ID for a string and use that same ID for all instances of that string. For example, suppose that a catalog includes the "Hello" string 1000 times. Use this option to specify that you want to generate one unique ID and translate the string only once, instead of generating 1000 unique IDs and translating the string 1000 times.

  6. Click OK.

Consider the following webmessages.xml file, which contains duplicate captions:

<WebMessageTable system="catalog" type="folder" path="/shared/example/A">
    <WebMessage name="kcap12790830_5" use="Caption" status="new">
        <TEXT>A Really Good Report</TEXT>
    </WebMessage>
</WebMessageTable>
<WebMessageTable system="catalog" type="folder" path="/shared/example/B">
    <WebMessage name="kcap12790830_5" use="Caption" status="new">
        <TEXT>I like this report</TEXT>
    </WebMessage>
</WebMessageTable>
<WebMessageTable system="catalog" type="folder" path="/shared/example/Copy of A">
    <WebMessage name="kcap12790830_5" use="Caption" status="new">
        <TEXT>A Really Good Report</TEXT>
    </WebMessage>
</WebMessageTable>

In this example file, Object B has an invalid duplicate message ID. Object Copy of A has a valid but duplicate message ID. You can make the following selections in the Export Captions dialog:

  • Selecting Create unique IDs even for identical strings generates new and unique IDs for both Object B and Object Copy of A.

  • Selecting No, use the same ID for all identical strings generates a new and unique ID for Object B and deletes the WebMessage element for Object Copy of A. While this option generally ensures fewer messages to translate, keep in mind that you now see two objects with the same name in a directory listing of the catalog in Presentation Services and in Catalog Manager.

2.2.10 Merge Option No Longer Available in Catalog Manager

This issue applies to Version 10.1.3.4.2.

In previous releases of 10.1.3.x, both the Upgrade and Merge options were available for EBA catalogs from the Tools menu in Catalog Manager. Starting with Release 10.1.3.4.2, the Merge option is no longer available. See Oracle Business Intelligence New Features Guide for information on the upgrading of EBA catalogs.

2.2.11 Issue Handling Case-Sensitivity in Presentation Services for Tasks Such as Searching

This issue applies to Versions 10.1.3.4.1 and 10.1.3.4.2.

You can use the CaseInsensitiveMode element in the instanceconfig.xml file to specify whether to use case sensitivity when performing tasks in Presentation Services that relate to case, such as searching and sorting. The default value is false, and a sample setting is shown below:

<ServerInstance>
<CaseInsensitiveMode>True</CaseInsensitiveMode>
</ServerInstance>

The BI Server has the CASE_SENSITIVE_CHARACTER_COMPARISON parameter that controls whether the BI Server uses case-sensitivity. You should ensure that Presentation Services has the same case-sensitivity setting as the BI Server. To do so, set the CaseInsensitiveMode element to the corresponding value. If the values do not correspond, then you might see inconsistent results in operations such as sorting.

For example, if CASE_SENSITIVE_CHARACTER_COMPARISON is set to On, then set CaseInsensitiveMode to its default value of False so that case-sensitivity is enabled in both places.

For more information, see the description of the CASE_SENSITIVE_CHARACTER_COMPARISON parameter in Oracle Business Intelligence Infrastructure Installation and Configuration Guide.

2.2.12 Including BI Publisher Reports on a Dashboard

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When you include a BI Publisher report on a dashboard, you generally allow that report to participate as a recipient of the dashboard state by passing in dashboard context to that report using core dashboard prompts. For scenarios that do not require passing of context to or from the BI Publisher report to the larger dashboard-based analytic application, you can display a variant of the default BI Publisher toolbar, which exposes the underlying parameter prompts of that BI Publisher report. Within that frame, a user can then pass in parameters to a single BI Publisher report.

This approach can be confusing to the user as any other dashboard prompts on the page do not contribute to the BI Publisher report, which also does not participate in passing context back to the rest of the application. Changes to the BI Publisher toolbar are also applied globally for all BI Publisher reports that are embedded in dashboards across the entire Presentation Server instance.

To configure the alternate BI Publisher toolbar, add the "ReportingToolbarMode" node to the instanceconfig.xml file within the "AdvancedReporting" node and set its value to 6. Remove the "ReportingToolbarMode" node to revert to the default toolbar behavior, as shown in the following example:

<AdvancedReporting> 
   <ReportingToolbarMode>6</ReportingToolbarMode> 
</AdvancedReporting> 

See the "Making Oracle BI Presentation Services Configuration Changes" section in the Oracle Business Intelligence Presentation Services Administration Guide for information on editing the instanceconfig.xml file.

2.2.13 Issue Registering Oracle BI EE on UNIX Computers with EPM Workspace

This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

As you follow the steps to register Oracle BI EE that is installed on a UNIX computer (AIX, HPUX, Solaris and Linux) with EPM Workspace, you might encounter an error message about a nonzero return code. You can ignore this error message, because the registration process has succeeded. You can verify a successful registration by running the EPM System Configurator. You see Oracle BI EE as one of the registered components in the EPM System Configurator. Refer to the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide for information on the EPM System Configurator.

2.2.14 Unable to Navigate from BI Answers to Interactive Dashboards in EPM Workspace

This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

Navigation from Oracle BI Answers to Oracle BI Interactive Dashboards in EPM Workspace is not supported. However, you can navigate from a dashboard to other dashboards or to a dashboard page in EPM Workspace. You can verify the navigation by inserting a BI Answers report on a dashboard.

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

This issue applies to Version 10.1.3.4.2.

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, stop the javahost services on Windows platforms or kill the process on Linux platforms. Edit the run.bat file on Windows platforms or the run.sh file on Linux platforms to add the following line to the java process section:

-Duser.language=en -Duser.region=US

2.3 Oracle Business Intelligence Answers

This section provides release notes for Oracle Business Intelligence Answers (Oracle BI Answers). It contains the following topics:

2.3.1 Refreshing Before Downloading in Compound Layout View

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

As you work in the Compound Layout View, you can change the output by modifying the different views. Before selecting the Download link on the bottom of the page, select the Refresh Results icon. By refreshing first, you ensure that any recent changes are reflected in the downloaded views.

2.3.2 Defining an Aggregation Rule for a Set Operation

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When you use a set operation, ensure that you define an aggregation rule. If you use the default aggregation, then the expression does not work with set operations.

2.3.3 Error When Defining a Measure

This issue applies to Versions 10.1.3.2, 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When you try to define a measure in the Repository, you receive an error message similar to the following:

Error Message: The Attribute xxxx defines a measure using an obsolete method.

This error message appears because of Logical columns containing nested aggregation rules. The method was used in Oracle BI EE releases before 10.1.3.2 but is no longer supported. Beginning in the Oracle BI EE 10.1.3.2 release, Repository administrators can no longer nest an aggregation rule within the logical column.

The following procedure is the correct method to define an aggregation rule for a Logical column.

  1. In the Repository's Business Model view, select the column.

  2. In the Logical Column screen, navigate to the Aggregation tab.

  3. In the Default aggregation rule window, select the rule to be used from the drop down list.

  4. Click OK.

2.3.4 Issue Replacing Columns in Formula Editor

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

As you work in the Formula Editor dialog for a column, you can select an existing column in the formula (by highlighting it) and you can replace it with another column from the column picker. However, when you use certain browser versions, you cannot replace the highlighted column with the new column. To work around this issue, delete the current column before adding the new column.

2.3.5 Issue with Report-Based Total Option

This issue applies to Versions 10.1.3.3 and 10.1.3.3.1. It is fixed in version 10.1.3.3.2.

If the Report-Based Total option is not selected, then you might find that filtering on nested aggregates returns the same result as when the Report-Based Total option is selected. This issue has no workaround.

2.3.6 Session Times Out When Publishing Oracle BI Content to OracleAS Portal

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When you use OracleAS Portal to publish Oracle BI content, you might notice that the portlet session expires. To work around this issue, use the ClientSessionExpireMinutes element in the instanceconfig.xml file to increase the length of the session.

2.3.7 "Resource Not Found" Error Message When Publishing Oracle BI Publisher Content

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

If you notice a "Resource Not Found" error message when attempting to publish an Oracle BI Publisher report to an Oracle BI Dashboard, then the cause is likely a reference to a report with a long name, such as one with 28 or more characters. In these cases, you can work around the issue by republishing the report using a shorter name.

2.3.8 Chart Display Errors in MHTML

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

If an error message or a graphic that contains an "X" in place of a chart appears in a report that was downloaded as MHTML, then the cause likely involves the way that the browser is interpreting the MHTML format. Problems most often arise when opening the MHTML report directly.

To work around this issue, first save the MHTML output as a file, then open that saved file.

2.3.9 Documentation Correction for Format Mask

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

The Oracle Business Intelligence Answers, Delivers, and Interactive Dashboards User Guide incorrectly identifies the position of the format mask when describing the syntax for using variables. The syntax should be changed in the following topics.

In the topic entitled "What is the syntax for referencing repository and presentation variables?", the bullet points should read as follows:

  • @{<variableName>}[format] - for repository variables. For example, @{dashboard.path} inserts the path to the current dashboard.

  • - @{variables.<variableName>}[format]{<value>} - for presentation
    variables. For example, @{variables.myFavoriteRegion}{Central} inserts
    the value of the presentation variable myFavoriteRegion.

    • variables - prefix that is required when you reference a
      presentation variable in a request.

    • variableName - a reference to an object available in the current evaluation context. For example: @{variables.myFavoriteRegion}.

    • format (optional) - a format mask (applied to {<variableName>}), dependent on the data type of the variable. For example: #,##0, MM/DD/YY hh:mm:ss, and so on.

    • value (optional) - a constant or variable reference indicating a value to be used if the variable referenced by the variableName is not populated (that is, is undefined).

In the topic entitled "To add or modify an Oracle BI narrative view", the syntax descriptions in the rows entitled "Prefix", "Narrative", and "Postfix", should read as follows:

You can use the @{variableName}[format]{<value>} syntax to include a variable.

In the topic entitled "To add or modify an Oracle BI static text view", in the table row entitled "Variables", the first sentence should read as follows:

The following HTML example includes variable expressions using the
@{variableName}[format]{<value>} syntax:

2.3.10 Enhancement to Display of Columns in Tables and Pivot Tables

This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

The display of columns in both tables and pivot tables has been enhanced in the following ways:

  • For columns of specified fixed widths: This release provides a better translation to PDF and a more faithful representation in the browser. You set specific fixed widths in the "Advanced Formatting Options" section of the Column Properties Style dialog.

  • For columns of unspecified widths: This release provides a more economical treatment of white space within cells of these columns. Font sizes within these columns do not change but because of this optimization, some tables appear slightly more compact than those displayed in previous versions.

2.3.11 Support For Bidirectional Language Charts

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

Oracle BI Enterprise Edition supports the bidirectional (BIDI) language Arabic, Hebrew, and Thai. However, due to a limitation in the current charting engine, Oracle BI Enterprise Edition does not properly support BIDI characters in charts. This issue is due to a limitation in the current charting engine.

As a workaround, Oracle recommends that customers use BI Publisher Chart, which is based on Oracle BI Beans technology. For more information about this issue and implementing the workaround, see the Oracle Business Intelligence New Features Guide Version 10.1.3.4.1.

2.3.12 Layout When Request is Downloaded to PowerPoint is Left-to-Right When the Oracle BI Server Locale is Arabic

This issue applies to Versions 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When the BI Server locale is Arabic and a request is downloaded to Microsoft PowerPoint, the layout in PowerPoint is seen in left-to-right orientation instead of right-to-left orientation.

2.3.13 Digit Glyph Displayed as Arabic Characters in PowerPoint When the Oracle BI Server Locale is Arabic

This issue applies to Versions 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When the BI Server locale is Arabic and a request is downloaded to Microsoft PowerPoint, digit glyphs are displayed in Arabic characters even though the PowerPoint file is opened in a non-Arabic windows environment (for example, English, Chinese, or Japanese WinXP).

2.3.14 Error When Opening PowerPoint 2003 (MHTML) Output from Oracle BI EE in PowerPoint 2010

This issue applies to Version 10.1.3.4.2.

When you export from Oracle BI EE to PowerPoint 2003, an MHTML file is generated that can be opened in PowerPoint 2003 and 2007. This MHTML file is supported in PowerPoint 2003 and 2007. PowerPoint 2010 no longer supports the MHTML format. Attempting to open the PowerPoint 2003 output from Oracle BI EE in PowerPoint 2010 causes an error.

To work around this issue, open the Oracle BI EE PowerPoint 2003 output in PowerPoint 2003 or 2007. You can save the content as PowerPoint 2007+, which you can then open in PowerPoint 2010.

2.3.15 Users Must Log In to Oracle BI Publisher from Answers

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When you attempt to access Oracle BI Publisher by selecting BI Publisher from the More Products menu in BI Answers, you are required to log in to Oracle BI Publisher even though you have previously logged into Answers. This issue has no workaround.

2.3.16 Error in Totals

This issue applies to Version 10.1.3.4.1 and 10.1.3.4.2.

An error in totals might occur if both of the following are true:

  • Report-based Totals is enabled, and

  • A measure uses the AGGREGATE aggregation rule instead of another aggregation rule such as SUM.

As a workaround, add the following setting anywhere within the WebConfig element in the instanceconfig.xml file: <ReportAggregateEnabled>true</ReportAggregateEnabled>. This change ensures that in the desired REPORT_AGGREGATE aggregation rule is used instead of the server AGGREGATE aggregation rule.

2.3.17 Issue with Totals and Value Suppression in Pivot Tables

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

You can specify value suppression using the Column Format tab of the Column Properties dialog. If you select the Repeat option in the Value Suppression area, then do not select the At the End option for totals of columns in pivot tables or unexpected results might occur. This issue has no workaround.

2.3.18 Font Size Does Not Change When Modifying Cascading Style Files in Linux

This issue applies to Version 10.1.3.4.1.

In deployments utilizing a J2EE container, editing cascading style files (for example, PortalBanner.css or Views.css) directly after they have been deployed into the container might yield inconsistent or no results. Changes to style can be made by editing the corresponding style files and then redeploying the EAR archive file.

In general, the correct way to make changes according to J2EE standards is as follows:

  1. Edit the file in /OracleBI/web/app/res/s_oracle10/b_mozilla_4.

  2. Unzip the analytics.ear file.

  3. Unzip the analytics.war file inside analytics.ear.

  4. Change the cascading style file here (do a search for the file/directory).

  5. Zip everything back up to re-create analytics.ear.

  6. Re-deploy analytics.ear to OC4J/IAS.

2.3.19 Performance Issue When Many Users Concurrently Export to PDF

This issue applies to Versions 10.1.3.4.0, 10.1.3.4.1, and 10.1.3.4.2.

If you have many users attempting to export reports to PDF concurrently, then you might notice that the performance of Presentation Services declines progressively. If as many as 100 users attempt to export to PDF at the same time, then browser sessions might hang and Presentation Services might halt. To work around this issue, limit the number of users who export to PDF concurrently.

2.4 Oracle Business Intelligence Interactive Dashboards

This section provides release notes for Oracle Business Intelligence Interactive Dashboards. It contains the following topics:

2.4.1 Portions of Dashboard Dialogs Obscured by Oracle BI Publisher Reports

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

In some cases a popup style of dialog shown within an Oracle BI Interactive Dashboard might appear "behind" BI Publisher reports, which also appear on that dashboard. This is due to the way that some browsers render layers for the iframe that contains that BI Publisher report. If a portion of a dialog, a multi-select prompt for example, is obscured by that BI Publisher report, then reposition the dialog relative to the dashboard page to access the critical controls.

2.4.2 Failure to Print a Dashboard Page with a Header or Footer

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, and 10.1.3.3.3. It is fixed in Version 10.1.3.4.

In a non-English locale (for example, Chinese, Japanese, Korean, Hebrew), an error occurs if you try to print a dashboard page that contains a header or a footer, and no PDF file is generated.

To work around this issue, do one of the following:

  • To correct this issue for an individual user, change the user's locale (that is, to a locale that is not Chinese, Japanese, Korean, or Hebrew).

  • To correct this issue for all users, update the userconfig.xml as follows:

    1. From Oracle BI home directory, go to <Oracle BI Home>/web/config/userconfig.xml.

    2. Replace all the string %SAWROOTDIR% with the actual value of that variable, which should be: <Oracle BI Home>/web.

      For example, if Oracle BI Enterprise Edition is installed under C:\OracleBI, then you should replace %SAWROOTDIR% with C:/OracleBI/web.

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

This issue applies to Versions 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

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.

2.4.4 Internationalization Support Issues in Oracle Briefing Book Reader

This issue applies to Versions 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

The following list contains known issues for the Oracle Business Intelligence Briefing Book Reader.

  1. The user interface for Oracle Business Intelligence Briefing Book Reader is not translated in the following languages:

    • Arabic

    • Greek

    • Hebrew

    • Hungarian

    • Norwegian

    • Polish

    • Romanian

    • Russian

    • Slovak

    • Thai

    • Turkish

  2. Oracle BI Briefing Book Reader displays content in a left-to-right orientation for languages that are bi-directional (for example, Arabic and Hebrew).

2.4.5 Join Catalog Group Link and Quit Link Display Erroneously in My Account Page

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

The Join Catalog Group (password required) link and Quit link display in the My Account page. These links are not functional and display in error.

2.4.6 Enhancements for Compressing Margins and Wrapping Column Text

This issue applies to Version 10.1.3.4.1 and Version 10.1.3.4.2.

Two enhancements have been added that can maximize the use of space on a dashboard page. The first, accessed from the PDF and Print Control dialog in the Dashboard Editor, compresses the margins of a dashboard page to the practical minimum. Select Maximum Width in the dialog to collapse the margins. If Maximum Width is not selected, then the selected pages render as usual.

The second enhancement provides a configuration option for a common column formatting .css workaround. The Line Break option allows for the wrapping of text within a column of a specified width. This option is available from the Style tab in the Column Properties dialog. Set the column width in the Additional Formatting Options section of the dialog. If a word width extends beyond the specified column width, then the column size is adjusted to match that width. This functionality does not crop text or force breaks within words.

2.5 Oracle Business Intelligence Delivers

This section provides release notes for Oracle Business Intelligence Delivers (Oracle BI Delivers). It contains the following topics:

2.5.1 iBot Headlines Cannot Contain Backslash Characters

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When you create a headline for an iBot, do not include the backslash (\) character in the headline. If the headline contains a backslash character, then you might see an irrecoverable Oracle BI Presentation Services error in the Job Manager.

This issue has no workaround.

2.5.2 iBot Recipient Gets ODBC Error Message

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

Under certain circumstances, if an iBot cannot connect to a database to run the query for the content, then the iBot recipient might receive an email that contains an ODBC error message.

This issue has no workaround.

2.5.3 Issue When Setting Values for iBot Prompts

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When you create an iBot on a Dashboard page that contains prompts, you cannot set values for the prompts before the iBot runs.

This issue has no workaround.

2.5.4 Issue with Conditional iBots, Unions, and Filters

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When you create a conditional iBot, be aware that it cannot be based on a request that contains both a union query and a filter. If you create such an iBot, then you see an error message in the scheduler log, but nowhere else. This issue has no workaround.

2.5.5 Issue with Non-Personalized Chained iBots

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

To create a non-personalized iBot that executes another iBot (known as chaining iBots), you must include yourself as a recipient of the non-personalized iBot by selecting the Me check box on the Recipients tab of the iBot Wizard. If you do not include yourself as a recipient of the non-personalized iBot, then Oracle BI Delivers does not execute the other iBot.

For example, if you want iBot A to execute iBot B by specifying iBot B execution as a post-action (using the Add Action option on the Advanced tab), then you must select the Me check box on the Recipients tab of the iBot Wizard for iBot A.

Note: To create a non-personalized iBot, you select the 'Not Personalized (use "Run As" user's data visibility)' option from the Data Visibility list on the General tab.

2.6 Oracle Business Intelligence Disconnected Analytics

This section provides release notes for Oracle Business Intelligence Disconnected Analytics (Oracle BI Disconnected Analytics). It contains the following topics:

2.6.1 Path Not Found Error Message on Mozilla Browser

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

If you access the Oracle BI Disconnected Analytics page using a Mozilla browser, then you might encounter a "Path Not Found" error when you select the Add/Edit Filter option. To work around this issue, use a browser other than a Mozilla one.

2.6.2 Incremental Preprocessed Synchronization Issues on Linux System

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

If Oracle BI Presentation Services runs on a Red Hat Linux computer, then you might encounter issues when performing an incremental preprocessed synchronization. This issue has no workaround.

2.6.3 Missing Languages in Oracle BI Disconnected Client

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

Oracle BI Disconnected Analytics does not support the following locales:

  • Greek (el)

  • Hebrew (iw)

  • Hungarian (hu)

  • Norwegian (no)

  • Romanian (ro)

  • Russian (ru)

  • Slovak (sk)

  • Turkish (tr)

The language folders for these eight languages are not installed out-of'-the-box. Users with any of these locales might encounter the following error:

Get sync error: SARRes.dll could not be loaded;

To work around this issue:

  1. On the computer where the Oracle BI Disconnected Analytics client is installed, locate the $<Disconnected_home>\OracleBI\Server\Locale folder.

  2. Copy and paste any of the existing language folders and rename it using the code for the required language (see the list of languages and codes above).

    For example, for the Turkish language, you might copy and paste the English language folder 'l_en' at the same location, and rename it as l_tr.

  3. Re-start the Oracle BI Disconnected Analytics Application Manager.

2.6.4 Using Windows Authentication and Single Sign-On with Disconnected Analytics

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

When you log in to Disconnected Analytics, you can use Windows Authentication, but no other single sign-on systems such as Oracle Single Sign-On. To configure for this authentication, you can follow the basic procedure for "Additional Configuration When SSO is Enabled for Oracle BI and BI Publisher" in the Oracle Business Intelligence Enterprise Edition Deployment Guide, with some exceptions. That procedure is written for Oracle BI EE and BI Publisher. Replace that procedure with the following one:

To enable SSO for Oracle BI Disconnected Analytics:

  1. On the same computer where BI Presentation Services Plug-in has been deployed, deploy another Presentation Services Plug-in using the file analytics.ear.

    Locate analytics.ear in the directory OracleBI_HOME/web/.

  2. Name the new Plug-in analyticsDisconnected.

    Make the same modifications to the web.XML file for this analyticsDisconnected servlet that were made to the web.XML file for the default "analytics" servlet.

  3. Make the following modification to the file mod_osso.conf to statically protect analyticsDisconnected.

    <Location /analyticsDisconnected>
       require valid-user
       AuthType Basic
       Allow from All
       Satisfy any
    </Location>
    

    mod_osso.conf is located in the directory Oracle_HOME/Apache/Apache/conf.

  4. Use one of two ways to synchronize a disconnected application: either using the command line or by clicking the Update Data button from within Disconnected Analytics. Use the URL for starting Disconnected Analytics (such as http://server/analyticsDisconnected) either at the command line or to start Disconnected Analytics in a browser.

2.7 Oracle Business Intelligence Scheduler

This section provides release notes for Oracle Business Intelligence Scheduler (Oracle BI Scheduler). It contains the following topics:

2.7.1 Setting Up the Java Scheduler Extensions in a Standalone Installation

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

In addition to the steps that are described in Oracle Business Intelligence Scheduler Guide, to use the Java Scheduler Extensions in a standalone configuration of Oracle Business Intelligence, you must configure the Javahost file, as described in this section.

If the Javahost file is not configured correctly, then you might encounter the following symptoms:

  • When an iBot runs, the iBot log file stops getting written to but the iBot is still in the running state in Job Manager and the NQScheduler.exe is continuously running at 50% CPU.

  • You cannot stop the Scheduler service using the Windows Services dialog, therefore you must stop the NQScheduler.exe file in Windows Task Manager.

To configure the Javahost file:

  1. On the Oracle Business Intelligence computer, edit the $ORACLE_HOME/OracleBI/web/javahost/config/config.xml file.

  2. Locate the Scheduler element and change the Enabled value to True and set the DefaultUserJarFilePath and DefaultTempFilePath values to the appropriate paths.

    For example, if the original config.xml code is:

    </Scheduler>

    <Enabled>False</Enabled>

    <DefaultUserJarFilePath>default</DefaultUserJarFilePath>

    <!-- <DefaultTempFilePath/> -->

    <!-- <DefaultPurgingPeriod/> -->

    </Scheduler>

    then you must change it to:

    </Scheduler>

    <Enabled>True</Enabled>

    <DefaultUserJarFilePath>$ORACLE_HOME/OracleBI/web/javahost/sample/scheduler</DefaultUserJarFilePath><DefaultUserJarFilePath>

    <DefaultTempFilePath><temporary file path><DefaultTempFilePath>

    <!-- <DefaultPurgingPeriod/> -->

    </Scheduler>

    Note:

    The <Enabled> attribute must be set to True for the scheduler RPC calls to be enabled.

    The <DefaultUserJarFilePath> attribute should be provided to specify the path for the Custom Java Program to pick up the jar files (for example, D:\temp\).

  3. Save the changes to the config.xml file.

  4. Restart the Scheduler and Javahost services.

2.7.2 Setting Up the Java Scheduler Extensions in a Clustered Installation

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

In addition to the steps that are described in Oracle Business Intelligence Enterprise Edition Deployment Guide, to use the Java Scheduler Extensions in a clustered configuration of Oracle Business Intelligence, you must configure the Javahost file and Job Manager settings, as described in this section.

If the Javahost file is not configured correctly, then you might encounter the following symptoms:

  • When an iBot runs, the iBot log file stops getting written to but the iBot is still in the running state in Job Manager and the NQScheduler.exe is continuously running at 50% CPU.

  • You cannot stop the Scheduler service using the Windows Services dialog, therefore you must stop the NQScheduler.exe file in Windows Task Manager.

To configure the Javahost file:

  1. For each BI Javahost in the cluster, start Job Manager by selecting Windows Start > Programs > Oracle Business Intelligence > Job Manager.

  2. Select File > Configuration Options.

  3. Display the Scheduler > Advanced tab.

  4. In the Scheduler > General tab, set the Scheduler Script Path and Default Script Path to network shares. For example:

    <DefaultScriptPath>\\<computer name or IP address>\Cluster\Scheduler\scripts\Common</DefaultScriptPath>

    <SchedulerScriptPath>\\<computer name or IP address>\Cluster\Scheduler\scripts\Scheduler</SchedulerScriptPath>

    Note: <computer name or IP address> is a shared file location and these paths can change depending on install.

  5. For each BI Javahost in the cluster, edit the $ORACLE_HOME/OracleBI/web/javahost/config/config.xml file.

  6. Locate the Scheduler element and change the Enabled value to True and set the DefaultUserJarFilePath and DefaultTempFilePath values to the appropriate paths.

    For example, if the original config.xml code is:

    </Scheduler>

    <Enabled>False</Enabled>

    <DefaultUserJarFilePath>default</DefaultUserJarFilePath>

    <!-- <DefaultTempFilePath/> -->

    <!-- <DefaultPurgingPeriod/> -->

    </Scheduler>

    you must change it to:

    <Scheduler>

    <Enabled>True</Enabled>

    <DefaultUserJarFilePath>\\<computer name or IP address>\Cluster\Scheduler\scripts\Common\javahost\sample\scheduler</DefaultUserJarFilePath>

    <DefaultTempFilePath>\\<computer name or IP address OR local area>\Cluster\Scheduler\temp</DefaultTempFilePath>

    </Scheduler>

    Note:

    The <Enabled> attribute must be set to True for the scheduler RPC calls to be enabled.

    The <DefaultUserJarFilePath> attribute should be provided to specify the path for the Custom Java Program to pick up the jar files. The temporary file path specified in the <DefaultTempFilePath> tag does not need to be a shared file area. It can be set to a local area, for example, D:\temp\.

  7. Save the changes to the config.xml file.

  8. Restart the Scheduler and Javahost services.

2.8 Oracle Business Intelligence Administration Tool

This section provides release notes for Oracle Business Intelligence Administration Tool (Oracle BI Administration Tool). It contains the following topics:

2.8.1 Specifying XML Data Sources

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

To use an XML file as a physical data source in Oracle BI Administration Tool, the file name in the URL that you specify must have an XML suffix. For example, if you have a data source located in D:\datasources\xml\Categories.xml, then the value that you specify in the URL field on the XML tab of the Physical Table - <name of data source> dialog must be D:\datasources\xml\Categories.xml. In addition, you must select XML as the value in the Database field on the General tab of the Database dialog.

2.8.2 New Connection Scripts Functionality in Connection Pool Object

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

Oracle BI Enterprise Edition 10.1.3.3 has expanded support for the "Execute On Connect" setting in the connection pool to include support for Lightweight session for Oracle 11g Fusion applications. A new tab called "Connection Scripts" has been introduced within the Connection Pool object and has the following options:

  • Execute on connect - Enhancement to the previous ability, it is now possible to execute multiple scripts (either a SQL or a DB Procedure call) on the database after making a connection.

  • Execute before query - New feature to execute a SQL or DB Procedure before each query.

  • Execute after query - New feature to execute a SQL or DB Procedure after each query.

  • Execute on disconnect - New feature to execute a SQL or DB Procedure before disconnecting from the database.

Note:

The administrator is expected to handle the exception arising out of these scripts using the proper exception handling mechanism within the script. Un-handled exceptions are exposed to the user executing the query and they stop the query execution.

2.8.3 Unable to Import UTF-8 Table/Column Names Through OCI

This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

If you import Oracle Database objects through OCI 10g, then table and column names in utf-8 format are not imported correctly. For example, if a column is named with Chinese characters, then the name becomes garbled when imported through OCI on a non-Chinese environment such as English. To work around this issue, use ODBC to import such objects into the repository.

2.8.4 Issues with Essbase

This section describes issues that you might encounter when using the BI Server with Essbase databases:

2.8.4.1 Inconsistent Essbase Query Results

This issue applies to Versions 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.

Inconsistent query results can occur if a physical database or catalog folder of type Essbase is dragged from the Physical layer of the repository to the Business Model layer to create a single Business Model.

To work around this issue, take one of the following actions:

  • If the Administrator wants to create a separate Business Model for each Cube, then each cube should be dragged individually to the Business Model layer.

  • If a single Business Model is desired for each physical database or physical catalog, then the database or catalog can be dragged to the Business Model layer. However, by doing so, any dimensions with the same name are treated as conforming dimensions and a single Logical dimension is created for all such dimensions. The Logical dimension is sourced from all such dimensions with the same name and hence might lead to potential query issues.

    It is the responsibility of the Administrator to correct the mappings or to create individual logical dimensions for dimensions that are not conforming.

2.8.4.2 Resolving an Issue with Custom Groups for Essbase Databases

This issue applies to Versions 10.1.3.4.1 and 10.1.3.4.2.

You might encounter problems when using custom groups in Oracle BI EE against Essbase databases. You can resolve these problems by setting the OBIS_Essbase_CustomGroup_Generation environment variable, as shown in the following example:

set OBIS_Essbase_CustomGroup_Generation=1

The CustomGroup syntax generation provides benefits in correctness (such as rolling up non-linear measures) and performance (such as better utilization of the slicer). You can set the OBIS_Essbase_CustomGroup_Generation variable to the values that are described in the following list. A value of 0 allows you to completely remove the use of the CustomGroup syntax. Values of 1 and 2 provide increasing use of the slicer with the CustomGroup syntax. However, custom group generation can negatively impact query performance in certain circumstances with a setting of 2.

  • 0 = There is a single member per dimension on the slicer. No custom group calculated member is used on the slicer.

  • 1 = There is a single member per dimension on the slicer or a calculated member on a slicer from a multi-member enumeration where possible. For example, you can define a calculated member called MyTerritory as [SF]+[LA].

    The BI Server first tries the optimization that is applied by the value of 0 and if that is not possible, then it tries to use the optimization of 1.

  • 2 = (Default) There is a single member per dimension on the slicer or a calculated member on a slicer from a multi-member enumeration where possible or from SUM (named set). For example, you can define a calculated member called MyTerritory as SUM(MySetOfCities).

    The BI Server first tries the optimization that is applied by the value of 0 and if that is not possible, then it tries to use the optimization of 1. If that is not possible, then it tries to use the optimization of 2.

This environment variable is specific to Release 10g. For Release 11g, this variable is replaced with an entry in the database features table for Essbase.

2.8.4.3 Error Message on Exceeding Tuples

This issue applies to Versions 10.1.3.4.1 and 10.1.3.4.2.

You might create an analysis in Oracle BI EE against an Essbase database and see the following error message:

SET IS TOO LARGE TO BE PROCESSED.SET SIZE EXCEEDS 2^32 tuples

You can work around this problem if you first apply the Essbase patch for Bug 8278841. Then you can turn on the workaround by setting an environment variable with a name in the following format:

OBIS_Essbase_NonEmptyTuples_Generation_Database.Catalog.CubeTable=1

In the variable, Database, Catalog and CubeTable refer to the names (external names when applicable) of those objects in the physical layer of the repository.

The following are two examples of setting this variable:

set OBIS_Essbase_NonEmptyTuples_Generation_FoodMart.FoodMart.salesdb=1

set OBIS_Essbase_NonEmptyTuples_Generation_130.35.50.106.ASOsamp.Sample=1

This environment variable is specific to Release 10g. For Release 11g, this variable is replaced with an entry in the database features table for Essbase.

2.8.4.4 Using the LIKE Function for Essbase Databases

This issue applies to Versions 10.1.3.4.1 and 10.1.3.4.2.

By default, the LIKE function is not activated in the Essbase Features table in the repository. If an Essbase instance supports the InStr function, then turn on the LIKE function for this instance in the repository.