rgy_check
Check
registry files for inconsistencies
Applicability
Product
|
Command
type
|
ClearCase®
|
command
|
Platform
|
UNIX®
|
| Linux® |
Windows®
|
Synopsis
- rgy_check { –vie/ws | –vob/s }
... [ –reg/ion region ] [ –sto/rage ]
Description
The rgy_check command examines
the contents of ClearCase VOB
and/or view registries, and reports any errors or inconsistencies.
Registry problems have various causes:
- Editing registry entries with editors
such as emacs or Notepad.
- Improper administration procedures; for
example, removing a VOB with an operating system command rather than with rmvob
- Faulty upgrade procedures; for example,
migrating a VOB to a new release that introduces a database schema change
without reformatting the VOB (using reformatvob)
- Defects in older releases of ClearCase
If rgy_check finds errors
or inconsistencies, it displays a line like the following at the end of its
output:
For each problematic registry entry, rgy_check displays
the registry entry and a warning or error message.
General problems
rgy_check reports the following
general problems:
- Duplicate entries in the registry
- Malformed entries in the registry
Registration anomalies
rgy_check reports the following
VOB or view registration anomalies:
- Objects with no UUID
- Two objects with same UUID
- Objects with no host name
- Objects with no local (server) pathname
- Two objects pointing to same host-local-path
- Tags with no UUIDs
- Tags with UUIDs that do not match any
object (stranded tag)
- Tag registry entries with no tag
Region-related problems
rgy_check may report these
problems:
- Objects with no associated tags in any
region (stranded object)
- Tags in regions that are not in the region
registry
- Tags with no global pathname
- Two tags in one region pointing to same
object UUID
- Duplicate tags in the same region
- Tags in one region with duplicate global
pathnames
Storage-related problems
In ClearCase, if you specify the –storage option, rgy_check also
reports these problems:
- View tags that point to global paths
with missing or incorrect .view files:
- Missing .view file
(usually a missing view)
- .view file with
invalid contents
- .view file that
contains an incorrect view UUID (that is, the UUID points to wrong view)
- VOB tags that point to global paths with
missing or incorrect replica_uuid files:
- Missing replica_uuid file
(usually a missing VOB)
- replica_uuid file
with invalid contents
- replica_uuid file
with an incorrect UUID (that is, the UUID points to wrong VOB)
Options and arguments
Specifying the kind of registry entries to display
- Default
- None.
- –vie/ws
- Checks the contents of the view tag and/or view object registries.
- –vob/s
- Checks the contents of the VOB tag and/or VOB object registries.
Specifying the region
- Default
- All regions.
- –reg/ion region
- Specifies the network region for which registry entries are to be checked.
Checking storage
- Default
- None.
- –sto/rage
- Checks for the existence of registered VOB and/or view storage directories.
Given a storage directory's existence, rgy_check looks
for basic storage configuration problems as well. Typically, registered storage
pathnames for multiple network regions are not accessible from a single host.
It is common practice to use –region to confine storage checks
to the current host's network region.
Examples
- Check the VOB registry for errors and
anomalies.
rgy_check -vobs
No registry errors/inconsistencies detected.
- Check VOB and view registries in the devel region
(which includes the local host). Include storage directory checks. In this
example, rgy_check finds a tutorial VOB from which the
user has removed the VOB's replica_uuid information.
rgy_check -vobs -views -region devel -storage
rgy_check: Error: The VOB storage at \\io\alh\ccasetut\tut.vbs has
no replica_uuid file.
This tag:
-tag = "\alh_IO_hw"
-global_path = "\\io\alh\ccasetut\tut.vbs"
-hostname = "io"
-mount_access = "private"
-mount_options = ""
-region = "devel"
-vob_replica = "7d7031db.6dfb11cf.a398.00:80:c8:81:fa:e0"
rgy_check: Error: 1 total registry errors/inconsistencies detected.
See also
IBM Rational ClearCase Administrator's
Guide