Re: Oracle Trace Analyzer

From: Mladen Gogala <>
Date: Thu, 3 Jan 2013 23:08:46 +0000 (UTC)
Message-ID: <>

On Thu, 03 Jan 2013 14:37:20 -0800, John Hurley wrote:
> On Jan 3, 2:28 pm, Mladen Gogala <> wrote:

>> I've just learned from the author that the venerable TRCA package uses
>> just PL/SQL to parse the trace files. That's why it's so slow and
>> resource consuming tkprof, orasrp and Cary's Method R profiler. There
>> are many parsing good tools but PL/SQL is not one of them. Most of the
>> parsing tools use finite automata which require lexer and grammar.
>> Lexer identifies the tokens while the grammar part performs the
>> required actions with the tokens. The most frequently used parsing
>> tools are lex/ yacc (flex/bison) and Perl.
>> That is why parsing of a 30MB trace file takes 10 minutes with TRCA and
>> it takes seconds with tkprof or orasrp.
>> --
>> Mladen Gogala The Oracle Whisperer
> What is the Oracle Trace Analyzer? You mean tkprof?

Nope. There is another one, look at the Metalink:

TRCANLZR (TRCA): SQL_TRACE/Event 10046 Trace File Analyzer - Tool for Interpreting Raw SQL Traces [ID 224270.1]

> Everyone that I know uses either orasrp or Cary's tool.

Cary's tool is not free. Orasrp has bugs. I reported some to Egor.

Mladen Gogala
The Oracle Whisperer
Received on Fri Jan 04 2013 - 00:08:46 CET

Original text of this message