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

11.1.2.2.101

11.1.2.2.102

11.1.2.2.103

11.1.2.2.104

11.1.2.2.105

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.

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

Note: This patch is cumulative and includes defects fixed in earlier patches.

Defect Number	Defect Fixed
· 18149808	During a restructure operation, a temporary storage manager is created with an index cache. Previously, Essbase used a default size for the index cache of the new storage manager regardless of the size already configured for the database (usually much larger). This sometimes increased the amount of page swapping. The storage manager was then structured to be the same size as the one already in use. This resulted in faster restructuring but could cause a sudden demand for memory equal to the size of the index cache.
· 18150375	After an abnormal shutdown, free index pages with an uncertain status within the database index are invalidated and set aside to prevent incorrect allocation.
· 18150388	This change fixes a bug in which an uncontrolled system shutdown could leave a database in an inconsistent state. Previously, if the system went down after an index cache page was swapped out, but before other transactions completed, the page written could refer to a page that was never written to the disk. With this fix, only pages without references to new pages can be swapped out, so the problem cannot occur.
· 18150427	The safest course of action when an inconsistency is detected is to restore from backup. The fix is to change the relevant error messages to reflect that. They have been changed to "Invalid block header: Illegal block type -- Please restore from backup" or "Invalid transaction status for block -- Please restore from backup".
· 18420435	The Essbase Server can terminate abnormally if the number of filters is between 32K or 64K.
· 18399049	When a user deletes an Essbase database that has a disk volume set, some application files will be deleted.
· 18307083	If the number of soft file descriptors is too high, an application will not load. A check has been added and an message will be returned for the users to set a smaller value.
· 18306933	When refreshing Planning Security Filters, and a calc script is opened, the Essbase Server will not return.
· 18492709	In some cases, the Essbase Server can terminate abnormally when CALCPARALLEL is used in a calc script.
· 18467904	While running a calculation in parallel and in a loop can result in an invalid block transaction.
· 18253423	When copying an application while a calculation is in progress can result in the Essbase server terminating abnormally.
· 18460291	When running multiple requests to copy an application can put the Essbase server in an unusable state.
· 18062973	Some MDX queries can use excessive RAM.
· 18373296	When using Suppress Missing Block and Transparent Partitions is used can cause an application to terminate abnormally.
· 18406253	An unexpected error is returned when executing an MDX statement with SOLVE_ORDER on an empty database. Error: Unexpected Essbase error 1200467
· 17650694	In some cases, when retrieving data an application can be put in an unusable state and may terminate abnormally.
· 17664671	When formula preservation is enabled, an error is encountered when zooming out.
· 17664745	Incorrect results can be returned when zooming in and using Suppress Missing and Formula Preservation.
· 18224609	When using Smart View Client, the POV can shift to the right when members are pivoted and the repeat member options is set.
· 17821414	Application terminates abnormally when performing a refresh or zoom-in.
· 18090396	In some cases, a member with varying attribute set is not displayed in a report.
· 17505074	Zooming in adds empty rows on child members
· 17315823	New empty formula rows can be added after a retrieval using Suppress Missing and Formula Preservation.
· 18330841	On 32-bit platforms, OCI data load can fail and an exception created.
· 17438884	An ASO Transparent Partition can return incorrect values to the target in some cases.
· 16748718	In some cases, date-time dimensions created with special characters, such as Russian characters, will not be created correctly.
· 18275226	Japanese characters are not displayed correctly in Essbase Administration Services SQL Interface.
· 17570471	An application can terminate abnormally if Failover mode is set to TRUE in Active-Passive Clustering.
· 18156520	Essbase using OPMN needs to stop gracefully.
· 18417229 · 18123984	Essbase Server abnormally terminates in some cases when using some Smart View client operations.

ODBCERRORLOGOFF Configuration Settings

ODBCERRORLOGOFF specifies whether ODBC driver error messages are written to the Essbase application log file.

Syntax:

ODBCERRORLOGOFF TRUE | FALSE

• TRUE—Logging of ODBC driver errors is disabled.

• FALSE—Logging of ODBC driver errors is enabled. The default value is FALSE.

Example:

ODBCERRORLOGOFF TRUE

(17264016, 16954507)

Known Issues in this Patch

• The formula preservation zoom introduces blank rows in worksheets.
(16756647, 16734127, 16734199)

Documentation Updates

Documentation Correction for MaxL Deploy Statement

14511078

In the Technical Reference, the MaxL deploy statement topic gives incorrect syntax for using an Oracle OCI connect identifier in the odbc_dsn specification.

The correction is:

To use an Oracle OCI connect identifier, use the following syntax after the odbc_dsn keyword:

$OCI$host:port/Oracle_service_name

Example:

$OCI$myserver:1521/orcl.us.oracle.com

Applying this Patch

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

Component	Patch ID
Essbase Client MSI (Windows)	18148661
Essbase Client (OPatch)	18148677
Runtime Client	18148673
Excel Add-in MSI	18148659
Essbase Server	18148668

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

1. Uninstall the 11.1.2.2 Essbase Client.

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

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.

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 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_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/<PATCH DIRECTORY> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_21 -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.

To apply this patch for runtime client:

1. Stop the Essbase service(s).

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 Spreadsheet Add-in:

1. Uninstall the 11.1.2.2 Spreadsheet Add-in.

2. To apply this patch, run Spreadsheet Add-in.exe, pick a destination folder, and complete the installation.

To apply this patch for Essbase Server:

1. Stop the Essbase service(s).

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 C:\Hyperion\products\Essbase\EssbaseServer\localized\<Language ID>\bin to C:\Hyperion\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:

- Arabic – ar

- Brazilian Portuguese - pt_BR

- Danish - da

- Dutch – nl

- Finnish – fi

- French – fr

- German - de

- Italian - it

- Japanese - ja

- Korean - ko

- Norwegian – no

- Polish - pl

- Russian - ru

- Simplified Chinese - zh_CN

- Spanish - es

- Swedish – sv

- Traditional Chinese - zh_TW

- Turkish - tr

6. Restart Essbase.

Rolling Back this Patch

To remove this patch for Essbase Client on Windows or Essbase Spreadsheet Add-in:

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

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

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_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 <PATCH ID> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME> /jdk160_21 -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_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