Deadlock. Update conflicts with concurrent update.

This happens when your transaction tries to update or delete a record that some other transaction updated or deleted. This is a normal event in database world and your application should be ready to deal with it.

This 'problem' is quite easy to reproduce, so you can play with it. Just open two isql sessions, run the same update query and then try to commit both transactions.

Please note that this problem is not always easy to debug, as there might be stored procedures or triggers involved that run the update on some table at certain time. If you find such hard to catch problem, adding some logging of queries via external tables (which are outside transaction control) might help.

If you designed your system in such way that deadlocks happen often, consider using NO WAIT transactions, so that you get the error instantly instead of waiting for deadlock timeout.

If you perceive deadlock as a problem you cannot solve, look into selecting a different isolation modes for transactions in your application.

Do you find this FAQ incorrect or incomplete? Please e-mail us what needs to be changed. To ensure quality, each change is checked by our editors (and often tested on live Firebird databases), before it enters the main FAQ database. If you desire so, the changes will be credited to your name. To learn more, visit our add content page.

All contents are copyright © 2007-2024 unless otherwise stated in the text.

Links   Firebird   News   FlameRobin   Powered by FB: Home Inventory   Euchre  
Add content   About  

 Installation and setup
 Backup and restore
 Connectivity and API
 Errors and error codes