Re: SQL performance issue determination
- From: Rich <richa03@xxxxxxxxx>
- To: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
- Date: Tue, 20 Apr 2010 16:02:53 -0700
Thanks, Brandon.
The plan is not the problem.
Sometimes there will be more accesses into a table for certain predicate
conditions and I want to determine what they are.
If I can get that/them, I might be able to determine a schema or app change
which will avoid these accesses.
I don't think this an Oracle "problem" - I think it's a schema issue...but I
can't prove it.
On Tue, Apr 20, 2010 at 3:34 PM, Allen, Brandon
<Brandon.Allen@xxxxxxxxxxx>wrote:
> Why do you need to get bind variables from all executions? The only ones
> that really matter are the ones that are peeked at hard parse time when the
> execution plan is determined – those are the ones you need to capture, and
> those are already captured for you in v$sql_plan.xml_other (can can be
> retrieved with
> dbms_xplan.display_cursor(‘<sql_id>’,’<child_number>’,’PEEKED_BINDS’)
>
>
>
> 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.
>
Other related posts:
