Final Hyperion WebLogic 10.3.6 Patch For EPM 11.1.2.4

 Thanks to Dave Shay.

Final WebLogic 10.3.6 Patch For EPM 11.1.2.4

A commenter on this blog, Ben, shared how to get the final WebLogic 10.3.6 patch for Hyperion / Oracle EPM 11.1.2.4.  We may download this patch without needing to get a password from Oracle Support.  The patch number is:

33471254

You need to be on an active Oracle Support contract for your EPM 11.1.2.4 in order to access the patch.

Ben also indicated we may pull up an Oracle Knowledge Base article that lists the final patches for various components of the EPM 11.1.2.4 suite.  The KB # is:

2796575.1

When you pull up this KB article, crtl-f in your browser and plug in this text to jump directly to the Hyperion section:

3.3.22 Oracle Hyperion Infrastructure Technology

If your 11.1.2.4 environment includes Essbase, we can expect more Essbase 11.1.2.4 patches to come out in 2022, because (for now) EPM 11.2.x uses Essbase 11.1.2.4 under the covers.

As of EPM 11.2.7.0, Essbase 12c is still not certified for Hyperion Planning.  Once an 11.2.x comes out that certifies Essbase 12c for Planning, I'll take a closer look at it.

As per the 11.2.7.0 README, EPM 11.2.x patches are expected to be released Quarterly according to this rough schedule (Oracle Corporation's Safe Harbor applies here):  January, April, July, and October.

On Oracle's EPM 11.2 documentation hub, click "Essbase" on the left-hand side.  Among other things, we are explicitly told to use Essbase 11.1.2.4:

"Use Essbase 11.1.2.4, which is compatible with Enterprise Performance Management Release 11.2.x"

Consult the 11.2.7.0 Install+Config Guide for more information about using Essbase 12c in an EPM 11.2.5+ environment.

Many of you are on PTO this week, so you might not notice this post until early 2022.

Have a Happy New Year!

What’s new in Hyperion EPM 11.2.7 ?

  - Improved protection for your target-system data of being overwritten during data loads in FDMEE. For more information, Enable Data Protection.

- There is no longer VB support for FDMEE. Customers need to migrate to Jython as the scripting language. Don’t worry if this sounds scary, we got you! Syntax can help you take care of these Jython conversions.

- There is no longer a dependency on WebLogic Admin server when starting up the EPM services.

- There is additional support for SSL for Oracle Essbase.

- There is additional support for IDM Products with header-based authentication.

- For folks who are into tuning, the default maximum heap size for Essbase JVM has changed to 1.2GB.

- After applying the 11.2.7 update, the only required configuration tasks are Deploy To Application Server for FDMEE followed by configuring the Web Server.

- Oracle JDK 1.8.0_291 is now the version of Java Development Kit installed with EPM 11.2.7.

- Be sure to review the documentation notes concerning the Windows Server 2019 Data Center Edition on the EPM support matrix. Learn more.

- The Smart View URI setting has been added back to the Workspace Server Settings in EPM Workspace. This was a bug in an earlier version.

- There are no more ‘scheduler job errors’ with the task flows. You can now successfully import task flows exported from 11.1.2.4.x EPM System into 11.2.x EPM System using Lifecycle Management for Oracle EPM.

- Reference the Financial Reporting Defects Fixed page for the bugs fixed in FDMEE, Planning, and HFM.

- For Oracle Hyperion Financial Data Quality Management, Enterprise Edition users, you must grant permission prior to applying the update to Release 11.2.5 or Release 11.2.6. [On the SYSTEM.schema_version_registry table – grant all to <FDMEE_SCHEMA_UESR>]

Hyperion 11.2.7 migration path from older releases

 How can you upgrade your application to 11.2.7?

There are several different upgrade paths depending on your version of EPM. See the below options.

• Release 11.2.5 & 11.2.6: make use of the ‘Apply Update’ option for upgrading the footprint to 11.2.7
• Release 11.2.4: Upgrade (‘Apply Update’) to 11.2.6 & then to 11.2.7
• Release 11.2.3: Upgrade (‘Apply Update’) to 11.2.5 & then to 11.2.7
• Release 11.2.2: Upgrade (‘Apply Update’) to 11.2.4 → 11.2.6 → 11.2.7
• Release 11.2.1: Upgrade (‘Apply Update’) to 11.2.3 → 11.2.5 → 11.2.7
• Release 11.2.0: Upgrade (‘Apply Update’) to 11.2.2 → 11.2.6 → 11.2.7
• Release 11.1.2.4.x: Upgrade to 11.2.x by installing the software on the new machines followed by migrating the applications (metadata & the data)
• Release 11.1.2.3 or earlier: Upgrade your environment to 11.1.2.4 followed by 11.2.x