Re: statspack snap level 7 as execution plan rep

Yes it is (a bug), and relates to v$sql_plan the bug is fixed in 10g, but there is no mention of it being backported to 9i

rgds

On 11/21/06, LS Cheng <exriscer_at_gmail.com> wrote:
>
> By the way statspack does not gather ACCESS_PREDICATES neither
> FILTER_PREDICATES, checking statspack.snap code it states this
>
> insert into stats$sql_plan
> ......................
> , 0 -- should be max( sp.access_predicates) (2254299)
> , 0 -- should be max(sp.filter_predicates)
>
> checked this in 9.2.0.8, I understand that there were bugs regarding these
> two fileds inv $sql_plan previous version 9.2.0.6 but in 9.2.0.8?
> 2254299 doesnt seem a bug number
>
> Cheers
>
> --
> LSC
>
> On 11/20/06, Jared Still <jkstill_at_gmail.com> wrote:
> >
> > Level 6 is required to get execution plans.
> >
> > Level 7 also included segment stats:
> >
> > From spdoc.txt:
> >
> > This level includes all statistics gathered in the lower level(s),
> > and additionally gathers the performance data on highly used
> > segments.
> >
> >
> > On 11/20/06, amonte < ax.mount_at_gmail.com> wrote:
> > >
> > > Hi
> > >
> > > I wonder if any of you use statspack to store a execution plan
> > > repository? When run in level 7. Is it worthy? Oracle 9.2.0.8 in
> > > HP-UX.
> > >
> > > TIA
> > >
> > > Alex
> > >
> >
> >
> >
> > --
> > Jared Still
> > Certifiable Oracle DBA and Part Time Perl Evangelist
> >
>
>

--
http://www.freelists.org/webpage/oracle-l