RE: Index clustering factor

  • From: "Brady, Mark" <Mark.Brady@xxxxxxxxxxxxxxxxx>
  • To: <jonathan@xxxxxxxxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 10 Jan 2008 14:37:09 -0500

Jonathan, can you expand upon the question, "what does OEM tell you
about the run-time predicates?" a bit.

Where in OEM would I look if wanted to answer that question?

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jonathan Lewis
Sent: Thursday, January 10, 2008 2:10 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: Index clustering factor

The optimizer cannot ignore the index hint for that query.
Therefore the hint is illegal.

The first thing to check is whether you have a column coercion issue.
What are the types of the columns and of the input variables - and what
does OEM tell you about the run-time predicates ?


Jonathan Lewis

Author: Cost Based Oracle: Fundamentals

The Co-operative Oracle Users' FAQ

----- Original Message -----
From: "Orysia Husak" <Orysia.Husak@xxxxxxxxxxxxx>
Subject: RE: Index clustering factor

The statement is expected to fetch only 1 or 2 rows. The default Oracle
gather_stats generates a histogram size auto.

We've provided an index hint in  the SQL and Oracle sill ignores the
>Our query is :
>Select * from tableA where fielda=:A and fieldb=:B
>We have an index on tableA (fielda, fieldb), but Oracle isn't using the


>>> This e-mail and any attachments are confidential, may contain legal, 
>>> professional or other privileged information, and are intended solely for 
>>> the addressee.  If you are not the intended recipient, do not use the 
>>> information in this e-mail in any way, delete this e-mail and notify the 
>>> sender. CEG-IP1


Other related posts: