Oracle® Essbase

Readme

Release 11.1.2.2.100


Copyright © 2012, 2014, Oracle and/or its affiliates. All rights reserved.

Updated: July 2014

Authors: EPM Information Development Team

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.

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

This software or hardware and documentation may provide access to or information on 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. 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.


Table of Contents:

Purpose

New Features

Installation Information

Supported Platforms

Supported Languages

Supported Paths to this Release

Defects Fixed in this Release

Defects Fixed in Release 11.1.2.2.000

Known Issues

Documentation Updates

Accessibility Considerations

Purpose

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

New Features

See the Oracle Essbase New Features. For new features relating to installation, architecture, and deployment changes in this release, sees "New Features" in the Oracle Enterprise Performance Management System Installation and Configuration Readme.

Installation Information

Late-breaking information about installation of Oracle Enterprise Performance Management 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 a 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 the 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 a 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.2 from the following releases:

Note:

For instructions to upgrade, see the Oracle Enterprise Performance Management System Installation and Configuration Guide, "Upgrading EPM System Products."

Table 1. Supported Paths to this Release

Release Upgrade Path FromTo

11.1.2.x

11.1.2.2

Note:

When moving from Release 11.1.2.0.x or 11.1.2.1.x to Release 11.1.2.2, you use the "Apply Maintenance Release" option in Oracle Hyperion Enterprise Performance Management System Installer, instead of following the documented upgrade procedures.

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

11.1.1.3.x

11.1.2.2

11.1.1.4.x

11.1.2.2

9.3.3.x

Note:

If you were using Oracle Hyperion EPM Architect Release 9.3.1, you can download the Oracle Hyperion Shared Services release 9.3.3 from My Oracle Support.

11.1.2.2

A release earlier than Release 9.3.3.x

If you are upgrading from a release earlier than 9.3.3.x, you must first upgrade to a supported release and then upgrade to release 11.1.2.2. For upgrade procedures for the earlier release, see the product installation guides for the interim release that you are upgrading to.

An environment that includes multiple releases, which can include an environment with one instance of 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 upgrade to Release 11.1.1.3 as your interim release. 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, instead of Release 11.1.1.3.

Recommendation:

When upgrading to a version of Essbase in which you use the EPM 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.

Defects Fixed in this Release

If you are upgrading from Release 11.1.2.0 or 11.1.2.1, use the Defects Fixed Finder tool to review the list of defects fixed between those releases and Release 11.1.2.2. This tool is available at:

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

  • 12642553 — MDX. When users attempt to query data to which they have no access, the Essbase server shuts down abnormally.

  • 9307062 — Aggregate Storage. Data retrievals that contain member name comparison formulas cause the application to terminate abnormally.

    Workaround: Modify the formulas to use comparisons of the form IS(CurrentMember(dim),[Member_Name]). This change also enables formulas to execute faster, as comparison of members is faster than member name comparison.

  • 12796353 — Aggregate Storage. MDX formula calculation on an aggregate storage database returns incorrect results when a formula on a member has a cross-dimensional reference which does not include a reference to a member from the dimension in which the formula member is present.

  • 12362301 — Aggregate Storage. Essbase uses too much memory (800 MB) when reading a very long (1 MB) MDX region expression. Commands that use an MDX region expression include MaxL queries and partial data clears on aggregate storage databases.

  • 12648910 — MaxL Perl Module. When running a Perl script that fetches a large number of rows, the session terminates. The MaxL Perl function fetch_row() is now improved and can process 65,535,000 rows.

  • 12965630 — Partitioning. Essbase does not support a query with attributes that extracts Dynamic Time Series members through transparent partitions, with the TARGETTIMESERIESOPT setting in Essbase.cfg.

  • 13341230 — Spreadsheet Add-in. In Oracle Essbase Spreadsheet Add-in for Excel 2010, the Browse button does not function, and the spreadsheet has to be saved with a manual path entry.

  • 12879367 — MaxL. The display partition advanced MaxL statement takes much longer than expected to display the partitions.

  • 13072924 — MDX. On Aggregate storage databases, when the cell status option is set to on, Essbase Server may terminate abnormally when running MDX queries that use the Leaves function through Smart View or Java API.

  • 13506517 — Dimension Build. Intermittently, dimension builds may return the following error and terminate the Essbase Server process (ESSSVR):

    fatal flex scanner internal error--end of buffer missed.

  • 13012815 — Dimension Build. Following a dimension build from Teradata with SQL Interface, the restructure fails with the following error:

    fatal flex scanner internal error--end of buffer missed.
  • 13627655 — Dimension Build. Upon failure of a large block-storage dimension build, Essbase and Oracle Essbase Administration Services shut down abnormally.

    New error message:

    Error code 1060356 The combined size of base dimension [%s] and attribute dimension [%s] exceeds current essbase limitations. To reduce the combined size of these dimensions, you can remove members, add alternate hierarchies, or use User-Defined Attributes (UDAs)
  • 13113956 — Aggregate Storage. Sending data from an Excel sheet to an aggregate storage database fails if the sheet contains both the member names and aliases.

  • 13572695 — Aggregate Storage. An aggregate storage member formula does not validate when a member name in the formula includes a dollar sign ($). Note: In formulas, member names starting with $ or & should be enclosed in quotation marks and brackets. For example, a formula referring to $testmember could be expressed: ["$testmember"]/100

  • 13086035 — Calculation. When using @ilancestors (@list for a calculation and the number of members in the result is greater than ten, the calculation fails with the following error:

    1012004 Invalid member name [@LIST].
  • 13370201 — Outline. When outlines are converted from block storage to aggregate storage, some of the consolidation properties of members may be changed and some member formulas may be removed.

  • 12576894 — API. Client applications may terminate abnormally when using the ESSGDTCONNECT C API function on databases created in Oracle Essbase Studio.

  • 12875766 — API. When an alias table is selected, the Essbase grid dimension metadata that is returned does not match the metadata in the alias table.

  • 12949163 — API. With TARGETTIMESERIESOPT set to True, EssOtlQueryMembersEx returns information for more members than expected.

  • 9758528 — MaxL. Alias names are abnormally truncated in the maxl.log file when the MaxL Shell (essmsh) is running in multi-byte (UTF-8) mode.

  • 12898890 — Partitioning. During block storage to aggregate storage transparent partitioning, the ENABLE_DIAG_TRANSPARENT_PARTITION configuration setting does not send the appropriate partition related messages to the application source and target log files.

  • 8836913 — Partitioning. Performance issues may occur when retrieving large amounts of data on transparent partitions with block storage sources and aggregate storage targets.

  • 13006588 — MaxL. Under Solaris 9 and 10 (also known as Solaris 2.9 and 2.10, or Solaris 5.9 and 5.10, respectively), encrypting a MaxL script that contains a create replicated partition MaxL statement may result in a segmentation fault error.

  • 13724689 — MaxL. The MaxL statement export outline does not include member solve orders in the resultant XML file of an exported aggregate storage database outline.

  • 12387447 — Unicode. In a Unicode Essbase application, if you have Russian-character text strings in an alias table, they may not print correctly in reports.

  • 8205953 — Calculation. When ESSLANG is set to Turkish_Turkey.ISO-8859-9@Turkish, calculation function names containing a lowercase "i" may cause a syntax error in the Calc Script Editor on validation.

  • 13388938 — Calculation. A retrieval of sparse, Dynamic Calc attribute members takes too long to complete.

  • 12947489 — Calculation. Using the calculation function @XWRITE in a calculation script with the @LOOPBACK keyword causes Essbase to stop responding and return a network error.

  • 12371965 — When a transparent partition from a block storage database to an aggregate storage database contains overlapping partitions, the values in the overlapping areas are aggregated incorrectly.

  • 13699262 — Filters. Essbase Studio Drill Through returns the following error when security filters are set:

    Unknown error: Not a valid entry
  • 13623101 — Filters. A dimension containing a filter set to metaread access cannot be expanded in Oracle Hyperion Interactive Reporting when selecting members by generation name or by level name.

  • 13385921 — Perl Module. On 64-bit Solaris, the Essbase Perl Module compiles, but the messages returned from the client via the Perl Module are truncated.

  • 12866455 — Data Load. A large parallel data load from a SQL source to an aggregate storage database errors out due to time-out, but the load buffers are not destroyed after errors.

  • 13627284 — Data Load. Following a data load, the application log shows the number of cells updated in scientific notation format instead of as a regular number.

Defects Fixed in Release 11.1.2.2.000

  • 13008515 — Essbase Agent. Under some conditions, an agent deadlock occurs when invoking the ListObjects call.

  • 11668895 — Block Storage. Execution of calculation script, in which @ISDESC calculation function calls for nonexistent members in the database, abnormally terminates the block storage application.

  • 12904542 — Calculator. A large number of FIX blocks in a calculation script caused the server to terminate abnormally.

  • 13017954 — Aggregate Storage. Aggregate storage application doesn’t start when the MDXLIMITFORMULARECURSION configuration setting is set to FALSE.

  • 13073851 — Essbase Agent. Under some conditions, the agent crashes because of memory corruption, which is also related to ListObjects call.

  • 9893023 — Calculator. Calculation times are inconsistent on fragmented databases.

  • 12774338 — Essbase Error. “Internal MDX API error: invalid cluster offsets.”

  • 11843851 — MDX. Basic functions used to access member properties do not return expected results on members with implicit shares and on members of dynamic hierarchies.

  • 12559940 — Essbase Agent. The Agent hangs when outline restructure and query execute simultaneously.

  • 11738323 — ESSPERL. Perl output is different on Essbase running on 64-bit Linux.

  • 10222309 — Spreadsheet Add-in. If Spreadsheet Add-in is installed, attempting to insert an Excel spreadsheet into a Microsoft PowerPoint document will fail, and may cause Excel to terminate abnormally.

  • 13005924 — Essbase Server. An email is sent or a spool file created when trigger conditions are not met.

  • 10317904 — Essbase Agent. Users who have been granted access as Database Manager cannot perform dimension build.

  • 12890247 — Aggregate Storage. CALCLOCKBLOCK configuration setting effects aggregate storage applications.

  • 12665494 — Spreadsheet Add-in. When an EPM client (such as Spreadsheet Add-in) is used with an Oracle client (such as Oracle ODBC) that is version 11.2.0.1, there is a path conflict wherein if the Oracle client path is specified first in the PATH system variable, the EPM client cannot be started.

  • 12857741 — Administration Services. When viewing active Essbase Server sessions in Administration Services Console, incorrect connect IP is shown.

  • 11679774 — API. Declaring variables in the incorrect order causes an error.

  • 11692298 — LROs. During an upgrade, LROs are not migrated.

  • 12860438 — API. Update version of esb32.bas file.

  • 11663343 — Administration Services. When Essbase is in Essbase native security mode, the Create/Delete Users and Groups permission in Administration Services Console does not work correctly.

  • 13252949 — Transparent Partition. Unable to view Dynamic Calc data retrieved through a transparent partition.

  • 13011030 — Dimension Build. After applying Essbase patch PSE 11.1.2.1.000_12861079, dimension build using OCI connection fails, if the data source has NULL values.

  • 12579538 — Transparent Partition. In a database with transparent partitions, if the TARGETTIMESERIESOPT parameter is not set in essbase.cfg, the D-T-S calculation will not execute on the source database, and the target database will display incorrect results.

Known Issues

The following issues are the noteworthy known issues of this release.

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

  • 12781588, 13574192 , 13781141 — Upgrade. Upgrading from Essbase 11.1.1.3.500 to 11.1.2.2.100 fails if ARBORPATH exceeds 60 characters.

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

  • 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

  • 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 Essbase 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 Oracle Hyperion 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.

  • Data Mining. In Essbase and Administration Services, Data Mining is no longer enabled by default. Documentation regarding Data Mining has been removed from the Essbase and Oracle Essbase Administration Services documentation set. Data Mining may be completely removed in a future release of Essbase. For Data Mining functionality, please consider Oracle Data Mining, which is an option in Oracle Database Enterprise Edition.

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

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

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

    For information on obtaining the AIX 5.3 kernel extensions update on Oracle OTN, see Applying AIX 5.3 Kernel Extensions Update.

  • 11684239 — Translation. For the Turkish translation of Spreadsheet Add-in, items do not display correctly in combination box drop-down lists.

    Workaround: Use the arrow keys to make items available and to move up and down the list.

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

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

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

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

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

    Note:

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

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 Web site (http://www.oracle.com/technology/documentation/epm.html). You can also use the EPM 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 Web site (http://edelivery.oracle.com/EPD/WelcomePage/get_form).

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

Configuring Teradata as a Data Source

This topic replaces the topic named “Establishing a Connection to a Teradata Database when Using Essbase with OPMN” that appeared in a previous version of this Readme.

To configure Teradata as a data source:

  1. Install Teradata drivers, which you must obtain from Teradata.

    • Essbase Studio uses JDBC drivers. The JDBC Teradata driver must be installed on the computer on which Essbase Studio Server runs.

      Essbase Studio uses the JDBC Teradata driver to deploy cubes in streaming mode.

      To deploy cubes in non-streaming mode, the ODBC Teradata driver must be installed on the computer on which Essbase Server runs.

    • Essbase uses ODBC drivers. The ODBC Teradata driver must be installed on the computer on which Essbase Server runs.

  2. Stop Essbase from the Windows Services panel using the Oracle Process Manager and Notification Server (OPMN) service: EPM_epmsystem1.

  3. Backup the OPMN configuration file (opmn.xml).

    For example:

    C:\Oracle\Middleware\user_projects\epmsystem1\config\OPMN\opmn\opmn.xml
  4. Open the opmn.xml file in a text editor.

  5. To properly load the Teradata drivers, the opmn.xml file must include a statement that points to the location of the Teradata libraries.

    1. Locate the following statement in the opmn.xml file:

      <variable id="ESS_CSS_JVM_OPTION7" value="-Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration"/>
    2. After this statement, add a statement similar to the following one:

      <variable append="true" id="PATH" value="C:\Program Files\Teradata\Client\14.00\Shared ICU Libraries for Teradata\lib"/>
  6. When using Teradata data sources with Essbase, and using OPMN to monitor and control the Essbase Agent process, you must update the opmn.xml file with variables for the operating system you are using.

    Note:

    The absolute path value cannot contain spaces. The examples of absolute path values are based on a 64-bit machine configuration.

    64-bit Windows

    Add these variables:

    • TWB_ROOT: Teradata root

    • PATH: Teradata shared libraries

    • PATH: Teradata client DLL libraries

    • PATH: Teradata Call-Level Interface Version 2 routines

    • PATH: Teradata message DLL libraries

    64-bit Windows example:

    <variable id="TWB_ROOT" value="C:\PROGRA~1\Teradata\Client\14.00"/>
    <variable append="true" id="PATH" value="C:\PROGRA~1\Teradata\Client\14.00\SHARED~1\lib"/>
    <variable append="true" id="PATH" value="C:\PROGRA~1\Teradata\Client\14.00\TERADA~1\bin64"/>
    <variable append="true" id="PATH" value="C:\PROGRA~1\Teradata\Client\14.00\CLIv2"/>
    <variable append="true" id="PATH" value="C:\PROGRA~1\Teradata\Client\14.00\TERADA~1\msg64"/>

    64-bit AIX

    Add these variables:

    • LIBPATH: Teradata ODBC libraries

    • LIBPATH: Teradata shared libraries

    • LIBPATH: ODBC components needed to load Teradata ODBC drivers

    • LIBPATH: Teradata client libraries

    • COPERR: Directory where the errmsg.txt file resides

    • NLSPATH: Teradata message libraries

    64-bit AIX example:

    <variable append="true" id="LIBPATH" value="/opt/teradata/client/ODBC_64/lib"/>
    <variable append="true" id="LIBPATH" value="/opt/teradata/client/13.10/tdicu/lib64"/>
    <variable append="true" id="LIBPATH" value="/usr/odbc/lib:/usr/odbc/drivers"/>
    <variable append="true" id="LIBPATH" value="/usr/lib:/usr/teragss/aix-power/client/lib"/>
    <variable id=" COPERR" value="/usr/libperion/essbase"/>
    <variable id="NLSPATH" value="/opt/teradata/client/13.10/odbc_32/msg/%N"/>
    <variable append="true" id="NLSPATH" value="/usr/lib/nls/msg/%L/%N"/>
    <variable append="true" id="NLSPATH" value="/usr/lib/nls/msg/%L/%N.cat"/>

    64-bit LINUX

    Add these variables:

    • TWB_ROOT: Teradata root

    • TD_ICU_DATA: Teradata shared libraries

    • NLSPATH: Teradata ODBC message libraries

    • COPERR: Directory where the errmsg.txt file resides

    • COPLIB: Directory where the libcliv2.so library file resides

    • LD_LIBRARY_PATH: Teradata libraries

    • PATH: Teradata client directories

    Note:

    The errmsg.txt and libcliv2.so files typically reside in the same directory. Therefore, the value for the COPERR and COPLIB variables is typically identical.

    64-bit LINUX example:

    <variable id="TWB_ROOT" value="/opt/teradata/client/13.10/tbuild"/>
    <variable id="TD_ICU_DATA" value="</opt/teradata/client/13.10/tdicu/lib64>"/>
    <variable id="NLSPATH" value="</opt/teradata/client/13.10/odbc_64/msg/%N >"/>
    <variable append=true id=NLSPATH value=/opt/teradata/client/13.10/tbuild/msg64/%N/>
    <variable id="COPERR" value="/usr/lib64"/>
    <variable id="COPLIB" value="/usr/lib64"/>
    <variable append=true id=LD_LIBRARY_PATH value=/opt/teradata/client/13.10/tbuild/lib64/>
    <variable append=true id=LD_LIBRARY_PATH value=/usr/lib64/>
    <variable append=true id=PATH value=/opt/teradata/client/13.10/tbuild/bin/>
    <variable append=true id=PATH value=/opt/teradata/client/13.10/tbuild/lib64/>
  7. Save the opmn.xml file.

  8. Start Essbase from the Windows Services panel using the OPMN service (EPM_epmsystem1).

  9. Verify the following:

    • Essbase: Use the Data Prep Editor in Administration Services Console to connect to a Teradata database using a DNS.

    • Oracle Essbase Studio: Perform a cube deployment in non-streaming mode, which uses the Teradata ODBC driver.

Copying an Aggregate Storage Application

To copy all of the data in an aggregate storage application, you must merge all incremental data slices into the main database slice. Data in unmerged incremental data slices is not copied.

Index Cache Size

The following information updates the index cache size information in the Essbase 11.1.2.2.100 documentation:

  • Minimum value: 1

  • Maximum values:

    • 32-bit Essbase: 4 GB

    • 64-bit Essbase: 256 TB

  • Default values:

    • Buffered I/O: 1 MB

    • Direct I/O: 10 MB

The minimum and maximum values apply to buffered and direct I/O.

32-bit and 64-bit Red Hat Linux Support for Teradata Data Sources

The following information updates the Red Hat Linux information in the “Using Teradata Data Sources” topic in the Oracle Essbase SQL Interface Guide:

Essbase supports Teradata Parallel Transporter (TPT) 12 with the Teradata 12 ODBC driver on 32-bit and 64-bit Red Hat Linux platforms.

Applying AIX 5.3 Kernel Extensions Update

See the description of defect 13404757 in the "Known Issues" section of this Readme.

If you have installed Oracle Database 11g Release 2 (11.2.0.1.0), the AIX 5.3 kernel extensions update file (rootpre.sh) is included. Or you can obtain the file from the Oracle Software Delivery Cloud site.

To apply the AIX 5.3 kernel extensions update:

  1. Log into Oracle Software Delivery Cloud at:

    https://edelivery.oracle.com/

  2. On the “Media Pack Search” page, enter the following information:

    • For Select a Product Pack, select Oracle Database.

    • For Platform, select IBM AIX on POWER Systems (64-bit).

  3. Click Go.

  4. In the results list, select Oracle® Database 11g Release 2 (11.2.0.1.0) Media Pack for IBM AIX on POWER Systems (64-bit), and then click Continue.

  5. On the “Oracle® Database 11g Release 2 (11.2.0.1.0) Media Pack for IBM AIX on POWER Systems (64-bit)” page, click Download next to Oracle Database 11g Release 2 (11.2.0.1.0) for IBM AIX on POWER Systems (64-bit) (Part 1 of 2).

  6. Unarchive the download file.

  7. Run the rootpre.sh file on the computers on which Essbase Server and Essbase client are installed.

Starting Essbase Server in the Foreground is Not Supported

Starting Essbase Server in the foreground is no longer supported. Documentation about starting Essbase Server in the foreground should be ignored.

During installation, Oracle Hyperion Enterprise Performance Management System Installer installs OPMN and registers Essbase Server for OPMN. OPMN manages the Essbase Agent, which manages Essbase Server.

Essbase Server start and stop scripts, which are located in the EPM_ORACLE_INSTANCE/bin directory, redirect to Oracle Process Manager and Notification Server:

  • Windows: startEssbase.bat and stopEssbase.bat

  • UNIX: startEssbase.sh and stopEssbase.sh

Changing Implied Share Settings

The following steps must be performed any time the IMPLIED_SHARE setting is changed in essbase.cfg:

  1. Change the IMPLIED_SHARE setting in essbase.cfg.

  2. Restart Essbase Server.

  3. Create a new application and database, with the IMPLIED_SHARE setting in place.

  4. Rebuild the outline, with the IMPLIED_SHARE setting in place.

  5. Reload the data.

  6. Run aggregation or calculation scripts.

  7. Restart the application.

Authentication when Using SQL Interface with Microsoft SQL Server

When using SQL Interface with Microsoft SQL Server as a data source, only SQL Server Authentication (in which the SQL Server username and password is provided) is supported. Windows Authentication for SQL Server is not supported.

CLASSPATH Information

For diagnostic and informational purposes, Essbase prints the value of the CLASSPATH environment variable to the Agent console during JVM initialization.

Configuration Setting for Running Essbase Server on Oracle Exalytics

When running Essbase Server on the Oracle Exalytics In-Memory machine, set the following configuration setting in the essbase.cfg file:

OracleHardwareAcceleration TRUE

The OracleHardwareAcceleration configuration setting applies to Exalytics only; it is not supported and should not be used in other deployments.

SECFILEBACKUPINTERVAL Configuration Setting

The SECFILEBACKUPINTERVAL configuration setting topic in the Oracle Essbase Technical Reference incorrectly states the description of the n argument. The following information is correct:

SECFILEBACKUPINTERVAL n

n—Specifies the amount of time in seconds.

The default value is 300 seconds (which is five minutes). A value of 0 means that the essbase.sec file will not be backed up. Other than 0, the value cannot be less than 300.

AGENTTHREADS Configuration Setting

The following description of the AGENTTHREADS configuration setting is more accurate than the topic in the Oracle Essbase Technical Reference.

AGENTTHREADS

Specifies the maximum number of threads that the Agent process (ESSBASE) can spawn. Agent threads are used for logging in and out of Essbase Server, starting and stopping an application, etc.

One agent thread is used in conjunction with a thread spawned by the AGTSVRCONNECTIONS configuration setting to allow the initial login through the Agent and to establish the first connection to an application and database. When a connection is requested, the Agent assigns a thread to the request and releases the thread when the connection is made.

The rest of the agent threads are used for other Agent tasks unrelated to AGTSVRCONNECTIONS. Once connected, AGTSVRCONNECTIONS threads are no longer used. Client requests are managed by threads spawned by the application process (ESSSVR).

Syntax

AGENTTHREADS n

n: Specifies the number of threads that the Agent process (ESSBASE) can spawn.

  • 32-bit platform: 2 to 500, inclusive

  • 64-bit platform: 2 and 1024, inclusive

The default value is 5.

Notes

  • Oracle strongly recommends that you use the default value when running Essbase on a 32-bit platform.

  • While the actual maximum value you can set is 500 (32-bit platform) or 1024 (64-bit platform), the maximum number of threads an operating system can handle might be much lower. Before specifying a value greater than the default value, check with your system administrator, as higher values can significantly consume system resources.

  • If you specify a number less than 2, over the maximum, or a decimal value, Essbase overrides the value with a closely approximate value of its own.

  • One thread is required for each initial connection to an application and database.

Example

AGENTTHREADS 15

AGTSVRCONNECTIONS Configuration Setting

The following description of the AGTSVRCONNECTIONS configuration setting is more accurate than the topic in the Oracle Essbase Technical Reference.

AGTSVRCONNECTIONS

Specifies the maximum number of threads that Essbase can spawn to allow the first connection to an application and database, negotiated between the Agent process (ESSBASE) and application process (ESSSVR). AGTSVRCONNECTIONS threads make the Agent process (ESSBASE) communicate with the application process (ESSSVR).

Each AGTSVRCONNECTIONS thread uses one Agent process (ESSBASE) thread only while logging in and connecting to an application and database. Once connected, client requests are managed by threads spawned by the application process (ESSSVR).

Syntax

AGTSVRCONNECTIONS n

n: Specifies the maximum number of AGTSVRCONNECTIONS threads that Essbase can spawn.

  • Default value: 5

  • Minimum value: 1

Caution!

Oracle recommends a maximum value of 10.

Notes

  • Make sure you have enough open file descriptors configured in the operating system to accommodate the value you set for AGTSVRCONNECTIONS.

  • Consider specifying a value greater than the default value, if you are expecting a large number of users to login and select the same application within a short period of time.

Example

AGTSVRCONNECTIONS 7

Sets the maximum number of AGTSVRCONNECTIONS threads that Essbase can spawn to 7.

SERVERTHREADS Configuration Setting

The following description of the SERVERTHREADS configuration setting is more accurate than the topic in the Oracle Essbase Technical Reference.

SERVERTHREADS

Overrides the default value of the number of threads that the application process (ESSSVR) can spawn. Application threads are used in calculations, client requires, administrative activities, etc.

When a transaction is requested, the application process (ESSSVR) assigns a thread to the transaction and releases the thread when the transaction is completed.

Syntax

SERVERTHREADS [appname] n
  • appname—Optional. Specifies an application; the SERVERTHREADS setting applies to all databases within the named application.

    If you do not specify an application, the setting applies to all applications and databases on Essbase Server.

  • n—Specifies the number of threads that the application process (ESSSVR) can spawn.

    • 32-bit platform: 20 to 500, inclusive

    • 64-bit platform: 20 to 1024, inclusive

    The default value is 20.

    If you specify a value that is:

    • Less than the minimum, Essbase interprets the value as 20

    • Greater than the maximum, Essbase interprets the value as 500 (32-bit platform) or 1024 (64-bit platform)

Notes

  • While the actual maximum value you can set is 500 (32-bit platform) or 1024 (64-bit platform), the maximum number of threads an operating system can handle might be much lower. Before specifying a value greater than the default value, check with your system administrator, as higher values can significantly consume system resources.

  • If the computer on which Essbase Server runs freezes while running multiple reports simultaneously, increase the value of SERVERTHREADS by one for each report you run.

  • Each application thread may create child threads for tasks such as parallel calculation, parallel data load or export, and parallel restructuring. If the total number of running threads is too high, threads may lose efficiency in contending for server resources. To manage thread contention, use the MAXTOTALACTIVETRANSACTIONS and MAXACTIVEUPDATETRANSACTIONS settings.

Example

SERVERTHREADS 25

Allows all applications on Essbase Server to spawn up to 25 threads.

SERVERTHREADS Sample 100

Allows the Sample application on Essbase Server to spawn up to 100 threads.

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.

Configuring Parallel SQL Connections for Essbase SQL Interface

(17867745) 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 Oracle 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
    ]

AGTMAXLOGFILESIZE and APPMAXLOGFILESIZE Configuration Setting Examples

(17932470, 17938478) 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.

Accessibility Considerations

It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community. Oracle's Oracle Essbase Spreadsheet Add-in supports accessibility features, which are described in Appendix E in the Oracle Essbase Spreadsheet Add-in User's Guide. The most up-to-date version of this guide can be found in the Oracle Enterprise Performance Management System Documentation Library on the Oracle Technology Network (http://www.oracle.com/technology/documentation/epm.html).

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