Caution: You are urged to carefully read and understand the following requirements. Failure to comply may result in applying a patch that can cause your application to malfunction, including interruption of service and/or loss of data. Before installing or applying this patch:

Verify that your system configuration (product version, patch level, and platform) exactly matches what is specified in the Readme.

Unsupported Features

MaxL Perl Module Will No Longer Be Supported in 12.2.1.3.0

MaxL Perl Module will not be supported starting with Release 12.2.1.3.0.

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.

Patch Type

This is a patch set update (PSU).

This patch replaces files in the existing installation and does not require a full installation.

Supported Paths to this Patch

You can apply this patch to the following releases:

· 11.1.2.4.000

· 11.1.2.4.001

· 11.1.2.4.002

· 11.1.2.4.003

· 11.1.2.4.004

· 11.1.2.4.005

· 11.1.2.4.006

· 11.1.2.4.007

· 11.1.2.4.008

· 11.1.2.4.009

· 11.1.2.4.010

· 11.1.2.4.011

· 11.1.2.4.012

· 11.1.2.4.013

· 11.1.2.4.014

· 11.1.2.4.015

· 11.1.2.4.016

· 11.1.2.4.017

· 11.1.2.4.018

· 11.1.2.4.019

· 11.1.2.4.020

· 11.1.2.4.021

· 11.1.2.4.022

· 11.1.2.4.023

Caution: Oracle recommends using the same version of all Essbase portfolio products (Essbase, Essbase Administration Services, Hyperion Provider Services, and Essbase Studio) and components (server, client, runtime client, API, and JAPI). When only some Essbase portfolio products are included in a patch release, the last released versions of the products that are not included in the patch are supported.

Essbase Administration Services 11.1.2.4.023, Provider Services 11.1.2.4.025, and Essbase Studio 11.1.2.4.016 are supported for use with Essbase 11.1.2.4.025.

Recommendation: After you apply a patch within the same release codeline, 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.

Prerequisites

Required User Rights

The user applying the patch should be the user who was set up to install and configure EPM System products. Required user privileges or rights:

Windows:

Use the user account that has Local administrator rights and was set up for installation and configuration. This user is an administrator and is the same for all EPM System products. Assign local policies if required by the product. Such assignments typically are: “Act as part of the operating system, Bypass traverse checking, Log on as a batch job, Log on as a service.”

UNIX/Linux:

Use the account that was used to install EPM System products and has Read, Write, and Execute permissions on $MIDDLEWARE_HOME. If you installed other Oracle products, the user who installed EPM System products must be in the same group as the user who installed the other Oracle products. OPatches are not intended to be applied using a root user.

Supported Platforms

Applies to all 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

Applies to all 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

Defects Fixed in this Patch

Defect Number	Defect Fixed
· 27744715	After running an Essbase job, Import Oracle Fusion Data Extensions for Transactional Business Intelligence does not display data populating correctly for reports based on cube.
· 27731207	Reports submitted from Oracle Business Intelligence generates an MDX query that in some cases causes an Aggregate Storage application connection closure with Network Error 10054.
· 27538674	MaxL script for allocation improvement to support larger size.
· 27476426	Calculation performance was slow in the case of Calc Dataexport for databases that have large block size and the calculation has a FIX on a large number of members.
· 27241692	Allocation calculation performance degraded in some cases after Essbase 11.1.2.4.012 Patchset Update.
· 25457372	In some cases, an Aggregate Storage application using SUBSELECT returns #MISSING.
· 27631111	A dimension build fails to update for duplicate members with the expense property type of an Aggregate Storage database.
· 27348228	The SET EMPTYMEMBERSETS set to ON in a calculation script does not work as expected and returns #MISSING.
· 27703870, 27629975	The EXPENSE property type for shared members should derive from the base member.
· 27553676	In some cases, an MDX query can cause the Essbase server to terminate abnormally.
· 26880357	In some cases, errors are returned after an Essbase outline is modified: Error: 1054001 Cannot load application <Application_Name> with error number [1052003]
· 27694630, 27372488, 28021881, 27932949	An essbase.cfg setting to configure and disable idle-time shutdown at app level has been added Syntax: SVRIDLETIME <val> SVRIDLETIME <app> <val> <val> is specified in minutes. If <val> is set to 0, the idle-time shutdown is disabled for the target application(s).
· 28158588	When an MDX report is run with a large queried region and access filters are used then an error can be returned: ERROR - 1200762 - Internal Error: Mathematical operation results in wide integer overflow/underflow. Reduce the size of the query region. ERROR - 1241101 - Unexpected Essbase error 1200762.
· 27965789, 27965768	There is an inconsistency in signage of values for MDX and Report Writer reports when "Use Expense Type" functionality is activated for Smart View reports.
· 27958040, 27736538, 28051882	In some cases, during a database restructure the database outline is missing and results in an error Essbase Error (1002097): Unable to Load Database
· 27920128	In some cases a report script causes the Essbase server to terminate abnormally.
· 27594652	Unable to run a calculation script if the script is large.
· 27422358	When running a calculation script against a Unicode Block Storage Application with @ISMBRUDA can result in the application terminating abnormally.
· 27283225	While running a calculation and a clear partial data on an Aggregate Storage Application in some cases can result in a core dump and will generate an exception file.
· 26821074	When running an MDX report it can fail with an error: Possible loss of data or precision in column
· 27969867	In some cases a query runs slower in Essbase 11.1.2.4.023 Patchset Update than in previous releases.
· 27875035	In some cases, incorrect results are returned when using an Aggregate Storage application with a query on a member that is tagged as dynamic calc with NONEMPYTUPLE.
· 27809356	In some cases when running a query with attributes on a Federated or Transparent Partition can result in abnormal termination.
· 27765425	In some cases when using Hybrid Aggregation, an MDX report on Link Reported Objects is not returned.
· 27717868	Creating an Aggregate Storage outline with attributes, then deleting the attributes and saving the outline may result in abnormal termination of the application.
· 27669383, 26928063	In some cases of using CREATE SET in MDX reports can result in an abnormal termination of the application.
· 27860762	Enhanced Auto Generation of Aggregate Views. See Documentation Updates below for more information.
· 27530595	Priorities for MDX property MEMBER_TYPE have been changed to allow filtering out dynamically calculated members for any dimension. Example: SELECT {} ON COLUMNS, FILTER([Measures].MEMBERS,[Measures].CurrentMember.MEMBER_TYPE <> 2) ON ROWS FROM [ASOSamp].[Sample] The MEMBER_TYPE for a non-attribute member is set now according to these rules: if ASO non-leaf member or member with formula, ==> 2 else if for BSO dynamic (and not dynamic-and-store) member with formula ==> 2 else if generation 1 member ==> 1 else if accounts ==> 3 else ==> 0 For completeness of the implementation, for attribute member: if attribute calc dimension, and not SUM ==> 2 else if attribute calc dimension, and SUM ==> 0 else if not attribute calc dimension with formula ==> 2 else if not attribute calc dimension without formula ==> 0

Known Issues in this Patch

Linked Partition in SmartView Client cannot connect to Essbase

Linked Partition in SmartView Client cannot connect to Essbase. The work around is to use Essbase host in the partition definition instead of cluster url.

(27502969)

Dim build setting "allow move" is not allowed

Dim build setting "allow move" (for moving a member to another parent) is
not allowed, regardless of the uniqueness defined at the generation level.

(26528652)

Issue with @PARENTVAL() Function

When a calculation formula associated with sparse member assigns a dynamic parent value to a stored child member through @PARENTVAL it may produce a #Missing result. To get the correct result the formula needs to be executed attaching to a dense member.

(24481074)

Essbase Administration Services Server Can Terminate Abnormally After Updating the Outline

If EAS server crashes upon "Update Outline" and if the JRE used is jrockit, add the option -Xss1m in setCustomParamsEssbaseAdminServices.sh at <EPM_ORACLE_INSTANCE>/bin/deploymentScripts>.
The default size of a thread stack in jrockit is 320K for win64 and 1M for linux64. So, set the -Xss value accordingly.

(22985660)

When running Essbase on an SLES 11 operating system and upgrading to 11.1.2.4.006 or above, Essbase Applications cannot load.

Workaround for this issue:

1. Update opmn.xml:
vim ./user_projects/epmsystem1/config/OPMN/opmn/opmn.xml

2.    Add LD_PRELOAD=/lib64/libc.so.6 under EssbaseAgent section:
  <process-type id="EssbaseAgent" module-id="ESS">
    <environment>
      <variable id="LD_PRELOAD" value="/lib64/libc.so.6"/>

3. Restart Essbase using opmn
(/refresh/home/Oracle/Middleware/user_projects/epmsystem1/bin/startEssbase.sh)

(23018108)

Increased usage of disk space on Exalytics

On Exalytics only: There may be increased usage of disk space under certain circumstances when the database grows rapidly. Use the alter database force restructure MAXL statement periodically, to reduce the disk space usage as needed.

(21219151)

On HP-UX, custom calculation allocations using the subtract option may return incorrect results.

On HP-UX, custom calculation allocations using the subtract option may return incorrect results. See "Allocation Options."

(21092593)

Applying this Patch

The section includes important information about applying this patch for Essbase.

Component	Patch ID
Essbase Client MSI (Windows)	27797117
Essbase Client (OPatch)	27797126
Runtime Client	27797123
Essbase Server	27797131

To apply this patch for Essbase Client on Windows 32-bit and 64-bit platforms:

1. Uninstall the Essbase Client.

2. To apply this patch, run the EssbaseClient.exe, pick a destination folder, and complete the installation.

NOTE: After applying the Essbase Client patch, you might need to set the ESSLANG variable to your local language.

To apply this patch for Essbase Client on UNIX and Linux platforms:

1. Stop the Essbase service(s).

2. Download and unzip the downloaded patch file <patch id>_<platform>.zip to <EPM_ORACLE_HOME>/OPatch.

NOTES:

o <patch id>_<platform>.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.

o You must unzip the file on the platform for which it is intended. After you unzip the patch file, verify that the executable and library files have execute permission before you apply the patch. If you apply the patch and the executable and library files do not have execute permission, you will not be able to start Essbase after applying the patch.

3. On the Essbase Server machine, launch command prompt and change the current directory to the <EPM_ORACLE_HOME>/OPatch.

4. To apply the patch, enter the following command on one line:

Windows:
opatch.bat apply <EPM_ORACLE_HOME>/Opatch/<PATCH DIRECTORY> -oh <EPM_ORACLE_HOME>
-jre <MIDDLEWARE_HOME>/jdk160_35

NOTE: The default for <EPM_ORACLE_HOME> is C:/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is C:/Oracle/Middleware.

UNIX/Linux:
./opatch apply <EPM_ORACLE_HOME>/OPatch/<PATCH DIRECTORY> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_35 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

NOTE: The default for <EPM_ORACLE_HOME> is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

5. If you use <MIDDLEWARE_HOME>/EPMSystem11R1/products/Essbase/EssbaseClient/api/redist you will need to update these files from <MIDDLEWARE_HOME>/EPMSystem11R1/common/EssbaseClient/11.1.2.0/bin

NOTE: The default for <MIDDLEWARE_HOME> is C:/Oracle/Middleware.

6. Restart Essbase.

NOTE: After applying the Essbase Client patch, you might need to set the ESSLANG variable to your local language.

To apply this patch for runtime client:

1. Stop the Essbase service(s).

2. Download and unzip the downloaded patch file <patch id>_<platform>.zip to <EPM_ORACLE_HOME>/OPatch.

NOTES:

o <PATCH ID>_<PLATFORM ID>.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.

3. On the Essbase Server machine, launch command prompt and change the current directory to the <EPM_ORACLE_HOME>/OPatch.

5. If you use <MIDDLEWARE_HOME>/EPMSystem11R1/products/Essbase/EssbaseClient/api/redist you will need to update these files from <MIDDLEWARE_HOME>/EPMSystem11R1/common/EssbaseRTC/11.1.2.0/bin

NOTE: The default for <MIDDLEWARE_HOME> is C:/Oracle/Middleware.

6. Restart Essbase.

To apply this patch for Essbase Server:

1. Stop the Essbase service(s).

2. Download and unzip the downloaded patch file <patch id>_<platform>.zip to <EPM_ORACLE_HOME>/OPatch.

NOTES:

o <PATCH ID>_<PLATFORM ID>.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.

3. On the Essbase Server machine, launch command prompt and change the current directory to the <EPM_ORACLE_HOME>/OPatch.

5. If a language other than English is installed copy localized files to your bin directory

Copy all the files from <EPM_ORACLE_HOME>/products/Essbase/EssbaseServer/localized/<Language ID>/bin
to
<EPM_ORACLE_HOME>/products/Essbase/EssbaseServer/bin

Replace <Language ID> in the preceding lines with the appropriate language identifier for your installation. The following are the language identifiers for each language available for this release:

o Arabic – ar

o Chinese (Simplified) - zh_CN

o Chinese (Traditional) - zh_TW

o Czech - cs

o Danish - da

o Dutch – nl

o English - en

o Finnish – fi

o French – fr

o French (Canadian) - fr_CA

o German - de

o Greek - el

o Hebrew - he

o Hungarian - hu

o Italian - it

o Japanese - ja

o Korean - ko

o Norwegian – no

o Polish - pl

o Portuguese - pt

o Portuguese (Brazilian) - pt_BR

o Romanian - ro

o Russian - ru

o Slovak - sk

o Spanish - es

o Swedish – sv

o Thai - th

o Turkish - tr

6. Restart Essbase.

Rolling Back this Patch

To remove this patch for Essbase Client on Windows:

1. In Windows Control Panel, navigate to Add or Remove Programs.

2. Select the appropriate item, and then click Remove.

3. Reinstall the previous version of the Essbase Client console.

To roll back this patch for Essbase Client on UNIX and Linux platforms, Essbase Runtime Client, or Essbase Server:

1. From a command line, change the directory to <EPM_ORACLE_HOME>/OPatch (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

2. To roll back the patch, enter the following command on one line:

Windows:
opatch.bat rollback -id <PATCH ID> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_35

NOTE: The default for <EPM_ORACLE_HOME> is C:/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is C:/Oracle/Middleware.

UNIX/Linux:
./opatch rollback -id <PATCH ID> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME> /jdk160_35 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

NOTE: The default for <EPM_ORACLE_HOME> is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

Troubleshooting FAQs

Why do I get the following patch conflict error message when running OPatch?

If the patch that you apply conflicts with a previously applied patch, you may receive the following error message when running OPatch:

Patch(es) <PreviousPatch#> conflict with the patch currently being installed (<NewPatch#>).

If you continue, patch(es) <PreviousPatch#> will be rolled back and the new patch (<NewPatch#>) will be installed.

If a merge of the new patch (<NewPatch#>) and the conflicting patch(es) (<PreviousPatch#>) is required, contact Oracle Support Services and request a Merged patch.

This error is returned when one patch attempts to update a previously patched file. When this conflict happens, you can either (1) roll back the previous patch and apply the new patch (this action might be appropriate if the previous patch was not critical) or (2) request a “merged patch” consisting of the new patch and the patch that it conflicts with. To request a merged patch, contact your Oracle Support representative.

Why do I get the OUI-67078 warning message when applying OPatch?

This warning means that the patch being applied is a superset of a patch already on the deployment and the existing patch will be rolled back. The following snippet shows the context of this warning.

The following warnings have occurred during OPatch execution:
1) OUI-67078:Interim patch 12345678 is a superset of the patch(es) [77777777] in OH C:\Hyperion
-----------------------------------------------------------------------------------
OPatch Session completed with warnings.

How can I find out which releases and patches of EPM System products are installed in a deployment?

In EPM System Release 11.x, you can use the lsinventory command to OPatch to find the release and patches that are installed in an Oracle Home. For example, enter the following command on one line:

Windows:

opatch.bat lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_35

UNIX/Linux:

./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_35
–invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

I applied the patch successfully but I don’t see the changes from the patch in the product. What should I do?

When patching an .EAR file for an application, you may need to delete the cached files in the following folders in order to see the changes provided with the patch:

<MIDDLEWARE_HOME>/user_projects/domains/<DOMAIN_NAME>/servers/
<MANAGED_SERVER_NAME/tmp/

<MIDDLEWARE_HOME>/user_projects/domains/<DOMAIN_NAME>/servers/
<MANAGED_SERVER_NAME/cache

Documentation Updates in this Patch

Auto Generation of Aggregate Views

Aggregate Views have been updated in order to improve the performance of Aggregate View creation with auto generation based on query tracking. To enable this, update the essbase.cfg file with the following

DefaultViewBuild <APP_NAME> <AUTO_Mode>

DefaultViewBuildSize <total_size>

<AUTO_Mode> = TRUE or FALSE - enable automatic default aggregate views maintenance (recreate default views on every destructive change, views removal or data load to empty DB)

<total size> - Optional. Selects views, specifying a storage stopping value in terms of a factor times the size of the unaggregated input (level 0) values. For example, a stopping value of 1.5 means that the view selection should permit the database to grow by no more than 50% as a result of the aggregation.

(27860762)

Idle Application Shutdown (Applicable Only on Linux)

An essbase.cfg setting to configure and disable idle-time shutdown at app level has been added

   Syntax:
   SVRIDLETIME n
   SVRIDLETIME <app> n

Where n is the number of minutes of idle time permitted before shutdown and <app> is the name of the application. The default value is 0 minutes which means it is disabled. The minimum value is 1 minute. The maximum value is 20160 minutes (two weeks). If this setting is not added to the essbase.cfg file, then idle-time shutdown is disabled.

An Essbase application server starts when needed: for example, when someone runs a calculation or a data load. To optimally use the server capacity, Essbase shuts down idle applications after n minutes.

SVRIDLETIME should always be set to a few more minutes than the idle-user session logout time, which you can change using the set session_idle_limit grammar in the MaxL alter system statement.

Maximum number of Alias Tables

The maximum number of Alias Tables has been increased from 32 to 56 starting with Patchset Update 11.1.2.4.023. If an outline is saved with more than 32 Alias Tables, then this outline will not be able to be saved with an older Patchset Update.

(25666963, 27458608)

RESTRUCTURETHREADS Recommended Setting

The WORKERTHREADS topic in the Technical Reference lists guidelines for threaded operations. The suggested setting for RESTRUCTURETHREADS is incorrect. Oracle recommends setting an application’s RESTRUCTURETHREADS to 2 for most systems, or 4 if the application runs on Exalytics. Check your calculation and restructure performance after making any changes.

Naming Convention for Essbase Application Description Update: PCM

The string "__PCM__" is reserved and should not be used for Essbase Application Descriptions.

(25599357)

Attribute dimension Members should be Ignored in Dataload

Attribute dimension members should be ignored during the data load. In previous releases it was not ignored and the intersection was overwritten with the new value. Starting with this patch this case will return an error if there is an attribute member in the data load file. In case of free form data load it will abort the data load.

(25675558)

Optimizing Custom Calculations by Skipping Empty Tuples

Because large data sets can be very sparse, using the NONEMPTYTUPLE property in custom calculation scripts can optimize your script to conserve memory resources.

You create a custom calculation script with one or a series of tuple-expression pairs in MDX, terminated by semicolons. You can optionally filter out empty result sets from being calculated, by including the NONEMPTYTUPLE property clause in the custom calculation script.

Using the NONEMPTYTUPLE property clause in a custom calculation script indicates to Essbase that the cell value being calculated for a tuple is empty whenever the given nonempty_member_list is empty.

Syntax

use_optimized_way;

tuple := [NONEMPTYTUPLE (nonempty_member_list)] numeric_value_expression;

Where

use_optimized_way — a literal keyword, required to enable the use of NONEMPTYTUPLE property in the calculation script. If omitted, NONEMPTYTUPLE directives are ignored.

tuple—an MDX specification of one or more members, where no two members can be from the same dimension.

NONEMPTYTUPLE — an optional property you can use to optimize calculation performance. If used, then you must follow this literal property with nonempty_member_list.

nonempty_member_list — one or more comma-separated member names from different dimensions.

numeric_value_expression — a simple MDX numeric value expression, such as a number or an arithmetic operation. The expression must be on the right side of the equation. Only arithmetic operators are permitted. An error is returned if non arithmetic operators (such as AND, OR, or IF statements) are used.

Examples

The following custom calculation script examples include a NONEMPTYTUPLE property clause to filter out empty tuples from being included in the calculation pass.

use_optimized_way;

([Balance].[Net Balance].[Net Change].[Allocation Out]):= NONEMPTYTUPLE ([Balance].[Remainder],[Rule]) -(([Balance].[Remainder],[Rule])*(20.24000/100));

([2014], [August], [Actual]):= NONEMPTYTUPLE ([2014], [January], [Actual]) ([2014], [January], [Actual]);

For more information about writing custom calculation scripts, see “Writing Custom Calculations” in the Oracle Essbase Database Administrator’s Guide.

(25416191, 26305739)

ODBC Driver Descriptor Management in Essbase

In releases prior to 11.1.2.4.014, you must update driver descriptor strings in essbase.cfg to exactly match those in odbcinst.ini after every driver version update. Driver versions may be updated without an Essbase release update, breaking DSN-less connections in Essbase. You must then update essbase.cfg for the DSN-less connections to work.

In Releases starting with 11.1.2.4.014, Essbase automatically finds the appropriate driver without requiring any configuration. The higher version of the drivers get preference.

Example 1

If you want to make a connection with Oracle Database, and the following list of drivers is available:

[ODBC Drivers]

Data direct 7.1 Oracle Wire Protocol

Data direct 7.1.4 Oracle Wire Protocol

Essbase uses the Data direct 7.1.4 Oracle Wire Protocol driver because it is the highest version.

Example 2

If you want to make a connection with SQL Server, and the following list of drivers is available:

[ODBC Drivers]

Data direct 6.0 SQL Server Wire Protocol

Data direct 7.0 SQL Server Wire Protocol

Data direct 7.1 SQL Server Wire Protocol

Data direct 7.1.4 SQL Server Wire Protocol

Essbase uses the SQL Server 7.1.4 driver because it is the highest version.

Notes:

· This functionality works differently in different releases. This document covers only 11.1.2.4.xxx releases, starting with 11.1.2.4.014.

· Older drivers may be present because of previous Essbase installations. When the new version of Essbase is installed, it must use the latest drivers supplied with the new installation. You cannot use the older drivers.

· (24943751)

Unexpected Labels Printing in Report Script

A report script using substitution variables and the MISSINGTEXT command with empty arguments may cause unexpected data presentation. Workaround: use an extra set of quotation marks in the MISSINGTEXT command. For example:

{MISSINGTEXT """"}

(23733454)

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];

no_force

Optional keyword. The no_force option 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 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;

JAPI SOAP web services will be removed in a future release

JAPI SOAP web services will be removed in a future release and they will be replaced with REST APIs.

Generating Delimited Output Tables for MaxL and MDX

Overview

For the following types of MaxL and MDX statements, whose output displays tables or grids of data, you can set the MaxL Shell (essmsh) to create spool (output) files that are more easily readable by programs (such as Microsoft Excel, RDBMS, or custom parsers) that can import delimiter-separated file formats such as CSV.

· Select statements (MDX)

· Display statements (MaxL)

· Query statements (MaxL)

Syntax

To turn on delimiters for tabular output, use a MaxL Shell command to turn on column delimiters in the MaxL script file. The syntax is:

set column_separator STRING;

where STRING is the column separator.

For example, to create tab-delimited output that Excel can read,

set column_separator " ";

where the double quotation marks enclose a single Tab.

The column separator can be any string. For example:

set column_separator "*|*";

To turn delimiters off after the select, display, or query statement has executed, use:

set column_separator off;

To turn column headers on or off, the syntax is:

set column_header on|off;

Column headers are on by default.

To control whether issued statements are repeated in the spool file, turn echo mode on or off. The syntax is:

set echo_mode on|off;

Echo mode is on by default.

Notes

The tabular output is saved in MaxL spool files. A MaxL Shell spool file is a text file of the shell session and its output.

To make spool files contain only the delimited tabular output that you want,

a. Use non interactive mode to run a MaxL script file. Non interactive mode means that MaxL Shell must be invoked with a script file name provided as the first (or only) argument.

b. Ensure that the spool on command is the last MaxL Shell operation in the script before the select, display, or query statement, and that the spool off command follows the final statement that you are interested in printing to the spool file.

c. Set the message level to warning; otherwise, informational messages will be printed in the spool file.
set message_level warning;

d. Turn off echo mode; otherwise, statements and newlines will be printed in the spool file.
set echo_mode off;

e. Optionally, turn off the printing of the header row in the spool file.
set column_header off;

The spool file contains a concatenation of all the select, display, or query statement results. Each result is separated by a single empty line.

Example Script

/* file name: report0.msh: */

set column_width 200;

/* to make spool file cleaner, return only warnings */

set message level warning;

set column_separator "#~";

set column_header off;

set echo_mode off;

spool on to 'output0mdxnohead.txt';

select {[Mar],[Apr]} on columns,

{[300],[400]} dimension properties

level_number, member_unique_name on rows,

crossjoin({[Actual],[Budget]},

{[Opening Inventory],[Ending Inventory]})

dimension properties level_number, member_unique_name on pages

from [Sample].[Basic];

spool off;

set column_header on;

spool on to 'output0mdxhead.txt';

select {[Mar],[Apr]} on columns,

{[300],[400]} dimension properties

level_number, member_unique_name on rows,

crossjoin({[Actual],[Budget]},

{[Opening Inventory],[Ending Inventory]})

dimension properties level_number, member_unique_name on pages

from [Sample].[Basic];

spool off;

/* More width for display database, as member names are ~4kb */

set column_width 10000;

set column_header on;

spool on to 'output0display.txt';

display session all;

display database Sample.Basic;

spool off;

spool on to 'output0querydbstats.txt';

query database Sample.Basic get dbstats dimension;

spool off;

logout;

exit;

Example Output Files

When run in non-interactive mode (essmsh report0.msh), the resulting spool files have the following contents:

MDX output without header (output0mdxnohead.txt):

Actual#~Opening Inventory#~0#~Actual#~0#~Opening Inventory#~Cream Soda#~1#~300#~29095#~30334

Actual#~Opening Inventory#~0#~Actual#~0#~Opening Inventory#~Fruit Soda#~1#~400#~26409#~27588

Actual#~Ending Inventory#~0#~Actual#~0#~Ending Inventory#~Cream Soda#~1#~300#~30334#~32266

Actual#~Ending Inventory#~0#~Actual#~0#~Ending Inventory#~Fruit Soda#~1#~400#~27588#~29550

Budget#~Opening Inventory#~0#~Budget#~0#~Opening Inventory#~Cream Soda#~1#~300#~27380#~28460

Budget#~Opening Inventory#~0#~Budget#~0#~Opening Inventory#~Fruit Soda#~1#~400#~27230#~29030

Budget#~Ending Inventory#~0#~Budget#~0#~Ending Inventory#~Cream Soda#~1#~300#~28460#~30190

Budget#~Ending Inventory#~0#~Budget#~0#~Ending Inventory#~Fruit Soda#~1#~400#~29030#~31520

MDX output with header (output0mdxhead.txt):

Scenario#~Measures#~Scenario.LEVEL_NUMBER#~Scenario.MEMBER_UNIQUE_NAME#~Measures.LEVEL_NUMBER#~Measures.MEMBER_UNIQUE_NAME#~Product#~Product.LEVEL_NUMBER#~Product.MEMBER_UNIQUE_NAME#~Mar#~Apr