That's an excellent idea - I've seen this as well. If the index is corrupted, the indexed search will not return the correct results. In my case rebuilding the index fixed the issue. On 10/19/07, Rob Dempsey <Rob.Dempsey@xxxxxxxxxx> wrote: > > I have seen different counts when there is an index on the table and > oracle has not maintained the index. > > Check what the execution plan is. If it is using a index then try the > same SQL with a /*+ FULL(t)*/ hint > > Rob > >