This technote explains how to resolve a failure that can occur when using IBM® Rational® ClearCase® (CC) Project Explorer, which fails with an "Assertion Failed!" when opening streams in IBM Rational ClearQuest® -enabled UCM projects.
After upgrading to ClearCase 126.96.36.199 or 188.8.131.52 , the ClearCase Project Explorer may fail with the following error when opening a stream in a ClearQuest-enabled UCM Project:
Expression: i < length()
For information on how your program can cause an assertion failure, see the Visual C++ documentation on asserts
(Press Retry to debug the application - JIT must be enabled)
This error occurs only when using existing streams in CQ-enabled projects. A newly-created stream in the same project as the failing streams does not have this issue. A newly created project, whether CQ enabled or not, does not have this issue.
You could also see the following error for this issue where the message in this case does not indicate Assertion failed!:
Caption: Microsoft Visual C++ Runtime Library
This application has requested the Runtime to terminate in an unusual way.
Please contact the application's support team for more information.
The issue is caused by what is known as "skew" between the ClearCase PVOB and the ClearQuest User Database. If any of the linked ClearQuest Records are missing the stream_object_id OR if the ClearQuest record ID and ClearCase Activity ID do not match, this will happen.
This issue has been identified as a product defect in ClearCase Project Explorer under APAR PK72895.
Resolving The Problem
Defect APAR PK72895 has been resolved in the following ClearCase updates:
Fix Pack 184.108.40.206
Fix Pack 220.127.116.11
Until the issue is resolved in the Project Explorer, the following steps can be taken to resolve the data issues causing the crash:
cleartool checkvob -ucm -fix -force -crm_only project:<Failing Project Name>@\PVOB
cleartool checkvob -ucm -fix -crm_dbname <CQDB> -project <UCM_Project_Record_Name>
Was this topic helpful?
29 September 2018