As mentioned in my previous post, I was able to spend this weekend doing some R&D in Hyperion / Oracle EPM 220.127.116.11 in Linux instead of doing heads-down customer-related work.
One of the items re-visited were the numerous bugs encountered with FDM Enterprise Edition (FDMEE). These bugs are specific to the Linux edition of EPM 18.104.22.168; the Windows edition of the same release works just fine. To see all of the gory details, expand August 2020 on the right-hand side of this page to see my 3-part series about the FDMEE 22.214.171.124 bugs in Linux. Part 1 of the 3-part series starts here.
If you're impatient and wish to avoid going through all of the error evidence, I can summarize FDMEE's problems in 2 major categories:
- When running "Configure Database" for FDMEE, many dozens of ODI tables are missing. The ODI Agent is thus unusable when FDMEE attempts to invoke it.
- When running "Deploy to Application Server" for FDMEE, WebLogic's configuration is incomplete. The FDMEE process starts and WebLogic says it enters RUNNING mode, but is essentially useless.
Again, for the sake of clarification, the above 2 problems are specific to FDMEE 126.96.36.199 hosted in Linux.
Here is the quick & dirty solution I tested this weekend, and it worked perfectly for me. I hope this helps you, too!
Create a throwaway virtual machine running Microsoft Windows Server 2016 or 2019. Download HFM Plus 188.8.131.52 and install it. You do not need to create a database or run configtool; completing the install for FDMEE is enough.
On your Linux FDMEE server(s), stop FDMEE and rename these 2 things:
- aif.ear within the Middleware/EPMSystem11R1/products/FinancialDataQuality directory structure. It is easy to find if you're not familiar with the back-end filesystem. Just cd to the folder I just mentioned and type: find . -type f -name aif.ear
Point of clarification: I can't say for sure that aif.ear is contributing to the problem. I can say with high confidence that Middleware/odi has problems in EPM 184.108.40.206's Linux edition!
Now grab the same 2 things from your Windows filesystem. In the case of Middleware\odi, you'll want to zip it up in Windows and unzip it in Linux. If FDMEE is clustered across multiple servers, do this on each.
Once the above is done, launch configtool.sh in Linux and re-run both Configure Database and Deploy to Application Server for just FDMEE. Pick all options again even though they have the green checkmark. When Configure Database asks if you want to Drop & Create or Re-Use, pick the Drop & Recreate option. If you have FDMEE clustered across multiple servers, do Configure Database on just one of them, and Deploy to Application Server on all FDMEE servers.
Once configtool is complete, check your FDMEE database/schema. All of the SNP* tables that were missing before ought to be present now.
rm -rf ErpIntegrator*/tmp and ErpIntegrator*/cache
Restart FDMEE and regression test. Middleware/user_projects/yourinstance/bin/validate.sh ought to come back green now where FDMEE is concerned.
If this blog entry does not help, I implore you to open a Service Request with Oracle. As of this writing, there are still no patches out there for either Hyperion Infrastructure (installtool+configtool) or FDM Enterprise Edition for 11.2.x. With 220.127.116.11 for Linux being so new, and many companies not having an EPM upgrade budget approved for Fiscal 2020, Oracle may be unaware of this issue. There will likely be a deluge of bug reports once Fiscal 2021 rolls around!
The 11.2.x upgrades my team & I performed thus far either haven't included FDMEE, or had FDMEE exclusively on MS Windows. So I could open an SR now about the issue, but the SR wouldn't have the same standing as if the problem were holding up a customer's upgrade project.