Sunday, June 13, 2021
Friday, June 4, 2021
I have much to say about the in-place upgrade to Hyperion / Oracle EPM 11.2.5. Anybody who knows me well... knows that I pretty much despise Hyperion in-place upgrades, and moving to 11.2.5 in-place is no exception. In fact, it may be one of the harder ones.
We've already talked on this blog previously about how applying the quarterly Oracle Critical Patch Update ("CPU") for Oracle Fusion Middleware - OPatch for Weblogic in particular - currently bricks your in-place upgrade from either 11.2.3 or 11.2.4 to 11.2.5.... unless you backed up your Middleware folder prior to patching it.
But this post is about other factors that'll make you want to tear your hair out.
Let's begin with OPMN.
Tuesday, May 18, 2021
"BeaService", how did I beat you?
If you have never heard about or read about NSSM before, READ ON!
When I record installation sessions for Hyperion / Oracle EPM, I tend to pause the recording when it is time to deploy NSSM to get Oracle WebLogic Admin Server setup as a Windows service.
Because NSSM is an acronym that is not entirely nice. I won't repeat it here. But you NEED this tool if you don't have it! Grab it here: NSSM download
NSSM lets you create a Windows service for any executable .bat or .exe. It does not work for OHS 12c and I have a separate post about that topic. But it works wonderfully for the Oracle WebLogic Admin Server ("WLS") in either 10.x or 12.x.
Simply download NSSM and unzip it in a directory of your choice. That directory should not be deleted later. I save my copy in D:\Scripts\NSSM on my primary EPM Foundation Server where the master version of WLS resides.
The beauty of this utility is:
- You can customize the name of the service, as in my first screenshot above.
- You can make it rotate the log files.
- You can force it to make the stdout and stderr logs reside in the same folder as your EPM service stdout/stderr logs!
I won't post the spoiler screenshots or else you won't hire me. 😈 But maybe I gave you a few helpful hints here?
Sunday, May 16, 2021
This ought to be a simpler post than what I usually write.
The topic of how to start Oracle HTTP Server ("OHS") 12c in Hyperion / Oracle EPM 11.2.x comes up frequently. I've previously posted about the little trick, buried within the EPM 11.2.x install/config guide, on how to save the WebLogic password for OHS so you aren't prompted every time you try to start up OHS.
"But hey! Dave, how do we start and stop OHS in a distributed MS Windows Server environment when OHS doesn't have its own Windows service anymore? The good old NSSM trick we use for WebLogic Admin Server doesn't work for OHS!"
An excellent question.
Login to each OHS host server in your distributed environment as your EPM network service account. Run the "storeuserconfig" trick to save epm_admin's password in your network service account's profile on the C drive. Search the install/config guide for the text "storeuserconfig" and it'll take you directly to the needed command syntax. Every member on your Hyperion support team who wants to start/stop services using their own distinct userID needs to perform this step. This is a one-time-only step until such time as your security team forces you to change the WebLogic epm_admin password.
Now on your OHS server(s) foreign to where you run your master start/stop scripts from (you are running custom start/stop scripts, yes?), create a simple little DOS batch script like this:
sc start "Oracle Weblogic ohs NodeManager (D_Oracle_Middleware_ohs_wlserver)"
start "StartOHS" /wait /i cmd /c %EPM_INSTANCE_HOME%\httpConfig\ohs\bin\startComponent.cmd ohs_component
Replace D_Oracle in that first command with the drive letter where you installed. e.g. E:_Oracle, F:_Oracle or whatever is appropriate. The drive letter is unfortunately embedded within the Oracle Node Manager 12c Windows service name.
Replace %EPM_INSTANCE_HOME% with the fully qualified path to your Oracle EPM Instance, which is DRIVE:\Oracle\Middleware\user_projects\epmsystem1 by default.
Note: the final line beginning with start "StartOHS" is all one line all the way through ohs_component. Blogger is linewrapping it in an undesirable way.
Save this script as DRIVE:\scripts\startohs.bat or whatever you want.
Replace startComponnent.cmd with stopComponent.cmd and now you have your stopohs.bat script as well!
Finally, use this to invoke it remotely from your master start/stop scripts:
wmic /node:%FDNHOST2% process call create "DRIVE:\Scripts\startohs.bat"
wmic is a built-in Windows command. Provided your userID is an administrator on the foreign server, you may use this syntax to invoke any batch file, command, or executable you wish.
Wednesday, May 12, 2021
- 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 220.127.116.11.
- 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.
Tuesday, April 27, 2021
We finally get Oracle Fusion Middleware (FMW) 18.104.22.168!
SQL Server 2017!
Essbase 21c certified!
The bad news:
If you're still using Essbase Studio, migrate away from it. Essbase Studio is slated to be retired in EPM 11.2.6 as per this Oracle Statement Of Direction: https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=81935405509356&id=2731169.1&_afrWindowMode=0&_adf.ctrl-state=rbcbyuw9y_4
Visual Basic scripts for FDMEE need to be migrated to Jython ASAP. VB scripting is expected to be decertified in EPM 11.2.7. We knew this some time ago, but now we now the release number where VB goes away for FDMEE.
Oracle's readme for 11.2.5 confirms what I've suspected. In 11.2.x we aren't getting Patch Set Updates (PSUs), but rather new "dot" releases. Here's a copy/paste directly from the 11.2.5 readme:
EPM System updates are released on a quarterly basis, generally in January,
April, July, and October.
You can directly apply an update from the previous two updates.
I won't paste the entire thing. When you download 11.2.5 from Oracle eDelivery, you get this folder:
EPM_11.2.5\EPM 22.214.171.124.000\EPM System Installation Documentation\EPM System Installation
Stop, open this folder. Open the readme before doing anything. Here's the Cliff Notes. You can apply 11.2.5 as an in-place upgrade on top of either 11.2.3 or 11.2.4. Do not attempt to apply it on top of 126.96.36.199 or any older release; you need to do a fresh install and LCM your apps from the older release. Only 188.8.131.52 is certified for this migration path.
If you were an early adopter like me, you need to jump to 11.2.2 before you can get to 11.2.3 or higher. You can apply 11.2.2 on top of either 11.2.0 or 11.2.1. You can't get to 11.2.3, .4 or .5 unless you're on at least .2. Job security!
Migration Path documentation: 184.108.40.206.x to 11.2.x
If you're on Financial Close Management 220.127.116.11 or older, prepare for pain. I've done it and it is not fun. :(
It is now time to back up my sandbox and attempt the upgrade. Wish me luck!