My loyal readers just KNEW this blog post was coming. 😁
Hyperion / Oracle EPM 184.108.40.206 was released on Friday, February 11, 2022. I have it online now and here are initial observations.
(Disclaimer: the above screenshot is from the sample "Vision" application & associated financial data that ships with Hyperion Planning.)
Get Ready To Patch!
<Feb 12, 2022 4:52:31 PM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 220.127.116.11.0 Thu Sep 12 04:04:29 GMT 2019 1974621>
java version "1.8.0_301"
Java(TM) SE Runtime Environment (build 1.8.0_301-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.301-b09, mixed mode)
Tip: If you want to use the old "FRConfig" utility to configure the default POV prompt on/off setting or HFR batch bursting external folders, you will want to back up the pre-delivered \Oracle\Middleware\jdk\ folder structure before applying the latest Quarterly Critical Patch Update ("CPU") for Java.
Depending upon the method you use to patch/replace JDK 8, FRconfig won't launch and you won't see an error message explaining why. The root cause is the Java quarterly CPU may be missing hundreds of files. This issue may have started with the October 2021 CPU. I noticed it also applies in the January 2022 CPU. Oracle has a Knowledge Base article about this problem, but you have to dig a little bit to find it. I'll probably need to write a separate blog on this specific topic alone.
Essbase 64-bit - Release 11.1.2 (ESB18.104.22.168.045B020)
OPatch Version: 22.214.171.124.7
f:\oracle\middleware\jdk\bin\java -jar f:\oracle\middleware\coherence\lib\coherence.jar
Oracle Coherence Version 126.96.36.199.0 Build 74888
(File is dated Sept 12, 2019)
Planning "Vision" Sample Application is Still Old
Vision still has a start year of FY09. The good news is it extends out to FY27, so you have 5 more years to play with before you need to add more.
Essbase Stills Logs in TRACE Mode
Edit your $ARBORPATH\bin\logging.xml to fix this. While you're at it, edit your $EPM_ORACLE_INSTANCE\config\OPMN\opmn\opmn.xml if you, like me, tire of seeing the opmn ping messages in Essbase.log every 20 seconds... 24x7.
You have to insert the line highlighted in yellow exactly where shown. OPMN can be picky about the order of statements in opmn.xml apparently:
<restart retry="2" timeout="600"/>
<ping timeout="20" interval="0"/>
<port id="essbase-port-range" range="32768-33768"/>
<process-set id="AGENT" numprocs="1" restart-on-death="false">
Those of you who've worked with me in the past know I prefer restart-on-death="false" rather than the default "true" setting. This permits a graceful shutdown of Essbase via MaxL, with error notification (if your shutdown script is clever) if an application is loading data, calculating, or restructuring.
Premier Support Extended
The 11.2.8 README says EPM 11.2 Premier Support now runs through "at least 2032". So we have an additional 2 years than we originally expected when 11.2.0 came out. Oracle Safe Harbor applies here of course.
Log4J is now version 2.17.1. Consult your IT Security folks to verify this satisfies their vulnerability concerns.
MSAD 2019 Certified
EPM 11.2.8 now speaks with MSAD 2019. This should make IT a bit happier.
Upgrade Leapfrog - GONE!!!!
Quite simply: this one is huge. Prior to 188.8.131.52, we could only upgrade in-place from an older 11.2.x release if we were, at most, 1-2 dot releases behind. Now we may jump directly to 11.2.8 from any 11.2.x release, provided we are coming from at least 11.2.2. If you're still on 184.108.40.206, you will be standing up new server infrastructure and you'll jump directly to 11.2.8 and do a bunch of LCM, HFMCopyApplication, and EAS Console migrations.
This screenshot from the 11.2.8 README says it clearly:
Essbase 21c Now Certified for Planning & Profitability
This is another big one.
Many of my customers have been holding back on kicking the Essbase 21c tires because they use Hyperion Planning. Now is the time to take a serious look at Essbase 21c. The last I looked, Essbase 220.127.116.11 (which is the default Essbase version in EPM 11.2.x) support runs through the end of 2022.
My knowledge on this Essbase 18.104.22.168 support expiration topic may be a bit out of date, so I'll need to prowl around on Oracle's website to see if they're changed their position on this specific point or not.
2021 was very busy for me doing non-stop upgrades to 11.2.x for many customers. 2022 is shaping up to be the same situation, with my first 11.2.7 going live in Production one week from now.
If you've never touched EPM 11.2.x before, be sure to get some professional consulting help from someone who has successfully done it and gone live in Production. There are important differences between standing up EPM 11.2.x versus EPM 11.1.2.x.
First patch is here too:ReplyDelete
33809263 11.2.8 RUE TO PATCH LOG4J 2.17.1 FOR EPM 11.2.8 RELEASE
Actually I upgraded 2 environments from 11.2.4 to 11.2.8. Config tool is requesting to perform the "Deploy to Application Server". Doing so and finishing the update Essbase won't start anymore showing an ESSBASE.SEC file corruption error message. To solve the issue we had to run through the Essbase Server configuration step and re-assign Essbase server the existing Essbase Cluster using the "Assign to existing cluster" button. In our environments the Essbase Cluster name is not the default EssbaseCluster-1 but a different specific name EssbaseQS, EssbaseProd etc.ReplyDelete
A suggestion for you: If your Essbase cluster names are environment-specific (such as including DEV, QA, PROD, etc in the cluster name), it could make LCM migrations a bit more complicated than they ought to be. This is just my opinion so feel free to disagree with me. :)Delete
I see you have coherence unpatched version as well.
In the 11.2.8 readme certain patchversions described, but except for opatch nothing gets patched during maintenance upgrade. (=bug)
got confirmed from support you can run postInstallPatch.bat and pass MIDDLEWARE_HOME as an argument like:
Yes, my 11.2.8 sandbox is unpatched. It is sitting behind a private network so I'm not yet concerned. I've been heads-down getting a customer's 11.2.7 to go live. Now that is behind me, I'll return my attention to 11.2.8 and continue working through the integration with Essbase 12.3.Delete
Appreciate the knowledge share! I think I'll try it out tomorrow evening. :)
More info about this issue on My Oracle Suport: EPM 11.2.8 not Applying Fusion Middleware Patches Listed in Readme (Doc ID 2853654.1)Delete