Character Conversion Reading From Oracle Database 18.5 Not Translated Correctly When Using JDBC 12.2.0.1 (Doc ID 2641763.1)

Last updated on APRIL 15, 2022

Applies to:

Symptoms

When querying for data from a Java application using Oracle JDBC driver 12.2.0.1, some characters are not being translated correctly. The characters are translated correctly when using Oracle JDBC driver 11.2.0.4.

Before
UP0957/AN N473UPÚDT QXS RNO 212359 M04AÚ- 212359 21RNOSDF2359026904224
0032 0030 0031 0037 002d 0031 0032 002d 0032 0031 002d 0032 0033 002e 0035 0039 002e 0032 0036 002e 0039 0036 0034 0031 0035 0031 004d 0033 004b 00da 0046 0049 0020 0055 0050 0030 0039 0035 0037 002f 0041 004e 0020 004e 0034 0037 0033 0055 0050 00da 0044 0054 0020 0051 0058 0053 0020 0052 004e 004f 0020 0032 0031 0032 0033 0035 0039 0020 004d 0030 0034 0041 00da 002d 0020 0020 0032 0031 0032 0033 0035 0039 0020 0032 0031 0052 004e 004f 0053 0044 0046 0032 0033 0035 0039 0030 0032 0036 0039 0030 0034 0032 0032 0034 0020 0020

After
UP0957/AN N473UPￚDT QXS RNO 212359 M04Aￚ- 212359 21RNOSDF2359026904224
0032 0030 0031 0037 002d 0031 0032 002d 0032 0031 002d 0032 0033 002e 0035 0039 002e 0032 0036 002e 0039 0036 0034 0031 0035 0031 004d 0033 004b ffda 0046 0049 0020 0055 0050 0030 0039 0035 0037 002f 0041 004e 0020 004e 0034 0037 0033 0055 0050 ffda 0044 0054 0020 0051 0058 0053 0020 0052 004e 004f 0020 0032 0031 0032 0033 0035 0039 0020 004d 0030 0034 0041 ffda 002d 0020 0020 0032 0031 0032 0033 0035 0039 0020 0032 0031 0052 004e 004f 0053 0044 0046 0032 0033 0035 0039 0030 0032 0036 0039 0030 0034 0032 0032 0034 0020 0020

The database character set is US7ASCII. The driver is doing character conversion differently.

 Symptom:

Characters show ???? instead of the data.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.