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

· 11.1.2.1.102 PSU

· 11.1.2.1.103 PSU

· 11.1.2.1.104 PSU

· 11.1.2.1.105 PSU

· 11.1.2.1.106 PSU

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

Defect Number	Defect Fixed
• 17821405	When performing a Smart View refresh with REALFREE() on Solaris can cause an ASO application to terminate abnormally.
• 17082163	In some cases, an Essbase application can terminate abnormally when running a dimension build with a rules file.
• 16622516	An error message that was posted to the Application log was not included in the MAXL log in the case of an error in a data load using SQL interface.
• 16485314	Essbase does not support a query with attributes that extracts Dynamic Time Series members through transparent partitions, with the TARGETTIMESERIESOPT setting in Essbase.cfg.

Known Issues in this Patch

The following issues are the noteworthy known issues of this patch:

· During data retrieval, a crash may occur if your client Essbase path points to your Essbase/server/bin directory.
Workaround: Point your client Essbase path to the Essbase runtime client directory.

· 14148420 - This release may not work with Essbase Administration Services Release 11.1.2.1.000 You will need to upgrade Administration Services to release 11.1.2.1.103 or later.

· 15980494 - Issuing MaxL commands during data load may cause the data load to terminate abnormally and may cause Essbase to stop responding.

· 16457613 - The TARGETTIMESERIESOPT configuration setting is used to optimize queries on transparent partitions. When this configuration setting is set in the essbase.cfg file and a transparent partition is defined on the time dimension, Dynamic Time Series calculations on any data existing on the target database returns #Missing or the result is incorrect. This behavior occurs because D-T-S calculations with this optional configuration setting are always extracted from the source database of the transparent partition.

· 16457664 - In a database with a transparent partition in which the target has no data blocks covered by the query, Dynamic Time Series calculations on attributes returns #Missing. This behavior occurs when the TARGETTIMESERIESOPT configuration setting is not specified in the essbase.cfg file.

· 16369144 - These steps need to be followed any time the IMPLIED_SHARE setting is changed
in the CFG file:
1. Add IMPLIED_SHARE FALSE to the CFG file
2. Restart Essbase
3. Create a new application and database when CFG setting is in place
4. Rebuild the outline when the CFG setting is in place.
5. Restart the Essbase application and Essbase Agent
6. Reload the data
7. Run aggregation/calculation scripts
8. Restart the application

Applying this Patch

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

Component	Patch ID
Runtime Client	17545113
Essbase Server	17545111

To apply this patch for runtime client:

1. Stop the Essbase service(s).

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

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

3. 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_21

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.

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

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

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_21

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. Copy localized files to your bin directory:

Copy all the files from
C:\Oracle\Middleware\EPMSystem11R1\products\Essbase\EssbaseServer\localized\
<Language ID>\bin
to
C:\Oracle\Middleware\EPMSystem11R1\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:

- French – fr

- German - de

- Spanish - es

- Italian - it

- Brazilian Portuguese - pt_BR

- Japanese - ja

- Korean - ko

- Simplified Chinese - zh_CN

- Traditional Chinese - zh_TW

- Russian - ru

- Turkish - tr

- Danish - da

- Swedish – sv

- Arabic – ar

- Finnish – fi

- Dutch – nl

- Norwegian – no

- Polish - pl

6. Restart Essbase.

Rolling Back this Patch

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

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

To roll back this patch for 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. Enter the following command on one line:

Windows:
opatch.bat rollback -id <PATCH ID> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_21

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_21

UNIX/Linux:

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

Configuring Parallel SQL Connections for Essbase SQL Interface

(17844304) In the "Performing Multiple SQL Data Loads in Parallel to Aggregate Storage Databases" topic in the Essbase SQL Interface Guide, incorrect information is given for configuring SQL drivers to enable parallel SQL connections. The following information is correct:

This feature requires parallel SQL connections. You must create a SQL configuration file named esssql.cfg in the ARBORPATH/bin folder to change the default settings for the ODBC driver you are using. (By default, SQL Interface disables parallel connections for the DataDirect ODBC drivers that are provided with Essbase.)

The following examples enable parallel SQL connections:

· Microsoft SQL on Windows (non-DataDirect driver):

[

Description "SQL Server"

DriverName SQLSRV

UserId 1

Password 1

Database 1

SingleConnection 0

UpperCaseConnection 0

IsQEDriver 0

]

· Microsoft SQL on UNIX and Linux (DataDirect driver):

[

Description "DataDirect SQL Server Native Wire Protocol"

DriverName ARSQLS

UserId 1

Password 1

Database 1

SingleConnection 0

UpperCaseConnection 0

IsQEDriver 1

]