Skip to Content

enque/table_size in ASCS/CI

Hi,

In our R/3 Landscape , in all 4 Application servers enque/table_size is set to value 20000 KB

App1 - 20000 , App2 - 20000 ,....

(Value defined in /sapmnt/<SID>/profiles ---> Application servers instance profile)

But in ASCS/CI server , this value is defined as 4096 KB (enque/table_size = 4096)

(Value defined in /sapmnt/<SID>/profiles ---> ASCS instance profile)

When checked in the process list; The enque process (EN) and message server process (MS) running on the CI server using ASCS instance profile.

I want to know which parameter values used by the SM12. (Lock Table)

Is it (enque/table_size = 4096) in CI

OR

Is it (enque/table_size = 20000) in Application servers

I think since it using ASCS profile , it uses (enque/table_size = 4096)

Is this right?

Then is it necessary to have this enque/table_size value 20000 in Application servers. Will there any affect to SM12 lock table?

OR will the lock table use these table_size value , server wise.

Like .... For Appser1 20000, For CIserver 4096 ...

Regards,

Zerandib

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    avatar image
    Former Member
    Nov 14, 2010 at 06:35 AM

    Hi,

    You need to set this parameter where enqueue server is running may be if you have standalone enque server

    Setting this parameter on app server will not effect at all.

    Regards,

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 15, 2010 at 12:58 PM

    enque/table_size takes value from the profile where enque process runs. In your case, ASCS prof (in CI server).

    Thanks,

    Subrata

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 15, 2010 at 03:04 PM

    Hello,

    AS ABAP instance of an SAP system contains the enqueue server and the message server (ASCS = ABAP SAP Central Services). And there can only be one such instance in the SAP system, and it can be made into a high availability SPOF (single point of failure) instance.

    In your scenario, enque/table_size parameter in CI will be taken into consideration. And not enque/table_size parameter in app server, as enqueue process resides in CI and not in app server.

    << Moderator message - Point begging removed >>

    Thanks and regards,

    Meghan

    Edited by: Rob Burbank on Nov 15, 2010 3:08 PM

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 15, 2010 at 11:24 PM

    enque/table_size parameter value is applicable to the server where enqueue server defined.(traditionally in CI for non clusters or in ASCS if you have one)

    All the app server workprocess reads the enque table(shared memory) through RFC.

    Please see the point # 3 in the link given below.

    Link: [https://service.sap.com/sap/support/notes/552289]

    Add comment
    10|10000 characters needed characters exceeded