V$AW_CALC
reports on the effectiveness of various caches used by Oracle OLAP during dynamic aggregation.
Column | Datatype | Description |
---|---|---|
|
|
A unique numeric identifier for the session. |
|
|
The number of times a dimension member is found in the aggregate cache (a hit). The number of hits for run-time aggregation can be increased by fetching data across the dense dimension |
|
|
The number of times a dimension member is not found in the aggregate cache and must be read from disk (a miss). |
|
|
The number of times the data is found in the session cache (a hit). |
|
|
The number of times the data is not found in the session cache (a miss). |
|
|
The number of times the data is found in a page in the OLAP page pool (a hit). |
|
|
The number of times the data is not found in the OLAP page pool (a miss). |
|
|
The number of newly created pages in the OLAP page pool that have not yet been written to the workspace LOB. |
|
|
The number of previously unused pages that have been recycled with new data. |
|
|
The number of times the data from the OLAP page pool has been written to the database cache. |
|
|
The number of kilobytes in the OLAP page pool. |
|
|
The command currently being executed. |
|
|
The command most recently completed. |
|
|
The number of times the aggregation engine returns a logical NA because the AGGINDEX option is on and the composite tuple does not exist. |
|
|
The number of times the aggregation engine finds a value in a position that it was called to calculate. |
|
|
The number of times the aggregation engine calculates a parent value based on the values of its children. |
|
|
The ID of the container to which the data pertains. Possible values include:
|