Thursday, October 17, 2019

October 2019 Quarterly Critical Patch Updates announced for Hyperion

Hi EPM/Hyperion on-premises Infrastructure friends,

The following information is what I was able to dig up concerning OCT2019CPU, published just a few days ago.

Here are the specific patch ID #s which apply to Hyperion.

Oracle WebLogic Server, versions 10.3.6.0.0
30109677: WLS PATCH SET UPDATE 10.3.6.0.191015
(Available for 11.1.2.3 and 11.1.2.4 only)
November 11 update: Please consult WebLogic Breaks Jython? before promoting this patch to Production.

Oracle Java SE, version 7
30384776: Oracle JDK 7 Update 241 b31
Requires our upgrade procedure from Java 6 & JRockit 6 to Java 7 is performed first:
(Available for 11.1.2.4 only)

Hyperion Data Relationship Management, version 11.1.2.4
28818149: ORACLE DATA RELATIONSHIP MANAGEMENT - 11.1.2.4.347 PSU
(This is a stale patch – the last DRM patch is from Feb 2019)
               
Hyperion Enterprise Performance Management Architect, version 11.1.2.4
22078964: PSE REQUEST FOR 22074034-DRM INTEG: REBUILD OF WS CLIENT PROXY FOR DRM API WS
(Extremely stale patch from 2015 - only applies to customers who integrate EPMA with DRM)

Hyperion Financial Reporting, version 11.1.2.4.7xx
29712951: RA 11.1.2.4.711 PATCH SET UPDATE FOR FINANCIAL REPORTING
(patch is 4 months old)

Hyperion Planning 11.1.2.4
29889455: HYPERION PLANNING - PATCH SET UPDATE 11.1.2.4.009
(patch is 3 months old)
Check the patch readme and Oracle forum for Essbase certification issues.  Prior Essbase patches were de-certified by Oracle for Planning 11.1.2.4.006.  I don’t know if this has been fixed for .009.

Hyperion Shared Services 11.1.2.4
28314691: Patch Set Update: HSS 11.1.2.4.008
(patch is 1 year old. Depends upon prior PSEs being applied first and in a specific order.  Consult the readme)

EPM Workspace / RA Framework 11.1.2.4
29115044: TRACKING BUG FOR R&A PSU 11.1.2.4.009
Extreme care must be taken when downloading Workspace / RA Framework patches!
We must look for this text within the patch readme:








Unless things have changed, co-mingling RA Framework / Workspace 11.1.2.4.9xx with an 11.1.2.4.000/700 system could corrupt Workspace and make it non-functional.

Source of the above patch info from support.oracle.com:
“Critical Patch Update (CPU) Program Oct 2019 Patch Availability Document (PAD) (Doc ID 2568292.1)”

7 comments:

  1. OK fact-checkers! Tell me if I got anything wrong, and I'll update the post. :)

    ReplyDelete
  2. thank you for the post, this is very useful!

    ReplyDelete
  3. your warning about RA patch related to EPM 11.1.2.4.900 is also true for Shared Services patchs that are only valid for 11.1.2.4.000 and not 11.1.2.4.900 right ?

    ReplyDelete
  4. Hi Jul, yes if the patch is for anything designated as EPM 11.1.2.4.9xx, I would advise you to inspect the patch readme very carefully.

    ReplyDelete
  5. Just FYI I wouldn't recommend the Weblogic patch. I kept getting this error until I removed it.

    <User defined listener com.hyperion.lcm.web.common.LCMContextListener failed: java.lang.NullPointerException.
    java.lang.NullPointerException
    at com.hyperion.lcm.common.LCMLogger.isLoggable(LCMLogger.java:1128)
    at com.hyperion.lcm.common.LCMLogger.log(LCMLogger.java:1172)
    at com.hyperion.lcm.common.resource.ResourcesCache.cacheProductResourcesOnStartUp(ResourcesCache.java:139)
    at com.hyperion.lcm.web.common.LCMContextListener.contextInitialized(LCMContextListener.java:38)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    Truncated. see log file for complete stacktrace

    ReplyDelete
    Replies
    1. Appreciate the info, Charles. My team has seen mixed results with the WebLogic patch. I will kick the tires in my test lab later this afternoon. I've been in fire-fighting mode lately and haven't had much time for R&D. :(

      Delete
    2. I was finally able to get around to applying this WebLogic patch in one of my test labs. While LCM is working, the patch broke one of our Jython scripts. The patch updated a jar file that Jython uses. I'm going to instruct my team to wait to apply this patch for now.

      Delete