We have used relocate a number of times to reorganize our projects, and to
distribute load to more servers. If VOB size (i.e. disk consumption) is not
the issue, I would always go for a "relocate -update". It kind of eases the
problems with view private files, and DOs. The major advantage of using
"-update" is that old releases aren't damaged - which can happen with the
"real" relocate. You have to make sure that elements in the original
location are locked obsolete, though. You also have to set the symbolic link
to the new location manually. With these two precautions taken, our VOB
splitting scheme worked out very well. We are currently also a "pure" NT
shop =;-).
Cheers, Axel.
> -----Ursprüngliche Nachricht-----
> Von: owner-cciug@rational.com [mailto:owner-cciug@rational.comIm
> Auftrag von Daigle, Sheldon
> Gesendet am: Donnerstag, 21. September 2000 17:44
> An: cciug@rational.com
> Betreff: [cciug] cleartool relocate command
>
>
> I've been lucky to have never had to do this command, but my luck has out.
> One of our VOBs has grown out of control and the VOB server comes to it's
> knees daily. I know it's time to split this VOB up.
>
> Can some of you who have done this before please share what
> problems you've
> had, what to look out for, what not to do, etc? I know view private files
> can get stranded, derived objects get burned so I'd like to know the best
> way to handle all this stuff.
>
> BTW - This is a complete Windows NT environment; VOB servers and client
> machines. We have no UNIX systems accessing ClearCase.
>
> Thanks,
> Sheldon Daigle
> Unisphere Networks
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:26:45 EDT