Raising the replica feature level

This topic describes how to raise the feature level for a single replica.

There is an important rule related to raising a replica's feature level: if the current family feature level is less than or equal to 1, the first replica in a VOB family whose feature level is raised must be the replica that masters the VOB object.

To raise the replica feature level:

(This step is unnecessary if the feature level is greater than 1.) After installing the new version of DevOps Code ClearCase® on a server host, determine which replica masters the VOB object:
```
cleartool describe vob:vob-tag
```
If the replica whose feature level you want to raise first does not master the VOB object, you must transfer mastership of the VOB object:
1. Change mastership of the VOB object:
```
multitool chmaster replica-name vob:vob-tag
```
2. Export an update packet to the replica whose feature level you want to raise:
```
multitool syncreplica –export –fship replica-name@vob-tag
```
3. At the receiving replica, import the packet:
```
multitool syncreplica –import –receive
```

Determine whether the replica is self-mastering:


cleartool describe replica:replica-name@
vob-tag

If the replica is not self-mastering, convert it to a self-mastering replica. See Transferring mastership of a replica object.
Raise the feature level of the replica. Enter this command on the replica host:
```
cleartool chflevel –replica feature-level replica:replica-name@vob-tag
```
Export update packets to all other replicas in the VOB family to inform them about the feature level change.
Optional: Change mastership of the replica back to the original master replica.