Home
Administering
Learn how to administer the product.
Administering HCL Compass Multisite
Administering HCL Compass Multisite
Troubleshoot MultiSite operations
There are common situations in which running a HCL Compass 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.
Stateless record type naming conflicts
To fix a naming conflict for a stateless record, you must rename one of the records.
Find stateless records with naming conflicts
You can use the ratl_keysite field in queries designed to find stateless records of the same name. Follow these guidelines when querying for stateless records with naming conflicts.

Administering
Learn how to administer the product.
- Administering HCL Compass
  Learn how to administer the HCL Compass.
- Administering HCL Compass Web
  This section discusses how to administer HCL Compass Web.
- Administering HCL Compass Multisite
  Administering HCL Compass Multisite
  - Introduction
    HCL VersionVault MultiSiteHCL Compass MultiSite adds a powerful capability to HCL VersionVaultHCL Compass. With MultiSite, developers at different locations can use the same HCL VersionVault versioned object base (VOB) HCL Compass database set (a schema repository and its associated user databases). For HCL VersionVault, each location (site) has its own copy (replica) of the VOB. For HCL Compass, 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 HCL VersionVaultHCL Compass 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 HCL Compass 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 HCL Compass 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 HCL Compass 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 HCL Compass 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.
        Record uninqueness
        To ensure that a record is unique, stateless record types use the ratl_keysite field. The ratl_keysite field is an internal system field that stores the name of the site where an object was created.
        Find stateless records with naming conflicts
        You can use the ratl_keysite field in queries designed to find stateless records of the same name. Follow these guidelines when querying for stateless records with naming conflicts.
        Renaming records
        This topic provides information about renaming stateless records with naming conflicts.
      - 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 HCL VersionVault MultiSite and HCL VersionVault that display HCL VersionVault MultiSite information. There are a series of MultiSite commands and API functions that display or modify MultiSite information.

Find stateless records with naming conflicts

You can use the ratl_keysite field in queries designed to find stateless records of the same name. Follow these guidelines when querying for stateless records with naming conflicts.

Use the ratl_keysite field as both a Display field and Filter when creating a query on the respective stateless record type.
If the query finds any duplicate record names, rename them according to a site-specific naming convention that has been agreed upon. Remember that your current replica must master a record in order for you to modify it.

To assist you in viewing and modifying records, you can add the ratl_keysite field to the form of any stateless record type where you expect naming conflicts to arise. For more information, see the Schema Developer topics in the HCL Compass Help.