Welcome
Administering
Learn how to administer the product.
Administering Rational® ClearQuest® Multisite
Administering Rational® ClearQuest® Multisite
Troubleshoot MultiSite operations
There are common situations in which running a Rational® ClearQuest® MultiSite command produces an unexpected result, sometimes accompanied by a warning or error message.
Naming conflict resolution
If you do not impose a site-specific naming convention for Workspace items (queries, reports, charts, and so on), users and groups, and other stateless records, it is possible to have different objects with the same name.
Workspace naming conflicts and Rational® ClearQuest® Web
If two Workspace items (queries, reports, and so on) have the same name, both items work as expected in the Windows™, Linux™, and the UNIX™ system clients, according to mastership restrictions and database privileges. However, in Rational® ClearQuest® Web, only one of the items works. To avoid confusion, you must rename one or both of the items.

IBM ClearQuest 10.0.9
Overview
Learn general information about the product.
Installing
Learn how to install the product.
Upgrading and migrating
Learn how to upgrade and migrate data for the product.
Administering
Learn how to administer the product.
- Administering Rational® ClearQuest®
  Learn how to administer the Rational® ClearQuest®.
- Administering Rational® ClearQuest® Web
  This section discusses how to administer Rational® ClearQuest® Web.
- Administering Rational® ClearQuest® Multisite
  Administering Rational® ClearQuest® Multisite
  - Introduction
    and Rational® ClearQuest® MultiSite add a powerful capability to and Rational ClearQuest. With MultiSite, developers at different locations can use the same versioned object base (VOB) or Rational ClearQuest database set (a schema repository and its associated user databases). For Rational ClearQuest, each location has its own copies, or replicas, of the schema repository and user databases. At any time, changes made in one replica can be sent in update packets to other replicas. You can manage replicas by using the command-line tools.
  - Implementation planning
    Before you install and use DevOps Code ClearCase®DevOps ClearQuest® MultiSite, you need to plan your implementation.
  - Packet transportation methods and configuration
    The method you choose for transporting packets between replicas depends on connectivity. If your replicas do not have IP connectivity, you must use a file-based transport method. If your replicas have connectivity, you can use the store-and-forward facility.
  - Database replica creation
    Creating your database replicas requires careful planning and consideration part of which involves making decisions about mastership and methods of packet delivery.
  - Replica synchronization
    Replica synchronization uses the same export-transport-import procedure that is used during replica creation.
  - Database replicas administration
    Sustaining a smoothly functioning MultiSite environment requires dedicated administration. Many administrative processes can drastically change your environment and require careful consideration and planning.
  - Mastership management
    The management of mastership affects how database objects are accessed and manipulated by users in your MultiSite environment. Mastership management is an ongoing process as new objects are entered into the database and users' requirements change.
  - Troubleshoot MultiSite operations
    There are common situations in which running a Rational® ClearQuest® MultiSite command produces an unexpected result, sometimes accompanied by a warning or error message.
    - Replica export problems
      There are common replica export problems that may occur.
    - Transport problems
      There are problems that can occur during the transport phase of synchronization.
    - Replica import problems
      There are common replica import problems that can occur.
    - Synchronization export problems
      There are common problems that can occur during the export phase of synchronization.
    - Synchronization import problems
      The topics in this section describe problems that can occur during the import phase of synchronization.
    - Removing circular duplicate links
      In a replicated Rational® ClearQuest® environment it is possible to create a circular duplicate link when a defect and its duplicate are both set to the Duplicate state.
    - Naming conflict resolution
      If you do not impose a site-specific naming convention for Workspace items (queries, reports, charts, and so on), users and groups, and other stateless records, it is possible to have different objects with the same name.
      - Workspace naming conflicts and Rational® ClearQuest® Web
        If two Workspace items (queries, reports, and so on) have the same name, both items work as expected in the Windows™, Linux™, and the UNIX™ system clients, according to mastership restrictions and database privileges. However, in Rational® ClearQuest® Web, only one of the items works. To avoid confusion, you must rename one or both of the items.
      - Stateless record type naming conflicts
        To fix a naming conflict for a stateless record, you must rename one of the records.
      - Ambiguous users and user groups
        When resolving user and user group naming conflicts, you must be able to properly identify which user and group name you are specifying.
    - Lost database replica recovery
      Occasionally, a replica is lost. This loss is usually due to a hardware failure (for example, disk crash), a software failure (for example, OS-level file system corruption), or a human error. If an unreplicated database is lost, you can restore a recent copy from backup and resume development work. The changes made between the time of the backup and the time of the failure are not recoverable.
    - replica repair with multiutil repair
      You can use the multiutil repair command to troubleshoot and repair problems in a replica that might cause some MultiSite commands to fail.
    - Error messages
      The messages listed in this topic are generated by the mkorder, mkreplica, shipping_server, and syncreplica commands.
  - MultiSite command set
    This section summarizes the commands for DevOps ClearCase® MultiSite and DevOps ClearCase that display DevOps Code ClearCase MultiSite information. There are a series of MultiSite commands and API functions that display or modify MultiSite information.
Reporting
Learn how to generate reports for the product.
Developing
Learn how to develop schemas by using the Rational® ClearQuest® Designer.
Managing change and releases
Learn how to manage change and release in the product.
Integrating
You can integrate Rational® ClearQuest® with other software by adding packages to existing schema.
Extending product function
Learn how to extend the product.
Reference
Review reference information for the product.
Tutorials

Workspace naming conflicts and Rational® ClearQuest® Web

If two Workspace items (queries, reports, and so on) have the same name, both items work as expected in the Windows™, Linux™, and the UNIX™ system clients, according to mastership restrictions and database privileges. However, in Rational® ClearQuest® Web, only one of the items works. To avoid confusion, you must rename one or both of the items.

In order for you to modify a Workspace item, your current replica must master it. To determine which replica masters a Workspace item, open the Workspace, right-click the item, and click Mastership.

To rename a Workspace item:

Right-click the Workspace item and click Rename.
Type a new name in the highlighted area and click Enter.