RE: Explain Plan not the same through ODBC

Okay, then check for parameter changes made by the application or user, different bind variable values or different methods of retrieving the plan (e.g. autotrace, explain plan for, 10046 trace, v$sql_plan). Are the two executions sharing the same child cursor in v$sql? If not, check v$sql_shared_cursor to see why not.

From: Luc Demanche [mailto:lucdemanche_at_gmail.com]  

We are connecting to the same Oracle user, so it's the same database, same schema, same statistics, same triggers, etc. The only difference is for one, we are using SQLPlus, for the other, it's through ODBC.

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