After doing my seminar in Spain last month, one of the attendees sent me a secret note about what the CBO would look like in Oracle 12g. Apparently it’s re-engineered from ground and completely different from anything we’ve seen before. It goes beyond being automatic, intelligent and auto-tuning, it’s actually edible too!
The New CBO
Thanks to John Ospino for sending me this insider-info ;)
Great! I excite about that (CBO).
I’m waiting! ;)
“do you want fries with that?”
…
I can see this happening.
The fries-pack will be added by default, but wil be a separately licensed-option – payable.
And removal of the fries-pack will be a messy affair, with ketchup all over the place.
I wonder if EE will include a “Super-Size-That” option?
I actually had a chance to pilot test this. There are definitely some bugs (or maybe Oracle calls these features).
For example, I found that when doing massive parallel queries with hash joins, the CBO completely choked and the instance crashed. It basically had a heart attack.
In other cases, the results just poured out uncontrollably. I would say the optimizer had trouble digesting the information I fed to it.
hahaha…I love this CBO…:)
Anand
Finally my investigations knows daylight, jejejeje. Thank to you pal. It’s a pleasure share freaky stuff with you.
The CBO isn’t a black box anymore!
Looks delicious. I can’t wait!
Hahaha :))) Great pic :) Thanks for sharing Tanel
it’s very funny!!
one of the things i want in CBO, is to use storage index (oracle exadata feature) in execution plan. current CBO does not uses storage indexes to eliminate extends for which it has to perform IO. instead storage indexes we used at runtime to eliminate extends. Oracle still use old fashion Partitions to accomplish this task. which is not good in most of the cases.