Troubleshooting
Problem
Attempts to run fs_check reports "WARNING: The cache and archive files for name-version:type:instance differ only in carriage return characters" in IBM Rational Synergy
Symptom
The fs_check command reports the following message:
WARNING: The cache and archive files for name-version:type:instance differ only in carriage return characters
Cache file path: \\server\dbshare\dbname\st_root\cache\source\#56\123456
Archive path: archive/source/ascii/ccm_rcs/1/3/name,v
Archive version: 1.1
Cause
This warning means that carriage returns are different between the archived object source and the cache file. On a Windows server, all of the ascii cache files would be in Windows ascii format. On a UNIX server, the ascii files would be in UNIX ascii format. Windows uses two bytes 0d, 0a
in Hexadecimal representing Carriage Return <CR>
and Linefeed <LF>
whereas UNIX just uses the single byte linefeed.
This warning is most commonly seen in cases where the database has been moved from one operating system format to another, without proper conversion of the database files.
There have also been instances where the tool used to modify the file puts
<CR> <LF>
at the end of the lines.
Diagnosing The Problem
- Look at the cache file specified in the error and see what format is being used and determine if this is correct for your installation or not.
- Rename the cache file for safe keeping
- Run '
ccm cat name-version:type:instance
' to create the cache file form the archive. Look at this file and and see what format is being used and determine if this is correct for your installation or not.
Resolving The Problem
- Affecting all ASCII objects:If this is affecting every ascii object version in the database, please contact Rational Client Support for instructions on how to modify all the files appropriately.
or
- Affecting some ASCII objects: If this is being reported for a small number of objects, then
- Determine if the original cache file or the cache file created from the archive are correct and put that file in the cache.
- Run
archive_fix
to resolve the error:
Technote 1624991: How to fix your fs_check errors
Related Information
Was this topic helpful?
Document Information
Modified date:
22 December 2020
UID
swg21627144