As mentioned in my previous post about EPM 18.104.22.168, I decided to attempt an in-place upgrade from Hyperion / Oracle EPM 22.214.171.124 to 126.96.36.199.
Before I launch into this discussion, I want to be very up-front: I do not like EPM in-place upgrades. They are fraught with risk as you never know what issues you'll encounter. Once you encounter them, you have to work non-stop to fix them because the system you've attempted to upgrade is now non-functional.
This spells disaster for a Production system where the customer only provides a weekend to get it all done; everything must be online by 7AM Monday morning.
So why did I even bother???
Let's look at the recent Oracle EPM 11.2.x release history:
- EPM 188.8.131.52 released December 2019
- EPM 184.108.40.206 released April 2020; Chrome and Edge fully certified, IE11 de-certified
- EPM 220.127.116.11 released June 2020 and includes Linux
- EPM 18.104.22.168 released sometime between September 15 - early October 2020
Now lets examine the list of patches for EPM 11.2.x:
Oracle is patching Essbase 22.214.171.124, and I'd have to check but I believe patches for DRM 11.2 are also on a separate track. The rest of the EPM suite, however, only has bugfixes as provided in EPM Releases 126.96.36.199 through 188.8.131.52 as listed above.
The question lingers in my mind: will we see PSEs or PSUs start to trickle out for the non-Essbase components, or will we continue to see new "dot" releases every 3 months or so?
Doubting the former, I considered the latter.
If Oracle were to continue this trend of issuing dot releases instead of PSEs/PSUs, then us remaining on-premises Infrastructure people ought to get comfortable with performing in-place upgrades within the EPM 11.2.x.x releases. Thus, my adventure began.
The above out of the way, here's my observations after performing the in-place upgrade and troubleshooting it. In no particular order:
- The documentation is absolutely correct that we need to edit \Oracle\Middleware\EPMSystem11R1\products\Essbase\eas\console\bin\admincon.bat and change the reference of Java from Java 6 to Java 8. Java 6 has been out of Extended Support for some time.
- Essbase Sample Applications not visible after installing them via installtool. In 184.108.40.206, I didn't install the sample applications. In 220.127.116.11 I wanted to test them. Installtool said the install was a success. After digging around, I found them in \Oracle\Middleware\EPMSystem11R1\products\Essbase\EssbaseServer\app
- This was NOT my ARBORPATH
- I checked epmsys_registry and \Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin\setEssbaseEnv.bat -- both of them had the ARBORPATH I wanted
- I'm not sure if this is the correct method, but I edited \Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin\server.properties and followed the comments within it. I added an entry for ARBORPATH, bounced Essbase, and then I could migrate or create apps and they appeared where I wanted.
- installtool re-applies Middleware and Essbase patches every time it runs. This behavior is not new and dates back to at least 18.104.22.168. I don't recall if 22.214.171.124 and prior did this. When you see installtool "stuck" at 97-98%, that's what it is doing. The lesson here is don't start applying Essbase patches or the quarterly critical Oracle Middleware patches until you're satisfied you're completely done using installtool.
- Analytic Provider Services does not work. This behavior started in 126.96.36.199 and continues through 188.8.131.52.
- The error message in the WebLogic log is "weblogic.application.ModuleException: java.lang.RuntimeException: Failed to deploy/initialize the application as given archive is missing required standard webservice deployment decriptor." ("descriptor" typo is Oracle's, not mine).
- The fix is to patch the Essbase Suite up to a higher patch level, such as 184.108.40.206.040 or .041 as of this writing. Consult the APS patch README to see which other patches correlate to the Analytic Provider Services patch you want to apply.
- Oracle database clients, WebLogic Server, and OHS would not upgrade and installtool shows errors during the upgrade process. Don't worry about this as you don't need to upgrade them. 220.127.116.11 through 18.104.22.168 use the same versions of this software. Just ignore and move on!
- On a positive note, the Google Chrome "white screen" rendering bug in LCM has been fixed in 22.214.171.124!
- Consolidation Administration->Settings->System still has the same defaults as 126.96.36.199.
- MinDataCacheSizeInMB: 2.25GB -- This is likely too high for sandboxes and DEV environments. It might be OK for UAT and PROD. You decide! Tuning is an art, not science.
- SessionManagerTimeoutInMS 1,200,000 (20 minutes) -- Many HFM admins asked me to triple it. This affects EPM Workspace AND SmartView.
- Another positive note. Oracle has done a great job cleaning up the many references within scripts to Java 6 that I mentioned in my more than a cupful of Java post. EAS Console thick client launcher and MetadataMerge.bat are the last remaining offenders now.
- I completely understand why EAS Console is still referring to Java 6. EAS Console is 188.8.131.52 software at this time, so it needs to work in an 184.108.40.206 system that uses Java 6.
- Another positive note. My Windows Registry fix for the Planning RMI issue was preserved. Bookmark the post I linked if you need to use the classic Planning command-line utilities, as they need RMI running properly.
That's about it! (But isn't that enough?)