Does the Essbase Studio Catalog Need to be Upgraded After Migrating To EPM v184.108.40.206
(Doc ID 1987165.1)
Last updated on MAY 22, 2018
Applies to:Hyperion Essbase Studio - Version 220.127.116.11.505 and later
Information in this document applies to any platform.
When upgrading our EPM environment from 18.104.22.168.500 to 22.214.171.124 by applying the 126.96.36.199 maintenance release, the install documentation and readme has the following regarding the Essbase Studio Catalog.
Is this step not required when upgrading from 188.8.131.52.500 to 184.108.40.206:
Essbase Studio Manual Configuration Tasks in a Maintenance Installation
If you used the "Apply Maintenance Release" option to move from Essbase Studio Release 220.127.116.11, 18.104.22.168 or 22.214.171.124 to this release, you must update the Essbase Studio catalog after installation and configuration.
You update the catalog by issuing the "reinit" command in the Essbase Studio command line client, which updates the catalog with the latest release procedures.
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