Databases Reference
In-Depth Information
When Configuring a Channel
This example configures a channel to debug and trace at level 5:
RMAN> configure channel device type disk debug=5 trace=5;
RMAN> backup datafile 4;
You should now have a trace file located in the directory specified for your diagnostic trace files. To clear the
channel debug settings, use the
clear
parameter as shown here:
RMAN> configure channel device type disk clear;
How It Works
The
debug
command produces a detailed report of internal operations executed by RMAN. You'll notice that the
performance of RMAN will suffer when debugging is enabled. Therefore, we don't recommend running commands
in debug mode on a production database. You should turn on debugging only in test environments or at the
recommendation of Oracle Support.
Debugging Basics
The
debug on
command is equivalent to
debug all
. Both of those commands turn on all available types of debugging.
You also have the option of enabling debugging just for certain types of operations. Listed next are specific areas for
which you can turn on debugging:
•
io
•
sql
•
plsql
•
rcvman
•
rpc
For example, if you wanted to debug just I/O-related operations when backing up your users' tablespace, you
would enable I/O debugging as shown here:
$ rman target /
RMAN> spool log to rman.log
RMAN> spool trace to rman.trc
RMAN> set echo on
RMAN> debug io
RMAN> backup datafile 4;
RMAN> debug off
RMAN> spool trace off;
RMAN> spool log off;
Your output file (rman.trc in this example) should indicate that IO debugging has been enabled:
RMAN-03036: Debugging set to level=9, types=IO
