Enterprise Performance Management(EPM): EPM Registry Is Not Getting Updated After The Re-deploy And Re-configuration Of EPM 184.108.40.206.0
(Doc ID 2145923.1)
Last updated on DECEMBER 20, 2020
Applies to:Hyperion Essbase - Version 220.127.116.11.000 and later
Information in this document applies to any platform.
EPM Registry is not getting updated after the re-deploy and re-configuration of EPM 18.104.22.168.0
The Environment was having FQDN (Full Qualified Domain Name) issues after the installation and configuration of the EPM 22.214.171.124.0 as a fresh install (Foundation server and Essbase Server environment). Before the server name was the FQDN but due to DNS issues in the network (not resolving the DNS name), changed the DNS name and got the new name to point to the server IP address. Once having the new FQDN, redeployed and reconfigured the application dropping the database and creating the new one and able to login to workspace and Essbase server via EAS console.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document