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 is a cumulative patch. The complete product EARs are shipped.

Supported Paths to this Patch

Apply this patch to the following release:

o 11.1.2.2.500

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

Other Required Patches

There are no other required patches.

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

This patch applies to all supported platforms.

Supported Languages

This patch is supported for English only.

Defects Fixed in this Patch

Defect Number	Defect Fixed
· 19631154	[Performance Improvement] Account Reconciliation Manager has "java.lang.OutOfMemory" errors even after applying the patch 19576777.
· 19569801	In Account Reconciliation Manager, you are unable to delete custom attributes.
· 19563765	[Performance Improvement] Account Reconciliation Manager has "java.lang.OutOfMemory" errors even after applying the patch 19384470.
· 19072653	When you log on to Close Manager, UI hangs and throws error on some locales.
· 19247521	In Account Reconciliation Manager, members of a viewer group can see and open reconciliations, but they cannot see any prior reconciliations listed in the Prior Reconciliations tab.
· 19446320	In Account Reconciliation Manager, when you run a data load for reconciliations under two different locations, the reconciliations view displays two rows for the same currency.
· 17271570	In Account Reconciliation Manager, date formatting is not locale sensitive for some locales.
· 18698386	In Close Manager, when you import a template from CSV file having task questions of type List, the list values imported do not show up.
· 17381921	In Account Reconciliation Manager, when you have single currency setting, the auto reconciliations routine closes the reconciliations improperly.
· 20162432	In Account Reconciliation Manager, when you delete a reconciliation, it takes an unusual long time to delete.
· 18907089	In Close Manager, when you export a template, the Group or Team assigned the Task Owner role exports as User ID invalid.
· 19366944	[Performance Improvement] Account Reconciliation Manager shuts down unexpectedly on SQL Server with "java.lang.OutOfMemory" error.

Known Issues in this Patch

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

General Financial Close Management Issues

Application Access

Defect Number	Known Issues
· 11869333, 11922789	Financial Close Management forces WebLogic to check for JSP Pages.

Internet Explorer 7/8

Defect Number	Known Issues
· 9356443	Under certain heavy load conditions, a user session may freeze when using Internet Explorer. Workaround: Increase OHS: KeepAliveTimeout to 61 seconds.

ADF

Defect Number	Known Issues
· 13366076	In the View menu, you cannot scroll to the bottom of the list using "Scroll to last" of the tree table.
• 14695470	The time zone of some countries has been changed; therefore, the time zone displayed is not correct.

Close Manager Issues

Dashboard

Defect Number	Known Issues
· 8921652	Status Chart and Overview portlets do not swap when you drag in Internet Explorer.
· 9761181	An error message may be displayed if the user attempts to drill into the Alerts bar in the Status Chart control after printing the control.

Task Details

Defect Number	Known Issues
· 16746240	If an open task is assigned to an external user who no longer exists in the directory, you cannot edit the task. Workaround: Delete the task and recreate the task with a different user assignment.

Defect Number

Known Issues

· 16746240

If an open task is assigned to an external user who no longer exists in the directory, you cannot edit the task.

Workaround: Delete the task and recreate the task with a different user assignment.

Schedules

Defect Number	Known Issues
· 16745794	When a user imports a schedule from a template using a time zone different from the server time zone, the start date and time are the same as the server, but should be the start date and time of the user.

Task Action

Defect Number	Known Issues
· 16935604	When you launch the Task Actions Dialog from email, the dialog does not close after you select an action. Workaround: Close the browser window.

Defect Number

Known Issues

· 16935604

When you launch the Task Actions Dialog from email, the dialog does not close after you select an action.

Workaround: Close the browser window.

Smart View

Defect Number	Known Issues
· 14780216	In Close Manager, when you open the alerts tab you receive a null pointer exception. Workaround: On the Smart View Task Actions window, click on Actions, and then Refresh before you open the Alerts tab.

Defect Number

Known Issues

· 14780216

In Close Manager, when you open the alerts tab you receive a null pointer exception.

Workaround: On the Smart View Task Actions window, click on Actions, and then Refresh before you open the Alerts tab.

General

Defect Number	Known Issues
· 14382235	When you use the Esc key in various manage dialogs, bad or loss of data occurs.

Account Reconciliation Manager Issues

Security

Defect Number	Known Issues
· 12962672	Oracle Hyperion Shared Services Account Reconciliation Manager and Close Manager submenus list both Account Reconciliation Manager and Financial Close Management roles.

Installation

Defect Number	Known Issues
· 14390242	Account Reconciliation Manager roles and application are not available if only the Account Reconciliation Manager module is installed.

Setup

Defect Number	Known Issues
· 14368407	When you import a global integration token, which is dependent on a new attribute, the import fails.

· 15917071	Importing custom currency with replace all option, fails with array out of bounds error.

Reconciliation Actions

Defect Number	Known Issues
· 16051716	The ‘Currency bucket not enabled’ error during generate all should not appear on a single currency system since there is just one, single currency bucket.

ERPi Integration

Defect Number	Known Issues
· 15856161	If a scheduled data load is set to run at the same time as another data load that references the same location is running, the second data load should not run. This is in fact what is happening; however an error message should tell you that there is a data load error. The error message is not visible in the Task Scheduler UI. It can be retrieved from the Account Reconciliation Manager logs under <MIDDLEWARE_HOME>/user_projects/<INSTANCE_NAME>/diagnostics/logs/arm.

Defect Number

Known Issues

· 15856161

If a scheduled data load is set to run at the same time as another data load that references the same location is running, the second data load should not run.

This is in fact what is happening; however an error message should tell you that there is a data load error. The error message is not visible in the Task Scheduler UI. It can be retrieved from the Account Reconciliation Manager logs under <MIDDLEWARE_HOME>/user_projects/<INSTANCE_NAME>/diagnostics/logs/arm.

Applying this Patch

The section includes important information about applying this patch for EPM System Installer.

CAUTION: Confirm that ALL Prerequisites are completed prior to moving forward.

CAUTION: Because of the extensive database changes that result from applying this patch, rolling back the patch is not supported. Before you apply the patch, be sure to perform an entire system backup.

>To apply this patch:

1. All Financial Close Management patches should be installed on all the boxes that host the below managed servers:

o Financial Close Management managed server

o Foundation Services managed server

o Admin server

o SOA server

2. Confirm the environment is running properly.

Windows:

Go to Start, then Programs, then EPM System, then Foundation Services, then <INSTANCE_NAME>, and then Epm system diagnostic.

Linux:

Run this command:

<MIDDLEWARE_HOME>/user_projects/<INSTANCE_NAME>/bin/validate.sh).

3. Stop FinancialClose Managed Server, then stop the SOA Managed Server, and the Foundation Services Managed Server and then Admin Server.

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

5. On the Financial Close Management Managed server, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.

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

-jdk <MIDDLEWARE_HOME>/jdk160_29

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> -jdk <MIDDLEWARE_HOME>/jdk160_29 -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.

7. Ignore step 8 and 9 when Foundation Services Managed server and Financial Close Management Managed server are on the same machine.

8. On the Foundation Services Managed server(s), from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.

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

-jdk <MIDDLEWARE_HOME>/jdk160_29

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> -jdk <MIDDLEWARE_HOME>/jdk160_29 -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.

Post-installation Steps

1. At this point, you should have just run Opatch and all the servers are still shutdown. If not, please shut them down.

2. Start Admin Server, Foundation Services Managed Server, SOA managed server.

3. Wait for SOA Managed Server to be up and running.

4. On the Financial Close Management Managed server(s), open the command line window.

5. Set the environment variables:

Windows:

1. Set the EPM_ORACLE_INSTANCE environment variable by running the below command in the command line. Ensure that there is no space before and after =.

set EPM_ORACLE_INSTANCE=<MIDDLEWARE_HOME>\user_projects\<INSTANCE_NAME>

Example:

set EPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1

UNIX/Linux:

1. Set the EPM_ORACLE_HOME environment variable by running the below command in the command line based on shell.

setenv EPM_ORACLE_HOME <MIDDLEWARE_HOME>\EPMSystem11R1

export EPM_ORACLE_HOME=<MIDDLEWARE_HOME>\EPMSystem11R1

Example:

setenv EPM_ORACLE_HOME \Oracle\Middleware\EPMSystem11R1

2. Set the EPM_ORACLE_INSTANCE environment variable by running the below command in the command line based on shell.

setenv EPM_ORACLE_INSTANCE <MIDDLEWARE_HOME>\user_projects\<INSTANCE_NAME>

export EPM_ORACLE_INSTANCE=\Oracle\Middleware\user_projects\<INSTANCE_NAME>

Example:

setenv EPM_ORACLE_INSTANCE \Oracle\Middleware\user_projects\epmsystem1

6. Perform the below steps to set configure Logical Address for Web Applications:

a. Run EPM System Configurator: Select Programs, then Oracle EPM System, then Foundation Services, and then EPM System Configurator.

b. Unselect all the nodes and then under Hyperion Foundation, select "Configure Logical Address for Web Applications".

c. Verify that the host and port for Financial Close and Account Reconciliation Manager are set with your load balancer server’s host and port (if you utilize a load balancer; for example, OHS, IIS, or external load balancer).

d. If no change is made, click Cancel to exit the EPM System Configurator, otherwise click Next and then Finish to complete the configuration changes.

7. Run the database and SOA Deployment script:

NOTE: Make sure that the there are no errors displayed in the command window after execution of FCMPS2501 script. If there are any, go to the Troubleshooting section below before contacting Oracle Support.

In the same command line window, change the directory to <EPM_ORACLE_HOME>\products\FinancialCloseManagement-Common\scripts

Windows:

Run FCMPS2501.bat

Linux:

Run FCMPS2501.sh

8. Start Financial Close Managed Server.

9. After the patch has been applied, confirm the environment is running properly:

Windows:

Go to Start, then Programs, then EPM System, then Foundation Services, then epmsystem1, and then EPM System Diagnostic.

Linux:

Run this command: <MIDDLEWARE_HOME>/user_projects/<INSTANCE_NAME>/bin/validate.sh

10. All tests should display PASSED.

11. Validating Financial Close Management Configuration.

a. Launch the Close Manager validation tool from a web browser:

http://<FCMHOST>:<FCMPORT>/fcc/faces/oracle/apps/epm/fcc/ui/page/FCCValidation.jspx

Where FCMHOST is the name of the machine where FinancialClose0 managed server is configured

and where FCMPORT is the Listening port of FinancialClose0 managed Server in the WebLogic console.

The default FCMPORT is 8700.

b. Log on with Close Manager administrator credentials.

c. To validate the Close Manager configuration, click the Validate Close Manager Configuration button.

d. All results should have check marks instead of an X.

e. To run validate the test schedule, click Validate Test Scheduler.

f. All results should have marked with check marks instead of an X.

12. Validating Account Reconciliation Manager Configuration.

a. Launch the Account Reconciliation Manager validation tool from a web browser:

http://<FCMHOST>:<FCMPORT>/arm/faces/oracle/apps/epm/arm/ui/page/common/ARMValidation.jspx

Where FCMHOST is the name of the machine where FinancialClose0 managed server is configured

and where FCMPORT is the Listening port of FinancialClose0 managed Server in the WebLogic console.

The default FCMPORT is 8700Login with Account Reconciliation Manager administrator credentials.

b. Log on with Account Reconciliation Manager administrator credentials.

c. To validate the Account Reconciliation Manager configuration, click the Validate Account Reconciliation Manager Configuration button.

d. All results should have check marks instead of an X.

e. To run validate the test schedule, click Validate Test Scheduler.

f. All results should have marked with check marks instead of an X.

13. All users should now clear cached files from their browsers.

Troubleshooting

Opatch failed on Prerequisite check because LCMAMService-Client.jar is still active.

When Opatch is applied and Opatch checks the prerequisites, if you see the following error message:

Running prerequisite checks...

Prerequisite check "CheckActiveFilesAndExecutables" failed.

The details are:

Following files are active :

C:\Oracle\Middleware\EPMSystem11R1\common\FCMProxy\11.1.2.0\LCMAMService-Client.jar

ApplySession failed during prerequisite checks: Prerequisite check "CheckActiveFilesAndExecutables" failed.

System intact, OPatch will not attempt to restore the system

1. Verify that Shared Services is stopped and wait for 10 minutes, and then try to run OPatch again.

2. If you still get the same error, run a free utility from Microsoft called Process Explorer to detect the process holding local files.

>To run Process Explorer:

1. Download and extract the ZIP to a directory:

http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

2. Launch procexp.exe.

3. Accept the agreement message from Microsoft (first time only).

4. When Process Explorer is launched:

a. Navigate to View, and then Show Lower Pane.

b. Navigate to View Menu, then Lower Pane View, and then Handles.

5. To find which process is holding LCMAMSERVICE-CLIENT.JAR:

a. Click Find, and then Find Handle or DLL.

b. Mention LCMAMSERVICE-CLIENT.JAR in the Handle or DLL substring box.

c. Click Search, which lists the processes.

Failed to deploy SOA Composites by the script in post installation step

If you see any errors related to SOA composite deployment failure when running FCMPS2501.bat/sh (usually it will be shown as 'Failed to deploy FCCXXXComposite or ARMXXXComposite under the section Retire and Deploy CM SOA Composites/Retire and Deploy ARM SOA Composites) in FCMPS2501.log located at <EPM_ORACLE_HOME>\products\FinancialCloseManagement-Common\scripts.

1. Fix the reason behind the error e.g. you could check if the SOA server and admin server are up and running.

2. Set the environment variables as stated in Step 5 of Post Installation Steps Section.

3. In the same command line window, change the directory to <EPM_ORACLE_HOME>\products\ FinancialCloseManagement-Common\scripts.

4. Please run the FCMPS2501.bat/sh after setting the necessary environment variables

Data load fails from ExportToARM ODI scenario at the "IsCurrencyCodeExist" step with table or view not found error.

If data load fails from ExportToARM ODI scenario at the "IsCurrencyCodeExist" step with table or view not found error then run the below SQL Queries.

Note : In the below queries replace <ERPI_Schema> with the ERPI Schema Name and <ARM_Schema> with ARM Schema Name.

1. Log in to ARM schema and run following 3 queries.

o GRANT SELECT ON ARM_CURRENCIES TO <ERPI_Schema> ;

o GRANT SELECT ON ARM_DATALOAD_RULES TO <ERPI_Schema>;

o GRANT SELECT ON ARM_CURRENCY_BUCKETS TO <ERPI_Schema>;

2. Now login to ERPI schema and see if following query can be executed.

Select currency From <ARM_Schema>.ARM_Currencies;

After Applying this Patch, New Features Do Not Display in Financial Close Management

In some cases, the user interface may not reflect the new code applied by this patch.

To confirm this is not an issue:

· For Account Reconciliation Manager, the Account Reconciliation Manager Validation Tool should display the build version as 11.1.2.2.501.XXXX. See step 12 of the Post-Installation Steps to launch the Validation Tool.

· For Close Manager, the Financial Close Management Validation Tool should display the build version as 11.1.2.2.501.XXXX. See step 11 of the Post-Installation Steps to launch the Validation Tool.

If the build version does not display as 11.1.2.2.501.XXXX, follow these steps to force the user interface to display the new code by forcing WebLogic to check for JSP pages:

1. Open the WebLogic Administration Console (http://<SERVER>:<PORT>/console).

2. Go to Home, and then Deployments.

3. Expand Financial Close under deployments, select fcc, and then select the Configuration tab.

4. Update JSP Page Check (in seconds) to a non-negative number (for example, 1).

5. Save to update the deployment plan.

6. After saving, set the JSP Page Check (in seconds) to the original value (for example, -1).

Note: If you do not reset the value to -1, you may experience WebLogic performance issues.

7. Save again.

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:

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

Run:

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