Overview

Casabase Cube provides a migration path for moving existing Oracle Essbase and Oracle Cloud EPM applications to Snowflake.

The migration process is designed to preserve supported multidimensional structures and business logic from the source application while moving the analytical model to a modern OLAP architecture running natively within Snowflake.

Casabase Cube is not an Essbase runtime, so some Essbase and Cloud EPM features are unsupported or handled differently. Review Compatibility Notes before validating a production migration.

Migration Overview

A typical migration uses two artifacts from the source application:

• The native Essbase outline (.otl) file
• A native level-0 export containing the application’s detailed data

Casabase Cube uses the outline to create the cube’s multidimensional structure and the native level-0 export to load the underlying data.

The overall process is:

1. Obtain the native outline (.otl) from Oracle Essbase or Oracle Cloud EPM.
2. Create a native level-0 export of the source data.
3. Make the required files available to Casabase Cube.
4. Import the outline.
5. Rebuild the cube hierarchies.
6. Import the native level-0 data.
7. Review migration messages and compatibility differences.
8. Validate the migrated cube and begin querying.

Choose Your Source Platform

Although Oracle Essbase and Oracle Cloud EPM use the same underlying Essbase outline and data formats, the process for obtaining the required artifacts differs between the two platforms.

Choose the guide for your source environment:

Oracle Essbase

Use the Oracle Essbase migration guide when migrating an Essbase application where you have access to the Essbase application artifacts and native data export capabilities.

Migrating from Oracle Essbase →

Oracle Cloud EPM

Use the Oracle Cloud EPM migration guide when migrating an application from Oracle Enterprise Performance Management Cloud.

The Cloud EPM process includes additional steps for retrieving the native Essbase outline and exporting the native level-0 data from the Oracle-managed environment.

Migrating from Oracle Cloud EPM →

Required Migration Artifacts

Artifact	Purpose
Essbase outline (.otl)	Defines the multidimensional structure of the application, including dimensions, hierarchies, members, aliases, formulas, and member properties.
Native level-0 export	Contains the detailed source data that will be loaded into Snowflake and queried by Casabase Cube.

Caution

Casabase Cube migration uses the native Essbase outline (.otl). XML outline exports and dimension CSV metadata exports are not required for the current migration workflow.

Interactive and Automated Migration

Casabase Cube supports both interactive and scripted migration workflows.

Interactive Migration

For initial migrations, testing, and ad hoc administration, the Casabase Cube interface provides a guided workflow for:

1. Uploading and importing the .otl file
2. Rebuilding hierarchies
3. Importing the native level-0 export
4. Querying the resulting cube

The .otl file can be uploaded directly through the Casabase Cube interface.

See the 5-Minute Quick Start for an introduction to this workflow.

Automated Migration

For repeatable production processes, migration operations can be performed using Casabase Cube SQL stored procedures.

In this workflow, migration artifacts are first placed in a Snowflake stage accessible to Casabase Cube. Stored procedures can then be called from SQL or incorporated into your organization’s existing orchestration and automation processes.

This approach is recommended for recurring production processes where source metadata or data must be refreshed from Oracle Essbase or Oracle Cloud EPM.

What Gets Migrated

The outline import is designed to recreate the multidimensional structures required by Casabase Cube, including:

• Dimensions
• Hierarchies
• Members
• Parent-child relationships
• Aliases
• Aggregation operators
• Shared members
• Member formulas
• Relevant member properties

The native level-0 export provides the detailed data associated with those structures.

Note

Migrated formulas and application structures should be validated as part of the migration process, particularly for applications containing complex Essbase calculations or application-specific logic. See Compatibility Notes for known differences that should be included in the validation plan.

Next Steps

Continue with the migration guide for your source platform:

• Migrating from Oracle Essbase
• Migrating from Oracle Cloud EPM
• Compatibility Notes