Question & Answer
Question
Users with link-based work areas discover that their checked-out files are owned by ccm_root instead of their own ID, so the files are not writable by the users. What causes this issue?
Cause
This can be caused by removing full read/write/execute permission from the temporary directories in the path st_root directory tree of the database.
It may also be a result of the database path being NFS mounted with attribute caching enabled.
Answer
In the path st_root/cache/source directory of the database, there are 100 subdirectories that hold the source files for all Rational Synergy source objects. These directories hold the files to which work areas link. Each of these 100 directories, #00 ... #99, have a tmp/ directory that must have wide-open permissions (777). Rational Synergy must be able to change ownership on files.
Upon checkout, the client process (run as the user) copies the source of the predecessor to the tmp/ directory. Then the engine process (run as ccm_root) moves it up a level to its proper location. This action results in a cache file that is owned by the end user.
Check the ownerships of these 100 tmp directories and ensure that they have 777 permissions.
su ccm_root
cd <database_path>
# List the 100 tmp directories and their permissions
find . -type d -name tmp -exec ls -l {} \;
# Change the permissions back to the default 777 (drwxrwxrwx)
find . -type d -name tmp -exec chmod 777 {} \;
Also, make sure that attribute caching is not enabled. For details on implementing this, see technote 1615832 at http://www-01.ibm.com/support/docview.wss?uid=swg21615832.
If this does not resolve the issue, contact IBM Rational Support.
Was this topic helpful?
Document Information
Modified date:
22 December 2020
UID
swg21624804