Home
Administering
Learn how to administer the product.
Administering HCL Compass Multisite
Administering HCL Compass Multisite
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.
Replica deletion
To remove a replica, you must complete all the necessary steps; if you do not, synchronization and mastership problems can occur in other replicas in the family.
Using MultiSite after removing the last replica in a clan
If you use the rmreplica –dbset command on the last replica in your clan (leaving only the databases at the site containing the working schema repository), the database is no longer part of a MultiSite environment. It is now an unreplicated database and cannot be used to create new replicas while it is in this state.

Using MultiSite after removing the last replica in a clan

If you use the rmreplica –dbset command on the last replica in your clan (leaving only the databases at the site containing the working schema repository), the database is no longer part of a MultiSite environment. It is now an unreplicated database and cannot be used to create new replicas while it is in this state.

To change the state of the database so that you can replicate it again, you do not need to run the activate command. You must use the HCL Compass Maintenance Tool to change the database set name back to the form expected by multiutil; for example, CQMS.clan-name.site-name.