[20160902][轉載]跟蹤rman操作.txt
[20160902]跟蹤rman操作.txt
--轉載:跟蹤rman
--以前僅僅知道debug,沒有知道這麼細,做一個記錄,原連結裡面還有DGMGRL,EXPDP / IMPDP,SRVCTL,OPATCH,10046事件的跟蹤。
RMAN
RMAN is the Oracle utility used to backup and recover your databases. To enable tracing is RMAN, you have to switch rman is "debug" mode.
This mode can be enabled directly in rman:
[oracle@oel7 ~]$ rman target /
Recovery Manager: Release 12.1.0.2.0 - Production on Wed Feb 24 15:45:13 2016
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1413029491)
RMAN> debug on
RMAN-03036: Debugging set to level=9[MEDIUM], types=ALL
DBGSQL: TARGET> begin dbms_rcvman.setDebugOn; dbms_rcvman.dumpPkgState('Debug On'); end;
DBGSQL: sqlcode = 0
DBGRCVMAN: ENTERING dumpPkgState Debug On
.../...
Or (much better) it can be enabled with the debug option in the rman command, and by specifying a trace file :
[oracle@oel7 ~]$ rman target / debug trace=tracefile.trc
Recovery Manager: Release 12.1.0.2.0 - Production on Wed Feb 24 15:22:10 2016
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
RMAN-06005: connected to target database: ORCL (DBID=1413029491)
RMAN> disconnect
All the debug stuff is then located in your "tracefile.trc" file.
You can enable tracing on specific component in rman :
SQL: for tracing SQL queries generated by rman
RESTORE: for tracing restore operation only
RECOVER: for tracing recovery operation only
RESYNC: for tracing synchronization operation only
DUPLICATE: for tracing duplicate operation only
And for each or all of these component, you can set a verbosity level from 1 (lowest) to 10 (highest). 9 is the default
verbosity level. Sometimes, you can change the verbosity level without any change in your tracefile.
Here are some examples (point that many components can be traced at the same time):
[oracle@oel7 ~]$ rman target / debug recover level=10 trace=tracefile.trc
[oracle@oel7 ~]$ rman target / debug sql level=1 trace=tracefile.trc
RMAN> debug restore,sql level=10
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/267265/viewspace-2124380/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- oracle跟蹤事件(轉載)Oracle事件
- [20151111]跟蹤除錯rman.txt除錯
- 轉載 oracle 跟蹤檔案 和轉儲命令Oracle
- [20231025]跟蹤rename操作2.txt
- [20131122]跟蹤sql profile的操作.txtSQL
- Oracle 跟蹤事件【轉】Oracle事件
- sql_trace跟蹤工具(轉)SQL
- 揭祕ORACLE備份之----RMAN之四(塊跟蹤)Oracle
- 玩轉跟蹤(to owner session、other session)Session
- 專案計劃與跟蹤(轉)
- [20150527]跟蹤單個sql語句.txtSQL
- [zt] oracle跟蹤檔案與跟蹤事件Oracle事件
- oracle跟蹤檔案與跟蹤事件(zt)Oracle事件
- oracle跟蹤檔案和跟蹤事件(zt)Oracle事件
- 轉:使用 Tkprof 分析 ORACLE 跟蹤檔案Oracle
- oracle sql跟蹤 event 10046 - 轉OracleSQL
- oracle 跟蹤檔案和轉儲命令(轉摘)Oracle
- [20160720]檢視了解oracle跟蹤事件.txtOracle事件
- [20120723跟蹤檔案的定位.txt
- oracle11g有DBMS_MONITOR跟蹤TRUNCATE操作Oracle
- sqlnet跟蹤SQL
- ORACLE 跟蹤工具Oracle
- 如何跟蹤資訊流廣告轉化資料?
- 網路讀者的眼球跟蹤研究 (轉)
- [20190917]oracle跟蹤事件簡單寫法.txtOracle事件
- [20211013]閱讀ldd原始碼跟蹤.txt原始碼
- [20160830]清除日誌與跟蹤檔案.txt
- [20161130]11g跟蹤檔案位置.txt
- [20160704]從跟蹤檔案抽取sql語句.txtSQL
- [20140217]在toad使用跟蹤檔案.txt
- [20160902]簡單探究linux的free命令.txtLinux
- 利用sql_trace跟蹤一個指定會話的操作SQL會話
- 使用10046 event trace跟蹤全表掃描操作
- Oracle中如何跟蹤SQL或資料庫操作 [final]OracleSQL資料庫
- [20160816]使用oradebug跟蹤sql net.txtSQL
- 基於行跟蹤的ROWDEPENDENCIES實現資訊變化跟蹤
- 【Longkin】ASP.NET應用程式跟蹤---(一)跟蹤頁面ASP.NET
- 網路地址轉換(NAT)的報文跟蹤