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

· 11.1.2.1.102

· 11.1.2.1.103

· 11.1.2.1.104

· 11.1.2.1.105

· 11.1.2.1.106

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
· 17852217	There are two new global methods to clean up the deployment history for each cube. Usage: Open the Studio command line client and enter: call 'util'::'globalCleanModelHistoryAndLeaveLastSucc'(): It will keep the most recent (last) successful deployment record for each cube If a cube, however, had never been deployed successfully, all its deployment history records will be removed. OR call 'util'::'globalCleanModelHistory'(): It will remove all deployment records no matter they are successful or failure.
· 17530256	Never consolidate operator is enabled for ASO outlines. Note: Aggregate storage outlines require all members of stored hierarchies to have ADD (+) aggregation, except for label-only members and their children. See Known Issues 17892407 below.
· 17466314	Essbase Studio does not allow setting a hierarchy as stored when all children have consolidation property as ignored (~) for an ASO cube.
· 16750764	Some deployments failed with TaskOutOfMemoryException error in case of multiple deployments into the same application with option drop database.
· 16702848	An EPMA-Essbase Application when deployed with a member with multiple UDAs, the deployment is successful in Essbase but only one UDA out of two UDAs is deployed.
· 16608915	When there is a recursive hierarchy where the level is set to a non zero value, then in some cases a drill through report will return incorrect values.
· 16556333	Unable to re-import XML file if a text file data source contains a filename with the character '&'.

Known Issues in this Patch

· If you install Essbase Studio 11.1.2.1.107, start Essbase Studio Server for the first time, and then issue a reinit command, the command fails and returns an error. The workaround for this issue is to stop and restart Essbase Studio Server. (14747771)

· For ASO outlines, Studio allows consolidations such as Never Share or Ignore Member anywhere in outline without validation for Essbase restrictions. Deployment will fail if such consolidations are applied to the members that are NOT label-only members and their direct children. (17892407)

Applying this Patch

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

Component	Patch ID
Essbase Studio Console	17545096
Essbase Studio Server	17545104

Essbase Studio Console

To apply this patch to the Essbase Studio Console:

1. Stop Essbase Studio Console.

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

NOTE: <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 Essbase Studio Console.

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

NOTE: <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 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_21

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_21 -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. Re-start Essbase Studio Server.

6. 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 start_BPMS_bpms1_CommandLineClient.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 roll back this patch for Essbase Studio Console:

1. Stop Essbase Studio Console.

2. From a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.

Enter the following command:

opatch.bat rollback –id <patch_id> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_21

3. Restart Essbase Studio Console.

Essbase Studio Server

To roll back this patch on Essbase Studio Server:

1. Stop Essbase Studio 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_21

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

3. Restart Essbase Studio Server.

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

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

g. Call start_BPMS_bpms1_CommandLineClient.bat|sh to start the Essbase Studio command line client.
A command window called the CPL Shell is displayed.

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

i. 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_21

UNIX/Linux:

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