Forum Stats

  • 3,873,729 Users
  • 2,266,635 Discussions


Using DNS entry instead of reconfiguration

Mikkis Member Posts: 223 Blue Ribbon
edited Jul 9, 2020 12:59AM in EPM System Infrastructure

We have recently performed DB upgrade in non-prod. As part of the upgrade we have built new DB server - say BBB. Our hyperion environment was pointing to old DB server - say AAA. Now we need to change DB server from AAA to BBB.
For that, instead of re-configuring the DB for hyperion components, we put DNS entry in BBB server (In other words, AAA is the second alias for BBB)

Now anything in hyperion that points to AAA is  essentially pointing to BBB (Pinging AAA gives the IP address of BBB server).

My question is - has anyone done the DB change this way without reconfiguration? If yes, what are some of the things I need to check or validate?

I have done full testing of environment without any issues. For one issue with Workspace login for newly provisioned users, I disabled a setting in weblogic. Other than this, didn't see any issues. Diagnostic reports are good.

Thanks in advance,




  • Vasantha Kumar
    Vasantha Kumar Member Posts: 66 Bronze Badge
    edited Jul 8, 2020 11:27PM

    Since you have made the DNS/Alias entry at the DB side to point back to the new DB instance with the existing connection which are configured in EPM, I think it should be fine.



  • Madhusudhan. M
    Madhusudhan. M Principal Consultant Member Posts: 1,912 Silver Trophy
    edited Jul 9, 2020 12:59AM

    It's better to log an SR with Oracle, to know implications about this change. Because, on-going, if you find any issue, we can't trace the changes which change is causing that issue.

    When you are pinging Host AAA, you mentioned you are getting IP Address of BBB. I think, this is fine, because ultimately we needs to get connect with IP Address.