Sometimes you face such issues in SAP BW which may drive you crazy and this deadlock issue is one of them. I have recently resolved this infamous dump so decided to share my experience with you all. Before any further delay, let me tell you the system & database details about my system.

Component/System Values
SAP_BW 740
Database System MSSQL
Kernel Release 741
Sup.Pkg lvl. 230

Let me first explain what is deadlock.

A database deadlock occurs when two processes lock each other’s resources and are therefore unable to proceed.  This problem can only be solved by terminating one of the two transactions.  The database more or less at random terminates one of the transactions.

Example:

Process 1 locks resource A.

Process 2 locks resource B.

Process 1 requests resource A exclusively (-> lock) and waits for process 2 to end its transaction.

Process 2 requests resource B exclusively (-> lock) and waits for process 1 to end its transaction.

For example, resources are table records, which are locked by a modification or a Select-for-Update operation.

Following dump is expected when you will upload master data attribute.

Dump1.jpg

Sometimes you might encounter this dump too.

Dump2.jpg

Solution:

In order to avoid this issue please make sure that your DTP does not have semantic grouping ON and it’s processing mode should be “Serially in the Background Process”. To be on the safe side, I would recommend to create new DTP with these settings.

Please let me know if you find this blog helpful or not.

P.S. This was related to time-dependent master data.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Mario Tibollo

    And what if we really need to use the semantic grouping? Or, if serial processing is not possible due to performance reasons? What would you then propose as solution?

    M.

    (0) 

Leave a Reply