27.5 Renaming a VOB or View Host

If you rename a host that holds the physical storage for one or more VOBs or views, the existing registry entries for those VOBs and views become invalid. Until you re-register those VOBs and views and replace their old tags, the VOBs and views will be inaccessible. From the registry perspective, the rename-host procedure is quite similar to the move-storage-directory procedures described in Chapter 12, Moving VOBs and Chapter 21, Moving Views.

1. Make sure that the storage directories are not being used. If the host is home to one or more VOBs, make sure that all clients unmount those VOBs (cleartool umount). If the host is home to one or more views, terminate all processes using the views.

2. Shut down ClearCase on the host.

3. Rename the host. Make the change using the vendor-supplied procedure or tool. In most cases, this involves a restart of the operating system, which also restarts ClearCase processing. In any event, make sure that ClearCase processing is restarted on the host.

NOTE: If the host is a license or registry server host, you must reconfigure the host's clients to know its new name.

4. Create new registry entries for each VOB and view on the host. Use register -replace to update object registry entries, use mktag -replace to update tag entries, and use mkstgloc to update server storage locations.

5. Update view information in VOBs as needed. If any dynamic views have their storage directories on the host, you must update the information that each VOB keeps about dynamic view storage directory locations. To do this, use each dynamic view on the renamed host to check out a single element from each VOB that the view has ever accessed. You can cancel the checkout (uncheckout) immediately if you want.