Oracle Hyperion Reporting and Analysis Framework

 

Release 11.1.2.4.007 Patch Set Update (PSU): 26865623

Readme

About this Patch. 1

Patch Type. 1

Supported Paths to this Patch. 2                                                                                                 

Prerequisites. 2

Other Required Patches. 2

Required User Rights. 2

Supported Platforms. 2

Supported Languages. 2

Defects Fixed in this Patch. 2

Known Issues in this Patch. 3

Applying this Patch. 3

Rolling Back this Patch. 3

Troubleshooting FAQs. 4

Why do I get the following patch conflict error message when running OPatch?. 4

Why do I get the OUI-67078 warning message when applying OPatch?. 4

How can I find out which releases and patches of EPM System products are installed in a deployment?. 5

I applied the patch successfully but I don’t see the changes from the patch in the product. What should I do?. 5

About this Patch

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.

Patch Type

This is a patch set update (PSU). This PSU replaces files in the existing installation and does not require a full installation.

 

Supported Paths to this Patch

You can apply this patch to the following releases:

·         11.1.2.4.000

Prerequisites

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

Defects Fixed in this Patch

Defect Number

Defect Fixed

26178212

Problem with Service Administration page

26178235

Problem with smart page

 

 

 [NOTE to writers: FOR CUMULAtive patches only. List earlier patch DEFECTS FIXED and create sub-headings for each previous patch, where YYYYYYYY refers to an earlier patch.  DELETE THIS SECTION IF NOT CUMULATIVE.  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).]

Known Issues in this Patch

[NOTE TO WRITERS: This section is required.  If the patch doesn’t have any known issues, INCLUDE THIS SENTENCE.] 

This patch does not contain any known issues.

 

[NOTE TO WRITERS: Per Legal: This sentence must be included IF THERE ARE KNOWN ISSUES.]

 [NOTE TO WRITERS: If the patch is cumulative, check with your product team about whether to include any known issues from the earlier patches.]

Applying this Patch

This section includes important information about applying this patch for Reporting and Analysis Framework.

[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.    Oracle recommends making a backup of the existing installation before applying this patch.

2.    Shut down all services and servlet instances related to the Oracle Hyperion Enterprise Performance Management System Workspace 11.1.2.4.000 installation.

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

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.

4.  On EPM Workspace machine, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.

5.    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.3: JDK160_35

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/26865623 -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/26865623 -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.

 [NOTE TO WRITERS: If your product is a web application, you need to add this step after the step where the patch is applied:

This step is not required for WebLogic.]

6.  For WebSphere deployments, you must use EPM System Configurator to redeploy the Web application.   

7.  For WebAnalysis, You have 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.

8.  Restart Oracle Hyperion EPM services and servlets.

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

Rolling Back this Patch

To roll back a patch:

1.    Shut down all services and servlet instances related to the Oracle Hyperion Enterprise Performance Management System Workspace 11.1.2.4.000 installation.

2.  On EPM Workspace machine, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

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

Windows:

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

     4.  For WebSphere deployments, you must use EPM System Configurator to redeploy the Web application.  

5.  Restart Oracle Hyperion EPM services and servlets.

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

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:

[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_35

UNIX/Linux:

./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_35 –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