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 126.96.36.199, 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 188.8.131.52 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 184.108.40.206).
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 220.127.116.11 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!
The majority of on-premises EPM systems run on Microsoft platforms. EPM versions 18.104.22.168 and older run on MS Windows Server 2008 R2, and EPM 22.214.171.124 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 are many “flavors” of UNIX. The most popular one where EPM is concerned is Red Hat Enterprise Linux (RHEL). Both EPM 126.96.36.199 and 188.8.131.52 are certified to run on RHEL 6. Where RHEL 6 is concerned, we refer to the chart below.
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 184.108.40.206 I’ve seen “out in the wild” are MS SQL Server 2012 R2 and Oracle Enterprise Database 12.x. EPM 220.127.116.11 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 a chart.
Both from an operating System and a Database perspective, Finance will be pressured by IT to upgrade, due to operating system support. IT highly frowns upon 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).
If you are running 18.104.22.168 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 22.214.171.124, 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.”
This means that 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 126.96.36.199 through 188.8.131.52 ship with Java SE 6 and JRockit 6. Only EPM 184.108.40.206 is certified to replace Java 6 and JRockit 6 with Java SE 7.
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 220.127.116.11.
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!
Subscribe to Our Blog
Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.
EPM applications help measure the business performance. This post will help you choose the best EPM solutions for your organization’s needs and objectives.
Curious about Oracle’s new Enterprise Data Management Cloud Service? Get the full scoop in Datavail’s latest blog post.