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

· 11.1.2.1.103

· 11.1.2.1.104

· 11.1.2.1.105

· 11.1.2.1.106

Prerequisites

Required Microsoft Patch

Microsoft has identified a security issue that could allow a hacker to compromise your Windows-based system. You MUST install the Microsoft VC 2005 SP1 ATL redistributable pack before applying this patch.

The updated VC 2005 redistributable is available here for both x86 (32-bit) and x64 (64-bit):

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

Other Required Patches

· The 11.1.2.1.107 Administration Services Console and 11.1.2.1.107 Administration Server are both required for this release.

· You must install Essbase runtime client 11.1.2.1.107 on the same machine as Administration Server 11.1.2.1.107.

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
• 17852223, 17739974	After Java 7 Update 45 has been updated, EAS console cannot start via Web Launcher.
• 16471592	Administration Services support for JRE 1.7

Applying this Patch

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

Component	Patch ID
Administration Console	17545124
Administration Server	17545122

Administration Services Console

To apply this patch to the Administration Services console:

1. Stop all EPM products running on the machine hosting Administration Services 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 Administration Services Console.

Administration Server

To apply this patch to the Administration Server:

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

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.

6. Restart Administration Server.

Rolling Back this Patch

Administration Services Console

To roll back a patch on Administration Services Console:

1. Stop all EPM products running on the machine hosting Administration Services 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 EPM System products.

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_21

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_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