cleartool error: Not a vob object when recommending a baseline

When creating a baseline for a stream, it reported the following error message and failed. The cause is that the recommend baseline is removed and the stream cannot find it.

M:\qinl_NewMainline_int>cleartool chstream -rec NewMainline_10_12_2007.1228 NewMainline_i@\CBFEProjects
cleartool: Error: Not a vob object: "291fb10e.71e711dc.8fad.00:01:83:f9:3b:ad".
cleartool: Error: Unable to get current recommended foundation for stream "NewMainline_i".
cleartool: Error: Unable to set the recommended baselines for stream "NewMainline_i".
cleartool: Error: Unable to change all streams.

Solution. un-recommend baseline in the stream, and recommend a good baseline.

M:\qinl_NewMainline_int>cleartool chstream -nrec NewMainline_i@\CBFEProjects
Changed stream "NewMainline_i@\CBFEProjects".

M:\qinl_NewMainline_int>cleartool chstream -rec NewMainline_10_12_2007.1228 NewMainline_i@\CBFEProjects
Changed stream "NewMainline_i@\CBFEProjects".

fetch cleartext error - No permission match

After restore VOBs to another ClearCase server, some VOBs reported the following error message when trying to access (read) the contents.
...
fetch cleartext view=BUILD_CBFE13.3_d vob=/vobs/MidTier dbid=0x16f - No permission match
fetch cleartext view=BUILD_CBFE13.3_d vob=/vobs/MidTier dbid=0x173 - No permission match
fetch cleartext view=BUILD_CBFE13.3_d vob=/vobs/MidTier dbid=0xdf - No permissi match
...

A "cleartool desc" command found out that the original additional group cbfedev disappeared. To add the additional group, "cleartool protectvob -add_group" command ran without error. However the result showed that the additional group was not added to the VOB.

Solution.

$ cd /ccstorage/vobs/MidTier.vob
$ cd .identity
$ ls
gid group.500 uid
$ rm group.500
rm: group.500: override protection 410 (yes/no)? y
$ cleartool protectvob -add cbfedev /vobs/MidTier

Run "cleartool desc" again, the result showed that the group had been added to the VOB. And the fetch cleartext error was gone as well.

$ cleartool desc -l vob:/vobs/MidTier
...
VOB ownership:
owner cbfedev.cibc.com/ccadmin
group cbfedev.cibc.com/clearcase_cbfe
Additional groups:
group cbfedev.cibc.com/cbfedev
...

Fix Views after Upgrading ClearCase Client

After upgrading ClearCase client from 2003.6 to 7, my local snapshot view report the following error when accessing it.

C:\ccase\views\qinl_rel14.0>cleartool update
cleartool: Error: Operation "view_get_prop(VIEW_PROP_WEBVIEW)" failed: view storage directory or control files unavailable --
additional information may be present in the view server host's view log.
cleartool: Warning: Unable to open snapshot view "C:\ccase\views\qinl_rel14.0".
cleartool: Error: 'C:\ccase\views\qinl_rel14.0' is not a valid snapshot view path.

The cause is the during ClearCase upgrade, the albd service account id and group id also changed. If the ClearCase administrators group name has changed or you have moved a view to a new domain that has a different SID for this group, then the -replace_server_process_group switch is required for fix_prot utility.

Kill the view_server process first. Then run,

C:\ccase\views\qinl_rel14.0>"C:\Program Files\Rational\ClearCase\etc\utils\fix_prot" -replace_server_process_group c:\ccase\view_stg\qinl_rel14.0.vws
Re-protect "c:\ccase\view_stg\qinl_rel14.0.vws"? [no] y
Reprotection complete.

Remove the view shortcut, and added back again. Everything is back to normal.

C:\ccase\views\qinl_rel14.0>cleartool lsview -l qinl_rel14.0
Tag: qinl_rel14.0
Global path: \\Cbad4-xcidh3\view_stg\qinl_rel14.0.vws
Server host: Cbad4-xcidh3
Region: windows
Active: NO
View tag uuid:9396be72.f06c41d3.9db4.a4:68:8d:06:15:e9
View on host: Cbad4-xcidh3
View server access path: C:\ccase\view_stg\qinl_rel14.0.vws
View uuid: 9396be72.f06c41d3.9db4.a4:68:8d:06:15:e9
View attributes: snapshot
View owner: AD\qinl