Re: oracle sql profile - need help please
Date: Tue, 13 Apr 2010 06:22:05 -0700 (PDT)
On Apr 13, 2:15 pm, gazzag <gar..._at_jamms.org> wrote:
> On 13 Apr, 13:22, Andy <andy..._at_gmail.com> wrote:
> > Hi folks
> > Enterprise Manager suggested a better plan for me (Oracle 10.2.3 /
> > Solaris64) and I went for it. However, it doesn't look like it's being
> > Any help as to how I can force LIVE to do what TEST is doing? If the
> > force-match takes effect, I'd like to assume that would have sorted
> > it ? We have no access to the underlying SQL.
> Are there any differences in INIT.ORA parameters?
Hi - Nothing that would make a different; just larger SGA etc for LIVE system. More "sizing" parameters rather than anything of a case more likely to inflict a different plan.
If I could get this profile to apply, I'd like to think that would sort it....
Any ideas? Thanks for the reply.
> > SELECT /*+ LEADING INDEX(S_ S436_IX1) INDEX(SHAPE F436_UK1)
> > INDEX(MMLINE A436_IX1) */ HCREF.MMLINE.FEATCODE,
> > HCREF.MMLINE.SHAPE ,S_.eminx,S_.eminy,S_.emaxx,S_.emaxy ,SHAPE.fid,SHAPE.numofpts,SHAPE.entity,SHAPE.points,SHAPE.rowid
> > FROM (SELECT /*+ INDEX(SP_ S436_IX1) */ DISTINCT sp_fid, eminx, eminy,
> > emaxx, emaxy FROM HCREF.S436 SP_ WHERE SP_.gx >= :1 AND SP_.gx <= :2
> > AND SP_.gy >= :3 AND SP_.gy <= :4 AND SP_.eminx <= :5 AND SP_.eminy
> > <= :6 AND SP_.emaxx >= :7 AND SP_.emaxy >= :8) S_ , HCREF.MMLINE ,
> > HCREF.F436 SHAPE WHERE S_.sp_fid = SHAPE.fid AND S_.sp_fid =
> > HCREF.MMLINE.SHAPE
> > Thanks
> > A
Received on Tue Apr 13 2010 - 08:22:05 CDT