How To Fix DBMAN958 - Lock problem: Inclusion of new SIDs from request &2 (InfoCube &1)

DBMAN958 - Overview

• Message type: E = Error

• Message class: DBMAN - Data Manager Message Class

• Message number: 958

• Message text: Lock problem: Inclusion of new SIDs from request &2 (InfoCube &1)

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message DBMAN958 - Lock problem: Inclusion of new SIDs from request &2 (InfoCube &1) ?

  The SAP error message DBMAN958 indicates a lock problem related to the inclusion of new System Identifiers (SIDs) from a request in an InfoCube. This error typically occurs during data loading or processing in SAP BW (Business Warehouse) when there are issues with data locks or when the system is unable to process the request due to existing locks.
  
  Cause:
  
  Data Locking: The error usually arises when there are existing locks on the InfoCube or the data being processed. This can happen if another process is currently accessing or modifying the same data.
  Long-running Processes: If a long-running data load or update process is in progress, it may prevent other requests from being processed.
  Inconsistent Data State: If the data state is inconsistent due to previous failed loads or interruptions, it may lead to locking issues.
  Concurrency Issues: Multiple users or processes trying to access the same data simultaneously can lead to lock contention.
  
  
  Solution:
  
  Check Locks: