memory issue

[Former Member]

Hi,

Tuning:

em/initial_size_mb =32768

em/max_size_mb=4092

PHYS_MEMSIZE=64

RAM size is 210 GB.the RAM utilization is never reached more than 60% .how to utilize or tune my

DB parameters so that it will use max RAM.

Also we are getting frequently lock table overflow .

enque/table_size =281600 in app server1 and 4096 in app server2.

Please suggest.

Regards,

ARNS.

[markus_doehr2]

> em/initial_size_mb =32768

> em/max_size_mb=4092

> PHYS_MEMSIZE=64

>

> RAM size is 210 GB.the RAM utilization is never reached more than 60% .how to utilize or tune my

> DB parameters so that it will use max RAM.

What OS are you using?

What database are you using? The above parameters are no database parameters but SAP parameters...

Markus

[Former Member]

hi,

Details:

SAP platform ECC 6.0

OS HP-UX 11.23 ia64

database 10 g oracle

database size is 6TB

Our locktable is 300MB size still table overflow occurig.

Mainly this is happening when runnong MIGO transactions amd locks or on table EQUI,RISENQ.

Regards,

ARNS

[Former Member]

hi,

so has this problem any solution? we have the same issue with MIGO and i dont know, i can increase the max size in parameter ENQUE/TABLE_SIZE...

thx

pj

[Former Member]

Hello,

Are you facing any performance problems?

Are you having any additional instance running on the same box?

suggest you reading the following for memory;

http://help.sap.com/saphelp_erp2004/helpdata/en/02/96253c538111d1891b0000e8322f96/frameset.htm

For the lock overflow:

Is the error specific to one app server.If yes, consider changing the parameter enqueu_table size.

Thanks,

Prasanna

[Former Member]

Hi,

We dont have multiple instance on same server.We have 3 app servers.

We are getting lock entries in MIGO t.code for ex

though we have increased lock entry table size to max.

[vincentlim826]

- check your SM12 -> Extra -> Diagnosis / Statistics

- enque/table_size should be set the enqueue server. If you're running standalone enqueue, set it at (A)SCS profile.

- if enque/table_size is easily occupied, then it can be poor application design issue that requires massive locks.

Regards,

Vincent

[Former Member]

Mainly locks or occuring in standard Tcodes like MIGO.

[Former Member]

We have 2 application servers.Each server have different enque/table_size value.

This is to be set on only central instance ?or both CI and DI.

[Former Member]

Raghu,

It should be set on the lock server or the CI.

Sorry about the above comment.

http://help.sap.com/saphelp_nw04/helpdata/EN/37/a2e3ab344411d3acb00000e83539c3/content.htm

Check this.It is clear from this link.

BTW, is the parameter being present in the ..../sys/profile/SID_<app_server>.pfl..?

thanks,Prasanna

[Former Member]

many lock entries found RISENQ and EQUI tables only.