We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE:[sap-basis] Large No. Of Dumps SYSTEM_NO_TASK_STORAGE

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Reply from snowy0 on Sep 20 at 10:17 PM
schawnekar,

you are wrong, it is possible to run a 32-bit application on 64-bit OS... it all depends on which Os this is running. For example, this is widely accepted on Windows platform.

This being said, I don't see why anyone would run a 32-bit application if a 64-bit version is available...

---------------Original Message---------------
From: satish
Sent: Thursday, September 11, 2014 12:08 AM
Subject: Large No. Of Dumps SYSTEM_NO_TASK_STORAGE

Dear Gurus

We are on ECC 6.0 32 bit, Kernel 7.20/600, Oracle 10.2 Windows 2003
Enterprise edition 64 bit OS.

We are getting large number of dumps of SYSTEM_NO_TASK_STORAGE in ST22 in
our production server after upgrading kernel to 7.20. We have tried to
overcome the problem but could not succeed, hereunder the rz10 parameters
and dump for reference. Kindly suggest the parameter value.

Satish

Dump

-------
What happened?

Each transaction requires some main memory space to process

Application data. If the operating system cannot provide any more

Space, the transaction is terminated.

What can you do?

Try to find out (e.G. By targeted data selection) whether the

Transaction will run with less main memory.

If there is a temporary bottleneck, execute the transaction again.

-

If the error persists, ask your system administrator to check the

Following profile parameters:

O ztta/roll_area (1.000.000 - 15.000.000)

Classic roll area per user and internal mode

Usual amount of roll area per user and internal mode

O ztta/roll_extension (10.000.000 - 500.000.000)

Amount of memory per user in extended memory (EM)

O abap/heap_area_total (100.000.000 - 1.500.000.000)

Amount of memory (malloc) for all users of an application

Server. If several background processes are running on

One server, temporary bottlenecks may occur.

Of course, the amount of memory (in bytes) must also be

Available on the machine (main memory or file system swap).

Caution:

The operating system must be set up so that there is also

Enough memory for each process. Usually, the maximum address

Space is too small.

Ask your hardware manufacturer or your competence center

About this.

In this case, consult your hardware vendor

Abap/heap_area_dia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

For each dialog process.

Parameters for background processes:

Abap/heap_area_nondia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

For each background process.

Other memory-relevant parameters are:

em/initial_size_MB: (35-1200)

Extended memory area from which all users of an

Application server can satisfy their memory requirement.

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

You can use the ABAP dump analysis transaction ST22 to view and manage

Termination messages, in particular for long term reference.

Ror analysis

A new storage area of 809336 bytes was requested

(storage calss TASK).

All the available space has been used up.

RZ10 Parameters

 
Reply to this email to post your response.
 
__.____._
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
  
Copyright © 2014 Ziff Davis, LLC. and message author.
Ziff Davis, LLC. 28 E 28th Street New York, NY 10016
snowy0  
 
Mark as helpful
View this online
Ask a new question
 
In the Spotlight
Become a blogger at Toolbox.com and share your expertise with the community. Start today.

_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language