db file sequential read等待事件的一点研究
db file sequential read等待事件有3个参数：file＃，first block＃，和block数量。
这个等待事件有3个参数P1，P2，P3， 其中P1代表Oracle要读取的文件的绝对文件号， P2代表Oracle从这个文件中开始读取的起始数据块号， P3代表读取的BLOCK数量，通常这个值为1，表明是道单个BLOCK被读取。 SQL> select SESSION_ID,NAME,P1,P2,P3,WAIT_TIME,CURRENT_OBJ#,CURRENT_FILE#,CURRENT_BLOCK#
from v$active_session_history ash, v$event_name enm
where ash.event#=enm.event#
and SESSION_ID=39; 2 3 4 SESSION_ID NAME P1 P2 P3 WAIT_TIME CURRENT_OBJ# CURRENT_FILE# CURRENT_BLOCK#
---------- ------------------------------ ---------- ---------- ---------- ---------- ------------ ------------- --------------
39 db file sequential read 4 531505 1 0 77088 4 531505
39 db file sequential read 4 528344 1 0 77088 4 528344
39 db file sequential read 4 520464 1 0 77088 4 520464
39 db file sequential read 4 517219 1 0 77088 4 517219
39 db file sequential read 4 502844 1 0 77088 4 502844
39 db file sequential read 4 489070 1 0 77088 4 489070
39 db file sequential read 4 480568 1 0 77088 4 480568
39 db file sequential read 4 478611 1 0 77088 4 478611
39 db file sequential read 4 473972 1 0 77088 4 473972
39 db file sequential read 4 473407 1 0 77088 4 473407
39 db file sequential read 4 458534 1 0 77088 4 458534 SESSION_ID NAME P1 P2 P3 WAIT_TIME CURRENT_OBJ# CURRENT_FILE# CURRENT_BLOCK#
---------- ------------------------------ ---------- ---------- ---------- ---------- ------------ ------------- --------------
39 db file sequential read 4 458186 1 0 77088 4 458186
39 db file sequential read 4 457625 1 0 77088 4 457625
39 db file sequential read 4 457150 1 0 77088 4 457150
39 db file sequential read 4 452548 1 0 77088 4 452548
39 direct path read 4 440464 8 0 78043 4 440424
39 direct path read 4 430640 8 0 78043 4 430632
39 direct path read 4 425312 8 0 78043 4 425304
39 direct path read 4 421408 8 0 78043 4 421400
39 direct path read 4 416384 8 0 78043 4 416376
39 direct path read 4 410928 8 0 78043 4 410920
39 direct path read 4 406240 8 0 78043 4 406232 SESSION_ID NAME P1 P2 P3 WAIT_TIME CURRENT_OBJ# CURRENT_FILE# CURRENT_BLOCK#
---------- ------------------------------ ---------- ---------- ---------- ---------- ------------ ------------- --------------
39 direct path read 4 404944 8 0 78043 4 404936
39 direct path read 4 399648 8 0 78043 4 399640
39 direct path read 4 394544 8 0 78043 4 394536
39 direct path read 4 389344 8 0 78043 4 389336
39 direct path read 4 383936 8 0 78043 4 383928
39 direct path read 4 379280 8 0 78043 4 379272
39 direct path read 4 374288 8 0 78043 4 374280
39 direct path read 4 369504 8 0 78043 4 369496
39 direct path read 4 364144 8 0 78043 4 364136
39 direct path read 4 359120 8 0 78043 4 359112
39 direct path read 4 354192 8 0 78043 4 354184 SESSION_ID NAME P1 P2 P3 WAIT_TIME CURRENT_OBJ# CURRENT_FILE# CURRENT_BLOCK#
---------- ------------------------------ ---------- ---------- ---------- ---------- ------------ ------------- --------------
39 direct path read 4 350192 8 0 78043 4 350184
39 direct path read 4 346832 8 0 78043 4 346824
39 direct path read 4 341936 8 0 78043 4 341928
39 direct path read 4 337088 8 0 78043 4 337080
39 direct path read 4 331632 8 0 78043 4 331624
39 direct path read 4 327056 8 0 78043 4 327048
39 direct path read 4 321984 8 0 78043 4 321976
39 direct path read 4 316784 8 0 78043 4 316776
39 direct path read 4 311680 8 0 78043 4 311672
39 direct path read 4 306448 8 0 78043 4 306440
39 direct path read 4 301200 8 0 78043 4 301192 SESSION_ID NAME P1 P2 P3 WAIT_TIME CURRENT_OBJ# CURRENT_FILE# CURRENT_BLOCK#
---------- ------------------------------ ---------- ---------- ---------- ---------- ------------ ------------- --------------
39 direct path read 4 295688 8 0 78043 4 295680
39 direct path read 4 290600 8 0 78043 4 290592
39 direct path read 4 286744 8 0 78043 4 286736
39 direct path read 4 281464 8 0 78043 4 281456
39 direct path read 4 276136 8 0 78043 4 276128
39 direct path read 4 271064 8 0 78043 4 271056
39 direct path read 4 266136 8 0 78043 4 266128
39 direct path read 4 261160 8 0 78043 4 261152
39 direct path read 4 256200 8 0 78043 4 256192
39 direct path read 4 255000 8 0 78043 4 254992
39 direct path read 4 254824 8 0 78043 4 254816 发现很多都是 db file sequential read等待事件 SQL> select owner,object_name,object_type from dba_objects where object_id=77088; OWNER OBJECT_NAM OBJECT_TYPE
---------- ---------- -------------------
SCOTT T1 TABLE BLOCK_ID: extent的起始块 BLOCKS:extent块的数量 SQL> select owner,segment_name,segment_type from dba_extents
where file_id = 4 and 531505 between block_id and block_id+blocks-1; 2 OWNER SEGMENT_NA SEGMENT_TYPE
---------- ---------- ------------------
SCOTT T1 TABLE 这里是回表造成的单块读 模拟下索引上的单块读,模拟index full scan SQL_ID 0r8t4zj3urrnp, child number 0
-------------------------------------
select id from t1 where t1.id is not null order by id Plan hash value: 2463307338 ----------------------------------------------------------------------------
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
----------------------------------------------------------------------------
| 0 | SELECT STATEMENT | | | | 42364 (100)| |
|* 1 | INDEX FULL SCAN | ID_IDX1 | 20M| 248M| 42364 (1)| 00:08:29 |
---------------------------------------------------------------------------- Predicate Information (identified by operation id):
--------------------------------------------------- 1 - filter("T1"."ID" IS NOT NULL) Note
-----
- dynamic sampling used for this statement (level=2) SQL> col name format a30
SQL> select SESSION_ID,NAME,P1,P2,P3,WAIT_TIME,CURRENT_OBJ#,CURRENT_FILE#,CURRENT_BLOCK#
from v$active_session_history ash, v$event_name enm
where ash.event#=enm.event#
and SESSION_ID=24; 2 3 4 SESSION_ID NAME P1 P2 P3 WAIT_TIME CURRENT_OBJ# CURRENT_FILE# CURRENT_BLOCK#
---------- ------------------------------ ---------- ---------- ---------- ---------- ------------ ------------- --------------
24 db file sequential read 4 589800 1 0 78139 4 589800
24 db file sequential read 4 483506 1 0 77088 4 483506
24 db file sequential read 4 447172 1 0 77088 4 447172
24 db file sequential read 4 469775 1 0 77088 4 469775
24 db file sequential read 4 458597 1 0 77088 4 458597
24 db file scattered read 4 446041 7 0 77088 4 446044
24 db file scattered read 4 525865 8 0 77088 4 8714
24 db file sequential read 4 8714 1 0 -1 4 8714
24 db file sequential read 1 64155 1 0 40 1 64155
24 db file sequential read 1 11540 1 0 40 1 11540
24 db file sequential read 1 19442 1 0 62 1 19442 SESSION_ID NAME P1 P2 P3 WAIT_TIME CURRENT_OBJ# CURRENT_FILE# CURRENT_BLOCK#
---------- ------------------------------ ---------- ---------- ---------- ---------- ------------ ------------- --------------
24 db file scattered read 1 46040 8 0 68 1 46040
24 db file sequential read 1 172 1 0 -1 0 0
24 db file sequential read 1 21910 1 0 -1 0 0
24 db file scattered read 1 83984 8 0 -1 0 0
24 db file sequential read 1 64354 1 0 -1 0 0
24 db file sequential read 1 64335 1 0 -1 0 0
24 db file scattered read 1 70152 3 0 -1 0 0
24 db file scattered read 1 55196 5 0 -1 0 0
24 db file scattered read 1 5376 8 0 -1 0 0
24 db file sequential read 1 2867 1 0 -1 0 0 21 rows selected. select owner,segment_name,segment_type from dba_extents
where file_id = 4 and 589800 between block_id and block_id+blocks-1; SQL> 2 OWNER SEGMENT_NAME SEGMENT_TYPE
------------------------------ --------------------------------------------------------------------------------- ------------------
SCOTT ID_IDX1 INDEXdb file sequential read等待事件的一点研究的更多相关文章
- oracle之 db file sequential read等待事件优化思想
为什么db file sequential read事件在full table scan操作中显现,为什么在多块读中为什么会有单块读存在 ? extent的大小 :当扩展区中的最后一组块仅是1个块,o ...
- 何时会发生db file sequential read等待事件？
很多网友对系统内频繁发生的db file sequential read等待事件存有疑问,那么到底在那些场景中会触发该单块读等待事件呢? 在我之前写的一篇博文<SQL调优:Clustering ...
- db file sequential read等待事件 --转载
db file sequential read db file sequential read等待事件有3个参数:file#,first block#,和block数量.在10g中,这等待事件受到用户 ...
- db file scattered read 等待事件
db file scattered read 等待事件: 我们经常会见到db file scattered read 等待事件,在生产环境中,这个等待事件可能更为常见.这个事件表明用户进程正在读数据 ...
- [20180316]理解db file parallel read等待事件.txt
[20180316]理解db file parallel read等待事件.txt --//一直对db file parallel read等待事件不理解,因为在实际系统中很少遇到这样的等待事件. S ...
- control file sequential read 等待事件
可能的原因 control file sequential read Reading from the control file. This happens in many cases. For ex ...
- Oracle 等待事件 db file sequential read
db file sequential read-数据文件顺序读取 等待事件: "db file sequential read" Reference Note (文档 ID 345 ...
- 全表扫描引发的db file sequential read
今天我要做一个SQL调优,监控该SQL, 利用ASH 监控 该SQL是在sid=4848 上面跑的 db file sequential read等待事件有3个参数:file#,first block ...
- 记一次insert因为db file sequential read影响性能导致性能原因的分析
通过详细的10046 trace发现,大量的io等待分布在以下数据文件上:Misses in library cache during parse: 0Elapsed times include wa ...
随机推荐
- TeleMCU视频会议之Android版本号WebRTC client支持
本文原创自 http://blog.csdn.net/voipmaker 转载注明出处. 最新版本号TeleMCU 添加了Android手机端WebRTC视频会议能力,Android手机安装Chro ...
- [转] 设计模式 -- Facade
PS:Façade模式注重简化接口,Adapter模式注重转换接口,Bridge模式注重分离接口(抽象)与其实现,Decorator模式注重稳定接口的前提下为对象扩展功能. Facade模式 Faca ...
- Quartz简单使用
官方的Quartz会提供例子的,例子看个前三四个感觉就够用了,主要就是起Timer的作用,但是比timer稳定,而且功能更全. UpdateClientTimer.task(ClearJob.clas ...
- 《Android群英传》读书笔记 (2) 第三章 控件架构与自定义控件详解 + 第四章 ListView使用技巧 + 第五章 Scroll分析
第三章 Android控件架构与自定义控件详解 1.Android控件架构下图是UI界面架构图,每个Activity都有一个Window对象,通常是由PhoneWindow类来实现的.PhoneWin ...
- 10 条提升 Android 性能的建议
About the Speaker: Boris Farber 每个人都知道一个 App 的成功,更这个 App 的性能体验有着很密切的关系.但是如何让你的 App 拥有极致性能体验呢?在 Droid ...
- Gson解析json数据(转)
一. www.json.org这是JSON的官方网站. 首先,我,我们需要在code.google.com/p/google-gson/downloads/list下载JSON的jar包,解析后把gs ...
- iOS图片拉伸
常用的图片拉伸场景有:聊天页面的气泡,需要根据内容拉伸,但圆角拉伸后会变形,为避免圆角拉伸,可以指定拉伸区域.UIImage实体调用以下方法即可指定拉伸区域. - (UIImage *)stretch ...
- IOS 开发 【objective-c 基础1】
案例:读取本地硬盘上程序根目录下words.txt文件内容,显示每行的字符数. // // main.m // hello // // Created by swack on 15/11/27. // ...
- codevs1955光纤通信（并查集）
/* 第一眼以为就是个区间覆盖 然后敲完提交60分0.0 然而觉得自己的做法很对 以为数据错了 后来发现XXX他的牛棚是一圈(牛过得挺好的啊 还能赏湖...) 然后枚举断开的点 可惜n=750 p=1 ...
- asp.net上传文件并创建文件夹和删除文件
上传文件部分代码: /// <summary> /// 上传保存文件并返回文件的保存地址和文件名称 /// </summary> /// <param name=&quo ...