Oracle® Essbase

Release Patch Set 1 (PS1):


Purpose. 1

New Features. 1

Installation Information. 2

Essbase Failover Clusters Required Post-Installation Patch. 2

Performance Management Architect Required Post-Installation Patch. 2

Supported Platforms. 2

Supported Languages. 3

Supported Paths to this Release. 3

Defects Fixed in this Release. 4

Defects Fixed in Release 9

Known Issues. 11

Tips and Troubleshooting. 17

Re-hosting Essbase Using Failover Clustering. 17

Documentation Updates. 17

Accessing EPM System Product Documentation. 17

Copying and Pasting Code Snippets from PDFs. 18

Deprecated Essbase.cfg Configuration Settings. 18

Starting Administration Services Console. 18

SQL Interface Guide Corrections. 18

Applying AIX 5.3 Kernel Extensions Update. 19

Establishing a Connection to a Teradata Database when Using Essbase with OPMN. 19

Accessibility Considerations. 20



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

Top of Document

New Features

See the Oracle Essbase New Features.

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

Top of Document

Installation Information

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

Essbase Failover Clusters Required Post-Installation Patch

After configuring Essbase failover clusters, you must install an OPMN patch before starting any services. Failure to install this patch prior to starting services may result in the following situations:

·        Configured OPMN service-failover processes may fail to restart if they unexpectedly terminate even when restart-on-death is set to true in opmn.xml.

·        High availability does not work if you do anything that causes opmn.xml to be reread; for example, if you are instructed by Oracle Technical Support to turn on OPMN debug.

·        On Windows x64, if you stop OPMN on the active node, the passive node may terminate abnormally.

These are the patch locations on the Oracle Automated Release Updates Web site:

Note: On the Oracle Automated Release Updates Web page, “FMW" refers to Fusion Middleware release, which the OPMN patches are from, and not the Essbase release number.

·        Linux32

·        Win32

·        Linux x64

·        Win x64

·        Solris64

·        AIX64

·        hpux ia64

Performance Management Architect Required Post-Installation Patch

If you use Essbase with Oracle Hyperion EPM Architect, Fusion Edition, after the installation and configuration of Performance Management Architect, you must install Performance Management Architect patch 11804477.

Top of Document

Supported Platforms

Information about system requirements and supported platforms for EPM System products is available in a spreadsheet format in the Oracle Hyperion 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) and listed in the Oracle Business Intelligence product area:

Top of Document

Supported Languages

Information about supported languages for EPM System products is available in a spreadsheet format on the Translation Support tab in the Oracle Hyperion Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on OTN (listed in the Oracle Business Intelligence product area):

Top of Document

Supported Paths to this Release

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

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

Release Upgrade Path From


Note that when moving from Release to Release, you use the "Apply Maintenance Release" option in EPM System Installer, instead of following the documented upgrade procedures.


Note: If you were using Performance Management Architect Release 9.3.1, you can download the Performance Management Architect Release 9.3.3 from My Oracle Support.


A release earlier than Release 9.2.1.x

If you are upgrading from a release earlier than 9.2.1.x, you must first upgrade to a supported release and then upgrade to release 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 Hyperion Shared Services or an environment with two instances of Shared Services

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


Note: If you are starting from Release, 9.3.0.x, 9.3.1.x (except for Essbase,,, and, or 11.1.1.x, Oracle recommends that you upgrade to Release 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 Essbase and Shared Services Release, however, still synchronize security information. For this reason, if you are using Essbase Release,,, or, you must first upgrade all products to Release 9.3.3, instead of Release

Top of Document

Defects Fixed in this Release

Defect Number

Defect Fixed

• 7033834

Calculator. When data is exported from Essbase to a relational database, DATAEXPORT produces an error if a dimension member name contains single quotation marks.

• 7225100

MaxL. The iferror command does not function with the alter system shutdown command, causing the system to continue processing without errors being detected.


Data Mining. In Shared Services mode, if you do not specify a password for Essbase in Oracle Essbase Administration Services User Properties, when you run data mining tasks through the Data Mining wizard, error messages are displayed. If you specify a password for Essbase Server and restart Administration Services Console, the mining tasks run successfully.

• 7278577

Calculator. During calculations, applications may intermittently terminate abnormally.

• 7323349

Server Administration. In DATAEXPORT operations, null values are displayed as -.000000000000002 instead of NULL.

• 9096888

High Availability. ODL logging is not supported in Essbase High Availability.

• 9114777

High Availability. The ESSBASEFAILOVERTRACELEVEL setting in essbase.cfg does not function, causing essbase.log to continually increase in size.

• 9182301

High Availability. If you use Essbase failover clusters, you cannot use XREF or partitioning.

• 9238490

Client API. The ESSGETLOGFILE and ESSGETLOGFILEEX are not recording file encoding information.

• 9318086

High Availability. OPMN incorrectly allows a second Essbase instance in a clustered environment to start while the first Essbase instance is running. The correct behavior is for OPMN to only allow one of the Essbase instances to run at any given time.

• 9374215

MDX. MDX queries that reference a UDA with a single quote mark inside a calculated member do not return the expected results.

• 9394420

Agent. Essbase corrupts security file when it is terminated with Kill-9 parameter.

• 9432132

SQL Interface. A SQL data load fails on Linux because the data is encoded UTF-16 when Essbase expected UTF-8 encoding.

• 9464277

Spreadsheet Add-in. Excel 2007 crashes when Spreadsheet Add-in is enabled and a data source is selected after a chart or graph is inserted.

• 9492720

Server Administration. The error log file is not generated for deployment to Essbase on HP-UX platform.

• 9506984

Spreadsheet Add-in. While using Spreadsheet Add-in, selecting a range of cells for a drill-through report results in only the data from the first cell being displayed in the report.

• 9507912

High Availability. Application names in Essbase failover clusters cannot contain multibyte characters.

• 9523818

MaxL. Using the MaxL deploy command to check error level status always reports success (errorlevel 0), even when the deploy command was not successful.

• 9535258

API. The command EssGetObjectInfo() returns the incorrect file size for files whose size is greater than 4 gigabytes.

• 9553601

High Availability. Essbase Agent hangs after the server is shut down even though logs indicate a proper shutdown of the Agent.

• 9571830

Batch Clients. The commands to get and put objects (qPartialDataClear, qPutObject3, and qGetObject3) do not support all object types.

• 9572664

SQL Interface. SQL interface fails to work when using Oracle Call Interface (OCI) to connect to the data source. This error message is displayed:

Cannot load instant client shared library [oraociei11.dll]. Make sure that the required binaries are present with correct environment variables set.

• 9577470

Agent. Shared Services and Essbase validate passwords in different ways, causing logins to Shared Services to fail.

• 9579175

Aggregate Storage. A Spreadsheet Add-in retrieval of aggregate storage data fails to correctly recognize attribute members with Russian characters in their names.

• 9664240

Server Administration. In rare circumstances, data load may freeze.

• 9668792

Server Administration. Data loads may intermittently fail with error 1220000.

• 9707881

SQL Interface. EssOCI shared library does not load when using the OCI connection.

• 9742190

Aggregate Storage. Essbase Server terminates abnormally when shared members are included in aggregate storage Clear Data operations.

• 9748369

API. In Spreadsheet Add-in, when the Use Styles option is selected, cascading into separate workbooks fails.

• 9756935

MDX. Filters on aggregate storage databases do not work as expected with MDX queries that include calculated members. In some cases, users are unable to access cells to which they have filter access. Part of the fix for this problem is to treat cells to which a user does not have access as #Missing during the calculation of calculated members.

• 9770428

Agent. On Windows AMD and UNIX platforms, Oracle Essbase Administration Services does not recognize the CPU type for Sun SPARC machines.

• 9774781

SQL Interface. If the data type for columns is set to nchar() in MS SQL Server, the dimension build is invalid and the outline contains errors.

• 9778433

API. Retrieving a Smart List in Administration Services causes the Essbase server to terminate abnormally.

• 9800527

Partitioning. When a transparent partition is created between two aggregate storage databases, the parent members of shared members in the target database contain no data.

• 9827959

Partitioning.  When a transparent partition is created between two aggregate storage databases, using the Essbase > Keep Only function causes a database crash.

• 9844842

MaxL. In archive mode, the db readonly flag changes back to the previous setting after the application is unloaded and shut down.

• 9854180

Partitioning. Connecting to an application that is the target for one transparent partition and for one linked partition causes the Essbase Serer to terminate abnormally.

• 9857531

SQL Interface. Parallel data load freezes during the Commit stage if user attempts to cancel the operation.

• 9858187

Data Extraction. When Spreadsheet Add-in retrieves from older versions of Essbase Server, such as 7.1.3, EssCell functions return the error: Bad binary spreadsheet table.

• 9858198

Calculator. Essbase Server terminates abnormally when a calculation script causes the AD_TOKEN_SIZE to exceed its buffer size.

• 9858215

Server Administration. Updating drillable regions causes Essbase to terminate abnormally.

• 9883671

MDX. When using NONEMPTYMEMBER on more than one calculated member in an MDX query, a syntax error is generated.

• 9910697

API. The command adShrRuleJoin fails and Essbase terminates abnormally if any fields are null or contain an empty string.

• 9920217

Agent. Choosing the option in Administration Services to start an application automatically when the Essbase server is started causes the Essbase Agent to terminate abnormally.

• 9941905

Agent. When Essbase applications repeatedly stop and restart over an extended period of time, the agent may eventually run out of file descriptors and fail to restart the application.

• 9968488

Spreadsheet Add-in. Giving a workbook a name that is longer than 127 characters causes Excel to shut down when connecting to Essbase.

• 10052052

Metadata. On a block storage database, a dimension build rules file executes without error even though the associated data contains recursive relationships, and a data load appears to run, but verification of the resulting outline fails with this error message: A shared member cannot be a descendant of its own prototype.

The correct behavior would be for the offending members to be rejected during the dimension build so that the build can succeed.

• 10062374

API. The EssAutologin dialog box is not displayed on Windows 64-bit systems when using Auto_Default.

• 10062389

Calculator. When a calculation script has a name longer than the limit of eight characters, Essbase may execute a different script instead of generating an error stating that the script name is too long.

For example, if you have two scripts, and, and you try to execute, Essbase may execute instead of generating an error that the script you selected cannot be executed because the name is longer than the limit.

• 10079409

Kernel. Deleting a block storage member in an Administration Services outline causes Essbase to fail.

• 10079782

Spreadsheet Add-in. In double-byte character languages, some dimension builds and data loads of Excel spreadsheets may fail.

• 10079805

Agent. Logging into Essbase with a user name that contains more than 30 characters causes Essbase to terminate abnormally.

• 10083160

Agent. Essbase Agent may terminate abnormally while retrieving security information from Shared Services.

• 10083170

MDX. MDX query results do not include the specified member.

• 10083513

Agent. Essbase terminates abnormally when the number of agtsvrconnections is set to a value greater than 5.

• 10083551

Agent. When some users exist in Shared Services, and Essbase is externalized using the auto password option, an output file called MigratedUserPassword.txt is missing some of the users.

• 10088484

MDX. The Essbase application stops responding when running an MDX query against a block storage application and the user running the MDX query has security filters.

• 10088486

Spreadsheet Add-in. Microsoft PowerPoint functionality for Paste 'MS Excel Worksheet Object' behaves in the same way as 'Paste Link' when both Excel and PowerPoint are open.

• 10088493

MaxL. A shell script generates an exit code 141 error, calling a MaxL script and causing the Autosys job to fail.

• 10088497

Calculator. SET CREATENONMISSINGBLK does not work on a member with a formula calling on a dynamic calculation member that has a cross-reference in the formula.

• 10093820

Server Administration. Use of a substitution variable in a rules file header definition causes the Essbase data load to fail on a block storage application, generating “Unexpected Essbase error 1019026.”

• 10096650

Calculator. DATAEXPORTCOND reads only first parameter in statement, resulting in failure of some data to be exported.

• 10096661

Spreadsheet Add-in. EssVSetMenu(True) returns a false value, which causes it to keep adding the Essbase menu into Spreadsheet Add-in because it is not registering that it already exists resulting in multiple Essbase menus.

• 10096696

Partitioning. When retrieving on the target of a partitioned cube, if at least one member does not belong to the source partition (transparent), then data is incorrectly displayed in the spreadsheet.

• 10096724

Metadata. The server terminates abnormally due to an implicit recursion present in MDX formulas. The recursion should have been caught and an error generated when the recursion depth exceeds the MDX limit of 31 levels.

• 10096755

Aggregate Storage. When aggregate storage databases are upgraded from pre-9.3.1 releases, retrievals on some MDX formulas may fail and generate an error stating Recursion limit [31] reached. You can override the recursion limit by setting "MDXLimitFormulaRecursion FALSE" in essbase.cfg.

• 10119138

Aggregate Storage. The command Essmsh terminates abnormally when executed against a non-existent aggregate storage calculation script.

• 10135016

Partitioning. Retrieving two-pass calculated members in a transparent partition while using an attribute dimension results in data retrieval failure.

• 10143496

Aggregate Storage. Adding real members in an alternate hierarchy of an aggregate storage dimension that has shared members may cause a full restructure instead of the expected light restructure.

• 10153934

Partitioning. A replicated partition with upper level stored members on the block storage source that are mapped to level 0 members on the aggregate storage target fails to replicate data after the environment is upgraded to Essbase

• 10158829

Calculator. Essbase may terminate abnormally while evaluating a FIX statement that contains a large member set.

• 10173993

Calculator. Calculation on a transparent partition target fails if GETDBSTATS is called on the source, whether from the outline being opened in Administration Services Console or by another means. The error message reads: (1013009) Administrator Has Temporarily Disabled User Commands.

• 10207959

Calculator. After adding attribute dimension members to a block storage database that is set as the target in a transparent partition (where the source database is aggregate storage), calculations may fail and cause the database to terminate abnormally.

• 10237797

MaxL. The ESSCMD-to-MaxL script conversion utility, cmd2mxl, converts a GETPARTITIONOTLCHANGES command to a refresh outline statement that has incorrect syntax.

• 10255121

Security. Refreshing security at the application level can cause Essbase to stop responding. When the security refresh takes a long time to process, which is more likely to happen at the application level, Essbase does not process further requests until the security refresh is complete. The fix for this problem is to allow Essbase to process additional requests while it is refreshing security.

• 10275620

Server Administration. Performance is slower than expected when retrieving from a block storage partitioned target with Oracle® Essbase Analytics Link for Hyperion Financial Management as the source. To enable the optimization function, add SSOPTIMIZEDGRIDPROCESSING TRUE to the essbase.cfg file.

Note that when using this optimization setting, queries that benefit from it can require up to two times more memory to execute.

• 10279894

Partitioning. When the source and target of a replicated partition have a different number of members, replication of data from source to target fails with this error message: One of the defined dimensions doesn't have mapped members.

• 10287609

Agent. In Administration Services, in Essbase > Edit Sessions, user IDs are displayed incorrectly.

• 10304342

Server Administration. When migrating an application from Release 9.3.1.x to the current release, if a member formula contains a C++-style comment (prefaced by "//") in its last line, the migration may fail, and Essbase Server may terminate abnormally.

• 10356225

Agent. Users with write privileges on a database may see information on other users that they are not entitled to see.

• 10360107

Aggregate Storage. Retrieval containing MDX queries from an aggregate storage partitioned target database causes the application to terminate abnormally.

• 10368038

API. If a member has a format string greater than 256 characters in length, it may be impossible to open that member in order to edit it.

• 10373538

Server Administration. If CRASHDUMP is set to true in essbase.cfg, files may be deleted from your system when stopping an Essbase application.

• 10386246

Calculator. Member expansions during calculation script validations that return a large number of members may cause Essbase to stop responding.

• 10386252

Data Extraction. Retrievals that include dynamic calc and store members may cause Essbase to terminate abnormally.

• 10386264

Data Extraction. A member selection based on varying attributes incorrectly returns an empty member set.

• 10386284

Aggregate Storage. Performance is relatively slow when retrieving data from an aggregate storage application on Solaris 64-bit computers as compared to Solaris 32-bit computers.

• 10386293

Server Administration. An incorrect value for Essbase server RAM is displayed in the Administration Services console.

• 10386640

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

• 10386660

Server API. Application log messages relating to a calculation script execution failure mention only the @XREF function as the cause for the error, when other possible causes exist.

• 10386683

Metadata. Unexpected behavior may occur when using Read and Metaread filters combined.

• 10386698

MaxL. A successful build dimension runs through MaxL and reports errors, directing the user to a log file, but the error log file does not exist.

• 10386712

MaxL. The MaxL Deploy command fails on UNIX platforms, causing Essbase to stop responding or to terminate.

• 10386724

Partitioning. On the target of a transparent partition, if you run a calculation script containing the statement SET REMOTECALC OFF, then you retrieve data and then refresh several times, the data is no longer displayed. Refreshing several more times may cause the data to return into view.

• 10386728

Partitioning. Retrieving data from a transparent partition with an aggregate storage source and a block storage target erroneously returns zeros.

• 10386741

Server Administration. Saving an outline from which shared members were deleted causes the application to terminate abnormally if OUTLINECHANGELOG is set to true in essbase.cfg.

• 10386751

Server Administration. In an outline for which duplicate members are enabled, you cannot create an alias for a member in the same operation in which you add it as a shared member.

• 10403627

Data Extraction. The Report Writer rename command does not work as expected.


Top of Document

Defects Fixed in Release

Defect Number

Defect Fixed

• 549665 (2‑HYPER00016030)

Server Administration. When you open rules files that are stored on a server, records longer than 4,000 bytes incorrectly wrap to multiple lines.

• 6535115 (1‑135608506)

MaxL. On UNIX systems, relative references in MaxL export statements do not write files to the expected directories.

• 6535465 (1‑146129775)

API. EsbSetUser overwrites the user description field with junk characters.

• 6550528 (2‑HYPER00054975)

API. In Spreadsheet Add-in, manually selecting members by generation name using the menu command returns the correct number of members; however, selecting members using a VBA macro incorrectly returns one less member than the count of actual members.

• 6551209 (2‑HYPER00083225)

System Dependent Layer. On Linux systems, when using Application Manager to view server information, no data is displayed in the FILE column.

• 6552375 (2‑HYPER00077574)

Server Administration. The ESSUTF8 utility does not handle paths with wildcards correctly.

• 6552376 (2‑HYPER00077579)

Server Administration. Running the ESSUTF8 utility using the ''-e'' option to display encoding erroneously updates the datetime stamp on the scanned files.

• 6565633 (8‑512632571)

Metadata. Metadata security for attribute queries does not function correctly.

• 6576618 (8‑582790524)

MaxL Perl Module. MaxL Perl Module ( does not compile on 64-bit operating systems.

• 6585364 (8‑656332849)

Data Mining. The Essbase data mining API, accessed using MaxL, does not provide a robust mechanism for discovering the mining session ID, which is the handle for accessing the results of a create mining result command.

• 6858547

Agent. Connecting to an Essbase application using Shared Services returns an error message indicating that the user name is too long.

• 6918863

MaxL. Assigning application and database access to an OpenLDAP user by adding the user to a group does not work when you use the MaxL create user command with the member of clause.

• 6997897

Spreadsheet Add-in. Multiple Essbase menus are displayed in Excel.

• 7169821

Agent. Users with names that begin with special characters cannot be provisioned.

• 7439034

Server Administration. Essbase cannot handle host names that exceed 30 characters.

• 7462123

Server Administration. Host names greater than 30 characters cause Essbase server to terminate abnormally.

• 7483209

External Authentication Configuration. Essbase does not allow connections to external users with multiple attributes.

• 7511003

Metadata. Unexpected database restructuring occurs when a dynamic calculation member is added to a dense dimension.

• 7558645

Agent. You cannot create user names that begin with a backslash ( \ ), using MaxL or ESSCMD from Administration Services Console.

• 8248780

Metadata. Aggregate storage database restructuring terminates abnormally when a shared member is not marked as shared.

• 8265958

API. In Oracle Hyperion Smart View for Office, Fusion Edition, if the Suppress No Data/#Missing and Suppress Zero options are enabled during ad hoc analysis, the server incorrectly returns an internal Oracle Hyperion Provider Services error when connecting to the outline.

• 8278841

MDX. When running an MDX query, Essbase returns an error indicating that the query cannot be processed because the set size exceeds the tuple limit.

• 8317306

Metadata. When migrating an aggregate storage application from an earlier release of Essbase, if the NODENAME entry in essbase.cfg exceeds 32 characters, migration fails and an empty outline is created; attempting to open the empty outline causes Administration Server to terminate abnormally.

• 8394774

Metadata. For block storage applications, the querymembers command does not find extended share members.

• 8398518

Agent. After refreshing security from Shared Services, group changes are not applied in Administration Console.

• 8445096

Server Administration. When a filter user is granted filter access using a member set function, if the member set becomes NULL through metadata changes, the user has full access to the data.

• 8448098

Server Administration. When creating metadata security, a label-only ancestor of a meta-read member is granted access when it should be denied.

• 8585732

Aggregate Storage. Aggregate view creation ignores the stopping value, resulting in aggregate views that require more disk space than expected.

• 8588965

MaxL. MaxL encryption fails for user names that contain the maximum number of characters.

• 8617195

Calculator. Formulas involving upper-level members and @CURRMBRRANGE return incorrect results.

• 8667389

MaxL. MaxL command to convert a block storage outline to an aggregate storage outline fails with an unexpected Essbase error.

• 8677145

Calculator. The DATAEXPORTCOND calculation command clashes with the FIX command.

• 8709580

Server Administration. Database restructuring fails when OUTLINECHANGELOG TRUE is included in essbase.cfg.

• 8722852

MDX. When running an MDX query, Essbase returns an error indicating that the query cannot be processed because the set size exceeds the tuple limit.

• 9198701

Calculator. Using the XREF function in a calculation script causes the system to freeze.

• 9240162

MaxL Perl Module. MaxL Perl Module ( does not compile on 64-bit operating systems.

• 9342960

MDX. When an Essbase security filter and BI suppression are active in a report, the combination causes some row labels to repeat.


Top of Document

Known Issues

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

Defect Number

Known Issue


Spreadsheet Add-in. Running VBA scripts may cause Microsoft Excel to terminate abnormally.

Workaround: Remove and disable the Essbase Excel COM add-in:

Note: If the COM Add-Ins button is displayed on your Excel toolbar, skip to step 4.

1.    In Excel, select Tools, and then Customize.

2.    On the Commands tab, under Categories, select Tools.

3.    Under Commands, select COM Add-Ins and drag it to your toolbar, and then click Close.

4.    On the toolbar, click the COM Add-Ins button

5.    Select EXCEL and EQD COM Addin, and then click Remove.


MDX. The PARENT function returns incorrect values.

Workaround: Tag the members along the sales dimension as “never share.”


Metadata. The @RDESCENDANTS function does not work as a MetaRead filter due to an issue with shared member metadata security.


Server Administration. Sparse restructure fails if the disk volumes for the page files run out of disk space.


Spreadsheet Add-in. Exporting reports to Excel from Oracle Financial Analyzer (OFA) results in a MS VC++ program error when Spreadsheet Add-in is installed and registered on the same computer as OFA.

Workaround: Remove and disable the Essbase Excel COM add-in:

Note: If the COM Add-Ins button is displayed on your Excel toolbar, skip to step 4.

1.    In Excel, select Tools, and then Customize.

2.    On the Commands tab, under Categories, select Tools.

3.    Under Commands, select COM Add-Ins and drag it to your toolbar, and then click Close.

4.    On the toolbar, click the COM Add-Ins button

5.    Select EXCEL and EQD COM Addin, and then click Remove.


Data Extraction. In Excel, data retrievals that use dynamic calculations return inconsistent results.


Calculator. A sparse dimension member's value is incorrect when it has a formula on a dense dimension, an attribute assigned, and is tagged as two pass.


Documentation. For Russian, German, French, Spanish, Brazilian Portuguese, Danish, Italian, Swedish and Turkish, using the batch file StartEssCmd does not ensure that Essbase messages are displayed correctly in the console window. You must ensure that the proper code page and font are used in the console window.

Workaround: The code page can be changed using chcp 1251 (Russian) or chcp 1252 (all other languages mentioned previously). This can be added manually to StartEssCmd.bat on your computer.

The font is changed using the properties dialog for the cmd.exe window; it either needs to be changed each time, or the change can be permanent depending on your preference.


Aggregate Storage. Aggregate storage date-time dimensions created prior to release 9.3.1 are not supported. You can delete date-time dimensions from an outline and use the Create Date-Time Dimension wizard to recreate them.


Agent. When the copy database command fails, the database is left in read-only mode.


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

9148350, 9094695

Spreadsheet Add-in. Spreadsheet Add-in does not work on Windows with Excel 2000.

Workaround: Copy dbghelp.dll from %ARBORPATH%\bin to %SystemRoot%\system32 and %SystemRoot%\system32\dllcache.


Spreadsheet Add-in. The currency report in Spreadsheet Add-in is not available out-of-the-box to users without DBMANAGE access.


Kernel. Applications with currency databases that span multiple disk volumes cannot be copied.


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.


High Availability. Multiple Essbase instances that belong to different Essbase clusters cannot use the same ARBORPATH.

Workaround: Set up only one Essbase cluster per ARBORPATH.


Essbase. On UNIX, OPMN management of Essbase and failover clustering is not supported if you are using Oracle BI EE as a data source for Essbase.


Aggregate Storage. Retrievals from aggregate storage applications use up all computer memory and swap spaced, and are unsuccessful.

Workaround: Add this setting to essbase.cfg for the application:

MAXFORMULACACHESIZE application_name database_name 4096

This line configures a value of 4 MB for formula cache. You must restart the application after modifying essbase.cfg.


High Availability. When creating failover clusters, cluster names cannot be longer than 64 characters, and Arborpath cannot be longer than 255 characters.


High Availability. If the service failover process is running, and something occurs to cause it to terminate and not restart, OPMN can hang or forget the state of the service failover and not attempt to restart the process later.

Workaround: Manually try reloading each OPMN participating in the service failover and then manually start the service failover if it is not running. If reloading hangs, manually terminate the OPMN server and monitor, and restart OPMN and the service failover process.


Server Administration. When Essbase is configured for a European locale, the data does not load successfully if the data is in a non-European format (dots are treated as decimal points and commas are treated as group separators).


Server Administration. When using Administration Services Release against Essbase, and Essbase is configured with the default port, dropping partitions using Administration Services Console fails.

Workaround: Specify the default port, 1423, when connecting to Essbase from Administration Services Console.


High Availability. Essbase failover cluster names cannot contain multibyte characters.

Workaround: Use English for cluster names.


XOLAP. An XOLAP cube fails to retrieve data if the outline has member names with double-byte characters.


High Availability. OPMN is unable to start Essbase if ARBORPATH is pointing to a mapped drive.


Calculator. Calculation times are inconsistent on fragmented databases.

9928354, 10117629

Partitioning. Queries containing an attribute value return only zeroes when executed from two transparent source partitions to a target database.


Report Writer. A report script retrieving members that contain a certain MDX formula causes an application to crash.

Workaround: Add FORMULAOPTLEVEL 2 to essbase.cfg.


Partitioning. When a substitution variable in a source partition is mapped to Void on the target, a lock-and-send to the source is not reflected in the target upon a retrieval.

10113961, 11682847

Upgrading. When applying the maintenance release to move from 11.1.2 to, if the Essbase database contains linked reporting objects (LROs), Essbase Server fails to start and returns this error message: mismatch linked object handle.

Workaround: Prior to applying the maintenance release, export the LRO information from the 11.1.2 database, and delete the LROs. Apply the maintenance release, and then import the exported LROs. For instructions, see the Oracle Enterprise Performance Management System Installation and Configuration Guide.


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


Spreadsheet Add-In. Applying currency formatting to a data value causes the number of decimal places to be reduced upon a lock and send.


Report Writer. A report script containing multiple Leaves commands in the same script, resulting in a large number of cells being queried, can result in incorrect member names in the report.


Spreadsheet Add-in. When attempting to lock or retrieve data from Essbase using Microsoft Excel 2007 in a spreadsheet that was created using Excel 2003, this error message is displayed:

Essbase has encountered an internal Excel error. Your sheet will not be overwritten and none of your data will be lost. However, you are strongly urged to exit Excel and restart in order to clear up the problem.


·        Save the non-working sheets as Excel 2003 sheets (.xls). Then, re-save them as Excel 2007 sheets (.xlsx).

·        Look for ways to reduce complexity, such as reducing the size of ranges.

Spreadsheet Add-in does not support worksheet sizes greater than 65,536 rows by 256 columns, which is the maximum worksheet size in Excel 2003. Excel 2007 supports worksheets up to 1,048,576 rows by 16,384 columns.


Spreadsheet Add-in. The Query Designer user interface for multibyte languages does not display correctly on Microsoft Windows XP with Microsoft Office 2007.


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.


Calculator. A data retrieval that includes a dynamic member marked as a two pass calculation that has a formula with another two pass calculation member that is also dynamic returns incorrect results.


MDX. The MDX DTS query member function can return incorrect results if the query contains duplicate members (either implied or explicit shared members, or repeated members). A workaround for this issue is to make sure that, when working with duplicate members, the calculated member is in the first set.

Queries like this one return correct  values:


member [Year].[HTD] as 'DTS(HTD,Jan)'


{[Measures],[profit]} on columns,

{[HTD],[Jan]} on rows

From Sample.Basic

Axis-1              (Measures)          (Profit)


(HTD)                              8024                8024

(Jan)                              8024                8024

While queries like this one return incorrect values:


member [Year].[HTD] as 'DTS(HTD,Jan)'


{[Measures],[profit]} on columns,  

{[Jan],[HTD]} on rows

From Sample.Basic

Axis-1              (Measures)          (Profit)


(Jan)                              8024                8024

(HTD)                              8024            #Missing


Login. When Essbase is set up to allow only secure (SSL) mode, as indicated by the following essbase.cfg configuration, a non-secure port specified in a login does not return an error. The login occurs on the secure port. The non-secure port specified in the login is ignored.

Client essbase.cfg:
ClientPreferredMode Secure
AGENTPORT        1423

Server essbase.cfg:
EnableSecureMode True
EnableClearMode   False
AGENTPORT       1423


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” in the “Documentation Updates” section of this Readme.


Top of Document

Tips and Troubleshooting

Re-hosting Essbase Using Failover Clustering

When using Essbase failover clustering to rehost Essbase, the entry FAILOVERMODE must be removed from the essbase.cfg file on the shared disk.

After FAILOVERMODE is removed from essbase.cfg, the opmn.xml file on Node2 must be updated to add numprocs.

In the opmn.xml file on Node 2, update:

<process-set id="AGENT" restart-on-death="false">


<process-set id="AGENT" numprocs="1" restart-on-death="false">

Top of Document

Documentation Updates

Accessing EPM System Product Documentation

The most recent version of each EPM System product guide is available for download from the Enterprise Performance Management System Documentation area of the OTN Web site ( For faster access to the documentation, you can also use the Enterprise Performance Management Documentation Portal ( which also links to EPM Supported Platform Matrices, My Oracle Support, and other information resources.

Deployment-related documentation is also available from the Oracle E-Delivery Web site (

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

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.

Deprecated Essbase.cfg Configuration Settings



·        NODENAME is completely replaced by ESSBASESERVERHOSTNAME, which serves all the purposes of NODENAME as well as specifies the host name to which Essbase binds.

·        SHAREDSERVICESLOCATION is no longer a valid setting. The necessary information is now centralized in the registry.

Starting Administration Services Console

The name of the executable file used to start Administration Services Console has changed. If you need to start Administration Services Console from the file system, launch the file \console\bin\admincon.bat from the directory to which Administration Services Console was installed. There is no longer a file named admincon.exe.

SQL Interface Guide Corrections                                               

·        In the Oracle Essbase SQL Interface Guide, the topic "Performing Multiple SQL Data Loads in Parallel to Aggregate Storage Databases" incorrectly states that you should create esssql.cfg in ESSBASEPATH/bin/. The correct location for esssql.cfg is $ARBORPATH/bin/.

Also, the second and third lines in the example are incorrect:





"SQL Server Wire Protocol"

"SQL Server Native Wire Protocol"





·        The procedure for "Configuring Data Sources on UNIX" contains errors.

Use the following, corrected procedure instead:

1. Open the $EPM_ORACLE_HOME/common/ODBC/Merant/x.x/odbc.ini file and add a data source       description.

2. Create a symbolic link to the $EPM_ORACLE_HOME/common/ODBC/Merant/x.x/odbc.ini from the UNIX user home directory:

ln -s $EPM_ORACLE_HOME/common/ODBC/Merant/x.x/odbc.ini


3. Verify that the .odbc.ini file in the user home directory matches the odbc.ini file in $EPM_ORACLE_HOME/common/ODBC/Merant/x.x

If the files do not match, repeat steps 1 and 2.

Applying AIX 5.3 Kernel Extensions Update

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

The AIX 5.3 kernel extensions update file can be found on Oracle OTN.

1.    Go to the following URL:

2.    On the “Oracle Database Software Downloads” page, scroll to the “Oracle Database 11g Release 1” section, and then to the “(” section.

3.    In the “AIX (PPC64)” line, click See All.

4.    On the “Oracle Database 11g Release 1 (” page, click Accept License Agreement.

5.    Scroll to the “Oracle Database 11g Release 1 ( for AIX (PPC64)” section.

6.    In step 4 of the onscreen directions, click the link and save the file to disk.

7.    Unarchive the file, and then run the file on the computers on which Essbase Server and Essbase client are installed.

Establishing a Connection to a Teradata Database when Using Essbase with OPMN

When using Teradata data sources with Essbase, and using Oracle Process Manager and Notification (OPMN) to monitor and control the Essbase Agent process, you must update the OPMN.xml with the following variables.

Note: The absolute path value cannot contain spaces. The examples of absolute path values are based on a 32-bit machine configuration. The absolute path value might be different on a 64-bit machine configuration.

·        To establish a connection to the Teradata database, add the TWB_ROOT variable:

<variable id="TWB_ROOT" value=”absolute_path_of_Teradata_Client_DLLs”/>

For example:

<variable id="TWB_ROOT" value="C:\Progra~1\Teradata\Client\13.10\Terada~1\"/>

·        Append the OPMN Session PATH with Teradata Client, Cliv2, and Message DLLs, using the following variables:

<variable append=”true” id=”PATH” value=”absolute_path_of_Teradata_client_DLLs”/>

<variable append=”true” id=”PATH” value=”absolute_path_of_Teradata_cliv2”/>

<variable append=”true” id=”PATH” value=”absolute_path_of_Teradata_message_DLL”/>

For example:

<variable append="true" id="PATH" value="C:\Progra~2\Teradata\Client\13.0\Terada~1\bin "/>

<variable append="true" id="PATH" value="C:\Progra~2\Teradata\Client\13.10\CLIv2"/>

<variable append="true" id="PATH" value="C:\Progra~2\Teradata\Client\13.0\Terada~1\msg"/>

Top of Document

Accessibility Considerations

It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community. 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 EPM System Documentation Library on the Oracle Technology Network (

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

Top of Document