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

11.1.2.4.001

11.1.2.4.002

11.1.2.4.003

11.1.2.4.005

11.1.2.4.006

11.1.2.4.008

11.1.2.4.009

11.1.2.4.010

11.1.2.4.011

11.1.2.4.013

11.1.2.4.014

11.1.2.4.015

11.1.2.4.016

11.1.2.4.018

11.1.2.4.020

11.1.2.4.022

11.1.2.4.023

Caution: Oracle recommends using the same version of all Essbase portfolio products (Essbase, Essbase Administration Services, Hyperion Provider Services, and Essbase Studio) and components (server, client, runtime client, API, and JAPI). When only some Essbase portfolio products are included in a patch release, the last released versions of the products that are not included in the patch are supported.

Essbase Administration Services 11.1.2.4.023, Essbase 11.1.2.4.025, and Essbase Studio 11.1.2.4.016 are supported for use with Provider Services 11.1.2.4.025.

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

Applies to all supported platforms.

Information about system requirements and supported platforms for EPM System products is available in a spreadsheet format in the Oracle Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on the Oracle Technology Network (OTN):

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Supported Languages

Applies to all supported languages.

Information about supported languages for EPM System products is available in a spreadsheet format on the Translation Support tab in the Oracle Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on OTN:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Defects Fixed in this Patch

Defect Number	Defect Fixed
· 27925746	The new Enable Varying Attributes option allows Oracle Essbase users to display #Invalid or #NumericZero for cells that are empty only because they are not associated with the context attribute or varying attribute in a query. When this option is selected, meaningless cells display as #Invalid or #NumericZero depending on the selection made for the Replacement option, #Invalid/Meaningless. For example, suppose an Essbase ad hoc query is designed to get sales for all products, but display data only for the product cells associated with the attribute of Ounces_12. With the Enable Varying Attributes option selected, all other product sales data cells not associated with the Ounces_12 attribute would then display #Invalid or #NumericZero. The Enable Varying Attributes option and the #Invalid/Meaningless option are both located in the Options dialog, Data Options tab. By default, the Enable Varying Attributes option is cleared. See Documentation Updates for more information.
· 27795364	Loads from Hyperion Financial Data Quality Management fail after applying Hyperion Provider Services Patchset Updates 11.1.2.4.022 and 11.1.2.4.023.
· 26364501	Using either a Shared or Private connection in Smart View Client, in some cases results in an error returned when user clicks the Oracle Essbase that is listed: Invalid datasource [[ com.essbase.api.base.EssException: error in Common Provider, Invalid datasource at com.essbase.smartview.SmartViewException.getEssException(Unknown Source)

Known Issues in this Patch

Drill-through Reports with Dynamic Time Series Functions in the Smart View Grid

Drill-through reports with recursive hierarchy based cube deployments from Essbase Studio do not work if Dynamic Time Series functions exist in the Smart View grid.

(22596350)

Applying this Patch

The section includes important information about applying this patch for Provider Services.

The patch id is 27797138.

To apply this patch:

1. Stop Provider Services.

2. Download and unzip the downloaded patch file, <PATCH ID>_<PLATFORM ID>.zip, to the <EPM_ORACLE_HOME>/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

NOTES:

o <PATCH ID>_<PLATFORM ID>.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.

o You must unzip the file on the platform for which it is intended. After you unzip the patch file, verify that the executable and library files have execute permission before you apply the patch. If you apply the patch and the executable and library files do not have execute permission, you will not be able to start Provider Services after applying the patch.

3. On the machine hosting Provider Services, launch command prompt and 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/<PATCH ID> -oh <EPM_ORACLE_HOME>
-jre <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/<PATCH ID> -oh <EPM_ORACLE_HOME> -jre <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.

5. Check that the Central Inventory exists and contains the expected set of components by entering the following command:

Windows: opatch.bat lsinventory -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_35

Unix/Linux: ./opatch lsinventory -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_35

If this command does not return the expected set of components, the /inventory directory wasn't created properly under <HYPERION_HOME> during the installation. In this case, follow the steps in “Resolving Central Inventory Issues” below before proceeding with these steps.

6. You are prompted to enter an email address and optional password. If you ignore this prompt by selecting the Enter key, the following message is displayed: “You haven’t provided an e-mail address for notification of security issues. Do you wish to remain uninformed of security issues ([Y]es, [N]o)” enter “Y” and the installer continues to the end of the installation. If you enter an email address and a password, the password must be from your Metalink account. If the password is invalid the installation will yield an error and stop. If you do not know your Metalink password, leave the password blank and the installation will continue.

7. Re-start Provider Services.

Rolling Back this Patch

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

Windows:
opatch.bat rollback -id <PATCH ID> -oh <EPM_ORACLE_HOME> -jre <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 <PATCH ID> -oh <EPM_ORACLE_HOME> -jre <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.

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

Documentation Updates in this Patch

Display Varying Attributes in Ad Hoc Grids

The new Enable Varying Attributes option allows Oracle Essbase users to display #Invalid or #NumericZero for cells that are empty only because they are not associated with the context attribute or varying attribute in a query. When this option is selected, meaningless cells display as #Invalid or #NumericZero depending on the selection made for the Replacement option, #Invalid/Meaningless.

For example, suppose an Essbase ad hoc query is designed to get sales for all products, but display data only for the product cells associated with the attribute of Ounces_12. With the Enable Varying Attributes option selected, all other product sales data cells not associated with the Ounces_12 attribute would then display #Invalid or #NumericZero.

The Enable Varying Attributes option and the #Invalid/Meaningless option are both located in the Options dialog, Data Options tab. By default, the Enable Varying Attributes option is cleared.

For more information, see the Smart View Client documentation:

· https://docs.oracle.com/applications/smartview/800/SVREA/toc.htm#SVREA-GUID-0DB52AA4-7EF3-4841-AB5F-D75A12EFB3CE

· https://docs.oracle.com/applications/smartview/800/UGSVU/enabling_varying_attributes.htm#UGSVU-GUID-41B3F40C-E605-448C-B472-9A4C8C48FC45

· https://docs.oracle.com/applications/smartview/800/UGSVU/opt_data.htm#UGSVU-options_202

(27925746)

How to use EssOutlineEditOption class with openOutline

Open the outline in editing mode. The user needs to have write privileges. Existing flags provided for opening the outline have been moved into EssOutlineEditOption class. EssOutlineEditOption has flags for outline locking, keepTransactions and incremental mode. While outline lock and keepTransaction flags default to true, incremental mode flag defaults to false.

EssOutlineEditOption has the below setter functions:

public void setLock(boolean bLock)
public void setKeepTransaction(boolean bKeepTransaction)
public void setIncremental(boolean bIncremental)

Example usage: For opening the
IEssCubeOutline cubeOutline = cube.openOutline(new EssOutlineEditOption());

(27407644)

Deprecated Essbase Properties in the essbase.properties File

Essbase properties service.olap.dataQuery.grid.maxRows and service.olap.dataQuery.grid.maxColumns in the essbase.properties file are deprecated.

· These properties, if defined in essbase.properties, do not have any effect on the grid result.

· The results of the grid are controlled by the QUERYRESULTLIMIT configuration setting in the essbase.cfg file on Essbase Server.

· With these changes, existing use cases that expect an error for the previous lower row and column limits set in JAPI will not get an error unless the QUERYRESULTLIMIT limit is exceeded.

· With these changes, Provider Services JAPI does not apply any limits against a previous version of Essbase. Essbase has to be upgraded to use the QUERYRESULTLIMIT configuration setting.