NLS_TERRITORY is not Correctly set based on the Locale
(Doc ID 2789581.1)
Last updated on JULY 06, 2021
Applies to:JDBC - Version 18.104.22.168 to 22.214.171.124.0 [Release 11.1 to 12.1]
Information in this document applies to any platform.
Change of behavior between JDBC 126.96.36.199 and JDBC 188.8.131.52.
JDBC 184.108.40.206 does not always set the NLS_TERRITORY, but the JDBC 220.127.116.11 and later versions do.
Example: testcase code here
In JDBC driver up to version 18.104.22.168 included, the NLS_TERRITORY may not reflect the JVM Locale. This is a bug that was corrected in JDBC 22.214.171.124. The behavior in JDBC 126.96.36.199 is that the NLS_TERRITORY is always set based on the JVM Locale.
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