About fix_prot

Technote (FAQ)

Question

How do I use the IBM® Rational® ClearCase® fix_prot utility to reprotect Microsoft® Windows® ACLs on VOB and view storage as well as adjust file and group ownership on VOB and view storage on UNIX® or Linux®?

For more information on fix_prot and its usage, refer to IBM Rational ClearCase Administrator's Guide under the topic of fix_prot.

IMPORTANT: It is recommended that ClearCase services on Windows be shut down prior to running the fix_prot utility. This will ensure that no files are held open by ClearCase processes which otherwise could be skipped during the execution of the utility.

Note: When you run fix_prot, if there are any Additional Groups that were part of the VOBs group list, running this command will remove those groups. As a result you will need to run the protectvob command to add these additional groups back to the VOB.

The proper syntax and process for running fix_prot is as follows:

Open a command prompt.

Change directory to the <CCHOME>\etc\utils and issue the following commands in order indicating the appropriate pathnames for the operating system on which you are running the command.

Note:Windows Only. If the ClearCase administrators group name has changed or you have moved a view to a new domain that has a different SID for this group, then the -replace_server_process_group switch is required.

Note:Windows Only. Fix_prot can be run on schema 53 and 54 VOBs with one exception. The -recover switch can only be used on schema 53 VOBs. The functionality of this Windows only switch restores correct file system ACLs in a VOB or view storage directory based on the information in the identity.sd and groups.sd files. It is not applicable to schema version 54 VOBs because vob_sidwalk –recover_filesystem performs this function.

%> fix_prot -replace <Path to VOB/View storage>

Note: After running the two fix_prot commands the views may be usable but the existing checkouts fail with the 'permission denied' message. After running a 3rd fix_prot command with -recurse -chown -chgrp -chmod (no -root option) on the *parent* folder of the "view.stg" folder then the checkins will succeed.

Note: There are unknown problems that can occur when changing ACLs on a file system remotely, so it is recommended that you run the fix_prot utility directly from the VOB/View server itself and not through a remote connection.

Note: If you have implemented the local almd directory location as described in technote 1687360, then you will have to change the permissions and protections of the local almd files to match any change you have made with fix_prot.

TROUBLESHOOTING:

If fix_prot returns an error message that begins with the following text: