Resolving Migration-Related Errors

Oracle Enterprise Performance Management Cloud supports many migration scenarios. These topics in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators provide detailed information:

Importance of the Essbase Version in Use

By default, EPM Standard Cloud Service and EPM Enterprise Cloud Service are deployed using an Oracle Essbase version capable of supporting Hybrid BSO cubes (referred to as Hybrid Essbase).

Legacy EPM Cloud environments, for the most part, are configured with an Essbase version that does not support hybrid-cubes (referred to as Non-hybrid Essbase). The following are exceptions:

Enterprise Planning and Budgeting Cloud
Planning and Budgeting Cloud with Plus One option
Financial Consolidation and Close Cloud with extended dimensionality

For legacy environments, you can use a self-service operation to upgrade from Non-hybrid to Hybrid Essbase. Compatibility of your snapshot with the Essbase configured in your environment may cause migration errors even when you are migrating between similar environments, for example, from test environment to production environment in legacy Planning and Budgeting Cloud. For detailed information, see About Essbase in EPM Cloud in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators.

What Should I Do If I Get a Migration Error?

Check if the migration is supported. Information about supported migrations is available in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators:
Verify that a compatible Essbase version is being used. You use the recreate EPM Automate to upgrade or downgrade Essbase in legacy environments.
Review the Migration Status Report to see the errors and potential corrective actions to fix them. See Generating the Migration Status Report in Administering Migration for Oracle Enterprise Performance Management Cloud.