Use the following files and commands to help diagnose MultiSite problems:
On UNIX:
On Windows:
multitool –version
multitool lsreplica –long
multitool lsepoch
uname –a (UNIX)
cleartool –version
On Windows, look for applicable messages in the Event Viewer’s application log and system log, and in the ClearCase MVFS log files (c:\mvfslogs).
To list the exports from your current replica to a sibling replica, use the following command:
cleartool lshistory replica:sibling-replica-name@vob-selector
For example, to list exports from your current replica in the family /vobs/dev to the replica sanfran_hub:
cleartool lshistory replica:sanfran_hub@/vobs/dev 12-Jul.16:13 root export sync from replica "boston_hub" to replica "sanfran_hub" "Exported synchronization information for replica "sanfran_hub". Row at export was: boston_hub=149 sanfran_hub=115" 29-Jun.16:19 smg change epoch of replica "sanfran_hub" "Changed epoch row for replica Old row was: boston_hub=152 sanfran_hub=115 New row is: boston_hub=149 sanfran_hub=115 epoch row set by special connected epoch tool." 29-Jun.10:12 smg export sync from replica "boston_hub" to replica "sanfran_hub" "Exported synchronization information for replica "sanfran_hub". Row at export was: boston_hub=149 sanfran_hub=115" ...
To list the imports at your current replica, use the following command:
cleartool lshistory replica:current-replica-name@vob-selector
For example, to list imports at the replica boston_hub in the family /vobs/dev:
cleartool lshistory replica:boston_hub@/vobs/dev 25-Jun.11:46 smg import sync from replica "sanfran_hub" to replica "boston_hub" "Imported synchronization information from replica "sanfran_hub". Row at import was: boston_hub=149 sanfran_hub=112" 10-Jun.12:36 smg import sync from replica "sanfran_hub" to replica "boston_hub" "Imported synchronization information from replica "sanfran_hub". Row at import was: boston_hub=136 sanfran_hub=111"