Use Unqualified Member Names to Improve Performance

When member names (including aliases) are unique in a given hierarchy, the Oracle Analytics query engine can take advantage of specific multidimensional expression (MDX) syntax to optimize performance.

After you import a cube table, you must confirm that member names are unique for a given hierarchy. It is important that you confirm this setting because query errors can result when a hierarchy is specified as having unique members when it doesn't.

You can fix this issue in the Essbase outline or in the physical hierarchies properties in Semantic Modeler.

To fix this issue in the Essbase outline, go to the outline and update each offending member variable by adding a prefix or suffix to make the member name unique, update SQL queries, and reload the data and members in the Essbase outline.

To fix this issue in the physical hierarchy:

1. On your home page, click Navigator and then click Semantic Models.
2. In the Semantic Models page, click a semantic model to open it.
3. Click Physical Layer .
4. Browse for and double click to open the physical cube table, and then from the Dimensions and Hierarchies pane, browse for and double click the hierarchy level where you want to set the property.
5. Click the Use unqualified member name for better performance field to select it.
6. Click Save.