2322108 - Update requests stay in initial status, enqueue lock entries remain after end of session

1. Some enqueue locks in SM12 are not released automatically, even if the enqueue owner already logged out, see Figure 1. And end users complain that they cannot process business transactions due to locking issues.
   

   Figure 1:Lock Entries, SM12

   It can be seen that these enqueue locks are handed over to update already with the result that the backup flag is set, see the Figure 2, and point .
   

   Figure 2:Lock Entry Details, SM12

   Whether enqueue locks are handed over to update or not also can be identified by different color like following:
   

   Figure 3: Lock Entries with and without backup flag set, SM12

2. In SM13, there are lots of update requests in ‘Initial’ status. Some business transaction is already saved by end user, but still not updated to database.
   

   Figure 4:Update Requests, SM13

   The update request was already sent to an update server, it can be seen from sm13-> goto->Update Header, see Figure 5, and point.
   

   Figure 5:Update Header, SM13

3. From ST22 you might see memory dumps LOAD_NO_ROLL, and work processes was stepped in to ‘PRIV’ mode (as it can be seen e.g. via SM50 or SM66).

NetWeaver Kernel 7.4x

LOAD_NO_ROLL, enqueue not released, update in ‘Initial’ status, EM dump, init, initial , KBA , BC-CST-UP , Update , BC-CST-MM , Memory Management , BC-CST-EQ , Enqueue , Problem