A Unique Instance Name Is Required When Configuring A New Install Of EPM 11.1.2.1 In Distributed Environment

A Unique Instance Name Is Required When Configuring A New Install Of EPM 11.1.2.1 In Distributed Environment [ID 1317679.1]

--------------------------------------------------------------------------------

Modified 10-MAY-2011 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution



--------------------------------------------------------------------------------



Applies to:
Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Hyperion Essbase - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Financial Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Planning - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Profitability - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Information in this document applies to any platform.

Goal
To install and configure Oracle EPM 11.1.2.1 in a distributed environment with a proper Instance name on each server

Solution
When configuring EPM 11.1.2.1 in a distributed environment, it is necessary to supply a new, unique Instance name on each server.

For example.

If using the default Instance name 'epmsystem1' on the first server, if you keep the same naming convention on subsequent servers, you will need to supply new, unique Instance names such as epmsystem2, epmsystem3, etc.

During Configuration each instance gets written to the EPM System Registry and the EPM System Configurator verifies that each instance name is unique. If you fail to provide a new unique instance name during the configuration process you will receive a message stating that the instance name is not valid. You will be forced to go back and enter a unique instance name.

Note: If you are applying the maintenance release (11.1.2 to 11.1.2.1), during the configuration process you select the first option "Modify existing instance" since the epmsystem1 instance name already exists and is shared by all servers in the distributed environment. Be sure not to delete or change the instance names during a maintenance release configuration as it will cause the configuration to change from a maintenance install to a new installation and will cause issues with the rest of the server deployments in the distributed environment