監控長時間執行的查詢(監控資料庫效能的SQL ) -- 轉
查詢v$session_longops動態效能檢視可以檢視執行時間大於6秒的查詢,如果想讓執行時間大於6秒的查詢被資料庫引擎收集,必須滿足以下條件:1 引數timed_statistics或sql_trace為true
2 涉及的物件(表或索引)必須被分析(analyze或dbms_stats)
監控資料庫效能的SQL
[Ref: http://xzh2000.itpub.net/post/96/102574 ]
在v$session_longops檢視中,sofar欄位表示已經掃描的塊數,totalwork表示總得需要掃描的塊數,所以我們即可以對正在執行的長查詢進行監控,比如在索引建立時,檢視索引建立的進度,也可以檢視系統中以往的長查詢。。。
[@more@]col opname format a32
col target_desc format a32
col perwork format a12
set lines 131
select sid,OPNAME,TARGET_DESC,sofar,TOTALWORK,trunc(sofar/totalwork*100,2)||'%' as perwork
from v$session_longops where sofar!=totalwork;
set lines 121
set pages 999
col opname format a29
col target format a29
col target_desc format a12
col perwork format a12
col remain format 99
col start_time format a21
col sofar format 99999999
col totalwork format 99999999
col sql_text format a101
col bufgets format 99999999
select opname,target,to_char(start_time,'yy-mm-dd:hh24:mi:ss') start_time,elapsed_seconds elapsed,
executions execs,buffer_gets/decode(executions,0,1,executions) bufgets,module,sql_text
from v$session_longops sl,v$sqlarea sa
where sl.sql_hash_value = sa.hash_value and upper(substr(module,1,4)) <> 'RMAN' and substr(opname,1,4) <> 'RMAN'
and module <> 'SQL*Plus' and sl.start_time>trunc(sysdate)
order by start_time;
==========================================================
1. 監控事例的等待
select event,sum(decode(wait_Time,0,0,1)) "Prev",
sum(decode(wait_Time,0,1,0)) "Curr",count(*) "Tot"
from v$session_Wait
group by event order by 4;2. 回滾段的爭用情況
select name, waits, gets, waits/gets "Ratio"
from v$rollstat a, v$rollname b
where a.usn = b.usn;3. 監控表空間的 I/O 比例
select df.tablespace_name name,df.file_name "file",f.phyrds pyr,
f.phyblkrd pbr,f.phywrts pyw, f.phyblkwrt pbw
from v$filestat f, dba_data_files df
where f.file# = df.file_id
order by df.tablespace_name;4. 監控檔案系統的 I/O 比例
select substr(a.file#,1,2) "#", substr(a.name,1,30) "Name",
a.status, a.bytes, b.phyrds, b.phywrts
from v$datafile a, v$filestat b
where a.file# = b.file#;5.在某個使用者下找所有的索引
select user_indexes.table_name, user_indexes.index_name,uniqueness, column_name
from user_ind_columns, user_indexes
where user_ind_columns.index_name = user_indexes.index_name
and user_ind_columns.table_name = user_indexes.table_name
order by user_indexes.table_type, user_indexes.table_name,
user_indexes.index_name, column_position;6. 監控 SGA 的命中率
select a.value + b.value "logical_reads", c.value "phys_reads",
round(100 * ((a.value+b.value)-c.value) / (a.value+b.value)) "BUFFER HIT RATIO"
from v$sysstat a, v$sysstat b, v$sysstat c
where a.statistic# = 38 and b.statistic# = 39
and c.statistic# = 40;7. 監控 SGA 中字典緩衝區的命中率
select parameter, gets,Getmisses , getmisses/(gets+getmisses)*100 "miss ratio",
(1-(sum(getmisses)/ (sum(gets)+sum(getmisses))))*100 "Hit ratio"
from v$rowcache
where gets+getmisses <>0
group by parameter, gets, getmisses;8. 監控 SGA 中共享快取區的命中率,應該小於1%
select sum(pins) "Total Pins", sum(reloads) "Total Reloads",
sum(reloads)/sum(pins) *100 libcache
from v$librarycache;select sum(pinhits-reloads)/sum(pins) "hit radio",sum(reloads)/sum(pins) "reload percent"
from v$librarycache;9. 顯示所有資料庫物件的類別和大小
select count(name) num_instances ,type ,sum(source_size) source_size ,
sum(parsed_size) parsed_size ,sum(code_size) code_size ,sum(error_size) error_size,
sum(source_size) +sum(parsed_size) +sum(code_size) +sum(error_size) size_required
from dba_object_size
group by type order by 2;10. 監控 SGA 中重做日誌快取區的命中率,應該小於1%
SELECT name, gets, misses, immediate_gets, immediate_misses,
Decode(gets,0,0,misses/gets*100) ratio1,
Decode(immediate_gets+immediate_misses,0,0,
immediate_misses/(immediate_gets+immediate_misses)*100) ratio2
FROM v$latch WHERE name IN ('redo allocation', 'redo copy');11. 監控記憶體和硬碟的排序比率,最好使它小於 .10,增加 sort_area_size
SELECT name, value FROM v$sysstat WHERE name IN ('sorts (memory)', 'sorts (disk)');
12. 監控當前資料庫誰在執行什麼SQL語句
SELECT osuser, username, sql_text from v$session a, v$sqltext b
where a.sql_address =b.address order by address, piece;13. 監控字典緩衝區
SELECT (SUM(PINS - RELOADS)) / SUM(PINS) "LIB CACHE" FROM V$LIBRARYCACHE;
SELECT (SUM(GETS - GETMISSES - USAGE - FIXED)) / SUM(GETS) "ROW CACHE" FROM V$ROWCACHE;
SELECT SUM(PINS) "EXECUTIONS", SUM(RELOADS) "CACHE MISSES WHILE EXECUTING" FROM V$LIBRARYCACHE;後者除以前者,此比率小於1%,接近0%為好。
SELECT SUM(GETS) "DICTIONARY GETS",SUM(GETMISSES) "DICTIONARY CACHE GET MISSES"
FROM V$ROWCACHE14. 找ORACLE字符集
select * from sys.props$ where name='NLS_CHARACTERSET';
15. 監控 MTS
select busy/(busy+idle) "shared servers busy" from v$dispatcher;
此值大於0.5時,引數需加大
select sum(wait)/sum(totalq) "dispatcher waits" from v$queue where type='dispatcher';
select count(*) from v$dispatcher;
select servers_highwater from v$mts;servers_highwater接近mts_max_servers時,引數需加大
16. 碎片程度
select tablespace_name,count(tablespace_name) from dba_free_space group by tablespace_name
having count(tablespace_name)>10;alter tablespace name coalesce;
alter table name deallocate unused;create or replace view ts_blocks_v as
select tablespace_name,block_id,bytes,blocks,'free space' segment_name from dba_free_space
union all
select tablespace_name,block_id,bytes,blocks,segment_name from dba_extents;select * from ts_blocks_v;
select tablespace_name,sum(bytes),max(bytes),count(block_id) from dba_free_space
group by tablespace_name;檢視碎片程度高的表
SELECT segment_name table_name , COUNT(*) extents
FROM dba_segments WHERE owner NOT IN ('SYS', 'SYSTEM') GROUP BY segment_name
HAVING COUNT(*) = (SELECT MAX( COUNT(*) ) FROM dba_segments GROUP BY segment_name);17. 表、索引的儲存情況檢查
select segment_name,sum(bytes),count(*) ext_quan from dba_extents where
tablespace_name='&tablespace_name' and segment_type='TABLE' group by tablespace_name,segment_name;select segment_name,count(*) from dba_extents where segment_type='INDEX' and owner='&owner'
group by segment_name;18、找使用CPU多的使用者session
12是cpu used by this session
select a.sid,spid,status,substr(a.program,1,40) prog,a.terminal,osuser,value/60/100 value
from v$session a,v$process b,v$sesstat c
where c.statistic#=12 and c.sid=a.sid and a.paddr=b.addr order by value desc;轉自:http://xsb.itpub.net/post/419/105941
-----------
檢視等待事件
--v$session_wait檢視中的p1、p2、p3表示等待事件的具體含義,如果Wait Event是db file scattered read,那麼p1=file_id/p2=block_id/p3=blocks,然後透過dba_extents即可
確定出熱點物件.
--如果是latch free的話,那麼p2為閂鎖號,它指向v$latch.
--求等待事件及其對應的latch
col event format a32;
col name format a32;
select sid,event,p1 as "p1 as file_id", p2 as "p2 as block_id/latch", p3 as "p3 as blocks",l.name
from v$session_wait sw,v$latch l
where event not like '%SQL%' and event not like '%rdbms%' and event not like '%mon%' and sw.p2 = l.latch#(+);
--求等待事件及其熱點物件
col owner format a18;
col segment_name format a32;
col segment_type format a32;
select owner, segment_name, segment_type from dba_extents
where file_id = &file_id and &block_id between block_id and block_id + &blocks - 1;
--綜合以上兩條SQL,同時顯示latch及熱點物件(速度較慢)
select sw.sid, event, l.name, de.segment_name from v$session_wait sw, v$latch l, dba_extents de
where event not like '%SQL%' and event not like '%rdbms%' and event not like '%mon%'
and sw.p2 = l.latch#(+) and sw.p1 = de.file_id(+) and p2 between de.block_id and de.block_id + de.blocks - 1;
--如果是非空閒等待事件,透過等待會話的SID可以求出該會話在執行的SQL
select sql_text from v$sqltext_with_newlines st, v$session se
where st.address = se.sql_address and st.hash_value = se.sql_hash_value and se.sid = &wait_sid order by piece;
----
發表於: 2004.11.22 11:06
分類: Performance Tuning
出處: http://smartcobra.itpub.net/post/487/6179
---------------------------------------------------------------
當我們對資料庫的效能進行調整時,一個最重要的參考指標就是系統等待事件。$system_event,v$session_event,v$session_wait這三個檢視裡記錄的就是系統級和session級的等待事件,透過查詢這些檢視你可以發現資料庫的一些操作到底在等待什麼?是磁碟I/O,緩衝區忙,還是插鎖等等。
透過如下sql你可以查詢你的每個應用程式到底在等待什麼,從而針對這些資訊對資料庫的效能進行調整。
Select s.username,s.program,s.status,se.event,se.total_waits,se.total_timeouts,se.time_waited,se.average_wait from v$session s,v$session_event se
Where s.sid=se.sid
And se.event not like ‘SQl*Net%’
And s.status = ‘ACTIVE’
And s.username is not null;
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/789833/viewspace-1039973/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- oracle資料庫效能監控的SQL(轉)Oracle資料庫SQL
- 監控資料庫效能的SQL資料庫SQL
- JAMon監控SQL執行時間SQL
- 監控資料庫效能的SQL彙總資料庫SQL
- 正常執行時間監控
- 資料庫效能SQL監控指令碼資料庫SQL指令碼
- 資料庫效能監控資料庫
- 系統監控&JVM監控指標資料查詢JVM指標
- 【SQL】Oracle資料庫監控sql執行情況SQLOracle資料庫
- SQL Server資料庫監控SQLServer資料庫
- 監控寶SQL Server效能監控的功能和配置SQLServer
- 監控Oracle長時間執行的工作(v$session_longops)OracleSessionGo
- 監控 SQL Server 的執行狀況SQLServer
- oracle 長sql監控OracleSQL
- 監控oracle效能的一些常用查詢Oracle
- 【SQL監控】SQL完全監控的指令碼SQL指令碼
- oracle資料庫執行狀態監控SHELLOracle資料庫
- 資料庫監控資料庫
- Oracle 資料庫監控SQL語句Oracle資料庫SQL
- Dataguard從庫效能的監控
- 監控SQL Server的執行狀況(1)SQLServer
- 監控資料庫執行超過6s的操作資料庫
- MySQL監控-Datadog資料庫監控調研MySql資料庫
- 監控Oracle資料庫效能的指令碼段整理Oracle資料庫指令碼
- 如何監控ORACLE資料庫表的增長量Oracle資料庫
- 【SQL】Oracle資料庫SQL監控報告示例SQLOracle資料庫
- 資料庫效能監控瓶頸理論資料庫
- 一種對雲主機進行效能監控的監控系統及其監控方法
- 監控資料庫活動資料庫
- APM效能監控軟體的監控型別服務及監控流程型別
- 某次資料庫效能監控中發現的問題資料庫
- 分享自己做的一個指定程式以及執行緒長時間cpu監控的工具執行緒
- 基於Prometheus的資料庫監控Prometheus資料庫
- Oracle資料庫的監控內容Oracle資料庫
- [轉]監控Oracle資料庫的常用shell指令碼Oracle資料庫指令碼
- 監控Oracle資料庫的常用shell指令碼(轉)Oracle資料庫指令碼
- sqlserver資料庫系統效能監控步驟SQLServer資料庫
- Oracle常用監控SQL(轉)OracleSQL