Forcing index usage...

Hi!
(9.2.0.6, linux)
I'm in a situation where oracle spatial doesn't use a domain index even if I use the index hint.
In fact, as long as the spatial operator (sdo_relate) is the only predicate in the where
clause, the index gets used, so the index is okay.
But as soon as I add more predicates or nest the query into another one,
the index doesn't get used and the query takes forever.

Is there anything I can do apart from the hint?

I'm seriously considering splitting my query into two, the first one
putting the spatial related results into a temporary table and the second one
doing the rest with the intermediate result.

Any thoughts on that?

Lots of Greetings!
Volker
.

Relevant Pages

  • Re: Forcing index usage...
    ... I'm in a situation where oracle spatial doesn't use a domain index even if I use the index hint. ... as long as the spatial operator is the only predicate in the where ... But as soon as I add more predicates or nest the query into another one, ...
    (comp.databases.oracle.server)
  • Re: Forcing index usage...
    ... I use the index hint. ... But as soon as I add more predicates or nest the query into another one, ... The Co-operative Oracle Users' FAQ ...
    (comp.databases.oracle.server)
  • Re: Spotlight Searching in Python - Mac OSX
    ... # create and initalize our query ... def hideApplication_: ... # the NSMetadataQuery will send back a note when updates are ... return predicate ...
    (comp.lang.python)
  • Re: Oracle Outer Joining - Unexpected Result Sets
    ... The main driving query of the script that I have been presented with, ... the above query predicate should ... numbers returned in this column by Oracle are different depending on ...
    (comp.databases.oracle.server)
  • Oracle Outer Joining - Unexpected Result Sets
    ... The main driving query of the script that I have been presented with, ... the above query predicate should ... numbers returned in this column by Oracle are different depending on ...
    (comp.databases.oracle.server)