Last updated on MAY 19, 2017
Applies to:JDBC - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
After upgrading the database from 10.2.0.5 to 184.108.40.206, some queries changed behavior.
Before the upgrade, due to the JDBC setup:
the queries results were case and accent insensitive.
Now, even if the setup for the JDBC driver is done as before, it turns to case and accent sensitive, bringing only the rows that match exactly the WHERE clause.
These queries come from a JBoss server (JBOSS EAP 6.1) using Oracle JDBC OCI Driver 220.127.116.11.
Doing a test with thin driver (which is not an option), it behaves like in 10g database (as case and accent insensitive).
It seems that the JDBC OCI driver setup (nls_comp and nls_sort) is being ignored.
It should behave as it was in 10g. The use of these two alter session commands let to have the queries case and accent insensitive.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms