rgy_check: Error: This VOB object is stranded (it has no tags in any region)

Problem(Abstract) This technote explains how to resolve the error rgy_check: Error: This VOB object is stranded (it has no tags in any region) when running the IBM® Rational® ClearCase® utility rgy_check.

Symptom

Running the rgy_check utility returns the following output. rgy_check: Error: This VOB object is stranded (it has no tags in any region): -hostname = "host1" -local_path = "d:\ClearCase_Storage\usr_name_tut\input.vob" -vob_replica = "d8b54141.3b1011d4.9719.00:60:08:cc:c1:65" -vob_family = "d8b54140.3b1011d4.9719.00:60:08:cc:c1:65" Similar errors like the following may be reported if the issue is related to a View: The rgy_check command reports the following error: # /opt/rational/clearcase/etc/rgy_check -views rgy_check: Error: This view object is stranded (it has no tags in any region): -hostname = "host1" -local_path = "/views/dev_debug.vws" -owner = "vobadm" -view_uuid = "b86d5c88.d1cf11db.8fa7.00:01:83:44:97:72" -attributes = "sumview" rgy_check: Error: This view object is stranded (it has no tags in any region): -hostname = "host1" -local_path = "/views/dev.vws" -owner = "vobadm" -view_uuid = "56ad2448.d1c811db.8fa3.00:01:83:44:97:72" -attributes = "sumview" rgy_check: Error: 2 total registry errors/inconsistencies detected. Email notification from the nightly scheduled job, Daily View Space, reports the following error: Job 5 "Daily View Space" (16091) Completed: OK but with messages: "cleartool: Error: Storage directory "/views/dev.vws" does not exist. cleartool: Error: Storage directory "/views/dev_debug.vws" does not exist. Note: Daily View Space is a default job in the ClearCase Schedule.

Cause

The VOB has been removed, but the vob_object (uuid) entry still exists in the ClearCase registry. In the case of a view, it may have been removed improperly , which left a stranded reference to it in the ClearCase registry.

Resolving the problem

Use the cleartool unregister command to manually remove the VOB or View references from the ClearCase Registry. For a VOB: Example: cleartool unregister -vob -uuid d8b54141.3b1011d4.9719.00:60:08:cc:c1:65 For a View: Example: cleartool unregister -view -uuid b86d5c88.d1cf11db.8fa7.00:01:83:44:97:72 Review the IBM Rational ClearCase Command Reference Guide on the topic of rgy_check (cleartool man rgy_check) as well as the topic of unregister (cleartool man unregister) for more information. Also refer to technote 1134700 for more information about Manually removing a VOB or View from the ClearCase registry whose storage has been deleted.

Preparing backup_registry_server to be a registry server failed

Problem(Abstract) This technote explains why attempts to switch the backup registry server to the primary registry server on UNIX® of Linux® using the IBM® Rational® ClearCase® command rgy_switchover results in the error rgy_switchover: Error: Preparing prime_reg_svr to be a registry server failed.

Symptom

Attempts to make a backup registry server host the primary registry server host results in the following error: Example: Registry server: prime_reg_svr Backup registry server: backup_reg_svr rgy_switchover -backup prime_reg_svr prime_reg_svr backup_reg_svr Registry switchover started at 21-Nov-05.16:07:03 rgy_switchover: Error: Preparing prime_reg_svr to be a registry server failed Registry switchover finished at 21-Nov-05.16:07:03

Cause

This issue may be caused by either of the following: This problem can be caused when the backup registry server is believed to be a primary (master) registry server. There have been instances where there is no error when rgy_backup is run, however the backup files are not created in /var/adm/rational/clearcase/rgy/backup

Resolving the problem

Check the contents of /var/adm/rational/clearcase/rgy/rgy_svr.conf on the backup registry server. Check the contents of /var/adm/rational/clearcase/rgy/rgy_hosts.conf. If the entry in the rgy_svr.conf says master, open the configuration file with a text editor and delete the entry. Ensure the first line in the rgy_hosts.conf file specifies the rgy_server name and the second line the backup registry server name. Run rgy_backup on the backup registry server. Then run rgy_switchover again.

rgy_check: Error: Two View objects have the same pathname on a server

Problem(Abstract) This technote explains why the error rgy_check: Error: Two View objects have the same pathname on a server occurs when using the IBM® Rational® ClearCase® rgy_check command on Microsoft® Windows®, Linux® and UNIX®. Symptom Running rgy_check -views is reporting the following error: rgy_check: Error: Two View objects have the same pathname on a server. First object: -hostname = "integ" -local_path = "/user/integ/.views/cspatch.vws" -view_uuid = "0f12a312.75e511d0.a6a1.00:01:55:42:fc:96" This object: -hostname = "integ" -local_path = "/user/integ/.views/cspatch.vws" -view_uuid = "4422a476.75e511d0.a6a2.00:01:55:42:fc:96" rgy_check: Error: A view tag duplicates another view's global pathname in region smnos. Similar errors may be reported if you are running rgy_check with the -vobs option.

Cause

The error message indicates that two view tags are assigned to the same view's physical storage directory which is illegal in ClearCase. Only one view tag can be given for a view's physical storage directory within a single region. First tag: -tag = "CS_PATH" -hostname = "integ" -global_path = "/usrx/sv1/integ/.views/cspatch.vws" -region = "smnos" -view_uuid = "0f12a312.75e511d0.a6a1.00:01:55:42:fc:96" Second tag: -tag = "cspatch" -hostname = "integ" -global_path = "/usrx/sv1/integ/.views/cspatch.vws" -region = "smnos" -view_uuid = "4422a476.75e511d0.a6a2.00:01:55:42:fc:96" How did this happen? This usually happens when there is a process hanging around for a particular view which wasn't removed the proper way. When the user then issues a cleartool mkview command with the same name as the view that was improperly removed, a second view tag entry with a different uuid in the same region is inadvertently created.

Resolving the problem

In order to resolve the errors you need to unregister the view and remove the extra view tag. Issue a cleartool unregister -view -uuid passing the uuid of the view. Example: cleartool unregister -view -uuid 4422a476.75e511d0.a6a2.00:01:55:42:fc:96 Remove the additional view tag: Example: cleartool rmtag -view cspatch Review IBM Rational ClearCase Command Reference on the topics of unregister or rmtag (cleartool man unregister or rmtag) for more information.

Error: Unknown host 'xxx': [WINSOCK] Host not found

Problem(Abstract) This technote explains why the error, Error: Unknown host 'xxx': [WINSOCK] Host not found, may occur when using IBM® Rational® ClearCase®. Symptom Attempts to run a credmap command results in the following error: C:\Program Files\Rational\ClearCase\etc\utils>credmap foo Identity on local system: User: DOM1\jdoe (NT:S-1-5-21-1607275091-1726037764-648285020-1004) Primary group: DOM1\clearuser NT:S-1-5-21-1607275091-1726037764-648285020-1007) Groups: (8) DOM1\None (NT:S-1-5-21-1607275091-1726037764-648285020-513) Everyone (NT:S-1-1-0) DOM1\Debugger Users NT:S-1-5-21-1607275091-1726037764-648285020-1009) BUILTIN\Administrators (NT:S-1-5-32-544) BUILTIN\Users (NT:S-1-5-32-545) NT AUTHORITY\INTERACTIVE (NT:S-1-5-4) NT AUTHORITY\Authenticated Users (NT:S-1-5-11) LOCAL (NT:S-1-2-0) Identity on host "foo": credmap: Error: Unknown host 'foo': [WINSOCK] Host not found credmap: Error: Unable to find albd credmap: Error: Unknown host 'foo': [WINSOCK] Host not found credmap: Error: Unable to find albd credmap_local_to_remote_sid returned ClearCase object not found After changing the machine name of the ClearCase registry server errors like the following are reported when performing various ClearCase operations: unknown host hostname:[WINSOCK] valid name, no data record of requested type OR C:\cleartool lsvob cleartool: Error: Unknown host 'xxx': [WINSOCK] Host not found

Cause

The above errors may be caused by either of the following: The credmap utility was given an invalid host name as a parameter in the command. The HOST name is either spelled incorrectly or is no longer a valid name. In the example above "foo" is the incorrect hostname. The ClearCase registry server machine name was changed but the value of the atriaregy Windows registry key located at: HKEY_LOCAL_MACHINE\SOFTWARE\Atria\ClearCase\CurrentVersion was still pointing to the old machine name on the Registry Server. Another cause could be that the host is not in the DNS table.

Diagnosing the problem

Attempt to ping the hostname used in the credmap command: Perhaps the host name is not being resolved: %>ping foo Unknown host foo. or C:\>ping foo Ping request could not find host foo. Please check the name and try again. If ping does return output, use the IP address or the fully qualified name (foo.ibm.com) of the host in the credmap output instead: Example: C:\>credmap 9.34.75.11 Identity on local system: User: DOM1\jdoe (NT:S-1-5-21-1607275091-1726037764-648285020-1004) Primary group: DOM1\clearuser (NT:S-1-5-21-1607275091-1726037764-648285020-1007) Groups: (8) DOM1\None (NT:S-1-5-21-1607275091-1726037764-648285020-513) Everyone (NT:S-1-1-0) DOM1\Debugger Users (NT:S-1-5-21-1607275091-1726037764-648285020-1009) BUILTIN\Administrators (NT:S-1-5-32-544) BUILTIN\Users (NT:S-1-5-32-545) NT AUTHORITY\INTERACTIVE (NT:S-1-5-4) NT AUTHORITY\Authenticated Users (NT:S-1-5-11) LOCAL (NT:S-1-2-0) Identity on host "9.34.75.11": User SID: UNIX:UID-22319 Primary group SID: 110 Group SID list: (1) NOBODY

Resolving the problem

If you are using the correct hostname when running the credmap utility and it is not being resolved, you will need to work with your Network admin to determine the cause or continue to use the IP address when running the credmap command. If it was determined that the hostname setting in the Windows registry is incorrect (as referenced in cause 2 above), it will need to be changed as follows: Note: This solution contains information about modifying the system registry. Before making any modifications to the Microsoft® Windows® Registry Editor, it is strongly recommended that you make a backup of the existing registry. For more information describing how to back up the registry, refer to the Microsoft Knowledge Base article 256986. Open the Windows registry editor, Start > Run > type regedit > click OK Browse to the following registry key: HKEY_LOCAL_MACHNE\SOFTWARE\Atria\ClearCase\CurrentVersion In the right-hand pane of the Registry editor, check the value of the AtriaRegykey Make sure it is set to the correct ClearCase registry server hostname. If it contains the wrong value, double-click the AtriaRegy key and change the value to the correct host name of the ClearCase registry server. Ensure that the hostname is in the DNS table

Specified host is not a registry server

Problem(Abstract) This technote explains why running any IBM® Rational® ClearCase® cleartool command yields the error message Trouble contacting registry on host specified host is not a registry server on Microsoft® Windows®, Linux® and UNIX®. Symptom The following error is reported when running various cleartool commands: Trouble contacting registry on host specified host is not a registry server On the UNIX / Linux server, you may also get this error after installing ClearCase or updating a ClearCase patch when at the [What is the registry server hostname?] prompt during the installation,

Cause

The error may be caused by an incorrect registry hostname being set on the ClearCase client or the registry file on the registry server may be missing or corrupted. During the ClearCase installation the incorrect hostname may have been entered. For example if you enter myhost when the actual hostname is myhost.lex.ibm.com which is the output of a uname -a on the registry server.

Resolving the problem

Note: When following the instructions below keep in mind that on Unix and Linux hosts running ClearCase version 7.0.1 and later the registry files are located in /var/adm/rational/clearcase/config Refer to technote 1265395 ClearCase 7.0.1 registry files on UNIX and Linux moved from 'rgy' to 'config' for further information about this change. UNIX/LINUX CLIENT Make sure that the correct registry server name is specified in the rgy_hosts.conf file on the client host from which the cleartool command has been executed: cd /var/adm/atria/rgy cat rgy_hosts.conf UNIX/LINUX SERVER Nonexistent or corrupted rgy_svr.conf file on the registry server host itself. The rgy_svr.conf file on the registry host is what informs ClearCase that it is a registry host. The file should exist in the /var/adm/atria/rgy (/var/adm/rational/clearcase/config in version 7.0.1 or later) on the registry host, and it should contain the word master. If this file does not exist, create it. If the file exists but does not contain the word master, edit the file and add the keyword master. Stop and restart ClearCase /opt/rational/clearcase/etc/atria_start stop /opt/rational/clearcase/etc/atria_start start WINDOWS CLIENT Make sure that the correct registry server name is specified in the ClearCase Control Panel on the client from which the cleartool command has been executed. The "Use registry server on host" radio button ought to be selected with a valid host name in the box. WINDOWS SERVER Make sure that the registry server points to itself in the ClearCase Control Panel by selecting the "Use local host as registry server" radio button.

Invalid hostname text reported in warning message and logs

Problem(Abstract) This technote explains the cause for invalid error text being reported in IBM® Rational® ClearCase® warning messages and logs on UNIX® and Linux®. Symptom

Cause

While running the db_loader on a VOB that had been moved from another server, the following warning is reporting invalid characters for the hostname because the .hostname file located in the VOB storage directory contained the old hostname. db_loader: Warning: Database not found in local registry for cmd: "". Using client path /export/home/vobstore/db_loader_vob.vbs/db db_loader: Error: The vob_object registry for "/export/home/vobstore/db_l oader_vob.vbs/db/.." specifies incorrect hostname for server; expected hostname: host1 actual hostname: . Use cleartool unregister/register -vob to correct. db_loader: Error: Process not running on registry specified hostname ( ┐⌠╕) db_loader: Error: Cannot open database in '/export/home/vobstore/db_loade r_vob.vbs/db': db_loader: Error: Error from libdb (1) Cause 2 The following is another example of output reported in the ClearCase logs: 2006-12-10T03:36:25-05 db_server(4334): Error: The vob_object registry for "/vbs/test1/db/.." specifies incorrect hostname for server; expected hostname: þìÄþë actual hostname: test2-vob,pid==20240,euid==UNIX:UID-0, cleartool 'chepoch' '-actual' 'rtp-master@/vob/test1'. Use cleartool unregister/register -vob to correct. This issue has reported as defect APAR PK36046.

Resolving the problem

This defect has been resolved in the following updates: ClearCase 7.0 ClearCase 7.0 7.0.0.1-RATL-RCC-IFIX03 ClearCase LT 7.0 7.0.0.1-RATL-RCCLT-IFIX03 ClearCase 2003.06.00 ClearCase 2003.06.16 - Windows clearcase_p2003.06.16.NT-2007B ClearCase LT 2003.06.16 - Windows clearcase_lt_p2003.06.16.NT-2007B ClearCase 2003.06.00 - UNIX and Linux - User Space clearcase_p2003.06.00-47 ClearCase 2003.06.00 - UNIX and Linux - MVFS clearcase_p2003.06.00-46 ClearCase LT 2003.06.00 - UNIX and Linux clearcase_lt_p2003.06.00-23 WORKAROUND: Review technote 1170877 for details concerning a resolution for the above errors related to the invalid text reported for the hostname.

Clients list not displayed under ClearCase Network in the Administration Console

Problem(Abstract)

This technote identifies a defect whereby no clients are listed when clicking ClearCase Network in the IBM® Rational® ClearCase® Administration Console on Microsoft® Windows®.

Symptom

When selecting the ClearCase Network option in the Administration console, no clients are listed although there are entries correctly listed in the client_list.db file. The ClearCase Registry server collects information about client hosts that have recently accessed the registry server. This information is stored in the client_list.db file which is located by default in the /var/adm/rational/clearcase directory on UNIX® or Linux® or in the C:\Program Files\Rational\ClearCase\var directory on Microsoft® Windows®: A restart of ClearCase does not resolve the issue.

Cause

The cause of this problem is that IBM Rational Common Licensing (FLEXlm) is being used and the Administration Console does not have any data to read from the FLEXlm license server to populate the "ClearCase Network." The FLEXlm license server does not keep a list of clients that access it and therefore cannot populate the "ClearCase Network" list. FLEXlm licensing, also known as IBM Rational Common Licensing, is an available licensing scheme for use with Rational ClearCase 7.0 and later versions. The following example shows how the output would typically be displayed. When experiencing the problem described in this technote, the data you see listed under "ClearCase Network" would not be displayed. Other symptoms would include the following: Clicking on the ClearCase Network in the Administration Console will list the registry server name at the top with no license server name only displaying empty quotes. For example: ClearCase Network Hosts using ClearCase as recorded by the registry server 'my_server' and the license server ' ' Clicking on the Hosts icon in the Administration Console under "ClearCase Registry" the "License Server" column does not contain a value for any ClearCase host that uses FLEXlm licensing. This has been reported as defect PK53129.

Resolving the problem

The decision was made by Product Management to exclude the resolution of this defect from future upgrades and releases. WORKAROUND: To display a list of all the clients that contacted the registry and or license server, the following command can be run from a command prompt: cleartool lsclients -host -type registry Review the IBM Rational ClearCase Command Reference on the topic of lsclients (cleartool man lsclients) for more information.

Cleartool lsclients returns incorrect information

cleartool lsclient command returns information about hosts that should have been dropped from the client_lists.db file on Microsoft® Windows®, UNIX® and Linux®. Symptom The lsclients command should list all the clients for a given registry or license host. If a client does not access the server for 30 days, it is supposed to be dropped from the list. The output below, however, shows that this is incorrect. % date Mon Mar 6 16:57:47 EDT 1997 Client: arkansas ... Last registry access: 06-Mar-97.15:05:16 Last license access: 06-Mar-97.15:30:00 Client: arkansas.rational.com ... Last registry access: never Last license access: 14-Jan-97.01:22:07 <-- Note the date Note: Host arkansas and arkansas.rational.com are valid names for the same host.

Cause

This is problem has been logged as Defect APAR IC38943.

Resolving the problem

This defect has been resolved in the following patches: 2003.06.00 ClearCase and CCLT on Windows Service Release 5 ClearCase UNIX & Linux clearcase_p2003.06.00-21 ClearCase LT UNIX and Linux clearcase_lt_p2003.06.00-11 2002.05.00 ClearCase UNIX & Linux clearcase_p2002.05.00-42 ClearCase LT UNIX and Linux clearcase_lt_p2002.05.00-20 ClearCase Windows clearcase_p2002.05.00.NT-37 ClearCase LT Windows clearcase_lt_p2002.05.00.NT-14