I think that the Clearcase server is also used for hosting the view server, but how can I be sure?
#cleartool hostinfo -long
Client: abcd123
Product: ClearCase 8.0.1.4
Operating system: AIX 1 7
Hardware type: 00C7D6164C00
Registry host: abcd123
Registry region: ggg
License host: abcd123.kalzam.razel.steria.ch
As described in "Rational ClearCase server processes", a view_server is a long-lived process that manages activity in a particular view.
So if you see any view_server process on a given host, then that host is a view server.
But that does not mean it is the only one, and any ClearCase client can also hosts its own view (if ClearCase was installed with a view server as part of its features)
See also cleartool lsstgloc for listing registry information about server storage locations for views, VOBs, or both.
cleartool lsstgloc -view -host anHostname
If that returns something, then 'aHostname' is a view server.
If you have a view tag in mind, describe it to get its view storage path:
cleartool lsview -l -full -pro aViewTag
From that global path, you can get the view server hostname with:
cleartool lsstgloc -view -long -storage a/global/path
Type: View
Region: atria_r_d_unix
Storage Location uuid: 3988ccaa.412d11d4.a313.00:01:80:7c:c6:73
Global path: /net/peroxide/export/home/bert/stgloc_view1
Server host: peroxide
Server host path: /export/home/bert/stgloc_view1
Related
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.
We have a ClearCase server installed on Solaris box and there are several vobs replicated in a multi-site environment. Now as this Clearcase server is becoming old we have setup an new Server on Windows and able to bring that new server into multi-site with all the required vobs. Now we would like to remove/decommission the vobs from old solaris box and want to free up the space occupied by those vobs.
Can any one suggest the best procedure to do this and also point us to the links for that procedure?
You can:
follow the technote "Moving a VOB using ClearCase MultiSite", which basically:
creates a replica on the source vob server:
import the replica on the destination vob server:
multitool mkreplica -export -workdir c:\\
[-maxsize 100m] -fship :
#
Import:
multitool mkreplica -import -workdir /var/tmp/doesntexist/ -tag
/your/new/vobtag/ -stgloc -auto -npreserve -public /var/adm/atria/
shipping/ms_ship/incoming/
simply rmtag and unregister the vob on the solaris box, in order to remove it completely from the central registry server.
See "How to remove a VOB or View from the ClearCase registry"
The alternative, to delete that vob, and to follow "Deleting a replica"
Then you can simply delete the vob and get back that disk space.
How to know an incoming sync packet is inteded for a particular vob?
multitool lspacket -l doesn't tell for which vob this is intended.
I have several incoming packets intended for my replica but when I import them using this command i am getting the below error:
C:\Program Files\IBM\RationalSDLC\ClearCase\var\shipping\ms_ship\incoming>multitool syncreplica -import sync_usal_unix_2012-11-29T23.00.17-05.00_2296
multitool: Error: Sync. packet C:\Program Files\IBM\RationalSDLC\ClearCase\var\shipping\ms_ship\incoming\sync_usal_unix_2012-11-29T23.00.17-05.00_2296 is not applicable.
Actually, multitool lspacket is the right command to check initially:
The OP vchitta initially thought:
The lspacket gave the below out put which shows that the intended replica name is correct but it doesn't reveal the VOB details.
multitool lspacket sync_usal_unix_2012-12-01T23.01.06-05.00_19957
Packet is: C:\Program Files\IBM\RationalSDLC\ClearCase\var\shipping\ms_ship\incoming\sync_usal_unix_2012-12-01T23.01.06-05.00_19957
Packet type: Update Packet fragment: 1 of 1
VOB family identifier is: 360ab8c4.661e11d3.a49e.00:01:80:a9:b5:ec
To which I argued:
Did you search '360ab8c4.661e11d3.a49e.00:01:80:a9:b5:ec' in the vob registry?
(or simply cleartool lsvob -l)
Is there any other Vob which would have the same uid?
See VOB objects and VOB replica objects.
Yes or no, this is your answer right there.
THE IBM documentation clearly mentions:
Each replica is a VOB, but the VOB object and VOB-replica object are different objects in the VOB database.
Specifically:
VOB object: The database has a single VOB object.
This object’s UUID is listed as the VOB family uuid in a lsvob –long listing.
VOB-replica object (or replica object): The database has a VOB-replica object for each of the VOB’s replicas.
This object’s UUID is listed as the Vob replica uuid in a lsvob –long listing.
The OP adds:
No.
No vob is having family identifier with the above UUID.
Now I am able to find which vob a packet is intended for with the help of family UUID.
I found this particular packet is for Platfom vob which I didn't replicated yet.
Original answer
See first "Packet is not applicable to any local replicas"
To verify that the host-name property of a VOB replica is wrong, enter the following command:
cleartool describe –fmt "%[replica_host]p\n"
replica:importing-replica-name#VOB-tag
For example:
cleartool describe –fmt "%[replica_host]p\n" replica:newyork#/vobs/tests
manhattan
If the host name is incorrect, use the chreplica command to change it. At the master replica of the importing replica, enter a chreplica command:
multitool chreplica –c "comment" –host new-host
replica:importing-replica-name#VOB-tag
For example:
multitool chreplica –c "change host name" –host brooklyn
replica:newyork#/vobs/tests
Updated replica information for "newyork".
Send an update packet to the other replicas in the family.
You can have multiple causes, as describes in this technote
Cause
The import command may have been run from a host other than the VOB server.
The hostname associated with the replica may have changed and MultiSite has not been updated.
The VOB server may have multiple host names and or multiple network cards and MultiSite is not properly configured to work with them.
Resolving the problem
For cause 1:
Make sure the syncreplica -import command is being run on the VOB server host.
The syncreplica -import command must be run on the VOB server host as it is a server operation.
For cause 2:
Check the hostnames associated with the replica and compare the outputs using the two commands below.
The VOB and the replica should show identical "host" output. If they do not, this is likely to be the problem.
Use the multitool chreplica -host command to resolve the problem.
Review the MultiSite Administrator's Guide on the topic of chreplica (multitool man chreplica) for more details.
cleartool lsvob -long <vob tag>
multitool lsreplica -long <replica-name>
For cause 3:
If the import is in fact being run on the correct server host, check to see how many hostnames that machine has.
Maybe the server has more then one network card, or several aliases.
If there is more than one name, make sure that the alternate_hostnames file exists.
It should contain each and every hostname the machine has, one per line.
Note: The alternate_hostnames file is supported on UNIX® and Linux® only.
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 set up one Clearcase server, one Clearcase client, both on Windows XP. And created the following local groups and users.
Machine A (Clearcase server)
Group: Clearcase Admin - User: ccadmin
Group: Clearcase User - User: ccadmin, ccuser
Machine B (Clearcase client)
Group: Clearcase Admin - User: ccadmin
Group: Clearcase User - User: ccadmin, ccuser
Then I logon machine B with ccuser, I checked out source code successfully, but when I try to add new files to source control, it prompted the following error:
No permission to perform operation "make branch"
Must be one of: member of element group, element owner, VOB owner, member of Clearcase group
p.s. I check in/out source code with Clearcase plugin in RAD
I added CLEARCASE_PRIMARY_GROUP to environment for my account in both machines, but another error shows up
Now the group "Clearcase User" is in the VOB list, is the error due to the different hostname?
New Update
You need to describe the vob into which you try to add to source control
cleartool describe -l vob:\YourVob
And make sure your CLEARCASE_PRIMARY_GROUP refers to one of the groups (primary or secondary) listed by that command for the vob.