Wednesday, May 12, 2021

In-Place Upgrade to EPM 11.2.5.0

The comments section for my prior post about EPM 11.2.5.0 has really lit up with a common theme:

An in-place upgrade from either Hyperion / Oracle EPM 11.2.3.0 or 11.2.4.0 (the only certified paths to get to 11.2.5.0) fails if one applied the OPatch update necessary to subsequently apply the quarterly Oracle Critical Patch Update ("CPU") for Oracle Fusion Middleware - most notably WebLogic and OHS.

The commenter community seems to be in agreement that the best approaches are:
  • If Oracle Middleware, Opatch in particular, has yet to be patched, back it up!  If disk space is available, back up \Oracle\Middleware in its entirety before applying the quarterly Cracle Critical Patch Updates.
  • If the system is unpatched, it is apparently safe to perform the in-place upgrade to 11.2.5.0.
  • If the system was patched, it will be necessary to restore \Oracle\Middleware\Opatch and perhaps \Oracle\Middleware\wlserver and \Oracle\Middlware\oracle_common.  The jury is out on exactly where the bug resides with respect to patching.  All that is known for certain is Opatch is a primary culprit and the Opatch update cannot be rolled back without performing a filesystem restore for the Opatch folder structure.
Additionally, I experienced issues with missing jar files where ODI 12.2.1.4 and FDMEE 11.2.5.0 is concerned.  I have yet to determine if this is due to the issue mentioned above....  an EPM 11.2 customer-facing upgrade that just got handed over from me to the UAT team has eaten up all of my "free time".

I've installed a fresh VM and a fresh/unpatched EPM 11.2.4.0 and will perform the in-place upgrade to 11.2.5.0 to vet if ODI/FDMEE is truly broken or not in this release.  The EPM Configurator tool does not reveal the problem when FDMEE is broken, but there's a way I can see it on the back-end.

Finally, time permitting, I'll take my unpatched 11.2.4.0 Middleware backup, restore it to my botched/patched 11.2.4.0->11.2.5.0 in-place upgrade VM and see if I can put Humpty Dumpty back together again.

And here we thought RCU was difficult....

5 comments:

  1. Hey Dave -- did you happen to run into an issue running the UA for your FDMEE instance with the 11.2.5 upgrade? I'm upgrading an 11.2.3 system and the UA is whining about not being able to find the STB schema that I'm looking right at. I'm gonna poke at it with the RCU for a bit, but noticed that my UA is version 12.2.1.3 (despite the 11.2.5 update having been applied to this erstwhile-11.2.3 system).

    Thanks for all the great content! You and Jon Goodwin have been helping the rest of us poor infra slobs out for moons, and I appreciate ya. Cheers!

    ReplyDelete
    Replies
    1. Hi, I could not UA to work for FDMEE. The problem is, as you correctly stated, we don't use RCU to create the ODI content. I tried to fake the system by manually creating that little RCU schema table, but UA didn't like it.

      After spinning our wheels for 2+ weeks on an Oracle SR that wasn't going fast enough for our project timeline, we were forced to punt. We recreated the ODI objects by hand within ODI Studio. Not a pleasurable experience!

      Delete
  2. Has Oracle not even acknowledged the problem yet, Dave? Did they log a bug and are they attempting to replicate the suspected OPatch issue?

    ReplyDelete
    Replies
    1. Hi Larry. I've encountered this in one of my sandboxes, but fortunately have backed up the Middleware folder for customers on 11.2.4 who haven't patched yet. I won't have standing to open a customer-facing Oracle SR on this issue until I encounter a customer who needs help with this.

      At least one other commenter on this blog has hit this exact issue and I believe they have an SR open. Oracle acknowledged the issue, but I haven't heard news of a fix yet.

      Delete
  3. With all of the messes I've seen on the interwebs, and my own steaming pile of manure created by this over the top patch, I'm going to sit tight on patching up until the next release. I know, at that point, we'll have no choice since they're only supporting patching up from the last two prior releases. We can only hope that they fix this mess in time for the next release and, hopefully, give some sort of fix for this release. The beat goes on 🙂

    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!