I use Perforce for source control of the Teamcenter documentation files. Today, I noticed some files were revised and checked-in by other users. When I tried to get the latest version of the files by Sync to Head Revision, Perforce gave the following error:
"Can't clobber writable file..."
I found it was because some of the files on my local drive were not in read-only mode. Its a known fact that when we check-in a file after modifications, Perforce marks our local copy of the file read-only. However, in this case, it was not known why that did not happen. It assumed that since the local file was not in read-only mode, the file was open for edit. If Perforce allowed the Sync to Head Revision, the files could have been corrupted.
The solution was to manually mark my local copies of the files read-only. On Sync to Head Revision now, Perforce did not throw any error message.
Click here to read about other users who encountered the same error message and their possible causes.