Uppercase Accented Character Not Correctly Translated Via Offline Migration In SQL*Developer
(Doc ID 1511513.1)
Last updated on FEBRUARY 10, 2020
Applies to:Oracle SQL Developer - Version 3.2 and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
SQL Developer 3.2 is used to migrate a database from SQL Server to Oracle Database 11.2.
After the migration, special characters are displayed as � in several tables.
The Source and Target Database details are :
Source Database : SQL Server 2008
Platform : Windows
Target Database : Oracle 11.2
Platform : Sun Solaris 10
For example, on SQL Server, create a table with one column:
The character "É" should be stored in Unicode as C3,89
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