Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Explain Plan not the same through ODBC
All good possibilities. Adding one more - does your query have a hint and
does the other front end tool strip off non-ANSI comments?
mwf
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
On Behalf Of Allen, Brandon
Sent: Tuesday, February 20, 2007 4:01 PM
To: lucdemanche_at_gmail.com; oracle-l
Cc: cdelisle_at_msds.com
Subject: RE: Explain Plan not the same through ODBC
Here are some possible causes to look at off the top of my head: different users with different environment settings (e.g. one has a trigger to change optimizer_mode or any number of other parameters, or such changes are made by the application or user), different bind variable values, different schemas, different system stats, different object stats, different methods of retrieving the plan (e.g. autotrace, explain plan for, 10046 trace, v$sql_plan).
Regards,
Brandon
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Luc Demanche
Why do we have 2 different explain plan for the same SQL ?
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-lReceived on Tue Feb 20 2007 - 16:06:47 CST
![]() |
![]() |