Dump TSV_LIN_ALLOC_FAILED in SRM

Question

While extracting the datasource in RSA3 it throws the TSV_LIN_ALLOC_FAILED runtime error in SRM.It is a costomized extractor using the customized function module.
Thanks,

Answer 1

Here is the ST22 dump,
Runtime Errors         TSV_LIN_ALLOC_FAILED
Date and Time          12/19/2011 07:54:24
Short text
     No memory available to extend the index of an internal table.
What happened?
     Each transaction requires some main memory space to process
     application data. If the operating system cannot provide any more
     space, the transaction is terminated.
What can you do?
     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.
    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.
Error analysis
    The linear index of an internal table was to be enhanced. However, the
    requested memory for this purpose of 706240 bytes was no longer available
    in the roll area.
    Storage location: "Session memory"
How to correct the error
    Try to decide by analysis whether this request is
    reasonable or whether there is a program error. You should pay
    particular attention to the internal table entries listed below.
    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_LIN_ALLOC_FAILED" " "
    "SAPLBBP_PDBUP" or "LBBP_PDBUPF2C"
    "FILL_X_TABLES"
System environment
    SAP-Release 701
    Application server... "sappr1a2"
    Network address...... "10.163.2.46"
    Operating system..... "HP-UX"
    Release.............. "B.11.31"
    Hardware type........ "ia64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "hpbpgc01"
    Database type..... "ORACLE"
    Database name..... "PR1"
    Database user ID.. "SAPSR3"
    Terminal.......... "FFXCTXGC26"
    Char.set.... "C"
    SAP kernel....... 701
    created (date)... "Oct 31 2010 21:56:13"
    create on........ "HP-UX B.11.23 U ia64"
    Database version. "OCI_102 (10.2.0.4.0) "
    Patch level. 117
    Patch text.. " "
    Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
    SAP database version. 701
    Operating system..... "HP-UX B.11"
    Memory consumption
    Roll.... 1917712
    EM...... 2002743520
    Heap.... 1998752864
    Page.... 1867776
    MM Used. 3846087392
    MM Free. 143093200
User and Transaction
    Client.............. 100
    User................ "XMSELVA"
    Language key........ "E"
    Transaction......... "RSA3 "
    Transactions ID..... "4EEEF6C8B62E4B0BE10000000AA3022E"
    Program............. "SAPLBBP_PDBUP"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
Information on where terminated
    Termination occurred in the ABAP program "SAPLBBP_PDBUP" - in "FILL_X_TABLES".
    The main program was "RSFHGEN2 ".
    In the source code you have the termination point in line 120
    of the (Include) program "LBBP_PDBUPF2C".
Source Code Extract
Line  SourceCde
   90             log_not_found = 1
   91             OTHERS        = 2.
   92         IF sy-subrc <> 0.
   93           PERFORM abort.
   94         ENDIF.
   95         IF c_on = c_off. MESSAGE w536(bbp_pd). ENDIF.
   96
   97       ELSE.
   98
   99 *------ address data were not found
  100         CALL FUNCTION 'BBP_PD_MSG_ADD'
  101           EXPORTING
  102             i_msgty       = c_msgty_w
  103             i_msgid       = 'BBP_PD'
  104             i_msgno       = 163
  105           EXCEPTIONS
  106             log_not_found = 1
  107             OTHERS        = 2.
  108         IF sy-subrc <> 0.
  109           PERFORM abort.
  110         ENDIF.
  111         IF c_on = c_off. MESSAGE w163(bbp_pd). ENDIF.
  112       ENDIF.
  113
Information on where terminated
    Termination occurred in the ABAP program "SAPLBBP_PDBUP" - in "FILL_X_TABLES".
    The main program was "RSFHGEN2 ".
    In the source code you have the termination point in line 120
    of the (Include) program "LBBP_PDBUPF2C".
Source Code Extract
Line  SourceCde
   90             log_not_found = 1
   91             OTHERS        = 2.
   92         IF sy-subrc <> 0.
   93           PERFORM abort.
   94         ENDIF.
   95         IF c_on = c_off. MESSAGE w536(bbp_pd). ENDIF.
   96
   97       ELSE.
   98
   99 *------ address data were not found
  100         CALL FUNCTION 'BBP_PD_MSG_ADD'
  101           EXPORTING
  102             i_msgty       = c_msgty_w
  103             i_msgid       = 'BBP_PD'
  104             i_msgno       = 163
  105           EXCEPTIONS
  106             log_not_found = 1
  107             OTHERS        = 2.
  108         IF sy-subrc <> 0.
  109           PERFORM abort.
  110         ENDIF.
  111         IF c_on = c_off. MESSAGE w163(bbp_pd). ENDIF.
  112       ENDIF.
  113
  113
  114     ENDIF.
  115 *---fill gx_bup
  116     PERFORM insert_gx_bup USING it_bup.
  117
  118   ENDLOOP.
  119
>>>>>   SORT gx_addr BY guid.
  121 ENDFORM.                    " fill_x_tables
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 1
SY-TABIX 53
SY-DBCNT 0
SY-FDPOS 45
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Report for the extractor call
SY-MSGTY E
SY-MSGID R1
SY-MSGNO 201
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 2
SY-DATUM 20111219
SY-UZEIT 052933
Thanks,