JDBC/thin conversion of "\U3000" to ASCII 0x00 (null) with database with a US7ASCII character set
Last updated on JUNE 01, 2017
Applies to:JDBC - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
JDBC/thin testcase application shows that a UNICODE CHARACTER "\U3000" is converted to 00 (null) when inserted in to a database with a US7ASCII character set.
On one hand it is expected since the JDBC driver is preventing non-ascii characters from being stored in the database, however storing a character of 00 (null) in character columns will cause problems with applications retrieving content as strings.
This issue does not occur with databases using other character sets, multi-byte charactersets.
This is only an issue with the thin driver. The OCI driver behaves as expected and inserts question mark (3F) which is the standard replacement character for ASCII.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms