Roll area too small

[Former Member]

Hi Gurus,

In my environment , a background job got cancelled . The log of that job shows that the

Roll area too small

.

What is the meaning of -

---

Roll area too small and what might be the reason behind this error message.

Thanks in Advance,

Sachin.

[Esha1]

Hi

Roll area is basically used for storing user context. In St02 you can find out the trend of consumption of this area in past.

If in the log of this cancelled job its showing that the roll area is too small.

First have a search in st22 dumps these kind of dumps are occuring again and again in the system because of roll area problem or is there any other job which got cancelled because of same reason.

After that have a look of memory consumption of that job. Check various memory consumption parameters that will shown in dump like roll area, extended memory and heap memory to verify that problem lies with the roll area or why the jobs require such high memory.

After that you can verify the memory availiablity to increase the roll area.

ztta/roll_area: Maximum roll area per user context: set it to this value for 64-bit systems: 6500000

Hope this helps!!

Edited by: Esha Rajpal on Sep 5, 2008 8:54 AM

[Former Member]

Hi Esha,

Thanks for the info on the roll area.

In my case only this job is getting the Roll area too small eror.

Could you please tell me how to find the memory consumption statistics of a particular job.

Thnaks in Advance,

sachin.

[Former Member]

adding to my previous reply, there are no dumps at the time when the job gets canceled.

[Former Member]

Attaching the job log of the canceled job.

09/17/2008 04:00:06 Job started

09/17/2008 04:00:06 Step 001 started (program ZVORDCLOSE_ZBLK, variant CHBLKCLSE, user ID BACKGROUND)

09/17/2008 04:00:39 Background Job CLOSE_ZBLK_ORDERS Created and Processed BDC CLS_ZBLK_ORD. Go to transaction SM35 to look at the details

09/17/2008 04:00:40 Step 002 started (program ZVORDCLOSE_ZBLK, variant KZOCLOSEORDERS, user ID BACKGROUND)

09/17/2008 04:00:41 Step 003 started (program ZVORDCLOSE_ZBLK, variant LBGCLOSEORDERS, user ID BACKGROUND)

09/17/2008 04:00:44 Background Job CLOSE_ZBLK_ORDERS Created and Processed BDC CLS_ZBLK_ORD. Go to transaction SM35 to look at the details

09/17/2008 04:00:44 Step 004 started (program ZVORDCLOSE_ZBLK, variant PRTCLOSEORDERS, user ID BACKGROUND)

09/17/2008 04:00:49 Background Job CLOSE_ZBLK_ORDERS Created and Processed BDC CLS_ZBLK_ORD. Go to transaction SM35 to look at the details

09/17/2008 04:00:49 Step 005 started (program ZVORDCLOSE_ZBLK, variant UD_CLOSEORDERS, user ID BACKGROUND)

09/17/2008 04:03:03 Background Job CLOSE_ZBLK_ORDERS Created and Processed BDC CLS_ZBLK_ORD. Go to transaction SM35 to look at the details

09/17/2008 04:03:18 Roll area too small

09/17/2008 04:03:18 Job cancelled

The following is the entry in the system log (SM21).

I feel this entry in SM21 is related to the canceled job.

04:00:04 ap05_PRD_01 BTC 058 010 BACKGROUND ST 0 No free memory available in class SHORT. Memory block ID "MELSAV", 736 bytes.

04:00:04 ap05_PRD_01 BTC 058 010 BACKGROUND D0 1 Transaction Canceled 00 024 ( ).

Thanks,

Sachin.

[Former Member]

Hi Sachin,

We encountered exactly the same problem 'No free memory available in class SHORT. Memory block ID "MELSAV", 736 bytes.'. Did you manage to solve this problem yet?

I've checked some memory parameters and saw that the profile parameter ztta/roll_area is set to 3000000. This is quite low for our system with 100GB of memory. Maybe increasing this parameter (let's say to 6500000 or even higher according to Note 789477 (we use an AIX 64-bit system)) may solve this problem. We are now discussing this with the functional people to have the parameter change tested coming weeks.

Cheers,

Danny

[Esha1]

Hi

You can check in ST03n which user is running that job and check the memory consumption of that user like extended memory in memory statistics option. Also check that you have set all the memory parameters according to SAP Notes.

Hope this helps.

Kind Regards

Esha

[Former Member]

Hi,

Can you send the detail log here.

Anil

[Former Member]

Hi Sachin,

You can check the role area usage ib t-code st02

Check for current usage percentage and max use and in memory.If max use= inmemory then there is less roll area.You can increase the value with the parameter ztta/roll_area

Regards

Ashok

[Former Member]

Hi,

Adding more to Ashok, Here is a link with more details about the SAP memory ( roll area is one among them ).

http://help.sap.com/saphelp_nw04/helpdata/en/28/d1d3f6bcb411d188b30000e83539c3/frameset.htm

If you have TADM12_2 ( SAP Web AS Implementation and Operation II ) Course book there is a dedicated chapter " SAP Memory Management ". You can find relevant stuff which is depicted pictorially.

Rgds

Radhakrishna D S

Edited by: Radhakrishna D S on Sep 5, 2008 7:39 AM