Three typical scenarios can lead to incorrect storage protections:
- Copying the storage directory incorrectly
- If you do not use the appropriate copy utility, as described in Preserving NTFS ACLs when copying a VOB or view storage directory, when
copying a VOB or view storage directory, the ACLs on the copy are not correct.
For information about fixing protection problems caused by copying the directory,
see Fixing protection problems.
- Converting the file system to NTFS
- If you create the storage directory on a disk partition formatted as FAT
or FAT32 and later convert that partition to NTFS, the storage directory protection
becomes incorrect. A different VOB owner is reported after the conversion.
VOB and view servers do not start because the file identity.sd does
not agree with the security descriptor for the storage directory root. There
is no way to avoid this behavior. For information about correcting storage
directory protection, see Fixing protection problems.
- Editing permissions
- If you edit a file permission, for example, by using Windows® Explorer
or cacls, Rational® ClearCase® users
begin to have access and protection problems. To detect VOB storage directory
protection problems, use checkvob:
cleartool checkvob –protections –pool vob-stg-pname
where vob-stg-pname is the pathname of the VOB
storage directory. For information about fixing protection problems caused
by editing file permissions, see Fixing protection problems.
For more information, see the checkvob reference page.