Oracle® Essbase

Readme

Release 11.1.2.3.000


Copyright © 2013, 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 Native Security Mode Is No Longer Supported

New Features in this Release

Installation Information

Supported Platforms

Supported Languages

Supported Paths to this Release

Defects Fixed in this Release

Known Issues

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 Oracle Enterprise Performance Management System.

Note:

Oracle Essbase Spreadsheet Add-in is not included in the Essbase 11.1.2.3 release, nor is any previous version of Spreadsheet Add-in supported with Essbase 11.1.2.3. You must use Oracle Smart View for Office.

For more information, see the Oracle Essbase Spreadsheet Add-in Statement of Direction [ID 1466700.1] at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1466700.1.

Essbase Native Security Mode Is No Longer Supported

Caution!

Oracle strongly recommends not using Essbase native security mode because of security concerns. If you are currently using Essbase native security mode, you should convert Essbase Server to EPM System security mode and migrate users to EPM System security using Administration Services Console. See “Converting Essbase Server and Migrating Users to Shared Services” in the Oracle Essbase Administration Services Online Help. After you complete the conversion and migration tasks, Essbase security is managed as described in the Oracle Enterprise Performance Management System User Security Administration Guide. References in the Essbase and Oracle Essbase Administration Services 11.1.2.3 documentation about implementing and using Essbase native security mode should be ignored.

New Features in this Release

See the Oracle Essbase New Features.

In addition, the performance of the @XREF calculation function is improved when there are several dense dynamic XREF formulas. The performance improvement is especially notable for the vector mode of @XREF.

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.

If you are coming from Release 11.1.2.0, 11.1.2.1, or 11.1.2.2, use the Cumulative Feature Overview tool to review the list of new features added between those releases. This tool enables you to identify your current products, your current release version, and your target implementation release version. With a single click, the tool quickly produces a customized set of high-level descriptions of the product features developed between your current and target releases. This tool is available here:

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.

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

11.1.2.x

Apply the maintenance release to Release 11.1.2.3.

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

11.1.1.4.x

Upgrade to Release 11.1.2.3.

Release 11.1.1.0.x to 11.1.1.3.x

Apply the maintenance release to Release 11.1.1.4 and then upgrade to Release 11.1.2.3.

Release 9.3.3.x

Upgrade to Release 11.1.2.2 and then apply the maintenance release to Release 11.1.2.3.

An environment that includes multiple releases, which can include an environment with one instance of Oracle Hyperion Shared Services or an environment with two instances of Shared Services

See "Upgrading from an Environment with Multiple Releases" in the "Upgrading EPM System Products" chapter in the Oracle Enterprise Performance Management System Installation and Configuration Guide.

Note: If you are starting from Release 9.2.0.3+, 9.3.0.x, 9.3.1.x (except for Essbase 9.3.1.4.1, 9.3.1.5, 9.3.1.6, and 9.3.1.7), or 11.1.1.x, Oracle recommends that you first upgrade to Release 11.1.1.3, then apply the maintenance release to Release 11.1.1.4, and then upgrade to Release 11.1.2.3. If you are starting from an earlier release, Oracle recommends that you upgrade to the highest level release that directly supports upgrade from your starting release.

Security Synchronization between Essbase and Shared Services was removed in Essbase Release 9.3, starting with Release 9.3.1.4.1. Essbase and Shared Services Release 11.1.1.3, however, still synchronize security information. For this reason, if you are using Essbase Release 9.3.1.4.1, 9.3.1.5, 9.3.1.6, or 9.3.1.7, you must first upgrade all products to Release 9.3.3, then upgrade to Release 11.1.2.2, and then apply the maintenance release to Release 11.1.2.3.

Recommendations:

  • When upgrading to a version of Essbase in which you use the Oracle Hyperion Enterprise Performance Management System Installer and Oracle Hyperion Enterprise Performance Management System Configurator, as in this release, database outlines that were created in any of the previous Essbase releases listed in this topic should be recreated in this release to take advantage of any new structures, features, and functionality.

  • Additionally, after you perform an upgrade from one release codeline to another, Oracle recommends as a best practice that you export the data from your databases, clear the data from the databases, and then reload the data.

Defects Fixed in this Release

This section includes defects fixed in Release 11.1.2.3.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

  • 15856456 -- Data Load. A data load using Oracle Call Interface (OCI) on a database in which data values have a large number of precision digits returns the error: Invalid member [member] in data column.

  • 14210803, 12629034 -- Data Load. A SQL data load using Oracle Call Interface (OCI) fails to load data and fails to return an error.

  • 14252473 -- Essbase Server. On Linux, Essbase terminates abnormally if a delete application request is issued while active users are connected to it.

  • 14031563 -- MDX. Running a report to show a large number of leaf members from multiple dimensions returns the error message: Query is allocating too large memory ( > 4GB) and cannot be executed. Query allocation exceeds allocation limits.

  • 15880564 -- Essbase Agent. On AIX, the Essbase Agent stops responding during a MaxL display session operation, and the application creates an .xcp file.

  • 14710347 -- Grid. Restarting Essbase causes renumbering of row entries in the SSAUDIT transaction log file, when user names in the log file contain whitespace.

  • 14618630 -- Grid. The SSAUDIT transaction log files do not record "lock and send" updates when the grid contains only a title row (no header row) and that row ends before the data rows.

  • 15884510, 16168918 -- Aggregate Storage. An aggregate storage application stops responding during a query against a database whose outline has an MDX formula containing a CASE/WHEN expression.

  • 14189474 -- Outline API. The Outline API function EssOtlQueryMembersByName returns an incorrect parent name and incorrect unique name for a shared member in a duplicate-member outline.

  • 16178344 -- MDX. An Essbase application terminates abnormally during an MDX query containing a dimension signature mismatch in a CrossJoin.

  • 14658729 -- API. An Essbase API program running on Windows 2008 R2 (64-bit) consumes too much memory.

  • 14844850 -- MaxL Shell. The MaxL Shell terminates abnormally during execution of a nested MaxL script, where the embedded script followed an error condition that was not handled correctly.

  • 14209988 -- MDX.Essbase stops responding and returns Network error [10054]: Cannot Receive Data when executing a custom calculation containing the Leaves function against an aggregate storage database.

  • 12949431 -- Report Writer. Running a report script with incorrect syntax causes the application to stop responding.

  • 14669283 -- Calculations. When a transparent partition is defined on the time dimension, Dynamic Time Series calculations on attributes return #Missing when data exists on the target for the data blocks covered by the query. This behavior occurs when the TARGETTIMESERIESOPT configuration setting is not specified in the essbase.cfg file.

  • 13995902 -- Calculations. When used in a member formula, the @DATEPART calculation function does not update the value of a member in the measure dimension if the application is not restarted.

  • 14103464 -- Calculations. An application terminates abnormally during startup or during certain calculations when Essbase is under heavy load.

  • 14301062 -- Essbase Server. Essbase Server terminates abnormally when using MaxL to export an outline that contains varying attributes.

  • 14538369 -- Essbase Server. Running an MDX script in which an Essbase application or database is not specified causes Essbase Server to terminate abnormally.

  • 14228984 -- MDX. Unauthorized data can be accessed if the PROPERTY_EXPR MDX property is used in dimension properties and calculation members.

  • 13906119 -- MaxL. The deploy MaxL statement encounters a parsing error when encrypted.

  • 13883641 -- Calculations. When a member name in an outline contains a single quote, the DATAEXPORT calculation command changes the member name to include two single quotes.

  • 14221692 -- Partitions. An aggregate storage database that is the target of a transparent partition terminates abnormally when running an MDX query that includes the partition area.

  • 14278594 -- Partitions. Essbase Server terminates abnormally when running an MDX query with a filter user on the target aggregate storage database of a transparent partition.

  • 15845424 -- Partitions. Essbase is unable to create a transparent partition when member names used in the partition area contain a dollar sign ($).

  • 11839965 -- MaxL. When running an encrypted MaxL script that targets an aggregated storage database with multiple data load buffers, Essbase incorrectly removes the first buffer.

  • 13483901 -- MaxL. When running an encrypted MaxL script that creates a drill-through URL, Essbase encounters a parsing error.

  • 14498391 -- Partitions. Calculation on a replicated partition does not work when the target partition can be updated option is not selected.

Known Issues

The following are the noteworthy known issues of this release.

  • 16618139, 16515442 -- High Availability. When the Oracle Hyperion Foundation Services database is configured on an Oracle Real Application Clusters (RAC) database in which the JDBC URL connection string specifies more than one node of the RAC database, Essbase fails to start in failover mode.

    As an example, assume that the Foundation Services database is defined with the following non-SCAN-based RAC JDBC URL:

    jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=on)
    (ADDRESS=(PROTOCOL=TCP)(HOST=myrachost1)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)
    (HOST=myrachost2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl)))

    If Essbase is configured in high-availability mode as an active/passive failover cluster, Essbase fails to start, with an error similar to the following one:

    ESSBASE / Error (1320059) Essbase error due to dbName and dbPort property missing in the Shared Services registry database. 
    The database Host is [myepmsystem.oracle.com]. If you are using Oracle RAC as the database, contact your database 
    administrator to manually configure the database connection.

    Workarounds:

    • Oracle 11gR2 or later: If the Foundation Services Oracle database version is 11gR2 or later, configure RAC using the SCAN-based method and reconfigure the Foundation Services database to use the corresponding SCAN virtual host name.

      This connection mechanism is the same as connecting to a single-node Oracle database. Essbase supports this approach.

    • Earlier than Oracle 11gR2: If the Oracle Hyperion Foundation Services Oracle database version is earlier than 11gR2, Essbase does not fully support a non-SCAN-based RAC connection, although this type of connection can work as long as the primary RAC node is alive.

      Follow these instructions to make Essbase work with the primary RAC node:

      In the following procedure, epmsys_registry_script refers to the epmsys_registry.bat (Windows) and epmsys_registry.sh (UNIX) files.

      1. Open a command prompt at the EPM_ORACLE_INSTANCE\bin folder.

        Windows example:

        C:\Oracle\Hyperion\Middleware\user_projects\epmsystem1
      2. To show the properties of the DATABASE_CONN component (for example, dbJdbcUrl) in the EPM System registry, run the following command:

        epmsys_registry_script view FOUNDATION_SERVICES_PRODUCT/DATABASE_CONN

        Windows example:

        epmsys_registry.bat view FOUNDATION_SERVICES_PRODUCT/DATABASE_CONN
      3. Make a note of the unique ID for the dbName property, if the property exists.

        For example:

        1f906cf29b5be305S4edbf22713d8d835e3aS7ff3
      4. If the localhost_name property that represents the primary RAC node host is incorrect, run the following command:

        epmsys_registry_script updateproperty "#ID/@localhost_name" OracleRACNode1DbHost

        Windows example:

        epmsys_registry.bat updateproperty "#1f906cf29b5be305S4edbf22713d8d835e3aS7ff3/@localhost_name" myracdb1.oracle.com

        A message is displayed, indicating that the property has been updated.

      5. If the dbName property is not present, run the following command:

        epmsys_registry_script addproperty "#ID/@dbName" OracleDbServiceName

        Windows example:

        epmsys_registry.bat addproperty "#1f906cf29b5be305S4edbf22713d8d835e3aS7ff3/@dbName" orcl

        A message is displayed, indicating that the property has been added.

      6. If the dbPort property is not present, run the following command:

        epmsys_registry_script addproperty "#ID/@dbPort" OracleDbPort

        Windows example:

        epmsys_registry.bat addproperty "#1f906cf29b5be305S4edbf22713d8d835e3aS7ff3/@dbPort" 1521

        A message is displayed, indicating that the property has been added.

      7. To verify the property changes for the DATABASE_CONN component, rerun the following command:

        epmsys_registry_script view FOUNDATION_SERVICES_PRODUCT/DATABASE_CONN

        Windows example:

        epmsys_registry.bat view FOUNDATION_SERVICES_PRODUCT/DATABASE_CONN
      8. Start Essbase.

        Note: 13974353, 13944879 -- Essbase failover cluster works as long as the configured primary RAC node is available. If the primary RAC node goes down, Essbase goes down and fails to start. If Essbase needs to be brought up when the primary RAC node is down, the temporary workaround is to modify the database properties in the EPM System registry to point to the secondary RAC node.

        Follow these instructions to make Essbase work with the secondary RAC node:

        In the following procedure, epmsys_registry_script refers to the epmsys_registry.bat (Windows) and epmsys_registry.sh (UNIX) files.

        1. Open a command prompt at the EPM_ORACLE_INSTANCE\bin folder.

          Windows example:

          C:\Oracle\Hyperion\Middleware\user_projects\epmsystem1
        2. To show the properties of the DATABASE_CONN component (for example, dbJdbcUrl) in the EPM System registry, run the following command:

          epmsys_registry_script view FOUNDATION_SERVICES_PRODUCT/DATABASE_CONN

          Windows example:

          epmsys_registry.bat view FOUNDATION_SERVICES_PRODUCT/DATABASE_CONN
        3. Make a note of the unique ID for the dbName property, if the property exists.

          For example:

          1f906cf29b5be305S4edbf22713d8d835e3aS7ff3
        4. Change the localhost_name property that points to the primary database host to the secondary database host, using the following command:

          epmsys_registry_script updateproperty "#ID/@localhost_name" OracleRACNode2DbHost

          Windows example:

          epmsys_registry.bat updateproperty "#1f906cf29b5be305S4edbf22713d8d835e3aS7ff3/@localhost_name" myracdb2.oracle.com

          A message is displayed, indicating that the property has been updated.

        5. If you need to change the dbName property (for example, the SERVICENAME of the secondary RAC node is different than the primary RAC node, or you want to connect using the SID of the secondary RAC node, which is different than the SID of the primary RAC node), run the following command:

          epmsys_registry_script updateproperty "#ID/@dbName" OracleDbServiceName

          Windows example:

          epmsys_registry.bat updateproperty "#1f906cf29b5be305S4edbf22713d8d835e3aS7ff3/@dbName" orcl2

          A message is displayed, indicating that the property has been updated.

        6. If the dbPort property for the secondary RAC node is different from the primary RAC node, run the following command:

          epmsys_registry_script addproperty "#ID/@dbPort" OracleDbPort

          Windows example:

          epmsys_registry.bat addproperty "#1f906cf29b5be305S4edbf22713d8d835e3aS7ff3/@dbPort" 1522

          A message is displayed, indicating that the property has been added.

        7. To verify the property changes for the DATABASE_CONN component, rerun the following command:

          epmsys_registry_script view FOUNDATION_SERVICES_PRODUCT/DATABASE_CONN

          Windows example:

          epmsys_registry.bat view FOUNDATION_SERVICES_PRODUCT/DATABASE_CONN
        8. Start Essbase.

        Note:

        This temporary workaround is valid only as long as the secondary RAC database node is alive. If at a later time the secondary RAC node goes down and Essbase is expected to work, follow these same instructions to reconfigure the database in the EPM System registry to point to the most preferred and alive node in the RAC database.

  • 16457613 -- The TARGETTIMESERIESOPT configuration setting is used to optimize queries on transparent partitions. When this configuration setting is set in the essbase.cfg file and a transparent partition is defined on the time dimension, Dynamic Time Series calculations on any data existing on the target database returns #Missing or the result is incorrect. This behavior occurs because D-T-S calculations with this optional configuration setting are always extracted from the source database of the transparent partition.

  • 16457664 -- In a database with a transparent partition in which the target has no data blocks covered by the query, Dynamic Time Series calculations on attributes returns #Missing. This behavior occurs when the TARGETTIMESERIESOPT configuration setting is not specified in the essbase.cfg file.

  • 13457388 -- 64-bit Windows Server 2008. When running 64-bit Essbase on 64-bit Windows Server 2008, some Essbase Server names are not recognized. This issue occurs when the IPv6 option is disabled on 64-bit Windows Sever 2008.

    Workaround: Enable IPv6. Microsoft recommends that you leave IPv6 enabled (which is the default).

  • 13637169 -- AIX (64-bit). Applications terminate abnormally when the ulimit data segment size is too small. Oracle recommends setting the data segment size to unlimited. See “Setting User Limits on 64-bit AIX” in the Oracle Enterprise Performance Management System Installation and Configuration Guide.

  • 13624319 -- HP-UX. Essbase Server running on HP-UX 11.23 is unable to create an application. Error messages:

    /usr/lib/hpux64/dld.so: Unsatisfied code symbol '__cxa_get_exception_ptr' in load module
    'EPM_ORACLE_HOME/products/Essbase/EssbaseServer/bin/libessasosm.so'.
    [Tue Jan 24 11:23:08 2012]Local/ESSBASE0///Error(1052003)
    Timed out reading from server
    [Tue Jan 24 11:23:08 2012]Local/ESSBASE0///Error(1054001)
    Cannot load application Apbg6641 with error number [1052003] - see server log file
    [Tue Jan 24 11:23:08 2012]Local/ESSBASE0///Error(1054067)
    Internal error

    Workaround: HP-UX 11.23 is not a supported operating system. For a supported version of HP-UX, see the Oracle Hyperion Enterprise Performance Management System Certification Matrix (http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html).

  • 16453364 -- Using a calculation string with the execute calculation MaxL statement can cause the Essbase Agent to run slowly and become seemingly unresponsive. To avoid this behavior, save the calculation string as a server-based calculation script and execute the stored calculation script.

  • 13847733 -- Upgrade. If you are upgrading Essbase to a new machine, sample applications cannot be moved. New sample applications will be installed on the new machine.

  • 10096616, 13084180 -- SSL. When SSL is enabled, some Essbase operations experience performance degradation.

  • 11725513, 13404757 -- Kernel. Logging into Essbase Server from the MaxL Shell on certain servers that run AIX 5.3 might result in the following error message:

    MAXL> login essexer password;
    WARNING - 1040152 - Failed to load ZT library
    WARNING - 1040156 - SSL initialization failed with error code [1040152]
    OK/INFO - 1051034 - Logging in user [essexer]
    OK/INFO - 1051035 - Last login on Monday, February 07, 2011 2:57:58 PM.
    OK/INFO - 1241001 - Logged in to Essbase.

    This error also might occur when starting Essbase Server or running ESSCMD, and is related to initiating SSL.

    Workaround: Apply the AIX 5.3 kernel extensions update on the computers on which Essbase Server and Essbase client are installed.

  • 10159576, 12618625 -- Kernel. In this release, the 64-bit server has been expanded to accommodate larger cache sizes. As a result, if using an older client (9.3.x, 11.1.1.x, or 11.1.2.1) with this version's 64-bit server, the following functionality is disabled:

    C-API:

    • EssGetDatabaseState — Displays zeroes for data cache, data file cache, or index cache

    • EssSetDatabaseState — Cannot set the sizes of data cache, data file cache, or index cache

    • EssGetDatabaseInfo — Displays zeroes for data cache, data file cache, or index cache

    MaxL

    • alter database DBS-NAME set data_cache_size SIZE-STRING

    • alter database DBS-NAME set data_file_cache_size SIZE-STRING

    • alter database DBS-NAME set index_cache_size SIZE-STRING

    ESSCMD:

    • GETDBSTATE — Displays zeroes for data cache, data file cache, or index cache

    • SETDBSTATE — Cannot set the sizes of data cache, data file cache, or index cache

    • GETDBINFO — Displays zeroes for data cache, data file cache, or index cache

    Data Mining. In Essbase and Oracle Essbase Administration Services, Data Mining is no longer supported. For Data Mining functionality, please consider Oracle Data Mining, which is an option in Oracle Database Enterprise Edition.

  • 16403153 -- Importing a text list value with an ID greater than 32768 results in an error.

  • 12757320, 11875089, 12757319 -- Filters. Filters are not created for a provisioned user when running Refresh Security Filters from within Oracle Hyperion Planning to synchronize Planning with Essbase and if the Delegated User Management option is enabled in Oracle Hyperion Shared Services Console.

    Workaround: Disable Delegated User Management and run Refresh Security Filters from Planning again.

  • 12757316, 11875352 -- Filters. Duplicate user entries can be created when running Refresh Security Filters from within Planning to synchronize Oracle Hyperion Planning with Shared Services and Essbase, if the Delegated User Management option is enabled and the user exists in more than one external repository.

  • 11800146, 10623580 -- Kernel. Direct I/O is not supported on Linux.

  • 12884791 -- Committed Access Rollback. In committed access mode, there is a potential for a leak of free space in data files during transactional rollback.

  • 20046936 -- To avoid abnormal application shutdowns, follow these recommendations:

    • Do not use the DELAYEDRECOVERY configuration setting in essbase.cfg, and in particular, do not set it to FALSE.

    • Do not run the MaxL statement alter database recover freespace.

Accessing EPM System Product Documentation

The most recent version of each EPM System product guide is available for downloading or viewing from the EPM System Documentation area of the OTN website (http://www.oracle.com/technology/documentation/epm.html). You can also use the Oracle Enterprise Performance Management System Documentation Portal (http://www.oracle.com/us/solutions/ent-performance-bi/technical-information-147174.html), which also links to EPM Supported Platform Matrices, My Oracle Support, and other information resources.

Deployment-related documentation is also available from the Oracle Software Delivery Cloud website (http://edelivery.oracle.com/EPD/WelcomePage/get_form).

Individual product guides are available for download on the Oracle Technology Network website only.

Recommended User and Group Management

Oracle recommends using Oracle Hyperion Shared Services Console, Oracle Hyperion Shared Services Java API, or Oracle Hyperion Enterprise Performance Management System Lifecycle Management for the following user and group management tasks, instead of using MaxL or Essbase APIs:

  • alter user (add to group, remove from group)

  • create or replace user

  • create or replace group

  • drop user (except when using from security_file syntax)

  • drop group (except when using from security_file syntax)

  • display user all

  • display group all

(19266380)

JAVAMAXMEMBERSPEROUTLINE

This essbase.cfg configuration setting was introduced in Release11.1.2.1.102, but was not documented.

JAVAMAXMEMBERSPEROUTLINE

Sets a maximum number of member handles allowed to be open in a Java API Essbase outline.

JAVAMAXMEMBERSPEROUTLINE [appname [dbname]] n
  • appname—Optional. Specifies the application for which the maximum is to be set.

    If you specify a value for appname and do not specify a value for dbname, the setting applies to all databases in the specified application. To enable the setting for a specific database, you must specify an application and database.

  • dbname—Optional. Specifies the database, in the application specified by appname, for which the maximum is to be set.

    If you specify a value for dbname but do not specify a value for appname, your specification is ignored.

  • n—A value specifying the maximum number of allowed open member handles.

Triggers

Although the Oracle Essbase Technical Reference states that triggers functionality is a separately licensed option, it is not: the functionality is included.

Maximum size for DYNCALCCACHEMAXSIZE Configuration Setting

The following information updates the DYNCALCCACHEMAXSIZE topic in the Essbase 11.1.2.3 Oracle Essbase Technical Reference.

The maximum amount of memory that can be allocated for the dynamic calculator cache is 4 G. This limit applies to Essbase 32-bit and 64-bit.

The maximum size is specified as an integer expressed in bytes (B), kilobytes (K), megabytes (M), or gigabytes (G). A value expressed in whole bytes, without a qualifier (B, K, M, or G), results in a maximum size of 2 G, regardless of whether the value of the whole bytes expressed is larger than 2 G. To achieve a maximum amount up to 4 G, you must use a qualifier. For example, a value of 4294967296, which is equal to 4 G, results in only approximately 2 G of memory being allocated.

(16881805)

Runtime Substitution Variables String

The following information updates the information about the syntax of a string of runtime substitution variables in the Essbase 11.1.2.3 documentation.

When executing a stored calculation script with runtime substitution variables specified in a list, the list is a string of key/value pairs. The string must be enclosed with single quotation marks, and the key/value pairs must be separated by a semicolon, including a semicolon after the last runtime substitution variable in the string and before the terminal single quotation mark.

Updated example of a runtime substitution variable string:

'a=100;b=@CHILDREN("100");c="Actual"->"Final";d="New York";'

Updated example of a MaxL statement:

execute calculation Sample.Basic.Calc3 with runtimesubvars ‘a=100;b=50;’;

(16675163)

Configuring Parallel SQL Connections for Essbase SQL Interface

In the “Performing Multiple SQL Data Loads in Parallel to Aggregate Storage Databases” topic in the Oracle Essbase SQL Interface Guide, incorrect information is given for configuring SQL drivers to enable parallel SQL connections. The following information is correct:

This feature requires parallel SQL connections. You must create a SQL configuration file named esssql.cfg in the ARBORPATH/bin folder to change the default settings for the ODBC driver you are using. (By default, SQL Interface disables parallel connections for the DataDirect ODBC drivers that are provided with Essbase.)

The following examples enable parallel SQL connections:

  • Microsoft SQL on Windows (non-DataDirect driver):

    [
    Description "SQL Server"
    DriverName SQLSRV
    UserId 1
    Password 1
    Database 1
    SingleConnection 0
    UpperCaseConnection 0
    IsQEDriver 0
    ]
  • Microsoft SQL on UNIX and Linux (DataDirect driver):

    [
    Description "DataDirect SQL Server Native Wire Protocol"
    DriverName ARSQLS
    UserId 1
    Password 1
    Database 1
    SingleConnection 0
    UpperCaseConnection 0
    IsQEDriver 1
    ]

(17867759)

AGTMAXLOGFILESIZE and APPMAXLOGFILESIZE Configuration Setting Examples

In the Oracle Essbase Technical Reference, the examples for the AGTMAXLOGFILESIZE and APPMAXLOGFILESIZE configuration settings incorrectly state the type of log file. The following information is correct:

  • AGTMAXLOGFILESIZE Example

    AGTMAXLOGFILESIZE 1500000

    Sets the maximum Essbase Server log file size to 1500000 bytes.

  • APPMAXLOGFILESIZE Example

    APPMAXLOGFILESIZE 1500000

    Sets the maximum application log file size to 1500000 bytes.

(17932470, 17938478)

Execute Aggregate Selection MaxL Statement; selecting <INTEGER> views Grammar

The following information updates the description of the selecting <INTEGER> views grammar of the execute aggregate selection MaxL statement in the Essbase 11.1.2.3 Oracle Essbase Technical Reference.

Selects the number of views based on whether the number of views specified in <INTEGER> is greater than or equal to, or less than, the recommended number of default views that are returned by the execute aggregate selection statement. By default, Essbase determines the recommended number of default views.

Assume that <RECNUM> represents the recommended number of default views:

  • If the value of <INTEGER> is greater than or equal to the value of <RECNUM>, the selected number of views equals <RECNUM>.

    For example, if <INTEGER> equals 20 and <RECNUM> equals 15, the number of selected number of views equals 15.

  • If the value of <INTEGER> is less than the value of <RECNUM>, the number of views that are selected equals <INTEGER>.

    If you want the number of views that are selected to equal the value of <INTEGER>, use the stopping when total_size exceeds <STOPPING-VAL> grammar to change the number of recommended default views that are returned by the execute aggregate selection statement. Define the <STOPPING-VAL> factor large enough, such as 50 or 100, so that the number of default views that are returned by execute aggregate selection is greater than the value of <INTEGER>.

    For example, if <INTEGER> equals 20 and <RECNUM> equals 50, the number of selected number of views equals 20.

Note:

This parameter does not create views.

(16603260)

Starting and Stopping Essbase and Essbase Clusters Using OPMNCTL Commands

Essbase is managed by Oracle Process Manager and Notification Server (OPMN). Components that are managed by OPMN must be started and stopped using the opmnctl command line interface, regardless of whether Essbase is configured as a single node or for active-passive clustering in OPMN.

(21044579, 20714885)

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

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

(21264590)

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.