My Oracle Support Banner

Enterprise Performance Management(EPM): EPM Registry Is Not Getting Updated After The Re-deploy And Re-configuration Of EPM 11.1.2.4.0 (Doc ID 2145923.1)

Last updated on DECEMBER 20, 2020

Applies to:

Hyperion Essbase - Version 11.1.2.4.000 and later
Information in this document applies to any platform.

Symptoms

EPM Registry is not getting updated after the re-deploy and re-configuration of EPM 11.1.2.4.0

The Environment was having FQDN (Full Qualified Domain Name) issues after the installation and configuration of the EPM 11.1.2.4.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.

Cause

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
Symptoms
Cause
Solution


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