Databases Reference
In-Depth Information
From the OS Prompt or RMAN Command Line
This first example enables all debugging and places the debug messages in a separate file from the regular RMAN output:
$ rman target / debug=all trace=rman.trc log=rman.log
The prior command will enable verbose debugging and send the debug output to a file named rman.trc. The
regular logging of RMAN commands and output will be placed in the rman.log. We recommend that you put the
debug messages in a separate file (as shown in the prior line of code). This is particularly helpful when working with
Oracle Support and they request a file that contains just the debug information.
You can also turn on debugging around particular RMAN commands. For example:
$ rman target /
RMAN> spool log to rman.log
RMAN> spool trace to rman.trc
RMAN> run{
debug on;
backup datafile 4;
debug off;
}
RMAN> spool trace off;
RMAN> spool log off;
Again as a best practice, in the prior output debug messages are directed to a separate file from the regular
RMAN output.
When Allocating a Channel
This example uses
debug
with the
trace
parameter. Tracing at level 1 gives you the least amount of information,
and tracing at level 5 gives you the most verbose output. Run the
allocate
command from within the
run{}
block,
as shown here:
RMAN> run{
allocate channel d1 type disk debug=5 trace=5;
backup datafile 4;
release channel d1;
}
You should now have a trace file located in the directory specified for your diagnostic trace files. You can display
the directory of the trace files via this query:
SQL> select value from v$diag_info where name='Diag Trace';
If you're using an older version of Oracle, you can locate the trace file directory by displaying the value of the
user_dump_dest
initialization variable:
SQL> show parameter user_dump_dest
