IBM Support

About vob_sidwalk changes and propagation between MultiSite replicas

Question & Answer


Question

Why are IBM® Rational® ClearCase MultiSite® permission changes performed by the vob_sidwalk utility not propagated to sibling replicas even if those replicas are configured as identity preserving?

Answer

Note: The information in this technote has been incorporated into the 8.0 version of the IBM Rational ClearCase Information Center.



There are no oplog entries created for changes to user or group identities (SIDs, UID, GID) made by running the vob_sidwalk utility in a replicated VOB. In general, there are no oplog entries generated for protection changes made using ClearCase commands and utilities, technote 1211784.

When vob_sidwalk is run in a replica, it preserves the original SIDs on the VOB’s group list, so that operations that require container creation continue to succeed whether or not all such replicas in a family have been updated.

It is necessary that vob_sidwalk be run from all replicas in any VOB family that preserve user/group ID's.

After all members of the preserving replica family have been updated, the administrator must run vob_sidwalk again using the –delete_groups option to remove the historical group SIDs.

Note: Rational recommends removing historical SIDs due to the VOB limitation of 32 groups on its group list. Keeping unused historical SIDs may cause the list to overflow as new groups are added; refer to technote 1131881.

[{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Utilities and Tools","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF015","label":"IRIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0;7.0.1;7.1;7.1.1;7.1.2;8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018

UID

swg21194477