Linguistic Sorting on Application Side caused query to ignore SQL Profiles/SQL Baselines and was not using desired index.
(Doc ID 2570477.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Information in this document applies to any platform.
- On 18.104.22.168 version, SQL_IDs are not picking the desired explain plan after applying the profile
Linuguistic Sorting by the use of NLS_COMP = LINGUISTIC at client side, caused the Oracle Index access path to be ignored by specific runs from Application. Query invoked from SQLPLUS was using desired index.
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