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.
Transport problems
There are problems that can occur during the transport phase of synchronization.
Invalid destination
When the destination is not properly specified, the shipping server fails because it cannot determine where to deliver the packet.

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.
      - Invalid destination
        When the destination is not properly specified, the shipping server fails because it cannot determine where to deliver the packet.
      - Shipping server fails to start or connection is refused
        If the shipping server on the receiving host does not start or the connection is refused, check the albd_server log on the receiving host for an explanation of the failure.
      - Shipping order expires
        If the shipping server finds that a shipping order has expired, it attempts to return the packet to the originating host.
    - 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.
    - 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.

Invalid destination

When the destination is not properly specified, the shipping server fails because it cannot determine where to deliver the packet.

The local hosts hosts file, hosts NIS map, or Domain Name Service must list one of the following hosts:

Destination host
Next-hop host corresponding to the destination host (on Linux™ and the UNIX™ system, defined in a ROUTE entry in the hosts shipping.conf file; on Windows™, defined in the Routing Information section in the hosts MultiSite Control Panel.

If hosts in your network are known only by their IP addresses, you can use the IP addresses instead of host names.

In the absence of such entries, the shipping server fails, because it cannot determine where to deliver the packet. In this case, it writes error messages to its log file (Linux™ and the UNIX™ system) or the Windows™ Event Viewer.

If the destination host name was misspelled, use the mkorder command to create a new shipping order with the correct host name. If you misspell a host name in a mkreplica -export command, the incorrect host name is recorded. Verify the error with lsreplica -long, and correct the spelling with chreplica.

In other cases, you may have to revise the hosts database of remote hosts. The sending host must be able to communicate with the receiving hosts using TCP/IP. Use the rcp command on the sending host to copy a file to the receiving host. If it fails, you have a set up or networking problem with your host.