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.

Patch Type

This is a patch set update (PSU). This PSU 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.005

· 11.1.2.4.007

· 11.1.2.4.008

· 11.1.2.4.010

· 11.1.2.4.011

· 11.1.2.4.014

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.016, Essbase 11.1.2.4.016, and Provider Services 11.1.2.4.016 are supported for use with Essbase Studio 11.1.2.4.016.

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
· 25065147	When executing a Drill-Through Report on cells with higher aggregate levels results in an error and the report is not generated.
· 23521633	Essbase Studio Console reports an incorrect version in the Add/Remove Program.

Known Issues in this Patch

If one or more drill-through reports are created in the root of the Metadata navigator, then following error will be displayed when attempting to run a drill-through report from Smart View:

Cannot perform cube view operation. String index out of range:-1

Workaround: Create drill-through reports in a subfolder.

(25777166)

Applying this Patch

The section includes important information about installing this patch of Essbase Studio.

Component	Patch ID
Essbase Studio Console MSI	25225885
Essbase Studio Server	25225889

Essbase Studio Console

To apply this patch to the Essbase Studio Console:

1. Run the EssbaseStudioConsole.exe file, pick a destination folder, and complete the installation.

Essbase Studio Server

To apply this patch to the Essbase Studio Server:

1. Stop Essbase Studio Server.

2. Download and unzip the downloaded patch file, <PATCH FILE NAME>.zip, to the <EPM_ORACLE_HOME>/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

NOTES:

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

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 Studio after applying the patch.

3. From a command line, change the directory to <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 Essbase Studio and Provider Services are installed on different machines, then copy the cpld.jar file from the Essbase Studio machine to the Provider Services machine as follows:

a. On the machine where APS is running, stop the EPM system.

b. Copy the cpld.jar file from the Essbase Studio machine to the APS machine.

This file can be found in a location similar to the following on the Essbase Studio machine:
\Oracle\Middleware\EPMSystem11R1\common\essbase-studio-sdk\11.1.2.0\lib
Copy it to the similar location on the Provider Services machine.

NOTE: The file is not platform dependent and can be copied between different operating systems.

6. Re-start Essbase Studio Server.

7. Update the Essbase Studio catalog:

You must update the Essbase Studio catalog in order to use it with this patch. This is accomplished by issuing the “reinit” command in the Essbase Studio command line client, as described below.

a. Go to <MIDDLEWARE_HOME>/user_projects/epmsystem1/bin.

b. Call startEssbaseStudioCommandLineClient.bat/sh to start the Essbase Studio command line client.
A command window called the CPL Shell is displayed.

c. At the prompt, enter a valid admin user name and password.
NOTE: You must have Essbase Studio administrator privileges to use the reinit command.

d. At the prompt, enter the following command:
reinit

e. Type exit to close the CPL Shell.

The Essbase Studio catalog is now ready for use.

Rolling Back this Patch

Essbase Studio Console

To remove this patch for Essbase Studio Console:

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

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

3. Re-install the console using the previous version of the Essbase Studio Console Installer.

Essbase Studio Server

To roll back this patch on Essbase Studio Server:

1. Stop Essbase Studio Server.

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

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

4. If you performed copy of the cpld.jar file in step 5 when applying the patch, restore the backup copy of cpld.jar to the APS machine.

5. Restart Essbase Studio Server.

6. Update the Essbase Studio catalog:

You must update the Essbase Studio catalog in order to complete a roll back of this patch. This is accomplished by issuing the “reinit” command in the Essbase Studio command line client, as described below.

a. Go to <MIDDLEWARE_HOME>/user_projects/epmsystem1/bin.

b. Call startEssbaseStudioCommandLineClient.bat/sh to start the Essbase Studio command line client.
A command window called the CPL Shell is displayed.

c. At the prompt, enter a valid admin user name and password.
NOTE: You must have Essbase Studio administrator privileges to use the reinit command.

d. At the prompt, enter the following command:
reinit

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_29

UNIX/Linux:

./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_29 –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

Running Essbase Studio Release 11.1.2.4.016 with BI Release 12.2.2 to Enable Drill-through Reports

Essbase Studio is not provided with Essbase Release 12.2.2. To use Essbase Studio to deploy Essbase cubes and enable drill-through functionality with BI 12.2.2, you must install EPM 11g on a separate host and complete some configuration steps.

To install and configure Essbase Studio 11.1.2.4.016 with Essbase 12.2.2:

1. Install EPM 11.1.2.4 and apply the latest Opatch.

2. Install BI 12.2.2 on a different host.

3. Update the Essbase Studio server properties file with

server.trustedAuthenticationHost=<HOSTNAME>:<PORT>, where HOSTNAME is the host where Essbase is running, and PORT is the Essbase port.

Note: The server.properties file is located in
ORACLE_INSTANCE/EssbaseStudio/essbasestudio1/bin in the EPM 11.1.2.4 environment.

4. Stop and restart Essbase Studio server.

5. Stop the BI instance.

6. Copy cpld.jar from 11.1.2.4 EPM:

${EPM_ORACLE_HOME}/common/essbase-studio-sdk/11.1.2.0/lib

to BI12c:

${MIDDLEWARE_HOME}/user_projects/domains/${DOMAIN_NAME}/lib

7. Start BI

Limitation:

Each BI 12c domain only supports a single Essbase agent and Studio Server can develop trust to one BI Domain. In order to support multiple BI Domains with Essbase Studio you must deploy multiple instances of the Studio Server within your EPM deployment.

New Essbase Studio server.properties settings added in 11.1.2.4.016

server.dt.replaceParameters=true

When server.dt.replaceParameters is set to true, Essbase Studio uses standard SQL rather than parameterized SQL. Consider using this setting when a drill-through report with template SQL works at lower levels in the hierarchy, but fails at higher levels. The default setting is false.

server.essbase.extraDebugInfo=true

When server.essbase.extraDebugInfo is set to true, Essbase Studio displays messages in the Essbase Studio server.log file related to executing drill-through reports. The default setting is false.

Note: Oracle recommends that when server.essbase.extraDebugInfo is set to true, you set the logging level for Essbase Studio server to INFO in the logging.xml file. INFO is the default setting for logging level.

Incorrect Statement About Solve Order in the Essbase Studio User's Guide

The Release 11.1.2.4 Essbase Studio User's Guide incorrectly states that the member with the highest solve order number is evaluated first. The opposite is true: the member with the lowest solve order number is evaluated first.