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

SAP Error Message - Details

• 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: Use transaction code SM12 to check for existing locks on the InfoCube. If you find locks that are no longer needed, you can delete them (ensure that you have the necessary authorizations and that it is safe to do so).
  Monitor Processes: Use transaction code SM66 to monitor active processes in the system. Identify any long-running processes that may be holding locks and consider terminating them if they are not needed.
  Retry the Load: After resolving any locking issues, retry the data load or processing request that generated the error.
  Batch Processing: If you are running multiple data loads, consider scheduling them in a way that reduces concurrency and potential locking issues.
  Check for Errors: Review the logs for any previous errors that may have caused the current state. Use transaction codes like RSA1 (Data Warehousing Workbench) to check for errors in the data load process.
  System Configuration: Ensure that the system is properly configured for handling concurrent requests, including appropriate settings for lock timeouts and resource allocation.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: Display and manage locks.
  SM66: Global work process overview.
  RSA1: Data Warehousing Workbench for monitoring InfoCubes and data loads.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for relevant notes in the SAP Support Portal.
  Documentation: Review SAP BW documentation for best practices on data loading and handling locks.
  
  If the problem persists after trying the above solutions, it may be necessary to consult with your SAP Basis team or SAP support for further assistance.