Professional Documents
Culture Documents
Applies to:
SAP NetWeaver BW 3.x. For more information, visit the EDW homepage.
Summary
This article explains about the error Lock Table Overflow" encountered when the specified limit of Lock entries maintained with the Parameter enque/table_size which determines the size of the lock table in KB is Overflown.Articles briefs about the error Lock Table Overflow encountered when trying to collect large set of Objects to a Transport Request. Author: Rudra Pradeep Reddy Neelapu
Author Bio
Working as a BI Consultant with Deloitte Consulting India Pvt.Ltd., Skill set includes SAP Business Intelligence, ABAP and Business Objects.
Table of Contents
Introduction ......................................................................................................................................................... 3 Background Information...................................................................................................................................... 3 Lock Concept .................................................................................................................................................. 3 Lock Table ....................................................................................................................................................... 3 Use.. ............................................................................................................................................................ 3 Subsequent Analysis of Lock Table Overflows .................................................................................................. 3 About Lock Table Overflow error ........................................................................................................................ 3 Maintaining the Profile Parameter ...................................................................................................................... 8 Reason and Prerequisites for Lock Table Overflow ......................................................................................... 10 Lock management ............................................................................................................................................ 10 Diagnosis ...................................................................................................................................................... 11 Diagnosis in update....................................................................................................................................... 11 Statistics ........................................................................................................................................................ 13
Features ..................................................................................................................................................................... 13
Introduction
The error Lock Table Overflow is encountered when the configured lock table limit is too small. Lock entries are maintained with the Parameter enque/table_size. Parameter enque/table_size determines the size of the lock table in KB. This articles explains the scenario of Lock Table Overflow encountered when trying to collect large set of Objects to a Transport Request and steps taken to address the issue with the help of BASIS team. Before going ahead lets have brief information about Lock Entry and Lock Table concepts.
Background Information
Lock Concept The Purpose of lock mechanism in the SAP system is to synchronize the access to data on the database. Lock mechanism prevents two transactions from changing the same data on the database simultaneously. Lock Table The lock entries in the system need to be recorded. For this a table in the main memory of the enqueue server records the current locks in the system. For each elementary lock, the table specifies the owner, lock mode, name, and the fields in the locked table. Use The lock table is used to manage locks. Every time the enqueue server receives a lock request, the system checks the lock table to determine whether the request collides with an existing lock. If this is the case, the request is rejected. Otherwise, the new lock is written to the lock table.
On going with Diagnosis we can find that the error is because of Overflowed table when the System tried to enter SAP Locks in the Lock Table.
Below is the Log screen shot and we can find the Lock Management error in After Import Method.
We found the maximum number of Lock Entries recorded using SM12 -> Extras -> Statistics shows the statistics of the lock management, including the previous maximum fill levels (peak usage) of the partial tables in the lock table.
From the Profile Parameter Attributes we can find the default values of Parameter enque/table_size.
Below is the screen shot of Enqueue Statistics with reflected limits allowing for more Lock Entries.
On changing the parameter enque/table_size value with the help of BASIS we can increase the Lock Entries Limit. From the above screen shot we can find the maximum number of Lock Entries as 9085 while the earlier limit was 3603. Example: With the profile parameter "enque/table_size =32000, the size of lock table is set to 32000 KB (32 MB). With this setting, the tables can contain around 40000 entries. Note that the above sizes and numbers depend on various factors such as the kernel release, patch number, platform, address length (32/64-bit), and character width (Ascii/Unicode). Use the statistics display in SM12 to check the actual capacity of the lock table.
Lock management
Lock management contains a diagnosis function which can be used to determine the most important causes of malfunction. We can analyze the type of lock that exists and about the lock owners who have contributed to the lock table overflow. To achieve this purpose a history function is provided.
Diagnosis To determine the cause: Call transaction SM12 and choose "Extras" -> "Diagnosis" (new) checks the effectiveness of the lock management
Diagnosis in update Call transaction SM12 and choose "Extras" -> "Diagnosis in update" (new)
Below is the Screen Shot with Diagnosis in Update. Checks the effectiveness of the lock management in connection with updates
Statistics SM12 -> Extras -> Statistics (new) Shows the statistics of the lock management, including the previous maximum fill levels (peak usage) of the partial tables in the lock table. If the owner table overflows, cause 2 generally applies. In the alert monitor (RZ20), an overrunning of the (customizable) high-water marks is detected and displayed as an alert reason. If cause 2 applies, increasing the size of the lock table only delays the overflow of the lock table, but it cannot generally be avoided. For cause 3, you should consider a tuning of the task function Instead of issuing a large number of individual locks, it may be better to use generic locks (wildcard) to block a complete subarea. This will also allow you to considerably improve the performance. Features The following information on the last 10 lock table overflows is saved: The three lock owners with the most locks The three lock arguments with the most locks
Activities
Total Capacity Used On the List of Lock Entries screen choose the menu option Extras Top Capacity Used
Current The current capacity used status is displayed. History The overflow history is displayed. The person responsible, his or her user name, the time, and the number of locks are listed. Delete History The overflow history is deleted.
Related Content
http://forums.sdn.sap.com/thread.jspa?threadID=38586 http://forums.sdn.sap.com/thread.jspa?threadID=1801992 http://help.sap.com/saphelp_nw70ehp1/helpdata/EN/47/ea5e27e97f486ee10000000a42189d/content.htm For more information, visit the EDW homepage