EPM Registry Is Not Getting Updated After The Re-deploy And Re-configuration Of EPM 126.96.36.199.0
Last updated on JUNE 13, 2016
Applies to:Hyperion Essbase - Version 188.8.131.52.009 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 184.108.40.206.0
I was having FQDN (Full Qualified Domain Name) issues after the installation and configuration of the EPM 220.127.116.11.0 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.
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