Sunday, December 8, 2019

ODI Tables Missing in FDMEE Here's why!

So you did a fresh install of FDMEE, applied the latest patch, and then ran the config tool to "Create Database" and "Deploy To Application Server".  This is how I do it, as I hate repeating the same activity twice (before and after patching).

But lo' and behold, the ODI tables (SNP* etc) are missing within the FDMEE repository.  What's going on here?


On your FDMEE server, inspect this file.  If FDMEE is clustered across multiple servers, you need to do this on just one server only.  Let's assume your 1st FDMEE server is hosted on Windows and resides on the D drive:


Click the image if it doesn't render completely.  I'm an EPM Infrastructure guy and am thus graphically-challenged.  But the key nugget of information is this:  Do you see "" or ""?  Change that 3 to a 4!

The "FinancialDataQuality\odi\" folder doesn't exist in this patch, so your ODI Master and Work repository tables never get created!  The config wizard doesn't bark at you that you hit this problem.

Oh, there's one other thing.  In the later FDMEE patches, you get only one shot at creating the ODI tables within FDMEE.  Look within the same createODIRepos.bat file mentioned above. You'll see a line remarked out that was NOT remarked out in the unpatched version of the software.  Do you see it?  Post in the comments below and I'll give you a hint.  This remarked line is what makes the configurator wizard create the ODI Master and Work tables!

Fix the .bat file, re-run FDMEE's "Configure Database" task from the EPM Configurator on just one server.  No need to redeploy to WebLogic.  Restart FDMEE and you're good.

I can understand why Oracle decided to remark out that line; if you need to re-run "Configure Database" for FDMEE for any reason, maybe you don't want to lose your ODI customizations.  But what if the ODI tables never got created to start with?  Best to backup the original file, make your edits, run the configurator, and then when things are working OK you can restore your backup copy of the file to its original name.

Will this remain a bug in 11.2, or will it be fixed?  Time will tell!

Friday, December 6, 2019

Hot Off the Press: EPM 11.2 is Actually Coming in Dec 2019?

Oracle updated their EPM 11.2 Release Date blog post today, Dec 6, 2019, indicating Oracle is still projecting a release of EPM 11.2 sometime in December 2019 (*).  The precise day of the month isn't known yet.

(*) - Oracle Safe Harbor applies.  Date can be subject to change.

The blog post I've linked above contains a wealth of information, so I suggest you read it if you haven't checked it out lately.

Monday, November 25, 2019

Link to Nov 21 ODTUG Webinar recording

If you are a full ODTUG member, you may download a recording of last week's webinar I presented.

Here's the link: Support Expiration Dates


Date: 2019-11-22
Subtopic: EPM

Dave Shay, Datavail
Extended Support deadlines are drawing near for the technology undergirding on-premises Oracle EPM/Hyperion systems. Learn about vendor Extended Support deadlines for Java, Oracle JRockit, Microsoft Windows Server, Microsoft SQL Server, Linux, and Oracle EPM and prior, and learn how they will affect your EPM/Hyperion applications. While some of these dates are a few years away, others are not, which may surprise you.

Also, learn about implications of an upgrade vs. moving to the cloud if your system is subject to Sarbanes-Oxley or similar change audit controls. If your Oracle EPM system is subject to these controls, take note of ways to avoid being red-flagged in a future year’s SOX audit.

Monday, November 11, 2019

OCT2019CPU WebLogic "3L3H" Breaks Jython?

In a recent post, I listed the patches included in Oracle's October 2019 "Critical Patch Update".  Among them is a patch for Oracle WebLogic 10.3.6, which is part of the Oracle Middleware infrastructure that supports Hyperion

Customers who use Jython scripting within FDMEE may want to do extra regression testing before promoting this patch into Production.

A little background:

My team uses custom scripts to maintain 7 rolling days of Hyperion LCM backups.  One stumbling block with this is: when rolling off the 7th folder so it may be replaced, traditional MS-DOS "rmdir" doesn't work for certain subfolders in Windows Server 2012 R2 (usually Reporting Analysis Framework and Financial Close / ARM).  This is due to the famous "directory path too deep" error.

To work around this, we created a very simple Jython script.  Jython bypasses the Microsoft API, allowing us to delete folders containing paths which exceed the Microsoft limitation.

You do this:

SET CLASSPATH=%CLASSPATH%;%HYPDRIVE%\Oracle\Middleware\oracle_common\modules\oracle.jrf_11.1.1\jrf-wlstman.jar
%JAVA_HOME%\bin\java weblogic.WLST %SCRIPTDIR%/

And the Jython script looks like this:

# This Python/Jython script removes the oldest LCM backup folder.
# We use this technique to work around the Windows Server 2012
# limitation concerning directories containing pathnames exceeding
# 260 characters.
#  Written on 11/02/2016 by Dave Shay (Datavail)
# Modified on MM/DD/YYYY by Your Name - Briefly list changes

import shutil


I like simple solutions like this.  It uses technology that is already baked into the EPM infrastructure.  Now, a new challenger appears: WebLogic OCT2019CPU patch ID "3L3H".  This is what happens when trying to run our Jython script after applying the patch.

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Problem invoking WLST - Traceback (innermost last):
  File "D:\Scripts\", line 13, in ?
  File "D:\Oracle\Middleware\wlserver_10.3\common\wlst\modules\jython-modules.jar\Lib/shutil$py.class", line 117, in rmtree
  File "D:\Oracle\Middleware\wlserver_10.3\common\wlst\modules\jython-modules.jar\Lib/shutil$py.class", line 132, in _build_cmdtuple
  File "D:\Oracle\Middleware\wlserver_10.3\common\wlst\modules\jython-modules.jar\Lib/javaos$py.class", line 135, in listdir

The Rotation7 folder remains and now we essentially have 6 rolling days of backups instead of 7.

When I look at the "jython-modules.jar" file, I can see the timestamp changed to when it was patched.  It would appear Oracle accidentally broke something?

My team will open an SR with Oracle and try to get to the bottom of this.  In the meantime, I would tend to shy away from this specific patch.

Thursday, November 7, 2019

ODTUG Webinar Registration Link

Here's where to sign up for my upcoming ODTUG Webinar:

Registration Link

"Hyperion/EPM, Java, SQL Server…Upcoming Extended Support Deadlines and What They Mean for You
Dave Shay, Datavail"

This encapsulates information I've posted here across multiple threads, but I'll present it as a single discussion.

In the very least, some of you will finally get to hear my voice.  Please do not heckle... too much.  😆

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
(Available for and 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 only)

Hyperion Data Relationship Management, version
(This is a stale patch – the last DRM patch is from Feb 2019)
Hyperion Enterprise Performance Management Architect, version
(Extremely stale patch from 2015 - only applies to customers who integrate EPMA with DRM)

Hyperion Financial Reporting, version
(patch is 4 months old)

Hyperion Planning
(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  I don’t know if this has been fixed for .009.

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

EPM Workspace / RA Framework
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 with an system could corrupt Workspace and make it non-functional.

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

Friday, October 4, 2019

I might host a webinar soon?!?

Stay tuned.  Submitted application and we'll see if it is accepted.

But I can already hear it in my head:   "I award you no points."

the "I Award You No Points" guy