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 the issue described in the Readme matches the issue that you are encountering. Review the Bug Number referenced in the Readme for additional information.

· 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) that replaces files in an existing installation and does not require a full installation.

In addition to the bugs fixed in this PSU (see Defects Fixed in this Patch section), this patch set update consists of bug fixes made available through the following PSUs/PSEs:

· PSE Release 11.1.2.1.600 Patch 14740171

· PSE Release 11.1.2.1.600 Patch 14800313

Supported Paths to this Patch

You can apply this patch to Release 11.1.2.1.600 or to instances patched with the following Shared Services releases:

· Release 11.1.2.1.600 Patch 14740171

· Release 11.1.2.1.600 Patch 14800313

Do not apply this patch to Release 11.1.2.1.00.

Prerequisites

Required Microsoft Patch

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 can be applied to all platforms supported in release 11.1.2.1.00.See the Release 11.1.2.x Certification Matrix for a list of supported platforms.

Supported Languages

This patch supports all locales supported in Release 11.1.2.1.00.

Defects Fixed in this Patch

Defect Number	Defect Fixed
• 16728046	After generating a report using the View Report option, Shared Services does not allow you to change the Filter By option for subsequent reports.
• 16825199	In localized deployments, an error message is displayed in English when users attempt to log into EPM Workspace using a locked MSAD account.
• 16914238 16165824	Lifecycle Management fails to migrate all the data if the data set size exceeds 2GB.
• 17421110	Taskflow execution does not occur at the time specified in the taskflow schedule.
• 17488547	After a database connection timeout, users provisioned using external groups experience limited access to EPM System.

Defects/Enhancements Fixed in PSU 11.1.2.1.600 Patch 14740171

Defect Number	Defect Fixed
• 14678049	Users indirectly provisioned (through groups ) with the Shared Services Administrator role are unable to perform Lifecycle Management export of taskflows.

Defects/Enhancements Fixed in PSU 11.1.2.1.600 Patch 14800313

Defect Number	Defect Fixed
• 14659391	Essbase performs poorly if DB2 is set to use SERVER_ENCRYPT.
• 14338310	Essbase fails to start if DB2 is set to use SERVER_ENCRYPT.

Known Issues in this Patch

This patch does not contain any known issues.

Applying this Patch

This section includes important information about applying this patch for Shared Services.

To apply this patch:

1. Stop Foundation Services and other EPM System components and processes, including custom programs that use EPM System APIs.

2. Perform these steps on each machine that hosts EPM System components.

a. Download and unzip the downloaded patch file, 17734704.zip, to the EPM_ORACLE_HOME/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

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

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

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

Windows:

opatch.bat apply EPM_ORACLE_HOME/OPatch/17734704 -oh EPM_ORACLE_HOME -jdk 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.

UNIX/Linux:

./opatch apply EPM_ORACLE_HOME/OPatch/17734704 -oh EPM_ORACLE_HOME -jdk MIDDLEWARE_HOME/jdk160_21 -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.

3. Optional: If Essbase performs poorly because DB2 is set to use SERVER_ENCRYPT (bug 14659391).

a. Ensure that the value of AUTHENTICATIONMETHOD property in the JDBC URL specified in EPM_ORACLE_INSTANCE/config/foundation/11.1.2.0/reg.properties is defined as follows:

AUTHENTICATIONMETHOD\=EncryptedPassword

Note: The default EPM_ORACLE_INSTANCE location is $HOME/Oracle/Middleware/user_projects/epmsystem1

b. If the value of AUTHENTICATIONMETHOD is set to ClearText, complete these steps:

i. Create a backup copy of EPM_ORACLE_INSTANCE/config/foundation/11.1.2.0/reg.properties.

ii. Using a text editor, edit reg.properties and set the value of AUTHENTICATIONMETHOD property as follows:
AUTHENTICATIONMETHOD\=EncryptedPassword

iii. Save and close reg.properties.

4. If Foundation Services is deployed on WebSphere application server, redeploy the Shared Services web application. See "Deploying EPM System Products to WebSphere Application Server" in the Oracle Enterprise Performance Management System Installation and Configuration Guide for instructions.

5. Start Foundation Services and other EPM System components and processes, including custom programs that use EPM System APIs.

Rolling Back this Patch

To roll back a patch:

1. Stop Foundation Services and other EPM System components and processes, including custom programs that use EPM System APIs.

2. Perform these steps on each machine that hosts EPM System components.

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

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

Windows:

opatch.bat rollback -id 17734704 -oh EPM_ORACLE_HOME -jdk 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.

UNIX/Linux:

./opatch rollback -id 17734704 -oh EPM_ORACLE_HOME -jdk MIDDLEWARE_HOME /jdk160_21 -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.

3. Optional: If you modified EPM_ORACLE_INSTANCE/config/foundation/11.1.2.0/reg.properties to fix bug 14659391, restore it using the backup copy that you created while applying the patch.

4. For WebSphere application server only: If you redeployed the Shared Services web application after applying the patch, redeploy the restored web application. See "Deploying EPM System Products to WebSphere Application Server" in the Oracle Enterprise Performance Management System Installation and Configuration Guide for instructions.

5. Start Foundation Services and other EPM System components and processes, including custom programs that use EPM System APIs.

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