cancel
Showing results for 
Search instead for 
Did you mean: 

PXA_NO_SHARED_MEMORY

Former Member
0 Kudos

Dear Guys

we are facing ABAP dump almost 1000+ can you please check and suggets solution

Short text

    600000 kilo bytes of shared memory for PXA not available.

What happened?

    When starting the R/3 System, 600000 Kbytes of storage space

    was required for the ABAP/4 program buffer (PXA), but this

    was not available.

    The system was started as an emergency system and is not fully

    operational.

    It is intended only for display and to eliminate errors.

    Under no circumstances should it be used for production

    purposes.

Error analysis

    The error probably occurred when installing the

    R/3 system.

    The return code of the SAP shared memory control was 1.

    The error reported by the operating system is:

    Error number..... 0

    Error text....... "No error"

How to correct the error

    Report the error to the group responsible for installing your

    R/3 System.

    The current size of the PXA was set at 554312 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_SHARED_MEMORY" " "

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

The parameters are set according to my RAM 20 GB according to iset below parameters

csi/enable                                  0

rdisp/elem_per_queue                        4000

icm/server_port_1                           PROT=SMTP,PORT= 2502

rsdb/obj/max_objects                        20000

rsdb/obj/buffersize                         50000

abap/shared_objects_size_MB                 100

sap/bufdir_entries                          10000

zcsa/db_max_buftab                          10000

abap/buffersize                             600000

zcsa/table_buffer_area                      100000000

rtbb/buffer_length                          60000

rsdb/cua/buffersize                         10000

zcsa/presentation_buffer_area               20000000

rdisp/appc_ca_blk_no                        1000

rdisp/wp_ca_blk_no                          1000

rsdb/ntab/entrycount                        30000

rsdb/ntab/ftabsize                          60002

rsdb/ntab/irbdsize                          15002

rsdb/ntab/sntabsize                         3000

Please suggest the solution.

Regards,

Somesh.K

Accepted Solutions (0)

Answers (4)

Answers (4)

madasamy_arunachalam
Active Participant
0 Kudos

Hi Somesh

In this situation, it is also worth to check shared memory segments assigned to the memory pool.

Go to your profile directory with sidadm, run below command.

1) sappfpar pf=InstanceProfileName check            (or)

2) sappfpar check pf=InstanceProfileName

Look for output from memory pool

Shared memory pools

Key:   10  Pool

            Size configured.....:   1

            Size min. estimated.:  2

            Advised Size........:    3

Key:   40  Pool for database buffers

            Size configured.....:   X

            Size min. estimated.:   Y

            Advised Size........:    Z

Change the parameter ipc/shm_psize_<segno> to Advised Size and restart the instance.

regards

Swami

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Somesh,

Three notes, very easy to understand and select:

Have a look:

4101 - PXA_NO_SHARED_MEMORY

1790345 - PXA_NO_SHARED_MEMORY

307976 - PXA_NO_SHARED_MEMORY


All here is needed to adjust abap/buffersize parameter keeping in mind the actual address space.


Divyanshu

Former Member
0 Kudos

Hi Somesh,

As dump clearly says(short text and what happened), its because the abap share buffer is low.

From the parameter list you gave, it is  abap/buffersize=600000 = appr. half GB only.

Check ST02 for swaps in program buffer and you can also get corresponding parameter by double clicking particular buffer -> Current parameters.

Try increasing the abap buffer (between 1 - 1.5GB)  based on your system or compare other systems in your landscape to get an idea.

Please note that the default value for program buffer is in KB's. Hence you need to convert GB to KB

Thanks and Regards,

Nikhil

Former Member
0 Kudos

I'm guessing that you've just changed some parameters and restarted the system, so go back to the old versions in /usr/sap/<SID>/SYS/profile and restart the system.  Then you can review the parameters at your leisure.

Regards,

Graham

Former Member
0 Kudos

I included paramter "rdisp/rfc_min_wait_dia_wp=2" After adding this am getting dump.

Former Member
0 Kudos

well get rid of it and restart the system