Reviewing Unary Operators and the Use of Label Only Setting

Carefully review all dimensions for the use of the following:

• Unary Plus operator

  Every member roll up as "addition" can increase the calculation count required for the entire cube. Use "never" or "ignore" where you do not need to add the member into its parent. In general, it is not mandatory to roll up all scenarios into the top node Scenario member using "addition". In such cases, set the children to "ignore" or "never" and the parent to "label only".

  The "Ignore" option prevents aggregation within the specific dimension containing the member but allows aggregation across other dimensions. For example, this setting ensures that members like Scenario (such as Actual and Budget) are not aggregated up, while allowing members from other dimensions, such as Entities and Products, to be aggregated. The "Never" option prevents aggregation across all dimensions. For instance, members like Exchange Rates, Smart Lists, and Text members typically only need to exist at the level they are loaded and do not require any form of aggregation.

• Label only for parents

  In ASO cubes, a parent must be set to "label only" when children are set to "ignore".

Review the Activity Report data related to these areas to check if these are causing performance issues:

• Cube size
• Cube performance
• Number of formula executions

For ASO cubes, the formula executions identified as ullFormulaExec and ullFormulaExecOOT are attributable to the number of calculations across dynamic hierarchy type dimensions. These are identified in the Context column of the Top 10 Longest Performing Essbase Queries over 15 seconds section in the Activity Report. For more information, see Essbase Metric in Getting Started Guide for Administrators.