1. Migrating Essbase Instances from Oracle Analytics Cloud to Essbase on Oracle Cloud Infrastructure via Marketplace
  2. Learn About Migration to Oracle Cloud Infrastructure
  3. About the Migration Scope

About the Migration Scope

Before migrating Essbase instances from Oracle Analytics Cloud to Oracle Cloud Infrastructure, consider the scope and constraints of this migration path.

Summary

  • Migration scenarios covered in this Guide

    • Source EssbaseOracle Analytics Cloud instance: , 105.2 or later

      Source Oracle Analytics Cloud - Classic instance: Essbase, 105.2 or later

    • Source Oracle Analytics Cloud Oracle Managed instance: Essbase, 105.2 or later (Oracle Identity Cloud Service instances only, not embedded LDAP)
    • Source identity management: Oracle Identity Cloud Service (Cloud accounts) or embedded LDAP server (traditional accounts)
    • Target Essbase 19c instance on Oracle Cloud Infrastructure
  • Not covered in the Guide
    • Source Oracle Analytics Cloud - Classic instance: Data Visualization, Business Intelligence
    • Database migration

Migration scenarios covered in this Guide

With Oracle Analytics Cloud, you can deploy services with several different feature sets: Business Intelligence, Data Visualization, and Essbase.

This Guide only describes how to migrate services deployed with Essbase.

Before you start, Oracle recommends that you patch your source service with the latest available version. The migration tools you need aren't available in earlier versions. For Oracle Managed instances, you must be on the latest version; if not, work with Oracle Support to ensure that you are.

You can verify the current version of your source and target environments in Oracle Cloud Infrastructure Console. If you're not sure, check with your administrator.

Not covered in this Guide

This Guide doesn’t describe how to migrate Oracle Analytics Cloud instances deployed with the Business Intelligence or Data Visualization, or non-Oracle Analytics Cloud artifacts, such as associated databases, security configuration, and so on. You must migrate non-Oracle Analytics Cloud artifacts separately or re-create them on the target instance.