If you use the ClearCase/ClearQuest UCM integration, you must run multiutil from a machine that does not require this integration. This is because multiutil requires special database set names that are not supported by the UCM integration.
The ClearQuest Integration Server (cqintsrv) caches information about its current session. You must terminate these processes before running the first mkreplica –export command on the working schema repository. If this is not done, error messages appear during ClearCase operations to indicate that the session is no longer valid.
If you use the ClearQuest UCM integration with MultiSite, the default behavior is to check mastership before delivery.
There are restrictions on using the RequisitePro, TestManager, and Rational Administrator integrations in a MultiSite deployment. If your current replica masters a ClearQuest record, but the associated Rational Project record is not mastered by the same replica, you cannot make changes to the integration information captured in a ClearQuest record (for example, adding new requirements to the requirements tab).