SYSTEM_SHM_AREA_OBSOLETE

[Former Member]

Hi,

In ST22 Particular ABAP program generating SYSTEM_SHM_AREA_OBSOLETE ABAP dump.

Error analysis

    An attempt was made to access a shared memory area that has already been

     released. Possible reasons for release:

    - explicit release from an ABAP program or from the shared objects

      management transaction

    - implicit release during resource shortages

    The area which was to be accessed was in the shared objects area

     "\AREA=ZGSDCL_PRICE_COPY_SHM_AREA\INST=ZZZZZZ_PRICESD_COPY_SHM_AREA\CLNT=410"

    and was locked using the handle object

     "{O:2*\CLASS=ZZZZZZ_PRICESD_COPY_SHM_AREA}".

Please let me know to reslove this dump issue in ECC production database.

Regards,

MK

[divyanshu_srivastava3]

If this is for a custom program, ask you abaper to look into this.

Otherwise, upload full dump in HTML or some other format.

Give your system information, like release and patch level.

Regards,

Divyanshu

[Former Member]

Hi,

Please find the dump information below.

Runtime Errors         SYSTEM_SHM_AREA_OBSOLETE

Date and Time          25.07.2014 13:47:49

Short text

     Access to a shared objects area that has already been released.

What happened?

     Error in the ABAP Application Program

     The current ABAP program "ZGSDCL_PRICE_COPY_SHM_CREATOR=CP" had to be

      terminated because it has

     come across a statement that unfortunately cannot be executed.

What can you do?

     Note down which actions and inputs caused the error.

     To process the problem further, contact you SAP system

     administrator.

     Using Transaction ST22 for ABAP Dump Analysis, you can look

     at and manage termination messages, and you can also

     keep them for a long time.

Error analysis

     An attempt was made to access a shared memory area that has already been

      released. Possible reasons for release:

     - explicit release from an ABAP program or from the shared objects

      management transaction

    - implicit release during resource shortages

    The area which was to be accessed was in the shared objects area

     "\AREA=ZGSDCL_PRICE_COPY_SHM_AREA\INST=ZGSDCL_PRICE_COPY_SHM_AREA\CLNT=400"

    and was locked using the handle object

     "{O:2*\CLASS=ZGSDCL_PRICE_COPY_SHM_AREA}".

How to correct the error

    If the error occurred in your own ABAP program or in an SAP

    program you modified, try to remove the error.

System environment

    SAP-Release 701

    Application server... "p1bfcp24"

    Network address...... "10.144.68.29"

    Operating system..... "AIX"

    Release.............. "6.1"

    Hardware type........ "00F7EA334C00"

    Character length.... 16 Bits

    Pointer length....... 64 Bits

    Work process number.. 20

    Shortdump setting.... "full"

    Database server... "p1bfcp11-db"

    Database type..... "DB6"

  Database name..... "FCP"

  Database user ID.. "SAPFCP"

  Terminal.......... " "

  Char.set.... "C"

  SAP kernel....... 720

  created (date)... "Jul 8 2012 19:43:01"

  create on........ "AIX 2 5 00092901D600"

  Database version. "DB6_81 "

  Patch level. 300

  Patch text.. " "

  Database............. "DB6 08.02.*, DB6 09.*, DB6 10.*"

  SAP database version. 720

  Operating system..... "AIX 2 5, AIX 3 5, AIX 1 6, AIX 1 7"

  Memory consumption

  Roll.... 0

  EM...... 456782080

  Heap.... 0

  Page.... 0

  MM Used. 447464928

  MM Free. 9294992

er and Transaction

  Client.............. 400

  User................ "CONTROLM"

  Language key........ "E"

  Transaction......... " "

  Transactions ID..... "53D1EDC6CBC512C0E10080000A9044EC"

  Program............. "ZGSDCL_PRICE_COPY_SHM_CREATOR=CP"

  Screen.............. "SAPMSSYC 0100"

  Screen line......... 2

formation on where terminated

  Termination occurred in the ABAP program "ZGSDCL_PRICE_COPY_SHM_CREATOR=CP" -

   in "READ_VARIANTS".

  The main program was "SAPMSSYC ".

  In the source code you have the termination point in line 22

  of the (Include) program "ZGSDCL_PRICE_COPY_SHM_CREATOR=CM005".

  The program "ZGSDCL_PRICE_COPY_SHM_CREATOR=CP" was started as a background job.

  Job Name....... " "

  Job Initiator.. " "

  Job Number..... " "

Source Code Extract

Line  SourceCde

    1 method read_variants.

    2

    3 * init

    4   clear ex_i_variants.

    5

    6 * entry checks

    7   if im_i_mara_key is initial.

    8     return.

    9   endif.

   10

   11 * read all variants from MARA:

   12 * keep the select FOR ALL ENTRIES simple to gain performance --> therefore

   13 * the field PMATA is not included, because it would need a NE-operator!

   14 * have in mind that ITAB IM_I_MATGRP_SKU is large!

   15   select matnr pmata

   16     into table ex_i_variants

   17     from mara

   18     for all entries in im_i_mara_key

   19     where matnr = im_i_mara_key-matnr

   20     and   attyp = '02'.

   21

>>>>> endmethod.

Regards,

MK

[divyanshu_srivastava3]

Since this is a custom program and variant, ask your ABAPers to check this code first.