Friday, August 23, 2019

Why Upgrade to EPM 11.2 or Move to the Cloud?

The title of this post is a question I get asked quite a bit.

By now, most on-premises customers have moved to Hyperion / Oracle EPM, which is the latest release currently available today

Upgrading on-premises can be a bit of a "project", depending upon how complex the environment is, and if any re-work is needed.  (For example: if you're on or prior and using FDM Classic Edition, the FDM content has to be re-implemented into FDM Enterprise Edition as part of the upgrade to

For this reason, many on-premises EPM shops tend to delay upgrades as long as possible.  Upgrades are usually disruptive to key end-users, and costs are involved from IT.  Consulting costs are also involved if you don't have deep EPM Infrastructure expertise in-house.  The typical upgrade cycle for many EPM customers, therefore, tends to be no more frequent than every 5 years.

There was a mad rush to upgrade to a few years ago when Microsoft ceased support for all browsers older than IE 11.  I think we will again see a mad rush to either EPM 11.2 or the Cloud very soon.  Read on to find out why!

Operating Systems

The majority of on-premises EPM systems run on Microsoft platforms.  EPM and older runs on MS Windows Server 2008 R2, and EPM runs on either 2008 or 2012.

2008 is already out of Microsoft Extended Support.  2012 will come out of Extended Support on October 10, 2023.

In the case of UNIX variants, there many "flavors" of UNIX.  The most popular one where EPM is concerned is Red Hat Enterprise Linux (RHEL).  Both EPM and are certified to run on RHEL 6.  Where RHEL 6 is concerned, we refer to the chart below.

(Content cropped from

So RHEL6 was released in 2010, and depending upon which support package your IT department purchased, it is either out of support now, or is coming out of support soon.


The two most popular databases for EPM I've seen "out in the wild" are MS SQL Server 2012 R2 and Oracle Enterprise Database 12.x.  EPM runs on MS SQL Server 2008 (SP3 should have been applied by now) and an older version of Oracle 12 or lower.

Let's talk about MS SQL Server first, as that one is slightly more popular than Oracle, as far as I've observed.  Again, let's refer to the chart.

(Source: Google search "MS SQL Server End of Life")

IT Departments

Both from an Operating System and Database perspective, Finance will be pressured by IT to upgrade, due to operating system support.  IT highly frowns on running systems that are out of vendor support!  (As a former IT guy myself, I know all too well how IT shops run internally, and how Compliance and/or Risk Management departments can tend to be a bit inflexible in this regard).

Hyperion / Oracle EPM

If you are running or older, the clock has already run out.  You are on what is called Lifetime Support.  In Plain English(TM), this means:
  • No new defect fixes
  • No new security patches
  • Access to the Knowledge Base
  • Access to previously issued patches
If you're on, which most of you should be on by now, you are still getting defect fixes and security patches, but the clock is ticking.  Let's refer to the Oracle Knowledge Base, article # 2251273.1.  I  won't paste the whole thing here, but here's the key nugget of information:

"... the end of Premier Support moved from December 2018 to December 2020.  The end of Extended Support remains at December 2021."
(Source: Oracle Corporation)

This means according to the Oracle Support package your company purchased, you either have until Dec 2020 or Dec 2021 to either upgrade or move to the Cloud.


EPM through ship with Java SE 6 and JRockit 6.  Only EPM is certified to replace Java 6 and JRockit 6 with Java SE 7 (see:

Chart time!


EPM Customers who are still paying their Oracle maintenance are on the "Extended Support" column as shown above.

Java 6 and JRockit 6 came out of support at the end of 2018.  As of this writing, Oracle is still issuing Quarterly security patches for Java 7.

EPM 11.2 is expected to ship with Java 8.  This would extend Java's support lifetime through March 2025.  It is my hope that Oracle issues a certification and upgrade instructions to let us upgrade the servers to Java 9 sometime before March 2025.  Otherwise, we'd be looking at a potential security problem in the future.


Look at all of the support expiration dates above, and we see the shortest "lifetime" is the one for EPM

If you don't think EPM 11.2 will be ready in time for a 2020 upgrade, or if your 2020 budget has already been established, then either switch over to Oracle's Extended Support plan or start looking at the Cloud.  (Note: the Cloud isn't for everyone.  There are some cases where it is a perfect fit, and other cases where the on-premises applications are too mature and integrated with each other.)

A big benefit of the Cloud is that once you've migrated into the Cloud, you will never again have to worry about future upgrades required by support expiration dates.  It is a double-edged sword, however: you need to regression test the monthly automatic Cloud updates.

I hope this information has been helpful.  Keeping track of all of these support expiration dates can be a real pain sometimes!

Thursday, August 22, 2019

Action Plan for Early EPM 11.2 Adopters

Several customers and prospects have reached out asking about the process to upgrade to EPM 11.2, what it would cost, etc.  Until I see the Release Notes, Installation Guide, and am able to download the software, I can't provide a comprehensive answer.

So the purpose of this post is more about what to do in advance in order to prepare a Proof of Concept (POC) lab / sandbox.

At this time ("Safe Harbor"), Oracle has disclosed the software will be introduced for Windows Server, and UNIX will come later.  Oracle has also indicated Windows Server 2016 and SQL Server 2016 will be certified for EPM 11.2.  What is not clear is if higher versions of Microsoft will be certified.

Unless there are further delays ("Safe Harbor"), EPM 11.2 is now just 1-2 months away.  Oracle's Knowledge Base and blog indicates Sept 2019 is a possible release date, but a Q&A in an Oracle webinar earlier this week suggested Oct 2019 is now the target date.  As with every new on-premises EPM/Hyperion release, it is always a "wait and see" approach.

All of the above being said, here are some things we can do to prepare our POC labs / sandboxes in anticipation of the new release.

  1. Procure license keys for Microsoft Windows Server 2016, and your choice of either an Oracle database or Microsoft SQL Server 2016.  Time-limited trials are typically available if your POC lab will be used for throwaway testing & prototyping.
  2. Procure a few virtual machines.  I'd suggest starting with 3:   1 for the web tier, 1 for Essbase (if you use it, otherwise put HFM & FDMEE on server #2), and 1 for the relational database.  On server #1, where the web tier will run, ideally you want 1 virtual CPU core and 2-4 GB of RAM for each web service.  As we are talking about a POC lab / sandbox, we can skimp a little.  Future UAT and Production environments would need to be beefier.  The disk footprint is unknown at this time -- when in doubt, provision a standard C: drive for the operating system, and 150GB or more for the D: drive where EPM will reside.
  3. Install the operating system and database.
  4. Run Windows Update and apply the recent database patches / updates.
  5. Install your favorite 3rd party utilities on server #1 and #2.  I tend to use Notepad++ and 7-zip.  If the relational database is to be hosted on a UNIX variant, I additionally install PuTTY and FileZilla.  All of these are legally free (not shareware).
Now we wait.

Avoid creating schemas/databases until the software and installation guide are released.  I expect the schemas/databases needed will be the same as and prior, but it would be wiser to wait.

We don't yet know if DRM will require Microsoft IIS, ASP.Net, and/or .Net Framework.  I'd wait to install these until the installation guide is published.

Finally, make sure your company is current on paying the Oracle Support maintenance fee.  Upgrades are only available to companies who are current on maintenance.

A reminder this blog post relates to a Proof of Concept lab / sandbox, which would be used to validate that your applications can be successfully migrated from your old system into EPM 11.2.  Once you're ready to build out your "real" EPM 11.2 environments, the number of servers and their specifications may be much different.

What else would you do to prepare?  Leave a comment!

Downloadable white paper for this post is now available over at!