Question & Answer
Question
Why are you unable to change the properties of IBM® Rational® ClearCase® element types in a MultiSite® replicated VOB after their creation and how can you create a new element type with the properties you desire using the same element type name?
Cause
In a replicated VOB modifying an element type is prohibited in order to avoid divergence issues.
SCENARIO 1: Changing unused element types in a replicated VOB
You are unable to change the properties of a ClearCase element type in a MultiSite replicated VOB after its creation and wish to create a new element type using the same element type name provided the element type has not been used.
Example
- GUI
- Command Line
- GUI
- Command Line
- GUI
- Command Line
You created a new element type in a replicated VOB with incorrect parameters. Note: Although the example is run on Windows, the same is true on UNIX and Linux. Create a new element type in a replicated VOB Note: The default Merge type was used. Created element type "test_type". Ooops. You meant to create the element type using the Merge type Never or you attempted to create a custom element type from the GUI. Attempts to change the element type results in an error due to this restriction: cleartool: Error: Can't redefine element types when VOB is replicated. cleartool: Error: Unable to replace definition of element type "test_type".
Attempts to remove the element type results in an error due to this restriction: cleartool: Error: Can't delete element types when VOB is replicated. cleartool: Error: Unable to remove element type "test_eltype". Note: The ClearCase MultiSite Administrator's Guide and the ClearCase Reference Guide on the topic of rmtype (cleartool man rmtype) document that the removal of element types in a replicated VOB is prohibited in order to avoid divergence. |
SCENARIO 2: Changing used element types in a replicated VOB
You are unable to change the properties of a ClearCase element type in a MultiSite replicated VOB after its creation (and use) and wish to create a new element type using the same element type name. Information about the steps necessary to change existing elements in the VOB to use the newly created element type are also discussed.
Example | ||||||
|
Answer
The only alternative is to create a new element type that has the features you wish to utilize.
FOR SCENARIO 1:
IMPORTANT: The assumption here is that the element type was created in a replicated VOB incorrectly. Attempts to make any corrections after the element type is created will fail due to the restriction. This workaround assumes that the element type has not yet been used.
** If you have already used the element type in your replicated VOB and wish to change the element type properties, follow the instructions in Scenario 2.
WORKAROUND:
The following workaround can be used to create a new element type in a replicated VOB using the same name of an existing element type.
- Rename the <incorrect> element type
Note: Review the ClearCase Command Reference Guide on the topic of rename (cleartool man rename) for more information.
- Lock -obsolete the <incorrect> element type
Note: Review the ClearCase Command Reference Guide on the topic of lock (cleartool man lock) for more information.
- Create the new element type with the same name
Note: Review the ClearCase Command Reference Guide on the topic of mkeltype (cleartool man mkeltype) for more information.
- Replicate to ALL sites in the family
Note: Review the MultiSite Command Reference Guide on the topic of syncreplica (multitool man syncreplica) for more information.
Example
| ||||||||
IMPORTANT: The assumption here is that the element type was created in a replicated VOB correctly, was associated to elements and then later changes needed to be made. Attempts to make any corrections after the element type is created will fail due to the restriction. This workaround assumes that the element type is currently in use. ** If you have NOT already used the element type in your replicated VOB and wish to change the element type properties, follow the instructions in Scenario 1.
|
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21148740