You can use query data to select the most appropriate set of aggregate views to materialize for a database. To capture data about the cost of each query that is performed against the database, you can enable query tracking. Once enabled, query tracking continues until one of the following happens:
Query tracking is disabled for the database, as described in this topic.
The application is shut down. If the application is shut down, query tracking does not resume automatically when the application is restarted.
Additional aggregate views are materialized for the database. Because query tracking data becomes invalid when additional views are materialized, materializing any new aggregate views resets the query tracking.
Query tracking, which is stored only in memory, includes queries from Oracle's Hyperion® Web Analysis, the grid API, report scripts, Java APIs, and so forth.
For information about how query cost is defined and how query data is stored, see “Selecting Views Based on Usage” in the Oracle Essbase Database Administrator's Guide.
To enable or disable query tracking for aggregate storage databases:
From Enterprise View or a custom view, select a database.
Right-click, and select Query tracking, and then Enable or Query Tracking, and then Disable.
When you enable query tracking, Essbase begins recording query information. When you disable query tracking, Essbase stops recording query information and clears query data from memory.
“Selecting Views Based on Usage” in the Oracle Essbase Database Administrator's Guide
alter database (MaxL) in the Oracle Essbase Technical Reference