dear genius ,
i paste my dump ....please give solution....
Thnaks
Lee
Runtime Errors PXA_NO_FREE_SPACE
Date and Time 29.08.2007 18:12:24
-
-
Short text |
No PXA storage space available at the moment. |
-
-
What happened? |
The current ABAP/4 program had to be terminated because there |
was no space available to load it. |
|
Each ABAP/4 program to be executed is stored in a central |
storage area that is divided between all users. |
This area was too small to hold all currently active programs for all |
users. |
Resource bottleneck |
|
The current program "SAPLMECOM1" had to be terminated because |
a capacity limit has been reached. |
-
-
What can you do? |
Since this could have resulted in a temporary bottleneck, you should |
try to restart the program. |
|
Ask your system administrator to increase the size of the area (PXA) |
used to store the ABAP/4 programs. |
|
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. |
|
-
-
Error analysis |
Unable to load a program of 3119104 bytes. |
The PXA ('program execution area') was too small to hold all |
currently active programs for all users. |
At present, the size of the PXA is set at 144792 Kbytes. |
The largest contiguous and unlocked memory chunk has 2720768 bytes. |
-
-
How to correct the error |
The current size of the PXA was set at 144792 kilobytes. |
You can increase or decrease the PXA in the SAP profile. When |
doing this, please refer to the relevent instructions in the |
installation manual. |
|
You can use the utility program 'ipclimits' to display the |
available system resources. |
|
If the error occures in a non-modified SAP program, you may be able to |
find an interim solution in an SAP Note. |
If you have access to SAP Notes, carry out a search with the following |
keywords: |
|
"PXA_NO_FREE_SPACE" " " |
"SAPLMECOM1" or "LMECOM1U01" |
"MEPO_DOC_INITIALIZE" |
|
If you cannot solve the problem yourself and want to send an error |
notification to SAP, include the following information: |
|
1. The description of the current problem (short dump) |
|
To save the description, choose "System->List->Save->Local File |
(Unconverted)". |
|
2. Corresponding system log |
|
Display the system log by calling transaction SM21. |
Restrict the time interval to 10 minutes before and five minutes |
after the short dump. Then choose "System->List->Save->Local File |
(Unconverted)". |
|
3. If the problem occurs in a problem of your own or a modified SAP |
program: The source code of the program |
In the editor, choose "Utilities->More |
Utilities->Upload/Download->Download". |
|
4. Details about the conditions under which the error occurred or which |
actions and input led to the error. |
|
-
-
System environment |
SAP-Release 700 |
|
Application server... "sapdev" |
Network address...... "192.168.1.226" |
Operating system..... "Windows NT" |
Release.............. "5.2" |
Hardware type........ "2x Intel 801586" |
Character length.... 16 Bits |
Pointer length....... 32 Bits |
Work process number.. 0 |
Shortdump setting.... "full" |
|
Database server... "SAPDEV" |
Database type..... "MSSQL" |
Database name..... "EMD" |
Database user ID.. "emd" |
|
Char.set.... "C" |
|
SAP kernel....... 700 |
created (date)... "Aug 29 2006 00:18:21" |
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10" |
Database version. "SQL_Server_8.00 " |
|
Patch level. 75 |
| Patch text.. " "
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.