Solution : https://service.sap.com/sap/support/notes/13907 (SAP Service marketplace login required)
Summary :
The error described pertains to an overflowed lock table, indicated by syslog messages and transaction failures in MM02, FBRA. The lock table may overflow due to three primary reasons: insufficient table size, lagging or halted updates, and poorly designed application programs causing excessive locks. To diagnose, transactions SM12 and techniques such as "Goto -> Diagnosis" and "Extras -> Diagnosis in update" are employed. Resolution involves adjusting the profile parameter "enque/table_size" to increase table capacity, monitoring updates, and mitigating poor application designs using generic locks. The alert monitor (RZ20) helps in identifying and managing high-water marks for preventive measures.
Key words :
updatessm12 -> okcode test -> error handling -> statistics, previous maximum fill levels, lock managementcall transaction sm12, call transaction sm12, sm12 -> extras -> statistics, high-water marks, set to32000 kb, interactive work process, approx 5400name table, approx 5400entry table
Related Notes :
| 1012446 | Mass transactions: Error message MC603, Lock table overflow |
| 1000476 | ISJP_CR number of locks is limited |
| 731872 | Technical Idoc Customizing for MI server |
| 642801 | Message T0902 |
| 534979 | HR-GB: P45 report can not lock all employees in live |
| 410372 | Shipping order: Blocking problems during import |
| 208192 | Causes for message V1042 when creating sales orders |
| 97760 | Enqueue: Performance and resource consuption |
| 68504 | Error MC600 or M3021 during release of costing |
| 34985 | IL02/IE02:Lock problems in large object hierarchies |