Great! Even more plan changes over multiple executions of the same SQL.

As if we didn’t have enough problems with optimizer plans that change at the whiff of a stat…

Hasn’t anyone got back to Oracle the clear message that what production environments need is a STABLE and PREDICTABLE optimizer?

Not something that keeps changing execution plans at the drop of a hat?

I can’t wait to see what will happen in closed, non-changing environments such as Peoplesoft, JDE, Siebel and even Oracle’s own apps when this ever-changing optimizer is unleashed on them…

At least give us the option of turning off all this unneeded overhead!

Ah well: one can only dream…

Thanks for the superb analysis, Tanel. Much appreciated.

Blurring the bondaries between SGA and PGA will quickly poses the question of keeping the definition for thes 2 strucutres. Let me guess, it will be named OGA : Oracle Global Area.