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.

Essbase Native Security Mode Is No Longer Supported

Caution! Oracle strongly recommends not using Essbase native security mode because of security concerns. If you are currently using Essbase native security mode, you should convert Essbase Server to EPM System security mode and migrate users to EPM System security using Administration Services Console. See “Converting Essbase Server and Migrating Users to Shared Services” in the Oracle® Essbase Administration Services Online Help. After you complete the conversion and migration tasks, Essbase security is managed as described in the Oracle® Enterprise Performance Management System User Security Administration Guide. References in the Essbase and Administration Services 11.1.2.3 documentation about implementing and using Essbase native security mode should be ignored.

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

· 11.1.2.3.001

· 11.1.2.3.002

· 11.1.2.3.003

· 11.1.2.3.500

· 11.1.2.3.501

· 11.1.2.3.502

· 11.1.2.3.503

· 11.1.2.3.504

· 11.1.2.3.505

· 11.1.2.3.506

· 11.1.2.3.507

· 11.1.2.3.507_20859535

· 11.1.2.3.507_21171146

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.3.508, Provider Services 11.1.2.3.507, and Essbase Studio 11.1.2.3.507 are supported for use with Essbase 11.1.2.3.508.

Recommendation: After you apply a patch within the same release codeline, Oracle recommends as a best practice that you export the data from your databases, clear the data from the databases, and then reload the data.

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
· 21246504	After a forced restructure, a block storage database takes longer to complete a calculation.
· 21116228	When running a dimension build for an aggregate storage database on an Accounts member, the member for time balance cannot be set to 'NONE.'
· 20924044	In some cases, the Essbase Agent becomes unresponsive and returns an error: "Failed to logout user [%s]: user has remote transactions in progress"
· 21078645	In some cases, the Essbase Administration Server terminates abnormally when editing an ASO outline.
· 21447894	When submitting data to an ASO outline the Application can terminate abnormally.
· 20929809	The Essbase Client MSI installer was packaged with incorrect files.

Known Issues in this Patch

None at this time.

Applying this Patch

The section includes important information about applying this patch for Essbase.

Component	Patch ID
Essbase Client MSI (Windows)	21248751
Essbase Client (OPatch)	21248744
Runtime Client	21248750
Essbase Server	21248746

To apply this patch for Essbase Client on Windows 32-bit and 64-bit platforms:

1. Uninstall the Essbase Client.

2. To apply this patch, run the EssbaseClient.exe, pick a destination folder, and complete the installation.

NOTE: After applying the Essbase Client patch, you might need to set the ESSLANG variable to your local language.

To apply this patch for Essbase Client on UNIX and Linux platforms:

1. Stop the Essbase service(s).

2. Download and unzip the downloaded patch file <patch id>_<platform>.zip to <EPM_ORACLE_HOME>/OPatch.

NOTES:

o <patch id>_<platform>.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 Essbase after applying the patch.

3. On the Essbase Server machine, launch command prompt and change the current directory to the <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 DIRECTORY> -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 DIRECTORY> -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. If you use <MIDDLEWARE_HOME>/EPMSystem11R1/products/Essbase/EssbaseClient/api/redist you will need to update these files from <MIDDLEWARE_HOME>/EPMSystem11R1/common/EssbaseClient/11.1.2.0/bin

NOTE: The default for <MIDDLEWARE_HOME> is C:/Oracle/Middleware.

6. Restart Essbase.

NOTE: After applying the Essbase Client patch, you might need to set the ESSLANG variable to your local language.

To apply this patch for runtime client:

1. Stop the Essbase service(s).

2. Download and unzip the downloaded patch file <patch id>_<platform>.zip to <EPM_ORACLE_HOME>/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.

3. On the Essbase Server machine, launch command prompt and change the current directory to the <EPM_ORACLE_HOME>/OPatch.

5. If you use <MIDDLEWARE_HOME>/EPMSystem11R1/products/Essbase/EssbaseClient/api/redist you will need to update these files from <MIDDLEWARE_HOME>/EPMSystem11R1/common/EssbaseRTC/11.1.2.0/bin

NOTE: The default for <MIDDLEWARE_HOME> is C:/Oracle/Middleware.

6. Restart Essbase.

To apply this patch for Essbase Server:

1. Stop the Essbase service(s).

2. Download and unzip the downloaded patch file <patch id>_<platform>.zip to <EPM_ORACLE_HOME>/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.

3. On the Essbase Server machine, launch command prompt and change the current directory to the <EPM_ORACLE_HOME>/OPatch.

5. Copy localized files to your bin directory:

Copy all the files from <EPM_ORACLE_HOME>/products/Essbase/EssbaseServer/localized/<Language ID>/bin
to
<EPM_ORACLE_HOME>/products/Essbase/EssbaseServer/bin

Replace <Language ID> in the preceding lines with the appropriate language identifier for your installation. The following are the language identifiers for each language available for this release:

o Arabic – ar

o Chinese (Simplified) - zh_CN

o Chinese (Traditional) - zh_TW

o Czech - cs

o Danish - da

o Dutch – nl

o English - en

o Finnish – fi

o French – fr

o French (Canadian) - fr_CA

o German - de

o Greek - el

o Hebrew - he

o Hungarian - hu

o Italian - it

o Japanese - ja

o Korean - ko

o Norwegian – no

o Polish - pl

o Portuguese - pt

o Portuguese (Brazilian) - pt_BR

o Romanian - ro

o Russian - ru

o Slovak - sk

o Spanish - es

o Swedish – sv

o Thai - th

o Turkish - tr

6. Restart Essbase.

Rolling Back this Patch

To remove this patch for Essbase Client on Windows:

1. In Windows Control Panel, navigate to Add or Remove Programs.

2. Select the appropriate item, and then click Remove.

3. Reinstall the previous version of the Essbase Client console.

To roll back this patch for Essbase Client on UNIX and Linux platforms, Essbase Runtime Client, or Essbase Server:

1. From a command line, change the directory to <EPM_ORACLE_HOME>/OPatch (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

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

SSMEMBERIDPROCESSING Configuration Setting

In this release, this feature is only applicable to users of Oracle General Ledger.

Controls whether Smart View keeps track of members in a report by using stable member IDs instead of (less stable) uniquely qualified member names.

For a database that has duplicate member names enabled, an internal member ID is associated with each member.

Syntax

SSMEMBERIDPROCESSING [appname [dbname]] TRUE | FALSE

· appname--Optional. Specifies the application for which member IDs should be used.

· dbname--Optional. Specifies the database, in the application appname, for which member IDs should be used.

· TRUE--Essbase tracks members using stable member IDs. This is the default for BI outlines, if DISPLAY_KEY and MEMBER_VALUE alias tables exist in the outline.

· FALSE--Essbase tracks members using qualified member names.

Description

For Smart View reports on duplicate member name outlines, member IDs can help Smart View maintain report validity for all members, even when members in the outline are moved or renamed.

Example

SSMEMBERIDPROCESSING Sample TRUE