Saturday, August 8, 2020

FDMEE Multiple Problems - Buggy Release - Part 1

I did a near-full stack implementation in a sandbox for Oracle EPM / Hyperion in Red Hat Enterprise Linux ("RHEL") 7.  Essbase, Planning, CalcMgr, Foundation, and EAS all seem to be working fine.  HFM of course is not available for Linux at this time.

FDMEE, however, has multiple issues and does not work.  In short, Oracle needs to issue a patch.  Clarification: this post is about the Linux edition only.  The Windows edition does not have these issues.

A patch also needs to be issued for Analytic Provider Services ("APS").  I managed to get it to work by copying over aps.ear from my sandbox.  Unfortunately, this solution won't help you if you didn't grab from Oracle eDelivery before it was removed.  So Oracle will need to issue a patch for APS as well.

I've downloaded for Windows and will check if that version also has the same issues.

Here's the initial symptom with respect to FDMEE:

I had deployed it to WebLogic and started it.  It binds to port 6550 as it should:

Digging digger, I found multiple problems behind the scenes.  The problems are in two major areas:

  1. The FDMEE database schema is incomplete; All of the SNP_* tables are missing.
  2. The WebLogic configuration is completely messed up where FDMEE ("ErpIntegrator" as WebLogic calls it) is concerned.

I had to do quite a bit of "surgery".  At this point, 2 of 3 problems as previously reported by the utility are now fixed.

So how did I manage to get to this point?  Hours of troubleshooting and experimentation.

Let's first address fixing the lack of SNP_* tables in the FDMEE database schema.  When we run the "Configure Database" task for FDMEE, here's what happens behind the scenes.  We can reproduce the issue at will by running the back-end utility manually.

Side note: I edited the utility to add echo statements for "Finished XYZ" so I could see which step was throwing the Java stack trace error.

The assertion that the supervisor password is blank is not true.  The script follows the same format used in, whereby Supervisor's userid and password are encrypted and hard-coded within the script.

This is not an issue in, and  While and are no longer available for download from Oracle eDelivery, I downloaded both releases when they were available, and I have an sandbox online for reference purposes.

In crawling through the various jar files in, I found the offending class oracle.odi.setup.suppoort.MasterRepositorySetupImpl is located within Middleware/odi/sdk/lib/odi-core.jar.

When comparing Linux vs. Windows, I found size and timestamp mis-matches between the two systems. Windows: 29,222,611 bytes dated Feb 1, 2020 Linux:      29,032,586 bytes dated Aug 22, 2017

Rut roh!

So I backed up Middleware/odi/sdk in and then copied over the whole directory structure from  Re-ran the utility in my screenshot above, and now all of the SNP_* tables are present.

So in the EPM Linux installer, the subdirectory "odi" is apparently packaged incorrectly and we need a patch for that.

My follow-up post concerns a myriad of problems within WebLogic.

No comments:

Post a Comment