What to do when cleartool rmview -uuid does not remove view references

How can referenced checkouts in an IBM® Rational® ClearCase® VOB be removed when the command, cleartool rmview -uuid, fails to clear the references as expected?

Cause

In ClearCase 7.0, defects APAR PK38852 and APAR PK50737 have been submitted to address the concern of rmview -uuid not removing all the references from the view. This behavior has been reported to occur when issuing cleartool rmview with or without the -uuid switch. Example error related to this symptom: Attempts to remove a view results in the following error: %>cleartool rmview -force -vob /vobs/test -uuid c05adaeb.45aa11da.92b5.00:01:80:f7:8d:2c cleartool: Warning: Looking for a broken Config Record that might still have some references to the view. This might take a long time depending of the number of derived objects and configuration records within the VOB. As a progress indicator, the total number of processed derived objects will be reported for approximately each 200 processed derived objects. cleartool: Error: Some view references are still left in the VOB. cleartool: Error: Trouble removing references to view Cause 2 The uuid typed in the command syntax is incorrect. Cause 3 In ClearCase 2003.06 defect APAR PK45597 has been opened to address the issue described below: When attempting to remove view references from a PVOB using cleartool rmview -uuid, a silent failure (with the tool claiming a successful removal) will occur if the view is associated with a UCM stream or activity mastered at a remote replica.

Answer

Defects APAR PK38852 and APAR PK50737 have been resolved in the following ClearCase 7.x updates; however, the update alone will not resolve the issue. The solution will not be complete until the updates are applied and the environment variable below is configured on the proper hosts. Note: The solution was implemented in this fashion to prevent unknown RPC calls being received by a lower versioned VOB or View server that would fill up with error logs regarding the unknown RPC calls. The following steps are required in order to eliminate the view removal issues. Upgrade the VOB server and any host which will run the rmview command to the applicable ClearCase 7.x updates identified below Windows 7.0.1 7.0.1.0-RATL-RCC-IFIX01 7.0.1.0-RATL-RCCLT-IFIX01 7.0.0.1 7.0.0.1-RATL-RCC-IFIX04 7.0.0.1-RATL-RCCLT-IFIX04 UNIX/Linux 7.0.1 7.0.1.0-RATL-RCC-IFIX01 7.0.1.0-RATL-RCCLT-IFIX01 7.0.0.1 7.0.0.1-RATL-RCC-IFIX04 7.0.0.1-RATL-RCCLT-IFIX04 After the upgrade, the following environment variable (EV) must be set on the host where the rmview command is to be run: CLEARCASE_RMVIEW_CR_FIX = 1 Use standard operating system and or shell script syntax to set the variable. Note: If you are running the rmview command from the VOB server, the variable is still required to be set on the host. IMPORTANT: Do not use the -all option if you use the -uuid option unless ALL of your VOB servers are on the required fix mentioned above and have the variable set. 2003.06.00 Host Considerations There are no updates for 2003.06.00 servers or clients experiencing this issue. If your VOB server is at version 2003.06.00, you will need to upgrade to the versions above and follow the steps aforementioned. If you have a mixed environment of 2003.06.00 clients and 7.x servers (regardless of where your views are stored), you must update the 7.x VOB server, set the variable on the VOB server and run the rmview command from the VOB server. Running the rmview command from a 2003.06.00 client will not produce expected results related to the solution of this issue. WORKAROUND 1: To prevent this issue from occurring on Microsoft® Windows®, try using the graphical remove view functionality, instead of the command line interface as this issue is only known to occur with cleartool rmview with or without the -uuid switch. WORKAROUND 2: If after running the instructions described in technote 1122515 the VOB still holds checkouts to your dynamic views, attempt to run recoverview on the referenced view as instructed in technote 1127003. WORKAROUND 3: If 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 by using the following command: cleartool unreserve -view Review technote 1129391 for more information. Solution 2 Be sure to check the spelling of the UUID in the command. Given that this is a specific string that must be entered exactly as seen, it is best to copy and paste the uuid, rather than typing it manually. Solution 3 There is no solution for APAR PK45597 at this time. This issue will not prevent the removal of the view itself from the view server, but the references to the view will still be left in the PVOB's database. Workaround: The view can be removed using cleartool rmview -uuid at the site that masters the stream and/or activity the view is associated with. Determining the stream in question will be non-trivial unless view and stream names share a common naming convention (which is the default when joining a project).