1. Using Oracle Essbase
  2. Integrate Essbase with Autonomous Database Using Federated Partitions
  3. Create a Federated Partition

Create a Federated Partition

This topic shows you how to create a federated partition between Essbase and Autonomous Data Warehouse Serverless.

This topic assumes you have completed the prerequisites and reviewed the information detailed in the preceding topics.

The following instructions are for the Essbase web interface. Log in as a service administrator or application manager.

To build a federated partition using Cube Designer, refer to Create a Federated Partition in Cube Designer.

  1. On the Applications page, click the name of the application you will use to create a federated partition.

  2. On the Customization page, click Settings, and expand Startup.

    Ensure that Allow Users to Start Application is enabled.


    Allow application to start check box in Application Settings.

  3. Click General, click the Database name, and click Partitions.

  4. Click Create >Federated.


    Create button on Partitions tab, with selections for Transparent, Replicated, and Federated.

  5. For Connection name, enter the connection to Autonomous Data Warehouse that was previously created by an administrator or application manager, as shown in Create a Connection for Federated Partitions.

  6. For Schema name, ensure that it matches the name of the database schema (user name that you entered when you created the connection).

  7. For Fact table name, select the name of the fact table in Autonomous Data Warehouse that stores numeric values and keys.

    If Essbase recognizes dimension names from the fact table, the values in the Dimension columns field may autocomplete with Essbase dimension names. Similarly, the values in the Pivot member columns field may autocomplete with members of the presumed pivot dimension.

  8. For Pivot dimension, select the name of the pivot dimension you decided to use from the Essbase outline, during the Identify the Pivot Dimension process.

    If the column names in the fact table are the same as the dimensions and pivot member names in the outline, then the mapping is automatically populated in in the Pivot member tab of the Essbase members to fact table column mapping. If any dimensions or members cannot be automatically mapped to a column in the fact table, you will need to map them manually.

    Use the Update button if you need to manually map stored pivot dimension members to fact table columns.


    Essbase members to fact table column mapping in the federated partition creation UI. Pivot dimension columns are mapped here. Essbase outline dimension member names are on the right, and fact table column names are on the left.

    If a member of the pivot dimension (or a non-measures dimension name) includes a special character, such as &, Oracle recommends renaming it.

    Essbase automatically maps member names with spaces to corresponding column names in the fact table with the space replaced by an underscore. For example, Essbase automatically makes the following mapping:

    Pivot dimension member name Fact table column name
    "Initial Inventory" INITIAL_INVENTORY

  9. Click Dimension column to map the non-pivot dimensions to columns in the fact table. They may map automatically if the fact table column names match the dimension names in the outline. If needed, you can map them manually.


    Essbase members to fact table column mapping in the federated partition creation UI. Non-pivot dimension columns are mapped here. Essbase outline dimension member names are on the left, and fact table column names are on the right.

  10. Click Validate.

  11. If the validation succeeded, click Save and Close, and confirm that it is OK to restart the application.

    Saving or validating your federated partition may take a while to complete. Check the job status.

    The federated partition is created. This process also creates dimension helper tables (and other artifacts) in Autonomous Data Warehouse, which are linked (by keys) to the fact table.


Federated partition definition with pivot member mapping shown in Essbase web interface

  1. In the Essbase web interface, open the application inspector: on the Applications page, find the target application name, click the Actions menu, and click Inspect.

  2. On the Settings tab, click Startup.

    Ensure that Allow Users to Start Application is enabled.


    Allow application to start check box in Application Settings.

  3. In the Essbase web interface, open the cube inspector: on the Applications page, expand the target application. In the row for the target cube, click the Actions menu, and click Inspect.

  4. Select the Partitions tab.

  5. Click Create >Federated.

  6. For Connection name, enter the connection to Autonomous Data Warehouse that was previously created by an administrator or application manager, as shown in Create a Connection for Federated Partitions.

  7. For Schema name, ensure that it matches the name of the database schema (user name that you entered when you created the connection).

  8. For Fact table name, select the name of the fact table in Autonomous Data Warehouse that stores numeric values and keys.

  9. For Pivot dimension, select the name of the pivot dimension you decided to use from the Essbase outline, during the Identify the Pivot Dimension process.

    If the column names in the fact table are the same as the dimensions and pivot member names in the outline, then the mapping is automatically populated in Essbase to column map. If any dimensions or members cannot be automatically mapped to a column in the fact table, you will need to map them manually.

    Use the Update button if you need to manually map stored pivot dimension members to fact table columns.

    If a member of the pivot dimension (or a non-measures dimension name) includes a special character, such as &, Oracle recommends renaming it.

    Essbase automatically maps member names with spaces to corresponding column names in the fact table with the space replaced by an underscore. For example, Essbase automatically makes the following mapping:

    Pivot dimension member name Fact table column name
    "Initial Inventory" INITIAL_INVENTORY

  10. Click Dimension column to map the non-pivot dimensions to columns in the fact table. They may map automatically if the fact table column names match the dimension names in the outline. If needed, you can map them manually.

  11. Click Validate.

  12. If the validation succeeded, click Save and Close, and confirm that it is OK to restart the application.

    Saving or validating your federated partition may take a while to complete. Check the job status.

    The federated partition is created. This process also creates dimension helper tables (and other artifacts) in Autonomous Data Warehouse, which are linked (by keys) to the fact table.


Federated partition definition with pivot member mapping shown in Essbase web interface


Federated partition definition with dimension column mapping shown in Essbase web interface

Note:

After you are finished creating the federated partition, one or more individuals should configure DBMS_CLOUD credentials to allow additional data load connectivity from Essbase to Autonomous Data Warehouse. Refer to Federated Partition Data Load for more information.