Plan a Federated Partition Environment

To combine the benefits of Essbase and Autonomous AI Lakehouse, consider implementing a federated cube. Here is how to plan the environment and your deployment strategy.

  1. Read the federated partition prerequisites before you use the Marketplace listing to deploy Essbase as a stack on your Oracle Cloud Infrastructure (OCI) tenancy: Prerequisites for Federated Cubes

  2. As is always advised when deploying Essbase on OCI via Marketplace, review the deployment instructions in Deploy Essbase. But before you deploy or upgrade the Essbase stack, refer also to these deployment instructions specifically for the federated partition environment: Deploy Essbase from Marketplace for Federated Cubes.

  3. Size your Autonomous AI Lakehouse to be able to handle being used as a repository for both the RCU schema as well as your user schema where the fact table resides. You shouldn't use any of the RCU schemas as the fact table. Refer also to Provision Autonomous AI Lakehouse for Federated Cubes.

  4. After you are finished creating the federated partition, one or more individuals must configure DBMS_CLOUD credentials to allow connectivity from Essbase to Autonomous AI Lakehouse. Refer to Set up Credentials for Federated Partitions for more information.