Run Time Error TSV_BTR_PAGE_ALLOC_FAILED

Question

I am getting a runtime error TSV_BTR_PAGE_ALLOC_FAILED while triggering the initial data load from SRM in to BI.
It is a customized extractor using customized function module.While analyzing the dump, a standard program throws this dump.
Pl give me a solution..
Thanks

Answer 1

Dump from ST22 ,
Runtime Errors         TSV_BTR_PAGE_ALLOC_FAILED
Date and Time          12/19/2011 05:27:36
Short text
     No memory available to enhance 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 index of a table - organized as tree-type - was to be enhanced, but
the requested memory of 8712 bytes was not available.
    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_BTR_PAGE_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.. 50
Shortdump setting.... "full"
    Database server... "hpbpgc01"
    Database type..... "ORACLE"
    Database name..... "PR1"
    Database user ID.. "SAPSR3"
    Terminal.......... " "
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.... 2730640
    EM...... 2002743520
    Heap.... 1961107504
    Page.... 32768
MM Used. 3819942032
MM Free. 140880688
User and Transaction
    Client.............. 100
    User................ "ALEREMOTE"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "4EEE7307C66D4D34E10000000AA3022E"
    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 "SBIE0001 ".
    In the source code you have the termination point in line 27
of the (Include) program "LBBP_PDBUPF2C".
    The program "SAPLBBP_PDBUP" was started as a background job.
    Job Name....... "BIREQU_4O81LDIVXQKOIU909IFIZWCHD"
    Job Initiator.. "ALEREMOTE"
    Job Number..... 02322400
Source Code Extract
Line  SourceCde
    1 &----
    2 *&Form  fill_x_tables
    3 &----
    4 *       text
    5 ----
    6 *      -->IT_BUP     text
    7 ----
    8 FORM fill_x_tables
    9                   TABLES it_bup STRUCTURE bbp_pds_bup_ic
   10                   USING  iv_object_type TYPE crmt_subobject_category_db.
   11
   12   DATA: lv_my_logsys     TYPE logsys,
   13         lv_subrc         TYPE sysubrc,
   14         lv_partner_ftype TYPE bbp_partner_ftyp,
   15         lv_partner_no    TYPE crmt_partner_no,
   16         lv_addr_nr       TYPE ad_addrnum,
   17         lv_addr_np       TYPE ad_persnum,
   18         lv_partner_guid  TYPEbu_partner_guid.
   19
   20
   21   CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
   22     IMPORTING
   23       own_logical_system = lv_my_logsys
   24     EXCEPTIONS
   25       OTHERS             = 0.
   26
>>>>>   SORT gx_addr BY addr_nopers_no.
   28
   29   LOOP AT it_bup.
   30 *      because there is no del_ind indicator on database we synchronize
   31 *      the flags del_ind and diesbaled
   32     it_bup-del_ind = it_bup-disabled.
   33 *      fill logsys
   34     IF it_bup-partner_src_sys EQ lv_my_logsys.
   35       CLEAR it_bup-partner_src_sys.
   36     ENDIF.
   37
   38 *---fill partner ID and no_type
   39     PERFORM fill_id_and_guid USING it_bup-partner_src_sys
   40                             CHANGING it_bup-partner_id
41                                      it_bup-partner_no
42                                      it_bup-no_type.
   43     MODIFY it_bup.
   44 *---get address-data from ZAV and fill gx_addr
   45     PERFORM pdbup_fill_addr_buffer USING    it_bup-addr_np
46                                             it_bup-addr_nr