UPDATE: Technical Bulletin #29

New Patches Available to Resolve rmview Performance Issues for 3.1.1 and 3.2

ClearCase patches clearcase_p3.2-27, clearcase_p3.2.NT-31, and clearcase_p3.1.1-69 have been issued to provide improved performance for rmview.

The above patches also fix problems addressed by recalled patches clearcase_p3.2-26 and clearcase_p3.1.1-66. These recalled patches were originally issued to provide improved performance for rmview without the problems associated with some earlier patches, but it was found that they introduced 2 new defects:

• #27758--clearmake core dump (GNU compatibility was not expanding wildcards when evaluating a target-list of rules)
• #28179--findmerge core dump (findmerge -merge would core dump or get a bad dbid)

The earlier patches, which have also been recalled, are clearcase_p3.2.NT-19, clearcase_p3.2.NT-24, clearcase_p3.2-13, clearcase_p3.2-17, and clearcase_p3.2-19, and were issued in response to Rational defect #26668. These patches introduced a defect (#27932) into standard ClearCase behavior. The correct result of the rmdo command is for the configuration record (CR) to be deleted when the derived object (DO) pointing to it is removed, in such a way that the deleted CR can never be retrieved.

The bug in the earlier patches allowed a deleted CR to be retrieved after you issued an rmdo command. This re-appearance of a CR which should not have been accessible could introduce inconsistency into your VOB database.

The new patches, in addition to improving rmview performance, fix defect #27932, specifically:

• They prevent a deleted ("stranded") CR from ever being accessible for retrieval
• If use of an earlier patch incorrectly retrieved a CR, they prevent that CR from ever being re-used, and automatically cause that CR to be permanently deleted the next time you use ClearCase to remove a DO (by using a command like rmview or rmdo from within ClearCase).

Once again, we at Rational apologize for delays in fixing this problem.

Any Questions?

Please contact Rational Support

UPDATE: Technical Bulletin #29 - 23 Jul 1998