Deploy Essbase from Marketplace for Federated Partitions

To use federated partitions, you must deploy Essbase according to specific requirements.

Prerequisites

These instructions assume you have already done the following, as a domain administrator on Oracle Cloud Infrastructure:

• Created a compartment, dynamic group, and policy on the Oracle Cloud Infrastructure tenancy, as described in Before You Begin with Oracle Essbase.

• Created a vault for encryption keys and secrets on the Oracle Cloud Infrastructure tenancy, as described in Create Vault, Secrets, and Encrypt Values.

• Created a confidential application and an initial Essbase system administrator on the Oracle Cloud Infrastructure tenancy, as described in Set Up Essbase Access in Identity Cloud Service. Be sure to save the application's client secret, as well as the Essbase administrator password, in the vault.

• Optional: Provisioned an Autonomous Data Warehouse Serverless as described in Provision an Autonomous Data Warehouse for Federated Partitions. Be sure to save the Database administrator's password in the vault.

  Note:

  You can provision Autonomous Data Warehouse during the Essbase deployment.

Instructions

From the Marketplace on Oracle Cloud Infrastructure, deploy an Essbase stack to the same tenancy where you have provisioned (or will provision) Autonomous Data Warehouse.

Follow the instructions in Deploy Essbase, but while completing those steps,

1. If you already provisioned Autonomous Data Warehouse Serverless previously, ensure that it is up and running.

2. In the Essbase Instance screen, set up the Essbase file catalog to be integrated with the OCI object storage bucket.

   Change the Catalog Storage Type from the default (Local Filesystem) to Object Storage. This step is required if you want to load data from Essbase to Autonomous Data Warehouse.

   
   
   
   
   

   Note:

   If you select Object Storage integration,

   • You cannot change it back to Local File system after deployment.
   • Any Essbase jobs that require read/write access to files in the Essbase catalog will search for them in (or export them to) the OCI object storage bucket associated with the Essbase stack on OCI.
   • For more information, see Create Stack and Specify Files in a Catalog Path.

3. In the Database Configuration screen, select how you want to configure Autonomous Data Warehouse Serverless with Essbase. Essbase will use this database as the repository for its RCU schemas.

   1. Select Use Existing Database to use a previously provisioned Autonomous Data Warehouse Serverless.

      
      
      
      
      

   2. If you want to provision Autonomous Data Warehouse Serverless during this Essbase deployment, click Show Advanced Database Options, and from Choose a database workload type, select Autonomous Data Warehouse.

   In a separate schema of the same database, you will need to create the fact table for the federated partition. No other database instance or type can be used for the fact table.