File to Idoc error:"Lock table overflow"

When I post 3000 records I see 3000 idocs generated in ECC successfully, when I try to post 4000 idocs I get an error in PI "Lock table overflow" in SM58, please help
Thanks

Hi.
The error could be due to following:
1. small size of lock table
2. a particular program sets a large no of locks
3. an update process hangs hence setting a large number of locks
please check below thread.
Lock table overflow
Also check below link frm help.sap.
http://help.sap.com/saphelp_nw70/helpdata/en/d3/43d2416d9c1c7be10000000a1550b0/frameset.htm
Hope this helps.
Regards,
Deepak.
Edited by: Deepak Shah on Feb 8, 2011 4:48 AM

Similar Messages

Lock table overflow - Delta (fetch)

Hi,
I have an InfoCube which contains large amount of data. Before starting to extract data from this InfoCube, I want to set datamart status as fetched to start extractions with new coming requests.
However, when I choose the processing mode of DTP as "9 No Data Transfer; Delta Status in Source: Fetched" and execute the DTP, it ends with an error: "Lock table overflow".
Is there any way to solve this without increasing the lock table parameters (enque/table_size) ?
Regards,
Erdem

You need to first resolve the issue with the "Lock table Overflow"....usign the below method in RZ10.
Here you can solve the problem in two ways
1) increase the size of the lock table via parameter
enque/table_size
2) or increase the enque work processes from 1 to 2 or 3
via parameter rdisp/wp_no_enq
Ask Basis team for their assistance on the same.
Thanks
Murali

Lock table overflow in SAP

We are tyring to execute a transaction and it is giving the error Lock table overflow, Though the enque/table_size parameter is set to 96,000 KB which i guess good enough.
Can you please suggest.
Thanks,
Chandu

Hello Chandu,
how many records this transaction is locking?
SAP Note 746138: Analyzing lock table overflows, describes how to analyze this issue.
Are you using Standalone enqueue? If that's the case check that the enqueue table size is defined in the ASCS instance.
kind regards,
Mercedes

Lock table overflow - BRF Plus - can it work with many entries in tables ?

hi,
when I'm trying to open expression table in BRFplus with 500 entries in web
I get an error: Lock table overflow and I see more then 2000 entries in sm12 for fdt_ tables
and the system cannot create any more locks (so other applications are not working)
why is that ? can BRF plus work with more then 100 entries in table expressions at all ?
can anyone tell from experience as this is a huge issue I believe
thank you,
Regards,
Michal Krawczyk

Hi Michal,
You are running a NW 701 system. This was the first version of BRFplus and the DB schema was not good for high volumne.
I have created some notes recommending to use decision table for up to 100 rows (of course other factors like # of columns are also important).
In NW 702 the DB schema has been changed and decision tables with 10.000 rows are possible and performance better by a factor of 100 and more.
In your specific case you may consider to increase the number of logs that are possible. But this is rather a workaround than a solution.
BR,
Carsten

Lock table overflow 1 & Error 7 when sending an IDoc

dear all,
we r getting error in purchasing cube for itm datasource
2lis_o2_itm for delta...
1.Lock table overflow 1
2.Error 7 when sending an IDoc
3.Errors in source system
when i check in details it is showing :
Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
its daily delta..plz give me solution its urgent....
at request in manage...we got some records...wat shud the process..
Thanks in adv
pinky reddy
Edited by: pinky reddy on Apr 8, 2008 7:42 AM

solved

IDOC Receiver Adapter, getting Lock Table Overflow to CRM System

Hello SDN!!!
This scenario is for PI to process a file and send to CRM via IDOC. The IDOCu2019s are only being created and not processed until later.
Problem: I am getting a Lock Table Overflow error in method IDOC_INBOUND_ASYNCHRONOUS via sm58 in PI which points to the CRM box.
I have been searching many forums and every solution seems to indicate increasing the lock table, the problem with that solution is we are currently trying to create (not process yet) 80000 IDOCu2019s. This would allocate too much for the lock table.
So my question is this, Shouldnu2019t the lock be released when the IDOC gets created or none the less when a packet of IDOCu2019s via content management (breaking up the file in 1000 increments) finish. The lock table in CRM keeps increasing until all rows from the file, sent via IDOC adapter in 80 messages with 1000 IDOCu2019s per messagein the table are complete (80 separate messages in sxmb_moni).
Background:
IDOC was imported, changed to include unbounded and reimported.
Content Management breaks the file into 80 different segments, thus creating 80 distinct mappings with distinct MessageIdu2019s.
80 IDOC packets are sent to CRM, via IDOC adapter and sm58.
TCODE sm12 in CRM shows the table to keep growing and locks not released until full message is complete.
Any help would be appreciated
Cheers
Devlin

The only way to process the IDOCs in this case is by increasing the "enque/table_size" parameter in order to create the required IDOCs. You can increase the value for this parameter up to 102400 (beyond that can cause performance issues). Since you need to handle 80000, this shouldn't be an issue.
Please refer to the notes below for more information about the lock queue overflow and management.
[Note 552289 - FAQ: R/3 Lock management|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=552289]
[Note 13907 - System error in the block handler, overflow lock table|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=13907]

Lock table Overflow as the file size is 50 MB BW side.

Hello Everyone,
I have a XML idoc file as input which is usually more then 50MB in size.
Usually, i am getting Lock table overflow at Receiver BW side . This error is pointing to Inbound_Asynchronous_Idoc.
i have tried dividing the Input XML idoc file into small group by handling them in chunk mode of sender communication channel.
However, since its TRFC , so if it gets processed in PI but at outbound if there is an Lock table overflow error, then it fails.
I have tried to process the 50 MB of file in parts by processing 5 MB at one point of time. but does this mean that BW also process data in parts or it gets entire 50 MB to process at one stretch.
Since the input is IDOC XML so i was not able to make use of Record Set per message. so i am making use of chunk mode.
AM i doing correctly ?
Regards,
Ravi

Hi Ravikanth,
If i make use of the below logic as mentioned in the link that you provided, then do i have to remove the chunk mode from communication channel .?
Secondly, mine is a SLSFCT idoc XSD that i am using here as source and target as well.
The hirearchy becomes like this after implementing the logic mentioned in link:
Messages
Message1
Z1ZBSD_SLSFCT01
IDOC
BEGIN
EDI_DC40
For Messages and MEssages1 there is no mapping at target side.
For Z1ZBSD_SLSFCT01 its 1..1 in source and 0..unbounded in target.
For IDOC its mapped to constant and Begin to constant with value 1 .
And then EDIDC to source and target are mapped to each other with occurrence of 1..1.
Is there some thing wrong that i am doing . because after this again the files are not getting divided
Regards

Error " RFC Status :- Lock table overflow "in event trace ( SWEL )

Hi experts ,
I will not mention this post as URGENT but you guys can understand the importance as I am in PRD Support of my workflows .
My Workflow is throughing error in SWEL , as below   and after error its getting deactivated .
The workflow is triigering based on the BO : DRAW and event CREATED .
Error : RFC Status           Lock table overflow
In feedback after error the message is : A system error has occurred in lock management .
I have resolved the deactivation problem after error , but   can any body please suggest me what is the root cause of this error , so that i can try to avoid that error .
Regards
Prabhudutta
Edited by: Prabhudutta Behera on Nov 20, 2008 5:58 AM

This error I have not faced. i will suggest you to check SWU3 transaction Code and check everything is configured. Also check SM12 and SM58. Also I will ask you to contact the Basis Guys related to this issue. Also check WF-BATCH is having all the authorization required. Try to replicate this from the system where Workflow is working.
Thanks
Arghadip

MC603 Lock Table Overflow Error in Maintenance Order Settlement

Hello,
I am running RKO7KO8G- "Settlement of Maintenance Orders" program in background. For few Orders I am getting "MC603:Lock Table overflow " error. What might be the problem for this?
Number of Order processed in a job is around 10,000.
I checked in SM12 table.No entry is found
Size of the Lock table details is
Min - 4096
Max - 102400
Diff Value - 4096
Profile Value - 10000
Current Value - 10000
Regards,

Hello Srinivas,
Please take a look at the below link.
http://help.sap.com/saphelp_nw04/helpdata/en/37/a2e3ab344411d3acb00000e83539c3/content.htm
As I already said, there is no standard value to define. You need to consider the no.of locks being generated and act accordingly to address this problem.
I suggest you please go through the lock management documentation to address this kind of problems in the feature.
Thanks,
Siva Kumar

Lock table overflow Error in BD91

Hi Sapper's,
Can anyone please tell me how to rectify the below error which occurs for me in T-Code - BD91.
MC603: Lock table overflow in T-Code BD91
Also please help me how to change the size of the profile parameter 'enque/table_size'
Please reply immeidately.
Regards,
Kumar.S

Dear,
Lock table overflows means that their are too many locks in the system at that point in time. Check SM12 to see these locks. Is your program causing all these locks or is it something else.
Please take help from technical person.
Also refer this link,
http://help.sap.com/saphelp_erp2005/helpdata/EN/c2/2d7037ecc92a7ee10000009b38f8cf/frameset.htm
Regards,
R.Brahmankar

Lock Table Overflow Error in SM58

Hi Team,
Error has observed on transactional RFC (SM58),it is happing every monday during business hours .So we observed that same day db2 automatic reorg job is running same day and same time in SAp PI .Please confirm is this issue with SAPPI or target system ?
Error Text: “Lock table overflow”
This issue has fixed after reorg job finished automatically .is there any relation b/w lock table and reorg job ?
I observed that this was due to DB2 reorg job causing the issue.Please correct me if am wrong ?
Regards ,
Ravindar.a

Hi
Please check the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/37/a2e3ba344411d3acb00000e83539c3/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/d3/43d2416d9c1c7be10000000a1550b0/frameset.htm
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/lock-table-overflow-506470
Mutti

"Lock table overflow" error msg when trying to change a repot program

hi ABAP experts,
We are getting the following error msg
"Lock table overflow
Choose 'Display object' or 'Cancel'.".
Click the question mark on the same error msg window, then the detailed error msg would like this:
Message no. MC603
Diagnosis
This table overflowed when trying to enter SAP locks in the lock table.
System Response
The locks could not be set.
Procedure
Contact your system administrator. If this error occurs frequently, change the size of the profile parameter 'enque/table_size'. This parameter defines the size of the lock table in KByte.
What would be the reason and how to resolve this problem?
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Apr 2, 2008 1:03 PM

Hi,
This could be bcos the lock table is getting overflowed beyond the allotted space. Check if any other program/BAPI is causing continuous creation of locks.
To analyze choose (SM12) Extras Statistics to display the statistics. These are the statistics that have been compiled since the last time the lock server was restarted.
Check the below link for more information on SAP Lock Concept.
http://help.sap.com/saphelp_nw04/helpdata/en/7b/f9813712f7434be10000009b38f8cf/content.htm
For details on Subsequent Analysis of Lock Table Overflows, check the below links.
http://help.sap.com/saphelp_nw2004s/helpdata/en/d3/43d2416d9c1c7be10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f0/b57338788f4d72e10000009b38f8cf/content.htm
Hope this helps. <REMOVED BY MODERATOR>
Thanks,
Balaji
Edited by: Alvaro Tejada Galindo on Apr 2, 2008 1:03 PM

Lock table overflow problem in transaction sm58

Hi ,
I have a file to idoc scenario.I am on xi 7.0 sp09.
I am posting about 10000 records at one time in a 1 mb file.
In idx5 i am able to idocs .
However in transaction SM58 I am seeing Lock table overflow error .
Regards ,
Deepak

Deepak,
Here you can solve the problem in two ways
1) increase the size of the lock table via parameter
enque/table_size
2) or increase the enque work processes from 1 to 2 or 3
via parameter rdisp/wp_no_enq
Please have a look on SAP Note: 928044.
---Satish

Error locking table TBTCO

Hi,
We are having issue in locking "Error locking table TBTCO" at our SM12 statics Maximum Number of Lock Owners     3603
Even on increasing the enque/table_size it not effecting the lock owner. Our environment having enq replication server.
The profile parameter for enque/serverinst = $(SCSID) (00)
enque replication server instance number is 10
What could be the correction need to be done?
Regards,
RMav

You have to check the reason for the error in the lock.
Get the Work Process number that logged the error in SM21. Check the trace file of this work proces. At the same timestamp of the error in SM21 you do find the root cause in the work process trace.
Usually this is caused by a overflow in the enqueue table, but not always. For this reason you have to check the work process trace the reasl root cause.
To check if the enqueue is suffering a overflow you should go to SM12 -> Extras -> Statistics
If in the statistics you do find that the "Maximum Fill Level" reached the maximum number of locks in these itens, for example:
Maximum Number of Lock Owners 39481
Maximum Fill level 458
Current Fill Level -25
Maximum Number of Lock Arguments 39481 <<<
Maximum Fill level 39480                                 <<<
Current Fill Level 15
Maximum Number of Lock Entries 39481    <<<
Maximum Fill level 39480                             <<<
this means that the enqueue was really suffering under an overflow situation.
Just for your information, the TBCTO is the table for the status of the jobs. So, every job need
to write the status in this table and also lock this table firstly.
Clébio

UCWB - Consolidation Workbench - Lock table overflow

Hello,
This is w.r.t SEM BCS. We are in the initial phase of consolidation implementation. When I try to execute UCWB - Consolidation Workbench, system is giving an error with Message No. MC603
Lock table overflow
Diagnosis
This table overflowed when trying to enter SAP locks in the lock table.
System Response
The locks could not be set.
Procedure
Contact your system administrator. If this error occurs frequently, change the size of the profile parameter 'enque/table_size'. This parameter defines the size of the lock table in KByte
Request you kindly reply in this regard.
Regards
Sreekanth

Hello Sreekanth
Have you implemented any note for this problem or adjusted the table parameters.I am also facing the same problem.Could you please let me know if there is any note which needs to be implemented.
thanks

File to Idoc error:"Lock table overflow"

Similar Messages

Maybe you are looking for