In-Memory Page
Note: Oracle In-Memory is available for Oracle 12c Release 1 (12.1.0.2) and above. Data is displayed for Oracle instances where In-Memory is available and has been enabled. In-Memory is disabled by default.
To open the In-Memory page
- Select the Spotlight on Oracle connection in the Spotlight Browser.
-
Click Configuration & Memory | In-Memory.
In Memory Throughput Chart
Use this chart to investigate the extent to which I/O is being consumed by In-Memory activities.
| Metric | Description |
|---|---|
|
In-Memory Scans |
The rate at which data is read from the In Memory column store. |
|
In-Memory Repopulate |
The rate at which data is repopulated into In-Memory from the buffer cache. |
|
In-Memory Repopulate from Storage |
The rate at which data is repopulated into In-Memory from disk. |
|
Logical Reads from Cache |
The rate at which data is read from SGA (not the In-Memory column store). |
In-Memory Overhead Chart
Use this chart to investigate the costs to the database of enabling In-Memory.
This chart shows the rate of database time used to populate the In-Memory store.
| Metric | Description |
|---|---|
| Total DB Time | The rate of time spent performing user calls on the database. |
| Population Time | The rate of time spent populating the In-Memory Column store. |
| Prepopulation Time | The rate of time spent initiating the population of In-Memory enabled objects with a priority of LOW, MEDIUM, HIGH or CRITICAL. |
| Repopulation Time | The rate of time spent recreating In-Memory Compression Units (IMCU). The Oracle Database repopulates an IMCU when the number of stale entries in the IMCU reaches a staleness threshold. |
| Trickle Repopulation Time | The rate of time spent in trickle repopulation. The IMCO (In-Memory Coordinator) background process may instigate trickle repopulation for any IMCU in the IM column store that has some stale entries but does not currently meet the staleness threshold. Trickle repopulate is a constant background activity. |
In-Memory Information