Diagnosing the problem Steps to diagnose: UNIX & LINUX ONLY: If a view was moved from one system to another, check whether, on the new file system, the view is mounted Review technote 1207807 for more information. Cause The cause of the error ultimately stems from the inability of ClearCase to successfully record the hostname in the .hostname file located in the storage directory of the VOB or One such application is WANSync by XOsoft Corp. http://invictanetworks.net/error-file/error-file-identity-not-persistent.html
If there is an incorrect ClearCase group name or BUILTIN\Administrators group in the following key: HKLM\Software\Atria\CurrentVersion\ClearCaseGroupName Resolving the problem Solution 1 If the file is corrupt, the .hostname file must be Cause EMC Celerra setting changed when new DART group was installed. If the account is different on the client, the only supported method to resolve this issue is to reinstall ClearCase from the correct release area to update the server process information. There may be files in the view that must be recovered or checked in before removing the view. http://www.ibm.com/support/docview.wss?uid=swg21122514
Check that root or the ClearCase administrators group has permission to write to this directory View Examples: View Tool Error creating view - '
You will be prompted to confirm; type yes. ~# fix_prot -r -root -chown user2 -chgrp ccusers /net/host1/home/jdoe/test.vws CAUTION! Check that root or the ClearCase administrators group has permission to write to this directory. Back to top Related information Adding groups to a view group list on UNIX and Linux About fix_prot Document information More support for: Rational ClearCase View: Dynamic Software version: 7.0, 7.0.1, The sticky bits are not set on the additional group files located in the view or VOB storage directory under the .identity directory (
cleartool: Error: Trouble communicating with VOB database: "/vobs/wsbu. 15". Solution 3 Remove the nosuid option from the export configuration file for the VOB storage and reboot the NAS filer to take effect. The uid and or gid files from the .identity directory on UNIX/Linux are not available. Changing ownership of a view requires modification of both the view file system objects and the view database entries to reflect desired ownership.
Symptom Attempt to create a VOB or view on UNIX or Linux (even if the storage is hosted on a NAS filer), results in the following error: UID Error - example This can be tested by listing the mount options for the file system (using the UNIX mount command, with no options). Error File ./.identity/uid Is Not Set-id For more details on changing UNIX mount options, review the UNIX man pages for 'mount' and 'mount_
Cause 2 This applies to Scenario 2 above. Refer to technote 1207386 for information about VOB database files. Use ls -l /var/adm/atria/almd to determine its current protections. get redirected here cleartool: Error: Failed to set identity on view: Operation not permitted.
Resolving the problem It may become necessary to run a keybuild to regenerate the corrupted VOB database key files. Note: Manually changing the account in the registry or services may not be enough as there are permission issues on the file system to manage as well. Watson Product Search Search None of the above, continue with my search Installing EMC Celerra results in "Operation not permitted" error using ClearCase mkview; mkelem; celerra; operation not permitted; unable to
Example: %> id -a uid=1234(user1) gid=17010(group1) groups=10002(group2), 1001(group3), 1002(group4), 12000(group5), 12001(group6), 12100(group7), 12101(group8), 12102(group9), 13000(group10), 13001(group11), 13100(group12), 13101(group13), 13102(group14), 11002(group15), 12300(group16), 7002(group17) ClearCase only support 16 groups on UNIX and This is not a ClearCase issue, rather this is an RPC issue. APAR PK10876 has been submitted to address this defect. Resolving the problem A work around has been implemented in ClearCase 7.0.
Unanswered question This question has not been answered yet. The only solution is to chown the file within a view/VOB context. Watson Product Search Search None of the above, continue with my search Reformatvob reports error "db_event_create_V3: RPC: Unable to receive; errno = A connection with a remote socket was reset by http://invictanetworks.net/error-file/error-file.html WORKAROUND: Remove the groups not pertaining to ClearCase use from the user's group list and attempt the view creation again.
The view was restored from a backup and the uid and gid are misprotected. Watson Product Search Search None of the above, continue with my search Operation "view_ws_is_ws_view" failed: view storage directory or control files unavailable .access_info; view_ws_is_ws_view; control files unavailable; stale; corrupt; 1131145; .pid For Symptom 2 This error can appear if a view server has been restarted and the .pid file is left behind in the view storage directory. DOMAINB\clearcase) Note: Same scenario may also apply with different clearcase_albd accounts.
Protecting "/home/jdoe/test.vws/admin/view_space"... As VOB owner or root, change directory to
Bad Example: share -F nfs -o rw,anon=0,nosuid -d "project dirs" /export1 Good Example: share -F nfs -o rw,anon=0 -d "project dirs" /export1 Solution 2 If using ClearCase 7.0, use the CLEARCASE_GROUPS Review technote 1142606 for more details.