rman target / debug trace
今天閒來無事,想看看rman的執行過程:
就使用如下命令:
rman target / debug trace=c:/rmanback.out
從rmanback.out獲取瞭如下資訊:
恢復管理器: Release 11.2.0.1.0 - Production on 星期二 6月 15 00:22:17 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Windows NT Version V6.1
CPU : 2 - type 8664, 2 Physical Cores
Process Affinity : 0x0x0000000000000000
Memory (Avail/Total): Ph:1934M/4026M, Ph+PgF:5317M/8050M
Starting with debugging set to level=9, types=ALL
CPU : 2 - type 8664, 2 Physical Cores
Process Affinity : 0x0x0000000000000000
Memory (Avail/Total): Ph:1934M/4026M, Ph+PgF:5317M/8050M
Starting with debugging set to level=9, types=ALL
DBGMISC: ENTERED krmksimronly [00:22:17.596]
DBGSQL: CHANNEL> alter session set events '19737 trace name context forever'
。。。。
DBGSQL: CHANNEL> select decode(archiver, 'FAILED', 1, 0) into :archstuck from v$instance
DBGSQL: CHANNEL> alter session set events '19737 trace name context off'
。。。。
DBGSQL: TARGET> select decode(open_mode, 'MOUNTED', 0, 'READ WRITE', 1, 'READ ONLY', 1, 'READ ONLY WITH APPLY', 1, 0) into :isdbopen from v$database
。。。。。。。
DBGSQL: TARGET> select decode(status, 'OPEN', 1, 0), decode(archiver, 'FAILED', 1, 0), decode(database_status, 'SUSPENDED', 1, 0) into :status, :archstuck, :dbsuspended from v$instance
。。。。。。。。
DBGSQL: TARGET> select decode(open_mode, 'READ WRITE', 1, 0) into :read_write from v$database
DBGSQL: TARGET> select value into :vcomp_txt from v$parameter where name = 'compatible'
。。。。。。。。。。。
等資訊
非常有意思,值得好好研究。
但是在生產系統不建議使用這些命令產生TRACE檔案。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/8183550/viewspace-665344/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- “rman target /” 和 “rman nocatalog target /” 區別
- "rman target /” 和"rman nocatalog target /”區別實踐
- rman: can't open target
- RMAN的"rman: can't open target"錯誤
- debug:am trace-ipc原始碼分析原始碼
- C#如何使用 Debug 和 Trace 類C#
- 【RMAN】RMAN-20001: target database not found in recoveryDatabase
- 【RMAN】RMAN-05001: auxiliary filename conflicts with the target databaseUXDatabase
- RMAN中的 debug調式命令
- RMAN-05541: no archived logs found in target databaseHiveDatabase
- rman duplicate target database RMAN-03002 RMAN-03015 RMAN-06136Database
- RMAN-20005: target database name is ambiguousDatabase
- RMAN備份、恢復實驗室 之 備份篇 【rman: can't open target】
- linux上“rman can't open target”問題解決Linux
- RMAN-20001: target database not found in recovery catalogDatabase
- 11g rman新特性 duplicate target database for standby from active databaseDatabase
- RMAN-05517: temporary file conflicts with file used by target database(zt)Database
- RMAN登陸及連線target資料庫的步驟方法資料庫
- RMAN DUPLICATE Without Connecting To Target DB For Both Disk & Tape_1375864.1
- 關於oracle 10G for suse 9 的rman: can't open targetOracle 10g
- [20161101]環境變數ORA_RMAN_SGA_TARGET變數
- Creation Of Rman Duplicate Without Target And Recovery Catalog Connec-1113713.1
- RMAN 11GR2 : DUPLICATE Without Target And Recovery Catalog Connection_874352.1
- memory_max_target,memory_target,pga_aggregate_target,sga_target
- memory_target、sga_target、pga_target的設定
- Hide RMAN Passwords when Connecting to a Target Database (Doc ID 183377.1)IDEDatabase
- oracle 10g rman duplicate target database for standby會自動新增臨時檔案Oracle 10gDatabase
- Openfiler配置ISCSI Target及FC Target
- RMAN-20002: target database already registered in recovery catalog 解決方法Database
- SQL TraceSQL
- trace errorstackError
- jQuery :targetjQuery
- 關於memory_max_target,memory_target,sga_max_size,sga_target
- 【例項】之memory_target、sga_target,pga_aggregate_target關係
- Oracle session traceOracleSession
- mysql trace optimizerMySql
- SQL_TRACESQL
- 沒有連線target database的情況下執行RMAN duplicate可能引發的問題Database