cancel
Showing results for 
Search instead for 
Did you mean: 

oss notes

Former Member
0 Kudos

Hi,

Can anybody say what oss notes 147568 contains

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

OSS note 147568 is used for Some memory management, like when u are getting error like

The current size of the PXA was set at 145096 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.

The OSS notes are available in the following link,

http://service.sap.com/notes

This will ask for a User name & password. Please contact your team leader/ PM for the details & get a user name & password.

After login, there is search option where we can enter the description of the issue. The system will search all relevant notes & will display. From this we need to choose the appropriate note to apply. Also we need to check whether this note is valid for the SAP version we are using.

If you know the SAP note number then directly enter the note number & the corresponding note will be displayed.

For more details discuss the same with the Basis team, since they are responsible for applying the notes.

Thanks,

Raja

Edited by: Raja Singh Chhabeda on Jul 29, 2008 12:41 AM

Former Member
0 Kudos

hi,

Your answer is helpful but i want the exact details inside that oss notes.

Former Member
0 Kudos

Hi,

The contents:

Summary

Symptom

Runtime error PXA_NO_FREE_SPACE occurs

(displayed - for example - in Transaction ST22).

Additional key words

PXA

Cause and prerequisites

Almost always one of the two following cases is the cause for runtime error PXA_NO_FREE_SPACE:

1. You have selected the program buffer too small (parameter abap/buffersize). Notice here that a separate program buffer exists for every application server.Consequently, another setting of the parameter abap/buffersize can also be selected for every application server.

2. The program buffer cannot be created in the size entered in the parameter abap/buffersize because of missing Shared Memory. It is created in the emergency mode with a smaller size. The size of the program buffer is either 4MB per work process or 32 MB in the shared memory, depending on the release level or patch level of the kernel. The size of the program buffer is also mentioned in the runtime error text under "Description of the error scenario")

Apart from PXA_NO_FREE_SPACE, runtime error PXA_NO_SHARED_MEMORY is also often found. When booting, this error also appears in the status bar as a message or as a short dump during the login.

In exceptional cases, runtime error PXA_NO_FREE_SPACE has another cause. The following list contains all known cases:

3. The following situation only occurs up to and including R/3 Release 4.0B:

Runtime error PXA_NO_FREE_SPACE occurs because many objects in the program buffer are locked by invalid LOCK counter values and thus cannot be displaced. You can check this situation in the ABAP debugger as follows:

Change to the display of the system area (Goto -> System -> System Areas) and enter 'PXA' for area name. The system will display a list of all objects in the program buffer. Objects, which cannot be displaced, include a value not equal to zero in column 'LOCKS'. Valid values in this column are 1,100,F0F,1000, 10000 and combinations or multiples of these values, for example: 20001. Because the LOCK counter in the shared memory is modified without semaphore protection for performance reasons, the system may generate invalid values in exceptional situations, as a result the objects remain locked until you shut down the application server. This error situation increasingly occurs on multiprocessor machines having many processors.

4. The following situation only occurs up to and including R/3 Release 4.0B:

Short dump PXA_NO_FREE_SPACE occurs several times, even though a high percentage of the program buffer is free (according to Transaction ST02). In addition, the portion of the gaps ("Gaps") is almost as large as the portion of the free buffer ("Free").

5. The following situation only occurs up to and including R/3 Release 4.0B:

Transaction ST02 displays swaps for the program buffer (PXA), even though there is still sufficient free space in the buffer. You can also note that as of a size of 300 to 400 MB, an extension of the program buffer brings no positive change to the swap situation. Rather more and more storage remains unused at the upper end of the program buffer.

6. The following situation only occurs prior to R/3 Release 4.6:

Many programs are generated by a batch job. Objects remain locked in the program buffer in in spite of COMMIT. In the ABAP Debugger, you can check whether a work process locks many objects in the program buffer as follows: Change to the display of the system area (Goto -> System -> System Areas) and enter 'PXALOCKS' for area name. The system will display a list of all objects in the program buffer. One column is provided per work process. An 'x' indicates that the object is locked by the respective work process. If a column contains many 'x', the work process locks many objects.

7. The following situation only occurs under AIX:

Short dump PXA_HASH_LOOP or PXA_NO_FREE_SPACE occurs directly after restarting the instance.

Prase

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi prasanth,

Your solution to my problem is more accurate and you have asked me in the 7th step to go to the menu path System- System Area and enter 'pxalocks'. My sap release is 4.7 and i don't know where i can find the above mentioned menu path and i'm not an abaper.

How to give the commit step in the program and where to give it? Pls explain me in detail what r the steps i should take to increase the pxa storage space. In RZ10 tcode i have seen the abap/buffer size and it is already given as 900000. How to extend it further more.

Pls answer in detail

former_member181995
Active Contributor
0 Kudos

Cheenu,

Summary

Symptom

Runtime error PXA_NO_FREE_SPACE occurs
(displayed - for example - in Transaction ST22).

Additional key words

PXA

Cause and prerequisites

Almost always one of the two following cases is the cause for runtime error PXA_NO_FREE_SPACE:


1. You have selected the program buffer too small (parameter abap/buffersize). Notice here that a separate program buffer exists for every application server.Consequently, another setting of the parameter abap/buffersize can also be selected for every application server.

2. The program buffer cannot be created in the size entered in the parameter abap/buffersize because of missing Shared Memory. It is created in the emergency mode with a smaller size. The size of the program buffer is either 4MB per work process or 32 MB in the shared memory, depending on the release level or patch level of the kernel. The size of the program buffer is also mentioned in the runtime error text under "Description of the error scenario")
Apart from PXA_NO_FREE_SPACE, runtime error PXA_NO_SHARED_MEMORY is also often found. When booting, this error also appears in the status bar as a message or as a short dump during the login.

In exceptional cases, runtime error PXA_NO_FREE_SPACE has another cause. The following list contains all known cases:
3. The following situation only occurs up to and including R/3 Release 4.0B:
Runtime error PXA_NO_FREE_SPACE occurs because many objects in the program buffer are locked by invalid LOCK counter values and thus cannot be displaced. You can check this situation in the ABAP debugger as follows:
Change to the display of the system area (Goto -> System -> System Areas) and enter 'PXA' for area name. The system will display a list of all objects in the program buffer. Objects, which cannot be displaced, include a value not equal to zero in column 'LOCKS'. Valid values in this column are 1,100,F0F,1000, 10000 and combinations or multiples of these values, for example: 20001. Because the LOCK counter in the shared memory is modified without semaphore protection for performance reasons, the system may generate invalid values in exceptional situations, as a result the objects remain locked until you shut down the application server. This error situation increasingly occurs on multiprocessor machines having many processors.
4. The following situation only occurs up to and including R/3 Release 4.0B:
Short dump PXA_NO_FREE_SPACE occurs several times, even though a high percentage of the program buffer is free (according to Transaction ST02). In addition, the portion of the gaps ("Gaps") is almost as large as the portion of the free buffer ("Free").

Refer to Note 175320
5. The following situation only occurs up to and including R/3 Release 4.0B:
Transaction ST02 displays swaps for the program buffer (PXA), even though there is still sufficient free space in the buffer. You can also note that as of a size of 300 to 400 MB, an extension of the program buffer brings no positive change to the swap situation.  Rather more and more storage remains unused at the upper end of the program buffer.

Refer to Note 121808

6. The following situation only occurs prior to R/3 Release 4.6:
Many programs are generated by a batch job. Objects remain locked in the program buffer in in spite of COMMIT. In the ABAP Debugger, you can check whether a work process locks many objects in the program buffer as follows: Change to the display of the system area (Goto -> System -> System Areas) and enter 'PXALOCKS' for area name. The system will display a list of all objects in the program buffer. One column is provided per work process. An 'x' indicates that the object is locked by the respective work process. If a column contains many 'x', the work process locks many objects.
7. The following situation only occurs under AIX:
Short dump PXA_HASH_LOOP or PXA_NO_FREE_SPACE occurs directly after restarting the instance.

Refer to Note 160875
Solution

1. In the text of the runtime error, check to see on which application server the error has occurred. On this server, check the setting of the parameter abap/buffersize (Transaction RZ10 or report RSPARAM). For this, read Notes:
      103747  (R/3 Release 40A,40B,45A
       97497   (R/3 Release 30C - 31I
2. Allow your system administrator to check whether there is a sufficient amount of system resources. (Utility program "ipclimits")
3. The kernel patch with the text
    'PXA: avoid illegal lock counter values'
for Release 3.1I and 4.0B has the effect that the LOCK counter is no longer modified in the shared memory. As a result, invalid values cannot occur.
4. Refer to Note 175320
5. Refer to Note 121808
6. The 4.6D kernel patch 185 with the text
    'PXA: release program locks during COMMIT'
deletes locks on objects in the program buffer at the time of COMMIT. Thus, the affected objects can be displaced from the program buffer (provided that they are not locked by another work process).
7. Refer to Note 160875

former_member184555
Active Contributor
0 Kudos

Hi

Deleting the message since the details are already posted in the above reply.

Thanks,

Ravi

Edited by: Ravi Sankar on Jul 29, 2008 7:58 PM