Oracle® Essbase Administration Services

Release Patch Set (PS):


About this Patch. 1

Patch Type. 2

Supported Paths to this Patch. 2

Prerequisites. 2

Patch Conflicts. 2

Supported Platforms. 2

Supported Languages. 3

New Features. 3

Defects Fixed in this Patch. 3

Known Issues in this Patch. 4

Applying this Patch. 5

Rolling Back this Patch. 7

Troubleshooting FAQs. 8


About this Patch

This Readme file describes the defects fixed in this patch set (PS) and the requirements and instructions for applying this PS.

Who should apply this patch: This PS contains defect fixes and changes that are specific to the Oracle Exalytics In-Memory machine. You should install this PS only in the following circumstances:

·         You are installing Essbase on the Exalytics In-Memory Machine, or

·         There is an urgent need for a defect fix that is included in this PS

Customers considering this PS for a platform other than the Exalytics In-Memory Machine should carefully review the list of fixed defects. If there is not a truly urgent need for a defect fix included in this PS, Oracle recommends customers install the upcoming Enterprise Performance Management (EPM) release, which will contain an update, instead of this patch set. To check the availability of the EPM release prior to installing this PS, visit the Oracle Software Delivery Cloud (

Oracle highly recommends that you do extensive testing before making this patch available in a general production environment.

Caution: Once applied, you cannot roll back this patch or any other Essbase component patch.

Also see the “New Features” section in this readme.

Patch Type

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

This PS includes patches for the following components:

·         Essbase Administration Server (Patch ID 12680469, OPatch)

·         Essbase Administration Services Console (Patch ID 12680465, OPatch)

·         Essbase Administration Services Console (Patch ID 13587342, part of a Hyperion Installation Technology patch that includes MSI installers for both Essbase Administration Services Console and Essbase Studio Console)

Supported Paths to this Patch

You can apply this patch to the following release:

Administration Services Release


Other Required Patches

Essbase Run-Time Client (RTC) patch for Release Install this patch before installing Administration Services.

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:

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

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.

Patch Conflicts

If you are using Hyperion Business Rules Release, this patch will delete it. You should therefore migrate from Hyperion Business Rules to Calculation Manager before applying this Essbase Administration Services patch. Refer to the Oracle Hyperion Calculation Manager Administrator’s Guide for guidance on how to migrate.

Supported Platforms

Applies to all supported platforms.

Note: This patch applies to all supported platforms, with the exception of Solaris 9 (also known as Solaris 2.9 or 5.9).

Supported Languages

Applies to all supported languages.

Top of Document

New Features

Changing Essbase Server and Application Log Levels

You can change Essbase log levels at the server and application level in Administration Services Console.

Top of Document

Defects Fixed in this Patch

Use the Defects Fixed Finder tool to review the list of defects fixed prior to release This tool is available here:

Defect Number

Defect Fixed

• 12814275

When migrating Essbase applications to Release, an error message, “Failed to migrate the application,” may be generated. The application, however, is successfully migrated.

• 10136151

Logging on to Administration Services Console using an offloader may fail and return the following error message, Failed: -1 Your session is not currently authenticated. Please log in.

• 13078050, 12928265

In releases prior to, column headers defined in data load rules files are retained when retrieving from a SQL data source, even when the column names in the SQL data source have been changed.

• 12396813

Under some circumstances, if you close the Administration Services Console window without completing an action, this may cause a subsequent log on attempt to fail. In this case, the error message you receive is, “Failed:-1 your session is not currently authenticated please log in.”

• 12637958

Attempting to export data to a remote server using the MaxL Editor may fail.

• 10080310

When using the MaxL Editor, attempting to save a script using the “Save As” menu option may fail.

• 12923340

When using Calculation Script Editor or Report Script Editor, if you select “View,” then “Navigation,” the Close Window icon (“X”) for the editor may no longer appear.

• 12545771

In the Simplified Chinese version of Administration Services Console, the text in the Assign Access Control dialog box is garbled.

• 9955008

In Administration Services Console, you may incorrectly be given the option to copy Planning applications. If you copy a Planning application from Administration Services, you will be unable to provision the application using Shared Services, and the application will not function properly.

• 9979257

The Financial Reporting file report.gif may be deleted by Administration Server. As a result, in Smart View, opening a Financial Reporting report may result in an error message.

• 12638860

After upgrading to Release, it may not be possible to establish an SSL connection to Administration Server using port 4443.


Top of Document

Known Issues in this Patch

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

Data Mining No Longer Enabled

In Essbase and Administration Services, Data Mining is no longer enabled by default. Documentation regarding Data Mining has been removed from the Essbase and 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 to the Oracle Database Enterprise Edition. (12771304)

Include Port Information When Running Administration Services in Fusion Mode

When logging into an Administration Server configured under Oracle Business Intelligence Enterprise Edition, you must specify the port number with the server name. For information on port settings, see the Oracle Fusion Middleware Administrator's Guide. (13359958)

Some Console Functions May Not Work With Windows 7

When running Administration Services Console under Windows 7, some functions may not work. If this occurs, changing Windows security so that the Users group has full access to the folder C:\Hyperion\products\Essbase\eas\console\temp (in a default installation) may resolve the issue. (12673530)

Migration Wizard Does Not Migrate LROs

When Essbase and Administration Services are running in Shared Services mode, the Migration Wizard running in Novice mode fails to migrate LROs from source applications to target applications if, on the Select Objects to Migrate page, you expand the database node. To successfully migrate LROs, do not expand the database node on the Select Objects to Migrate page. (13425491)

Administration Services Not Retaining Server Information

When WebLogic Admin Server is restarted after stopping Administration Server, Administration Services may not retain information on any Essbase servers added by the user. (12376259)

To work around this issue, perform the following:

1) Make a copy of WEBLOGIC_DOMAIN/config/fmwconfig/jps-config.xml as WEBLOGIC_DOMAIN/config/fmwconfig/jps-config-eas.xml. For example: copy C:\Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\jp-config.xml to C:\Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\jps-config-eas.xml.

2) Open the file jps-config-eas.xml in an editor and change the following entry: Find the tag "serviceInstance" with the name attribute "credstore" and change the default location from "./" to "EAS_HOME/server". For example:


    <!-- JPS Credential Store Service Instance -->

    <serviceInstance name="credstore" provider="credstoressp"


      <description>File Based Credential Store Service Instance</description>







3) Open the Windows registry, find HyS9eas and change the entry for

JVMOptionN, where N is a number, from\Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\jps-config.xml


Data Preview in EssbaseCluster-1 May Fail

If you are attempting to preview data on an Essbase instance that has been specified in Administration Services Console as EssbaseCluster-1, the action may fail with the error message, Can’t connect to olap services. Can’t connect to Essbase server. Error:Essbase Error (1042003): Network Error (11001): Unable to locate [EssbaseCluster-1] in Hosts file. (13115255)

Top of Document

Applying this Patch

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


Patch ID

Administration Server

12680469 (OPatch)

Administration Services Console

12680465 (OPatch, use for existing installations)

Administration Services Console

13587342 (MSI installer, use for new installations)


Caution: Once applied, you cannot roll back this patch or any other Essbase component patch.

Administration Server

To apply this patch to the Administration Server:

1.    Stop all EPM System products running on the machine hosting Administration Server and back up the following directories:




2.    Download and unzip the downloaded patch file, <PATCH FILE NAME>.zip to the <EPM_ORACLE_HOME>/OPatch directory.

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

3.    From the command line, set your current directory to <EPM_ORACLE_HOME>/OPatch.

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

opatch.bat apply <EPM_ORACLE_HOME>/OPatch/<patch ID> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>\jdk160_21

5.    Delete the temporary directories. After applying this patch, you must delete the temporary directory.

To delete the temporary directory:

From MIDDLEWARE_HOME\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0,
delete the tmp directory.

Restart Administration Server.

6.    Unzip the Administration Services help files for your locale, located in EPM_ORACLE_HOME/common/epmstatic/eas/docs/<locale>/ If you are using a default installation, extract them to this directory; if you maintain static help files in another location, extract the help files to that location.

Note: When the online help is installed according to the above instructions, it is expected to work when Administration Services Console is logged into Administration Server using the Oracle HTTP server. If Administration Services Console is logged directly into Administration Server and the help does not launch, specify the port number in the help URL corresponding to the Oracle HTTP server port number.

Administration Services Console

OPatch: To apply this patch to an existing Administration Services Console installation using the OPatch process (patch ID 12680465):

1.    Stop all EPM products running on the machine hosting Administration Services Console and back up the following directory:


2.    Download and unzip the downloaded patch file, <PATCH FILE NAME>.zip to the <EPM_ORACLE_HOME>/OPatch directory.

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

3.     From the command line, set your current directory to <EPM_ORACLE_HOME>/OPatch.

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

opatch.bat apply <EPM_ORACLE_HOME>/OPatch/<patch ID> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME> jdk160_21

5.     Restart Administration Services Console.

MSI: To install Administration Services Console using the MSI installer (patch ID 13587342):

1.    Stop all EPM products running on the machine hosting Administration Services Console and, if it exists, back up the following directory:


2.    From My Oracle Support, download the Administration Services Console zip file, <console_install_file>.zip, to a temporary directory.

Note: <console_install_file>.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.

3.    Unzip the file to extract the EASConsole.exe file.

4.    Run EASConsole.exe and follow the prompts.

5.    Restart Administration Services Console.

Top of Document

Rolling Back this Patch

You cannot roll back this or any other Essbase component patch.

Top of Document

Troubleshooting FAQs

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:


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

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


./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_21

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

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.

Top of Document


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