Optimizer Does not use Spatial Domain Index for SQL When NLS_comp=linguistic, NLS_sort=binary_ci
(Doc ID 1617278.1)
Last updated on APRIL 08, 2022
Applies to:
Oracle Spatial and Graph - Version 11.2.0.3 and laterInformation in this document applies to any platform.
Symptoms
On a table with column of type MDSYS.SDO_GEOMETRY, a spatial index is created in a session with NLS_comp=linguistic and NLS_sort=binary_ci
As a results a query from a session with NLS_comp=linguistic and NLS_sort=binary_ci in the os environment uses a full table scan.
But the same query from a session with standard NLS_comp=binary and NLS_sort=binary in the os environment uses the domain index.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |