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.
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.

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.

For example, a new customer named NetInc is created at two replicas during the same time period between synchronizations. When each replica synchronizes, there seem to be two customer records with identical names. To ensure uniqueness, HCL Compass references the ratl_keysite field.

If you need to use describe or chmaster commands to work with an ambiguous record, you must refer to its keysite name (originating site name). For example:

customer:NetInc<keysite-name>.

The following example uses the keysite name in the object selector:

multiutil describe -clan telecomm -site tokyo -family PRODA -user masako
-password secret customer:NetInc<boston_hub>

Multiutil: Mastership of ‘customer:NetInc<boston_hub>’ is ‘boston_hub’.