Solution : https://service.sap.com/sap/support/notes/552289 (SAP Service marketplace login required)
Summary :
This SAP Note provides guidance on managing the lock table effectively, addressing the sizing, wait times in syslog, communication methods in lock management, and the definitions of "black" and "blue" locks. It is recommended to start with a lock table size of 20 MB to avoid transaction terminations while using minimal resources. The note clarifies that communication within lock management involves several steps across various processes and servers, utilizing the message server, RFC, and potentially leading to the overload of central instances without sufficient dialog processes. Additionally, black locks represent normal transaction locks, and blue locks are specific to the update system. Monitoring tools and profile parameters, such as enque/table_size and enque/delay_max, are highlighted for optimal configuration.
Key words :
work process -> dispatcher -> message server -> dispatcher -> enq work process, work process -> gateway -> gateway -> dialog process, enq work process, profile parameter enque/delay_max, enqu/table_size solution [1] question, system rejects lock requests, dialog work processes, application server sets, enq process, enque/table_size = 20000you
Related Notes :
| 1552733 | CD: Lock table overflows when deleting |
| 1423066 | Optimization of the performance in EWM |
| 1118297 | XI runtime: QRFC processing of messages |
| 923610 | Memory parameter recommendations for banking systems |
| 852524 | Deletion of reservations from APO |