Product Documentation

V11.5 Release Notes

Previous Topic

Next Topic

FairCom Server keeps all transaction logs when deferred index thread starts with nonexistent log 1

FairCom Server did not properly remove its transaction logs if it deferred indexing was being used and the deferred indexing state file was created when transaction log #1 did not exist. For example, a server may have been updated from V10 to V11, so transaction logs existed (but not log 1) and the file DFRKSTATEDT.FCS did not exist. In this case, the following messages are observed in CTSTATUS.FCS:

1) at server startup:

Wed Mar 09 15:44:30 2016

- User# 00010 Thread Start: Tran File Deferred Indexing Thread

Wed Mar 09 15:44:30 2016

- User# 00010 L0000001.FCS: 96

Wed Mar 09 15:44:30 2016

- User# 00010 DeferredIndexer: ERR: Failed to set log position to log #1, offset 0: 96

Wed Mar 09 15:44:30 2016

- User# 00010 DeferredIndexer: ERR: Failed to get log position: 96

2) during server operation:

Thu Mar 10 01:59:00 2016

- User# 00168 The number of active log files increased to: 53205

Thu Mar 10 01:59:00 2016

- User# 00168 Deferred Indexer: Scan

The logic has been modified to correct this.

TOCIndex