Hello Shrikant,

With concurrency, there is always the potential of lock conflicts and deadlocks.
Event archival tries to delete event(s), while other parts of OBM may try to update the same event(s).

There is not much you can do other than what the error already suggests: Rerun the transaction.

I'm not sure if event archival does a retry or not. If it continues without erroring out, it probably does a retry, or it simply skips events that caused an error.

If it terminates due to the deadlock, then just run the archival again.

Best regards,
Tobias

Hi TObias,

Thanks for your response!

We are facing this issue since past few weeks, and we have tried to run the query many times still same error.

Found this KB but not sure if this resolves the issue, need to test

Automatic event archiving doesn't work properly in OBM with MSSQL

Hello,

Please try archiving smaller chunks of events.  For example, find out the oldest event on your system and archive these events (e.g. they are 10 days old).  Next, archive the next day (day 9), then the next (day 8) and so on.  I'd expect one archive will fail, but at least you'll have archived the older events and your database will be much happier.  I think trying to find the problem event is a little more difficult, which is why I'd rerun the archive as suggested above.