1. goryszewskig
    November 11

    Have You tried
    SQLT (SQLTXPLAIN) – Tool That Helps To Diagnose SQL Statements Performing Poorly [ID 215187.1]
    I’ve found it pretty useful.

  2. November 11

    No I haven’t yet, thanks for the suggestion. I will look into it.

    …then again I am not looking for a tkprof report alternative for Oracle trace files but am more interested in a trace profiler, that is, based on a tuning method. One that picks out the worse statement(s), based on that method, shows them in order and put it into context like DBTime alternatives in OEM (via using the Oracle tuning, diagnostics pack).

    This review is about the Method-R profiler, not a comparison of profilers.

    In the end you will have to pick what works for you.

    What I have read on the internet, SQLTXPLAIN is a tkprof alternative and not a profiling tool.

  3. November 12

    SQLTXPLAIN doesn’t strike me as a tkprof alternative as it has little to do with the Oracle Wait interface reporting we see in a detailed 10046 style Trace file.

    SQLTXPLAIN give you an overview of how Oracle decided to execute the statement by providing execution and plan details from AWR or cursor cache, object statistics details, system statistics details, and optionally kicking off a SQL Tuning Analyzer run and providing the results in its final report. SQLTXPLAIN also has ability to compare two tuning reports and hopefully point you to a reason when you get one of those “runs fine in Test but not in Prod” tickets.

    I have used SQLTXPLAIN about a dozen times and it does produce a nice report and helps document the environment surrounding the execution of the statement. I have tried compare a few times with varying results.

Comments are closed.