Oracle 视图 V$RSRC_CONS_GROUP_HISTORY 官方解释,作用,如何使用详细说明
本站中文解释
Oracle 视图V$RSRC_CONS_GROUP_HISTORY记录了资源组内所有員工的计算时间从而实现两个阶段的资源试点控制,这些信息用于计算参数和活动索引。
使用Oracle视图V$RSRC_CONS_GROUP_HISTORY可以:
1. 查询指定时间段内各资源组中计算时间的总和;
2. 查询員工在特定时间段内的计算任务及它们的进度;
3. 查看当前員工在特定资源组内的计算情况;
4. 根据員工的计算情况分析員工的工作效率;
5. 优化资源使用情况,通过管理资源组实现资源分配和调度;
6. 根据每一条计算任务的完成情况,评估资源的正确分配;
7. 根据资源组中计算任务的数量进行统计,以便对重要任务进行优先调度;
8. 向管理层报告每一资源组内所有員工计算任务的完成状况,改进资源使用率,提高资源利用率。
官方英文解释
V$RSRC_CONS_GROUP_HISTORY
displays a history of consumer group statistics for each entry in V$RSRC_PLAN_HISTORY
that has a non-NULL plan.
When the STATISTICS_LEVEL
is set to TYPICAL
or ALL
, this view contains information about CPU utilization and wait times even when no Resource Manager plan is set or when the Resource Manager plan does not monitor CPU or session resources.
A new window is created in V$RSRC_CON_GROUP_HISTORY
when a pluggable database (PDB) changes its resource plan. The plan windows inside a PDB are not impacted by a multitenant container database (CDB) resource plan change.
Since PDB plans can be set independently across different PDBs, V$RSRC_CON_GROUP_HISTORY
will not cover the same time period across different PDBs. Therefore, this view is not useful for comparing statistics across different PDBs.
Column | Datatype | Description |
---|---|---|
|
|
A sequential counter that uniquely describes the |
|
|
Consumer group object ID (a unique number, consistent across database shutdowns and startups) |
|
|
Name of the consumer group |
|
|
Cumulative number of requests that were executed in the consumer group |
|
|
Cumulative amount of time that sessions waited for CPU on the resmgr: cpu quantum wait event because of resource management (in milliseconds). This does not include waits due to latch or enqueue contention, I/O waits, and so on. When CPU resources are not being actively managed, this value is set to zero. |
|
|
Cumulative number of times all sessions in the consumer group had to wait for CPU on the resmgr: cpu quantum wait event because of resource management. This does not include waits due to latch or enqueue contention, I/O waits, and so on. When CPU resources are not being actively managed, this value is set to zero. |
|
|
Cumulative amount of CPU time consumed by all sessions in the consumer group (in milliseconds) |
|
|
Cumulative number of times that sessions in the consumer group had to yield CPU to other sessions because of quantum expiration. When CPU resources are not being actively managed, this value is set to zero. |
|
|
Percentage of CPU decisions for which the consumer group was present. When CPU resources are not being actively managed, this value is set to zero. |
|
|
Percentage of the CPU decisions for which the consumer group was present and was the only consumer group present. When CPU resources are not being actively managed, this value is set to zero. |
|
|
Percentage of the CPU decisions that the consumer group won. When CPU resources are not being actively managed, this value is set to zero. |
|
|
Number of times that sessions in the consumer group were queued because the consumer group reached its active session limit |
|
|
Number of times that queries in the consumer group were canceled because the consumer group reached its |
|
|
Number of switches into the consumer group because of the Resource Manager plan’s |
|
|
Number of switches out of the consumer group because of the Resource Manager plan’s |
|
|
Number of switches into the consumer group because of the Resource Manager plan’s |
|
|
Number of switches out of the consumer group because of the Resource Manager plan’s |
|
|
Number of switches into the consumer group because of the Resource Manager plan’s |
|
|
Number of switches out of the consumer group because of the Resource Manager plan’s |
|
|
Number of switches into the consumer group because of the Resource Manager plan’s |
|
|
Number of switches out of the consumer group because of the Resource Manager plan’s |
|
|
Number of switches into the consumer group because of the Resource Manager plan’s |
|
|
Number of switches out of the consumer group because of the Resource Manager plan’s |
|
|
Number of times that SQL queries running in the consumer group were aborted because they exceeded one of the Resource Manager plan’s |
|
|
Number of times that sessions running in the consumer group were terminated because they exceeded one of the Resource Manager plan’s |
|
|
Number of times that sessions in the consumer group were killed because they were idle for too long (reached |
|
|
Number of times that sessions in the consumer group were killed because they were idle too long (reached |
|
|
Total amount of time that sessions in the consumer group have spent in the QUEUED state because of the active session limit (in milliseconds) |
|
|
Number of times that requests from sessions in the consumer group timed out because they were queued for too long (reached |
|
|
Cumulative I/O wait time (in milliseconds) |
|
|
Total number of wait requests |
|
|
Number of single block megabytes read |
|
|
Number of single block megabytes written |
|
|
Number of multiblock megabytes read |
|
|
Number of multiblock megabytes written |
|
|
Number of single block read requests |
|
|
Number of single block write requests |
|
|
Number of multiblock read requests |
|
|
Number of multiblock write requests |
|
|
Total number of completed parallel statements in the consumer group |
|
|
Total number of parallel servers used by completed parallel statements in the consumer group |
|
|
Number of times that sessions in the consumer group were queued when trying to run parallel statements |
|
|
Cumulative sum of the parallel active times for all completed parallel statements in the consumer group (in milliseconds) |
|
|
Total amount of time that sessions in the consumer group were queued when trying to run parallel statements (in milliseconds) |
|
|
Number of times that parallel statements from sessions in the consumer group timed out because their queue time exceeded the Resource Manager plan’s |
|
|
Number of times that sessions in the consumer group were killed because their untunable PGA usage exceeded the |
|
|
The ID of the container to which the data pertains. Possible values include:
|
See Also:
-
“V$RSRC_PDB_HISTORY”
-
“V$RSRC_PLAN_HISTORY”
-
“STATISTICS_LEVEL”