ITIM_ERR (160) Reading records another connection is deleting
When reading records from a fixed-length record transaction-controlled data file, the read sometimes failed with error 160 if another connection was deleting the records. This error could occur even if the reader requested a read or write lock on the record. The logic has been modified to correct this.
Workarounds:
Add ITIM_RETRY_LIMIT 100 to ctsrvr.cfg. This increases the error 160 retry limit.
or
Change the application's record deletion code to commit the transaction with mode ctKEEP, and then call LKISAM(ctFREE). This causes the deleted records to remain locked until later in the transaction, reducing the likelihood of the reader encountering error 160.
