The 184.108.40.206 Essbase Readme document has been
updated to include a change in recommendation with regard to rebuilding versus migrating
the Essbase outlines between major release upgrades. This represents a change in the upgrade
process to ensure outlines take advantage of any new structures, features and
functionality introduced in the major release.
After a major release upgrade, be sure to rebuild
all outlines on the new release to eliminate any potential issue where the
outline may not be compatible or properly take advantage of any new
OPatch upgrades are not considered a major release
and therefore do not need to adhere to the new guidelines. The traditional outline upgrade or migration process
can continue to be utilized for OPatch upgrades.
Here is the statement added to the Essbase
220.127.116.11 Readme document:
When upgrading to a version of Essbase in which
you use the Oracle Hyperion Enterprise Performance Management System Installer
and Oracle Hyperion Enterprise Performance Management System Configurator, as
in this release, database outlines that were created in any of the previous
Essbase releases listed in this topic should be recreated in this release to
take advantage of any new structures, features, and functionality.