|
原帖由 anlinew 于 2010-8-5 15:39 发表 ![]()
在使用events来作为诊断依据是有时候可能会漏掉一些session
比如上面执行1分多钟的情况下该session的event始终被统计为容易被大家忽略的 SQL net 事件
10046的trace 虽然看上去全部等待的是 SQL*Net message from client ,其实这时间 SQL*Net message from client 的等待时间很短。
大部分还是cpu的等待。 EVENT的信息是上一步的等待
********************************************************************************
delete FROM test_filter_hash t1
where created < (select max(created) from test_filter_hash t2 where t2.object_id=t1.object_id
GROUP BY t2.object_id
)
call count cpu elapsed disk query current rows
------- ------ -------- ---------- ---------- ---------- ---------- ----------
Parse 1 0.00 0.00 0 0 0 0
Execute 1 29.72 29.16 0 1872451 0 0
Fetch 0 0.00 0.00 0 0 0 0
------- ------ -------- ---------- ---------- ---------- ---------- ----------
total 2 29.72 29.16 0 1872451 0 0
Misses in library cache during parse: 0
Optimizer mode: ALL_ROWS
Parsing user id: 150
Rows Row Source Operation
------- ---------------------------------------------------
0 DELETE TEST_FILTER_HASH (cr=1872451 pr=0 pw=0 time=29163167 us)
0 FILTER (cr=1872451 pr=0 pw=0 time=29163158 us)
10398 TABLE ACCESS FULL TEST_FILTER_HASH (cr=190 pr=0 pw=0 time=10485 us)
9852 SORT GROUP BY NOSORT (cr=1872261 pr=0 pw=0 time=29111090 us)
19704 TABLE ACCESS FULL TEST_FILTER_HASH (cr=1872261 pr=0 pw=0 time=29030998 us)
Elapsed times include waiting on following events:
lapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
SQL*Net message to client 1 0.00 0.00
SQL*Net message from client 1 0.08 0.08
******************************************************************************** |
|