Oracle Hyperion Enterprise Performance Management Workspace
[NOTE TO WRITERS: Go to the File or Document properties and change the “title.” The correct entry for “Author” and “Company” are provided in the template.]
Release 11.1.2.1.000 Patch Set Update (PSU): 11.1.2.1.600
Readme
Why do I get the following patch conflict error message when running OPatch?
Why do I get the OUI-67078 warning message when applying OPatch?
How can I find out which releases and patches of EPM System products are installed in a deployment?
This Readme file describes the defects fixed in this patch and the requirements and instructions for applying this patch.
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.
This is a patch set update (PSU). This PSU replaces files in the existing installation and does not require a full installation.
This is a standalone patch and it does not include previous patches.
[NOTE TO WRITERS: Add a sentence stating whether the patch Requires a full installation or a partial replacement. if it’s a partial replacement, The boilerplate for this statement is: “This patch replaces files in the existing installation and does not require a full installation.”]
[note to writers: State whether this is a cumulative or standalone Patch. If it’s cumulative, list the previous Patch IDs (XXXXXXXX) that are included. To find previous patch IDs, either Ask your team or look for the patch id in uninstall section of previous Readme. If Standalone, state that this patch does not include previous patches.]
You can apply this patch to the following releases:
11.1.2.1.000
[NOTE TO WRITERS: list the base Release(s) from which you can apply this patch and Include any prerequisite patches. TO refer to service fixes or service packs using the old nomenclature, use the fully qualified service fix/service pack version number along with the patch id, for example, 11.1.2.0.07 (12345678).]
[NOTE TO WRITERS: THis required MICROSOFT PATCH INFORMATION should be included in the following product readmes (FM, EPMA, HSF, FDM, Planning, Production Reporting, EAS) unless the patch is issued only on unix or linux platforms. Other products can delete this section.]
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
[NOTE TO WRITERS: Delete the windows and unix sections as appropriate based on what platforms the patch is for.]
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.”
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.
[NOTE TO WRITERS: State whether this patch IS being released on all platforms OR list the supported platforms.
If being released on all platforms, say “Applies to all supported platforms.”
If being released on one specific platform, list that platform (with no introductory text).
If being released on more than one specific platform, put the platforms in a bulleted list (with no introductory text). For example:
· Microsoft Windows (32-bit)
· Microsoft Windows x64 (64-bit)
· Oracle Solaris SPARC (64-bit)
· Linux x86
· Linux x86-64
· HP-UX Itanium
· IBM AIX on POWER Systems (64-bit)
This way of listing supported platforms is required for consistency in the Defects Fixed Finder.]
This patch supports all languages supported by Oracle Enterprise Performance Management System Workspace 11.1.2.1.000.
[NOTE TO WRITERS: State whether this patch IS being released on all languages OR list the supported languages. If ENGLISH ONLY, State "This patch supports English only."]
[NOTE TO WRITERS: present this list in a table format.
[NOTE TO WRITERS: do not copy descriptions from bug db. they need to be rewritten to be meaningful from the customer point of view.]
[NOTE TO WRITERS: Verify that the Defects Fixed list in the Readme includes: (1) All customer-reported defects regardless of severity; (2) All Sev 1, 2, and 3 defects whether customer reported or not; (3) Sev 4 at discretion of team.
NOTE: For Sev 3, non-customer-reported defects: The objective is to let customers know what areas of the product were touched in the patch, so they know what areas to test. Use your discretion for Sev 3 defects that are clearly internal and would not be in an area that customers would need to test.
Security vulnerabilities are not typically included. The guideline is: If a security bug is reported by a customer and if the issue is fixed across the EPM suite, then we can include that bug in the readme. Otherwise - if the problem is fixed in one product but still exists in other products - we can’t include them in the readme.]
The text in the first
column of the table must start with a bullet in order for the import into the
Defects Fixed Finder tool to work correctly. Like so:
|
Defect Number |
Defect Fixed |
|
• 14032287 |
IE9: Browser stops responding when trying to drag content in workspace page. |
|
• 14032275 |
IE9: Issue with menus that don't have sub-menus. |
|
• 13771377 |
Need logging around css calls |
|
• 14162288 |
Js errors displayed when accessed create / edit-users/groups/role |
|
• 14097591 |
FF8: Drop-down menu preferences is not displayed properly |
|
• 14399691 |
IE9: Receive "permission denied" when flipping between planning modules |
[NOTE TO WRITERS: This section is required. If the patch doesn’t have any known issues, INCLUDE THIS SENTENCE.]
[NOTE TO WRITERS: Per Legal: This sentence must be included IF THERE ARE KNOWN ISSUES.]
The section includes important information about applying this patch for Oracle Hyperion Enterprise Performance Management System Workspace.
[NOTE TO WRITERS: Make sure that instructions for applying the PATCH indicate specifically which components are being patched and which machines in a distributed installation should be patched. for example, “on the machine hosting the shared services web application, …”]
[NOTE TO WRITERS: For web applications, make sure you provide instructions for all supported application servers.]
To apply this patch:
1. Shut down all services and servlet instances related to the Oracle Hyperion Enterprise Performance Management System Workspace 11.1.2.1.000 installation.
2. 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.
NOTE: Determine the ORACLE_HOME and MIDDLEWARE_HOME for your installation prior to continuing the next step. By default, MIDDLEWARE_HOME is C:\Oracle\Middleware\ on windows and "$HOME/Oracle/Middleware/" on UNIX. EPM_ORACLE_HOME is <MIDDLEWARE_HOME>\EPMSystem11R1 on Windows and <MIDDLEWARE_HOME>/EPMSystem11R1 on UNIX.
3. On EPM Workspace machine, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.
4. To apply the patch, enter the following command on one line:
[NOTE TO WRITERS: very important! the jdk version in the apply command is different for 11.1.2.0, 11.1.2.1, and 11.1.2.2. change the jdk160_xx directory as follows:
11.1.2.2: jdk160_29
11.1.2.1: jdk160_21
11.1.2.0: jdk160_11
The example here is for 11.1.2.2.
Windows:
opatch.bat apply <EPM_ORACLE_HOME>\OPatch\14119724
-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.
UNIX/Linux:
./opatch apply <EPM_ORACLE_HOME>/OPatch/14119724 -oh <EPM_ORACLE_HOME> -jre <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.
5. Restart Oracle Hyperion EPM services and servlets.
6. All users should now clear cached files from their browsers.
To roll back a patch:
1. Shut down all services and servlet instances related to Oracle Hyperion Enterprise Performance Management System Workspace 11.1.2.1.000 installation.
NOTE: Determine the EPM_ORACLE_HOME and MIDDLEWARE_HOME for your installation prior to continuing the next step. By default, MIDDLEWARE_HOME is C:\Oracle\Middleware\ on windows and "$HOME/Oracle/Middleware/" on UNIX. EPM_ORACLE_HOME is <MIDDLEWARE_HOME>\EPMSystem11R1 on Windows and <MIDDLEWARE_HOME>/EPMSystem11R1 on UNIX.
2. On EPM Workspace machine, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch (by default, Oracle/Middleware/EPMSystem11R1/OPatch).
[NOTE TO WRITERS: very important! the jdk version in the apply command is different for 11.1.2.0, 11.1.2.1, and 11.1.2.2. change the jdk160_xx directory as follows:
11.1.2.2: jdk160_29
11.1.2.1: jdk160_21
11.1.2.0: jdk160_11
The example here is for 11.1.2.2.
3. To roll back the patch, enter the following command on one line:
Windows:
opatch.bat rollback -id 14119724 -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.
UNIX/Linux:
./opatch rollback -id 14119724 -oh <EPM_ORACLE_HOME> -jre <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.
4. Restart Oracle Hyperion EPM services and servlets.
5. All users should now clear cached files from their browsers.
[NOTE TO WRITERS: IF THIS PATCH INCLUDES CHANGES TO A JAVASCRIPT FILE, YOU NEED TO INCLUDE THE STEP ABOVE AS A FINAL STEP. IF IT DOESN’T, DELETE THIS STEP.]
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.
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.
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:
[NOTE TO WRITERS: very important! the jdk version in the apply command is different for 11.1.2.0, 11.1.2.1, and 11.1.2.2. change the jdk160_xx directory as follows:
11.1.2.2: jdk160_29
11.1.2.1: jdk160_21
11.1.2.0: jdk160_11
The example here is for 11.1.2.2.
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
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
Copyright © 2012, Oracle and / or its affiliates. All rights reserved. http://www.oracle.com