Purpose
GV$OB_SQL_WORKAREA_MEMORY_INFO displays the overall information about the SQL workarea, such as the maximum available memory, current memory usage, and current Hold memory. In this view, you can learn about the usage of workarea in the current tenant, such as the memory usage.
Fields
| Field | Type | Nullable? | Description |
|---|---|---|---|
| MAX_WORKAREA_SIZE | NUMBER(38) | NO | The maximum memory available for the workarea, which is determined by the ob_sql_work_area_percentage parameter. |
| WORKAREA_HOLD_SIZE | NUMBER(38) | NO | The size of the current Hold memory of the workarea. Note The specific memory usage cannot be obtained from the memory management module. Therefore, the size of the Hold memory is used. |
| MAX_AUTO_WORKAREA_SIZE | NUMBER(38) | NO | The estimated size of the maximum available memory 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_WORKAREA_SIZE in that this size is part of the maximum available size in auto mode. |
| TOTAL_MEM_USED | NUMBER(38) | NO | The size of memory used in auto mode. This size is calculated by 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. When 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 times the calculation of global bound size is triggered manually, not on a scheduled basis. |