Oracle Hyperion Calculation Manager

Release 11.1.2.1.000 Patch Set Update (PSU): 11.1.2.1.104

Readme

About this Patch. 1

Patch Type. 1

Supported Paths to this Patch. 2

Prerequisites. 2

Required User Rights. 2

Supported Platforms. 2

Supported Languages. 2

Defects Fixed in this Patch. 2

Defects Fixed in Patch 11.1.2.1.103. 3

Defects Fixed in Patch 11.1.2.1.102. 3

Defects Fixed in Patch 11.1.2.1.101. 3

Known Issues in this Patch. 3

Applying this Patch. 4

Rolling Back this Patch. 4

Troubleshooting FAQs. 5

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

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

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

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 Patch Set Update replaces files in the existing installation and is a stand-alone patch.

Supported Paths to this Patch

You can apply this patch to the following releases: Calculation Manager 11.1.2.1.000, 11.1.2.1.101, 11.1.2.1.102, and 11.1.2.1.103.

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 supports the same platforms as release 11.1.2.1.000.

Supported Languages

This patch supports the same languages as release 11.1.2.1.000.

Defects Fixed in this Patch

·         14056352 - If IE's browser language is set to Chinese, you may not be able to export Consolidation rules using Calculation Manager via LCM.

·         14069884 - Functions: @MBRPARENT, @BETWEEN,@EQUAL, @EXPAND, @LIKE, @MBRCOMPARE, @NOTEQUAL, and @TODAY, were missing in Calculation Manager

·         14128035 - Using a template in a rule, it may put default values for DTP's that were not prompted by the wizard

·         14279239 - Custom defined function may not validate in Calculation Manager

·         14298044 Using LCM to migrate Calculation Manager Rules from one application to another may not work.  To get the complete fix please apply Oracle Hyperion Shared Services PSU 11.1.2.1.600 (14142678).

·         14342781 - Using a run time prompt variable with a Custom defined function may not produce the prompt for the variable, and therefore may not launch the rule

·         14382653 - Calculation Manager may time out when running a calc script on a Essbase ASO cube

Defects Fixed in Patch 11.1.2.1.103

·         13787076 - When you switch from graphical to script mode, the cursor may display only intermittently and you may be unable to type.

·         13649622 - If you are working with the Function Selector, and you do not enter a value for the optional parameter, no comma is entered in the arguments field and validation fails.

·         13443136 - Calculation script validation may fail in Calculation Manager but succeed in Essbase Administration Services.

·         13649523 - A business rule with the ALLOCATE function may validate differently in Calculation Manager and Essbase Administration Services.

·         13839090 - You may only be able to use the MDALLOCATE function in Business Rules and not in Calculation Manager.

·         13830113 - You may be unable to validate a business rule with an attribute reference in Calculation Manager.

·         13689121 - After importing business rules for a Planning application into Calculation Manager, you may be unable to validate the business rules.

·         13825368 - In script mode, when you insert a line or copy code into the script editor, the line breaks may disappear. When you press Enter in the code and then copy code into the script editor, all of the line breaks may disappear.

 

Defects Fixed in Patch 11.1.2.1.102

·         13082500 – If you create an Essbase business rule, add a component, and give the component a caption, the caption may not be saved after you save the business rule.

·         13107882 – You may be unable to use Lifecycle Management to import a business ruleset when the ruleset contains business rules from different Planning applications.

 

Defects Fixed in Patch 11.1.2.1.101

·         12966784 – If you create a business ruleset and associate two or more business rules from different applications to it, the validation of this ruleset may fail with a “Member not found” error.

·         12962442 - If a member referenced in a business rule is in one plan type, but not in other plan types of an application, you must include that business rule as the first in the list of business rules within a business ruleset. If you do not include it as the first business rule, the business ruleset may fail validation against both Performance Management Architect and Planning, and you may be unable to deploy it, even though the individual business rules within the business ruleset all validate.

·         12977947 - After you log on to Calculation Manager, Essbase applications may not display in the System View, and you may be unable to access these applications.

 

Known Issues in this Patch

14355073 - A rule using a stringasnumber variable may not validate due to unresolved RTP error.   Workaround: In the rule, click on the begin component, Variables tab, enter a numeric value for the stringasnumber variable, save the rule.  Validation should now be successful and will use the numeric value you entered.

Applying this Patch

The section includes important information about applying this patch for Calculation Manager.

To apply this patch:

1.    Stop the Calculation Manager server.

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.

3.    On the server where Calculation Manager is installed, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.

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

Windows:

opatch.bat apply <EPM_ORACLE_HOME>/OPatch/14265667 -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/14265667 -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.

5.    Perform the standard Calculation Manager Web application server deployment task using Hyperion Enterprise Performance Management System Configurator (EPM System Configurator). See the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide for instructions.

6.    Restart Calculation Manager server.

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

Rolling Back this Patch

To roll back a patch:

1.    Stop the Calculation Manager server.

2.    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 14265667 -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 rollback -id 14265667 -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.

4.    Perform the standard Calculation Manager Web application server deployment task using Hyperion Enterprise Performance Management System Configurator (EPM System Configurator). See the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide for instructions.

5.    Restart Calculation Manager server.

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

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_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