Federated Cube Deployment Workflow

In order to implement a federated cube, Essbase and Autonomous AI Database Serverless need to be deployed together in a shared Oracle Cloud Infrastructure tenancy, with Autonomous AI Lakehouse serving as the repository database that holds RCU schemas for the Essbase stack deployed on OCI from Marketplace.

The workflow to set up a federated cube is:

  1. Review Plan a Federated Partition Environment.

  2. Review the Prerequisites for Federated Cubes.

  3. Log in to your organization's Oracle Cloud Infrastructure tenancy.

  4. Optional: Provision an instance of Autonomous AI Lakehouse. (You may instead choose to provision one during the next step).

    Note:

    Here and elsewhere in this federated partitions documentation, all references to Autonomous AI Lakehouse should be considered to mean Autonomous AI Database Serverless with Autonomous AI Lakehouse workload type.

    See Provision Autonomous AI Lakehouse for Federated Cubes.

  5. From the Marketplace listing in Oracle Cloud Infrastructure, deploy an Essbase stack to the same tenancy. See Deploy Essbase from Marketplace for Federated Cubes.

  6. Create a schema in Autonomous AI Lakehouse to use for the fact table. See Create a Schema for Federated Cubes.

  7. Create an Essbase application and cube.

    Select a BSO or ASO application and cube as the starting point. Depending on your circumstances, the starter cube may already exist, or you may create a new one and then create the federated partition over it.

    Note:

    After you create the federated partition, your cube becomes a federated cube.

    If you are not sure which type of cube to start with, review the comparison table in Federated Cubes: Integrate Essbase with Autonomous AI Database.

  8. Create a fact table in the Autonomous AI Lakehouse schema.

    Note:

    This step is not required if you plan to let Essbase manage the data storage. See Data Load Options for Federated Cubes.

    For guidelines on fact tables (and pivot dimensions), see Learn About Fact Tables and Pivot Dimensions.

  9. Define a connection that enables Essbase to access the schema on Autonomous AI Lakehouse, as shown in Create a Connection for Federated Cubes.

    To create a global connection, you need to have the service administrator role. To create an application level connection, you need to have user role, plus application manager permission on the application.

  10. Set up cloud credentials to enable Essbase to push data and metadata to Autonomous AI Lakehouse. See Set up Credentials for Federated Cubes.

  11. Log in to the Essbase web interface and create the federated partition, as described in Create a Federated Partition.

  12. Complete a workflow to enable SQL cancellation of long running requests. See Cancel Long Running SQL on Federated Cubes.

  13. Learn about maintaining and troubleshooting the federated cube. See Federated Cube Maintenance and Troubleshooting.