Trouble removing view references from a replicated VOB using rmview -uuid -vob command

After running the IBM® Rational® ClearCase® describe -long command, why are several VOB holds objects from the following views messages displayed even after using the cleartool rmview -uuid command to remove the references?

Cause

Review technote 1122515 for more information on the rmview -uuid command and it usage. The objects being referred to are most likely derived objects (DOs). When a DO is accessed by a view, two references are made in the VOB: One reference is specific to the DO The other is a general reference to the view. If the view is improperly removed in this situation, the above scenario can occur. The DO-specific reference to the view can be removed with the cleartool rmview -uuid command, but the other general reference cannot (even though the VOB is no longer really holding a reference to that view). Defect RATLC00588487 has been logged against this behavior.

Answer

This defect has been fixed in the following 2002.05.00 ClearCase patches. Microsoft® Windows® clearcase_p2002.05.00.NT-15 Linux and UNIX® clearcase_p2002.05.00-15 The patch above corrects a defect that could cause config records to be lost in a view. This could also cause internal errors when examining hierarchical config records (diffcr -flat or diffcr -recurse), and could also cause rmview to fail with an internal error when attempting to remove views that had lost config records. If the checkout/checkin to the deleted view is blocking your work, the existing checkout can be converted to UNRESERVED by the element owner or VOB owner using the following command: cleartool unreserve -view Review technote 1129391 for more information.