NLS_TERRITORY is not Correctly set based on the Locale
(Doc ID 2789581.1)
Last updated on AUGUST 09, 2023
Applies to:
JDBC - Version 11.1.0.6 to 12.1.0.1.0 [Release 11.1 to 12.1]Information in this document applies to any platform.
Symptoms
Change of behavior between JDBC 12.1.0.1 and JDBC 12.1.0.2.
JDBC 12.1.0.1 does not always set the NLS_TERRITORY, but the JDBC 12.1.0.2 and later versions do.
Example: testcase code here
Changes
In JDBC driver up to version 12.1.0.1 included, the NLS_TERRITORY may not reflect the JVM Locale. This is a bug that was corrected in JDBC 12.1.0.2. The behavior in JDBC 12.1.0.2 is that the NLS_TERRITORY is always set based on the JVM Locale.
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 |
| References |