今天闲来无事,想看看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/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/8183550/viewspace-665344/