About Lock Entries and Lock Table Overflow

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

Company: Deloitte Consulting Created on: 1 January 2011

Author Bio
Working as a BI Consultant with Deloitte Consulting India Pvt.Ltd., Skill set includes SAP Business Intelligence, ABAP and Business Objects.

SAP COMMUNITY NETWORK © 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 1

....................... 16 SAP COMMUNITY NETWORK © 2011 SAP AG SDN .................................................................... 15 Disclaimer and Liability Notice ................................................................................................................................... 3 Lock Table ................................ 13 Features .......................................................... 3 Use….....................................com 2 ...........................................................................................................................................................................................................................sap......................................................................................... 3 Subsequent Analysis of Lock Table Overflows ...................................................................................................................................sap........................................................................................................................................................................................................ 14 Delete History ...........................sap............................................................. 3 Maintaining the Profile Parameter ................................................................................................. 3 Background Information............... 11 Statistics .................................................................................. 14 Total Capacity Used ........................ 11 Diagnosis in update.....................................................com | BPX .............................................. 14 Current .......................................................................................................................... 13 Activities ........................................ 14 History .................................................................................................................................................................................................................................................................................................................................................................................... .................................................................sdn.......................................................................................................... 3 About Lock Table Overflow error ................................................................................... 10 Diagnosis ................................................. 3 Lock Concept ................................................................................boc............................................................................................................................................................................About Lock Entries and Lock Table Overflow Table of Contents Introduction .................................com | BOC .bpx................................... 14 Related Content ........................................................................................... 8 Reason and Prerequisites for Lock Table Overflow ........................................................................................................................................................ 10 Lock management ............................................................................................................................................................................

About Lock Entries and Lock Table Overflow Introduction The error “Lock Table Overflow” is encountered when the configured lock table limit is too small. About Lock Table Overflow error We faced the error “Lock Table Overflow” during the BI content activation and when trying to collect large set of Objects to a Transport Request. Before going ahead let’s have brief information about Lock Entry and Lock Table concepts. the table specifies the owner. Lock mechanism prevents two transactions from changing the same data on the database simultaneously. as the number of Lock entries has exceed the upper limit of maximum locks specified in the Lock Table. Screen shot of error resulted when collecting the Objects. which can be defined in a profile parameter. lock mode.bpx. For each elementary lock.com | BPX .com 3 . the request is rejected. Below are the error screen shots and suggestions from help for reference. If this is the case.sap. Parameter enque/table_size determines the size of the lock table in KB. the new lock is written to the lock table.sap. Use The lock table is used to manage locks. Every time the enqueue server receives a lock request.boc. the system checks the lock table to determine whether the request collides with an existing lock. 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. Background Information Lock Concept The Purpose of lock mechanism in the SAP system is to synchronize the access to data on the database. and the fields in the locked table. This error resulted because of Overflow of Lock entries. Subsequent Analysis of Lock Table Overflows The maximum number of locks in the lock table is subject to an upper limit.sap. Otherwise. Lock entries are maintained with the Parameter enque/table_size.com | BOC . For this a table in the main memory of the enqueue server records the current locks in the system. SAP COMMUNITY NETWORK © 2011 SAP AG SDN . You can determine both the maximum number and the current number of entries in the transaction using Extras/Statistics.sdn. Lock Table The lock entries in the system need to be recorded. name. Parameter enque/table_size determines the size of the lock table in KB.

bpx. Below is the Log screen shot and we can find the Lock Management error in After Import Method.com | BOC .boc.com 4 .sap.About Lock Entries and Lock Table Overflow 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.com | BPX .sdn. SAP COMMUNITY NETWORK © 2011 SAP AG SDN .sap.sap.

com 5 . including the previous maximum fill levels (peak usage) of the partial tables in the lock table.bpx.sdn.sap.boc.com | BPX .About Lock Entries and Lock Table Overflow We found the maximum number of Lock Entries recorded using SM12 -> Extras -> Statistics shows the statistics of the lock management.sap.com | BOC .sap. SAP COMMUNITY NETWORK © 2011 SAP AG SDN .

com | BPX .boc.sap.About Lock Entries and Lock Table Overflow From the Profile Parameter Attributes we can find the default values of Parameter enque/table_size.bpx.com 6 . SAP COMMUNITY NETWORK © 2011 SAP AG SDN .sdn.sap.sap.com | BOC .

About Lock Entries and Lock Table Overflow SAP COMMUNITY NETWORK © 2011 SAP AG SDN .com | BOC .sdn.sap.sap.bpx.com 7 .boc.com | BPX .sap.

sap.About Lock Entries and Lock Table Overflow Maintaining the Profile Parameter From the below steps you can have an idea of how we can find the Default values of Parameters. The following table describes the main profile parameters associated with the lock mechanism.boc.bpx.com | BPX .(For this we required the authorization to necessary set of Tcodes and Authorization Objects).sdn.sap.sap.com 8 .com | BOC . You can obtain a complete overview by searching for the parameters with the entry *enq* in transaction RZ11 Below is the screen shot of Enqueue Statistics with reflected limits allowing for more Lock Entries. SAP COMMUNITY NETWORK © 2011 SAP AG SDN .

sap. the tables can contain around 40000 entries.com 9 .sap. Note that the above sizes and numbers depend on various factors such as the kernel release. patch number. and character width (Ascii/Unicode).bpx.com | BPX .boc.sdn. Use the statistics display in SM12 to check the actual capacity of the lock table.com | BOC . With this setting.About Lock Entries and Lock Table Overflow On changing the parameter enque/table_size value with the help of BASIS we can increase the Lock Entries Limit. address length (32/64-bit). SAP COMMUNITY NETWORK © 2011 SAP AG SDN . the size of lock table is set to 32000 KB (32 MB).sap. Example: With the profile parameter "enque/table_size =32000”. platform. From the above screen shot we can find the maximum number of Lock Entries as 9085 while the earlier limit was 3603.

About Lock Entries and Lock Table Overflow Reason and Prerequisites for Lock Table Overflow A lock table overflow can occur if: Cause 1: The dimensions of the lock table are too small i.bpx. Cause 3: The application programs are poorly designed.boc.sap. SAP COMMUNITY NETWORK © 2011 SAP AG SDN . so that the lock entries of the update requests that are not yet updated cause the lock table to overflow. for example a collective run with many objects.com 10 . To achieve this purpose a history function is provided. the lock table configured is too small. The update process is hanging and this is passing a lot of locks onto the update task.sap.sdn. And the application sets a large number of locks Causes of malfunctions in lock management can be:      The enqueue server is not available The message server is not available Faulty computer connections Incorrect system installation Incorrect setting of system parameters Lock management Lock management contains a diagnosis function which can be used to determine the most important causes of malfunction.e. A lock is issued for each object in an application program. Cause 2: The update lags far behind or has shut down completely.com | BPX .sap.com | BOC . We can analyze the type of lock that exists and about the lock owners who have contributed to the lock table overflow.

com 11 .sap.sdn.About Lock Entries and Lock Table Overflow 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.com | BPX .sap.com | BOC . Checks the effectiveness of the lock management in connection with updates SAP COMMUNITY NETWORK © 2011 SAP AG SDN .boc.sap.bpx.

com | BPX .About Lock Entries and Lock Table Overflow SAP COMMUNITY NETWORK © 2011 SAP AG SDN .sap.sap.bpx.com | BOC .boc.com 12 .sdn.sap.

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 SAP COMMUNITY NETWORK © 2011 SAP AG SDN . cause 2 generally applies.About Lock Entries and Lock Table Overflow 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.com 13 .sap.boc.sdn. If the owner table overflows. If cause 2 applies. it may be better to use generic locks (wildcard) to block a complete subarea. increasing the size of the lock table only delays the overflow of the lock table.com | BOC .sap.sap. you should consider a tuning of the task function Instead of issuing a large number of individual locks. This will also allow you to considerably improve the performance. In the alert monitor (RZ20).bpx. but it cannot generally be avoided. an overrunning of the (customizable) high-water marks is detected and displayed as an alert reason.com | BPX . For cause 3.

sap.com | BOC . and the number of locks are listed. Delete History The overflow history is deleted.boc. the time.com | BPX . his or her user name.bpx.About Lock Entries and Lock Table Overflow 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.sdn.sap. History The overflow history is displayed.sap.com 14 . SAP COMMUNITY NETWORK © 2011 SAP AG SDN . The person responsible.

sap.sdn.com/saphelp_nw70ehp1/helpdata/EN/47/ea5e27e97f486ee10000000a42189d/content.com | BOC .sdn.com/thread.bpx.com 15 .com/thread.htm For more information.sap.jspa?threadID=1801992 http://help.sap.jspa?threadID=38586 http://forums.sap.sap. visit the EDW homepage SAP COMMUNITY NETWORK © 2011 SAP AG SDN .boc.About Lock Entries and Lock Table Overflow Related Content http://forums.com | BPX .sap.sdn.

sap. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample.bpx. or seek to hold. Changes made based on this information are not supported and can be overwritten during an upgrade.com | BPX .sap. and anyone using these methods does so at his/her own risk.com 16 .sap. You agree that you will not hold. SAP will not be held liable for any damages caused by using or misusing the information. including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. SAP COMMUNITY NETWORK © 2011 SAP AG SDN . code or methods suggested in this document.boc.com | BOC . SAP responsible or liable with respect to the content of this document.About Lock Entries and Lock Table Overflow Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP.sdn.

Sign up to vote on this title
UsefulNot useful