I am not able to add Connectors VOB to my load rules. Getting this CCRC Error when loading connectors.
getting error like :
Clearcase CM Server :Error :Unable to determine version for VOB root
directory
Clearcase CM Server :Error :Unable to access
"\Connectors":No such file or directory.
Clearcase CM Server:Error :1 config spec load rule problems
encountered
It cannot access that folder because:
either \Connector is not a vob tag
or that vob tag is never selected by the selection rules of the snapshot view config spec (for instance, there would not be any element * /main/LATEST)
Related
Working in Red Hat Linux trying to build RPMs that are accessed via Clearcase vobs but keep on getting a recurring error which states, 'unable to find albd-server on host ', 'Unable to contact view - clearcase object not found' and 'Unknown host - Name or service not know'. Any guidance would be much appreciated.
I solved the issue in the end by using clearmake -V in the makeall script. Because I'm working with shareable DOs this enabled me to avoid winking in between views. Thankfully it built successfully this time but instead of it being in the build error log it appeared as a test failure. Thanks for the help.
Check first the vobrpc_server_log on the ClearCase Vob Server.
As seen in this technote (for an older version of ClearCase, but still relevant)
Attempts to mount a VOB results in the following error:
ClearCase Object Not Found
This error may get reported in the VOBRPC error log:
01/06/2006 09:24:34 vobrpc_server(5016): Error: vobrpc_server.exe(5016):
Error: Unable to get VOB tag registry information for replica uuid
"db7983f9.052d498a.915f.bb:f9:0e:b0:b4:ea":
ClearCase object not found
This error may get reported in the vob_scrubber log:
vob_scrubber: Error: Unable to get VOB tag registry information
for replica uuid "db7983f9.052d498a.915f.bb:f9:0e:b0:b4:ea":
ClearCase object not found
This error will occur when trying to mount the VOB before the VOB tag creation is complete.
This would be due to a timing issue where the cleartool mkvob and cleartool mount operations are done via a script, and maybe a longer pause is required before the VOB is mounted on a remote host.
This would also be true in an environment where the VOB creation takes several moments to complete, and there is an extended period before the VOB tag is available for users to mount.
Note: This does not occur as a result of the cleartool mount that is executed automatically during the cleartool mkvob operation.
Cause 2: The VOB tag may still exist even though the VOB storage (or VOB server host) are no longer available in the ClearCase network.
This will happen as a result of improper removal of the VOB storage.
Cause 3: The server storage location (network share or export) is not available.
When mounting a VOB, the location that the VOB is stored must be accessible from the host that you are trying to mount the VOB.
Cause 4: If the VOB is not yet tagged in the primary region of the VOB server.
This is applicable to environments that have multiple registry regions.
Is this a clearmake build? Does it complete? (Winkin and shopping failures USUALLY don't cause a build failure.) What is printing those errors? Clearmake? Another ClearCase tool?
What is the exact version of ClearCase? If 9.0.1.x, the patch level and your license type may matter, as some older 9.0.1.x releases had an issue where you would get "extra" errors if you had albd contact failures and you use Rational Common Licensing.
This is a follow on from op - Moving Vobs between Win and AIX
Due to the aix and win vob servers sharing resources (common CC reg & Common Admin PVOB on the Aix box) we need to amalgamate these vob servers onto the AIX server as a precursor to our ultimate move to new servers at CC8.
on the Win VOb Server we have locked the vob, run vob_siddump then a reformat dump of the vob.
Then using xcopy we copied the dumped vob.vbs from Windows to AIX vob server run the fix_prot on the new server.
But when we run the reformatvob -load it goes through it's steps Shows "Loader Done" then shows the following errors
Error from vob database /vobstore/vobs/vobname.vbs.
Error Trouble Opening the VOB Database /vobstore/vobs/vobname.vbs,
Error Trouble Loading versioned object base /vobstore/vobs/vobname.vbs.
Because of the shared registry is this due to the existing registry entry and we need to unregister and then rmtag before registering and tagging fresh or do we need to do anything further?
Clearcase logs on aix vob server show:
DB Log - Error process not running on registery specified hostname (old win vob server)
Vob Log - shows unix UID and GID messange and Warning unable to verify mount options in vob tag registry Clearcase Object not found
David, there are a few things you need to do here:
unregister the VOB and remove all the tags that refer to the old server
reregister and retag the vobs at the new location.
If you can't register the VOB, run fix_prot -r -root ... to reset the ownership and try again.
run vob_sidwalk to remap object ownership.
run it again with -recover_filesystem to reset container ownership. Alternatively run checkvob -pool -protections -fix -force {vob storage dir}.
The last step really needed to be started on the Windows side before this started. Essentially, you needed a sid dump file to turn into the map file that the sidwalk needs (unless you want to remap everything to the VOB owner...)
The complete procedure to follow is at Moving VOBs between Operating system types You may want to start fresh from there if you still have the VOB located in the old location.
Following is the error while using ClearCase version 7.1.2.6 on windows site. Any suggestions how to fix it.
cleartool ls
cleartool: Warning: Can not update license cache
"C:\Program Files (x86)\IBM\RationalSDLC\ClearCase\var\cache\ClearCase_check\desker".
Please check ownership or permission.
What could cause this error message?
This is similar to PM09741:
Problem summary
ClearCase licensing does not handle account user-ID changes without user name changes.
That means something has changed (like the license server name)
I'm working with ClearCase 8 to test integration with my company's software, and I will be using the client and server software on the same machine, so I don't need the test VOBs I create to be accessible over the network. I'm trying to create a VOB on a local disk, rather than a network share, but I can't seem to figure out how to do it, if it is even possible.
First, I tried just using a regular path, e.g.:
cleartool mkvob -tag \vobFoo C:\Users\Public\cc_vobs\vobFoo.vbs
cleartool: Error: storage directory must be in UNC style (e.g. \\host\share\...)
After finding this question, my next attempt was this:
cleartool mkvob -tag \vobFoo \\localhost\c$\Users\Public\cc_vobs\vobFoo.vbs
cleartool: Error: Attempt to get location information on "\\localhost\c$\Users\Public\cc_vobs\vobFoo.vbs" failed: Invalid argument.
I checked - typing \\localhost\c$\Users into the "Run..." menu does bring up the proper folder in Windows Explorer, so I don't think it's an issue with the loopback adapter.
I did find some references to the error message here and here, but neither seems applicable to my situation (I'm not using UNIX and ClearCase Doctor doesn't give me the relevant error message)
Even after setting up a Windows share, this also failed:
cleartool mkvob -tag \vobFoo \\localhost\cc_vobs\vobFoo.vbs
cleartool: Error: Attempt to get location information on "\\localhost\cc_vobs\vobFoo.vbs" failed: Invalid argument.
The only way I could get the command to go through was to use the network host name with the share:
cleartool mkvob -tag \vobFoo \\hostname\cc_vobs\vobFoo.vbs
Is it simply not possible to setup a VOB in a local storage location like I'm trying to do? Or am I missing something?
I confirm that your UNC path cannot use localhost, but must start with the host name.
The reason is that the Vob storage path must be globally accessible, ie accessible from any computer (and localhost makes sense only from one computer).
The cleartool mkvob man page includes:
Windows—vob-storage-pname must be a UNC name.
UNC (Uniform Naming Convention):
The Microsoft Windows UNC, short for Universal Naming Convention or Uniform Naming Convention, specifies a common syntax to describe the location of a network resource, such as a shared file, directory, or printer. The UNC syntax for Windows systems has the generic form:
\\ComputerName\SharedFolder\Resource
Microsoft often refers to this as a "network path".
One way for you to have a local path (without having to define a share) is to use the -stgloc parameter, referring to the name of a pre-defined storage location (instead of -host -hpath -gpath arguments)
See cleartool mkstgloc (which defines storage locations for Vobs or Views).
You can use a local path there.
In many cases, ClearCase heuristically derives appropriate accessibility information from the stgloc-pname argument.
In cases where there is no file system connectivity between the server storage location and its clients, ClearCase derives the host name and host-local path, but because no meaningful global path can be derived, you must specify -ngpath to unset the global path information.
To create a server storage location for snapshot views or for VOBs intended to be accessed only through snapshot views, use these options:
-host -hpath -gpath when there is file system connectivity between the server storage location host and its clients.
-ngpath -host -hpath when there is no file system connectivity between the server storage location host and its clients.
So be careful if you do this (-ngpath option): your Vob won't be accessible through dynamic views, only snapshot views.
I have already created my project views from the Rational Clearcase Client on XP machine.
Due to some reason I need to format my machine and I have installed Windows 7. Now my problem is, I already have the existing folders of the views created on XP. How do I re-import it so it will be shown in my Clearcase Navigator on Windows 7 machine?
In the OP jaychapani 's case (ClearCase Remote client):
The view storage for a "web view" is by definition on the CCRC server (so not on the client)
See "
How to reconstruct a CCRC view copy area after an unintentional deletion"
(the equivalent of a snapshot view directory is called, in CCRC, "view copy area")
A situation may occur where a developer unintentionally deletes a copy area and there is no backup.
The Web view still exists on the CM server and the view tag still exists in the ClearCase registry.
There is no way to perform such recovery completely from the CCRC graphical user interface (GUI).
Determine the View Tag (you can run cleartool lsview -l on the Web server: ask your ClearCase admin)
Create a new copy area (for example: D:\Webviews\<VIEWTAG>)
Create a .copyarea.dat file in the root of the above directory
Refer to technote 1119280 About the .copyarea.dat and .copyarea.db files for further details about this file.
a. Copy a .copyarea.dat file from another (known good) copy area into the root of the new copy area
b. Remove the "READONLY" and "HIDDEN" file attributes from that file.
Determine the UUID of the webview <VIEWTAG>.
You can get the UUID by running a cleartool lsview -l on the Web server (again, ask your ClearCase admin).
Modify the .copyarea.dat in the root of the new copy area.
If it was from a copy, modify the UUID and also the name of the <WEBVIEW> including its hexadecimal length field; modify also the name of the VOB root directory.
The timestamp in .copyarea.dat file does not need to be modified.
Remove the view tag from the .ccase_wvreg file.
Refer to technote1228258 About the CCRC .ccase_wvreg file for further details about this file.
Use CCRC GUI to perform "Add existing view".
Perform a Refresh->Repair->Discordance.
This repairs the content of the view.
Original answer, for a full ClearCase installation
If depends where the view storage of your (snapshot) view is stored.
If the view storage isn't stored on your local computer, you can simply re-create the root directory of your snapshot view and use "regen_view_dot_dat.pl" script found in <cc-home-dir>\etc\utils to regenerate the view.dat hidden file.
See "Clearcase - Find out when view was created" for more on that tool.
From that path, you can type clearexplorer . (note the space and the '.' dot), and you will see your view back in the ClearCase Explorer. Update it and you will find back its content.
If you had saved your snapshot view before formatting (including the hidden file view.dat), this is even easier: go the root path of that view and type clearexplorer .: your view will be back.