Add Essbase Cube Tables to the Physical Layer

From the Oracle Essbase connection, you can drag and drop cube tables to add them to the semantic model's physical layer.

You need to create one physical database in the physical layer for each cube or set of cubes.

Dragging and dropping a cube table from the data source connection to the physical database populates some of the database's features, the query features, and connection pools. You can adjust these settings as needed. You can add query limits for application roles to the database.

For Essbase, a cube table must be located in a catalog. When you drag and drop a cube table from an Essbase connection into the physical database, Semantic Modeler adds a catalog.

See About Adding Essbase Cube Tables to the Physical Layer.

See About Connecting to an Oracle Essbase Data Source.

  1. On your home page, click Navigator Navigator icon and then click Semantic Models.
  2. In the Semantic Models page, click a semantic model to open it.
  3. Click Physical Layer Physical layer icon.
  4. In the Physical Layer pane click Create Create icon and then click Create Database.
  5. In Create Database, go to the Name field and type a name. In the Database Type field select Oracle Essbase. Click OK.
    The new database's Tables tab is displayed.
  6. In the Tables tab, click Connections Connections icon and in the connections pane, expand the Oracle Essbase connection and browse or search for the cube table to add to the physical database.
  7. Drag the cube table to the physical database and drop it into the Tables list.
  8. In the Cube Table Options dialog, specify how you want Semantic Modeler to add the cube table to the physical layer.
    Semantic Modeler creates a catalog and adds the cube table to it.
  9. Click the Connection Pools tab and verify that your database and connection pool settings are correct.
  10. Click the Tables tab to inspect and confirm the imported physical columns and hierarchical levels.
  11. Click the Tables tab, double click a hierarchy to open it, and go to the Hierarchy Type field to inspect and adjust its type. Note that by default Semantic Modeler imports all hierarchies as Unbalanced.
  12. Click Save.