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

· 11.1.2.4.010

· 11.1.2.4.012

· 11.1.2.4.013

· 11.1.2.4.015

· 11.1.2.4.016

· 11.1.2.4.020

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

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

Prerequisites

Required Microsoft Patch

Microsoft has identified a security issue that could compromise Windows-based systems. Before installing this patch, verify that the Visual C++ 2005 Redistributable Package installed on the computer is current. You may search and download the latest Visual C++ 2005 Redistributable Package from:

http://www.microsoft.com/en-us/download/default.aspx

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
· N/A	There are no fixed defects for this patch.

Known Issues in this Patch

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)

Applying this Patch

The section includes important information about installing this patch of Administration Services.

Component	Patch ID
HYPERION ESSBASE ADMINISTRATION SERVICES CLIENT MSI	28285134
HYPERION ESSBASE ADMINISTRATION SERVICES SERVER	28285151

Administration Services Console

To apply this patch to the Administration Services Console:

1. Uninstall the Administration Services Console.

2. Run the EASConsole.exe file, pick a destination folder, and complete the installation.

Administration Server

To apply this patch to the Administration Server:

1. Stop all EPM System products running on the machine hosting Administration Server.

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

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

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_35

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.

6. Restart Administration Server.

Rolling Back this Patch

Administration Services Console

To roll back a patch on Administration Services Console:

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 Administration Services console.

Administration Server

To roll back this patch on Administration Server:

1. Stop all EPM products running on the machine hosting Administration Server.

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_35

3. Delete the temporary directories. To roll back 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.

4. Restart EPM System products.

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

Expanding an Essbase Application Group in Shared Services

Before 11.1.2.4.020, when expanding an Essbase Application Group in Shared Services, right clicking on an Essbase Application and then choosing Assign Access Control takes a long time for the next screen to load and some icons are broken. A fix was introduced in 11.1.2.4.020 but to see the full fix requires implementing of one of the below options for the fix to work.

1)Adding a java option to provide the URL
The user has to add the java option "workspaceurl" to their startup script or windows registry depending upon how they start EAS and provide the value from the URL they use to launch shared services/workspace from their client system.

If the user starts EAS using script startEssbaseAdminServices.bat(sh) or start.bat(sh) from %EPM_ORACLE_INSTANCE%\bin then they have to add this java option in the file setCustomParamsEssbaseAdminServices.bat(sh) in set JAVA_OPTIONS section. This file is present at %EPM_ORACLE_INSTANCE%\bin\deploymentScripts and if they are starting EAS as a service from a windows m/c they have to add this java option in windows registry.

Example:
-Dworkspaceurl=<protocol>://<host>:<port>/interop
where
protocol:https or https
host:hostname in the url used to launch workspace from client system
port:port in the url used to launch workspace from client system

Like below
-Dworkspaceurl=http://slc05zss.us.oracle.com:19000/interop

2)Edit EPM registry using epmsys_registry.bat( or .sh if it is Linux)

We have added a new property "workspaceurl" to ADMIN_SERVICES_LWA programmatically and set it's initial value as empty(""). The customer can update the value of this property using epm registry utility to the URL that they use to launch Shared Services. The advantage of this way of providing the url compared to java option is that this doesn't require a restart of EAS server.

To implement workaround follow the steps below,

Modify epm registry to update the values of "workspaceurl" property of component "ADMIN_SERVICES_LWA" with the value used in the URL to launch shared services from client machine.

Use epmsys_registry.bat/.sh available at
<MIDDLEWARE_HOME>\user_projects\epmsystem1\bin to perform the above step.

The syntax of the command to update property,

epmsys_registry.bat updateproperty #<objectIDOfComponent>/@<propertyname> "propertyvalue"

For ex:

epmsys_registry.bat updateproperty #3b09532ccf7bd2ea7502df7d15d55342018S7f58/@workspaceurl

(25801104)