IBM Support

Considerations for Changing the Code Page in a ClearQuest MultiSite environment

Technote (troubleshooting)


The IBM® Rational® ClearQuest documentation states that to change the code page you need to recreate replicas. This could be unnecessary and time consuming. This technote explains steps if you are upgrading from a character set that is a subset of another, for example ASCII to Latin-1.


The documentation in the ClearQuest 7.0 Installation and Upgrade Guide p. 142 states:

    In a Rational ClearQuest MultiSite environment, to change the data code page at the master site and replicate the modified database, do the following:
    1. Back up your databases.
    2. Remove all replicas.
    3. Change the data code page at the master site.
    4. Scrub the oplogs.
This information can also be found in the Changing the Rational ClearQuest data code page value topic of the ClearQuest Information Center.

In a Rational ClearQuest MultiSite environment, changing the data code page from any non-ASCII value might introduce incorrect data in your oplogs. For best results, remove all replicas, clean the database at the mastering site, scrub the oplogs, and then re-create your replicas.

Resolving the problem

If you are upgrading from a character set that is a subset of another, for example ASCII to Latin-1, you will not have to remove and recreate all replicas.

Here are some steps and issues to consider:

  1. Verify that the vendor database character set is set appropriately as listed in the Appendix B Table 25 of the ClearQuest 7.0 Installation and Upgrade Guide.
    Note: If the database vendor character set is not correct to support the target code page, then the procedure as documented in the upgrade manual should be followed. This would involve creating a new database instance with the correct database vendor character set, and then copying the data into the newly constructed database instance.
  2. Run the codepageutil to verify that there are no offending records. If this is not run and there are some, you will have synchronization problems in the future. The remedy for this is to fix the records in the database
  3. Use the ClearQuest Maintenance Tool on the mastership site, to update the code page, and then perform a syncreplica.
  4. As with any schema change in a MultiSite environment, backup databases, stop all synchronizing, ensure all users are disconnected from all the databases (stop and restart database so there are no open connections), and ensure all sites are synchronized.


Always make new database back-ups of your schema repository and user databases prior to making schema changes and performing database upgrades. Failure to create back-up copies can limit your ability to recover from a an upgrade failure, design change issues or other unforeseen failures.

Cross reference information
Segment Product Component Platform Version Edition
Software Development Rational ClearQuest Multiutil

Document information

More support for: Rational ClearQuest
Maintenance tool

Software version: 7.0,,,,,,,,, 7.0.1,,,,,,,, 2003.06.00, 2003.06.13, 2003.06.14, 2003.06.15, 2003.06.16

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Reference #: 1256948

Modified date: 20 March 2007

Translate this page: