Table index creation resulted in Database Deadlock, Updates failed.

[Former Member]

Dear Experts,

It seems one of our customers had did some Table Index recreation ( by importing a transport request )

during working hours in production system, which resulted in immediate Database Deadlock.

We confirmed some deadlock error logs in SM21 and also some update (SM13) had failed.

In this situation I would like you answer the following:

01. We would like to completely analyze the impact with regard to the system

stability and Data consistency. please mention some useful points to analyze.

02. Also If possible how would you find which user has been affected by this deadlock.

( for ex. transactions / data updated by the user / what went wrong.

Best Regards

Raghunahth L

Useful System Info.

OS : Windows

DB: MS SQL Server 2000 SP4

SAP: R/3 4.70

[markus_doehr2 · Accepted solution]

A deadlock is usually resolved by the database itself. What you maybe have seen is the fact, that during index creation all modification operations on the affected table are blocked until the index creation is finished. Depending of the size of the table and the speed of the underlying I/O system this can take quite some time.

If you know the table name I would have a look in SE11/SE14 for versions, usually you can also see in the syslog which user did try to add an index.

Markus