|
Enable tracing only on those sessions that are having problems. Be
selective to minimize the performance burden on the sessions and to
retain more free space in the user dump destination directory.
Rename trace files after tracing is disabled. The new file name
should be something more meaningful that will be recognizable at a later
date. The name employee_index.trc is much more meaningful than
ORCL92_ora_3172.trc.
Delete trace files that are no longer needed to reduce clutter and
free disk space.
Explain Plan is not as useful when used in conjunction with tkprof
since the trace file contains the actual execution path of the SQL
statement. Use Explain Plan when anticipated execution statistics are
desired without actually executing the statement.
When tracing a session, remember that nothing in v$session
indicates that a session is being traced. Therefore, trace with caution
and remember to disable tracing after an adequate amount of trace data
has been generated.
tkprof does not control the contents of a trace file, it
simply formats them. Oracle provides multiple ways to actually generate
the trace file. tkprof is valuable for detailed trace file
analysis. For those DBAs that prefer a simpler tracing mechanism with
instant feedback, the autotrace utility should be used.
Deep inside the operating system executables there are
many utilities at the fingertips of Oracle professionals, but until now
there has been no advice on how to use these utilities. From tnsping.exe
to dbv.exe to wrap.exe, Dave Moore describes each utility and has
working examples in the online code depot. Your time savings from a
single script is worth the price of this great book.
Get your copy of Oracle Utilities: Using Hidden Programs,
Import/Export, SQL Loader, oradebug, Dbverify, Tkprof and More today
and receive immediate access to the Online Code Depot!
http://www.rampant-books.com/book_2003_1_utils.htm
Regards,
Don Burleson
www.dba-oracle.com
www.remote-dba.net
|
• Phone (252) 431-0049
