Optimizer Does not use Spatial Domain Index for SQL When NLS_comp=linguistic, NLS_sort=binary_ci

(Doc ID 1617278.1)

Last updated on JANUARY 26, 2014

Applies to:

Oracle Spatial and Graph - Version and later
Information in this document applies to any platform.


 A table with column having type MDSYS.SDO_GEOMETRY

The problem is the spatial index usage by Optimizer:
1. Index was created in a session with NLS_comp=linguistic and NLS_sort=binary_ci
2. Query from session with NLS_comp=linguistic and NLS_sort=binary_ci uses full table scan
3. Query from session with standard  NLS_comp=binary and NLS_sort=binary uses domain index


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms