View Incident Report

Serious

Reported By: Burak Kiper
Reported On: 1/29/1999
For: Version 1.08 Build 1

# 262 Starting a Transaction on Multiple Tables Pointing to the Same Physical Table Causes Lock Timeout

I use transactions. But working code seems not working now. I read the readme file that states reconsider your code. So I put a breakpoint over starttransaction. When press F8, in old times, after a while execution waited over the next line, But now, it just stay there and status is Running. That is
Startransaction line goes infinite loop.

Comments and Workarounds

Problem was caused by having two TDBISAMTable components attached to the same TDBISAMDatabase that were both pointing to the same physical data file. The result was that one transaction start would block the other transaction start attempt, and eventually a lock timeout error would be issued. The 1.09 release now includes individual StartTransaction, Commit, and Rollback methods for getting around this problem.

Resolution

Fixed Problem on 1/30/1999 in version 1.09 build 1

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap