RE: Query execution question
From: Allen, Brandon <Brandon.Allen_at_OneNeck.com>
Date: Wed, 16 Sep 2009 10:43:37 -0700
Message-ID: <64BAF54438380142A0BF94A23224A31E112B5D2FDB_at_ONEWS06.oneneck.corp>
Metalink 387394.1 also has a good description of the problem. If the query is just coming from a perl script, your best bet might be to change it to use literals instead of bind variables. Other possible solutions are:
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.
Date: Wed, 16 Sep 2009 10:43:37 -0700
Message-ID: <64BAF54438380142A0BF94A23224A31E112B5D2FDB_at_ONEWS06.oneneck.corp>
Metalink 387394.1 also has a good description of the problem. If the query is just coming from a perl script, your best bet might be to change it to use literals instead of bind variables. Other possible solutions are:
- Remove histograms on the involved tables (gather stats with method_opt=>'for all columns size 1')
- Stored outlines
- SQL Profiles (10g+ if you have Tuning Pack license)
- Upgrade to 11g and see if Adaptive Cursor Sharing fixes it or try using SQL Plan Management to preserve the good plan
Regards,
Brandon
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 Wed Sep 16 2009 - 12:43:37 CDT