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 ...
随机推荐
- Monkeyrunner入门示例
准备工作1.安装Android SDK2.熟悉MonkeyRunner的API(http://article.yeeyan.org/view/37503/164523)3.一部Android手机或模拟 ...
- 细说Lucene源码(一)：索引文件锁机制
大家都知道,在多线程或多进程的环境中,对统一资源的访问需要特别小心,特别是在写资源时,如果不加锁,将会导致很多严重的后果,Lucene的索引也是如此,lucene对索引的读写分为IndexReader ...
- 使用Tcl脚本分配FPGA管脚
自己主动生成Tcl文件 Project -> Generate Tcl File for Project... 弹出例如以下对话框.设置脚本路径. 编辑引脚 使用set_location_ass ...
- [转] Java中的访问控制
可见/访问性 在同一类中 同一包中 不同包中 同一包子类中 不同包子类中 public yes yes yes yes yes protected yes yes no ...
- [转] Linux下查看文件和文件夹大小
当磁盘大小超过标准时会有报警提示,这时如果掌握df和du命令是非常明智的选择. df可以查看一级文件夹大小.使用比例.档案系统及其挂入点,但对文件却无能为力. du可以查看文件及文件夹的大小. ...
- TCP 连接的要点
概念 TIME_WAIT: socket 仍然有数据在内核中待发送直到发送成功或超时,此socket不能被内核删除,同时等待是否要重传Ack对端还已发过来的FIN Linger Time:socket ...
- 给iOS开发者的GCD用户手册
Grand Central Dispatch,或者GCD,是一个极其强大的工具.它给你一些底层的组件,像队列和信号量,让你可以通过一些有趣的方式来获得有用的多线程效果.可惜的是,这个基于C的API是一 ...
- .NET六大剑客：栈、堆、值类型、引用类型、装箱和拆箱
.NET六大剑客:栈.堆.值类型.引用类型.装箱和拆箱 一.“堆”,“栈”专区 这两个字我相信大家太熟悉了,甚至于米饭是什么?不知道...“堆”,“栈”是什么?哦,这个知道... 之前我也写过一篇堆栈 ...
- 使用Javascript限制文本框只允许输入数字
很多时候需要用到限制文本框的数字输入,试过许多方法,都不太理想,遂决定自己实现一个来玩玩.曾经使用过的方法通过onkeydown事件来控制只允许数字: <input onkeydown=&quo ...
- HTML5 Blob与ArrayBuffer、TypeArray和字符串String之间转换
1.将String字符串转换成Blob对象 //将字符串 转换成 Blob 对象 var blob = new Blob(["Hello World!"], { type: 'te ...