FairCom DB V12 Release Notes

When a transaction deletes a key and adds it with a different offset then aborts, subsequent add of the key no longer fails with KDUP_ERR

Inserting a key into a transaction-controlled index could unexpectedly fail with a duplicate key error when the NXTMARKS and UPDMARKS optimizations were enabled if the key was previously deleted and added in a transaction and then that transaction was aborted. The logic has been modified to correct this.

Workaround: Add COMPATIBILITY NO_NXTMARKS or COMPATIBILITY NO_UPDMARKS to ctsrvr.cfg and restart c-tree Server.