Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Query tuning exercise: what to look for in a 10053 trace

RE: Query tuning exercise: what to look for in a 10053 trace

From: Allen, Brandon <Brandon.Allen_at_OneNeck.com>
Date: Tue, 25 Jul 2006 11:34:15 -0700
Message-ID: <04DDF147ED3A0D42B48A48A18D574C45059E1BA9@NT15.oneneck.corp>


Yep, read them both - and saw his presentation at Hotsos :-) I'm not sure on this, but I think the join order will be a result of the estd cardinalities as well - with a NL join, it will start with the row source that it expects to return the smallest number of rows, then probe the other table for matching rows. So, if it underestimates the cardinality, then it will end up doing a lot more probing than it expected to do.


From: Schultz, Charles [mailto:sac_at_uillinois.edu] Sent: Tuesday, July 25, 2006 11:25 AM
To: Allen, Brandon; oracle-l_at_freelists.org Subject: RE: Query tuning exercise: what to look for in a 10053 trace

I see you have been reading his "tuning by cardinality feedback" paper. Or perhaps "under the hood..."? =)
I have read them, but it takes a long time for me to absorb the wonderful insights these guys have.  

From an academic standpoint, I am trying to figure out why the CBO is using a different join order - perhaps this is a vain and useless endeavor, but I am curious.

Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.

--
http://www.freelists.org/webpage/oracle-l
Received on Tue Jul 25 2006 - 13:34:15 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US