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.

  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.

  3. Ensure that Allow Users to Start Application is enabled.


    Allow application to start check box in Application Settings.

  4. 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.

  5. Select the Partitions tab.

  6. Click Create >Federated.

  7. 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.

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

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

  10. 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
  11. Click Non measures to map the non numeric dimensions to columns in the fact table. They may map automatically if the fact table column names match the dimension names in the outline. Otherwise, map them manually.

  12. In the Areas tab, the partition target area is automatically defined based on the mapping. You do not need to edit the target area.

  13. Click Validate.

  14. 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 to see if partition creation is complete.

    The 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.

Example


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


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