TRACE ANALYZER alternative

An alternative to using Trace Analyzer to analyze a 10046 trace file is to use trace_report.

The trace_report script creates a formatted report of a SQL Trace dump file containing bind variables, wait statistics and histogram analysis, response time analysis, disk I/O histogram analysis, cursor summaries, cursor details, and row source plans.

trace_report contains many more features than tkprof, and does not require an Oracle database to analyze a trace file.

trace_report is much faster and uses far fewer resources than TRCANLZR, does not require an Oracle database to analyze a trace file, and does not require any changes to be made to the production database.

trace_report supports any version of Oracle from 7 through 10gR2. The script automatically adjusts to the version of the generated trace file.

trace_report is totally free.

The latest version is always available from http://www.dbasolutionsinc.com

Notes:
1) As trace_report is a Unix shell script, it's only usable in a Unix

   (Solaris, HP, AIX, etc) or Linux environment. 2) As no Oracle database is used, schema, user, object ids are printed,

   instead of the more easily understandable names. This is not an issue,    as object id translation is not needed for the majority of analysis,    and directions are printed in the report regarding how to translate the    object ids.

(trace_report was originally presented at IOUG 2004 in the "Oracle Internals - SQL TRACE Event 10046 trace analysis case study" session.)

Brian Lomasky

--
http://www.freelists.org/webpage/oracle-l