FairCom DB V12 Release Notes
Delayed durability log flush no longer causes rare invalid transaction log entry
When using the delayed durability feature, the following symptoms were sometimes observed:
- Reading transaction logs may fail with an error such as error 75 or 634.
- Automatic recovery may fail with an error such as error 75 or 634.
- FairCom Server may terminate with internal error
A problem could cause incorrect data, such as 0xff fill bytes instead of the proper log entry data, to be written to the transaction log.
The logic has been modified to eliminate this behavior.