Oracle 视图 V$RSRC_PDB_HISTORY 官方解释，作用，如何使用详细说明
本站中文解释
Oracle视图V$RSRC_PDB_HISTORY是一个数据字典视图，它可以用来查看由于资源限制影响而从现存的容器中驱逐的Pluggable Databases (PDBs)的历史信息。
V$RSRC_PDB_HISTORY视图拥有8列，包括：
RSRC_PDB_HISTORY_ID：PDB驱逐的唯一的ID；
CON_ID：PDB所在的容器的ID；
PDB_ID：PDB的ID；
PDB_NAME：PDB的名称；
START_TIMESTAMP：PDB驱逐开始的时间戳；
END_TIMESTAMP：PDB驱逐结束的时间戳；
RSRC_LIMIT：触发PDB驱逐的资源限制；
ERROR_MSG：驱逐导致的错误消息。
V$RSRC_PDB_HISTORY视图通过管理员查询历史资源限制侵入的PDB的时间起止，是一个非常有用的数据字典视图。
使用V$RSRC_PDB_HISTORY视图：
— 1. 查询Oracle中当前被暂时驱逐的PDB
SELECT pdb_name
FROM v$rsrc_pdb_history
WHERE end_timestamp IS NULL;
— 2. 查询指定日期范围内被驱逐暂时驱逐的PDB
SELECT pdb_name, start_timestamp
FROM v$rsrc_pdb_history
WHERE start_timestamp > = ‘&start_date’
AND start_timestamp
官方英文解释
V$RSRC_PDB_HISTORY displays a history of consumer group statistics for each entry in V$RSRC_PDB that has a non-NULL plan by pluggable database (PDB).
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_PDB_HISTORY when a multitenant container database (CDB) changes its resource plan. The plan windows for the CDB are not impacted by a PDB resource plan change.
V$RSRC_PDB_HISTORY covers the same time period for all PDBs. This view is specifically designed for comparing statistics across different PDBs.
Since V$RSRC_PDB_HISTORY does not contain information at the consumer group level, it is not useful for comparing consumer groups inside a PDB.
| Column | Datatype | Description |
|---|---|---|
|
|
|
A sequential counter that uniquely describes the |
|
|
|
PBD name |
|
|
|
Cumulative amount of time that sessions waited for CPU 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 number of times all sessions in the consumer group had to wait for CPU 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. |
|
|
|
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 |
|
|
|
The ID of the container to which the data pertains. Possible values include:
|
See Also:
“V$RSRC_CONS_GROUP_HISTORY”
