EPM Configurator Shows Server Name For Configured Database Even Though A DNS Alias Was Originally Provided
(Doc ID 2191542.1)
Last updated on FEBRUARY 28, 2019
Applies to:Hyperion BI+ - Version 126.96.36.199.000 and later
Information in this document applies to any platform.
When stepping through the EPM Configurator wizard to configure a particular EPM product, the "Configure Database" task is selected, and on the panel where the database details are specified, a DNS alias for the applicable server is provided. The entry is accepted and the configuration completes.
At a later time, the Configurator is launched to configure another product. It is observed that the entry for the server (specified above) is now the physical or true hostname instead of the DNS alias name that had been submitted. If the hostname is changed back to the DNS alias and re-configured, the incorrect hostname will eventually be reverted.
In the EPM registry report, localhost_name is set to the physical server, not the specified DNS alias.
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