1. Essbase Stack Deployment on Oracle Cloud Infrastructure
  2. Migrate Essbase Applications
  3. Migrate from Essbase 19c, 21c, or Oracle Analytics Cloud – Essbase
  4. Prepare to Migrate Applications and Users

Prepare to Migrate Applications and Users

Here are some considerations and requirements when migrating applications, whether from Essbase on Oracle Analytics Cloud, on OCI or independent deployments.

Considerations and requirements

  • Lifecycle Management (LCM) import and Migration Utility import do not support migration of federated partitions. Federated partitions must be recreated manually on the target, after migration from 21c to 21c.

  • You can use the Essbase Command Line Interface (CLI) to migrate your source application and artifacts across deployments and releases.

  • In Independent deployments, when you have a large number of applications and using LCM is not feasible to export your applications, see: Migrate Multiple Essbase Instances to a Single Shared Services Instance.

  • Export and import using Migration Utility does not support migration of applications, if the Essbase instance is configured in EPM mode; you must use CLI with LCM export and import commands.

  • If you're migrating across Essbase cloud deployments and releases, from v17.3.3 (or earlier), use the scripts for migrating to Essbase. See Scripts for Administration Tasks. This also applies to export and import of provisioned application roles and scripts.

  • Restoring an application or database from a prior backup, after the application or database was re-created using LCM import, isn't supported.

  • Global variables, email configuration settings, and file scanner settings must be set on the target instance before using any of the migration tools.
  • Oracle Identity Cloud Service roles aren't supported in Essbase.
  • Migration Utility can migrate users and groups from embedded LDAP (or from Identity Cloud Service) to Identity Cloud Service in addition to all Essbase applications.
  • If you're migrating users and groups from an LDAP source to an Essbase instance, Identity Cloud Service doesn't support nested groups. Therefore, group associations to other parent groups, from an LDAP source instance, aren't migrated to Identity Cloud Service targets, when using Migration Utility.
  • Any users or groups that exist with the same name in the target environment as in the source environment, aren't updated in the target.
  • To run CLI or Migration Utility, use the Identity Cloud Service user that you provisioned to be the initial Essbase Service Administrator during the Essbase deployment and setup.
  • When you run Migration utility for SSL connection, include the host (-Dhttps.proxyHost) and port (-Dhttps.proxyPort) proxy settings in the command line.
  • Solve order applies to dynamic members in the outline and to dynamic calculation execution of dimensions and members. Adjust the solve order of dimensions and members to indicate their calculation priority. Solve order is recommended instead of using Two Pass calculation, because it's more flexible. You can set solve order for dimensions or members, or you can use the default Essbase solve order. The minimum solve order you can set is 0, and the maximum is 127. A higher solve order means the member is calculated later; for example, a member with a solve order of 1 is solved before a member with a solve order of 2. See Solve Order in Hybrid Mode.
  • Free-form data exports and imports for cubes with typed measures behaves differently in 21c. For the latest information, see Loading, Clearing, and Exporting Text and Date Measures.

For migrations from Oracle Analytics Cloud - Essbase to Oracle 21c Essbase

  • You can use Migration Utility to migrate multiple source applications and elements from Oracle Analytics Cloud - Essbase deployments as well as from Essbase Marketplace deployments.

  • The following migration paths are not supported in Essbase 21c: migration FROM Oracle Analytics Cloud Essbase TO Essbase 21c on Windows independent deployment, or FROM Essbase 19c on Linux platform TO Essbase 21c on Windows independent deployment.

  • After migration from Oracle Analytics Cloud - Essbase, Identity Cloud Service provisioning doesn't continue to be honored. However, Essbase server/application-level role assignments are migrated.
  • All Identity Cloud Service users and groups listed in the Security provisioning page in the Oracle Analytics Cloud - Essbase web interface can be provisioned with one of the Essbase roles: User, Power User, and Service Administrator.

Required user roles

  • For exporting: Application manager for the application created. In addition, the following roles can use LCM commands and CLI: Service Administrator for all applications; Power User for all applications created by the Power User.
  • For importing: Power User or Service Administrator, for creating new applications during import. If you use the Power User role, then the target applications are owned by the Power User used in the migration.