> Hi Alexey, > > Thank you for posting. The full error text is : > > lock conflict on no wait transaction. deadlock. update conflicts with > concurrent update. concurrent transaction number is 36094733 > > lock conflict on no wait transaction. deadlock. update conflicts with > concurrent update. concurrent transaction number is 3590088 > > It repeats the same changing only the transaction number. This is > happening with different databases in different servers.
At least two UPDATE statements are updating the same record(s) (and the first hasn't committed yet), and the latest gets this error due to the no wait transaction option. The provided numeric transaction ID in combination with the MON$TRANSACTIONS table should help you to identify the transaction with the first, non-committed update statement. -- With regards, Thomas Steinmaurer http://www.upscene.com/ Professional Tools and Services for Firebird FB TraceManager, IB LogManager, Database Health Check, Tuning etc.
