Create a Schema for Federated Partitions

After you have provisioned an instance of Autonomous Data Warehouse Serverless, create a dedicated schema in the database for the fact table you need to work with Essbase federated partitions.

The schema you need to create for the federated partition, including its fact table, is independent from the Essbase RCU schemas. However, it does need to be in the same Autonomous Data Warehouse Serverless database, which is also known as the repository database.

Create a schema / Database user (for example, ADB_USER) with sufficient privileges to work with federated partitions.

CREATE USER ADB_USER identified by schemapass DEFAULT TABLESPACE DATA TEMPORARY TABLESPACE TEMP ACCOUNT UNLOCK;
grant CREATE ANALYTIC VIEW, CREATE HIERARCHY, CREATE TABLE, CREATE ATTRIBUTE DIMENSION, CREATE SESSION, CREATE VIEW, RESOURCE, CONNECT to ADB_USER;
grant execute on dbms_cloud to ADB_USER;
grant execute on dbms_cloud_oci_obs_object_storage to ADB_USER;
ALTER USER ADB_USER DEFAULT ROLE RESOURCE;
ALTER USER ADB_USER QUOTA UNLIMITED ON DATA;
commit;

Optional: If you plan to create more than one Essbase application using a federated partition, you must make a choice. You can use a single schema for all federated partitions, or create multiple schemas (typically one schema per application containing a federated partition).
Note:

Regardless of the number of schemas you create, you must maintain the following:
- Each Essbase application has only one database (cube).
- Each Essbase application has only one federated partition
- Each federated partition uses only one fact table.
- Unlike other partition types used in Essbase, the data is not in two locations. Your federated partition's fact table must contain all the cube's data.
For a comprehensive list, refer to Restrictions for Federated Partitions.
Now that you have created a schema for the fact table, you can move on to Set Up Fact Table and Identify Pivot Dimension.