Re: Oracle Trace Analyzer

From: John Hurley <johnthehurley_at_gmail.com>
Date: Thu, 3 Jan 2013 14:37:20 -0800 (PST)
Message-ID: <484081c7-42e2-40bb-a2b0-1308cc024a2d_at_v7g2000yqv.googlegroups.com>

On Jan 3, 2:28 pm, Mladen Gogala <gogala.mla..._at_gmail.com> 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 Whispererhttp://mgogala.byethost5.com

What is the Oracle Trace Analyzer? You mean tkprof?

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

I licensed a copy of Cary's tool ( through hotsos pricing ... kind of weird ) ... but do not use it because I find the sorting options that orasrp to be superior.

I find that my developers want to see long resource profiles contain SQL in the order that it was submitted into the oracle database engine. They can handle understanding that "not the first SQL in a resource profile is the SQL that needs attention first".

I have asked for an enhancement to the Method R profiler but apparently Cary believes strongly in how the tool should produce output. Received on Thu Jan 03 2013 - 23:37:20 CET