Unicode may be used in a distribution key.
Unicode data may be replicated among heterogeneous databases. Examples of this replication among heterogeneous databases are: DB2 Unicode to DB2 Unicode, DB2 Unicode to MS SQL Server Unicode (nchar and nvarchar) or DB2 Unicode to Oracle Unicode (nchar and nvarchar).
Connect CDC has two Unicode categories: Unicode and Long Unicode. Information about the supported Unicode datatype mappings are shown in the following tables. DBMSs are abbreviated in the tables as follows:
The following table shows the mappings that are supported for Unicode. Note that:
-
-> <- show direction
-
-> can be either source or target
-
If datatypes are equal, -> implies <->
-
n = length at source
-
m = length at target
Databases |
Datatype |
What happens... |
---|---|---|
Informix and Informix |
NCHAR(n) -> NCHAR(m) |
|
NVARCHAR(n) -> NVARCHAR(m) |
|
|
NCHAR(n) <-> NVARCHAR(m) |
->
<-
|
|
Informix and Oracle |
NCHAR(n) -> NCHAR(m) |
|
NVARCHAR(n) <-> NVARCHAR2(m) |
|
|
NCHAR(n) <-> NVARCHAR2(m) |
->
<-
|
|
NVARCHAR(n) <-> NCHAR(m) |
->
<-
|
|
MS SQL Server and MS SQL Server |
NCHAR(n) -> NCHAR(m) |
|
NVARCHAR(n) -> NVARCHAR(m) |
|
|
NTEXT -> NTEXT |
|
|
NCHAR(n) <-> NVARCHAR(m) |
->
<-
|
|
NCHAR(n) <-> NTEXT |
|
|
NVARCHAR(n) <-> NTEXT |
|
|
DB2/400 and DB2/400 |
GRAPHIC(n) -> GRAPHIC(m) |
|
VARGRAPHIC(n) -> VARGRAPHIC(m) |
|
|
GRAPHIC(n) <-> VARGRAPHIC(m) |
->
<-
|
|
MS SQL Server |
NCHAR(n) -> NCHAR(m) |
|
NVARCHAR(n) <-> NVARCHAR2(m) |
|
|
NCHAR(n) <-> NVARCHAR2(m) |
->
<-
|
|
NVARCHAR(n) <-> NCHAR(m) |
->
<-
|
|
NTEXT <-> NVARCHAR2(n) |
|
|
NTEXT <-> NCHAR(n) |
|
|
MS SQL Server to and from DB2/400 |
NCHAR(n) <-> GRAPHIC(m) |
->
<-
|
NVARCHAR(n) <-> VARGRAPHIC(m) |
->
<-
|
|
NCHAR(n) <-> VARGRAPHIC(m) |
->
<-
|
|
NVARCHAR(n) <-> GRAPHIC(m) |
->
<-
|
|
NTEXT <-> GRAPHIC(n) |
|
|
NTEXT <-> VARGRAPHIC(n) |
|
|
DB2/400 |
NCHAR(n) <-> GRAPHIC(m) |
->
<-
|
NVARCHAR2(n) <-> VARGRAPHIC(m) |
->
<-
|
|
NCHAR(n) <-> VARGRAPHIC(m) |
->
<-
|
|
NVARCHAR2(n) <-> GRAPHIC(m) |
->
<-
|