Migrating Oracle with Japanese databases

If you are using Rational® ClearQuest® version 2003.06.xx and you have an Oracle database whose Oracle character set is set to JA16SJIS (Shift-JIS), you must change this setting to JA16SJISTILDE before upgrading to version 7.1.x.

This change allows the database to store and process the full-width tilde character (Unicode value FF5E). Create or use an Oracle instance in which the Oracle character set is JA16SJISTILDE as the target. Then use the Maintenance Tool to move the schema repositories and the Designer to move the user databases to the Oracle instance.

Rational ClearQuest clients from Japanese versions 2003.06.00 through 2003.06.12 cannot handle the CLOB datatype. If you have clients from these releases in your environment, you cannot convert your Oracle databases to CLOB. In this situation, you have two options:

You can convert from LONG to CLOB and transfer data from a JA16SJIS (Shift-JIS) to JA16SJISTILDE Oracle instance at the same time, if you are running version 2003.06.15 or 2003.06.16. The move operation that transfers data to the new JA16SJISTILDE Oracle instance can perform the conversion from LONG to CLOB by specifying LOB_TYPE=CLOB in the Connect Options field of the target databases.

Any Rational ClearQuest clients from Japanese versions 2003.06.00 through 2003.06.12 can corrupt data in Oracle databases that use CLOB. Do not use these clients with databases that use CLOB.


Feedback