Product Documentation

FairCom RTG COBOL Edition User's Guide

Previous Topic

Next Topic

Transaction log files and best practices

Transaction control depends on a set of “write ahead” logs persisted on reliable storage devices. These should be located on your fasted available storage mounts. Modern SAN SSD is ideal. Frequently, it is necessary to retain as much transaction log data as possible for extended rollback or roll forward. Replicated environments may not be available, requiring the server to retain more logs than defaults allow. Options are available to ensure as much transaction log data is retained as possible.

Ultimately, hands off! These files are critical to the operation of your environment and the integrity of your data. You should ensure that transaction logs are not accessed by any other process, including virus scanners, etc. They should never be backed up, or otherwise copied over.

In fact, if for any reason FairCom RTG cannot write to these critical transaction logs, it will immediately terminate as it can no longer ensure the integrity of your data. A common situation where this happens is an out of storage space condition. Ensure there is always plenty of space for the transaction logs on the storage mount.

TOCIndex