Check Report Not Working With HFM Cluster and Sticky Server Enabled
Last updated on NOVEMBER 03, 2017
Applies to:Hyperion Financial Data Quality Management, Enterprise Edition - Version 18.104.22.168.000 and later
Information in this document applies to any platform.
When customer is in a clustered HFM Environment the Check Report is showing incorrect data.
What is happening is that FDMEE Connects to one server in the cluster to load the data. It then connects to another server in the cluster for the check report. However, the HFM servers do not synchronize fast enough for the check report to show correct data.
According to HFM team the sticky server logic works only if a user has a open session on a node then subsequent request will go to that node. In FDMEE the session is closed after every action load, consolidate, check. The way the current code structure requires major changes to keep the session open.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms