How To Fix DB6PM795 - DBCFG - MAXLOCKS - SAP recommendation: at least 90

SAP Error Message - Details

• Message type: E = Error

• Message class: DB6PM - DB2 UDB for UNIX, Windows: Performance Monitoring

• Message number: 795

• Message text: DBCFG - MAXLOCKS - SAP recommendation: at least 90

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 DB6PM795 - DBCFG - MAXLOCKS - SAP recommendation: at least 90 ?

  The SAP error message DB6PM795 DBCFG - MAXLOCKS indicates that the maximum number of locks configured for the database has been reached or is set too low. This can lead to issues with database operations, as the system may not be able to acquire new locks when needed, potentially causing transaction failures or performance degradation.
  Cause:
  
  Insufficient Lock Configuration: The database configuration for the maximum number of locks (MAXLOCKS) is set lower than the required threshold for the operations being performed.
  High Concurrency: A high number of concurrent transactions or users may be trying to access the same resources, leading to a higher demand for locks.
  Long-Running Transactions: Transactions that hold locks for an extended period can exhaust the available lock resources.
  
  Solution:
  
  
  Increase MAXLOCKS: 
  
  The SAP recommendation is to set the MAXLOCKS parameter to at least 90. This can be done by modifying the database configuration settings.
  The exact method to change this setting will depend on the specific database system you are using (e.g., Oracle, SQL Server, etc.). Generally, you would access the database configuration settings through the database management interface or command line.
  
  
  
  Monitor Lock Usage: 
  
  Use database monitoring tools to analyze lock usage and identify any long-running transactions or processes that may be holding locks unnecessarily.
  Optimize queries and transactions to reduce lock contention.
  
  
  
  Review Application Logic: 
  
  Ensure that the application logic is designed to minimize lock contention, such as by using shorter transactions or implementing proper error handling and retries.
  
  
  
  Database Maintenance: 
  
  Regularly perform database maintenance tasks, such as updating statistics and rebuilding indexes, to improve overall performance and reduce lock contention.
  
  
  
  Related Information:
  
  Database Documentation: Refer to the documentation for your specific database system for detailed instructions on how to change configuration parameters.
  SAP Notes: Check SAP Notes for any specific recommendations or patches related to this error message.
  Performance Tuning: Consider engaging in performance tuning activities to optimize database performance and reduce the likelihood of encountering lock-related issues.
  
  By addressing the MAXLOCKS configuration and monitoring lock usage, you can mitigate the impact of this error and improve the stability and performance of your SAP system.