Oracle® Essbase

Readme

Release 11.1.2.4.000


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

Updated: August 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

Features No Longer Supported or Deprecated in this Release

Compatibility Guidelines

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.

New Features in this Release

See the Oracle Essbase New Features. 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.

Essbase introduces behavior changes in addition to new features. Changes in behavior include deprecated and desupported features, components, configuration settings, options, and syntax.

The topics in this section apply to the Essbase 11.1.2.4 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.

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.

Additional Essbase Features No Longer Supported in this Release

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.

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

  • Oracle Essbase Integration Services, including Hybrid Analysis and Advanced Relational Access

    Many of the basic concepts of Hybrid Analysis and Advanced Relational Access have been folded into the functionality of XOLAP cubes in Oracle Essbase Studio.

  • Visual Basic API

    Oracle strongly recommends using the Essbase JAVA APIs. You can also use the Essbase C APIs.

  • Configuration settings:

    • PRELOADALIASNAMESPACE

    • PRELOADMEMBERNAMESPACE

    • PRELOADUDANAMESPACE

    • MAXACTIVEUPDATETRANSACTIONS

    • MAXTOTALACTIVETRANSACTIONS

Essbase Features Deprecated in this Release

In the release in which a feature is deprecated, the feature is still fully functional (unless limitations are specified) and supported. Typically, a deprecated feature will no longer be supported in the next release.

Note:

Oracle strongly recommends not implementing deprecated features.

The following Essbase features are deprecated in release 11.1.2.4:

  • 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:

    • alter user statement—only the add [to group] and remove [from group] grammar is deprecated

    • create group statement—the entire statement is deprecated

    • create user statement—the entire statement is deprecated

    • display group statement—only the all grammar is deprecated

    • display user statement—only the all grammar is deprecated

    • drop group statement—all grammar is deprecated except for the from security_file grammar

    • drop user statement—all grammar is deprecated except for the from security_file grammar

Limited Data Source Support for XOLAP

Starting with Essbase 11.1.2.4, XOLAP is supported for these data sources only:

  • IBM DB2

  • Netezza

  • Teradata

When upgrading from a supported earlier release of Essbase to release 11.1.2.4, you need to be aware of these compatibility guidelines.

Outline Compatibility between 11.1.2.4 Essbase Server and Client with Earlier Releases

In Essbase 11.1.2.4, an outline that is created or updated using the XML outline editing method results in a new outline version. Differences in outline versions impact whether an application can be used with an Essbase Server or client from an earlier release of Essbase.

Aggregate storage outlines:

  • To use the XML outline editing feature in Essbase 11.1.2.4, aggregate storage outlines that were created in an earlier release must first be migrated to 11.1.2.4.

    Methods for migrating an outline:

    • Open the outline in Administration Services Console and, when prompted to migrate the older outline, click OK.

    • Use the C API function EssOtlSetOPGVersion or the Java API method setOPGVersion.

    Note:

    Outlines that are migrated to 11.1.2.4 cannot be edited in an earlier release client.

  • An aggregate storage outline created in Essbase 11.1.2.4, regardless of whether it uses XML outline editing, cannot be used in an earlier release of Essbase.

Block storage outlines:

  • Block storage outlines created in an earlier release of Essbase can use XML outline editing in 11.1.2.4 without needing to migrate the outline. (Essbase automatically migrates block storage outlines.)

  • Block storage outlines that are created or updated in Essbase 11.1.2.4 and that use the XML outline editing feature cannot be used in an earlier release.

Table 1 describes the support matrix between Essbase Servers, clients, and RTCs:

Table 1. Support Matrix

Client

RTC[1]

Essbase Server

Aggregate Storage Outline

Block Storage Outline

11.1.2.2.xxx

11.1.2.3.0xx

11.1.2.3.5xx

11.1.2.2.xxx RTC with >= 11.1.2.2.xxx client.

11.1.2.3.0xx RTC with >= 11.1.2.3.0xx client

11.1.2.3.5xx RTC with >= 11.1.2.3.5xx client

11.1.2.4.000

Aggregate storage outline created in an 11.1.2.3.50x or earlier supported release: Edit and query is identical to the client's same-version Essbase Server.

Block storage outline created in a supported release and that does not use the 11.1.2.4 XML outline editing feature: Edit and query is identical to the client's same-version Essbase Server.

11.1.2.2.xxx

11.1.2.3.0xx

11.1.2.3.5xx

11.1.2.2.xxx RTC with >= 11.1.2.2.xxx client

11.1.2.3.0xx RTC with >= 11.1.2.3.0xx client

11.1.2.3.5xx RTC with >= 11.1.2.3.5xx client

11.1.2.4.000

Aggregate storage outline created in 11.1.2.4, regardless of whether it uses the XML outline editing feature: Edit fails; query is successful when querying client-version features.[2]

Block storage outline created in a supported release and that uses the XML outline editing feature in 11.1.2.4: Edit fails; query is successful when querying client-version features.[2]

11.1.2.4.000

11.1.2.4.000

11.1.2.4.000

Aggregate storage outline created in an 11.1.2.3.50x or earlier release: To use the XML outline editing feature in 11.1.2.4, the outline must first be migrated to 11.1.2.4.

Block storage outline created in a supported release: The outline does not need to be migrated to 11.1.2.4 before using the XML outline editing feature.[3]

1 The RTC version must be greater than, or equal to, the client version within the same release. For example, you can use the 11.1.2.2.001 RTC, or a higher version of the RTC in the 11.1.2.2.xxx release, with a client compiled with Essbase11.1.2.2.001.

2 A query that involves the XML outline editing feature does not result in abnormal termination.

3 If the block storage outline is updated in 11.1.2.4 to use the XML outline editing feature and that feature is later removed, the outline can then be used in an earlier client.

API Client Compatibility between 11.1.2.4 Essbase Runtime Client (RTC) and Earlier Releases

To use the Essbase 11.1.2.4 RTC, API client programs that were compiled with API headers and libraries from an earlier Essbase release must be recompiled with 11.1.2.4.000 API headers and libraries.

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.

Note:

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 2. 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 Essbase portfolio products (Essbase, Administration Services, Oracle Hyperion Provider Services, and Essbase Studio) and components (server, client, runtime client, API, and JAPI).

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

  • 18020023, 18019954, 13698528 -- Smart View. A pivot operation from row to column fails, pivoting the row member into the POV instead.

  • 17811942 -- Smart View. A pivot operation incorrectly shifts POV dimensions.

  • 19773529 -- Smart View. Incorrect values appear in a Smart View Client retrieval.

  • 19711424 -- Smart View. Data shows as #MISSING in Smart View Client after moving a member.

  • 19832878 -- Smart View. Empty rows are inserted while performing a zoom-in on a member in Smart View Client.

  • 18036612 -- Calculation. Saving an outline with a member formula containing a circular dependency results in a network error.

  • 17824533 -- Calculation. A calculation script that has FIX and EXCLUDE statements results in abnormal shutdown of the application while reordering the excluded members in the outline.

  • 14644362 -- Calculation. A calculation script that contains @CALCMODE(BottomUp) and SET CREATENONMISSINGBLK ON fails and results in an XCP file.

  • 17583010 -- Calculation. @MDANCESTVAL causes an abnormal shutdown of the application when used with runtime dependent functions.

  • 17443687 -- Calculation. @MAXSRANGE does not treat #MISSING values as described in the Oracle Essbase Technical Reference.

  • 14191566 -- Calculation. Data values may be different than expected because of rounding differences between older versions of Essbase and release 11.x. See the help topic for the @ROUND function in the Oracle Essbase Technical Reference, to optionally select a compatibility setting.

  • 19491013 -- Smart View. An aggregate storage application can terminate abnormally after connecting to and retrieving from Smart View Client.

  • 19832630 -- Aggregate storage. In some cases, aggregations return incorrect results for an aggregate storage application.

  • 19832902 -- Aggregate storage. On an aggregate storage database, an MDX formula can return inconsistent results.

  • 14829630 -- Data export. If a text measure exists in the database, DATAEXPORT fails for a relational database export using ODBC.

  • 19783553 -- Data export. Export performance was not optimal. With this fix, performance is improved.

  • 16843064 -- Report Writer. Report writer query with syntax error for <LINK command causes abnormal shutdown of application.

  • 19571906 -- Smart View. Smart View. After saving the data form, cell data is missing from a data form with three or more columns and duplicate rows or columns.

  • 19832856 -- Area. Using Smart View with Essbase Release 11.1.2.3 with SSOPTIMIZEDGRIDPROCESSING set to TRUE in essbase.cfg, data can be submitted by users to intersections that are secured as read-only.

  • 6552344 -- Calculation. Calculation performance improvements.

  • 17363415 -- Calculation. An @XREF calculation fails to process offsets correctly, and the application terminates abnormally.

  • 17563682 -- Aggregate storage. An application stops responding upon a Smart View Refresh All report.

  • 16711423 -- API. In Essbase Java API, an outline fails to verify if it has a dynamic calc member with more than 100 children.

  • 18016800 -- Metadata. An Essbase application terminates abnormally during a dimension build with an invalid rules file.

  • 17195715 -- MDX. An Essbase application terminates abnormally during an MDX query using hybrid aggregation.

  • 18034801, 18035015 -- MDX. An Essbase application terminates abnormally during an MDX query using the Count function.

  • 18077252 -- Aggregate Storage. An aggregate storage member formula referencing a member with $ in the name returns an unknown member error.

  • 17084177 -- Smart View. A zoom-in operation produces incorrect results with formula preservation and suppress #MISSING.

  • 17888409 -- MDX. An Essbase application terminates abnormally during an MDX query of descendants, with a slicer.

  • 17895101 -- MDX. An MDX query returns #MISSING results for a dynamic member that has children with formulas.

  • 17979579 -- MDX. An MDX query returns different results for a shared member than for the results of the base member.

  • 18032431 -- MDX. An MDX query in hybrid aggregation mode fails to complete due to memory allocation error.

  • 18067758, 18075356 -- MDX. An MDX query in hybrid aggregation mode returns different results than the same query in block storage mode.

  • 18169791 -- MDX. An MDX query failed to execute in hybrid aggregation mode for function @MOVSUMX.

  • 18259444 -- MDX. An MDX query in hybrid aggregation mode returns incorrect results for a member formula due to consolidation error.

  • 17339454 -- MDX. An Essbase transparent partition source application terminates abnormally during an MDX query from the target.

  • 17951591 -- Essbase Server. An Essbase application terminates abnormally during concurrent, long-running MDX query and default calculation.

  • 18179279 -- MDX. An MDX query fails to execute in hybrid aggregation mode for a database that contains either only sparse dimensions or only dense dimensions.

  • 19724545 -- Aggregate Storage. An aggregate storage database consumes too much memory in the formula cache.

  • 17646832 -- Java API. A network error is returned while retrieving runtime substitution variables using the method cube.getCalcFileRunTimeSubVars(), when there is only one substitution variable in the script or when there is no substitution variable.

  • 17715673 -- SQL Interface. Essbase application log contains ODBC errors, even though logging of ODBC driver errors is disabled using ODBCERRORLOGOFF TRUE.

  • 17769554 -- Smart View. After zooming in and out on a grid multiple times, an error is returned: Invalid Spread Sheet data. An application protocol error might exist between server and client processes.

  • 16907883 -- Smart View. Dragging all but one dimension from POV box to the grid results in the final dimension incorrectly being moved to a row after a refresh.

  • 18023119 -- Data Load. Japanese characters are not displayed correctly in Essbase Administration Services SQL Interface.

  • 19068245 -- Data Load. In committed access mode, an Essbase data load proceeds and doesn’t abort when terminated. Hence, index and page file sizes increase after termination.

  • 18097397 -- Calculation. The following message shows intermittently in the application log during a default calculation: Total Calc Elapsed Time for [inline] : [0] seconds

  • 18126090, 19517775 -- Calculation. Improved message logging has been implemented for FIXPARALLEL calculations.

  • 19644572 -- Metadata. Essbase returns a duplicate-name error after a Smart View zoom in, instead of returning the alias.

  • 19404334 -- Aggregate Storage. Aggregate storage custom calculations or allocations fail for dynamic level-0 members with the no-consolidation operator (~).

  • 16028783 -- MDX. Essbase terminates abnormally when running an MDX query that results in an out-of-memory error.

  • 15968738 -- Essbase application terminates abnormally when performing an ad hoc analysis that results in a network time-out error.

  • 18024633 -- Localization. Certain Turkish characters load as a question mark (?).

  • 13698559 -- Smart View.Smart View does not support single member POV.

  • 13698477 -- Smart View. Smart View does not support multiple members when pivoting from POV toolbar to grid.

  • 16193657 -- Encrypting a calculation script causes some MaxL statements to be removed.

  • 16184352 -- In an active-passive cluster, Essbase and OPMN terminate abnormally.

  • 16914851 -- Calc Scripts. Opening a calc script while a security refresh is running may cause Essbase to stop responding.

  • 14513014 -- Report Writer. Running a report script containing substitution variables may fail and result in the following error:

    Substitution Variable does not exist.
  • 13408039 -- Agent. Essbase may shut down abnormally when an administrator logs off remotely.

  • 13075833 -- Administration Services. In certain non-standard EPM System installations, renaming an Essbase application from Oracle Essbase Administration Services Console may result in the following error:

    1053003 Application directory does not exist.
  • 17430484 -- Smart View. In Smart View Client, comments to the right and left of the Essbase members disappear when the sheet is refreshed.

  • 17168989 -- Smart View. Cells with comments between rows, columns and data are cleared when a sheet is refreshed in Smart View.

  • 18204427 -- Aggregate Storage. Export of aggregate storage data was failing.

  • 19553648 -- When Essbase runs on Oracle Exalytics In-memory machine, associating filters to groups runs slowly.

  • 18898415 -- Data load. Essbase is unable to load data from a load rules file that uses the dimension reference method with quotes.

  • 18327910 -- Data import. The DATAIMPORTBIN command stops importing data after encountering the first #MISSING value.

  • 16987712 -- DB2. While deploying an XOLAP cube from Essbase Studio, Essbase is unable to connect to the DB2 data source and the cube deployment fails.

  • 16091482 -- Data load. Essbase is unable to load data from a data file in which the filename has multiple dots (for example, name.withdots.txt).

  • 17326375 -- Smart View. In Smart View, unable to drill down to a linked partition.

  • 17797213, 18416709 -- Partitions. When running an MDX query on a transparent partition, the target application terminates abnormally.

  • 14571411,16993227 -- Smart View. Error encountered when retrieving data from a transparent partition: Error (1040023) Invalid network data. Type is matched but length is zero. An application protocol error might exist between server and client processes.

  • 13027168, 13830462 -- Triggers. When triggers are defined and users fix on multiple blocks, messages written to the spool file differ from the messages sent via email.

  • 13715545 -- Partitioning. Essbase Server may terminate abnormally when the @XWRITE calc function is used to update the target in a transparent partition.

  • 13941885 -- MDX. MDX queries on members containing the @ symbol may return a syntax error.

  • 13998834 -- Partitioning. Cannot create a partition using hostname:port.

  • 14098621 -- Partitioning. Replacing partition definition files may fail when Essbase is set to a Japanese locale.

  • 15844420 -- Essbase does not start because of the presence of the essbase.lck file in ARBORPATH/bin.

  • 15949711 -- MDX. Queries using the CrossJoin MDX function may take longer than expected.

  • 15956201 -- MaxL. The MaxL import data statement (aggregate storage version) may fail when using the data_string and to load_buffer options.

  • 16371237 -- Aggregate Storage. Aggregate Storage applications may terminate abnormally when doing concurrent incremental data loads.

  • 16558387 -- Import. On block storage databases, creating a dimension with more than approximately 524,000 members may fail.

  • 19346471, 19348655 -- Kernel. An application log message pertaining to restructuring is incorrect after a successful recovery.

  • 19508701 -- SQL Interface. An error message is unclear when an Oracle Call Interface (OCI) connection fails in SQL Interface.

  • 19508718 -- SQL Interface. A data retrieval using Oracle Call Interface (OCI) from SQL Interface displays only first characters of column names. Hence, unable to proceed with data load or dimension build.

  • 19508740, 19508748 -- SQL Interface. A data and column name retrieval using Oracle Call Interface (OCI) from SQL Interface displays garbled characters. Hence, unable to proceed with data load or dimension build.

  • 19508773 -- SQL Interface. A data load having Unicode characters failed via ODBC (retrieved garbled characters) from SQL Interface.

  • 18267036 -- MDX. A log message related to recursive formulas in hybrid aggregation mode references the wrong member name.

  • 19595221 -- MDX. A query using the Leaves() function fails due to a memory limitation.

  • 19658894 -- Data Export. Data export from empty outlines did not succeed. Now it succeeds and creates a 0-byte file.

  • 19911956 -- Data Export. A data file exported from a calculation script, in some cases, contains an incorrect header record.

  • 20124119 -- Smart View. High retrieval time and incorrect results occur when a queried member is a label-only parent and one of the children (other than first child) is in the partition definition.

  • 18544423 -- Misc. Wrong version information is shown in the process explorer for a .dll.

  • 18638598 -- Report Writer. Results are not optimal for a report script retrieval from an aggregate storage transparent partition target.

  • 18355797 -- Metadata. Use of the allowed member name $NULL$ returns an error message upon retrieval.

  • 18731237 -- Metadata. Outline verification succeeds in a Planning database refresh even though a member formula is invalid.

  • 19517775, 18126090 -- Calculation. Improved message logging has been implemented for FIXPARALLEL calculations.

  • 19827483 -- Data Load. Cannot cancel parallel data load initiated from ESSCMD.

  • 19943308 -- Misc. Deleting drill-through definitions might cause application to hang.

  • 20047312 -- Misc. Defunct processes are listed on a UNIX server.

  • 20124477 -- Data Export. When run inside FIXPARALLEL, DATAEXPORT with “DATAEXPORTOPTIONS { DataExportRelationalFile ON; ..}” might produce an incomplete result.

  • 18936565, 19781319 -- Metadata, Queries. Reports and calculations run too slowly with ISUDA() in a member formula.

  • 20005755 -- Metadata. Unable to view an aggregate storage outline containing long text lists.

  • 20027524 -- Calculation. A member formula error causes abnormal shutdown of an application and partial generation of .xpc file.

  • 19920209 -- Calculation. A calculation script fails with a message that the query member count is too large.

  • 18603365 -- MDX. An MDX function that receives a String as a parameter returns an error if the String parameter comes as a property value.

  • 20200253 -- Smart View. An application stops responding upon a Smart View data submission when the spreadsheet has more than 256 columns.

  • 18690087 -- MDX. Incorrect results are returned for an Accounts member with a formula and Time Balance Average tag.

  • 18742275 -- MDX. An application stops responding during a query on a two pass member parent with children that have Time Balance tags (hybrid aggregation mode enabled).

  • 18742510 -- Hybrid Aggregation. Stopping an application and removing its hybrid aggregation mode subdirectories causes the application cache_size setting to reset.

  • 19382266 -- Hybrid Aggregation. Hybrid aggregation subdirectories cause recovery implications after abnormal shutdown.

  • 19517637 -- Kernel. The Essbase Server can terminate abnormally when running concurrent requests to calculate the database as well as run queries.

  • 20124157 -- Kernel. Two new informational messages are introduced in the application log (at the start and the end of an index write):

    "Begin writing [%s] dirty index pages for database [%s]."
    "Finished writing dirty index pages for database [%s]."
  • 19177623 -- Calculation. An error is returned during a calculation using @XWRITE: "Error executing formula for [mbrName] (line 0): stack full"

  • 19627818 -- Calculation. In a subsequent FIX statement, a calculation fails on a block newly created in a prior FIX statement with @CREATEBLOCK.

  • 19830716 -- Calculation. An application terminates abnormally while running concurrent calculations and report scripts.

  • 19832532 -- Outline API. In some cases, moving a member in an outline can terminate the application abnormally.

Known Issues

The following are the noteworthy known issues of this release.

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

  • 19461502 -- Some application and database statistics may not be accurate when parallel data load, parallel calculation, or parallel restructuring are in use. In particular, diagnostic statistics (such as average clustering ratio, cache hit ratios, and data block density statistics) should not be considered accurate in environments using parallel operations.

  • 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

  • 20148540 -- Using an older client to execute an aggregation view selection on an aggregate storage database is not supported.

  • 20362903 -- Backward compatibility message is incorrect.

  • 20388529 -- Upgrading does not update the odbc.ini, essbase.cfg, opmn.xml, and odbcinst.ini files to the latest ODBC.

  • 20780452 -- When LD_LIBRARY_PATH_64 is set on Solaris 64-bit, the opmnctl start all command fails and neither the opmn service nor any other opmn controlled process starts.

    The reason for this is that the opmn.xml file configures LD_LIBRARY_PATH, and when a system has both LD_LIBRARY_PATH and LD_LIBRARY_PATH_64 defined, only the LD_LIBRARY_PATH_64 setting is used. As a result, the opmnctl command fails to load the required libraries in $ORACLE_HOME/opmn/lib.

    To avoid this, remove the definition for LD_LIBRARY_PATH_64, or add the LD_LIBRARY_PATH value from opmn.xml to the LD_LIBRARY_PATH_64 variable.

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

  • 19654043 -- If a qualified member in a duplicate-member dimension load cannot be parsed, the dimension build fails, rather than failing on the specific line where the error exists. This situation applies to the following dimension build error codes with the corresponding member name syntax errors:

    • 1060382—/* "Syntax error, expecting ']'" */

    • 1060383—/* "Syntax error, expecting '['" */

    • 1060384—/* "Syntax error, expecting '.'" */

    • 1060385—/* "Syntax error, cannot be a qualified-name */

Accessing EPM System Product Documentation

Find the latest Oracle Enterprise Performance Management 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.

Removing Users with Filter Access

If a user has filter access provisioned in Oracle Hyperion Shared Services and you want to remove the user, you must first remove the user from Oracle Hyperion Shared Services, and then remove the user from the Essbase security file using the MaxL “drop user” command. (21782308)

Migrating an Aggregate Storage Application Clears All Aggregate Views

When an aggregate storage application is migrated to the current Essbase release, all aggregate views are cleared.

Aggregate Storage Databases Support Query Logging

In the Oracle Essbase Database Administrator's Guide, the table entitled, “Query Differences Between Aggregate Storage and Block Storage”, incorrectly states that query logging is not supported for aggregate storage databases. Query logging is available for block storage and aggregate storage databases, as stated in the “Implementing Query Logs” topic. (20596590)

MDX calculated members

MDX calculated members are not supported in Hybrid Aggregation mode in Release 11.1.2.4.000. (21490424)

Corrected BI Server Connection Information

In the Oracle Essbase SQL Interface Guide, in the topic, “Keywords and Values Used Within Configuration Files”, the example of an esssql.cfg file with connection information for Oracle BI Server is incorrect. (19607434)

The following is the correct information:

[
Description "Oracle BI Server"
DriverName libnqsodbc
UpperCaseConnection 0
UserId 1
Password 1
Database 1
SingleConnection 0 
IsQEDriver 0 
ConvertUTF16toUTF8 1
]

New C Outline API Function for Upgrading Aggregate Storage Outline

The following C Outline API function was added in Release 11.1.2.4.000, but was not documented.

ESS_FUNC_M EssOtlSetOPGVersion(ESS_HOUTLINE_T hOutline,
                               ESS_INT32_T iOPGVersion)

This function upgrades the version of the aggregate storage outline to the specified OPG version, enabling the new aggregate storage features for that release.

The value to use for iOPGVersion is:

ESS_MOPG_VERSION_LATEST—Latest OPG version. For 11.1.2.4.000, this enables XML outline editing. (20397415)

Troubleshooting: Unable to Request Server Thread

With the introduction of thread pool for parallel operations, increased resources are needed to start an Essbase application. If you encounter the error 'Unable to Request Server Thread' during startup, adjust the operating system settings that control the number of threads per process and the total number of threads in the system (for example, on Linux, tune nproc using ulimit). (20440094)

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)

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

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 11.1.2.4:

  • 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 Smart View:

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)

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.

Topics that include incorrect information:

  • Data Source Differences for Aggregate Storage Dimension Builds” topic—The ^ consolidation operator is incorrectly included in the “Consolidation Codes for Members of Aggregate Storage Outlines” table.

  • Outline Factors Affecting Data Values” topic—The ^ consolidation operator is incorrectly listed as supported for dynamic hierarchies in aggregate storage databases.

(19376666, 19131994)

MDX Functions Are Not Supported in Custom Calculation Scripts

In the Oracle Essbase Database Administrator's Guide topic entitled “Writing Custom Calculations”, the following statement appears:

The use of member functions is not supported for custom calculation scripts.

The correct statement should be:

The use of any MDX functions is not supported for custom calculation scripts.

(23239352)

Permission Required to Rename an Application

In the Oracle Essbase Technical Reference, the MaxL topic for Alter Application states that Application Manager permission is required to use the set of statements within Alter Application.

Correction: To rename an application, you must have Create/drop application privilege. (22456868)

Changes in Server Shutdown

Issuing a MaxL statement to unload an application cancels all active requests and database connections, and stops the application, unless you explicitly specify otherwise using the no_force option.

Updated MaxL Syntax

alter system unload application {all|APP-NAME} [no_force];
KeywordDescription
no_forceOptional keyword. Causes Essbase to return an error if active requests are running on the application.

Examples

The following terminates all active requests and stops all applications:

alter system unload application all;

The following stops all running applications (as the above statement does) and shuts down Oracle Essbase Server:

alter system shutdown;

The following prepares to unload application Sample; however, if active requests are running, an error is returned.

alter system unload application Sample no_force;

(22385118)

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.