IBM Support

After successful "atomic" checkin, subsequent non-atomic checkins fail



Attempts to perform subsequent IBM Rational ClearCase "atomic" checkin operations on element types derived from the binary_delta_file type (binary_delta_file, html, rose, rosert, xde, xml, or any element type you have created) results in the error "create_version: Error: Invalid pred_branch_oid".


The full error message is as follows:

create_version: Error: Invalid pred_branch_oid "f55a41f7.60a74575.96a9.72:4e:0e:42:07:07" (\atria\lib\mgrs\binary_delta\bdtm.c:547)
cleartool: Error: Type manager "_xml2" failed create_version operation.
cleartool: Error: Unable to check in "sample.xml".


This issue has been identified as a product defect under APAR PM10686.

Diagnosing The Problem

The "cleartool checkvob" command run on an element will produces messages like:

cleartool: Warning: Unexpected pool directory for container "36\31\0-8cd57c1ea6974c738a758b4f0f0b6ece-77" : should be "0\c\"

The "cleartool checkvob" cannot repair the condition.

Resolving The Problem

The defect has been resolved in Rational ClearCase


Avoid using the new atomic checkin feature (disable it with "cleartool protectvob -natomic") until a fixpack can be distributed that resolves this issue.

For any files that have already been affected, run the cleartool chtype command and change them to a different element type, and then back to the appropriate element type.

For example:
cleartool chtype file sample.xml

cleartool chtype xml sample.xml

[{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"VOB","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.1.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018