Rational ClearCase Commands Referenceannotate
apropos
catcr
catcs
cc.icon
cc.magic
cd
chactivity
chbl
checkin
checkout
checkvob
chevent
chflevel
chfolder
chmaster
chpool
chproject
chstream
chtype
chview
clearaudit
clearbug
cleardescribe
cleardiffbl
cleardiff
clearexport_ccase
clearexport_cvs
clearexport_pvcs
clearexport_rcs
clearexport_sccs
clearexport_ssafe
clearfsimport
cleargetlog
clearhistory
clearimport
clearjoinproj
clearlicense
clearmake
clearmake.options
clearmrgman
clearprojexp
clearprompt
cleartool
clearviewupdate
clearvobadmin
comments
config_ccase
config_spec
cptype
credmap
creds
deliver
describe
diffbl
diffcr
diff
dospace
edcs
endview
env_ccase
events_ccase
export_mvfs
exports_ccase
file
find
findmerge
fmt_ccase
getcache
get
getlog
help
hostinfo
init_ccase
ln
lock
lsactivity
lsbl
lscheckout
lsclients
lscomp
lsdo
lsfolder
lshistory
ls
lslock
lsmaster
lspool
lsprivate
lsproject
lsregion
lsreplica
lssite
lsstgloc
lsstream
lstype
lsview
lsvob
lsvtree
makefile_aix
makefile_ccase
makefile_gnu
makefile_pmake
makefile_smake
makefile_sun
man
merge
mkactivity
mkattr
mkattype
mkbl
mkbranch
mkbrtype
mkcomp
mkdir
mkelem
mkeltype
mkfolder
mkhlink
mkhltype
mklabel
mklbtype
mkpool
mkproject
mkregion
mkstgloc
mkstream
mktag
mktrigger
mktrtype
mkview
mkvob
mount_ccase
mount
msdostext_mode
mvfslog
mvfsstorage
mvfstime
mvfsversion
mv
omake
pathnames_ccase
permissions
profile_ccase
promote_server
protect
protectvob
pwd
pwv
query_language
quit
rebase
recoverview
reformatview
reformatvob
register
relocate
rename
reqmaster
reserve
rgy_backup
rgy_check
rgy_passwd
rgy_switchover
rmactivity
rmattr
rmbl
rmbranch
rmcomp
rmdo
rmelem
rmfolder
rmhlink
rmlabel
rmmerge
rmname
rmpool
rmproject
rmregion
rmstgloc
rmstream
rmtag
rmtrigger
rmtype
rmver
rmview
rmvob
schedule
schemes
scrubber
setactivity
setcache
setcs
setplevel
setsite
setview
shell
snapshot.conf
softbench_ccase
space
startview
type_manager
umount
uncheckout
unlock
unregister
unreserve
update
version_selector
view_scrubber
vob_restore
vob_scrubber
vob_sidwalk
vob_snapshot
vob_snapshot_setup
wildcards_ccase
winkin
xclearcase
xcleardiff
xmldiffmrg
DESCRIPTION
The recoverview command repairs a view database and the associated private storage area of a dynamic view. (A snapshot view has no private storage in the same sense as a dynamic view has.) Typically, you use this command after a system crash or similar mishap. You may also want to use this command to regain access to stranded view-private files. (See “Recovering View-Private Files: View lost+found Directory”.)
Automatic Recovery
When necessary, recoverview is invoked by a dynamic view's associated view_server process. Enter this command yourself if messages in the view log (view_log) suggest view database corruption (for example, INTERNAL VIEW DB ERROR).
Possible Data Loss
recoverview uses reformatview; that is, recovery involves a dump/load of the view database. recoverview deletes the old, invalid view database, which reformatview has renamed to db.dumped.
Depending on the state of the view database, this process may cause certain information to be lost. After a view is recovered, consult the view log to investigate possible data loss.
Note: On UNIX, the setuid bit is always lost on files that the view owner does not own.
For more information, see the reformatview reference page.
Recovering View-Private Files: View lost+found Directory
A file in view-private storage is normally accessed through a VOB pathname. That is, the file appears to be located in the VOB, but is actually stored in the view. But this view-VOB correspondence can be disrupted:
- A VOB can become temporarily unavailable, for example, by being unmounted.
- A VOB can become permanently unavailable, by being deleted.
- A particular VOB directory can become unavailable permanently, by being deleted with an rmelem command.
In all these cases, view-private files that are accessed through the unavailable VOB structure become stranded; the files cannot be used for normal ClearCase operations, because there are no VOB pathnames through which they can be accessed. You can resynchronize your view with the available VOBs with the –vob and –dir options. This recovers stranded files by moving them into the view's lost+found directory. Recovered files remain inaccessible to normal ClearCase operations; you can access them through the view storage directory, using standard operating system utilities and commands.
OPTIONS AND ARGUMENTS
Synchronizing a View with One or More VOBs
The following option synchronizes the dynamic view with one or more VOBs. With this option, recoverview moves all stranded files to the lost+found subdirectory. A typical time to synchronize is after performing a relocate operation.
Specifying the View
- Default
- None.
- –tag view-tag
- The view tag of any registered dynamic
view.
- view-storage-dir-pname
- The pathname of a dynamic view storage
directory. Use the lsview command to list
a view's storage directory.
Caution: Make sure that the current working directory is not the same as, or anywhere below view-storage-dir-pname.
Recovering View-Private Storage
The following options take ClearCase-internal identifiers for a VOB or a VOB directory (vob-identifier and dir-identifier) as arguments. The lsprivate command uses these identifiers when listing an inaccessible VOB or VOB directory.
Caution: If the VOB or directory is still accessible, using these options is probably incorrect; it will unsynchronize the view and VOB, not synchronize them.
EXAMPLES
The UNIX examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.
The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.
In cleartool single-command mode, cmd-context represents the UNIX shell or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.
Note: In the UNIX examples that follow, arguments and output that show multicomponent VOB tags are not applicable to ClearCase LT, which recognizes only single-component VOB tags. In this manual, a multicomponent VOB tag is by convention a two-component VOB tag of the form /vobs/vob-tag-leaf—for example, /vobs/src. A single-component VOB tag consists of a leaf only—for example, /src. In all other respects, the examples are valid for ClearCase LT.
Note: recoverview writes status messages to the view_log file; it does not print status messages on the standard output device.
- Synchronize the dynamic view jackson_fix with all VOBs in which it has created view-private files.
- Synchronize a dynamic view whose storage directory is /usr/home/jackson/ccviews/std.vws with the /vobs/dvt VOB.
- For
dynamic view cp_bugfix, recover view-private files
from a deleted VOB.
cmd-context lsprivate –tag cp_bugfix
...
cleartool: Warning: VOB is unavailable -- using name:
"<Unavailable-VOB-1>".
If it has been deleted use 'recoverview -vob <uuid>'
VOB UUID is 1127d379.428211cd.b3fa.08:00:69:06:af:65
...
cmd-context recoverview –vob 1127d379.428211cd.b3fa.08:00:69:06:af:65 –tag cp_bugfix