The minimum application permission required to materialize ASO aggregations is Application Manager.

The views to build must either be identified by their view IDs, obtained previously using execute aggregate selection, or by a view selection saved in an aggregation script.

You can also configure Essbase to generate aggregate views automatically. For more information about aggregate views, refer to Aggregating an Aggregate Storage Database.

Syntax

• DBS-NAME

• VIEW-ID

• VIEW-SIZE

• OUTLINE-ID

• VIEW-FILE-NAME

Keywords

You can build (materialize) ASO aggregations in the following ways using MaxL execute aggregate build.

execute aggregate build … using views...

Builds an aggregation based on a previously selected view (or views) and the associated ASO outline ID.

execute aggregate build … using view_file VIEW-FILE-NAME

Builds an aggregation based on a saved view selection stored in an aggregation script.

Omit the .csc file extension from the view file name when you issue the execute aggregate build statement.

Notes

• Although it is possible to pass arbitrary VIEW-ID and VIEW-SIZE arguments, this practice is not supported.

• Passing VIEW-SIZE arguments other than those returned by the execute aggregate selection command may cause unpredictable results.

Examples

execute aggregate build on database ASOSamp.Basic using views 711 0.00375 with outline_ID 4142187876;

Builds an aggregation of the ASOSamp.Basic cube. The build is based on the view of an aggregate storage outline (identified as 4142187876) having the view ID 711, and a view size of 0.00375.

execute aggregate build on database ASOSamp.Basic using view_file myView;

Builds an aggregation of the ASOSamp.Basic database based on the view saved in the aggregation script myView.csc.