Oracle® Essbase Studio

Readme

Release 11.1.2.4.000


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

Updated: June 2016

Authors: EPM Information Development Team

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

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

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

U.S. GOVERNMENT END USERS:

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

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

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

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. Microsoft Windows, PowerPoint, Word, Excel, Access, Office, Outlook, Visual Studio, Visual Basic, Internet Explorer, Active Directory, and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

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


Table of Contents:

Purpose

New Features in This Release

Installation Information

Supported Platforms

Supported Languages

Supported Paths to This Release

Defects Fixed in this Release

Known Issues

Tips and Troubleshooting

Documentation Updates

Purpose

This document includes important, late-breaking information about this release of Oracle Essbase Studio. Review this Readme thoroughly before installing Oracle Enterprise Performance Management System.

New Features in This Release

See the “Oracle Essbase Studio New Features Guide.” For new features relating to installation, architecture, and deployment changes in this release, see “New Features in this Release” in the Oracle Enterprise Performance Management System Readme.

For new features relating to installation, architecture, and deployment changes in this release, see “New Features in this Release” in the Oracle Enterprise Performance Management System Readme.

https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1092114.1

Installation Information

Late-breaking information about the installation of EPM System products is provided in the Oracle Enterprise Performance Management System Installation and Configuration Readme. Review this information thoroughly before installing EPM System products.

Oracle Smart View for Office is no longer installed with the Oracle Hyperion Enterprise Performance Management System Installer. To download and install the latest release of Smart View, go to http://www.oracle.com/technetwork/middleware/smart-view-for-office/overview/index.html.

Supported Platforms

Information about system requirements and supported platforms for EPM System products is available in spreadsheet format in the Oracle Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on Oracle Technology Network (OTN):

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

Supported Languages

Information about supported languages for EPM System products is available in spreadsheet format on the Translation Support tab in the Oracle Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on OTN:

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

Supported Paths to This Release

You can upgrade to EPM System Release 11.1.2.4 from the following releases:

Note: For upgrading instructions, see the Oracle Enterprise Performance Management System Installation and Configuration Guide, “Upgrading EPM System Products.

Table 1. Supported Paths to this Release

Upgrade Path From Release ...To Release 11.1.2.4

11.1.2.x

Apply the maintenance release to move to Release 11.1.2.4.

Note:

For Oracle Hyperion Financial Close Management, applying the maintenance release is supported only from Release 11.1.2.2 or 11.1.2.3.

For Oracle Hyperion Financial Management, applying the maintenance release is supported only from Release 11.1.2.1, 11.1.2.2, or 11.1.2.3.

11.1.1.4.x

Upgrade to Release 11.1.2.3 and then apply the maintenance release to move to Release 11.1.2.4.

Release 11.1.1.0.x to 11.1.1.3.x

Apply the maintenance release to move to Release 11.1.1.4, upgrade to Release 11.1.2.3, and then apply the maintenance release to move to Release 11.1.2.4.

Caution!

Oracle recommends using the same version of all Oracle Essbase portfolio products (Essbase, Oracle Essbase Administration Services, Oracle Hyperion Provider Services, and Essbase Studio) and components (server, client, runtime client, API, and JAPI).

Defects Fixed in this Release

This section includes defects fixed in Release 11.1.2.4.000. To review the list of defects fixed between earlier releases, use the Defects Fixed Finder. This tool enables you to identify the products you own and your current implementation release. With a single click, the tool quickly produces a customized report of fixed-defect descriptions with their associated platforms and patch numbers. This tool is available here:

https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1292603.1

  • 18084958 -- In the Connection Wizard, if you type the connection properties for a DB2 data source containing Materialized Query Tables (MQTables), and click next, the MQTables are not displayed.

    Note:

    This fix requires the Datadirect JDBC drivers to be updated to version 5.1. Please contact Oracle Support for assistance.

  • 17596834 -- When you select View Sample Data, no preview data is displayed if null values are present.

  • 13356961 -- The “show full path for dimension elements” option is not displayed by default.

  • 17263513 --When trying to set Independent Dimension Setting in the Varying Attribute dialog box, the OK button is grayed out even though the Type is Individual and From is filled out.

  • 19630395 -- Creating a hierarchy with a dimension named “currency” returns the following error message: “Hierarchy Error. Currency does not conform to Essbase naming standards. Enter a valid Essbase name.

  • 20243329 -- Essbase Studio incorrectly gives validation error for an aggregate storage application model when the Accounts dimension member is set to Label only and consolidation for its children is set to ignore.

  • 19850301 -- Drill-through using user-defined SQL with template variables becomes invalid after import-export.

Known Issues

The following are the noteworthy known issues of this release.

  • 21283286 -- When Essbase Studio is configured for using the TPT API and you are performing a cube deployment in non-streaming mode from a Teradata data source, dimension builds succeed, but data loads may fail with an error similar to this one:

    Failed to deploy Essbase cube. 
    Caused by: Failed to load data into database: db. 
    Caused by: Cannot get async process state. Essbase Error(1042017): Network 
    error: Timed out before receiving all data 
    

    Workaround: Configure an ODBC DSN with TPT API for Essbase Server and specify this driver as a named ODBC DSN in the first step of the Cube Deployment Wizard.

    The steps to set up a DSN for Essbase Server using TPT API are described in the Oracle Essbase SQL Interface Guide, in the topic, "Setting Up the Environment for Using Teradata Parallel Transporter."

    Example:

    If the Teradata server is named tera2db, you can set up a DSN named $TELAPI$tera2db and specify this in the Cube Deployment Wizard.

  • 12815260 -- When dimension elements have sort orders applied to them and, in the Essbase model, the members based on those dimension elements have prefix or suffix transformations applied to them, these members will not sort correctly after the model is deployed.

    Workaround: If you require prefix or suffix transformations on a member that has sort orders applied to the underlying dimension element, you can edit the key binding expression for the element to add the transformation. Do not use the transformation functionality in the Essbase model in this case.

    For example, using the TBC database, a Product dimension is built using the following hierarchy:

    FAMILY
        |_ SKU

    Before applying the transformation to the key binding expression, the dimension element properties are set as follows:

    • Dimension element FAMILY—with Key and Caption Bindings set to PRODUCTDIM.FAMILY, and Sort Column set to PRODUCTDIM.FAMILY

    • Dimension element SKU—with Key and Caption Bindings set to PRODUCTDIM.SKU, and Sort Column set to PRODUCTDIM.SKU

    Now edit the key binding expression using concatenation to add a prefix or suffix.

    For example, to add SKU from the PRODUCTDIM table as a suffix to the FAMILY dimension element, the additional text in bold below is added to the key binding expression:

    connection : \'TBC-oracle'::'TBC.PRODUCTDIM'.'FAMILY' || "_" || connection : \'TBC-oracle'::'TBC.PRODUCTDIM'.'SKU'
  • 16921268 -- Unable to shutdown Essbase Studio Server if installed on a custom port. The workaround is to modify stopServer.sh by adding Dserver.url=Essbase Studio Server machine:custom port number. For example, modify this entry:

    "${JAVA_HOME}/bin/java" -Xms128m -Xmx768m $JAVA_OPTIONS -cp 
    "${EPM_ORACLE_HOME}/products/Essbase/EssbaseStudio/Server/server.jar" 
    com.hyperion.cp.api.ShutdownRequest 

    To this:

    "${JAVA_HOME}/bin/java" -Xms128m -Xmx768m -Dserver.url=Essbase Studio Server machine:custom port number $JAVA_OPTIONS -cp 
    "${EPM_ORACLE_HOME}/products/Essbase/EssbaseStudio/Server/server.jar" 
    com.hyperion.cp.api.ShutdownRequest 
  • 16298982 -- When Essbase is running on Japanese Linux, loading Japanese characters to the outline in a native Japanese application does not work in non-streaming mode. Workaround: Use streaming mode instead.

  • 16423924--The Week element is missing from the Create date elements dialog box. The available options are Year, Quarter, Month, and Day of week. Workaround: Create a dimension element manually, using this syntax in the Caption Binding and Key Binding fields. Be sure to select Advanced for Key Binding.

    To represent the week of the month:

    'WM'( connection : \'tbc'::'TBC.SALES'.'TRANSDATE' ) . toString 
    'WM'( connection : \'tbc'::'TBC.SALES'.'TRANSDATE' )
    

    To represent the week of the year:

    'WY'( connection : \'tbc'::'TBC.SALES'.'TRANSDATE' ) . toString
    'WY'( connection : \'tbc'::'TBC.SALES'.'TRANSDATE' ) 

    For more information, see Creating an Expression on Which to Base a Dimension Element in the Oracle Essbase Studio User's Guide.

  • 16435266 -- In cases with parent/child columns, creating more than one self join using a single text file fails.

  • 16517700 -- If server.query.skipValidation=true is set in server.properties, validation for User-defined SQL in Drill-through reports does not work correctly. Validation of an invalid user-defined SQL statement incorrectly returns "User-defined SQL is valid."

  • 16522882 -- After upgrading from 11.1.2.2.000 to 11.1.2.3.000, adding a database source or issuing a reinit command may result in a JDBC driver error message. Workaround: Restart Essbase Studio Server if you get the JDBC Driver error message.

  • 16292007 -- When Oracle RAC is the data source, cube deployment in non-streaming mode with ODBC connection string is not supported.

  • 14625545 -- When dimension elements are created using delayed key bindings, and those elements are then used in an Essbase model that is enabled for duplicate member name support, cube deployment fails. Workaround: In the dimension elements, use the Advanced option and edit the Key Binding manually. For example, using the TBC database, for a dimension element created from the UDAMKTSIZE column, the Delayed key binding that automatically appears in the hierarchy is:

    class : \'tbc'\'REGION'\'REGION'.'caption' || "_" || class : \'tbc'\'MARKET'\'UDAMKTSIZE'.'caption' 
     
    Instead, edit the key binding in the dimension element by using the Advanced option as follows:
     
    connection : \'tbc'::'TBC.REGION'.'REGION'||connection : \'tbc'::'TBC.MARKET'.'UDAMKTSIZE'
  • N/A -- Integration Services catalog migration is not supported on 64-bit UNIX platforms or on the Windows 2008 64-bit platform.

  • N/A -- Transformation rules defined in the Essbase model will not be used in query generation for drill-through operations.

    Workaround: You may edit the expressions for the dimension element's caption binding to transform members.

  • N/A -- If Oracle is your catalog database: Essbase Studio no longer issues the ALTER SYSTEM command when connecting to the catalog database. For increased performance, add the ALTER SYSTEM statement to the Oracle database user's privileges for the Essbase Studio catalog user.

    Following are the recommended settings:

    ALTER SYSTEM SET open_cursors=300 SCOPE=MEMORY

    The catalog user is specified in the Oracle Hyperion Shared Services Registry during configuration and should have the privileges necessary to execute the ALTER SYSTEM statement.

  • 6576813 -- The JISX0213 Japanese character set, which replaces the JISX0208 and JISX0212 Japanese character sets, is supported on Windows Vista. The Essbase family of products does not support the JISX0213 Japanese character set.

  • 7138321 -- You cannot deploy an XOLAP-enabled Essbase model that is based on an Oracle Business Intelligence Enterprise Edition data source.

  • 7366645 -- When using Smart View or Oracle Essbase Spreadsheet Add-in to query cubes built in Essbase Studio, if the intersection for a drill-through cell is represented by both a base member and one or more associated attribute members, you cannot perform drill-through on that cell.

    Specifically, drill-through will not work on an intersection (cell) that is represented by members of a base dimension and members of attribute dimensions.

    When specifying intersections for a drill-through report in Essbase Studio, do not specify both the base and attribute hierarchies from a multichain hierarchy. Select only one of the hierarchies for drill-through.

    If you require drill-through from an intersection containing a base member and attribute members, you must build the cube using Oracle Essbase Integration Services.

  • 8661977 -- When deploying a cube for the first time, and the cube contains text or date measures, the data is loaded correctly. Upon subsequent deployments of the cube, selecting the "Load data" option along with either the "Add to existing data" or "Subtract from existing data" option, results in incorrect data.

    Workaround: Use custom data load SQL to selectively load data on numeric measures only, omitting any text or date measures.

  • 8897922 -- When migrating an OLAP metaoutline from Integration Services to Essbase Studio, members in a hierarchy may not be sorted properly in the deployed Essbase cube if both transformation and sorting rules are defined on the original Oracle Essbase Integration Services member set. In Essbase Studio, performing transformation in Essbase Model Properties does not resolve the issue.

    Workaround: Perform transformation in the Dimension Element Properties dialog box by editing the key binding expression of the dimension elements.

  • 8908738, 7127257 -- Microsoft Windows authentication is not supported for data source connections to Microsoft SQL Server.

  • 9315569 -- The labeling rules listed in the Editing Labeling Rules dialog box were not translated and appear in English for all languages.

    The Editing Labeling Rules dialog box is accessed from the Time Depth area of the Calendar Hierarchy dialog box, as described in "Defining Time Depth" in the Oracle Essbase Studio User's Guide.

  • 9325297 -- Varying attributes do not support NULL values in the "FROM" or "TO" columns of the "history" table. When working with varying attributes, if the history table contains rows with a NULL value in either the FROM or TO columns, then the attribute values from these rows are not built into an attribute dimension.

    Workaround: Ensure that there are non-NULL values in the FROM and TO columns of the history table. For more information on history tables, see “Setting Up a History Table for Varying Attributes” in the Oracle Essbase Studio User's Guide.

  • 9326364 -- If two independent dimensions have the same leaf member name for one varying attribute, deployment fails with the error, "Duplicate name of the field in the query."

    For example, suppose there is a varying attribute dimension, "VARYPER," and two independent dimensions, "Period" and "Year." If the leaf member name is the same for both "Period" and "Year" in the Essbase Model Properties, Independent Dimension Binding dialog box, the deployment will fail.

    Workaround: Rename the column for the physical relational table that will be used for the leaf member name. If that is not possible, you can create a user-defined table with the different column name and build the second independent dimension based on a column in the user-defined table.

  • 9364712 -- When deploying cubes in nonstreaming mode (the Enable streaming mode for cube deployment check box is cleared), deployment fails when the Essbase model is based on a Unicode data source.

    Workarounds:

    • Use streaming mode: In the Cube Deployment Wizard, ensure that the Enable streaming mode for cube deployment check box is selected.

    • Use nonstreaming mode with the data source enabled for N-CHAR support:

      First, create a DSN and enable the N-CHAR support option as follows:

      • On Windows, use the ODBC Data Source Administrator to create a DSN with the Enable N-CHAR Support option selected. This option is found on the Advanced tab of the ODBC driver setup dialog box.

      • On UNIX or Linux, edit the odbc.ini file to create a new DSN, and set the EnableNcharSupport value as follows:

        EnableNcharSupport=1

      Then, the Cube Deployment Wizard, complete these steps:

      1. In the Essbase Server connection options page, select the ODBC (Enter ODBC DSN Name) option and provide the DSN you created.

      2. In the Cube deployment options page, ensure that the Enable streaming mode for cube deployment check box is cleared.

      See the Cube Deployment chapter in the Oracle Essbase Studio User's Guide for information on using the Enable streaming mode for cube deployment check box.

  • 9433391 -- Deploying From Text File Data Sources

    • Cube deployment from text file data sources is always done in nonstreaming mode.

      Essbase Studio Server uses the nonstreaming cube building method automatically for text file data sources; you will not be asked about or notified of this internal load method.

    • Cube deployment progress statistics are not supported on text file data sources.

  • 9477466 -- In Smart View, when performing drill-through from an Essbase Studio-sourced cube to Oracle Hyperion Financial Data Quality Management, if the EPM System Single Sign-On token expires before the sessions of all products involved expire (Workspace, Oracle Hyperion Provider Services, Essbase, Essbase Studio, Oracle Hyperion Financial Data Quality Management), the following message is displayed: “Error: An error occurred logging on to the system using single sign-on. Please contact your administrator. Error: 2067 - You do not have access to the application!

    Workaround: Log in again to Workspace from Oracle Smart View for Office client.

  • 9492526, 9502269 -- On Windows, when Essbase is started using OPMN, cube deployment fails for cubes built from Oracle BI EE data sources if the option ODBC (Essbase dynamically creates ODBC connection string) is selected in the Cube Deployment Wizard.

    Workarounds: For successful deployment, use one of the following workarounds:

    • In the Cube Deployment Wizard, specify an ODBC DSN for the OBI data source connection. See “Providing Connection Information for Cube Deployment” in the Oracle Essbase Studio User's Guide for more information.

    • Check the “Enable streaming mode for cube deployment” option in the Cube Deployment Wizard to start Essbase Studio Server in streaming mode, then perform the deployment.

  • 9561925 -- Solaris only: Your machine likely has a network configuration problem if Essbase Studio Server fails to start, and either of the following messages appears in the server log file:

    • Cannot register server in catalog.

    • Network error prevented server registration check.

    Workaround: Manually add a single, empty row to the cp_server_key table in the Essbase Studio catalog database.

  • 11663358 -- Cubes containing calendar hierarchies with day attributes do not correctly build during cube deployment as most of the day attributes are missing. (Related to bug 11696797.)

  • 11696797 -- The day attributes of a calendar hierarchy are not all listed under the hierarchy in the Essbase Model Properties dialog. (Related to bug 11663358.)

  • 13810033 -- Essbase Studio does not support IPv6 protocol on Microsoft Windows platforms. Essbase Studio supports IPv6 protocol only on UNIX platforms.

  • 14155099, 14462547 -- Netezza Data Source for Essbase Studio. Unable to connect to a Netezza data source using non-streaming mode in Essbase Studio.

    Workaround: In non-streaming mode, the connection to a data source is made by Essbase, not Essbase Studio. Data source drivers are specified in the Essbase configuration file (essbase.cfg). By default, some data source drivers are disabled by the presence of a semicolon (;) comment indicator at the beginning of the data source entry. In the following example, the Netezza driver is disabled.

    BPM_Oracle_DriverDescriptor "DataDirect 6.1 Oracle Wire Protocol"
    BPM_DB2_DriverDescriptor "DataDirect 6.1 DB2 Wire Protocol"
    BPM_SQLServer_DriverDescriptor "DataDirect 6.1 SQL Server Native Wire Protocol"
    ;BPM_SQLServer_DriverDescriptor "SQL Server"
    ;BPM_Netezza_DriverDescriptor "NetezzaSQL"
    BPM_Teradata_DriverDescriptor "Teradata"
    ;BPM_ORACLEBI_DriverDescriptor "Oracle BI Server 11g_OHXXXX"
    ;BPM_ORACLEBI_DriverDescriptor "Oracle BI Server"
    BPM_MySQL_DriverDescriptor "DataDirect 6.1 MySQL Wire Protocol
    

    Edit essbase.cfg to make sure that the data sources you are using are listed and are not disabled by the semicolon comment indicator.

    Note:

    The Netezza ODBC driver must be installed on the machine on which Essbase Server runs.

Tips and Troubleshooting

Limitations and Guidelines

The Oracle Essbase Studio User's Guide (PDF and HTML format) contains an appendix entitled “Essbase Studio Limitations and Guidelines,” which describes various limitations you may encounter while working with Essbase Studio.

Also, refer to the Working with the Virtual Memory Setting section of this document.

Selecting a Language in the Essbase Studio Client Installer

The Essbase Studio client installer allows you to select a language, however if the system locale does not match the selected language, the UI in Essbase Studio matches language of the system locale and not the language selected in the installer. For example, if you launch the installer and select the Japanese language on a system with an English locale, the installer displays in Japanese, and Essbase Studio is installed successfully. When you launch Essbase Studio, the UI displays in English.

Verifying Catalog URL Property Syntax

If Essbase Studio Server fails to start, check the catalog.url property in theShared Services Registry file to verify that the syntax is correct.

If the syntax is incorrect, Essbase Studio Server will not start. If the syntax is incorrect, update the catalog.url property in the server.properties file or in Shared Services Registry to correct the problem. Then restart Essbase Studio Server.

Notes:

  • See the topic, “catalog.url” in the Oracle Essbase Studio User's Guide for more information and examples.

  • Settings in server.properties override settings in Shared Services Registry.

  • To view or modify settings in the Oracle Hyperion Shared Services Registry, use the epmsys_registry utility, described in the Oracle Enterprise Performance Management System Deployment Options Guide.

Running the "reinit" Command if Using "Apply Maintenance Release" Option

If you used the “Apply Maintenance Release” option to move from Essbase Studio Release 11.1.2, 11.1.2.1, 11.1.2.2 or 11.1.2.3 to this release, you must update the Essbase Studio catalog after installation and configuration. You update the catalog by issuing the reinit command in the Essbase Studio command line client. For instructions, see the Oracle Enterprise Performance Management System Installation and Configuration Guide, “Updating the Essbase Studio Catalog.

About Essbase Studio Server-Generated MaxL for XOLAP Cubes

(11058371, 11068896)

You can generate a MaxL deploy statement by choosing options in the Cube Deployment Wizard and then saving your selections as a MaxL script.

When redeploying XOLAP cubes, if you then edit the Essbase Studio Server-generated MaxL to remove or change any deployment settings, data may not be consistent.

To redeploy an XOLAP cube, do not change the deployment settings by editing an Essbase Studio Server-generated MaxL script. Instead, Oracle recommends that you launch the Cube Deployment Wizard, make your required selections, then save those selections in a new MaxL script.

Using the MaxL Import Dimensions Statement with Essbase Studio Rules Files

(7216055, 9034403)

You can use the MaxL Deploy statement to load members and data into Essbase from a rules file that was created in Essbase Studio. The Deploy statement provides you with the simplest way to accomplish this task.

You may, however, choose to use the MaxL Import Dimensions statement to load members from an Essbase Studio-generated rules file. If you choose to use the Import Dimensions statement to build an outline, note that a problem exists when building an Accounts dimension either from the fact table or from a hierarchy containing only user-defined members. When this is the case, use the following workaround to successfully load the data.

Workaround: Prepare an empty dummy text file that can be called in the MaxL Import Dimensions statement. For example:

import database 'tbc.MaxL1' dimension from local text data_file 'C:\dummy.txt' using server rules_file 'Account' on error append to 'C:\Hyperion\textUn1.log';

Working with the Virtual Memory Setting

(9460997, 9480016, 10415849)

On the machine where Essbase Studio Console is running, you may increase the virtual memory setting within the limits specified by your operating system.

For example, on Windows 32-bit platforms, the maximum virtual memory setting is 2048 MB.

Instructions on virtual memory configuration are in “Configuring Virtual Memory” in the Oracle Essbase Studio User's Guide.

Deploying Cubes Based on Oracle BI EE Data Sources

(9492623, 10391499)

Table 2 summarizes how Essbase Studio Server, running in streaming or nonstreaming mode, integrates with Oracle BI EE Server, assuming that Essbase is managed by OPMN, and whether streaming or nonstreaming mode is supported for a particular operating system. Also, if further configuration must be completed, there is a reference to the appropriate substep in step 2; for example, step 2.a or step 2.b.

Table 2. Essbase Studio Server Integration with Oracle BI EE Server

Oracle BI EE Version

Nonstreaming Mode server.essbase.streamingCubeBuilding=false

Streaming Mode server.essbase.streamingCubeBuilding=true

11.1.1.5 or later

Windows: Supported

Modify the essbase.cfg file. See step 2.b.

UNIX and Linux: Not Supported

Oracle BI EE ODBC driver has a conflict on common environment variables, such as ORACLE_HOME.

Windows: Supported

UNIX and Linux: Supported

See step 2.c.

10.1.3.4 or later

Windows: Supported

Requires the Oracle BI EE 11.1.1.5 ODBC driver installed on same machine as Essbase Server. See step 2.a.

UNIX and Linux: Supported

Manually modify opmn.xml to set the correct environment variables, which are different from 11.1.1.3. See step 2.d.

Windows: Supported

UNIX and Linux: Supported

10.1.3.3. or earlier

Windows: Not Supported

UNIX and Linux: Not Supported

Windows: Supported

See step 2.e.

UNIX and Linux: Supported

See step 2.e.

To complete any further configuration required by Table 2:

  1. On Windows, in nonstreaming mode (in Essbase Studio Console, in the Essbase Server connection options dialog of the Cube Deployment Wizard, select “Enable streaming mode for cube deployment.”) Essbase Studio can deploy cubes from Oracle BI EE data sources version 10.1.3.4.1 or later, as long as the Oracle BI EE ODBC driver is version 11.1.1.5 and resides on the same machine as the Essbase Server.

  2. Complete the steps below, as indicated in the preceding table, depending on your operating system, Oracle BI EE version, and whether you want to run Essbase Studio Server in streaming or nonstreaming mode:

    1. Uncomment the ;BPM_ORACLEBI_DriverDescriptor "Oracle BI Server 11g_OHXXXX" line by removing the semicolon:

      BPM_ORACLEBI_DriverDescriptor "Oracle BI Server 11g_OHXXXX"
    2. Change 11g_OHXXXX to the same instance number as appears in the Drivers tab of the ODBC Data Source Administrator; for example:

      BPM_ORACLEBI_DriverDescriptor "Oracle BI Server 11g_OH449923612"
    3. On UNIX and Linux, if you are deploying cubes based on Oracle BI EE version 11.1.1.5 or higher, you must use streaming mode.

    4. UNIX and Linux, in nonstreaming mode, when deploying cubes based on Oracle BI EE version 10.1.3.4 data sources, you must add the following environment variables to the opmn.xml file:

      <variable append="true" id="LD_LIBRARY_PATH"
         value="/.../prod1/OracleBI/server/Bin"/>true
                  id="LD_LIBRARY_PATH"
         value="/.../prod1/OracleBI/web/Bin"/>
      <variable id="SATEMPDIR" value="/.../prod1/OracleBIData/tmp"/>
      <variable id="SAROOTDIR" value="/.../prod1/OracleBI"/>
      <variable id="SA_ROOTDIR" value="/.../prod1/OracleBI"/>
      variable id="SADATADIR" value="/.../prod1/OracleBIData"/

      For more information, see “(UNIX) Configuring the Environment for Essbase and Oracle BI EE Integration” in the Oracle Enterprise Performance Management System Installation and Configuration Guide.

    5. On Windows, UNIX, and Linux, cubes may be deployed based on Oracle BI EE version 10.1.3.3 only if streaming mode is enabled.

  3. ODBC driver configuration for Oracle Business Intelligence Enterprise Edition running on UNIX is covered in the topic, “(UNIX) Configuring the Environment for Essbase and Oracle BI EE Integration,” in the Oracle Enterprise Performance Management System Installation and Configuration Guide.

Inconsistent Object in Catalog” Error During Upgrade

(11073948)

When upgrading from Release 11.1.1.3, during configuration with Oracle Hyperion Enterprise Performance Management System Configurator, if the Configure Database task fails for Essbase Studio, review the upgrade log file for a message related to inconsistent object in the catalog, similar to this:

Caused by: com.hyperion.cp.cplutil.scripts.export_import.exceptions.ExportException: Inconsistent object in catalog. Please check the object form : \'Drill Through Reports'\'Supplier', object id : @44#0#101#0@.

Important: Be sure that your 11.1.1.3 release environment is running and available until the Essbase Studio catalog is successfully upgraded.

This error occurs when you rename data source connections which have drill-through reports dependent on them.

If there is an error related to inconsistent objects in drill-through reports, then one or more drill-through reports are invalid and must be corrected before you can upgrade Essbase Studio. Fix inconsistent drill-through reports (drill-through reports that depend on data source connections that have been renamed) by taking any of these actions:

  • In the 11.1.1.3 environment, rename the data source connections back to their original names.

  • Update the invalid drill-through reports by providing new column values and, optionally, filters, in the Report Contents tab of the drill-through report editor.

  • Delete the invalid drill-through reports from the 11.1.1.3 environment and then recreate them in the upgraded Essbase Studio environment, if needed.

Then, restart Oracle Hyperion Enterprise Performance Management System Configurator and rerun the Configure Database task.

Starting Essbase Studio Server with Windows Authentication

(13562254)

When Essbase Studio Server is installed and configured as a Windows service, you cannot start it as a service using Windows authentication. In order configure Essbase Studio Server to take advantage of Windows authentication, you must do the following:

  1. If already running, stop the Essbase Studio Server service.

  2. Add the catalog.username property to the server.properties file as follows:

    catalog.username=

    Do not add any user name or other text to the catalog.username property.

  3. Start Essbase Studio Server using either the Start menu or the start_BPMS_bpms<instance>_Server.bat file.

Oracle Advanced Security

If you are using an Oracle database with Essbase Studio, you may want to configure the associated Oracle JDBC drivers with Oracle Advanced Security. Click the following link for information on Oracle Advanced Security:

http://download.oracle.com/docs/cd/B19306_01/network.102/b14268/asojbdc.htm#i1006717

Accessing EPM System Product Documentation

Find the latest EPM System product guides in the Oracle Help Center (https://docs.oracle.com/en/). To access documents to view or download, click the Applications icon. In the Applications Documentation window, select the EPM tab, and then click the Enterprise Performance Management link.

You can also find deployment-related documentation on the Oracle Technology Network (http://www.oracle.com/technetwork/index.html) and on the Oracle Software Delivery Cloud website (http://edelivery.oracle.com/EPD/WelcomePage/get_form). Or you can visit the EPM System Documentation Portal (http://www.oracle.com/us/solutions/ent-performance-bi/technical-information-147174.html). There, you’ll find links to My Oracle Support, EPM Supported Platform Matrices, and more.

Online Help in Internet Explorer

Some tables and text may display incorrectly in online help when using Internet Explorer 9.

Copying and Pasting Code Snippets from PDFs

When you cut and paste code snippets from a PDF file, some characters can be lost during the paste operation, making the code snippet invalid. Workaround: Cut and paste from the HTML version of the document.

Documentation Feedback

Send feedback on product documentation to the following email address:

EPMdoc_ww@oracle.com

Follow EPM Information Development on these social media sites:

Accessibility Considerations

Our goal is to make Oracle products, services, and supporting documentation accessible to the disabled community. EPM System products support accessibility features, which are described in the product's Accessibility Guide. Find the most up-to-date version of this guide in the Oracle Enterprise Performance Management System Documentation Library on the Oracle Technology Network (http://www.oracle.com/technology/documentation/epm.html).

In addition, this Readme file is accessible in HTML format.

Re-encrypting the Essbase Studio Password

(20746910)

If you are upgrading Oracle Business Intelligence to Release 11.1.1.9 and your Oracle Business Intelligence installation includes Essbase Studio , then you must manually re-encrypt the Essbase Studio password using the Essbase Studio password encryption utility. For more information, see "Encrypting the Catalog Password Manually In BI Installations" in Oracle Essbase Studio User's Guide.

Integration Services Catalog Migration

(21267577)

In the 11.1.2.4.000 Oracle Essbase Studio User's Guide, it says "Integration Services catalog migration is not supported on 64-bit UNIX platforms or on the Windows 2008 64-bit platform." However, Integration Services catalog migration is not supported on the Windows 2012 64-bit platform either. It is more accurate to say that Integration Services catalog migration is not supported on 64-bit platforms.

Only Private Synonyms are Displayed

(20224624)

When you select Show synonyms on the Select Tables page of the Connection Wizard, only private synonyms are displayed. Public synonyms are not displayed. This information is in the English version of the Release 11.1.2.4 Oracle Essbase Studio User's Guide, but it is not in the translated Release 11.1.2.4 Oracle Essbase Studio User's Guide.

Cannot Populate a Minischema from Multiple Data Sources

(20174855)

Step 5 from the Populating a Minischema for Relational Sources topic in the Data Source Connections chapter of the Oracle Essbase Studio User's Guide stated that you can populate a minischema from multiple data sources. This is not an accurate statement. The step has been removed from the English version of the 11.1.2.4 Oracle Essbase Studio User's Guide, but it remains in the translated guide for the 11.1.2.4 release.

Creating a Search Rule to Change and Reformat Alias Names

(18177023)

Updated the Oracle Essbase Studio User's Guide topic, “Creating a Search Rule to Change and Reformat Alias Names” to accurately reflect the user interface. In step 7, instances of “true” have been replaced with “yes.” This correction was made in the English version of the 11.1.2.4 Oracle Essbase Studio User's Guide, but the incorrect text remains in the translated guides for the 11.1.2.4 release.

Previously Undocumented User Role, cpDMDSAdmin

(11724835)

The Essbase Studio user role, cpDMDSAdmin, was previously undocumented. This role has all the privileges of the Essbase Studio Viewer, Data Source Administrator, and Metadata Administrator roles. The cpDMDSAdmin role name appears in the title bar of the Essbase Studio Console when both the Data Source Administrator and Metadata Administrator roles are selected when provisioning.

For information on provisioning and on all Essbase Studio roles, see the Oracle Enterprise Performance Management System User Security Administration Guide.

Erratum: Drill-Through C APIs Not Supported with Essbase Studio

(21264590) The following erratum applies to all 11.1.2.3.x and 11.1.2.4.x releases, and beyond.

The following Oracle Essbase C API functions are not supported with Oracle Essbase Studio drill-through.

  • EssGDTConnect

  • EssGDTRequestDrillThrough

  • ESSGDTGetInfo

  • ESSGDTSetInfo

  • ESSGDTListReports

  • EssGDTExecuteReport

  • EssDTAPIGetError

  • ESSGDTGetHeader

  • ESSGDTGetData

  • EssGDTEndDrillThrough