Oracle® Essbase

Readme

Release 12.2.1.0.0


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

Essbase 12.2.1 Use Cases for BI 12.2.1

Administration Services and Essbase Studio Are No Longer Available

Features No Longer Supported in this Release

Installation Information

Supported Platforms

Supported Paths to this Release

Known Issues in this Release

Documentation Updates

Documentation Feedback

Accessibility Considerations

Purpose

This document includes important, late-breaking information about this release of Oracle Essbase. Review this Readme thoroughly before installing Essbase in an Oracle Business Intelligence 12.2.1.0.0 environment.

Essbase 12.2.1 Use Cases for BI 12.2.1

These are the use cases for deploying Essbase 12.2.1 in BI 12.2.1:

  • Essbase12.2.1 includes the Essbase Business Intelligence Acceleration feature. Using the Essbase BI Acceleration Wizard, a BI administrator can deploy an Essbase cube with selected data from a BI business model, resulting in improved query performance and reducing the dependency on underlying database optimizations.

  • Expanding the domain to support Essbase 12.2.1 and later releases.

Note:

You can continue to use the Essbase databases in your pre-12.2.1 Essbase installations as BI data sources. See the Essbase documentation for the release you are using.

See these chapters in the Oracle Essbase Database Administrator's Guide for Release 12.2.1:

  • Part XI: “Essbase Deployed on a WebLogic Server Cluster

    • Chapter: “Essbase Java Agent

    • Chapter: “Understanding Essbase Deployed in BI 12.2.1

  • Part XII: “Essbase Cube Deployment Service and Essbase Business Intelligence Acceleration”:

    • Chapter: “Understanding the Essbase Cube Deployment Service

    • Chapter: “Understanding Essbase Business Intelligence Acceleration

    • Chapter: “Using the Essbase BI Acceleration Wizard

    • Chapter: “Essbase BI Acceleration Wizard UI Reference and Accessibility

Administration Services and Essbase Studio Are No Longer Available

Release 12.2.1 includes Essbase and Oracle Hyperion Provider Services. Oracle Essbase Administration Services and Oracle Essbase Studio are no longer available and are not supported with Release 12.2.1.

References to Administration Services and Essbase Studio in the Essbase and Provider Services documentation set should be ignored.

Features No Longer Supported in this Release

Essbase introduces behavior changes in addition to new features. Changes in behavior include desupported features, components, configuration settings, options, and syntax. In the release in which a feature is not supported, the functionality is either completely removed from the product or, if not completely removed, is no longer supported.

The topics in this section apply to the Essbase 12.2.1 release.

For information about features that were no longer supported or deprecated in previous releases of Essbase, see “Essbase Features No Longer Supported or Deprecated in Previous Releases” in the Oracle Essbase Database Administrator's Guide.

Starting with Essbase 12.2.1, these features are no longer supported:

  • Direct I/O

  • Block storage outline synchronization

  • Outline change log

  • Currency conversion applications and currency partitions

  • Data compression types: zlib and none

  • Linked partitions

  • Oracle Essbase Administration Services JAVA API

  • Network File System (NFS) protocol on Network Attached Storage (NAS) devices

  • MaxL statements and grammar related to user and group management or to other deprecated security functionality:

    • The following MaxL statements in their entirety are no longer supported:

      • alter group

      • alter user

      • create group

      • create user

      • deploy

      • drop group

      • drop user

      • export security file

    • In these MaxL statements, the following grammar is no longer supported:

      • alter system statement:

        • clear logfile

        • sync security_backup

        • compact security file

        • set message_level

        • set eas_loc

      • display group statement—failed_sss_migration

      • display system statement:

        • security file fragmentation_percent

        • lease manager

      • display user statement:

        • failed_sss_migration

        • shared_services_native with auto_password

        • migr_modified_access

      • grant statement— all privileges and roles (you can only grant calculation and filter access)

References to these features in the Essbase and Oracle Hyperion Provider Services documentation set should be ignored.

Installation Information

See the Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence for information on installing Essbase in the BI 12.2.1 environment.

Supported Platforms

See the Oracle Fusion Middleware 12c Certifications on the Oracle Fusion Middleware Supported System Configurations page on the Oracle Technical Network at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html.

Supported Paths to this Release

Essbase 12.2.1 supports only two use cases, neither of which involve upgrading from a previous release of Essbase. See Essbase 12.2.1 Use Cases for BI 12.2.1.

Caution!

Oracle recommends using the same version of the Essbase product and components (server, client, runtime client, API, and JAPI).

Known Issues in this Release

The following are the noteworthy known issues of this release.

  • 20148540 -- Performing an aggregate view selection using an 11.2.3.x client against the 12.2.1 Essbase Server generates the following error message:

    This protocol is obsolete. Client application must be upgraded to use this functionality.
  • 21165772 -- When setting up the Singleton shared data directory (SDD) in a scaled out deployment, Essbase must be set up in the same directory structure as the Essbase application directory. If the directory structure is not the same, block storage applications might not start.

  • 21875962, 21888775 -- Essbase Java Agent fails to start out of the box when Essbase is deployed in BI 12.2.1, which is configured with DB2.

    Workaround:

    1. Login to the Oracle WebLogic Server Administration console.

    2. Navigate to Services, then Data Sources, then wlsservices_datasource, and then the Connection Pool tab.

    3. Use the Lock & Edit option.

    4. In the Properties section, change the user property from:

      user=<RCU_PREFIX>_WLS_RUNTIME

      To:

      user=<RCU_PREFIX>_WLS

      For example:

      user=MYBI_WLS
      oracle.net.CONNECT_TIMEOUT=10000
      SendStreamAsBlob=true
    5. Save the changes.

    6. Navigate to Environment, then Clusters, then bi_cluster, and then the Migration tab.

    7. In the Auto Migration Table Name field, prepend <RCU_PREFIX>_WLS_RUNTIME to the exiting ACTIVE value:

      <RCU_PREFIX>_WLS_RUNTIME.ACTIVE

      Using the example from Step 4:

      MYBI_WLS_RUNTIME.ACTIVE
    8. Save the changes.

    9. Use the Activate Changes option to makes these changes take effect.

    10. Restart the BI 12.2.1 environment.

  • 19842726 -- If you use XML outline editing to rename a member, the cell data is not retained.

  • 20071438, 19926562 -- Exported data that contains member names in double quotation marks and ending in a backslash can lead to rejected records when it is re-imported using a rules file.

  • 20347013 -- With Essbase running on AIX, in some cases query results for a 0 value might display as 00. This issue is caused by the operating system, not Essbase.

    IBM has issued an APAR for AIX V7.1 that fixes this problem: IV24433: SPRINTF PRINTS ONE MORE FRACTIONAL DIGIT THAN SPECIFIED APPLIES TO AIX 7100-01. Download the fix from: http://www-01.ibm.com/support/docview.wss?uid=isg1IV24433

  • 21968145, 21962838 -- For Essbase Cube Deployment Service, a shared login must be manually configured in the connection pool.

    Description

    When using the Essbase Cube Deployment Service wizard to create a new Essbase connection pool in the BI repository, there is no opportunity to enter the shared login user name and password. However, in Oracle Business Intelligence 12.2.1.0.0 and higher, a shared login is required for all Essbase connection pools. An Essbase connection pool that is configured without a shared login will cause the BI Server to use Oracle Hyperion Shared Services shared token authentication, which is no longer supported for Essbase connections from BI. This may cause Essbase connections from certain BI components, such as Visual Analyzer, to fail with the following error:

    [nQSError: 96002] Essbase Error: Login failed with error 1051293. Verify the URL and the login credentials

    Workaround Option 1

    While using the Essbase Cube Deployment Service wizard, select from the RPD an existing Essbase data source and connection pool that already has the shared login information provided.

    Workaround Option 2

    After completing the Essbase Cube Deployment Service wizard, open the BI repository in the Oracle BI Administration Tool and manually update the connection pool created by the Essbase Cube Deployment Service wizard, providing the required shared login information. Or, deselect the SSO option if it is not required.

    To configure the user name and password for the Essbase connection pool created by the Essbase Cube Deployment Service wizard,

    1. Download the BI repository from the BI Server, using the data-model-cmd utility. For example,

      %DOMAIN_HOME%\bitools\bin\data-model-cmd.cmd downloadrpd -O repository.rpd -W YourRPDPassword -U YourBIAdminUsername -SI YourServiceInstance
    2. Open the RPD file in the Oracle BI Administration Tool.

      %DOMAIN_HOME%\bitools\bin\admintool.cmd
    3. Locate the connection pool created by the Essbase Cube Deployment Service wizard in the physical layer of the BI repository, and double click it to open the Connection Pool dialog.

    4. Check the Shared logon option, and enter the user name and password for the Essbase Server.

      Note:

      If you leave the SSO option checked, enter the user name and password of an Essbase administrator with the permission to impersonate other users.

    5. Save the repository, and close the Oracle BI Administration Tool.

    6. Upload the modified BI repository to the BI Server using the data-model-cmd utility. For example,

      %DOMAIN_HOME%\bitools\bin\data-model-cmd.cmd uploadrpd -I repository.rpd -W YourRPDPassword -U YourBIAdminUsername -SI YourServiceInstance
    7. Log out of any existing sessions in BI Answers or Visual Analyzer, and reconnect.

For more information about updating connection pool properties, see the Oracle BI Metadata Repository Builder's Guide.

Correction: Using Runtime Substitution Variables in Calculation Scripts Run in Smart View

The following information updates the “Using Runtime Substitution Variables in Calculation Scripts Run in Smart View” section of the Oracle Essbase Database Administrator's Guide for 12.2.1.0.0:

  • The value of the runtime substitution variable must be set to POV; it cannot be set to a member name.

  • The runtime substitution variable data type can be set to a member, string, or number; it cannot be set to a date

The correct syntax of a runtime substitution variable definition for use in Oracle Smart View for Office:

SET RUNTIMESUBVARS
{
rtsv = POV
   <RTSV_HINT>
      <svLaunch>
         <description>rtsv_description</description>
         <type>member | string | number</type>
         <dimension>dimName</dimension>
         <choice>single | multiple</choice>
         <allowMissing>true | false</allowMissing>
      </svLaunch>
   </RTSV_HINT>
};

Only the example in the “Example 1: Runtime Substitution Variable Set to POV” topic is correct. Ignore the examples in these topics:

  • Example 2: Runtime Substitution Variable Set to a Single Member Name

  • Example 3: Runtime Substitution Variable Set to Multiple Member Names

  • Example 4: Example: Runtime Substitution Variable—String Data Type Implied

The date data type is not supported; however, the string data type can be defined as a date.

The correct description of the string data type:

string—The runtime substitution variable value can be defined as a single member name, a comma separated list of member names (for example, "New York","Florida"), or a date.

When using the string data type, the Member Selection dialog box is not available; therefore, the Oracle Smart View for Office user must be sure to use the correct syntax (enclosing a member name in quotes, separating multiple member names with a comma, or, for a date, matching the format of the date string to the format that is defined in the calculation script—mm-dd-yyyy or dd-mm-yyyy).

(21903619, 22777038)

Drill-Through C APIs Not Supported with Essbase Studio

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

  • EssGDTConnect

  • EssGDTRequestDrillThrough

  • ESSGDTGetInfo

  • ESSGDTSetInfo

  • ESSGDTListReports

  • EssGDTExecuteReport

  • EssDTAPIGetError

  • ESSGDTGetHeader

  • ESSGDTGetData

  • EssGDTEndDrillThrough

@RELATIVE Calculation Function

Documentation for the @RELATIVE function states that it returns all members at the specified generation or level that are above or below the specified member. Clarification: If the specified parameters to @RELATIVE are used with the specified level or generation describing the specified member, then the specified member is included. For example, @RELATIVE(("100-10",0)) includes 100-10 in the results, because 100-10 is a level 0 member. @RELATIVE(("100",1)) includes 100 in the results, because 100 is a level 1 member. (23346627)

DATAEXPORT Calculation Command

The DATAEXPORT documentation incorrectly states that the command puts the database in read-only mode. (22899744, 20772811)

Incorrect MaxL Login Example

The example in the MaxL documentation for the login statement is incorrect. The correct example is:

login admin password on 'http://myhost:13080/aps/Essbase?clustername=EssbaseCluster-1'; 

(23033490)

Transaction History Not Saved With Forced Restructure

All data load and calculation transaction history is removed after a forced restructure, because empty blocks are removed upon restructure. (22952371)

Variable Defined By a VAR Calculation Command Cannot Be Included in the FIX Member Statement

The variable (varName) that is defined by a VAR calculation command cannot be used within the FIX member statement. The FIX members are evaluated before the calculation is executed, and variables are evaluated during runtime after the FIX statement is set. Because variables can change during the calculation execution, you cannot use the variable as part of the FIX statement. The following example shows the incorrect use of the variable in the FIX member statement:

VAR varName=1;
FIX (@relative(@memberat(@List("Product1","Product2"),varName),0)) 
   commands;
ENDFIX;

(22918285)

Correction: (^) Never Consolidate Operator is Not Supported in Aggregate Storage Databases

The following information updates the Oracle Essbase Database Administrator's Guide for 11.1.2.4:

  • The (^) never consolidate operator is not supported in aggregate storage databases. Any references to the use of the ^ operator in aggregate storage outlines should be ignored.

  • In Administration Services Console, by default, text and date measures are assigned the never consolidate operator (^). However, when used in an aggregate storage database, the ^ operator is ignored in the consolidation that follows.

In the “Outline Factors Affecting Data Values” topic, the ^ consolidation operator is incorrectly listed as supported for dynamic hierarchies in aggregate storage databases.

(19376666, 19131994)

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. This Readme file is accessible in HTML format.