10046 跟蹤的trace檔案相關解釋
Abbreviation in oracle Trace file
Here is a sample snippet from a trace file.
=====================
PARSING IN CURSOR #5 len=222 dep=1 uid=0 ct=3 lid=0 tim=1230889092568518 hv=3598296092 ad='402c848c' sqlid='1a8n1zgb7m90w'
select user#,password,datats#,tempts#,type#,defrole,resource$, ptime,exptime, ltime, astatus, lcount, decode(defschclass,NULL,'DEFAULT_CONSUMER_GROUP',defschclass),spare1,spare4,ext_username,spare2 from user$ where name=:1
END OF STMT
PARSE #5:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=4,plh=1457651150,tim=1230889092568518
EXEC #5:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=4,plh=1457651150,tim=1230889092568518
FETCH #5:c=0,e=0,p=0,cr=2,cu=0,mis=0,r=1,dep=1,og=4,plh=1457651150,tim=1230889092568518
STAT #5 id=1 cnt=1 pid=0 pos=1 bj=22 p='TABLE ACCESS BY INDEX ROWID USER$ (cr=2 pr=0 pw=0 time=0 us)'
STAT #5 id=2 cnt=1 pid=1 pos=1 bj=46 p='INDEX UNIQUE SCAN I_USER1 (cr=1 pr=0 pw=0 time=0 us)'
CLOSE #5:c=0,e=0,dep=1,type=3,tim=1230889092568518
=====================
Parsing in cursor
len=the length of the cursor.
dep=recursive depth of cursor(0-parent,>0-child)
uid=user id
oct=oracle command type no OCI
lid=user id owning the statement e.g. package(libary user id)
tim=the time the parse began
hv=hash valus
ad=sql address of cursor
sqlid=sql id of cursor
END OF STMT=indicate the end of sql STateMenT
c=cpu time
e=elapsed time
p=number of database blocks read (physical)
cr=number of consistent mode blocks read(logical)
cu=number of current mode blocks read(logical)
mis=number of library cache misses
r=number of rows returned
dep=recursive depth of cursor
og=optimizer goal (1=all_rows, 2=first_rows, 3=rule and 4=choose)
plh=plan hash value
tim=
cr=BG(Backgroud) Consistent Read mode
pr=OS Buffer Gets
pw=OS Write Calls
=====================
WAIT #5: nam='rdbms ipc reply' ela= 873 from_process=9 timeout=2147483647 p3=0 obj#=64143 tim=1230889212565389
WAIT #5: nam='rdbms ipc reply' ela= 820 from_process=5 timeout=2147483647 p3=0 obj#=64143 tim=1230889212566547
XCTEND rlbk=0, rd_only=1, tim=1230889212602618
=====================
nam=event name
ela=elapsed time
next three values after ela are indicate the P1, P2 and P3 variables for each specific event.
XCTEND=Transaction Commit END
rlbk True(1) if and only if the transaction was rolled back.
rd_only True(1) if and only if the transaction changed no data in the database
References:
1.Activating/deactivating trace
2.Interpreting Raw SQL_TRACE and DBMS_SUPPORT.START_TRACE output, Metalink Note 39817.1
3.Trace Analyzer TRCANLZR - Interpreting Raw SQL Traces with Binds and/or Waits generated by EVENT 10046 Metalink Note 224270.1
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/35489/viewspace-677023/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 跟蹤 sql 的trace檔案SQL
- Oracle跟蹤檔案trace檔案Oracle
- 跟蹤SQL - SQL Trace 及 10046 事件SQL事件
- 跟蹤session 與 trace檔案分析Session
- 跟蹤SESSION 與 trace 檔案解析Session
- ORACLE 10046 設定跟蹤事件後無跟蹤檔案Oracle事件
- ORACLE 跟蹤檔案詳細解釋Oracle
- 使用10046 event trace跟蹤全表掃描操作
- truncate、recreate後臺程式跟蹤檔案(trace file)
- 【最佳化】10046事件之生成跟蹤檔案事件
- 【最佳化】SQL_TRACE之生成跟蹤檔案SQL
- SQL 的跟蹤方法traceSQL
- 【TRACE】如果通過10046跟蹤資料庫效能問題資料庫
- 檔案-跟蹤檔案
- 【TRACE】Oracle跟蹤事件Oracle事件
- Oracle 10046跟蹤的使用Oracle
- ass109.awk 分析Oracle 的跟蹤檔案(trace file)Oracle
- sql_trace跟蹤檔案中名詞簡寫說明SQL
- 利用10046事件收集SQL的trace檔案事件SQL
- 控制檔案的跟蹤檔案全文
- [zt] oracle跟蹤檔案與跟蹤事件Oracle事件
- oracle跟蹤檔案與跟蹤事件(zt)Oracle事件
- oracle跟蹤檔案和跟蹤事件(zt)Oracle事件
- 怎樣收集10046跟蹤檔案來診斷效能問題
- Oracle跟蹤檔案Oracle
- 請教關於利用跟蹤檔案重建控制檔案
- 10046 跟蹤其他會話會話
- 路由跟蹤工具0trace路由
- 用oracle trace 來跟蹤sessionOracleSession
- sql_trace跟蹤工具(轉)SQL
- 解析listener跟蹤檔案
- git 忽略跟蹤檔案Git
- 尋找跟蹤檔案
- /etc/shadow檔案相關欄位的解釋
- 10046事件跟蹤會話sql事件會話SQL
- oracle sql跟蹤 event 10046 - 轉OracleSQL
- 使用10046跟蹤sql語句SQL
- git列出跟蹤的檔案列表Git