Parameter enque/table_size

Hello all
I would like to know what is the relation between the size of lock table ( defined by parameter "enque/table_size") and number of locks that could be handled.
If found only one related information in OSS note 13907 but it didn't helped me.
Thanks for help
Tomas

>
Tomas SESTAK wrote:
> Hello all
>
> I would like to know what is the relation between the size of lock table ( defined by parameter "enque/table_size") and number of locks that could be handled.
>
> If found only one related information in OSS note 13907 but it didn't helped me.
>
> Thanks for help
>
> Tomas
The relation cannot be translated directly from number of locks to used lock-space in K, since different lock objects have a different size.
therefore: only monitoring can give you a hint on how the situation of your landscape, CI is: [in this documentation|http://help.sap.com/saphelp_nw04/helpdata/EN/37/a2e3ab344411d3acb00000e83539c3/content.htm] you will find a general overview but also a link on how to look for statistics on your system ... as with every montoring/statistics: you will have to watch a while to get valid dates.

Similar Messages

  • Parameter enque/table_size  value

    Hi All,
    We face several times lock table overflow issue, Which cause users to hang up for some time for work.
    So we are planning to increase size of Enqueue table , I checked parameter enque/table_size it is set to 32768 in our system.
    Please suggest the recommandations to increase value of parameter enque/table_size or how can we calculate best suited value of this enq parameter.
    Regards,
    Shivam

    Hi,
    The enqueue ceiling is 1GB of memory, effectively giving you a maximum of 91,000+ locks.
    But as mentioned above, size the enqueue depending on  your system resources.
    I have in the past had a problem when on AIX where I increased the enqueue parameter and the system started up with no locks at all.
      This was due to some IPC parameter sizing in the instance profile..
    Mark

  • SCS Instance - enque/table_size

    Hi all,
    We need to adjust the parameter enque/table_size in our J2EE system. How can we define it in the SCS instance? We have already adjusted the parameter for the ABAP stack in RZ10. We have yet to adjust the parameter for the JAVA stack? How can we do this? Are we on the right track in SCS, or can we use exchange profile for this?
    Much appreciated, Thanks!

    Hello,
    Do you mean that after changing the profile  by editing the file and make a system restart the values of the profile file have been changed? Can you please then check the name of the profile and be sure that from RZ10 you did not change and activate that same profile?
    Regards,
    Blanca

  • Enque/table_size - Changing the parameter value

    Hi folks,
    I'm fairly new to SAP so was hoping for a bit of guidance with this matter.
    I need to increase the parameter value for "enque/table_size".  It's currently set to the default 4096kb and we're seeing a lot of lock table overflow errors.
    As the default value with Kernel 7.01 is 32MB, this seems like a good place to kick off.
    I've gone into RZ11 and entered the parameter name.
    Presumably, I select "CurrentValue" and Edit > Change Value?
    Because Change Value is greyed out.
    I have SAP_All in terms of authority. 
    So I'm a bit puzzlied!
    Any help would be appreciated.
    Thanks

    It seems your profile is not activated properly .
    First search for the value of the parameter in RZ11 or TU02 , If the value of the parameter is old proceed as either of the follows
    1 ) Go to /sapmnt/<SID>/profile ,  open the DEFAULT.PFL in an editor and add the entries . Bounce the system and check whetehr the entry appears in theRZ10 ( DEFAULT.PFL ) , since enqueue might be configured only in CI you can also do it in the instance profile
    2 ) Second option is to go to RZ10 , Open Default or instance profile ( Extended Maintainance ) , create the parametes ,Copy . Save . Activate the profile . Check version of the profile . Bounce the system and check again . This step is recommended
    Thanks ,
    Manu
    SAP Basis

  • Enque/table_size error

    hi,
    i have a problem that the enque/table_size is 32000 but the error is lock table overflow?
    the enque/table_size is max value?
    thanks in advance
    Ferhan

    This parameter defines the size of the lock table that is held in
    main memory by the enqueue server.
    The size of the lock table limits the maximum number of lock
    entries, In the case of an overflow of the lock table, you should check
    whether the update server is working correctly, since the lock table
    can grow in size very quickly if updates stop. If the cause is not
    update problems, you can use this parameter to increase the size of
    the lock table.
    You can view the fill level of the lock tables using the statistics
    functions of lock management (transaction SM12 -> Extras ->
    Statistics).
    This parameter can be increased up to a maximum of 102400

  • Parameter changes prevent SAP from starting

    Hello all,
    We are running SAP ERP 4.7ext 2.00 with two nodes in a Windows/MSSQL Cluster environment.
    1.     Last night, we made parameter changes to the central instance profile. In particular, we started with  adding the parameter “enque/table_size = 16384”, activated the profile and took the SAP R/3 RP1 Resource offline. We then tried to bring it back online but it went into a failed status. We removed this parameter using a text editor, and then retried to bring the SAP Resource online again, but to no avail – it went into a failed state again.
    2.     We had previously made backups of the profile files created by the reinstallation of the central instance (DEFAULT, START_DVEBMGS00_ZAASAPCCI001,  and RP1_DVEBMGS00_ZAASAPCCI001 – let’s call this File Set A.) and decided to use these files instead.  These files had the default parameters created on installation. We were successful in bringing the SAP resource online.
    3,     We made a parameter change and activated the profile in SAP – it does not matter which parameter you choose, for example, changing the number of dialog work processes from the default 2 to 20 . We took the SAP R/3 RP1 Resource offline but were unable to bring it back online - it went into a failed status.
    4.     We then took File Set A, and using a text editor  (1) made changes to the number of work processes; and (2) appended the extra parameters to them. Using these files we were now successful in bringing the SAP Resource online.
    5.     If we now made any changes to these files – either through SAP or by using the text editor, we are unable to restart SAP. We have to revert to step 4 above.
    6.     A strange anomaly we noticed is that if the profile files have the following commented lines in the beginning of the file  RP1_DVEBMGS00_ZAASAPCCI001. for example:
    #.*       Instance profile RP1_DVEBMGS00_ZAASAPCCI00                           *
    #.*       Version                 = 000007                                     *
    #.*       Generated by user = ABOOM                                            *
    #.*       Generated on = 11.05.2006 , 09:04:07                                 *
         Then we are unable to restart SAP.
    Is this a bug related to running a dual-node SAP cluster?  We were previously able to make parameter changes (either through SAP or through the use of a text editor) and restart SAP successfully.
    It is now become critical to determine the cause of this anomalous behaviour and resolve the problem. Failing this, the client wants to break the cluster and revert to a distributed SAP system installation (with separate DB and central instance hosts).
    Your comments and help wil be greatly appreciated.
    Regards,
    Lebo

    Hi Lebo,
    Can you try to edit your profiles (the correct ones) using sappad tool (/usr/sap/<SID>/<INST-ID>/run/exe/) and save it in the same format that was used to open it.
    Regards,
    Mike

  • System Lock Error while reset & reversing the cleared document - FBRA

    Hi Experts,
    Currently using t-code FBRA, when user trying to reset & reverse the cleared document , they are facing "System Lock Error". We have analyzed on this issue and found SAP note no. u201C487347 u2013FBRA: Overflow of the lock table in production systemu201D . After implementation of this note, SAP has created one new transaction code, FBRA_LOAC.
    However, when we tried to reset & reverse the cleared document using t-code FBRA_LOAC, we face the same error.
    Can you help me to resolve this issue ?
    Thanks in advance.
    Regards,
    Manish

    Hi:
          We once faced these issue and got it resolved by extending parameter after extending the profile-parameter "enque/table_size", as per note note 13907. Do not forget the restart the server after extension.
    Regards

  • BI content

    Hi All,
    I have fresh new BI IDES system with me.i want to install all the content like for Inventory and SD .
    I have gone to BI content and moved the info source for billing item -
    > in grouping i have given Data flow before and after - >  collection mode is Automatically-->now i clicked on INSTALL .
    but after sometime i got the error like "InfoCube 0RMA_C01 is not available" ...  "Checking InfoObject 0CM_CTAR"
    "InfoObject 0MATERIAL is not available in version A" .. "Checking InfoCube 0CM_C03 , 0CM_C05,0CM_C06, 0CM_C07,0CM_C08 ,0CM_C10" and many more.
    same way i am getting error for Inventory also like "many cubes are missing" since those cubes are not in use.
    So, all i need to know is do i have to make some settings or any configuration is required for that means to start work on BI ?
    Do please let me know... your help will be apperciated. 
    Regards,
    Komik Shah
    Edited by: komik shah on Sep 25, 2008 12:51 PM

    Hi
    The size of the parameter is normally set to 4096 kb only.
    But a lock table overflow can occur if:
    ·        The lock table is configured too small
    ·        An application sets a large number of locks
    ·        The update process is hanging and this is passing a lot of locks onto the update task.
    For the corrective measures, please refer the link below.
    http://help.sap.com/saphelp_nw04s/helpdata/en/d3/43d2416d9c1c7be10000000a1550b0/frameset.htm
    You can do one of the following things
    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
    Also check the link
    http://help.sap.com/saphelp_nw04s/helpdata/en/37/a2e3ab344411d3acb00000e83539c3/frameset.htm
    Hope this helps
    Regards
    Shilpa

  • Clearing in previous year

    Hi there
    I have an issue in resetting (using FBRA) clearing GL document which belongs to 2007. This clearing doc has few line items, which were generated while clearing other GL docs .
    While I thought it might be due to a closed period, I tested in my Quality system and I could reset clearing documents(which has no line items)  for last year(opened posting periods). In the same Quality system I am NOT able to reset few clearing documents, and the error is "System lock error: Inform system administrator" Message no. F5288.
    Can any body through advice on this issue.
    Many thanks in advance
    MSJ
    Edited by: MSJ on Sep 24, 2008 4:45 PM

    Go through the OSS note 13907 and ask your basis team to look into the issue:
    Reason and Prerequisites
    The lock table has overflowed.
    Cause 1: Dimensions of the lock table are too small
    Cause 2: The update lags far behind or has shut down completely, so that the lock entries of the update requests that are not yet updated cause the lock table to overflow.
    Cause 3: Poor design of the application programs. A lock is issued for each object in an application program, for example a collective run with many objects.
    Solution
    Determine the cause:
    SM12 -> Goto -> Diagnosis (old)
    SM12 -> Extras -> Diagnosis (new)
        checks the effectiveness of the lock management
    SM12 -> Goto -> Diagnosis in update (old)
    SM12 -> Extras -> Diagnosis in update (new)
        checks the effectiveness of the lock management in conjunction with updates
    SM12 -> OkCode TEST -> Error handling -> Statistics (old, only in the enqueue server)
    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.
    The size of the lock table can be set with the profile parameter "enque/table_size =<size>". <size> specifies the size of the lock table in kilobytes. The setting must be made in the profile of the enqueue server ( ..._DVEBM.. ). The change only takes effect after the restart of the enqueue server.
    The default size is 500 KB in the Rel 3.1x implementation of the enqueue table. The resulting sizes for the individual tables are:
    Owner table: approx 560.
    Name table:  approx 560.
    Entry table: approx 2240.
    As of Rel 4.xx the new implementation of the lock table takes effect.
    It can also be activated as described in note 75144 for the 3.1I kernel. The default size is 2000 KB. The resulting sizes for the individual tables are:
    Owner table: approx 5400
    Name table:  approx 5400
    Entry table: approx 5400
    Example: with the
    "enque/table_size =32000" profile parameter, the size of the enqueue table is set to 32000 KB. The tables can then have approx 40,000 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.
    If cause 2 applies, an enlargement of the lock table only delays the overflow of the lock table, but it cannot generally be avoided.
    In this case you need to eliminate the update shutdown or accelerate the throughput of the update program using more update processes. Using CCMS (operation modes, see training BC120) the category of work processes can be switched at runtime, for example an interactive work process can be converted temporarily into an update process, to temporarily increase the throughput of the update.
    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.

  • Problem with copy client

    Hi!
    I need to copy (scc9) productive system to QA and have mistake what the overflow lock table. I implement note 1039834, set parameter enque/table_size 16384, run 2 enq process in central instance. But the problem has not dared.
    Please help me.

    Hello,
    You say "run 2 enq process "  .
    There has to be only "one" enqueue request for a system.
    Please check and correct your wp via tx-code rz10.
    Arzu Kosdemir

  • Enqueue Replication Server - Lock Table Size

    Note : I think I had posted it wrongly under ABAP Development, hence request moderator to kindly delete this post. Thanks
    Dear Experts,
    If Enqueue Replication server is configured, can you tell me how to check the Lock Table size value, which we set using profile parameter enque/table_size.
    If enque server is configured in the same host as CI, it can be checked using
    ST02 --> Detail Analysis Menu --> Storage --> Shared Memory Detail --> Enque Table
    As it is a Standalone Enqueue Server, I don't know where to check this value.
    Thanking you in anticipation.
    Best Regards
    L Raghunahth

    Hi
    Raghunath
    Check the following links
    http://help.sap.com/saphelp_nw2004s/helpdata/en/37/a2e3ab344411d3acb00000e83539c3/content.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/44/5efc11f3893672e10000000a114a6b/content.htm
    Regards
    Bhaskar

  • Enqueue Replication Server.

    Dear Experts,
    If Enqueue Replication server is configured, can you tell me how to check the Lock Table size value, which we set using profile parameter enque/table_size.
    If enque server is configured in the same host as CI, it can be checked using
    ST02 --> Detail Analysis Menu --> Storage --> Shared Memory Detail --> Enque Table
    As it is a Standalone Enqueue Server, I don't know where to check this value.
    Thanking you in anticipation.
    Best Regards
    L Raghunahth

    Hello,
    I haven't worked on Standalone Enque server, however its worth checking help.sap.com for this.
    I did a bit of search found that monitoring can be done via ensmon
    Check this link, Monitoring standalone Enqueue Server.
    http://help.sap.com/saphelp_nw70/helpdata/EN/bb/84ba9b96e0a94f94ade7c73df93404/frameset.htm
    Also,
    there might be few interesting things in the Trace files.
    http://help.sap.com/saphelp_nw70/helpdata/EN/cb/42f83df31a42fe8e266502cccdd9a0/frameset.htm
    Regards,
    Siddhesh
    Edited by: Siddhesh Ghag on Sep 8, 2008 11:42 AM

  • Lock specific number of records using ENQUEUE & DEQUEUE

    Hi,
    Is it possible to lock a group of records in R/3?
    My requirement is to update a set of records in VBAP table. I'm not using a BAPI here. Instead, I use a direct UPDATE.
    In this case, i know i can lock individual records by passing VBELN and POSNR. But what if i have to lock 10 records?
    Is this possible in any way?
    Thanks in advance.
    The current solution is:
    1) LOOP at ITAB
    2) LOCK each entry
    3) UPDATE VBAP for that entry
    4) UNLOCK the entry
    5) Endloop
    I thought this solution might work: (Assume 10 records are present in ITAB)
    1) LOOP at ITAB (Lock all 10 entries)
    2) LOCK that entry
    3) ENDLOOP
    4) UPDATE VBAP from ITAB (Updates all 10 entries in one databae access)
    5) LOOP at ITAB(Unlock all 10 entries)
    6) UNLOCK that entry
    7) ENDLOOP
    Any help will be appreciated.
    Tabraiz.

    Hello,
    Both of your solutions will work.
    With solution 1 there will always be only 1 enqueue object created, because you always enqueue, perform the update and dequeue.
    This means that in SM12 you will only see 1 enqueue entry on your user ID at the same time when your program runs.
    Solution 2 is also possible but there you will have different enqueue objects that will be created, because you enqueue everything, then perform the updates and then dequeue everything.
    In SM12 (lock entries) this will result in more enqueue records on your user ID the time your program runs.
    You have to pay attention that lock entries (SM12) are stored in a queue that is limited, so make sure with solution 2 that you don't overflow the enqueue queue ! ! !
    Via tcode RZ11 you can check parameter enque/table_size (Size of lock table).
    Check the parameter value but also its documentation and you will understand why you should limit the number of open lock records.
    Success.
    Wim Van den Wyngaert

  • How can SAP be configured to prevent users from consuming locks?

    How can SAP be configured to prevent users from consuming locks?
    The issue is that we want to prevent users to use upto maximum locks and so that we will not get lock table overflow issue. I know that we can assign parameter "enque/table_size" a good amount of value. But it is not for any specific user.
    Also want to alert in CCMS if any user reaches to its maximum speficified limit of locks.
    Thanks
    Gopesh

    You cannot set a limit of locks per user. There are two ways to reduce/control the number of locks:
    - change fewer records within one transaction
    - cover more records with one lock using wildcards
    Basically it is an application / development issue.
    Best regards, Michael

  • Lock table

    My archival jobs continuously fails because of Lock table overflow even after increasing parameter enque/table_size  and then bounced.
    But  in SM12  No lock entries found 
    Under SM12 EXTRAS -> STATISTICS OR DIAGONOSTIICS are inactive
    Job logs as below...
    Job started
    Step 001 started (program ZRJJARC20, variant CLL4, user ID MINIO)
    Archiving session 000078 is being created
    Lock table overflow
    Job cancelled after system exception ERROR_MESSAGE
    Regards,
    Peter

    But i want to know why job fails even after clear lock entries in SM12.
    Below find statics of locks
    Enqueue Operations     42726
    rejected     47
    Error occured     1
    Dequeue Operations     4349
    Error occured     0
    Dequeue All Operations     3735
    Cleanup Operations     0
    Backup Operations     2
    Read Operations     5
    Compress Operations     0
    Verify Operations     0
    Records written     29182
    to the backup file     4
    Maximum Number of Lock Owners     25311
    Maximum Fill level     8
    Current Fill Level     6
    Maximum Number of Lock Arguments     25311
    Maximum Fill level     25310
    Current Fill Level     6
    Maximum Number of Lock Entries     25311
    Maximum Fill level     25310
    Current Fill Level     6
    Update; Fill Level at Maximum     1
    Current Fill Level     0
    Time in Lock Table /Seconds     2.876618s
    Wait for Lock Table /Seconds     0.736393s
    Time in Lock Server /Seconds     0.000000s

Maybe you are looking for