Using Unicode and partial Unicode databases with Universal Cache
Depending on your solidDB® database mode (Unicode or partial Unicode), you might need to specify the encoding of character data type columns (CHAR, VARCHAR, and so on).
About this task
▪If your solidDB® database mode is Unicode (General.InternalCharEncoding=UTF8), set the encoding of solidDB® character data type columns (CHAR, VARCHAR, and so on) to UTF-8.
▪If your solidDB® database mode is partial Unicode (General.InternalCharEncoding=Raw), set the encoding of solidDB® character data type columns (CHAR, VARCHAR, and so on) to the encoding used in the application environment.
Important: By default, the encoding of character data type columns is set to ISOLatin1. If your application uses Latin1 encoding, you do not need to set the encoding explicitly.
Procedure
1 In the Management Console, click Configuration > Subscriptions.
2 Select the subscription.
3 Click the Table Mappings view and select the table mapping.
4 Right-click and select Edit Mapping Details.
5 Click the Translation tab.
6 Select the character data type (CHAR, VARCHAR, and so on) source column. This enables the Encoding Conversion area.
7 Select the character encoding from the Source list.
▪Unicode databases: UTF-8
▪Partial Unicode databases: application encoding
8 Select the character encoding to which you want to convert from the Target list. For example, your backend data server might be storing the character data types in the UCS-2 big-endian form.
9 Click Apply.
10 Repeat the above steps for all subscriptions where solidDB® database is the source or target datastore.
Results
When you start replication on the subscription, IBM InfoSphere CDC converts the character encoding in the source column to the encoding you specified and populates the mapped target column with data in the new encoding.