Purpose
V$OB_SQL_WORKAREA_MEMORY_INFO displays some general information about the SQL workarea, including the maximum available memory, current memory usage, and currently held memory. Through this view, you can learn about the usage of the workareas in the current tenant, such as the memory usage.
Fields
| Field | Type | Nullable? | Description |
|---|---|---|---|
| MAX_WORKAREA_SIZE | NUMBER(38) | NO | The maximum memory that the workarea can occupy. The available memory is determined by ob_sql_work_area_percentage. |
| WORKAREA_HOLD_SIZE | NUMBER(38) | NO | The size of the currently held memory of the workarea. Note The specific memory usage cannot be obtained from the memory management module. Therefore, the size of the held memory is used. |
| MAX_AUTO_WORKAREA_SIZE | NUMBER(38) | NO | The estimated maximum available memory size in auto mode. The maximum available memory is calculated based on the following formula: MAX_WORKAREA_SIZE – WORKAREA_HOLD_SIZE + TOTAL_MEM_USED. It indicates the maximum memory that is automatically managed in the current workarea. |
| MEM_TARGET | NUMBER(38) | NO | The target size of memory that the workarea can occupy. It differs from max_auto_work_area in that its value is a percentage of the value of max_auto_work_area. |
| TOTAL_MEM_USED | NUMBER(38) | NO | The size of memory used in auto mode. This size is obtained from the automatic memory management module and does not reflect the actual usage size. |
| GLOBAL_MEM_BOUND | NUMBER(38) | NO | The maximum available global memory in auto mode. |
| DRIFT_SIZE | NUMBER(38) | NO | The current change in the required memory size. If the value of this field reaches the specified threshold, the global bound size is automatically recalculated. |
| WORKAREA_COUNT | NUMBER(38) | NO | The number of registered operator profiles. |
| MANUAL_CALC_COUNT | NUMBER(38) | NO | The number of calculations of the global bound size that are irregularly triggered. |