Question & Answer
Question
Are there any troubleshooting steps I can use to help ascertain why attempts to export an IBM® Rational® ClearCase MultiSite® update packet on Microsoft® Windows®, UNIX® or Linux® results in the error, multitool: Error: Unable to construct version?
Answer
Example:
# multitool sync -export -fship rep1@/vob1
Generating synchronization packet /usr/atria/shipping/ms_ship/outgoing/sync_12-Aug-04.18.24671_1
- shipping order file is /usr/atria/shipping/ms_ship/outgoing/sh_o_sync_12-Aug-04.18.24671_1
multitool: Error: Operation "construct_version" unavailable for manager "_xtools2"
(Operation pathname was: "/opt/rational/clearcase/lib/mgrs/_xtools2/construct_version")
multitool: Error: Unable to construct version.
multitool: Warning: Failed 1 time(s) to create cltxt file for version with oid: a4d7c451.7a5b4ee4.95fd.9b:a3:0f:2c:e1:3e. Maybe retrying...
multitool: Error: Operation "construct_version" unavailable for manager "_xtools2"
(Operation pathname was: "/opt/rational/clearcase/lib/mgrs/_xtools2/construct_version")
multitool: Error: Unable to construct version.
multitool: Warning: Failed 2 time(s) to create cltxt file for version with oid: a4d7c451.7a5b4ee4.95fd.9b:a3:0f:2c:e1:3e. Maybe retrying...
multitool: Error: Operation "construct_version" unavailable for manager "_xtools2"
(Operation pathname was: "/opt/rational/clearcase/lib/mgrs/_xtools2/construct_version")
multitool: Error: Unable to construct version.
multitool: Warning: Failed 3 time(s) to create cltxt file for version with oid: a4d7c451.7a5b4ee4.95fd.9b:a3:0f:2c:e1:3e. Maybe retrying...
multitool: Error: Could not get statistics of the version data file for this operation.
34063018:
op= mkbranch
replica_oid= 465b4044.3afd11d6.b7de.00:01:80:f0:0d:71
oplog_id= 3440170
op_time= 12-Aug-04.18:15:08UTC
create_time= 12-Aug-04.18:15:08UTC
version_oid= a4d7c451.7a5b4ee4.95fd.9b:a3:0f:2c:e1:3e
event comment= ""
data size= 224 data= 0xb8d48
------------
elem_oid= 2656b171.9fd34e1a.8aeb.bd:c0:df:de:68:86
branch_oid= de031ac7.6e7b4ad5.af9a.d0:ae:18:fc:c2:6a
branch_fstat= ino: 0; type: 2; mode: 00; uid: 4294967294; gid:
4294967294
nlink: 2; size: 0; blsz: 1024; blks: 0 fsid: 0; rdev 0
atime: Wed Dec 31 19:00:00 1969
mtime: Thu Aug 12 14:15:08 2004
ctime: Thu Aug 12 14:15:08 2004
brtype_oid= 983760b5.0dc84539.ba75.ef:13:a7:25:5c:50
from_ver_oid= 93f61907.3d294c9c.9cef.19:1c:bb:29:3b:ed
zero_ver_oid= a4d7c451.7a5b4ee4.95fd.9b:a3:0f:2c:e1:3e
zero_ver_fstat= ino: 0; type: 1; mode: 00; uid: 4294967294; gid:
4294967294
nlink: 0; size: 0; blsz: 1024; blks: 0 fsid: 0; rdev 0
atime: Wed Dec 31 19:00:00 1969
mtime: Thu Aug 12 14:15:08 2004
ctime: Thu Aug 12 14:15:08 2004
mkelem_master= FALSE
multitool: Error: Synchronization update terminated prematurely due to error -- aborting.
TROUBLESHOOTING TIPS:
- Check the type manager map file on the system to make sure that the file type which the error message is complaining about actually exists.
Note: In this example, the following error references the file type _xtools2:
multitool: Error: Operation "construct_version" unavailable for manager "_xtools2"
UNIX/Linux: /opt/rational/clearcase/lib/mgrs (Look for a subdirectory called _xtools2 in this example.)
Windows: C:\Program Files\Rational\ClearCase\lib\mgrs\map
Recommendation: If the type manager is not found, you will need to install it. This is done by either reinstalling the product (if a default type manager is missing) or is done by installing a customer type manager.
Note: This problem is most commonly seen when moving VOBs to a new server and the custom type manager was not installed on the new server. The instructions required to configure the client will depend on the customization in place within your environment; IBM Rational support cannot provide support for creating and maintaining customized type managers.
- To determine the element version that is having the problem, set to a view, cd into the exporting VOB and dump the oid listed as the "version_oid" line from the syncreplica output . cleartool dump oid:<oid> will identify the element version.
From the error above you would run:
cleartool dump oid:a4d7c451.7a5b4ee4.95fd.9b:a3:0f:2c:e1:3e.
Example:
%> cleartool dump oid:b2d758.cf8331.9182.d7:e8:e3:09:44:1d
oid:b2d7a858.cf824331.9182.d7:e8:e3:09:44:1d
/vobs/myvob/blah.txt@@/main/mybranch/0
oid=b2d7a858.cf824331.9182.d7:e8:e3:09:44:1d dbid=122 (0x7a)
<…omitted output…>
source cont="/host/vob.vbs/s/sdft/1e/0-b2d758cf83319182d7e8e309441d-hx"
clrtxt cont="/host/vob.vbs/c/cdft/28/7/b2d758cf83319182d7e8e309441d"
Recommendation: If the version is in the lost+found directory, decide whether or not it is needed. If you wish to keep it, move (cleartool mv) the version to the directory in which you want it to reside; otherwise remove (cleartool rmelem) the file. If removed, you can run multitool syncreplica -export again otherwise continue with the steps below.
Review technote 1120317 for more details about the lost+found directory.
- Check if cleartext can be generated for the version in question:
UNIX or Linux: %> cat blah.txt@@/main/mybranch/0
Windows: %> type blah.txt@@\main\mybranch\0
If the following (or similar) errors appear, the problem is likely caused by some kind of corruption of the source container for the element.
mvfs: ERROR: view=my_view@@ vob=/vobs/myvob - ClearCase vob error
see view_log on host myhost for more info
fetch cleartext view=my_view@@ vob=/vobs/myvob=0x395e - I/O error
wc: cannot open myfile.txt@@/main/mybranch/0
Error in view_log on myhost:
05/02/02 10:54:32 view_server(14871): Error: text_file_delta: Error: Specified version does not exist
For instructions on replacing a source container from backup review technote 1221899.
Recommendation: If cleartext can be generated and the other tips did not help, contact support for assistance to help determine the yet to be documented cause.
Related Information
Was this topic helpful?
Document Information
Modified date:
29 September 2018
UID
swg21190274