Re: 11gr2 sql issue

  • From: Greg Rahn <greg@xxxxxxxxxxxxxxxxxx>
  • To: ksmadduri@xxxxxxxxx
  • Date: Tue, 8 Nov 2011 19:30:47 -0800

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 <ksmadduri@xxxxxxxxx> 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

Greg Rahn

Other related posts: