Re: 11gr2 sql issue

From: Greg Rahn <>
Date: Tue, 8 Nov 2011 19:53:38 -0800
Message-ID: <>

I'm unclear of what question you seek the answer to. Are you trying to find out why there was a plan regression and how to resolve it or are you just curious about a bunch of wait events (symptoms) from the bad plan - which seems a lot less interesting and useful to me given the root cause is really what I'd be looking for/at.

On Tue, Nov 8, 2011 at 7:37 PM, Kumar Madduri <> wrote:
> Greg
> I did explain plans too and there were changes  (i thought i mentioned
> this..). We just took a 10053 trace to see if we can get any other useful
> information as originally when the developer ran this from TOAD the sql
> never completed. We did not even have a sql id at that time.
> But what striked me was this event. The same query runs fine when I use the
> ordered hint or set the optimizer_features_enabled to
> and the event no longer appears
> I was not mentioning about 10053 trace being useful though but se.sql .
> Explain plan does show differences obviously.
> On Tue, Nov 8, 2011 at 7:30 PM, Greg Rahn <> wrote:
>> I'd disagree that this is useful -- the most useful information with
>> plan changes is simply the full plans (dbms_xplan) and you dont even
>> need a 10053 trace for that.
>> On Tue, Nov 8, 2011 at 7:05 PM, Kumar Madduri <> wrote:
>> > Hi
>> > As part of regression testing in our db upgrade from to
>> >,
>> > one of the developers reported a slow sql (attached slow_sql.sql)
>> > We did a 10053 trace and noticed one of the things was wip_entities was
>> > not
>> > doing a Index scan in 11gR2 vs 11gR1.
>> > But what is most useful till this point is Tanel's se.sql script which
>> > reports this
>> --
>> Regards,
>> Greg Rahn

Greg Rahn
Received on Tue Nov 08 2011 - 21:53:38 CST

Original text of this message