查找bad sql的要领 查找运行体系里bad sql是一个迂腐的话题, 我们要按照本身的现实环境来说明。 毫不能教条的运用下面先容的这些要领。 行使这些SQL语句时,会对体系表发生分组操纵,虽然也增大了体系的负载。 提议各人在体系启动了一段时刻后,在三更负载较轻的时刻按时(譬喻:一个月)来查一查。必然要详细题目详细说明。 下面是我保藏的一些查找bad sql的要领: column sql_text format a80; -- 值得猜疑的SQL 来自http://www.ixora.com.au/ select substr(to_char(s.pct, '99.00'), 2) || '%' load, s.executions executes, p.sql_text from ( select address, disk_reads, executions, pct, rank() over (order by disk_reads desc) ranking from ( select address, disk_reads, executions, 100 * ratio_to_report(disk_reads) over () pct from sys.v_$sql where command_type != 47 ) where disk_reads > 50 * executions ) s, sys.v_$sqltext p where s.ranking <= 5 and p.address = s.address order by 1, s.address, p.piece / -- 逻辑读多的SQL select * from (select buffer_gets, sql_text from v$sqlarea where buffer_gets > 500000 order by buffer_gets desc) where rownum<=30; -- 执行次数多的SQL select sql_text,executions from (select sql_text,executions from v$sqlarea order by executions desc) where rownum<81; -- 读硬盘多的SQL select sql_text,disk_reads from (select sql_text,disk_reads from v$sqlarea order by disk_reads desc) where rownum<21; -- 排序多的SQL select sql_text,sorts from (select sql_text,sorts from v$sqlarea order by sorts desc) where rownum<21; --说明的次数太多,执行的次数太少,要用绑变量的要领来写sql set pagesize 600; set linesize 120; select substr(sql_text,1,80) "sql", count(*), sum(executions) "totexecs" from v$sqlarea where executions < 5 group by substr(sql_text,1,80) having count(*) > 30 order by 2; -- 游标的调查 set pages 300; select sum(a.value), b.name from v$sesstat a, v$statname b where a.statistic# = b.statistic# and b.name = 'opened cursors current' group by b.name; select count(0) from v$open_cursor; select user_name,sql_text,count(0) from v$open_cursor group by user_name,sql_text having count(0)>30; --查察当前用户&username执行的SQL select sql_text from v$sqltext_with_newlines where (hash_value,address) in (select sql_hash_value,sql_address from v$session where username='&username') order by address,piece; (编辑:湖南网)
【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容!
|