Configure unicode for databases
Overview
Configure each database used in the Connections deployment for unicode, whether for DB2, Oracle, or SQL. Configuring databases for unicode ensures that database tools like export and import do not corrupt unicode data.
Set configuration for unicode BEFORE Connections installation. Unicode cannot be set after Connections installation.
Configure unicode for Oracle databases
Installation must be performed so the AL32UTF8 character set is used. This is mandatory for proper unicode handling by Connections, and must be set properly at install time, since it cannot be modified after installation.
- On the Initialization Parameters page, click the Character Sets tab.
- Select the Use Unicode (AL32UTF8) option.
Configure unicode for DB2 databases
Perform the following steps on each DB2 instance in the deployment:
- Stop any WebSphere server connected to the DB2 database we are configuring.
- Log in to the DB2 server as the DB2 instance owner, and run...
db2set DB2CODEPAGE=1208
db2stop force db2start
- To check the new configuration:
db2set
This should return DB2CODEPAGE=1208. If not, it is not configured correctly and you should try Step 4 again.
Configure unicode for SQL Server databases
Latin1_General_BIN must be the collation for proper unicode handling by Connections, and must be set properly when the instance is installed, since it cannot be modified after installation.
- On the Customize the SQL Server 2008 Database Engine Collation dialog click the Window collation designator and sort order option.
- From the drop down menu select Latin1_General.
- Select the Binary option to make Latin1_General_BIN the default collation.
Parent topic:
Create databases