No free memory available in class PERM.

[Former Member]

To all,

I have a SAP system that has been running well for couple years. This server houses both CI and DB. 64 bit, SQL2000, 32GRAM. ABAP only, no J2ee

Recently, we encounter issues. when SM21, I see

No free memory available in class PERM . Memory block ID "ROLEPT", 500001880 bytes.

Start Workproc36, Pid 6708

Start Workproc 5, Pid 6964

Start Workproc31, Pid 216

No free memory available in class PERM . Memory block ID "SHORT ", 3200088 bytes.

No free memory available in class PERM . Memory block ID "SHORT ", 3200088 bytes.

No free memory available in class PERM . Memory block ID "ROLEPT", 500001880 bytes.

Run-time error "SYSTEM_NO_ROLL" occurred

> Short dump "110407 112140 usapodev APD00 " generate

Shared Memory for PXA buffer not available

Initialization RUNT Failed, Return Code -000001

Stop Workproc39, PID 6276

Run-time error "PXA_NO_SHARED_MEMORY" occurred

> Include ??? line 0000.

I have done some researches but couldn't seems to able to resolve our problem.

Below is our RZ10 instance parms. This params have been adjusted and set at time of implemenations by consultant. Nothing have change. We don't have increase in work load or user access system, except our 3 ABAPers.

SAPSYSTEMNAME APD

SAPGLOBALHOST usapodev

SAPSYSTEM 00

INSTANCE_NAME DVEBMGS00

DIR_CT_RUN $(DIR_EXE_ROOT)\$(OS_UNICODE)\NT

DIR_EXECUTABLE $(DIR_INSTANCE)\exe

DIR_ROLL C:\usr\sap\APD\DVEBMGS00\data

DIR_PAGING C:\usr\sap\APD\DVEBMGS00\data

DIR_DATA C:\usr\sap\APD\DVEBMGS00\data

DIR_REORG C:\usr\sap\APD\DVEBMGS00\data

DIR_TRANS
usapodev\sapmnt\trans

DIR_TEMP .

DIR_SORTTMP C:\usr\sap\APD\DVEBMGS00\data

PHYS_MEMSIZE 32000

abap/buffersize 900000

abap/heap_area_dia 16001269760

abap/heap_area_nondia 16001269760

abap/heap_area_total 20494417920

abap/heaplimit 81788928

abap/swap_reserve 121634816

abap/use_paging 0

rdisp/wp_no_dia 25

rdisp/wp_no_btc 8

rdisp/wp_no_enq 1

rdisp/wp_no_vb 6

rdisp/wp_no_vb2 2

rdisp/wp_no_spo 1

rdisp/appc_ca_blk_no 1000

rdisp/wp_ca_blk_no 1000

rdisp/tm_max_no 2000

rdisp/max_comm_entries 2000

rdisp/ROLL_SHM 65792

rdisp/PG_SHM 65792

rdisp/max_arq 2000

rdisp/max_wprun_time 18000

rdisp/ROLL_MAXFS 164864

rdisp/PG_MAXFS 124800

icm/server_port_0 PROT=HTTP,PORT=80$$

ms/server_port_0 PROT=HTTP,PORT=81$$

icm/host_name_full usapodev.us.kingston.corp

install/codepage/appl_server 4103

rtbb/buffer_length 200000

rsdb/cua/buffersize 20000

rsdb/ntab/entrycount 85947

rsdb/ntab/ftabsize 119311

rsdb/ntab/irbdsize 25794

rsdb/ntab/sntabsize 11930

rsdb/obj/buffersize 120000

rsdb/obj/max_objects 50000

zcsa/presentation_buffer_area 15664128

zcsa/system_language E

zcsa/installed_languages 1MED

zcsa/table_buffer_area 410224640

gw/max_conn 2000

login/no_automatic_user_sapstar 0

sap/bufdir_entries 40000

em/blocksize_KB 14192

em/stat_log_size_MB 20

em/stat_log_timeout 0

em/initial_size_MB 30100

em/address_space_MB 30100

ztta/roll_first 1024

ztta/roll_area 500001792

ztta/roll_extension 12000952320

Would you please help to tell me what I need to do to fix the problem. Thank you so much for your time and assistant. Elizabeth

[former_member189546 · Accepted solution]

Hello,

It might be bug described in

Note:1248835 No free memory available in class PERM "ROLEP"

regards,

John Feely

[markus_doehr2]

> I have a SAP system that has been running well for couple years. This server houses both CI and DB. 64 bit, SQL2000, 32GRAM. ABAP only, no J2ee

Just for curiosity: So you're runinng a 32bit database (SQL Server 2000) on a 64bit operating system?

Markus

[Former Member]

Hi Markus,

Thank you for your assistant. Sorry, my fault. Ours is SQL2005.

Elizabeth.

[Former Member]

Hi,

Reduce the no. of dialogue process and also remove abap/buffersize 900000 and other related parameter files.

If you are using Windows, then please read the Zero Administration on Windows note, before you assign all those parameter.

Regards

Prash

[Former Member]

Hi Prash,

This is exactly what I was thinking.

We are a small SAP shop, so the most logical is I like to reduce the #of dialog process.

Would you assist in what other params should I change and what values should I put.

Sorry, as I don't have much experience with these number sas I am not a consultant who

might see these on the day-to-day basis.

Thanks.

[Former Member]

Hello -

In addition to my previous post the dynamic method as per 88416 will help against the error's encountered currently. If the error's persist an analysis should be undertaken by your basis team. Here is some additional advise in this context :

Use transaction ST02 -> Detailed Analysis Menu -> SAP Memory-> Ext. Memory Blocks & Mode List, allow you to monitor memory.

SM04 -> Goto -> Memory gives you a snapshot of memory being used but no history.

Note #649327 (Analysis of memory consumption) also gives related information.

By calling Transaction SM04 and choosing 'Goto' -> 'Block list',you can display an overview of the current roll and paging memory levels resulting from active users and their transactions. Try to decide from this whether another program requires a lot of memory space (perhaps too much).

Regards

SAP

[Former Member]

Hello

Operating SAP on MS Windows platforms is a dynamic process when ZAMM (SAP note 88416) is used. SAP advise to use this dynamic method.

The basis for zero administration memory management on Windows is the dynamically self-extending extended memory. An "infinitely" large memory resource is made available with this method. The extended memory is initially set to the size of the profile parameter PHYS_MEMSIZE ([PM]). If more memory is required by the user, the extended memory extends itself in steps of "[PM] / 2" up to the set limit of the profile parameter em/max_size_MB or until the address space in the Windows page file is used up. By setting the standard value for em/max_size_MB to 20000 MB (100000 MB for 64bit), it is the size of the Windows page file that represents the actual limit for the extension of the extended memory. The profile parameter PHYS_MEMSIZE determines how much of the entire main memory is to be used by the SAP system.

Set-up the memory management as per SAP note 88416.

Regards

SAP

[Former Member]

Hi Elizabeth,

This is due insufficient memory space, as mentioned MS SOL server database, at the OS level consumes more memory, please monitor the MS SOL database at the OS level and at SAP level check the which PID and ABAP pro gramme consumes large space, and monitor the work load analysis to find and inconsistency in reading the load .

once all the monitoring is completed, conclude based on the Physical memory size, as mentioned by you physical memory is low , increase PHY_MEM- to 5000 MB if not sufficient still increase the same to another 1GB.

Regards

Rajiv

[xymanuel]

Hi Elizabeth,

i dunno whats exact your problem,

but i see one parameter which is, in my opinion, wrong.

Its PHYS_MEMSIZE 32000, which means your ABAP CI instance will in maximum consume 32GB.

Together with the maximum value of em/initial_size_MB = 30100, which is 30GB Maximum of extended Mem.

And in which memory segment lays your SQL Server and your OS?

You have to count RAM Usage OS + RAM Usage SQL Server (min/max memory) + em/initial_size_MB (+ a little overhead).

Together this should be smaler than 32GB!

In your configuration the ABAP instance try to get more physical memory which is not available because your sql server uses a lot.

Maybe this is the problem.

I would say, set SQL Server min/max memory to 18GB to get good datacache hitrates.

Set PHYS_MEMSIZE to 10GB (try deleting em/initial_size_MB because ZAMM will set the correct value) search notes for ZAMM.

The 4GB rest is for overhead of the ABAP instance and the OS.

Isnt your server terrible swapping (see OS06, last 24h, memory, pages out/sec) with your settings??

ztta/roll_first should be 1 and not 1024. The workprocess should use extended memory asap.

Kind regards

Manuel