To: <jkstill@xxxxxxxxx>, "Oracle-L Freelists" <oracle-l@xxxxxxxxxxxxx>
Date: Wed, 1 Aug 2007 00:48:19 -0600
Playing with things, it seems that debug creates a trace file (whereas just
putting in trace does not). Very interesting stuff in the trace file.....
RF
Robert G. Freeman
Oracle Consultant/DBA/Author
Principal Engineer/Team Manager
The Church of Jesus Christ of Latter-Day Saints
Father of Five, Husband of One,
Author of various geeky computer titles
from Osborne/McGraw Hill (Oracle Press)
Oracle Database 11g New Features Now Available for Pre-sales on Amazon.com!
BLOG: http://robertgfreeman.blogspot.com/
Sig V1.2
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Jared Still
Sent: Tuesday, July 31, 2007 10:44 AM
To: Oracle-L Freelists
Subject: RMAN debug and trace
RMAN accepts trace and debug parameters for ALLOCATE/CONFIGURE CHANNEL.
eg. ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE' debug=5 trace 2;
There are different levels of debug and trace.
I can't seem to find any documentation explaining the different levels of
debug or trace.
There isn't much help in the PL/SQL source for dbms_backup_restore either.
Anyone here have some documentation on this?
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
