BC_BOR021 - Lock could not be set (system error)

SAP Error Message - Details

• Message type: E = Error

• Message class: BC_BOR - BC Training (All Courses)

• Message number: 021

• Message text: Lock could not be set (system error)

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 BC_BOR021 - Lock could not be set (system error) ?

  The SAP error message BC_BOR021: Lock could not be set (system error) typically indicates that there is an issue with the locking mechanism in the SAP system. This error can occur for various reasons, and understanding the cause is essential for finding a solution.
  Causes:
  
  Database Lock Table Full: The lock table in the database may be full, preventing new locks from being set.
  Lock Entry Corruption: There may be corruption in the lock entries, which can lead to issues when trying to set new locks.
  System Resource Issues: Insufficient system resources (like memory or CPU) can lead to failures in setting locks.
  Network Issues: Problems with network connectivity can also cause issues with lock management.
  Configuration Issues: Incorrect configuration settings in the SAP system can lead to locking problems.
  Long-running Transactions: If a transaction is holding a lock for an extended period, it may prevent other transactions from acquiring the necessary locks.
  
  Solutions:
  
  
  Check Lock Table Size: 
  
  Use transaction code SM12 to check the lock entries. If the lock table is full, consider increasing its size in the database configuration.
  
  
  
  Clear Locks: 
  
  In transaction SM12, you can delete unnecessary lock entries, especially if they are orphaned or belong to terminated sessions.
  
  
  
  Monitor System Resources: 
  
  Use transaction SM50 or SM66 to monitor the system's performance and check for any long-running processes that may be holding locks.
  
  
  
  Review Configuration: 
  
  Check the configuration settings related to locks in the SAP system. Ensure that they are set correctly according to the system's requirements.
  
  
  
  Check for Network Issues: 
  
  Ensure that there are no network connectivity issues that could be affecting the communication between the application server and the database.
  
  
  
  Restart the Application Server: 
  
  If the issue persists, consider restarting the application server to clear any temporary issues that may be affecting the locking mechanism.
  
  
  
  Consult SAP Notes: 
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SM12: To view and manage lock entries.
  SM50/SM66: To monitor active processes and their status.
  SM21: To check system logs for any related errors or warnings.
  
  
  
  SAP Basis Team: If the issue cannot be resolved through the above steps, it may be necessary to involve the SAP Basis team for deeper analysis and resolution.
  
  
  Documentation: Always refer to the official SAP documentation for the most accurate and detailed information regarding error messages and system configurations.
  
  
  By following these steps, you should be able to diagnose and resolve the BC_BOR021 error in your SAP system.