VL10b Error in EHP5

Question

Dear Guru's,
We currently doing some test in EHP5 environment and facing problem when running tcode VL10B
Message of the error is "Internal error found ==> see syslog"
It also gives message in ST22
"No more storage space available for extending an internal table."
First I think it was a Basis issue, but after Basis team allocated more memory the problem still occurs.
Please advice
Regards,
AT

Answer 1

Hi Sunny,
Bellow are the complete shortdump
Short text
    No more storage space available for extending an internal table.
What happened?
    You attempted to extend an internal table, but the required space was
    not available.
What can you do?
    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.
    Try to find out (e.g. by targetted data selection) whether the
    transaction will run with less main memory.
    If there is a temporary bottleneck, execute the transaction again.
    If the error persists, ask your system administrator to check the
    following profile parameters:
    o  ztta/roll_area            (1.000.000 - 15.000.000)
           Classic roll area per user and internal mode
           usual amount of roll area per user and internal mode
    o  ztta/roll_extension       (10.000.000 - 500.000.000)
           Amount of memory per user in extended memory (EM)
    o  abap/heap_area_total      (100.000.000 - 1.500.000.000)
           Amount of memory (malloc) for all users of an application
           server. If several background processes are running on
           one server, temporary bottlenecks may occur.
           Of course, the amount of memory (in bytes) must also be
           available on the machine (main memory or file system swap).
           Caution:
           The operating system must be set up so that there is also
           enough memory for each process. Usually, the maximum address
           space is too small.
           Ask your hardware manufacturer or your competence center
           about this.
           In this case, consult your hardware vendor
    abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each dialog process.
    Parameters for background processes:
    abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each background process.
    Other memory-relevant parameters are:
    em/initial_size_MB:         (35-1200)
           Extended memory area from which all users of an
           application server can satisfy their memory requirement.
Error analysis
    The internal table "\FUNCTION=SHP_LIKP_SELECT_02\DATA=CT_LIKP" could not be
     further extended. To enable
    error handling, the table had to be delete before this log was written.
    As a result, the table is displayed further down or, if you branch to
    the ABAP Debugger, with 0 rows.
    At the time of the termination, the following data was determined for
    the relevant internal table:
    Memory location: "Session memory"
    Row width: 2864
    Number of rows: 1845456
    Allocated rows: 1845456
    Newly requested rows: 4 (in 1 blocks)
    Last error logged in SAP kernel
    Component............ "EM"
    Place................ "SAP-Server prt02ec_P2S_00 on host prt02ec (wp 5)"
    Version.............. 37
    Error code........... 7
    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
    Description.......... " "
    System call.......... " "
    Module............... "emxx.c"
    Line................. 2232
    The error reported by the operating system is:
    Error number..... " "
    Error text....... " "
How to correct the error
    The amount of storage space (in bytes) filled at termination time was:
    Roll area...................... 6221072
    Extended memory (EM)........... 3469161024
    Assigned memory (HEAP)......... 2000761376
    Short area..................... " "
    Paging area.................... 0
    Maximum address space.......... 18446744049921009200
    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:
    "TSV_TNEW_PAGE_ALLOC_FAILED" " "
    "SAPLLE_SHP_DB_DELIVERY_BUF_EXE" or "LLE_SHP_DB_DELIVERY_BUF_EXEU11"
    "SHP_LIKP_SELECT_02"
    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..... 702
    SAP Basis Level. 0009
    Application server... "prt02ec"
    Network address...... "10.1.7.60"
    Operating system..... "SunOS"
    Release.............. "5.10"
    Hardware type........ "sun4u"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 5
    Shortdump setting.... "full"
    Database server... "prt02ec"
    Database type..... "ORACLE"
    Database name..... "P2S"
    Database user ID.. "SAPPEP"
    Terminal.......... "AllanTheGreat"
    Char.set.... "C"
    SAP kernel....... 720
    created (date)... "Oct 16 2011 21:41:26"
    create on........ "SunOS 5.9 Generic_122300-28 sun4u"
    Database version. "OCI_102, 10.2.0.4.0, V3 "
    Patch level. 109
    Patch text.. " "
    Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
    SAP database version. 720
    Operating system..... "SunOS 5.9, SunOS 5.10, SunOS 5.11"
    Memory consumption
    Roll.... 6221072
    EM...... 3469161024
    Heap.... 2000761376
    Page.... 0
    MM Used. 5302533992
    MM Free. 168458384
User and Transaction
    Client.............. 100
    User................ "ALLANT"
    Language key........ "E"
    Transaction......... " "
    Transaction ID...... "4EC3C0DF7CC71D8EE10000000A01073C"
    EPP Whole Context ID.... "8021287E578F1ED184864F59ADB45A42"
    EPP Connection ID....... "4EC3C0F77CC71D8EE10000000A01073C"
    EPP Caller Counter...... 1
    Program............. "SAPLLE_SHP_DB_DELIVERY_BUF_EXE"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Debugger Active..... "none"
Server-Side Connection Information
    Information on caller of Remote Function Call (RFC):
    System.............. "P2S"
    Installation Number. " "
    Database Release.... 702
    Kernel Release...... 720
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "asynchronous with reply and non-transactional (emode 0,
     imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. 100
    User................ "ALLANT"
    Transaction......... "VL10X"
    Call Program........."SAPLV50R_VIEW"
    Function Module..... "SHP_VL10_DELIVERY_CREATE_PARA"
    Call Destination.... "prt02ec_P2S_00"
    Source Server....... "prt02ec_P2S_00"
    Source IP Address... "10.1.7.60"
    Additional information on RFC logon:
    Trusted Relationship " "
    Logon Return Code... 0
    Trusted Return Code. 0
    Note:
    - For Releases < 4.0, information on the RFC caller not available.
    - The installation number is available from caller Release > 700
    Additional information on RFC logon:
    Trusted Relationship " "
    Logon Return Code... 0
    Trusted Return Code. 0
    Note: For releases < 4.0, information on the RFC caller are often
    only partially available.
Information on where terminated
    Termination occurred in the ABAP program "SAPLLE_SHP_DB_DELIVERY_BUF_EXE" - in
     "SHP_LIKP_SELECT_02".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 14
    of the (Include) program "LLE_SHP_DB_DELIVERY_BUF_EXEU11".
Source Code Extract
Line  SourceCde
    1 FUNCTION SHP_LIKP_SELECT_02.
    2 *"----
    3 ""Lokale Schnittstelle:
    4 *"       IMPORTING
    5 *"             REFERENCE(IT_LIKP_KEY) TYPE  SHP_VL10_LIKP_KEY_T
    6 *"             REFERENCE(IF_SORT) TYPE  XFELD DEFAULT 'X'
    7 *"       CHANGING
    8 *"             VALUE(CT_LIKP) TYPE  SHP_VL10_LIKP_T
    9 *"       EXCEPTIONS
   10 *"              NO_RECORD_FOUND
   11 *"----
   12 * For buffered select use FunctionGroup V50R !!!
   13
>>>>>   SELECT * FROM LIKP
   15            INTO TABLE CT_LIKP
   16            FOR ALL ENTRIES IN IT_LIKP_KEY
   17            WHERE   VBELN = IT_LIKP_KEY-VBELN.
   18
   19   IF SY-SUBRC <> 0.
   20     MESSAGE E551(VR) WITH 'LIKP' RAISING NO_RECORD_FOUND.
   21   ELSEIF IF_SORT = 'X'.
   22     SORT CT_LIKP BY VBELN.
   23   ENDIF.
   24 ENDFUNCTION.
Edited by: Allan Taufiq on Nov 16, 2011 11:23 AM