In some situations, it is possible for a file-close operation to occur without a guarantee of a data sync to disk first. For transaction-controlled files, this meant a file could be left corrupted on disk while the FairCom DB Server transaction control system would have no knowledge of this. Extra protection has been added to ensure that this situation did not occur.
This behavior will cause a system cache flush before physically closing transaction logged files or write-through files. This behavior can be disabled by adding COMPATIBILITY NO_SYS_FLUSH_ON_CLOSE to the server configuration file.