How To Fix 14079 - Shared lock statistics reset

14079 - Overview

• Message type: E = Error

• Message class: 14 - Task handler messages

• Message number: 079

• Message text: Shared lock statistics reset

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 14079 - Shared lock statistics reset ?

  The SAP error message 14079, which states "Shared lock statistics reset," typically occurs in the context of SAP systems when there is an issue related to the shared lock mechanism. This error can arise due to various reasons, including system performance issues, database locks, or inconsistencies in the lock table.
  
  Cause:
  
  Lock Table Overflow: The shared lock table may have reached its maximum capacity, leading to the reset of lock statistics.
  Database Performance Issues: Slow database performance or deadlocks can cause the lock statistics to reset.
  System Configuration: Incorrect configuration settings for the lock table size or related parameters can lead to this error.
  High Load: A high number of concurrent users or processes trying to access the same resources can lead to contention and reset of lock statistics.
  
  
  Solution:
  
  Increase Lock Table Size: If the lock table is too small, consider increasing its size. This can be done by adjusting the parameters in the SAP profile