Release 11.1.2.4.007 Patch Set Update (PSU): 26751072
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 defect 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 patch replaces files in the existing installation and does not require a full installation.
You can apply this patch to EPM System Release 11.1.2.4.006 (patch 26496794) only.
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.
This patch can be applied to all platforms supported in release 11.1.2.4.000. See the Release 11.1.2.x Certification Matrix for a list of supported platforms.
This patch supports all locales supported in Release 11.1.2.4.000.
|
Defect Number |
Defect Fixed |
|
27018210 |
Essbase could not be initialized because the EPM System configuration tool configured the primary RAC node as the base database in the database connection. |
|
26665432 |
Taskflow Status Summary tab did not list taskflows when you search for taskflows that were initiated between two dates. |
|
26443779 |
The following error was displayed when
exporting many forms using Lifecycle Management: |
|
25824130 |
Oracle Financial Management was unable to email taskflow notification if the SMTP server was configured to use port other than port 25. |
|
25685920 |
Group name was not displayed when viewing group properties. |
This patch does not contain any known issues.
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, 26751072.zip, to the EPM_ORACLE_HOME/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).
NOTE: 26751072.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/26751072 -oh EPM_ORACLE_HOME -jdk MIDDLEWARE_HOME/jdk160_35
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/26751072 -oh EPM_ORACLE_HOME -jdk MIDDLEWARE_HOME/jdk160_35 -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. For WebSphere Application Server only: 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.
4. Start Foundation Services and other EPM System components and processes, including custom programs that use EPM System APIs.
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 26751072 -oh EPM_ORACLE_HOME -jdk MIDDLEWARE_HOME/jdk160_35
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 26751072 -oh EPM_ORACLE_HOME -jdk MIDDLEWARE_HOME /jdk160_35 -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. For WebSphere Application Server only: 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.
4. Start Foundation Services and other EPM System components and processes, including custom programs that use EPM System APIs.
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:
Windows:
opatch.bat lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_35
UNIX/Linux:
./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_35 –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 © 2017, Oracle and / or its affiliates. All rights reserved. http://www.oracle.com