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

· 11.1.2.3.001

· 11.1.2.3.002

· 11.1.2.3.003

· 11.1.2.3.500

· 11.1.2.3.501

· 11.1.2.3.502

· 11.1.2.3.503

· 11.1.2.3.505

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.3.507, Essbase 11.1.2.3.508, and Essbase Studio 11.1.2.3.507 are supported for use with Essbase Administration Services 11.1.2.3.508.

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
· 20685694	Connecting to an Essbase database using the EAS URL fails with connection reset on load balancer (reverse proxy).
· 20424038	Using an 11.1.2.3.500 rules file that is saved to a local machine can result in the dimension build to fail.
· 20262953	In some non-English languages, users are unable to enable DTS in an outline.
· 19932479	The EAS console for 11.1.2.3.50x is unable to connect to an 11.1.2.1 Essbase server.
· 19877341, 18769503	After applying the EAS 11.1.2.3.500 patch, EAS will not connect to an 11.1.1.3 Essbase server.
· 19848651	EAS outline editor does not display the range details of varying attribute with JRE 1.7.0_65.
· 19692775	The Find Member in the EAS Outline Editor does not work properly if a default alias table is selected.
· 19631311	The EAS console does not work with JRE 1.6.0.65.
· 19614752	In EAS, the sort order of a user list is not what is expected after you highlight one of the user items and edit.
· 18959073	In the Shared Services screen, the "Back" and "Help" buttons are not legible.

Known Issues in this Patch

None at this time.

Applying this Patch

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

Component	Patch ID
HYPERION ESSBASE ADMINISTRATION SERVICES CLIENT MSI	20183719
HYPERION ESSBASE ADMINISTRATION SERVICES SERVER	20183747

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.

Documentation Updates

None at this time.

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