V$STATNAME
显示
V$SESSTAT
和
V$SYSSTAT
表中的统计信息名称
This
view displays decoded statistic names for the statistics shown in
the
V$SESSTAT
and
V$SYSSTAT
tables.
On
some platforms, the
NAME
and
CLASS
columns
contain additional operating system-specific statistics.
Column
|
Datatype
|
Description
|
STATISTIC#
|
NUMBER
|
Statistic
number (
统计编号
)
Note:
Statistics
numbers are not guaranteed to remain constant from one release to
another. Therefore, you should rely on the statistics name rather
than its number in your applications.
|
NAME
|
VARCHAR2(64)
|
统计名
|
CLASS
|
NUMBER
|
A
number representing one or more statistics classes. The following
class numbers are additive:
|
STAT_ID
|
NUMBER
|
Identifier
of the statistic (
统计标识符
)
|
V$MYSTAT
显示当前
session
的统计信息
Column
|
Datatype
|
Description
|
SID
|
NUMBER
|
当前
session
ID
|
STATISTIC#
|
NUMBER
|
统计编号
|
VALUE
|
NUMBER
|
统计值
|
--
显示当前session
的统计信息
SELECT
'STAT...' || a.NAME NAME, b.VALUE
FROM
v$statname a, v$mystat b
WHERE
a.STATISTIC# = b.STATISTIC#
V$LATCH
显示总的以
latch
名称分组的
latch
统计信息,包括父
latch
与子
latch,
单独的父
latch
与子
latch
统计信息分别在
V$LATCH_PARENT
,
V$LATCH_CHILDREN
视图
V$LATCH
shows
aggregate latch statistics for both parent and child latches, grouped
by latch name. Individual parent and child latch statistics are
broken down in the views
V$LATCH_PARENT
and
V$LATCH_CHILDREN
.
Column
|
Datatype
|
Description
|
ADDR
|
RAW(4
| 8)
|
Address
of the latch object
|
LATCH#
|
NUMBER
|
Latch
number
|
LEVEL#
|
NUMBER
|
Latch
level
|
NAME
|
VARCHAR2(50)
|
Latch
name
|
HASH
|
NUMBER
|
Latch
hash
|
GETS
|
NUMBER
|
Number
of times the latch was requested in willing-to-wait mode
latch
被请求的次数
|
MISSES
|
NUMBER
|
Number
of times the latch was requested in willing-to-wait mode and the
requestor had to wait
|
SLEEPS
|
NUMBER
|
Number
of times a willing-to-wait latch request resulted in a session
sleeping while waiting for the latch
|
IMMEDIATE_GETS
|
NUMBER
|
Number
of times a latch was requested in no-wait mode
|
IMMEDIATE_MISSES
|
NUMBER
|
Number
of times a no-wait latch request did not succeed (that is,
missed)
|
WAITERS_WOKEN
|
NUMBER
|
This
column has been deprecated and is present only for compatibility
with previous releases of Oracle. No data is accumulated for this
column; it will always have a value of zero.
|
WAITS_HOLDING_LATCH
|
NUMBER
|
This
column has been deprecated and is present only for compatibility
with previous releases of Oracle. No data is accumulated for this
column; it will always have a value of zero.
|
SPIN_GETS
|
NUMBER
|
Willing-to-wait
latch requests which missed the first try but succeeded while
spinning
|
SLEEP[1
| 2 | 3]
|
NUMBER
|
These
columns have been deprecated and are present only for
compatibility with previous releases of Oracle. No data is
accumulated for these columns; they will always have a value of
zero. As a substitute for this column you can query the
appropriate rows of the
V$EVENT_HISTOGRAM
view
where the
EVENT
column
has a value of
latch
free
or
latch:%
.
|
SLEEP4
|
NUMBER
|
This
column has been deprecated and is present only for compatibility
with previous releases of Oracle. No data is accumulated for this
column; it will always have a value of zero. As a substitute for
this column you can query the appropriate rows of
the
V$EVENT_HISTOGRAM
view
where the
EVENT
column
has a value of
latch
free
or
latch:%
.
|
SLEEP[5
| 6 | 7 | 8 | 9 | 10 | 11]
|
NUMBER
|
These
columns have been deprecated and are present only for
compatibility with previous releases of Oracle. No data is
accumulated for these columns.
|
WAIT_TIME
|
NUMBER
|
Elapsed
time spent waiting for the latch (in microseconds)
|
$TIMER
This
view lists the elapsed time in hundredths of seconds. Time is
measured since the beginning of the epoch, which is operating system
specific, and wraps around to 0 again whenever the value overflows
four bytes (roughly 497 days).
Column
|
Datatype
|
Description
|
HSECS
|
NUMBER
|
Elapsed
time in hundredths of a second
|
DBMS_UTILITY
GET_TIME
Function
This
function determines the current time in 100th's of a second. This
subprogram is primarily used for determining elapsed time. The
subprogram is called twice – at the beginning and end of some
process – and then the first (earlier) number is subtracted from
the second (later) number to determine the time elapsed.
Syntax
DBMS_UTILITY.GET_TIME
RETURN
NUMBER;
Return
Values
Time
is the number of 100th's of a second from the point in time at which
the subprogram is invoked.
Usage
Notes
Numbers
are returned in the range -2147483648 to 2147483647 depending on
platform and machine, and your application must take the sign of the
number into account in determining the interval. For instance, in the
case of two negative numbers, application logic must allow that the
first (earlier) number will be larger than the second (later) number
which is closer to zero. By the same token, your application should
also allow that the first (earlier) number be negative and the second
(later) number be positive.
GET_CPU_TIME
Function
This
function returns the current CPU time in 100th's of a second. The
returned CPU time is the number of 100th's of a second from some
arbitrary epoch.
Syntax
DBMS_UTILITY.GET_CPU_TIME
RETURN
NUMBER;
Return
Values
Time
is the number of 100th's of a second from some arbitrary epoch.
分享到:
相关推荐
DB2数据库管理最佳实践主要关注的是数据库的日常运维,其中包括了收集统计信息、重组操作以及相关的维护工具。这里我们将深入探讨这些关键知识点。 1. **Runstats**:Runstats是DB2数据库管理系统中的一个重要工具...
在更新统计信息后,可以执行Rebind以更新相关对象的绑定: ```sql REBIND PACKAGE <包名> ``` 执行流程通常是先用Runstats收集统计信息,然后执行Reorg,接着再次收集统计信息,最后进行Rebind。在大型系统中,这...
接下来,根据实际情况调整相关的HA Manager配置参数,例如增加最大堆内存限制、调整垃圾回收策略等,以确保系统能够处理更大的对象。具体的调整方法可以根据官方文档或者实践经验来进行。 通过上述步骤的实施,不仅...
DB2目录存储了数据库对象的相关元数据,包括表、视图、索引等的信息。优化器在决定访问路径时会查询这些统计信息,因此保持目录的准确性和时效性至关重要。定期运行RUNSTATS可以帮助更新这些统计信息,以反映数据的...
DB2优化器的问题诊断对于高级数据库管理员和DB2使用者来说尤为重要,因为它能帮助他们分析访问计划,诊断查询性能问题,并从DB2的开发和支持团队中直接学习到相关知识。 在介绍DB2优化器和问题诊断方法时,我们首先...
可以通过查询`SYSCAT.TABLESPACES`视图来获取相关信息。 **字段含义:** - `TBSP_FREE_PAGES`:表示表空间中剩余的空闲页数。 - `KEEP`:表示保留的空间大小。 - `PER`:表示剩余空间百分比。 **更新频率:** 这些...
- RUNSTATS命令:运行统计的命令。 - OPTIMIZATION命令:优化相关的命令。 - VARIATIONALTECHNOLOGY命令:变分技术的命令。 - PROBABILISTIC Design命令:概率设计相关的命令。 - DISPLAY Program命令:显示程序的...
)测试检查类型错误-应该只找到与runstats模块有关的类型错误,其中没有类型提示: mypy simulateCribbageGames.py使用模拟从交易到手数计算的一只手: python simulateCribbageGames.py 有关其他模拟选项的帮助: ...
- **内容面板**:展示与选定对象相关的各种操作和配置选项。 #### 活动监视器 活动监视器提供了一个实时监控数据库活动的界面,它可以帮助数据库管理员了解当前正在运行的进程、查询和其他活动的状态。 #### 内存...
通过以上详细的命令介绍,我们可以了解到DB2数据库管理系统提供了丰富的工具和命令来管理数据库及其相关操作。这些命令不仅涵盖了基本的数据库管理功能,还涉及了数据备份恢复、性能优化等方面,是DB2管理员日常工作...
- **Runstats**:定期执行`RUNSTATS`,更新统计信息,使DB2能够更准确地评估查询代价,选择最优查询路径。 ### 索引优化 索引是加速数据检索的关键机制,合理设计和维护索引对于性能至关重要: - **多列索引**:...
### Itrenzheng IBM DB2 000-701 认证题库知识点解析 #### 一、概述 本篇文章将针对...它会显示有关表的物理存储结构的状态信息,如碎片率、空间利用率等,以便管理员决定是否需要执行重组织操作来优化性能。
- `list` 用于显示数据库对象或设置的相关信息。 - `get` 用于获取数据库参数的设置和状态。 9. **runstats** - `runstats` 运行统计分析,更新系统目录表中的信息,有助于优化查询性能。 10. **backup** 和 **...
### DB2基本命令详解 #### 一、启动与停止数据库 - **启动数据库**: `db2start` ...以上就是DB2中关于实例管理和常用DML操作的相关命令总结,这些命令可以帮助您更好地管理数据库环境,提高工作效率。
- **注意事项**: 删除数据库将永久删除所有与该数据库相关的数据和元数据。 - **示例**: `db2dropdb mydb` #### 5. 断开所有应用程序连接 - **命令**: `db2forceapplicationall` - **描述**: 强制断开所有连接到...
在本文中,我们重点关注如何使用 DB2look 重新创建优化器访问计划,以解决与查询性能和编译器相关的问题。 当遇到访问计划问题或性能下降时,DB2look 可以帮助分析和调试。例如,如果你在执行查询时发现优化器选择...
- **Runstats**:Runstats 是一种统计信息收集工具,可以帮助优化查询计划。 - **并行 LOAD 加快数据转入性能**:通过并行加载数据到分区表中,可以显著提高数据导入速度。 #### 七、总结 综上所述,DB2 的对数...