rgy_check
Check registry files for inconsistencies
SYNOPSIS
- ClearCase:
- rgy_check { –vie·ws | –vob·s }
... [ –reg·ion region ]
[ –sto·rage ]
- ClearCase LT:
- rgy_check { –vie·ws | –vob·s }
... [ –hst·orage ]
DESCRIPTION
The rgy_check command
examines the contents of ClearCase or ClearCase LT 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 or ClearCase LT
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
Region-related problems are more likely
to occur ClearCase than in ClearCase LT because ClearCase installations
are not restricted to a single region. However, in either case, 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)
In ClearCase LT, if you specify the –storage option, rgy_check reports
the same kinds of problems that ClearCase reports when you use –storage,
except that view and VOB objects (rather than tags) are checked.
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.
- –hst·orage
- Checks for the existence of registered
VOB and/or view storage directories on the ClearCase LT server host.
Given a storage directory's existence, rgy_check looks
for basic storage configuration problems as well. You must run rgy_check at
the ClearCase LT server host when you use this option.
EXAMPLES
- Check
the VOB registry for errors and anomalies.
- 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.
SEE ALSO
Administrator's Guide