My Oracle Support Banner

EPM Registry Is Not Getting Updated After The Re-deploy And Re-configuration Of EPM (Doc ID 2145923.1)

Last updated on MARCH 21, 2018

Applies to:

Hyperion Essbase - Version 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

I was having FQDN (Full Qualified Domain Name) issues after the installation and configuration of the EPM as a fresh install (Foundation server and Essbase Server environment). Before my server name was the FQDN but due to DNS issues in the network (not resolving the DNS name) I changed the DNS name and got the new name to point to the server IP address. Once having the new FQDN I redeploy and reconfigure the application dropping the database and creating the new one and I am 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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.