Set up an Essbase Failover Environment

Get Started

  1. Follow the steps in Essbase Failover Prerequisistes.

  2. Log in to the primary node, open a command prompt or terminal, and ping the secondary (failover) node. Make note of its public IP. For example,
    ping secondaryhost.example.com
  3. Log in to the secondary (failover) node, open a command prompt or terminal, and ping the primary node. Make note of its public IP. For example,
    ping primaryhost.example.com

Set up the Primary Node

  1. Install Oracle Essbase 21c using the EPM 11.2.15 installer. See Installing Essbase Server.
  2. Start the EPM configuration tool and configure all the EPM components, including Essbase 21c. Ensure that you note the the EPM schema details so that this can be reused on every failover node while configuring EPM Foundation services. See Configuring Foundation Services.

Set up the Secondary (Failover) Node

  1. Use the EPM 11.2.15 installer to install the Foundation services and Essbase 21c. It should be installed in the same path as the primary node. See Installing Foundation Services.

    Note:

    The installation path on the primary and secondary nodes should be precisely the same directory path (not on the same system). For example, on both primary and secondary nodes, it may be <Local Drive>:\Oracle\EPMSystem. This implies that they can have the same path name, and they are not shared directories.

  2. Start the EPM configuration tool and configure ONLY the EPM foundation component. Remove the selection (uncheck) for Essbase. Ensure that you connect to the same EPM schema that is set up on the primary node when configuring the EPM foundation.
  3. Follow the steps described in Set up an Essbase Failover Environment to perform the Essbase 21c primary and secondary (failover) configuration.

Note:

  • The EPM configuration tool's Configure Essbase option shouldn't be chosen on any of the failover nodes.
  • In the event that the Configure Essbase option is inadvertently checked or selected during the configuration of a failover node using the EPM configuration tool, that node will turn into an independent installation that cannot be changed afterwards.
  • In the event of an EPM upgrade, Essbase 21c replaces Essbase 11.1.2.4 only after the manual Essbase failover procedures have been carried out.
  • In the event that the system had APS before the upgrade, the upgrade would not take place. APS would be available in the Failover node only if it was installed or configured in the primary node.