Re: top down approach to reducing io from awr report

From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Mon, 22 Aug 2011 13:04:37 +0000 (UTC)
Message-ID: <pan.2011.08.22.13.04.35_at_gmail.com>



On Mon, 22 Aug 2011 03:40:23 -0700, dba cjb wrote:

> Is there any way I can dig deeper to find the sql that is doing most of
> the work
> / the sql_id for the pl/sql doesn't give me anything to look at ...or am
> I restricted at what I can drill down on via sql_id
>
>
> My general aim is to reduce i/o overhead where possible & I want to
> attack the 'biggest' culprits
> by looking at explain plans.
>
> I would welcome any ideas on drilling further om pl/sql code or comments
> on alternative approaches?
>
>
> regards
> Chris B

The best way would be to collect the execution trace for the processes using that particular PL/SQL and analyze it with tkprof or orasrp. Profiling the PL/SQL code with the DBMS_PROFILER also wouldn't be a bad idea.

-- 
http://mgogala.byethost5.com
Received on Mon Aug 22 2011 - 08:04:37 CDT

Original text of this message