Supported vendor database character sets

Each Rational® ClearQuest® data code page has a corresponding vendor database character set for each supported vendor database (Oracle, DB2, SQL Server).

To help you choose an appropriate character set for your vendor database, Table 1 lists the supported Rational ClearQuest data code page values and their corresponding vendor database character set values. For example, to use a schema repository with data code page 1251 (Cyrillic) for an Oracle database, create an empty Oracle database instance and then set the vendor database character set to CL8MSWIN1251.

Note: Rational ClearQuest does not support the Unicode character set.

For instructions about how to set the character set for your vendor database, see the vendor database documentation.

Table 1. Supported Rational ClearQuest data code pages and corresponding vendor database character sets
Rational ClearQuest data code page Oracle character set DB2 code set SQL Server collation
932 (Japanese) JA16SJISTILDE (see Code page 932 (Japanese) on Oracle) IBM-943 (943) (see Code page 932 (Japanese) on DB2) Japanese_*
936 (Simplified Chinese) ZHS16GBK (limited support - see Code page 936 (Simplified Chinese) on Oracle) GBK (1386) Chinese_PRC_*
949 (Korean) KO16MSWIN949 1363 Korean_Wangsung_*
950 (Traditional Chinese) ZHT16MSWIN950 big5 (950) Chinese_Taiwan_Bopomofo_*
1250 (Eastern Europe) EE8MSWIN1250 1250 Romanian_*
1251 (Cyrillic) CL8MSWIN1251 1251 Cyrillic_General_*
1252 (Western Europe) WE8MSWIN1252 1252 Latin1_General_*
1253 (Greek) EL8MSWIN1253 1253 Greek_*
1254 (Turkish) TR8MSWIN1254 1254 Turkish_*
1255 (Hebrew) IW8MSWIN1255 1255 Hebrew_*
1257 (Baltic) BLT8MSWIN1257 1257 Estonian_*
20127 (ASCII) Any Any Any
60932 (Safe Shift-JIS) JA16EUC eucJP (954) N/A
Note: For Microsoft Access databases, you do not need to set the vendor database code page.

Code page 932 (Japanese) on Oracle

JA16SJISTILDE is the recommended vendor database character set 932 for Japanese SJIS data on Oracle. This is a change from the recommendation for earlier versions of Rational ClearQuest, which was JA16SJIS. These two character sets are the same except for the way that the wave dash and the tilde are mapped to and from Unicode. Because Rational ClearQuest Version 7.0 uses Unicode to communicate to the database, it is now necessary to use the JA16SJISTILDE character set. For the proper method to convert an existing Oracle database from JA16SJIS to JA16SJISTILDE, see the Oracle documentation.

Code page 932 (Japanese) on DB2

IBM-943 is the recommended code set for Japanese SJIS data on DB2. You must configure the database management system to use the conversion table that is compatible with the Microsoft definition of code page 932. If this alternate character set is not used, you cannot set the Rational ClearQuest data code page to 932 for new schemas. Also, if you do not convert an existing DB2 database set to use the alternate conversion table, some characters in the 932 character set will be corrupted. See the document http://publib.boulder.ibm.com/infocenter/db2help/index.jsp?topic=/com.ibm.db2.udb.doc/core/r0012306.htm, in the section titled "Alternative Unicode conversion tables for the coded character set identifier (CCSID) 943".

Code page 936 (Simplified Chinese) on Oracle

Rational ClearQuest has a limitation when configured to use code page 936 on Oracle. Oracle does not supply a character set that corresponds exactly to Microsoft code page 936. The closest match is the ZHS16GBK character set, which excludes the euro character (U+20AC). You can configure your Oracle database to use ZHS16GBK with Rational ClearQuest, but you will have the following limitations:
  • If you are using the command, installutil setdbcodepage you must use the –allowconversion option. This command allows you to set the Rational ClearQuest data code page value to 936 even though the validation for the euro character fails.
  • You cannot use the euro character in your data. If you use this character in data, it is stored as a replacement character in the database, effectively corrupting it.
  • If you use Rational ClearQuest MultiSite, use Oracle databases that are configured identically with ZHS16GBK for every database in the clan. If you mix vendor databases throughout the clan and a euro character is entered, data divergence occurs because non-Oracle databases can store the euro, but Oracle databases store it as a replacement character.

Feedback