SYSTEM_SHM_AREA_OBSOLETE

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

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

Similar Messages

  • Shared memory -  Delete instances

    data :  text type char10.
    text =  'ME'.
    data :  val1 type string.
    try.
    o_area = zcl_mar_area=>attach_for_write(  ).
    create object o_sme area handle o_area.
    o_area->set_root( o_sme ).
    o_sme->value = 'TEXT'.
    o_area->detach_commit( ) .
    catch cx_shm_attach_error.
    endtry.
    data :  val1 type string.
    try.
        data : hdl type ref to zcl_mar_area,
              root type ref to zcl_mar_shma.
        hdl = zcl_mar_area=>attach_for_read( ).
        val1 = hdl->root->value.
    *   TRY.
      data : oref   type ref to cx_root,
              text type string,
             text1   type string.
    *    itab_fms = hdl->root->itab.
    catch cx_shm_inconsistent into oref.
            text1 = oref->get_text( ).
    catch cx_shm_change_lock_active into oref.
            text1 = oref->get_text( ).
    catch cx_shm_exclusive_lock_active into oref.
            text1 = oref->get_text( ).
    catch cx_shm_read_lock_active into oref.
            text1 = oref->get_text( ).
    catch cx_shm_no_active_version into oref.
            text = oref->get_text( ).
    if hdl is not INITIAL.
    hdl->detach( ).
    hdl->detach_commit( ).
    endif.
    *TRY.
    data: rc type shm_rc.
    CALL METHOD zcl_mar_area=>invalidate_instance
      EXPORTING
        inst_name         = CL_SHM_AREA=>DEFAULT_INSTANCE
        terminate_changer = ABAP_TRUE
      receiving
        rc                = rc
    * CATCH cx_shm_parameter_error .
    *ENDTRY.
    endtry.
    TRY.
    CALL METHOD zcl_mar_area=>free_instance
      EXPORTING
        inst_name         = CL_SHM_AREA=>default_instance
        terminate_changer = ABAP_TRUE
      receiving
        rc                = rc
    CATCH cx_shm_parameter_error .
    ENDTRY.
    I am getting this dump - SYSTEM_SHM_AREA_OBSOLETE
    PLease help

    Works as designed.
    Quote from documentation for free_instance:
    After this method has been executed, all programs where area handles still exist for the released area instance versions are terminated with the SYSTEM_SHM_AREA_OBSOLETE runtime error.
    Not sure why your are using free instance anyway. The invalidation should be sufficient. Also at the beginning of your code, you use detach and detach_commit in succession, detach_commit is enough to close the changing connection.

  • Shared Memory Short Dump: SHMM ab_ShmResetLocks - anyone?

    hello:)
         I have a problem with shared memory area (SHMM) that dumps.
    I have a tool that uses a shared memory area instance to store data.
    When I run the tool and update the data stored in the instance, a short dump is thrown:
    SYSTEM_SHM_AREA_OBSOLETE with the explanation:
    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 first one does not match, as I DO NOT explicitly release the instance of my area.
    Moreover, ST22 shows me different parts of code every time, so my code is not the cause, or a specific part of code, or data that I shift.
    The second one would probably be the cause.
    But how can I avoid it?
    Moreover, there in SM21(System Log) there is at this time, there is a runtime error, that says
    ab_ShmResetLocks and nothing more:(
    Shared Memory size is sufficient.
    The Shared Memory Area Settings (SHMA) do not time out the read/write access(Lifetime: no entry and Automatic area structuring is set)
    Any help is more than welcome, why i get the short dump!!
    best regards
    simon:)

    Please check the following SAP notes:
    [SAP Note 1105266 WDA: Runtime error SYSTEM_SHM_AREA_OBSOLETE|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_wd/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d31313035323636%7d]
    Also check the below notes for related details.
    Note 1322182 - Memory consumption of ABAP Shared Objects
    [SAP Note 764187 SYSTEM_SHM_AREA_DETACHED runtime error|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_aba/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d373634313837%7d]
    Please check the size of the shared memory object in the profile parameter abap/shared_objects_size_MB.
    Regards,
    Dipanjan

Maybe you are looking for