As I previously posted (http://wp.me/p2jaSq-2k), the Essbase 184.108.40.206.500 patches include many new features, but that was not all. Oracle had another patch hit just a couple of days later as John Goodwin reported (http://john-goodwin.blogspot.com/2014/03/epm-patch-11123500-has-landed.html).
So, I had a new install at a client and wanted to see how all of this actually works. I installed EPM 220.127.116.11 as normal. At this client, that included Essbase, EAS, APS, FR, and OBIEE. I started by applying the new Hyperion HUB patch 17529887.
The “superpatch” as Goodwin called it did appear to patch many products. My Foundation Services, Provider Services, Financial Reporting, and Reporting and Analysis Framework all seemed to have been patched. That’s fantastic; however, APS was not patched to 18.104.22.168.500 as expected, it was a lower version, 22.214.171.124.000.4380. EAS and Essbase were not touched by the superpatch.
Therefore, the reason behind my post today is to inform the public that in order to patch the entire system, you will need the superpatch as well as the other patches that I previously mentioned. The whole stack, as far as I am aware, requires the following patches:
- Hyperion HUB (17529887)
- Hyperion Client Patches (18383790)
- Crystal Ball
- EPMA clients
- HSF Client (32 & 64-bit)
- Planning Smart View Extension
- Predictive Planning (32 & 64-bit)
- Essbase Client (17767307)
- Essbase Runtime Client (17767299)
- EAS (17767309)
- EAS Console (17767316)
- APS (17767293)
- Essbase Studio (17767295)
- Essbase Studio Console (17767296)
- Essbase Server (17767302)