Purpose

This document includes important, late-breaking information about this release of Oracle Enterprise Performance Management System. Review this Readme thoroughly before installing EPM System.

Overview

This Quarterly Release Update is distributed as an OPatch containing OPatches for individual EPM system components. Release 11.2.27 is a cumulative update that includes all updates from Release 11.2.15. This update can be applied on top of any release from 11.2.15 onwards.

For a list of OPatches for individual EPM system components, see OPatch Dependencies and Details.

Oracle recommends that you read the 11.2.27 Readme Guide in its entirety before applying the patch to Release 11.2.27.

Release 11.2.27 (Release 11.2, Update 27) includes the following deliverables:

  • Oracle Enterprise Performance Management System - 11.2.27.0.000 for Microsoft Windows x64 (64-bit)
  • Oracle Enterprise Performance Management System - 11.2.27.0.000 for Linux x86-64
  • Oracle Enterprise Performance Management System - Client Installers 11.2.27.0.000 for Microsoft Windows x64 (64-bit)
  • Oracle Data Relationship Management 11.2.27.0.000 for Microsoft Windows (64 bit)

Note:

Release 11.2.27 will not contain an Installation and Configuration guide. See Oracle Enterprise Performance Management System Installation and Configuration Guide for Release 11.2.15 for more information.

EPM System Update and Upgrade Policies

See EPM System Update and Upgrade Policies for more information on update and upgrade policies for Oracle Enterprise Performance Management System.

New Features

This section includes new features in this release. To review the list of new features from earlier releases, use the Cumulative Feature Overview tool. This tool enables you to identify the products you own and your current implementation release. With a single click, the tool quickly produces a customized report of new feature descriptions. This tool is available here: https://apexapps.oracle.com/pls/apex/f?p=20620:1:0

Release 11.2.27 includes the following new features:

  • Feature Updates

    Table 1-1 New Features

    Features Descriptions
    A New Version of the Java API Reference for the Oracle Hyperion Shared Services Guide is Published.

    This guide provide a current reference for the Common Security Services (CSS) API in the Oracle Enterprise Performance Management (EPM) 11.2 documentation.

    NOTE: The reference supports developers who work with Hyperion Shared Services Security APIs and replaces reliance on outdated JavaDocs published for earlier releases.

    For more information, see Java API Reference for Oracle Hyperion Shared Services Guide
    Financial Management Features

    This update includes two new features for Oracle Hyperion Financial Management:

    • Add Submitted By and Submitted On to Journal Reports

    • Include Journal Label in the Description Column of Data Audit

    Review the Financial Management Features.

  • Patches and Updates

    Table 1-2 Bundled Patch Updates

    Component Version
    Java Java 8 Update 501
    Essbase 21.8.3
    WebLogic Patch Set Update 12.2.1.4.260703
    Application Development Framework (ADF) Bundle Patch 12.2.1.4.260622

    Note: Important UI Changes in ADF Patch Update

    To enhance EPM application accessibility in alignment with the latest Oracle Accessibility Guidelines (OAG).

    The ADF patch update increases row heights and spacing across various EPM applications, including HFM, FDMEE, Planning, and Reports, to improve usability for users with accessibility needs. While these changes align with accessibility standards, they may result in fewer visible rows per page and increased scrolling.
    Oracle HTTP Server (OHS) 19c

    • Bundle Patch 12.2.1.4.260624

    • Database Release Update 19.30.0.0.0 For FMW Database Client.

    Oracle Data Integrator (ODI) No patches in this release
    Microsoft Active Directory 2025 is now certified and supported.
  • For details on new features introduced in previous versions, see New Features: 11.2.8 - 11.2.26.

Financial Management Features

This release introduces two new features alongside several important fixes and general improvements.

Add Submitted By and Submitted On to Journal Reports

Enhance Journal Reports to make Submitted By and Submitted On available as selectable report columns.

For each journal, the report must display the user who performed the most recent Submit action and the corresponding submission timestamps. These fields must be independent of the existing Approved By/Approved Time and Posted By/Posted Time fields, since submission, approval, and posting can be performed by different users under segregation-of-duties controls.

Include Journal Label in the Description Column of Data Audit

Enhance Data Audit to display the journal label in the Description column for each journal-related audit entry.

When a journal is processed, the Description column displays the business-entered journal label, enabling auditors, Console users, and control teams to quickly identify, filter, and select journal vouchers for review without opening the underlying journal.

Financial Management Schema Upgrade

This release introduces schema changes for the above new features. To run the existing application successfully, you need to run the schema upgrade tool from the configuration on any one Financial Management server only.

When you import any application from older version after the first time running the schema upgrade. You need to run schema upgrade for the newly imported application only.

To upgrade one application, the schema upgrade must be run from a command prompt:

  • Windows:
  • Open a command prompt in %EPM_ORACLE_HOME%\products\FinancialManagement\Server
  • Execute the appropriate command below for the database type:
    • SQL Server:
    • ofmssu -dbname=<dbname> -dbtype=MS_SQL_SERVER -dbuser=<dbuser> -dbpassword=<dbpassword> -dbserver=<dbserver> -dbport=<dbport> -eoi=<EPM Oracle Instance folder> -applist=<appname>
    • Oracle:
    • ofmssu -dbname=<sn or sid> -dbtype=ORACLE -dbuser=<dbschema> -dbpassword=<dbpassword> -dbserver=<dbserver> -dbport=<dbport> -eoi=<EPM Oracle Instance folder> -applist=<appname>
  • Linux:
  • Open a terminal in $EPM_ORACLE_HOME/products/FinancialManagement/Server
  • Execute the appropriate command below for the database type:
    • SQL Server:
    • ./ofmssu -dbname=<dbname> -dbtype=MS_SQL_SERVER -dbuser=<dbuser> -dbpassword=<dbpassword> -dbserver=<dbserver> -dbport=<dbport> -eoi=<EPM Oracle Instance folder> -applist=<appname>
    • Oracle:
    • ./ofmssu -dbname=<sn or sid> -dbtype=ORACLE -dbuser=<dbschema> -dbpassword=<dbpassword> -dbserver=<dbserver> -dbport=<dbport> -eoi=<EPM Oracle Instance folder> -applist=<appname>

Financial Management Platform-Independent Release

On May 22, 2024, Microsoft announced the deprecation of VBScript along with its timeline. See VBScript deprecation: Timelines and next steps for more details.

To support Financial Management customers in executing business logic natively, Financial Management Platform Independent Release 11.2.21 was delivered in April 2025. This release introduces native script engine support in preparation for upcoming deprecations.

Table 1-3 Key Changes in 11.2.21

Change Area Details
Server Process Changed to ofmserver.exe
Server Log File Name Format: xfm_odl_srv_<appname>.log
Array Handling Financial management script engine had inconsistency during the array handling. Array created with two different ways behave differently and returning the lbound value 0 and 1

Table 1-4 Example: Array Handling Differences

Example Code snippet lbound Value
Example 1 
Dim A(20) 
for i = lbound(a) to ubound(a) 
next 
Here lbound(a) = 0
0
Example 2 
myList = HS.Entity.List("","[Base]") 
for j = lbound(myList ) to ubound(myList) 
next 
Here lbound(myList) = 1
1
  • As a Financial Platform independent release these inconsistencies have been addressed. The functions which return an array are impacted, for example, List, AttributeList, etc.
  • Avoid hardcoding array bounds (0 or 1). Always use lbound() and ubound() as index references.

Financial Management Updates on Microsoft Engine Removal

As Microsoft has confirmed the deprecation of the VBScript engine (see Deprecation details), the Financial Management roadmap provides the plan for its removal and the introduction of an alternative with no significant impact.

Table 1-5 Microsoft Engine Removal Timeline

Release Timeline Windows Support Linux Support
11.2.21 Apr 2025 Microsoft Script Engine (Default) -
11.2.22 Jul 2025
  • Microsoft Script Engine (Default)
  • Native Script Engine (Available)
 -
11.2.23 October 2025
  • Microsoft Script Engine (Default)
  • Native Script Engine (Available)
 Native Script Engine
11.2.31 October 2027
  • Native Script Engine (Default)
  • Microsoft Script Engine (Critical fixes only)

In this release the Native Script Engine will become the default script engine. Starting from 11.2.22 to 11.2.31 release customers are advised to plan the transition from the Microsoft Script Engine to the Native Script Engine.

 Native Script Engine
11.2.39 October 2029
  • Native Script Engine (Default)
  • Microsoft Script Engine (Removed)

Starting from 11.2.22, till 11.2.39, customers must transition from the Microsoft Script Engine to the Native Script Engine. In release 11.2.39, the Microsoft Script Engine is removed, and is no longer an available option.

Note: If Microsoft adjusts their timeline for the deprecation of VBScript, Oracle will align its timeline accordingly to ensure continued support for the Microsoft Script Engine, as needed.

Native Script Engine

For more information on the script engine transition updates. See Procedure to switch from Microsoft Engine to Native Script Engine.

Important Announcements

Deprecation of Hyperion Profitability and Cost Management (HPCM) Detailed Application Type

Beginning with release 11.2.27, Profitability and Cost Management (HPCM) will no longer support the creation or use of the Hyperion Profitability and Cost Management (HPCM) Detailed Application type. If you are upgrading from an earlier release, existing HPCM Detailed Applications will no longer be accessible after upgrading to 11.2.27.

Essbase Administration Services Lite (EAS Lite) Deprecation

Essbase Administration Services Lite (EAS Lite) is deprecated as of Essbase 21c and will not be available in Essbase 26.x or later releases. All administrative functionality is now provided through the Essbase Web Platform UI. The new Essbase Web Platform UI delivers a unified, modern interface for streamlined administration and improved user experience.

For more information, see the latest Statement of Direction for Essbase Administration Services Lite (Doc ID 2501038.1)

Supported Platforms

Information about system requirements, browser support, supported languages and supported platforms for Oracle Enterprise Performance Management System products is available in spreadsheet format in the Oracle Enterprise Performance Management System Certification Matrix. This matrix is posted on the Supported Platforms Matrices page on Oracle Technology Network (OTN):

Oracle Enterprise Performance Management System - Certification Matrix.

Supported Paths

Oracle recommends that you apply the set of Oracle Enterprise Performance Management System Release 11.2.27 product Opatches together, using the ApplyUpdate script. If you are updating from an earlier release, you must first update to Release 11.2.15.

  • EPM System updates are released on a quarterly basis, generally in January, April, July, and October.
  • Updates include changes for all embedded components, such as WebLogic and Java, as needed.
  • Updates are applied in place.
  • Any customer patches that were released are rolled into the next update.
  • Updates are expected to be easy to apply and have minimum impact for you to absorb.

Installing EPM for the First Time

Before you install and configure, review the installation prerequisites and requirements listed in Installation Prerequisites and Requirements.

Ensure to have the latest Visual C++ Redistributable for the Hyperion Financial Management (HFM) application. For more information, see Upgrading VC++ from Versions 11.2.15-11.2.20 to 11.2.26.

Table 1-6 Installing EPM for the First Time

Task Reference
1. Optional: Remove Microsoft Visual C++ 2010 (x86 and x64). Optional: Removing Microsoft Visual C++ 2010
2. Install Release 11.2.15 Installing EPM System Products
3. Install HFM using the HFM Linux Installer (11.2.23). Installing and Configuring HFM on Linux
4. Update RCUSchema.properties file Updating RCU Schema Properties
5. Apply Update to Release 11.2.27 Applying Release 11.2.27
6. Configure Release 11.2.27 Configuring EPM System After Applying an Update

Updating from Release 11.2.x

Before you apply the update to Release 11.2.27, review the prerequisites and requirements listed in Applying an Update Prerequisite Tasks.

Table 1-7 Updating to Release 11.2.27 from 11.2.8

Task Reference
1. Apply Update from Release 11.2.8 to Release 11.2.12 or 11.2.13 or 11.2.14 Applying an Update to EPM System Products
2. Install Update to Release 11.2.15 Installing EPM System Products Using Apply Update
3. Apply Update to Release 11.2.27 Applying Release 11.2.27
4. Optional: Remove Microsoft Visual C++ 2010 (x86 and x64). Optional: Removing Microsoft Visual C++ 2010

  1. Restart your machine.

  2. Redeploy all the web applications. (Under HFM, ensure that you check the Configure Application Server option.

  3. Start all the services. For information about starting services, see Starting and Stopping EPM System Products in Enterprise Performance Management System Installation and Configuration Guide .

5. Configure Release 11.2.27 Configuring EPM System After Applying an Update

Table 1-8 Updating to Release 11.2.27 from Versions Earlier than 11.2.8

Task Reference
1. Install Update to Release 11.2.8 Installing EPM System Products Using Apply Update
2. Apply Update from Release 11.2.8 to Release 11.2.12 or 11.2.13 or 11.2.14 Applying an Update to EPM System Products
3. Install Update to Release 11.2.15 Installing EPM System Products Using Apply Update
4. Apply Update to Release 11.2.27 Applying Release 11.2.27
5. Optional: Remove Microsoft Visual C++ 2010 (x86 and x64). Optional: Removing Microsoft Visual C++ 2010

  1. Restart your machine.

  2. Redeploy all the web applications. (Under HFM, ensure that you check the Configure Application Server option.

  3. Start all the services. For information about starting services, see Starting and Stopping EPM System Products in Enterprise Performance Management System Installation and Configuration Guide .

6. Configure Release 11.2.27 Configuring EPM System After Applying an Update

Upgrading from Release 11.1.2.x

You can upgrade Oracle Enterprise Performance Management System Release 11.1.2.x products to Release 11.2.27.

Table 1-9 Upgrading from Release 11.1.2.x

Task Reference
1. Upgrade from 11.1.2.x to Release 11.2.8 Upgrading EPM System
2. Apply Update from Release 11.2.8 to Release 11.2.12 or 11.2.13 or 11.2.14 Applying an Update to EPM System Products
3. Install Update to Release 11.2.15 Installing EPM System Products Using Apply Update
4. Apply Update to Release 11.2.27 Applying Release 11.2.27
5. Optional: Remove Microsoft Visual C++ 2010 (x86 and x64). Optional: Removing Microsoft Visual C++ 2010

  1. Restart your machine.

  2. Redeploy all the web applications. (Under HFM, ensure that you check the Configure Application Server option.

  3. Start all the services. For information about starting services, see Starting and Stopping EPM System Products in Enterprise Performance Management System Installation and Configuration Guide .

6. Configure Release 11.2.27 Configuring EPM System After Applying an Update

Applying and Rolling Back Release 11.2.27

Related Topics

Prerequisites

Table 1-10 Prerequisites for Applying Release 11.2.27

Step Description
Disable Anti-Virus Disable the anti-virus software before you apply Release 11.2.27 to your environment and ensure it remains disabled through out the update process. You may re-enable it after the update is complete.
Check for Patch Conflicts To identify any EPM patch conflicts before applying the quarterly update, enter the following command:
  1. On Windows:

    Note: The following script must only be run with Administrator privileges.

    .\ApplyUpdate.ps1 <MIDDLEWARE_HOME> -verify
  2. On Linux:

    ./ApplyUpdate.sh <MIDDLEWARE_HOME> -verify
Stop Services Stop services:
  • Oracle Enterprise Performance Management System services
  • Node Manager Windows Service and Oracle HTTP Server, if you are using Oracle HTTP Server as your web server
  • WebLogic Administration Server
  • If Essbase is running, stop the servers.

For information about stopping services, see Starting and Stopping EPM System Products in Enterprise Performance Management System Installation and Configuration Guide.

Back Up Folders Back up the following folders before applying the update:
  • EPM Oracle Home. The default EPM Oracle home location is MIDDLEWARE_HOME/EPMSystem11R1.
  • EPM Oracle Instance. The default location for the EPM Oracle Instance is MIDDLEWARE_HOME/user_projects/epmsystem1.

You can delete these folders after you apply the update and validate the installation.
Back Up Keystores

Back up the keystores from:

  • MIDDLEWARE_HOME\jdk\jre\lib\security\cacerts

  • MIDDLEWARE_HOME\EPMSystem11R1\common\JRE\Sun\1.8.0\lib\security\cacerts

Note: A new version of JDK is included with every 11.2.x Release update. During this update process, existing JDK folders are removed and replaced with newer versions. After applying the Release update, you must restore the backed up keystores (cacerts).

To import the keystores, run the following command: Once the keystores are imported, restart all the EPM services for the changes to take effect.

keytool -import -alias alias_name -keystore <path_to_keystore_file> -file <path_to_certificate_file> -storepass keystore_password -trustcacerts

See Configuring SSL-Enabled External User Directories for more information.

TEMP Directory Redirecting the TEMP directory (/tmp) is not supported or feasible during the Apply Update procedure. Ensure the /tmp directory has sufficient space and the necessary permissions. Additionally, confirm that the noexec option is not set on the /tmp directory and remove it if it is enabled.
Back Up Essbase ODBC Driver Configurations

Essbase 21.8.1 deployment includes updated DataDirect ODBC drivers (version 8.0.2).

You need to manually update your ODBC configuration (applies on Linux and Windows).

For more information, see Pre-Applying Release Steps.

Applying Release 11.2.27

Release 11.2.27 applies a set of OPatches for all EPM system components on your environment. Oracle recommends that you apply the entire set using the ApplyUpdate utility.

Ensure that you meet all the prerequisites before you apply Oracle Enterprise Performance Management System Release 11.2.27 to your environment. See Prerequisites for more details.

From the Oracle Software Delivery Cloud (http://edelivery.oracle.com/), select the products that you licensed and add them to the cart. All required zip files are included. Select your platform, and download the files into /download_location.

For the list of deliverables in Release 11.2.27 (Release 11.2, Update 27), see Overview:

Unzip the files into /download_location.

  • Use a zip file extraction program that can handle long path names, such as 7-Zip.
  • If you are prompted that any files or common components already exist, click Yes to overwrite the files.
  • Unzip to a directory with no spaces in the name.

Note:

Essbase Manual ODBC Configurations Steps are required when configured with SQL Server database only.

  1. To perform the Pre-Applying Patch Release 11.2.27:

    NOTE:

    The following steps are only required on the specific host where Essbase is installed.

    You must manually back up the legacy 7.1.6 ODBC configurations to preserve them in case an Essbase version rollback is required.

    1. Locate ODBC Driver configuration files here:

      • odbc.ini: <Domain Root>/<Domain Name>/config/fmwconfig/essconfig/core

      • odbcinst.ini: <Oracle_HOME>/essbase/modules/oracle.essbase.datadirect.odbc/7.1.6/odbcinst.ini

      • ODBC driver libraries: <Essbase Product Home>/modules/

    2. Back up your existing ODBC Driver 7.1.6 configuration files: odbc.ini, and odbcinst.ini.

  2. To Apply Patch Release 11.2.27:

    1. On Windows: Launch Windows PowerShell as an Administrator from the Start menu. Navigate to the directory where you extracted the ZIP files and run the following script. For example, navigate to 11.2.27.0-Update-Win directory and run the following script.

      Note:

      • The following script must only be run with Administrator privileges.
      • Before running the following script, ensure that you do not extract any additional OPatch ZIP folders or OPatch ZIP files under 11.2.27.0-Update-Win directory (which contains the ApplyUpdate.ps1 script) in addition to the ZIP files/folders that are already present. 
      .\ApplyUpdate.ps1 <MIDDLEWARE_HOME>
    2. On Linux: Navigate to the directory where you extracted the ZIP files. Run the following script from the directory where you extracted the ZIP file. For example, navigate to 11.2.27.0-Update-Linux folder and run the following script:

      Note:

      Before running the following script, ensure that you do not extract any additional OPatch ZIP folders or OPatch ZIP files under 11.2.27.0-Update-Linux directory (which contains the ApplyUpdate.sh script) in addition to the ZIP files/folders that are already present. 
      ./ApplyUpdate.sh <MIDDLEWARE_HOME>

  3. To perform the Post-Applying Patch Release 11.2.27:

    1. After applying Release 11.2.27, redeploy the following services:

      • Oracle Hyperion Foundation.

      • Profitability and Cost Management.

      • Data Management (FDMEE)

    2. Configure the Web Server including the LWA (Logical Address for Web Applications) if required.

    3. Manually update the Essbase ODBC Configuration for SQL Server database only:

      Note:

      The following steps are only required on the specific host where Essbase is installed.

      Essbase ODBC Configurations steps are required when configured with SQL Server database only.

      • Linux:

        • Open odbc.ini for editing.

        • Replace the old driver names with new ones, providing the absolute library path in the Driver name entry.

          For example, (replace Oracle_HOME with your system's Oracle_HOME path):

          • From: Driver=<Oracle_HOME>/essbase/modules/oracle.essbase.datadirect.odbc/7.1.6/lib/ARsqls27.so

            To: Driver=<Oracle_HOME>/essbase/modules/oracle.essbase.datadirect.odbc/8.0.2/lib/ARsqls28.so

          • From: Driver=<Oracle_HOME>/essbase/modules/oracle.essbase.datadirect.odbc/7.1.6/lib/ARdb227.so

            To: Driver=<Oracle_HOME>/essbase/modules/oracle.essbase.datadirect.odbc/8.0.2/lib/ARdb228.so

          • From: Driver=<Oracle_HOME>/essbase/modules/oracle.essbase.datadirect.odbc/7.1.6/lib/ARmysql27.so

            To: Driver=<Oracle_HOME>/essbase/modules/oracle.essbase.datadirect.odbc/8.0.2/lib/ARmysql28.so

        • (Optional) replace the old driver descriptions with new ones.

          From: Oracle 7.1 SQL Server Wire Protocol

          To: Oracle 8.0 SQL Server Wire Protocol

        • Save odbc.ini.

        • Edit the odbcinst.ini file.

          <Oracle_HOME>/essbase/modules/oracle.essbase.datadirect.odbc/8.0.2/odbcinst.ini.

          Example for Oracle

          Where Oracle_HOME is your system specific installation path.

          Driver=<Oracle_HOME>/essbase/modules/oracle.essbase.datadirect.odbc/8.0.2/lib/Ardb228.so

        • Save odbcinst.ini.

      • Windows:

        • On the Essbase Windows server, open the Windows Registry Editor (from Start menu, run regedit).

        • Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI.

        • Right click ODBC.INI and select Export. Save it as a backup, in case you need to roll back the OPatch. For example, save the configuration as odbc.orig.reg.

        • Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI.

        • Right click ODBCINST.INI and select Export. Save it as a backup, in case you need to roll back the OPatch. For example, save the configuration as odbcini.orig.reg.

        • Navigate into ODBC.INI and select essbase_datasource

        • For the entries named Driver and Description, right click and select Modify to update the information for all data sources.

          • From: Oracle 7.1 SQL Server Wire Protocol

          • To: Oracle 8.0 SQL Server Wire Protocol

        • Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources.

        • For the entry named essbase_datasource.

          • From: Oracle 7.1 SQL Server Wire Protocol

          • To: Oracle 8.0 SQL Server Wire Protocol

        • On the Essbase Windows Server, navigate to <ESSBASE_PRODUCT_HOME>\modules\oracle.essbase.datadirect.odbc\8.0.2.

        • Make a backup copy of ODBC802.reg (for example, ODBC802_orig.reg).

        • Edit ODBC802.reg, replacing all occurrences of $ODBC_PATH with the absolute path of the ODBC drivers. For example:

          <Local Drive>:\\Oracle\\Middleware\\Oracle_Home\\essbase\\modules\\oracle.essbase.datadirect.odbc\\

        • Double click the edited ODBC802.reg file. This will edit the Windows registry to have entries for the DataDirect 8.0.2 drivers bundled with Essbase 21.8.1.

    4. Start all services now.

      For information about starting services, see Starting and Stopping EPM System Products in Enterprise Performance Management System Installation and Configuration Guide.

Rolling Back Release 11.2.27

Ensure that you meet all the prerequisites before you proceed with the rollback feature.

The rollback feature allows you to rollback all the OPatches except the following:

  • JDK OPatches
  • Weblogic CPU OPatches
  • Oracle Virtual Directory (OVD) OPatch
  • Oracle HTTP Server (OHS) OPatch
  • Fusion Middleware (FMW) OPatches
    • FMW.ADF
    • FMW.EM
  • ODBC OPatch
  • Oracle Hyperion Shared Services OPatch
  • Oracle Hyperion Infrastructure OPatch

To Rollback the update:

  1. On Windows:

    Launch Windows PowerShell from the Start menu as an Administrator and run the following script from the directory where you extracted the ZIP file. For example, navigate to 11.2.27.0-Update-Win directory and run the following script: 

    .\RollbackUpdate.ps1 <MIDDLEWARE_HOME>

    Ensure that the Essbase Rollback steps are only required on the specific host where Essbase is installed.

  2. On Linux:

    Navigate to the directory where you extracted the ZIP files. Run the following script from the directory where you extracted the ZIP file. For example, navigate to 11.2.27.0-Update-Linux folder and run the following script: 

    ./RollbackUpdate.sh <MIDDLEWARE_HOME>

To perform the Post-Rollback update:

  1. After applying Release 11.2.27, redeploy the following services:

    • Oracle Hyperion Foundation.

    • Profitability and Cost Management.

    • Data Management (FDMEE)

  2. To Rollback the Essbase version, perform these steps:

    Note:

    Ensure that the Essbase Rollback steps are only required on the specific host where Essbase is installed.

    • To Rollback Essbase on Windows:

      1. Delete the ODBC.INI registry entry.

      2. Double click odbc.orig.reg and previous entries will be restored.

        Alternatively, you can import or merge the registry entries.

      3. Delete ODBCINST.INI registry entry.

      4. Double click the odbcinst.orig.reg and previous entries will be restored.

        Alternatively, you can import or merge the registry entries.

    • To Rollback Essbase on Linux:

      1. Restore the ODBC.INI configuration.

        From:

        cd <Domain Root>/<Domain Name>/config/fmwconfig/essconfig/core --odbc_ini_orig

        To:

        cd <Domain Root>/<Domain Name>/config/fmwconfig/essconfig/core --odbc_ini

      2. Restore ODBCINST.INI configuration.

        From:

        cd <Oracle_HOME>/essbase/modules/oracle.essbase.datadirect.odbc/7.1.6/odbcinst.ini

        To:

        cd <Oracle_HOME>/essbase/modules/oracle.essbase.datadirect.odbc/8.0.2/odbcinst.ini

        Note:

        See ODBC Configuration File Path Details.

  3. Start all services now.

    For information about starting services, see Starting and Stopping EPM System Products in Enterprise Performance Management System Installation and Configuration Guide .

Verifying Status

You can check the status of the ApplyUpdate or Rollback script by following one of the steps below:

  1. Open Oracle Enterprise Management System Workspace, click Help > About Oracle Enterprise Performance Management System Workspace, Fusion Edition > Show Details.
  2. Check the inventory for Oracle Enterprise Performance Management (EPM) OPatches. To check the inventory for EPM OPatches, enter the following command in one line:

    Before running this command, ensure that you change the directory from the command line to : <MIDDLEWARE_HOME>\EPMSystem11R1\OPatch

    • On Windows: opatch lsinventory -oh <MIDDLEWARE_HOME>\EPMSystem11R1 | findstr /i /L /c:"Patch"
    • On Linux: opatch lsinventory -oh <MIDDLEWARE_HOME>\EPMSystem11R1 | grep "Patch[ ][ ]"
    Sample Output:
D:\Oracle\Middleware\EPMSystem11R1\OPatch lsinventory -oh D:\Oracle\Middleware\EPMSystem11R1\OPatch | findstr /i /L /c:"Patch  "
Patch  33727616     : applied on Sun Feb 20 23:39:56 PST 2026
Patch  33678607     : applied on Sun Feb 20 23:36:01 PST 2026
Patch  33093748     : applied on Sun Feb 20 23:35:18 PST 2026
Patch  32720458     : applied on Sun Feb 20 23:34:51 PST 2026
  3. Check the inventory for Oracle Fusion Middleware (FMW) OPatches. To check the inventory for FMW Opatches, enter the following command in one line:

    Before running this command, ensure that you change the directory from the command line to : <MIDDLEWARE_HOME>\OPatch

    • On Windows: opatch lsinventory -oh <MIDDLEWARE_HOME> | findstr /i /L /c:"Patch"
    • On Linux: opatch lsinventory -oh <MIDDLEWARE_HOME> | grep "Patch[ ][ ]"
    Sample Output:
Oracle Interim Patch Installer version 13.9.4.2.7
OPatch version    : 13.9.4.2.7
OPatch detects the Middleware Home as "D:\Oracle\Middleware"
Patch  33727616     : applied on Tue Apr 12 19:02:01 EDT 2026
Unique Patch ID:  24578917
Patch description:  "WLS PATCH SET UPDATE 12.2.1.4.220105"
Patch  33678607     : applied on Tue Apr 12 18:59:04 EDT 2026
Unique Patch ID:  24558585
Patch description:  "RDA release 20.4-20211126 for OFM SPB"
Patch  33093748     : applied on Tue Apr 12 18:58:36 EDT 2026
Unique Patch ID:  24325771
Patch description:  "One-off"
Patch  32720458     : applied on Tue Apr 12 18:58:19 EDT 2026
Unique Patch ID:  24558359
Patch description:  "JDBC 19.3.0.0 FOR CPUJAN2022 (WLS 12.2.1.4, WLS 14.1.1)"
Patch  1221412      : applied on Tue Apr 12 18:57:54 EDT 2026
Unique Patch ID:  24516660
Patch description:  "Bundle patch for Oracle Coherence Version 12.2.1.4.12"
Patch  33697227     : applied on Tue Apr 12 18:54:58 EDT 2026
Unique Patch ID:  24560598
OPatch succeeded.
  4. Check the inventory for Oracle HTTP Server (OHS) OPatches. To check the inventory for OHS Opatches, enter the following command in one line:

    C:\Oracle\Middleware\ohs\OPatch>opatch.bat lsinventory -oh C:\Oracle\Middleware\ohs | findstr /i /L /c:"Patch"

The log file details and location of the files are described in the table below:

Table 1-11 Log Names and Location

Script Summary Log File Name Detail Log File Name Location
ApplyUpdate ApplyUpdateSummary.log ApplyUpdateDetail-<Day>.<DD>.<MM>.<YYYY>-<HH>.<MI>.<SS>.log <EPM_ORACLE_HOME>/diagnostics/logs/install/
RollbackUpdate RollbackUpdateSummary.log RollbackUpdateDetail-<Day>.<DD>.<MM>.<YYYY>-<HH>.<MI>.<SS>.log <EPM_ORACLE_HOME>/diagnostics/logs/install/

Summary log contains the status of each product OPatch and detail log contains the detailed information about the status of each OPatch applied along with the OPatch output. For more details on OPatches Common Error Messages, tips and troubleshooting, see Tips and Troubleshooting.

Optional: Applying Individual OPatches

Oracle recommends that you apply the set of Oracle Enterprise Performance Management System Release 11.2.27 product Opatches together, using the ApplyUpdate script. See Applying Release 11.2.27 for more details.

However, you can also apply selected OPatches based on your operating system environment:

Note:

It is recommended to take a back up of the original configure<OS>.properties file before you edit the properties file for the desired OPatches.
  1. From the directory where you downloaded and extracted the 11.2.27.0-Update-<OS> folder, open configureWindows.properties or configureLinux.properties file based on your operating system.
  2. In the configure<OS>.properties file, include only those products that you want to apply. For example, if you want to apply Oracle Hyperion Calculation Manager OPatch, ensure that the entry CALC=39836026 is present in the configure<OS>.properties file. The list of individual products and their OPatch IDs in the configure<OS>.properties file are listed below:
    • CALC=39836026
    • FDMEE=39798264
    • FCM=39563227
    • HFM=38893225
    • FR=39804821
    • HP=39816022
    • HPCM=39826679
    • HSS=39695295
    • Infra=39695300
    • InfraCommon=39808812
    • TAXPROV=39837389
    • Workspace=39798165
    For more details on individual EPM system products, OPatch ZIP file names and OPatch IDs, see OPatch Dependencies and Details.
  3. Run the ApplyUpdate Script to apply the individual OPatch:
    • On Windows:

      Note:

      The following script must only be run with Administrator privileges. 
      ApplyUpdate.ps1 <MIDDLEWARE_HOME>
    • On Linux: 
      ApplyUpdate.sh <MIDDLEWARE_HOME>

    Note:

    For additional information, refer to your individual OPatch Readme Guide.

OPatch Dependencies and Details

The following table lists the set of OPatches and dependencies for individual EPM system components:

Table 1-12 OPatch Details

Product Product OPatch ID OPatch Dependency - Component OPatch Dependency - ID
Oracle Hyperion Calculation Manager (CALC) 39836026 NA NA
Oracle Hyperion Financial Data Quality Management Enterprise Edition (FDMEE) 39798264 NA NA

Oracle Hyperion Financial Close Management (FCM)

Note: Oracle Hyperion Tax Governance is included in this OPatch.

39563227 NA NA
Oracle Hyperion Financial Management (HFM) 38893225 ADF 39597055
WebLogic 39683721
Oracle Hyperion Financial Reporting (FR) 39804821 NA NA
Oracle Hyperion Planning (HP) 39816022 NA NA
Oracle Hyperion Profitability and Cost Management (HPCM) 39826679 NA NA
Oracle Hyperion Shared Services (HSS) 39695295 Oracle Hyperion Infrastructure (Infra) 39695300
Oracle Hyperion Infrastructure (Infra) 39695300 Oracle Hyperion Shared Services (HSS) 39695295
Oracle Hyperion Infrastructure (Infra) Commons 39808812 NA  
Oracle Hyperion Tax Provision (TAXPROV) 39837389 NA NA
Oracle Hyperion Enterprise Performance Management Workspace (Workspace) 39798165 NA NA

Error Correction Policy

This topic outlines the error correction policies for Oracle Enterprise Performance Management (EPM) Release 11.2.x.

For information on the Oracle Enterprise Performance Management Error Correction Policy, visit these My Oracle Support articles:

  • Oracle Enterprise Performance Management (EPM) 11.2 Software Error Correction Policy [Doc ID 2749950.1]
  • Oracle Enterprise Performance Management (EPM) Release 11.2 Grace Periods for Error Correction [Doc ID 2627593.1]
  • Oracle Hyperion Financial Management Error Correction will be OPatch based.

Defects Fixed

Release 11.2.27 resolves the following defects:

Table 1-13 Defects Fixed in 11.2.27

Defect Number Description
Oracle Hyperion Financial Management
36765310 You can search for and select entities reliably in Financial Management web forms, including entities near the end of large member lists.
38140016 Applications created through import can now be opened successfully in Financial Management.
38442944 Financial Management improves memory handling when retrieving member properties through the MetadataOM API, supporting more stable processing for workloads that use this API.
38560711 Financial Management improves journal creation when currency validation is encountered, reducing interruptions caused by an invalid-currency message.
39275337 Financial Management Tax improves Calculate and Consolidate processing after an upgrade to 11.2.24.
39465933 Financial Management improves Lifecycle Management artifact processing when the current service is temporarily unavailable.
39575793 Financial Management improves application stability during consolidation processing in 11.2.23.
39581983 The Native Script Engine now provides versioning information for use in scripts and related automation.
39583447 Financial Management improves stability for applications that could previously stop unexpectedly during consolidation.
39704688 The MetadataOM "GetMemberPropertiesUsingMembers" API preserves parent-member information in Financial Management 11.2.21 and later releases.
39717003 Financial Management improves Native Script Engine processing so that consolidation does not abort unexpectedly.
39725922 Custom Documents now honor the configured security class in Financial Management.
39767954 Financial Management improves consolidation processing after an application is switched to the BSL application type.
39768497 Financial Management improves member-list file processing after an application is switched to the BSL application type.
39858686 You can assign Access Control in Financial Management 11.2.26 when external SSL offloading is configured.
Oracle Hyperion Profitability and Cost Management
39954435

Calculation Enhancement: The custom calculation rule formula has been enhanced to support the NONEMPTYTUPLE directive, which you can use to avoid calculating empty result sets. This can lead to a significant performance increase for rules that operate on sparse data.

For more information, see the Skipping Empty Tuples to Optimize Custom Calculations section.

39854964

Allocation rules now apply parent-member filters to all corresponding level-0 descendants, so include and exclude ranges correctly reflect filters specified on either leaf or parent members.

Oracle Hyperion Planning
39508750

When metadata or data load using Outline Load utility with relational database as source is executed, the number of records processed statistics may be displayed incorrectly.
Oracle Hyperion Financial Data Quality Management, Enterprise Edition (FDMEE)
38797590

Oracle E-Business Suite (EBS) source-system initialization now completes correctly in Data Management instead of submitting a job that hangs without creating the expected ODI process.

Oracle Hyperion Financial Close Management
39672439

Activity-summary email links now open Close Manager correctly instead of displaying a blank page and causing navigation errors until the session is reopened.

Oracle Hyperion Financial Reporting
39804864

Financial Reporting books now continue to work after an issue is fixed where a data source heading value is de-serialized as a number.

Oracle Hyperion Enterprise Performance Management Workspace
36606419 508: Open document popup dialog options expanded state incorrectly read by jaws.
39638054 Manage favorites menu item disabled when no favorites exist.

See Defects Fixed: 11.2.0 - 11.2.26 for the list of cumulative defects fixed starting from Release 11.2.0.

Known Issues

Release 11.2.27 includes the following known issues.

Table 1-14 Known Issues in 11.2.27

Defect Number Description

Oracle Hyperion Infrastructure Technology
40057720

When upgrading an EPM instance from a release earlier than 11.2.26 directly to 11.2.27 or later release, connections to configured external user directories may fail due to new encryption algorithm.

Workaround: Update the password for each configured external provider in the Shared Services Console and restart the service; alternatively, use the Registry command to download CSS.xml, update the external provider passwords in plain text, and then update CSS.xml.

39186085

In EPM 11.2.20 and later, Oracle HTTP Server (OHS) may purge previously rotated OHS access and admin logs from httpConfig\ohs\servers\ohs_component\logs during OHS startup, which can cause archived logs required for auditing to be missing.

Workaround: To set the retention value to 0 in both httpd.conf and admin.conf to disable log purging.

For example:

  • CustomLog "||${PRODUCT_HOME}/bin/odl_rotatelogs ${ORACLE_INSTANCE}/servers/${COMPONENT_NAME}/logs/access_log 43200 0" common

  • CustomLog "||${PRODUCT_HOME}/bin/odl_rotatelogs ${ORACLE_INSTANCE}/servers/${COMPONENT_NAME}/logs/admin_log 43200 0" common

For more information, see Unexpected Purging of Older Oracle HTTP Server (OHS) Logs at Startup in Installation and Configuration Troubleshooting Guide
39007726

After applying Essbase 21.8.1 and then rolling back (downgrading) to an Essbase version earlier than 21.8, applications that were created or last updated on 21.8.1 may not be displayed in the EAS Console. This happens because pre-21.8 Essbase versions cannot interpret the encrypted metadata introduced in 21.8.x, which can cause the application’s EAS Managed setting to be cleared during the rollback. After re-enabling EAS management, the applications correctly reappear and can be administered in EAS as expected.

Workaround: In the Essbase Web User Interface (or using the Essbase REST APIs), re-enable the EAS Managed flag for the affected application. For more information, see Manage Applications Using EAS Lite
39039397

After upgrading to Essbase 21.8.1 (for example, via EPM 11.2.27 update), the required SQL/ODBC configuration is not automatically applied, which can cause issues in EPM products that rely on Essbase connectivity.

Workaround: Perform the manual ODBC configuration steps documented for Essbase 21.8.1 upgrades. The specific steps vary depending on your operating system. See Upgrade to Essbase 21.8 Requires Manual ODBC Configuration
38442505

In distributed EPM deployments where Foundation is installed on one machine (hostname1) and other components (Planning/CalcManager, and so on) are installed on a different machine (hostname2), the generated startManagedWebLogic.sh script may contain an incorrect WebLogic Server URL that points to hostname2 instead of the Foundation (AdminServer) host (hostname1).

Workaround: Edit <EPM_ORACLE_INSTANCE>/user_projects/domains/EPMSystem/bin/startManagedWebLogic.sh and update ADMIN_URL to use the correct AdminServer host/port (for example, change http://<hostname2>:7001 to http://<hostname1>:7001)

39084422

During database re-hosting on single and distributed Windows deployments, the Essbase CHGHOST utility on the Essbase Virtual Machine (VM) may report an ODI T2P plugin error. This message is ODI related and does not impact Essbase re-hosting when ODI is not used.

Workaround: If you are not using ODI, ignore the ODI error and continue the re-hosting procedure.

38584088

Creating a new Taskflow with the browser language set to French Canadian results in an error due to missing variables. The Taskflow works as expected when the browser language is set to English, but it fails in other languages.

38257991

In HFM environments upgraded to 11.2.19 or later, users with their browser language set to Italian experienced errors when editing task flow start dates. The system displayed dates in DD/MM/YYYY format, but saving triggered an Invalid start date format.

Workaround: Ensure to use DD/MM/YYYY format to avoid "Invalid month value" error.

Oracle Hyperion Calculation Manager
39473348 In Calculation Manager, the Analyze Script option may fail to produce the expected diagnostic information.
39121046 In Calculation Manager, the Debug option may not work.
Oracle Hyperion Planning
40009093

Business rules that use Planning Custom-Defined Functions (CDF) in the script may fail to execute.

Workaround:

1. Copy HspCDFUt.jar from <Oracle_EPM_Home>/products/Planning/lib folder from Planning server and paste to <Oracle_Middleware_home>/essbase/products/Essbase/EssbaseServer/java/udf folder.

2. If Essbase is installed on multiple servers, copy the jar to all the Essbase servers.

3. Re-start Essbase services.

39010704

Creating the Planning Application such as Sample Vision could fail on Microsoft SQL Server due to an Essbase SQL Server ODBC driver configuration issue, which caused Essbase errors during artifact import and resulted in incomplete application creation.

Workaround: You must ensure to manually configure Essbase ODBC driver so that Planning application is created successfully with all data. See Upgrade to Essbase 21.8 Requires Manual ODBC Configuration
Oracle Hyperion Financial Reporting
NA
  • Prepositions used in search strings are not working. For example, when you search:
    • "StockAgeing_analysis by BS", if you remove "by" it works.
    • "PL by entities", search string "PL entities" works fine
  • When using the search feature, ensure the search text field on Workspace's top right side has the intended search string, or if using Advanced Search this top right search field is empty; otherwise, it will append the previous search text and the new search text.
Oracle Hyperion Profitability and Cost Management
39916746

Detailed Profitability Applications are no longer supported and will not be accessible in this patch. Legacy Detailed Profitability applications are hidden and entry points across the workspace, application lists, application-type selection, and REST APIs are removed.

If you installed this patch but are still using Detailed applications, you should roll back this patch. Your Detailed Profitability applications will become accessible again after rolling back this patch and then re-registering each application. To re-register after rolling back:

  • 1. In the Profitability Applications console, select the Detailed application that you want to continue using, then select Re-Register from the Actions menu.

  • 2. In the Workspace Navigator, select Applications > Refresh. You will be able to see the re-registered application in the Applications > Profitability list.

39976279

For Linux server instances, the Profitability service may fail to shut down due to a known issue with EclipseLink JMS cache coordination. The current workaround is to configure two stop server settings for FMW 14c: GracefulShutdownTimeout and IgnoreSessionsDuringShutdown.

  • 1. Enable the IgnoreSessionsDuringShutdown to allow the server to shut down even when HTTP sessions are still active.

  • 2. Set the GracefulShutdownTimeout to a reasonable amount of time such as 120 seconds to force shutdown if the EclipseLink fails to release the JMS message resource.

For more information, see the Server: Administration: Start or Stop section in Fusion Middleware Control Help for WebLogic Server.

38966131

When importing an application template, the Import Template dialog allows you to select from the Essbase clusters that are defined for the environment. However, the selected cluster value doesn't always get saved as it should, and is then treated as NULL during the import. This results in failure to create the Essbase cube during template import, and hence failure to load the input data if present. The Template Import job will show Success status, even though the cube and the input data weren't imported. Note that this problem only occurs with Template Import. The Essbase Cluster is correctly saved when creating a new application from scratch.

Workaround: If you experience this issue, you can follow these steps:

1. Open the application and in Model Summary, Model Level Preferences, select the appropriate Essbase Cluster value and save the change.

2. Go to Manage Database > Essbase Deploy and deploy the cube.

3. Extract the InputData text file from the template, then import it using Manage Database > Data Load.

35715398

Because of an Essbase Error (1290010) in Essbase 21c, calculations for one or more POVs are unsuccessful. This is caused when an allocation or other calculation script runs longer than the time allowed by the current Essbase configuration. Workaround: Add the following lines to the essbase.properties file to prevent the timeout:

  • olap.server.netSocketTryInfinite=false

  • olap.server.netRetryCount=144000

    (144000 is equivalent to 8 hours)

For more details, see the Provider Services Configuration chapter in Configuration Reference for Oracle Essbase.
35743432 Member formulas requiring double quotes in their syntax can be imported in Update Dimension by using double double quotes around the formula. However, if that dimension is later exported using Export Dimension, those formulas will each be exported with only a single set of double quotes. To re-import that dimension using the exported the file, the file must be edited to re-add the extra set of double quotes for each formula that requires double quotes in its syntax.
38412133 Occasionally, a deploy cube failure occurs when using an APS Essbase connection in a Windows distributed environment configured for SSL. As a workaround, use an embedded Essbase connection to complete the deploy operation successfully.
36888486

By default, Profitability and Cost Management supports up to 15 Management Ledger applications. This limit is in place because Management Ledger applications use a dimension cache to accelerate UI interactions and improve the performance of batch jobs. During the startup of the Profitability service, the cache for all existing Management Ledger applications is loaded. The limit prevents out-of-memory errors during service startup, and long service startup times. Starting in Release 11.2.19, the applications limit is controlled by a user-configurable governor which allows you to increase this limit, provided the server is configured with sufficient memory. Contact Oracle Support if you need access to this governor.
35889576

When you install Profitability and Cost Management on Linux using a language other than English, only that language will be functional for end users in the UI, even after you select a different language in the browser settings.

When you install on Linux using English, all supported languages will be available for end users, by changing the language in the browser settings. This problem is not known to affect Windows installations.
36198484

For clustered environments where there are more than one managed Profitability instance, e.g. Profitability0 and Profitability1, there is an installation preference that must be set in order to fully enable the communication between the clustered nodes. Execute the following SQL in a tool like Oracle SQL Developer, while logged in as the Profitabilty product schema owner. Be sure to commit the change, and then restart the Profitability service.

INSERT INTO HPM_INSTALLATION_PREFERENCE
   (ID,NAME,VALUE,HPM_INSTALLATION_ID,CREATED_TIMESTAMP,CREATED_USERID,MODIFIED_TIMESTAMP,MODIFIED_USERID,DISPLAY_ORDER)
VALUES (46, 'dimension.cache.cluster.refresh.enabled', 'Y', 1, SYSDATE, 'INIT', SYSDATE, 'INIT', 46);

This will ensure that dimension updates will be visible in both nodes.

If you revert to non-clustered mode, you should delete this row and restart the Profitability service, to disable the dimension cache cluster refresh.
36353159 When a Profitability application template exported from a Windows instance is successfully imported into Linux instance, a rare failure to create the Essbase cube from the InputData content in the template may occur. This rare situation is generally discovered when accessing the missing cube. To resolve the issue, follow these steps:
  1. Use Manage Database > Essbase Deploy to create the calculation cube.
  2. Use Manage Database Data Load to load the text file found within the template's InputData folder.
35659280

Standard Profitability Applications are no longer supported, and will not be accessible in this patch.

If you installed this patch but are still using Standard applications, you should roll back this patch. Your standard applications will become accessible again after rolling back this patch and then reregistering each application. To reregister:

  1. In the Profitability Applications console, select the Standard application that you want to continue using, then select Re-Register from the Actions menu.
  2. In the Workspace Navigator, select Applications and then, click Refresh. You will now see the reregistered application in the Applications > Profitability list.
36124578 Starting with the 11.2.16 release, the REST Sample Client can only be run on the server where Profitability and Cost Management is installed. See the Oracle Hyperion Profitability and Cost Management REST API Developer’s Guide for details.

See Known Issues: 11.2.0 - 11.2.26 for the list of cumulative known issues starting from Release 11.2.0.

Tips and Troubleshooting

Tips and troubleshooting topics are listed in the Installation and Configuration Troubleshooting Guide.

All Oracle Enterprise Performance Management System guides are available in the library on the Oracle Help Center: https://docs.oracle.com/en/applications/?tab=8.

Documentation Updates

Accessing EPM System Product Documentation

Find the latest Oracle Enterprise Performance Management System product guides in the Oracle Help Center (https://docs.oracle.com/en/). To access documents to view or download, click the Applications icon. In the Applications Documentation window, select the Enterprise Performance Management tab, and then look for your release in the Enterprise Performance Management list.

You can also find deployment-related documentation on the Oracle Technology Network (http://www.oracle.com/technetwork/index.html) and on the Oracle Software Delivery Cloud website (http://edelivery.oracle.com/EPD/WelcomePage/get_form).

Reviewing EPM Critical Security Patch Updates (CSPU) and EPM Patch Advisory Document (PAD) Updates

Critical Security Patch Updates (CSPU) Patch Advisor

You must review the Security Alerts as the source of truth for release-specific guidance.

Enterprise Performance Management Patch Advisory Document

You must review the Oracle Enterprise Performance Management Patch Advisory Document (PAD) Updates for release-specific guidance.

Appendix

New Features: 11.2.8 - 11.2.26

This section includes the list of cumulative new features starting from Release 11.2.8. You can also review the list of new features from previous releases by using the Cumulative Feature Overview (CFO) tool. This tool enables you to identify the products you own and your current implementation release. With a single click, the tool quickly produces a customized report of new feature descriptions. This CFO tool is available here:https://apexapps.oracle.com/pls/apex/f?p=20620:1:0

Table 1-15 New Features: 11.2.0 - 11.2.26

Release Link to New Features
New Features: 11.2.23 - 11.2.26 11.2.23 | 11.2.24 | 11.2.25 | 11.2.26
New Features: 11.2.18 - 11.2.22 11.2.18 | 11.2.19 | 11.2.20 | 11.2.21 | 11.2.22
New Features: 11.2.13 - 11.2.17 11.2.13 | 11.2.14 | 11.2.15 | 11.2.16 | 11.2.17
New Features: 11.2.8 - 11.2.12 11.2.8 | 11.2.9 | 11.2.10 | 11.2.11 | 11.2.12

Defects Fixed: 11.2.0 - 11.2.26

This section includes the list of cumulative defects fixed starting from Release 11.2.0.

Table 1-16 Defects Fixed: 11.2.0 - 11.2.26

Release Link to Defects Fixed
Defects Fixed: 11.2.21 - 11.2.26 11.2.21 | 11.2.22 | 11.2.23 | 11.2.24 | 11.2.25 | 11.2.26
Defects Fixed: 11.2.16 - 11.2.20 11.2.16 | 11.2.17 | 11.2.18 | 11.2.19 | 11.2.20
Defects Fixed: 11.2.11 - 11.2.15 11.2.11 | 11.2.12 | 11.2.13 | 11.2.14 | 11.2.15
Defects Fixed: 11.2.6 - 11.2.10 11.2.6 | 11.2.7 | 11.2.8 | 11.2.9 | 11.2.10
Defects Fixed: 11.2.0 - 11.2.5 11.2.0 (NA) | 11.2.1 | 11.2.2 | 11.2.3 | 11.2.4 | 11.2.5

Known Issues: 11.2.0 - 11.2.26

This section includes the list of cumulative known issues starting from Release 11.2.0.

Table 1-17 Known Issues: 11.2.0 - 11.2.26

Release Link to Known Issues
Known Issues: 11.2.21 - 11.2.26 11.2.21 | 11.2.22 | 11.2.23 | 11.2.24 | 11.2.25 | 11.2.26
Known Issues: 11.2.16 - 11.2.20 11.2.16 | 11.2.17 | 11.2.18 | 11.2.19 | 11.2.20
Known Issues: 11.2.11 - 11.2.15 11.2.11 | 11.2.12 | 11.2.13 | 11.2.14 | 11.2.15
Known Issues: 11.2.6 - 11.2.10 11.2.6 | 11.2.7 | 11.2.8 | 11.2.9 (NA) | 11.2.10
Known Issues: 11.2.0 through 11.2.5 11.2.0 | 11.2.1 | 11.2.2 | 11.2.3 | 11.2.4 | 11.2.5