The source_modify_time attribute is set to the time when an object version was first checked into a static state. The setting must match the time stamp on the cache file.
Someone edited the cache file after checking it in as user ccm_root. That user owns all static cache files.
WARNING: filename.c-2:csrc:DCM2#2's cache file modification time is NEWER than its source modification time in the database:
Cache file path:
database_path/st_root/cache/source/#83/27783
Source modification time: Wed Jul 19 11:40:15 2009
Cache modification time: Tue Sep 05 13:03:08 2009
First, move the cache file to a safe backup folder:
% mv database_path/st_root/cache/source/#83/27783 /tmp/27783.saved
% ccm finduse filename.c-2:csrc:DCM2#2
% ccm cat filename.c-2:csrc:DCM2#2 > /dev/null
This action re-creates the cache file from the archive. Now, compare this file to the cache file you moved to the /tmp directory. If the files are identical, then delete the saved file. If they are not identical, follow the instructions in Serious, recoverable errors to correct the error.
An ascii type object version, or one based on the ascii type, has a source that contains at least one character that does not belong in the 7-bit ascii character set.
In older versions of Rational® Synergy, this warning can also mean that the source is truncated in the archive because the ascii archiver treats the first of these binary characters as an end-of-file (EOF) marker. In recent releases, because the source is automatically archived as type binary, this particular warning displays in older releases of the software, or in recently upgraded databases.
To fix this corruption, rearchive the object versions with a binary archiver. On each of the affected object versions, create and set the handle_source_as attribute to binary. Then, run the ccm archive_fix command to rearchive.
% ccm attr –c handle_source_as –t string –v “binary” myfile.txt-1:ascii:2
Then, you must run the ccm archive_fix command to archive the sources. The object version’s type remains unchanged, but the method that is used to archive it is for binary source files.
See the Archive conversion FAQs - fs_check command for instructions on running the ccm archive_fix command.
Cachefile path: database_path/st_root/cache/source/#56/123456
Archive path: archive/source/ascii/ccm_rcs/1/3/name,v
Archive version: 1.1
The carriage returns of the archived object source and the cache file are different. On a Windows server, all of the ascii cache files are in the Windows ascii format. On a UNIX server, all of the ascii files are in the UNIX ascii format. This warning is commonly seen when databases are moved from one operating system format to another, without properly converting the database files.
If the issue is reported on a few objects, then determine which files are correct, and replace the files. If this formatting issue is affecting every ascii object version in the database, contact IBM® Rational Support for instructions on modifying all of the files.