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/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 【TRACE】如果通過10046跟蹤資料庫效能問題資料庫
- Oracle 10046 SQL TRACEOracleSQL
- /etc/shadow檔案相關欄位的解釋
- sp_trace_setfilter sqlserver篩選跟蹤或跟蹤過濾FilterSQLServer
- git列出跟蹤的檔案列表Git
- [20200818]12c 10046跟蹤時間戳.txt時間戳
- Golang 大殺器之跟蹤剖析 traceGolang
- 單個SQL語句的10046 traceSQL
- Git跟蹤與提交檔案Git
- .gitignore忽略跟蹤指定檔案Git
- CVPR 2018 目標跟蹤相關論文
- ABAP的許可權檢查跟蹤(Authorization trace)工具
- git刪除未跟蹤檔案Git
- git clean清除未跟蹤檔案Git
- 如何在 Git 中取消檔案的跟蹤Git
- [20200818]12c 10046跟蹤時間戳2.txt時間戳
- Golang 效能測試 (3) 跟蹤刨析 golang traceGolang
- 轉:使用 Tkprof 分析 ORACLE 跟蹤檔案Oracle
- git列出所有已經跟蹤檔案Git
- Oracle執行語句跟蹤 使用sql trace實現語句追蹤OracleSQL
- sql_trace相關指令碼SQL指令碼
- 使用dbms_monitor.session_trace_enable跟蹤一個會話Session會話
- Linux檔案相關命令詳解(一)Linux
- [20201118]18c 10046跟蹤時間戳3(虛擬機器).txt時間戳虛擬機
- 【TRACE】如何設定或動態跟蹤Oracle net偵聽器Oracle
- SAP CRM One Order跟蹤和日誌工具CRMD_TRACE_SET
- [20211227]抽取跟蹤檔案中的繫結變數值.txt變數
- 10046 tracefile註釋
- 妙用 Intellij IDEA 建立臨時檔案,Git 跟蹤不到的那種IntelliJIdeaGit
- 從10046 trace 的trca報告中總結的時間模型示例模型
- 【LOG】Oracle資料庫清理日誌、跟蹤檔案利器Oracle資料庫
- Windows下用命令列工具ADRCI跟蹤日誌檔案Windows命令列
- [20191221]12c查詢跟蹤檔案內容.txt
- Linux檔案管理相關命令Linux
- 實驗七 檔案相關
- spring boot配置檔案相關Spring Boot
- git將當前目錄下所有檔案納入跟蹤Git
- git 刪除已經新增到git跟蹤的檔案或資料夾Git
- linux使用者相關檔案Linux