Forum Stats

  • 3,827,258 Users
  • 2,260,753 Discussions
  • 7,897,193 Comments

Discussions

EPMA Hyperion Planning: Essbase cube move from one server to other

Amit Porwal 007
Amit Porwal 007 Member Posts: 31
edited Jun 28, 2016 1:56AM in Planning and Budgeting

Hello All,

I came across a situation where we have Various EPMA Planning applications spread across Two Essbase server (ESS1 an ESS2).

Now we need to decommission One of the Essbase server (ESS2), and I need to know What needs to be done to

Migrate some of the EPMA Planning apps from ESS2 to ESS1.

so that the final configuration will Have just one EPMA and One Essbase server for all the Planning applications.

Really Appreciate your time to this post and Thanks in advance for any idea/steps to this problem statement.

Regards,

Amit

Amit Porwal 007

Best Answer

  • Sh!va
    Sh!va Member Posts: 1,035 Gold Badge
    edited Jun 27, 2016 10:31AM Answer ✓

    Open DSN of all Planning application whose Essbase side is on ESS2 server

    and point them on ESS1.

    Now migrate Essbase objects and data from ESS2 to ESS1 of those planning

    application.

    For cross checking run validate/deploy from EPMA for those planning cube.

    Cheers!

    Sh!va

Answers

  • Sh!va
    Sh!va Member Posts: 1,035 Gold Badge
    edited Jun 27, 2016 10:31AM Answer ✓

    Open DSN of all Planning application whose Essbase side is on ESS2 server

    and point them on ESS1.

    Now migrate Essbase objects and data from ESS2 to ESS1 of those planning

    application.

    For cross checking run validate/deploy from EPMA for those planning cube.

    Cheers!

    Sh!va

  • Madhusudhan. M
    Madhusudhan. M Business Analyst Member Posts: 1,904 Silver Trophy
    edited Jun 28, 2016 1:56AM

    Take backup of all folder structure as your saying you are going decommission the server.

    After changing the DSN, you should copy the essbase applications into ESS1 then bounce services once.(Essbase), then try to connect and access applications.

    Thanks,

    Mady

    Amit Porwal 007Amit Porwal 007
This discussion has been closed.