Subject | Re: [firebird-support] Deadlock error from firebird during midnight |
---|---|
Author | Dimitry Sibiryakov |
Post date | 2017-11-30T14:29:45Z |
30.11.2017 14:31, 'Joje' joje@... [firebird-support] wrote:
whom belong transaction from first error message.
Don't forget to change transaction isolation level from default (for .NET provider)
"read committed no record version" to "read committed record version at least" or, better,
"snapshot".
--
WBR, SD.
> Interesting part is this error occurs only at midnight from 12 to 2 AM. Thereafter,These application don't start transaction in Firebird database. Run audit and find out
> everything goes smoothly without any error. I tried replicating this on my test machine
> but no success.
>
> On analysing the pattern I think at midnight some CPU intensive applications like
> (/Machine backup or AV scanning etc/.) might be running on server machine.
whom belong transaction from first error message.
Don't forget to change transaction isolation level from default (for .NET provider)
"read committed no record version" to "read committed record version at least" or, better,
"snapshot".
--
WBR, SD.