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:
http://www.epmonprem.pro/2018/07/upgrading-to-java-7-for-epm-11124-it.html
https://www.datavail.com/blog/upgrading-to-java-7-for-epm-11-1-2-4-it-doesnt-need-to-be-difficult/
(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)”
Posted by at

13 comments:

  1. Dave ShayOctober 17, 2019 at 10:43 PM

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

    ReplyDelete
  2. julOctober 18, 2019 at 12:50 AM

    thank you for the post, this is very useful!

    ReplyDelete
  3. julOctober 18, 2019 at 12:53 AM

    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. Dave ShayOctober 18, 2019 at 9:43 AM

    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. CharlesOctober 30, 2019 at 7:51 PM

    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. Dave ShayNovember 6, 2019 at 12:10 PM

      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. Dave ShayNovember 11, 2019 at 4:33 PM

      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
  6. SavvanaJuly 18, 2020 at 11:41 AM

    having issues with weblogic patches

    ReplyDelete
  7. SavvanaJuly 18, 2020 at 11:42 AM

    Error:
    --------------
    hfmxxxx.com:19000/interop/conf/audit/auditReleaseConfig.xml
    Status: 404 - Not Found
    =====================

    ReplyDelete
  8. SavvanaJuly 18, 2020 at 11:43 AM

    We just tried recently after upgrading from 11.1.2.3 to 11.1.2.4.207, weblogic got patched, Oracle suggested to do a jdbc patch as well. But after restarting the services - Shared serivices did not open in Workspace - all other applications are opening fine.

    Below are the errors/log:

    Error:
    --------------
    hfmxxxx.com:19000/interop/conf/audit/auditReleaseConfig.xml
    Status: 404 - Not Found
    =====================

    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address
    ==============

    We removed the weblogic patch and it is working fine now.

    I have some questions:
    Do we need to install or replace the jar files ( JDBC updates)
    and then install the weblogic patch?

    It went well in the 2.3 environment withouot the JDBC patches

    Eagerly waiting for a reply

    We are with SQL 2012 database

    ReplyDelete
    Replies
    1. Dave ShayJuly 18, 2020 at 1:05 PM

      Hi, when you did your upgrade from 11.1.2.3 to 11.1.2.4, was it an in-place upgrade or a fresh install? I'm a huge proponent of the latter approach: I've done these upgrades both ways, and the in-place approach (where you are installing 11.1.2.4 on top of 11.1.2.3) frequently encounters various corruption-related problems.

      Regardless of how you got to 11.1.2.4, installTool puts some WebLogic and ADF/JDeveloper patches out there automatically. Once you get on 11.1.2.4, you can use the bsu (Bea Smart Update) utility to roll off your current WebLogic patch, and then jump to the latest patch - again by using bsu. I never manipulate the WebLogic folder by hand; I always use the Oracle-provided tools.

      One last point of order: did you do a fresh download from eDelivery to get 11.1.2.4.900, or did you open Oracle SR to get the 11.1.2.4.0 media? If you are unsure, launch installTool again and look at the title bar.... if it says 11.1.2.4.900, you could be hosed. We cannot jump from any prior release directly to 11.1.2.4.900, as (unless Oracle changed things after .900 came out), there's no supported migration path to that release this could be why you're getting that 404 error when you try to login to Workspace.

      Good luck.

      ps: We did not manually manipulate any JDBC jars. Prior to patching up WebLogic, we applied the procedure to swap out Java 6 with Java 7. I believe one of the WebLogic 10.3.6 patches from last year states Java 7 is needed. Oracle's Knowledge Base has an article on how to get to Java 7 (EPM 11.1.2.4.x only), and I have an article here on this blog as well.

      Delete
  9. SavvanaJuly 19, 2020 at 11:47 AM

    Thanks for your quick reply Dave..

    We are at version 11.1.2.4.207. EPM Installer shows 11.1.2.4
    We have SQL Database

    Applied the Weblogic patch - 30857748 using Smart Update utility and it went well, but we had that shared services error

    I did not swap the jars ( JDBC patch 27541896 refer Oracle Note 1970437.1) before applying the above weblogic patch

    May be I need to replace the .jars first and then apply the weblogic patch?

    Also the KD doc from ORacle is little confusing regarding the jars swapping.

    Are there any other locations other than the two folders ( ext, lib folder ) mentioned below where we need to swap the .jar's?

    1) D:\Oracle\Middleware\wlserver_10.3\server\ext\jdbc\oracle\11g\
    2) D:\Oracle\Middleware\wlserver_10.3\server\lib (one jar file in this folder)

    I see someother folders with .jars ( do we need to replace/swap the jars here to?)

    D:\Oracle\Middleware\wlserver_10.3\server\adr
    D:\Oracle\Middleware\oracle_common\modules\oracle.jdbc_11.1.1\
    D:\Oracle\Middleware\ohs\jdbc\lib

    Is it a good option to try replacing the jars and then install weblogic?

    Also, We have distributed environment with 4 servers and I see weblogic in all of them ( eventhough the Weblogic service is running on one server) - do we need to install the weblogic patch on all the servers where I see the weblogic ?

    Thanks again..

    ReplyDelete
  10. SavvanaJuly 22, 2020 at 3:24 PM

    Had to apply Patch 18561746 - for shared services to come back up.
    Applied all the three patches in all the servers of the environment( except the DB Server)

    ReplyDelete

Thank you very much for your interest in this blog! I hope you're finding it helpful.

Please keep comments relevant to the topic in the post, as this blog is not a free-for-all substitute for Oracle Support or traditional consulting. If you have many questions unrelated to the specific topic at hand, consider contacting me on LinkedIn (https://www.linkedin.com/in/daveshay) so we may discuss the possibility of consulting.

Commenting on posts older than 90 days unfortunately goes into moderation, thanks to spammers who've been hitting this blog. Please have patience, and thanks for your understanding!

Comments including URLs linking back to gambling or other things unrelated to Oracle EPM will be deleted on sight. If you're an EPM consultant and are offering me constructive criticism or a tip, go ahead and DO link back to your blog or firm's website if you so desire.

Thanks again for reading!

Subscribe to: Post Comments (Atom)