Database Reference
In-Depth Information
version specifies whether to display the version number of TVD$XTAT. It can't be used along
with other arguments.
wait specifies whether detailed information for wait events is shown. Enabling this feature
(that is, setting this argument to yes ) might have a significant overhead during processing.
Therefore, I suggest you set it initially to no . Afterward, if the basic wait information isn't
enough, you can run another analysis with it set to yes .
logging controls the logging level. The following values are available: severe , warning , info ,
fine , and finer . This argument is important only when debugging the execution of the tool.
Interpreting TVD$XTAT Output
This section is based on the same trace file already used earlier with TKPROF. Because the output layout of TVD$XTAT
is based on the output layout of TKPROF, I describe only information specific to TVD$XTAT here. To generate the
output file, I used the following parameters:
tvdxtat -i DBM11203_ora_28030.trc -o DBM11203_ora_28030.txt -s no -w yes -t text
Note that both the trace file and the output file in HTML and text format are available along with the other files of
this chapter.
The output file begins with overall information about the input trace file. The most important information in this
part is the interval covered by the trace file and the number of transactions recorded in it:
Database Version
****************
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Automatic Storage Management, Oracle Label Security, OLAP,
Data Mining and Real Application Testing options
Analyzed Trace File
*******************
/u00/app/oracle/diag/rdbms/dbm11203/DBM11203/trace/DBM11203_ora_28030.trc
Interval
********
Beginning 30 Nov 2012 23:21:45.691
End 30 Nov 2012 23:21:58.097
Duration 12.407 [s]
Transactions
************
Committed 0
Rollbacked 0
The analysis of the output file starts by looking at the overall resource usage profile. The processing here lasted
12.407 seconds. About 56 percent of this time was spent running on the CPU, about 24 percent was spent reading and
writing temporary files ( direct path read temp and direct path write temp ), and about 23 percent was spent
 
Search WWH ::




Custom Search