IBM Support

cleartool find vob / -kind [oid|dbid|login|sibrep|wko] reports error: Can't get objects of type **null meta type**

Troubleshooting


Problem

This technote explains an issue that can occur where an error, Can't get objects of type **null meta type**, is reported when running the IBM Rational Cleartool find command with the -kind arguments [oid|dbid|login|sibrep|wko].

Symptom

$ cleartool find tools / -type f -kind [oid|dbid|login|sibrep|wko] -print
db_next_objs_V3: RPC: Unable to receive; errno = Connection reset by peer
cleartool: Error: Trouble communicating with VOB database: "/vobs/tools".
Check database log on VOB host "hostn".
db_abort_trans_V3: RPC: Unable to receive; errno = Connection reset by peer
db_next_objs_V3: RPC: Unable to receive; errno = Connection reset by peer
cleartool: Error: Trouble communicating with VOB database: "/vobs/tools".
Check database log on VOB host "hostn".
cleartool: Error: Can't get objects of type **null meta type** (0) from VOB: error detected by ClearCase subsystem

Command examples that will cause the issue:

/usr/atria/bin/cleartool find <dir> -type <type> -kind oid -print
/usr/atria/bin/cleartool find <dir> -type <type> -kind dbid -print
/usr/atria/bin/cleartool find <dir> -type <type> -kind login -print
/usr/atria/bin/cleartool find <dir> -type <type> -kind sibrep -print
/usr/atria/bin/cleartool find <dir> -type <type> -kind wko -print

[{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Cleartool","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"},{"code":"PF027","label":"Solaris"}],"Version":"7.1.0.2;7.1.0.1;7.1;7.0.1.7;7.1.1;7.0.1.6;7.0.1.5;7.0.1.4;7.0.1.3;7.0.1.2;7.0.1.1;7.0.1;7.0.0.8;7.0.0.7","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
16 June 2018

UID

swg21419816

Page Feedback