Restrictions

Essbase on Autonomous AI Lakehouse is an Oracle-managed cloud service.

Oracle manages the service infrastructure and its integration with Autonomous AI Lakehouse, so you can focus on modeling, calculations, and analysis.

Most readers can use the tasks in this guide without needing to consider these limitations. The differences are most relevant when you move applications, calculation scripts, or processes from another Essbase offering.

Managed Service Boundaries

You do not need to deploy and configure Essbase on Autonomous AI Lakehouse, as it is Oracle managed.

Application Design

Each Essbase application contains one cube.

Features Not Available/ Not Relevant

Essbase on Autonomous AI Lakehouse does not include:

• Scenario management (sandbox cube environment with approval workflows)
• Legacy Essbase currency conversion cubes
• Data audit using Essbase AUDITRAIL configuration (Autonomous AI Lakehouse has its own data audit capabilities)
• Essbase triggers for cube events
• Shadow applications are not available
• Making copies of applications or cubes is not supported

Calculations and Data Operations

Do not assume that a calculation script from another Essbase offering will run without changes. Some advanced calculation features are not supported. To review official limitations, refer to: Restrictions for Federated Cubes.

If you need to load additional source files beyond what is in Lakehouse, use a DBMS-formatted source file for efficient data loading. Refer to: Data Load Options for Federated Cubes.

Moving Existing Applications

Lifecycle Management import operations and Migration Utility imports are not available. Review existing applications and processes before you move them to Essbase on Autonomous AI Lakehouse.