Welcome
Administering
Learn how to administer the product.
Administering Rational® ClearQuest® Multisite
Administering Rational® ClearQuest® Multisite
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.
Empty vendor database creation
Before you import a replica-creation packet, you must create an empty vendor database to contain the replica data.

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.
    - Database activation
      Before you can create the first replica of a database, you must activate the database set (a schema repository and its associated user databases). After you activate a database set, you can replicate it multiple times. A database set needs to be activated only once.
    - Export a replica-creation packet
      You create a replica by generating replica-creation packets and sending them to the sites that will host the database replicas. You do this with the mkreplica –export command.
    - Empty vendor database creation
      Before you import a replica-creation packet, you must create an empty vendor database to contain the replica data.
    - Import a replica-creation packet
      When you import a replica-creation packet, you import raw data into existing vendor databases. Replica-creation packets do not contain databases; they contain the metadata and record data that form a database. Packets are not vendor specific and can be used to create a schema repository or user database from any supported vendor database.
    - Replica creation scenario
      The following topics provide an example of the replica export, transport, and import processes.
  - 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.
  - 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

Empty vendor database creation

Before you import a replica-creation packet, you must create an empty vendor database to contain the replica data.

Note: To prevent data corruption, the code page (or character set) of your vendor databases should match the data code page value of your database set.

Attention: Do not create a Rational® ClearQuest® database before receiving a database replica. Importing a replica packet into an empty vendor database creates a Rational® ClearQuest® database. If you have created a Rational® ClearQuest® database with the Maintenance Tool or Rational® ClearQuest® Designer, the replica import fails.