The following information is what I was able to dig up concerning OCT2019CPU, published just a few days ago.
“Critical Patch Update (CPU) Program Oct 2019 Patch Availability Document (PAD) (Doc ID 2568292.1)”
Dedicated to Oracle EPM (Hyperion) on-premises infrastructure topics, such as upgrading, patching and troubleshooting.
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!
OK fact-checkers! Tell me if I got anything wrong, and I'll update the post. :)ReplyDelete
thank you for the post, this is very useful!ReplyDelete
your warning about RA patch related to EPM 22.214.171.124.900 is also true for Shared Services patchs that are only valid for 126.96.36.199.000 and not 188.8.131.52.900 right ?ReplyDelete
Hi Jul, yes if the patch is for anything designated as EPM 184.108.40.206.9xx, I would advise you to inspect the patch readme very carefully.ReplyDelete
Just FYI I wouldn't recommend the Weblogic patch. I kept getting this error until I removed it.ReplyDelete
<User defined listener com.hyperion.lcm.web.common.LCMContextListener failed: java.lang.NullPointerException.
Truncated. see log file for complete stacktrace
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
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
having issues with weblogic patchesReplyDelete
Status: 404 - Not Found
We just tried recently after upgrading from 220.127.116.11 to 18.104.22.168.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.ReplyDelete
Below are the errors/log:
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
Hi, when you did your upgrade from 22.214.171.124 to 126.96.36.199, 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 188.8.131.52 on top of 184.108.40.206) frequently encounters various corruption-related problems.Delete
Regardless of how you got to 220.127.116.11, installTool puts some WebLogic and ADF/JDeveloper patches out there automatically. Once you get on 18.104.22.168, 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 22.214.171.124.900, or did you open Oracle SR to get the 126.96.36.199.0 media? If you are unsure, launch installTool again and look at the title bar.... if it says 188.8.131.52.900, you could be hosed. We cannot jump from any prior release directly to 184.108.40.206.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.
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 220.127.116.11.x only), and I have an article here on this blog as well.
Thanks for your quick reply Dave..ReplyDelete
We are at version 18.104.22.168.207. EPM Installer shows 22.214.171.124
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?
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?)
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 ?
Had to apply Patch 18561746 - for shared services to come back up.ReplyDelete
Applied all the three patches in all the servers of the environment( except the DB Server)