How To Fix DB6PM735 - DBCFG - LOCKLIST: value is higher than recommended upper limit &1

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 735

• Message text: DBCFG - LOCKLIST: value is higher than recommended upper limit &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 DB6PM735 - DBCFG - LOCKLIST: value is higher than recommended upper limit &1 ?

  The SAP error message DB6PM735 DBCFG - LOCKLIST: value is higher than recommended upper limit &1 typically indicates that the lock list size configured for the database is set higher than the recommended upper limit. This can lead to performance issues or instability in the database system.
  Cause:
  
  Configuration Settings: The lock list size is configured in the database settings, and it may have been set too high, exceeding the recommended limits.
  Database Load: An increase in the number of concurrent users or transactions may have led to a higher demand for locks, prompting an administrator to increase the lock list size.
  Database Version: Different versions of the database may have different recommendations for lock list sizes.
  
  Solution:
  
  Review Configuration: Check the current configuration of the lock list size in the database settings. This can usually be done through the database administration tools or SQL commands.
  Adjust Lock List Size: If the lock list size is indeed higher than the recommended limit, consider reducing it to a value within the recommended range. This can often be done through a configuration file or database command.
  Monitor Database Performance: After making changes, monitor the database performance to ensure that the new settings are effective and that there are no adverse effects on performance.
  Consult Documentation: Refer to the database documentation for specific recommendations regarding lock list sizes based on your database version and workload.
  Test Changes: If possible, test the changes in a development or test environment before applying them to production to ensure that they do not negatively impact the system.
  
  Related Information:
  
  Database Documentation: Always refer to the official documentation for your specific database (e.g., SAP HANA, DB2, etc.) for guidelines on lock list configurations.
  SAP Notes: Check SAP Notes for any specific recommendations or patches related to this error message.
  Performance Tuning: Consider overall database performance tuning, which may involve adjusting other parameters in addition to the lock list size.
  Support: If the issue persists or if you are unsure about making changes, consider reaching out to SAP support or your database administrator for assistance.
  
  By addressing the lock list size and ensuring it is within the recommended limits, you can help maintain the stability and performance of your SAP system.