Short dump "EXSORT_NOT_Enough_MEMORY" in production system

[Former Member]

Hi,

"EXSORT_NOT_Enough_MEMORY" dump occuring in production system,Could any one please tell me how to fix this dump.

Please refer the error message below

What happened?

*********************

The current ABAP program had to be terminated because the

ABAP processor detected an internal system error.

The current ABAP program "RSBPCOLL" had to be terminated because the ABAP

processor discovered an invalid system state.

Error analysis:

************************

The current ABAP/4 program was meant to sort a dataset (internal table

or extract). For reasons of capacity, this was not possible due to

insufficient main storage space. Therefore, the

external sort was called and resulted in the following error:

the following error:

SAP runtime system internal error.

-

---

Last error logged in SAP kernel

-

---

Component............ "EM"

Place................ "SAP-Server cambsvr15_PEC_00 on host cambsvr15 (wp 12)"

Version.............. 37

Error code........... 7

Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "

Description.......... " "

System call.......... " "

Module............... "emxx.c"

Line................. 1886

and i see that background job "SAP_COLLECTOR_FOR_JOBSTATISTIC" job being failed with below error.

Job started

Step 001 started (program RSBPCOLL, variant , user ID BACKGROUND)

ABAP/4 processor: EXSORT_NOT_ENOUGH_MEMORY

Job cancelled

Please help me to correct this error.

Best Regards,

Vinod

[Former Member]

Problem resolved after i changed the sap reorg job definitions..thanks for all help.

[Former Member]

HI Vinod,

I'm also hitting with the kind of the same problem, but not of the performance collector job.

Can I know the details step on what action you have taken?

BR,

Eida

Edited by: Eida Hanafiah on Aug 5, 2009 12:06 PM

[Former Member]

Hi Vinod

I am also facing the same problem frequently in our quality system.

Could you please tell me what you changed and what are the steps i need to follow.

Regards

Janakiram

[Former Member]

This problem is related to virtual address space of a single process!

you are running a 32 Bit system?

/3GB option is activated?

[Former Member]

Hi Peter,

Thanks for your prompt response.

Yes,we are running a 32 bit sytem(Windows 2003,EE,SP1) and How can i find that /3GB option is enabled or not? i think we need to check this at OS level if yes,

I see that / PAE is enabled in my production system

Here is my Boot loader file entry which you can find /PAE enabled on it...

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise, PAE" /fastdetect /PAE /NoExecute=OptOut

and more over we have tried to change some memory parametres after occurence of this problem like EM/Initial_Size_MB and PHYS_MEMSIZE,abap/heap_area_nondia as referred in SAP Note:193529 and restarted the server and instance to freeup the system resourses but no luck on it.

We are running the sytem with 6GB of RAM and Currently allocated Virtual memory is :15360 MB,

Here are my Some of my system memory parameters for your reference.Please tell me the ways to resolve this issue.

abap/heap_area_nondia 2000000000

abap/heap_area_total 5000000000

ztta/roll_area 2000000

ztta/roll_extension 2000000000

em/initial_size_MB 6143

PHYS_MEMSIZE 6143

I would be glad to be of any assistance.Please let me know the possible ways to solve this issue.

Thanks & Regards,

Vinod

[Former Member]

well running on 32 Bit Windows is not a good idea, see notes [996600|http://service.sap.com/sap/support/notes/996600],[129813|http://service.sap.com/sap/support/notes/129813].

Read this [document|http://service.sap.com/~sapidb/011000358700006425762006E] to understand the virtual address space problem on 32 Bit Windows.

Edited by: Peter Simon on Sep 18, 2008 9:11 AM

[Former Member]

Hi,

Is there any workaround for this than switching to 64bit like changing some memory parameters, by providing or adding additional resourses??

Many Thanks,

Vinod

[former_member204746]

no,

Read Peter Simon's answer. it tells it all,

so, it's a max of 2.7GB usable memory (with /3gb /pae) or 64-bit.

but you may have another problem that is causing the usage of so much memory.

Please review SAP note 997535 - DB02: Problems with History Data.

[Former Member]

Hi

Vinod

In which system u got this dump, means(dev, qas, prd).

how is the statistics of the ST02, the % of the buffers utilization.

Have u checked the workprocess in SM50.

Is this the first time you got or frequently occuring.

Regards

Bhaskar

[Former Member]

Hi Bhaskar,

yes, I have checked the Wp status and it looks fine.I'm getting this error on My PRD system on regular basis since 1 week.

We have tried to restart the server but no luck.

Here are the ST02 values and background job SAP_COLLECTOR_FOR_JOBSTATISTIC also being failed with this error.

Buffer Hitratio Allocated Free space Dir. size Free directory Swaps

[%] [kB] [kB] [%] Entries Entries [%]

Program 99.11 400,000 1,481 0.38 100,000 90,774 90.77 36,307

CUA 99.31 3,000 264 10.53 1,500 1,263 84.20 14,934

Screen 98.45 4,297 27 0.82 10,000 9,653 96.53 645

Calendar 99.76 488 359 75.10 200 48 24.00 0

OTR 100.00 4,096 3,439 100.00 2,000 2,000 100.00 0

SAP memory Current use Max. use In memory On disk

[%] [kB] [kB] [kB] [kB]

Roll area 1.45 3,808 7,680 262,144 0

Paging area 3.40 8,904 13,056 0 262,144

Extended Memory 9.05 389,120 812,032 4,299,776

Swaps

0

21,249

0

16,399

36,307

14,934

645

0

0

272

0

210,742

0

Please let me know if you require further information.

Thanks & Regards,

Vinod