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.

This is a cumulative patch (PSU) and includes 11.1.2.1.502PSU (13862417)

Supported Paths to this Patch

This patch can be applied to release 11.1.2.1.00, 11.1.2.1.501 and 11.1.2.1.502

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/downloads/details.aspx?familyid=766A6AF7-EC73-40FF-B072-9112BAB119C2&displaylang=en

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:

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

Supported Platforms

· Microsoft Windows (32-bit)

· Windows 64-bit running in 32-bit emulation mode.

Note: This is the first release that has official support of Internet Explorer 9.0.

Supported Languages

This patch is supported for English only.

Defects Fixed in this Patch

Defect Number	Defect Fixed
• 14659145	UpCheckvalidation does not work in multi-load / journals
• 14496246	Exporting validaiton rules gives time out error
• 14205258	Non-Admin users get kicked out when exporting process explorer questions
• 16635484	Process Explorer Certification/Assessment for YE appear 1 period late when using a non-default Fiscal Start Period.

Defects Fixed in Patch 11.1.2.1.502 (13862417)

Defect Number	Defect Fixed
• 14018222	Data import ERPI-FIN-D is intermittently closing the connection to FDM in the list.
• 14018167	Internet Explorer 9 is crashing and getting script errors.
• 13956551	Data protection produces "unknown error in HSVDATA object".
• 13811149	The Batchaction event script does not execute when running batch from upsShell.
• 13794139	Drill back fails from Smart View to FDM.
• 13634506	When launching the FDM URL, the error message "Error retrieving security agent header" is displayed.
• 13611500	An error message, "Error Stream Failed, Invalid file path provided" is displayed, when viewing the .err log file jv exp.
• 13591000	Data protection issues occur when writing to files.

Defects Fixed in Patch 11.1.2.1.501 (12795642)

Defect Number	Defect Fixed
• 12814913	Add support for the new ERPI adapter version ERPI-FIN-D.
• 12747233	Non-administrator users are logged out when exporting an undefined map to Microsoft Excel.
• 12558253	Add support for full fresh execution mode to ERPI adapter.
• 10379010	Fixed a bug that prevented HTML tags from processing correctly in the Intersection Validation report.

Known Issues in this Patch

The following issues are the noteworthy known issues of this patch.

· FDM does not support real time replication of the application file share, including but not limited to NAS, Client for NFS on Windows, or 3rd party replication software

The recommended backup strategy for the FDM file share is to back up during off hours.

Applying this Patch

The section includes important information about applying this patch for FDM.

To apply this patch:

1. Download and unzip the downloaded patch file, 16582335_11121_WINNT.zip, to the <EPM_ORACLE_HOME>/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

NOTE: 16582335_11121_WINNT.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.

2. Stop the FDM Task Manager service.

3. Stop the HyperionFDMAppPool application pool in IIS.

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

5. To apply the patch, enter the following command on one line:

opatch.bat apply <EPM_ORACLE_HOME>\OPatch\16582335 -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.

6. Start the FDM Task Manager service.

7. Start the HyperionFDMAppPool application pool in IIS.

Rolling Back this Patch

To roll back a patch:

1. Stop the FDM Task Manager service.

2. Stop the HyperionFDMAppPool application pool in IIS

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

4. To roll back the patch, enter the following command on one line:

Windows:

opatch.bat rollback -id 16582335 -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.

5. Start the FDM Task Manager service.

6. Start the HyperionFDMAppPool application pool in IIS.

7. All users should clear cached files from their browsers.

Notes

Custom batch scripts should no longer include the commands to initialize the batch engine. FDM API does this automatically when the scripts are run using UPSSHELL. If you still include these commands in your script, the script may not run correctly and you do not get the expected results.

The commands that need to be removed from scripts are:

Dim BATCHENG

Set BATCHENG = CreateObject("upsWBatchLoaderDM.clsBatchLoader")

BATCHENG.mInitialize API, SCRIPTENG

Troubleshooting FAQs

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:

opatch.bat lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_29

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.