Report MB5L giving runtime error TSV_TNEW_PAGE_ALLOC_FAILED

Hi,
While running the Report MB5L we are getting the runtime
error "TSV_TNEW_PAGE_ALLOC_FAILED"
We tried to schedule this report at non-peak hours but it again got
terminated with same error.
We are using 12GB of RAM.
ztta/roll_area 6500000
ztta/roll_extension 4000317440
abap/heap_area_total 3001024512
abap/heap_area_dia: 5000683008
abap/heap_area_nondia: 2000000000
em/initial_size_MB: 8192
Please find the attached screenshot of ST22 dump analysis.
Regards,
Prashant
Edited by: Prashant Shukla on Feb 25, 2009 11:10 AM

Hi Juan,
Pls find the details below-:
Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED                                                  
Date and Time          24.02.2009 23:31:32                                                                               
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.                                                                               
If the error persists, ask your system administrator to check the                             
    following profile parameters:                                                                               
Error analysis                                                                               
The internal table "\FUNCTION=MBEW_EXTEND\DATA=SEARCH_MBEWH_TAB[]" 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: 372                                                                               
Number of rows: 354608                                                                        
    Allocated rows: 354608                                                                        
    Newly requested rows: 32 (in 1 blocks)                                                        
How to correct the error                                                                               
The amount of storage space (in bytes) filled at termination time was:                                                                               
Roll area...................... 6203136                                                       
    Extended memory (EM)........... 4001304840                                                    
    Assigned memory (HEAP)......... 2000059568                                                    
    Short area..................... " "                                                           
    Paging area.................... 32768                                                         
    Maximum address space.......... 18446697160833538863                                                                               
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" " "                                                              
    "SAPLMG27" or "LMG27F02"                                                                      
    "SEARCH_EXIT"                                                                               
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 700                                                                               
Application server... "ecprdciclu"                                                            
    Network address...... "172.25.1.34"                                                           
    Operating system..... "Linux"                                                                 
    Release.............. "2.6.18-53.el5"                                                         
    Hardware type........ "x86_64"                                                                
    Character length.... 16 Bits                                                                  
    Pointer length....... 64 Bits                                                                 
    Work process number.. 19                                                                      
    Shortdump setting.... "full"                                                                               
Database server... "isrecprdb2"                                                               
    Database type..... "ORACLE"                                                                   
    Database name..... "RPD"                                                                      
    Database user ID.. "SAPSR3"                                                                               
Char.set.... "C"                                                                               
SAP kernel....... 700                                                                         
    created (date)... "Nov 18 2008 20:45:39"                                                      
    create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"                                           
    Database version. "OCI_102 (10.2.0.2.0) "                                                                               
Patch level. 185                                                                               
Patch text.. " "                                                                               
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."                
    SAP database version. 700                                                                     
    Operating system..... "Linux 2.6"                                                                               
Memory consumption                                                                               
Roll.... 6203136                                                                               
EM...... 4001304840                                                                               
Heap.... 2000059568                                                                               
Page.... 32768                                                                               
MM Used. 5803144952                                                                               
MM Free. 199241240                                                                               
User and Transaction                                                                               
Client.............. 610                                                                      
    User................ "SANCHIT"                                                                
    Language key........ "E"                                                                      
    Transaction......... " "                                                                      
    Transactions ID..... "49A289F286FA2313E1000000AC190122"                                                                               
Program............. "SAPLMG27"                                                               
    Screen.............. "SAPMSSY0 1000"                                                          
    Screen line......... 6                                                                        
Information on where terminated                                                                   
    Termination occurred in the ABAP program "SAPLMG27" - in "SEARCH_EXIT".                       
    The main program was "RM07MBST ".                                                                               
In the source code you have the termination point in line 558                                 
    of the (Include) program "LMG27F02".                                                          
    The program "SAPLMG27" was started as a background job.                                       
    Job Name....... "RM07MBST"                      
Regards,
Prashant

Similar Messages

  • Report giving runtime error

    hi,
    i HAD MADE A REPORET IN which i havce to display the bolck stock ,it is giving runtime error as i had added 1 more table,plzz help me out as it is really urgent to me. here is d code:-
    *& Report  ZDEMO_SMARTFORM_COPY
    REPORT  ZDEMO_SMARTFORM_COPY.
    TABLES: MCHB,MARA,T001W.
    DATA: BEGIN OF ITAB OCCURS 0,
          ITEMID LIKE MARD-MATNR,
          SPEME LIKE MARD-SPEME,
          WERKS LIKE MARD-SPEME,
          LGORT LIKE MARD-LGORT,
          NTGEW LIKE MARA-NTGEW,
          MEINS LIKE MARA-MEINS,
          GEWEI LIKE MARA-GEWEI,
          CHARG LIKE MCHB-CHARG,
          WTKG LIKE MARA-NTGEW,
          STOCK TYPE P LENGTH 10 DECIMALS 3,
          DESC LIKE MAKT-MAKTX,
          TOTWT LIKE MARD-SPEME,
          WT TYPE P LENGTH 12 DECIMALS 3,
          END OF ITAB.
         ITEMID LIKE MCHB-MATNR,
         CSPEM LIKE MCHB-CSPEM,
         CHARG LIKE MCHB-CHARG,
         WERKS LIKE MCHB-WERKS,
    *PARAMETERS : PLANT LIKE MCHB-WERKS OBLIGATORY.
    PARAMETERS : PLANT LIKE MARD-WERKS OBLIGATORY.
    DATA : DESC LIKE MAKT-MAKTX.
      SELECT AMATNR ASPEME AWERKS ALGORT BNTGEW BMEINS BGEWEI CCHARG FROM MARD AS A
        INNER JOIN MARA AS B ON BMATNR = AMATNR
          INNER JOIN MCHB AS C ON CMATNR = AMATNR
            INTO TABLE ITAB WHERE AWERKS = PLANT AND ASPEME > 0.
    SELECT AMATNR ACSPEM ACHARG AWERKS  BNTGEW BMEINS B~GEWEI FROM MCHB AS A
       INNER JOIN MARA AS B ON BMATNR = AMATNR
         INTO TABLE ITAB WHERE AWERKS = PLANT AND ACSPEM > 0.
    WRITE: / 'ITEMID           DESCRIPTION                              STOCK.QTY  BATCH NO.           NETWT          TOTAL.WEIGHT '.
    ULINE.
    LOOP AT ITAB.
          IF ITAB-NTGEW <> 0 .
            CALL FUNCTION 'ZGET_ITEM_WEIGHT'
             EXPORTING
               P_BUID         = ITAB-WERKS
               P_ITEMID       = ITAB-ITEMID
               P_QTY          = ITAB-NTGEW
               P_UOM          = ITAB-GEWEI
               P_UOM1         = 'KG'
             IMPORTING
               P_RETVAL       = ITAB-WTKG.
          ENDIF.
       CONVERTING ITEM QTY IN KG
          ITAB-WT = ITAB-STOCK.
          IF ITAB-MEINS = 'G'.
            ITAB-WT = ITAB-STOCK / 1000000.
          ELSEIF ITAB-MEINS = 'KG'.
            ITAB-WT = ITAB-STOCK / 1000.
          ELSEIF ITAB-MEINS = 'TO'.
            ITAB-WT = ITAB-STOCK * ITAB-WTKG / 1000.
         ENDIF.
       ITAB-TOTWT = ITAB-WTKG * ITAB-CSPEM.
       ITAB-TOTWT = ITAB-WTKG * ITAB-SPEME.
       SELECT SINGLE MAKTX FROM MAKT INTO DESC WHERE MATNR = ITAB-ITEMID.
         WRITE:/ ITAB-ITEMID,15 DESC,50 ITAB-SPEME,ITAB-CHARG,ITAB-WTKG,ITAB-TOTWT.
       MODIFY ITAB.
       ENDLOOP.

    HI,
    i had tried to ftech data from mard and it isgiving runtime error. dis is the code:-
    TABLES: MCHB,MARA,MARD.
    DATA: BEGIN OF ITAB OCCURS 0,
          MATNR LIKE MARD-MATNR,
          SPEME LIKE MARD-SPEME,
          WERKS LIKE MARD-SPEME,
          LGORT LIKE MARD-LGORT,
          END OF ITAB.
          SELECT MATNR SPEME WERKS LGORT FROM MARD INTO CORRESPONDING FIELDS OF TABLE ITAB.
          LOOP AT ITAB.
          WRITE:/ ITAB-MATNR,ITAB-SPEME,ITAB-WERKS,ITAB-LGORT.
          ENDLOOP.

  • Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED during extraction

    Hi,
    Anyone knows what the solution is to this problem:
    Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
    |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
    |Error analysis                                                                                |
    |    The internal table "\FUNCTION=CRM_UPLOAD_BTMBDOC_FILL\DATA=ET_BILLPLAN_D" 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: 1908                                                                               |
    |    Number of rows: 35912                                                                         |
    |    Allocated rows: 35912                                                                         |
    |    Newly requested rows: 8 (in 1 blocks)                                                         |
    |    Last error logged in SAP kernel                                                               |
    |                                                                                |
    |    Component............ "EM"                                                                    |
    |    Place................ "xxx"                   |
    |    Version.............. 37                                                                      |
    |    Error code........... 7                                                                       |
    |    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "                  |
    |    Description.......... " "                                                                     |
    |    System call.......... " "                                                                     |
    |    Module............... "emxx.c"                                                                |
    |    Line................. 1897                                                                    |
    |                                                                                |
    |    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...................... 6221152                                                       |
    |    Extended memory (EM)........... 1826778184                                                    |
    |    Assigned memory (HEAP)......... 2000035456                                                    |
    |    Short area..................... " "                                                           |
    |    Paging area.................... 73728                                                         |
    |    Maximum address space.......... 4294967295                                                    |
    |                                                                                |
    |    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" " "                                                              |
    |    "SAPLCRM_UPLOAD_BTMBDOC" or "LCRM_UPLOAD_BTMBDOCF36"                                          |
    |    "FILL_BILLPLAN"                                                                               |
    |                                                                                |
    |    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.                                                           |
    |                                                                                |

    Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
    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.
    |Error analysis                                                                                |
    |    The internal table "\FUNCTION=CRM_UPLOAD_BTMBDOC_FILL\DATA=ET_BILLPLAN_D" 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: 1908                                                                               |
    |    Number of rows: 35912                                                                         |
    |    Allocated rows: 35912                                                                         |
    |    Newly requested rows: 8 (in 1 blocks)                                                         |
    |    Last error logged in SAP kernel                                                               |
    |                                                                                |
    |    Component............ "EM"                                                                    |
    |    Place................ "SAP-Server XXXX"                   |
    |    Version.............. 37                                                                      |
    |    Error code........... 7                                                                       |
    |    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "                  |
    |    Description.......... " "                                                                     |
    |    System call.......... " "                                                                     |
    |    Module............... "emxx.c"                                                                |
    |    Line................. 1897                                                                    |
    |                                                                                |
    |    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...................... 6221152                                                       |
    |    Extended memory (EM)........... 1826778184                                                    |
    |    Assigned memory (HEAP)......... 2000035456                                                    |
    |    Short area..................... " "                                                           |
    |    Paging area.................... 73728                                                         |
    |    Maximum address space.......... 4294967295                                                    |
    |                                                                                |
    |    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" " "                                                              |
    |    "SAPLCRM_UPLOAD_BTMBDOC" or "LCRM_UPLOAD_BTMBDOCF36"                                          |
    |    "FILL_BILLPLAN"                                                                               |
    |                                                                                |
    |    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.                                                           |
    |                                                                                |

  • Runtime errors: TSV_TNEW_PAGE_ALLOC_FAILED

    Hi,
    When I am trying to check the consistency of background jobs in SM65, It is throwig a runtime error TSV_TNEW_PAGE_ALLOC_FAILED. Kindly look into the below text message from ST22.
    ShrtText
        No 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?
        Make a note of the actions and input which caused the error.
        To resolve the problem, contact your SAP system administrator.
        You can use transaction ST22 (ABAP Dump Analysis) to view and administer
        termination messages, especially those beyond their normal deletion
        date.
        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)
    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 "IT_18" could not be enlarged further. To allow
    error handling, the table had to be deleted before this log was
    created. So, if you branch to the ABAP debugger from the display
    of this log, the table will there be displayed with 0 rows.
    At the moment of the termination, the following data was
    determined for the respective internal table:
    Storage location: "Session memory"
    Row width: 1296
    Number of rows: 1166120
    Allocated rows: 1166120
    Newly requested rows: 8 (in 1 blocks)
               Last error logged in SAP kernel
    Component............ "EM"
    Place................ "SAP-Server ord-sapprd_PRD_00 on host ord-sapprd (wp 0)"
    Version.............. 37
    Error code........... 7
    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
    Description.......... " "
    System call.......... " "
    Module............... "emxx.c"
    Line................. 1878
    How to correct the error
        The amount of storage space (in bytes) filled at termination time was:
        Roll area...................... 1709536
        Extended memory (EM)........... 408685712
        Assigned memory (HEAP)......... 1190561024
        Short area..................... " "
        Paging area.................... 57344
        Maximum address space.......... " "
        You may able to find an interim solution to the problem
        in the SAP note system. If you have access to the note system yourself,
        use the following search criteria:
        "TSV_TNEW_PAGE_ALLOC_FAILED" C
        "SAPLSBPT" or "LSBPTFXX"
        "DO_TBTCO_CONSISTENCY_CHECK"
        If you cannot solve the problem yourself and you wish to send
        an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
       To obtain this, select in the current display "System->List->
       Save->Local File (unconverted)".
    2. A suitable printout of the system log
       To obtain this, call the system log through transaction SM21.
       Limit the time interval to 10 minutes before and 5 minutes
       after the short dump. In the display, then select the function
       "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, select the Editor function "Further Utilities->
       Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    System environment
    SAP Release.............. "640"
    Application server....... "ord-sapprd"
    Network address.......... "10.31.18.27"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "16x Intel 80158"
    Character length......... 16 Bits
    Pointer length........... 32 Bits
    Work process number...... 0
    Kindly suggest me the options ASAP as this is happened in the production system.
    Thanks in advance,
    Suneetha Reddy

    Hi Sunnetha,
    SM65 is a resource hungry tcode, and always suggested to run during a off-business hours. Try to run when there is not much acvitity going on in the system.
    I'm not very much sure, but please check how many entries there in TBTCO table. as the dump gives indication of
    DO_TBTCO_CONSISTENCY_CHECK.
    Check RSBTCDEL(2) program is running daily or not. This runs as a background job to delete the old job information from the tables TBTC*. If this has not run, then you can run and delete older job logs and then retry.
    Which system you're using? ECC or BW??
    Note - parameter settings of BW largely varies from that of a ECC system.
    Thanks,
    Debasis.

  • Handle Runtime error: TSV_TNEW_PAGE_ALLOC_FAILED

    Hi,
    In my programme, some times I end up with handling of lots of data in internal table. And this results in a dump.
    Category               ABAP Server Resource Shortage
    Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
    Short text
        No more memory available to extend an internal table.
    I read few threads where they suggested to increase the internal memory of ths system. This is beyond my scope!
    Is there anyway I can catch this exception and stop the programme from executing further?
    Thanks in advance!
    Cheers
    Kiran

    Hello Kiran,
    TSV_TNEW_PAGE_ALLOC_FAILED is a not catchable error. It happens if a program exceeds the system boundaries, typically ~2 GB. Requesting so much memory is a strong indication for a flaw in the archtecture.
    Anyway these kind of errors require a change in the program or in the arguments given to them. In newer releases you may try S_MEMORY_INSPECTOR to analyse the endless need of memory. In older releases watch out for hughe internal tables in the ST22 dump.
    Regards
      Klaus

  • Runtime error TSV_TNEW_PAGE_ALLOC_FAILED on executing FAGLL03.

    Hi expert,
    I am getting Runtime error TSV_TNEW_PAGE_ALLOC_FAILED error while executing FAGLL03.
    Please do the neeful.
    extented memeory--4,186,112
    and Heap Memory---1,960,171
    is configured.
    Os--HP-UX
    ECC 6.0 with oracle 10g
    server has 12 GB of RAM for the application instance and db instance is other server.
    Please
    Regards,
    vivek

    How to correct the error
        The amount of storage space (in bytes) filled at termination time was:
        Roll area...................... 5720752
        Extended memory (EM)........... 502780800
        Assigned memory (HEAP)......... 0
        Short area..................... " "
        Paging area.................... 122880
        Maximum address space.......... 4294967295
    and the paramters are.
    em/initial_size_MB---4092
    abap/heap_area_total---2000000000
    Please do the neeful.

  • Runtime Error TSV_TNEW_PAGE_ALLOC_FAILED

    Hello friends,
    One of our Z-transactions (run in background) terminates with the runtime error TSV_TNEW_PAGE_ALLOC_FAILED. It runs successfully in another system. Of course memory settings are different in these systems so are the resources. I see in the affected system that parameter abap/heap_area_total is 2GB and parameters abap/heap_area_dia and abap/heap_area_nondia are only allocated 10MB each. Will there be any issue if we increase the above 2 parameters to 2GB each? If we do so, is the value allocated entirely at startup? Will it affect system performance? Please help.
    Thanks,
    Atul Lotlikar.

    Hi Atul,
    You can extend abap/heap_area_dia  and abap/heap_area_nondia to 2GB without any problem. 10MB was limitation for 32-bit AIX system. It only gets activated at the start up.
    However, you might want to have a look at em/initial_size_MB and ztta/roll_extension and try to increase them in the system where the problem is occurring.
    Also, two systems can have different amount of data volume which can explain why it runs in one system but not in other. Then you probably have to have a look at the Z-program itself.
    Hope it helps.
    Cheers !!
    Satya.
    PS: pls reward points if the answer was helpful...Thx.

  • Infoset query: Runtime Errors  TSV_TNEW_PAGE_ALLOC_FAILED

    Hi
    I have searched the forum and could not find suitable solution for my problem.
    We have an infoset query whose data source is an ABAP program and this is within our BW system only. Earlier it used to run perfectly fine. Recently, due to the increasing data, the load for the same is failing because of memory issue with runtime Error  TSV_TNEW_PAGE_ALLOC_FAILED . The dump occurs within 5-7 minutes of the data load. Once, we give some more filter selections in the infopackage, it runs fine.
    Our problem is neither we can increase the memory any further nor we want to give filter selections in the infopackage. Also, once we execute the ABAP program alone, it runs fine.
    Any help to solve this problem is appreciated.
    Cheers
    Chanda

    Hi,
    There are 3 ways to avoid this kind of problem:
    1) Reduce the data set - if it is possible to process this in smaller
    chunks then please do. This is an infoset query - please be more restrictive in your selections
    - please refer to note 354657.
    When you work with infosets that use tables or joins then it is
    possible to read packages (from Rel. 6.10 on). When you work with
    infosets that use logical databases or data retrieval programs than
    it is not possible to read packaged - by technical restrictions.
    That means that the query is executed completely taking all restrictions
    into account and the result is stored internally.
    2) Re-allocate some of the unused shared memories to program memory.
    A prime candidate for this is Roll and Page "In Memory" values.
    Alternative memory management via PHYSMEMSIZE generally overallocates
    roll and page memory. Please reduce the amounts allocated to the "in
    memory" part (see ST02) using the parameters below, for instance:
    rdisp/ROLL_MAXFS....Total amt of ROLL (Filesystem+SHM); in 8KB blocks
    rdisp/ROLL_SHM......Shared memory element of Roll; in 8KB blocks
    rdisp/PG_MAXFS......Total amt of Page (Filesystem+SHM); in 8KB blocks
    rdisp/PG_SHM........Shared memory element of Roll; in 8KB blocks
    =>Filsystem amt = MAXFS - SHM
    60MB or so each in memory should be sufficient.
    This should allow an extra 260Mb or so for process memory.
    Bear in mind however that Roll_SHM MUST be greater than 10% of
    Roll_MAXFS.
    This will not affect alternative memory management operation in any way.
    3) Reduce the em/global_area_MB from 128 to 64MB.
    These measures should give you ~320MB additionally per work process.
    To get even more - if there is a 64 bit machine in the landscape then
    redirect the load there.
    I would like for you to review the SAP Note 712664. Although
    the Notes 20527, 369726 and 166551 specifically refers to this
    and has helped resolve multiple performance problems.
    I hope it can help you.
    Fran.

  • Is it a bug in JNI...CallVoidMethod(..) giving runtime error??

    Hi
    I have invoked jvm using C++. I called the main method of my application and it is running fine.
    When I try to invoke another method of the same class that is not static by GetMethodID(..) and then CallVoidMethod(..), the ID is coming out fine but the call to the method is giving a runtime error.
    When I make this method static in java, it runs fine.
    Is it a bug in JNI that we cannot call nonstatic void methods?

    I have declared the jclass cls object in global space in C++ file. I use the FindClass(..) function to find it. Everything is turning out to be fine till I call the main() function of the java class.
    Now when I get the Id using the GetMethod(..) function of JNI, it comes out fine and gives no errors. It is only when I call the CallVoidMethod(...), it gives me a runtime error. I have tried to use this method in java without C++ and it gives no error.
    Any idea .. what may be wrong?

  • BI IView giving runtime error

    HI,
    Portal Runtime Error
    An exception occurred while processing your request
    Exception id: 12:09_09/04/08_0074_336182350
    See the details for the exception ID in the log file.
    This is the error , I am getting
    When we are publishing from WAD to portal , it is giving the Portal Runtime Error.
    If we create the same one step by step manualy it is giving the result.
    Difference I found is in both the iviews is : System - BI (alias of logical system in the landscape)
    Manually created Iview , System : Sap_LocaSystem
    For BI system all the connection tests it is giving successful results .
    And in RSPOR_SETUP program , result I found
    Status 9   -   No check with Portal SID <PORTAL_SID>
    Status 10 -   No check with Portal SID <PORTAL_SID>
    Is this 9, 10 properties should be corrected ?
    Thanks and Regards,
    Srini

    Hi,
    The trace file is :
    com.sap.security.core.persistence.imp.PrincipalDatabag Thu Apr 10 13:35:00 AST 2008
    UniqueID: UACC.PRIVATE_DATASOURCE.un:index_service
    Type: UACC
    Home data source: PRIVATE_DATASOURCE
    Private id part: un:index_service
    Principal exists.
    "com.sap.security.core.usermanagement"|->"SecurityPolicy" (no time limit)=
    "com.sap.security.core.usermanagement"|->"lastsuccessfulpasswordcheck" (no time limit)=
    "com.sap.security.core.usermanagement"|->"validfrom" (no time limit)=
    "com.sap.security.core.usermanagement"|->"lastsuccessfullogon" (no time limit)=
    "com.sap.security.core.usermanagement"|->"validto" (no time limit)=
    "com.sap.security.core.usermanagement"|->"ispassworddisabled" (no time limit)=
    "com.sap.security.core.usermanagement"|->"j_user" (no time limit)="index_service"
    "com.sap.security.core.usermanagement"|->"lastpasswordchange" (no time limit)=
    "com.sap.security.core.usermanagement"|->"userid" (no time limit)="USER.PRIVATE_DATASOURCE.un:index_service"
    "com.sap.security.core.usermanagement"|->"previoussuccessfullogon" (no time limit)=
    "com.sap.security.core.usermanagement"|->"lockreason" (no time limit)=
    "com.sap.security.core.usermanagement"|->"lastfailedlogon" (no time limit)=
    "com.sap.security.core.usermanagement"|->"successfullogoncount" (no time limit)=
    "com.sap.security.core.usermanagement"|->"passwordchangerequired" (no time limit)=
    "com.sap.security.core.usermanagement"|->"failedlogonattempts" (no time limit)=
    "com.sap.security.core.usermanagement"|->"islocked" (no time limit)=
    "$serviceUser$"|->"SERVICEUSER_ATTRIBUTE" (no time limit)="IS_SERVICEUSER"
    #1.5 #00144F94DC4800A100000DF600002DBF00044A825E981C1D#1207823700073#com.sap.security.core.imp#sap.com/irj#com.sap.security.core.imp.[cf=com.sap.security.core.imp.AbstractUserAccount][md=constructor][cl=30114]#J2EE_GST_EPD#0####b4e72140030c11ddada100144f94dc48#Thread[ThreadPool.Worker5,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Path##Plain###Exiting method#
    #1.5 #00144F94DC4800A100000DF700002DBF00044A825E983307#1207823700074#com.sap.security.core.imp#sap.com/irj#com.sap.security.core.imp.[cf=com.sap.security.core.imp.AbstractPrincipal][md=getPrincipalDatabagValues][cl=30114]#J2EE_GST_EPD#0####b4e72140030c11ddada100144f94dc48#Thread[ThreadPool.Worker5,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Debug##Java###null
    [EXCEPTION]
    #1#java.lang.Exception: LazyFetch: "UACC.PRIVATE_DATASOURCE.un:index_service"-->"com.sap.security.core.usermanagement","displayname".
         at com.sap.security.core.imp.AbstractPrincipal.getPrincipalDatabagValues(AbstractPrincipal.java:1729)
         at com.sap.security.core.imp.AbstractPrincipal.getAttributeValueString(AbstractPrincipal.java:1782)
         at com.sap.security.core.imp.AbstractUserAccount.getDisplayName(AbstractUserAccount.java:2238)
         at com.sap.security.core.imp.UserAccountWrapper.getDisplayName(UserAccountWrapper.java:509)
         at com.sapportals.portal.security.usermanagement.User50_Impl.getDisplayId(User50_Impl.java:222)
         at sun.reflect.GeneratedMethodAccessor600.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sapportals.portal.security.usermanagement.WrappedUserInvocationHandler.callOtherMethod(ServiceUserFactoryImpl.java:172)
         at com.sapportals.portal.security.usermanagement.WrappedUserInvocationHandler.invoke(ServiceUserFactoryImpl.java:147)
         at $Proxy10.getDisplayId(Unknown Source)
         at com.sapportals.config.fwk.IConfigClientContext.<init>(IConfigClientContext.java:84)
         at com.sapportals.config.fwk.IConfigClientContext.createContext(IConfigClientContext.java:132)
         at com.sapportals.config.fwk.IConfigClientContext.createContext(IConfigClientContext.java:118)
         at com.sap.workflow.cfg.AbstractConfiguration.<init>(AbstractConfiguration.java:279)
         at com.sap.workflow.cfg.SchedulerConfiguration.<init>(SchedulerConfiguration.java:22)
         at com.sap.workflow.es.scheduler.TaskSchedulerDeadline.run(TaskSchedulerDeadline.java:63)
         at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:174)
         at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:108)
         at java.lang.Thread.run(Thread.java:534)
    #1.5 #00144F94DC4800A100000DF800002DBF00044A825E983D07#1207823700081#com.sap.security.core.imp#sap.com/irj#com.sap.security.core.imp.[cf=com.sap.security.core.locking.imp.LockManager][md=escapePrincipalID][cl=30114]#J2EE_GST_EPD#0####b4e72140030c11ddada100144f94dc48#Thread[ThreadPool.Worker5,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Debug##Plain###Mapped principalid for locking: "UACC.PRIVATE_DATASOURCE.un:index_service"-->"000_bTtZDFaWpfKiQ131rUhvSA=="#
    #1.5 #00144F94DC4800A100000DF900002DBF00044A825E985131#1207823700087#com.sap.security.core.imp#sap.com/irj#com.sap.security.core.imp.[cf=com.sap.security.core.locking.imp.LockManager][md=escapePrincipalID][cl=30114]#J2EE_GST_EPD#0####b4e72140030c11ddada100144f94dc48#Thread[ThreadPool.Worker5,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Debug##Plain###Mapped principalid for locking: "UACC.PRIVATE_DATASOURCE.un:index_service"-->"000_bTtZDFaWpfKiQ131rUhvSA=="#
    #1.5 #00144F94DC4800A100000DFA00002DBF00044A825E985A12#1207823700089#com.sap.security.core.imp#sap.com/irj#com.sap.security.core.imp.[cf=com.sap.security.core.locking.imp.LockManager][md=escapePrincipalID][cl=30114]#J2EE_GST_EPD#0####b4e72140030c11ddada100144f94dc48#Thread[ThreadPool.Worker5,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Debug##Plain###Mapped principalid for locking: "USER.PRIVATE_DATASOURCE.un:index_service"-->"000_zCZ7K+TFQWRbSAklTiJDwQ=="#
    #1.5 #00144F94DC4800A100000DFB00002DBF00044A825E98710D#1207823700095#com.sap.security.core.imp#sap.com/irj#com.sap.security.core.imp.[cf=com.sap.security.core.locking.imp.LockManager][md=escapePrincipalID][cl=30114]#J2EE_GST_EPD#0####b4e72140030c11ddada100144f94dc48#Thread[ThreadPool.Worker5,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Debug##Plain###Mapped principalid for locking: "USER.PRIVATE_DATASOURCE.un:index_service"-->"000_zCZ7K+TFQWRbSAklTiJDwQ=="#
    #1.5 #00144F94DC4800A100000DFC00002DBF00044A825E988C3D#1207823700097#com.sap.security.core.imp#sap.com/irj#com.sap.security.core.imp.[cf=com.sap.security.core.imp.AbstractPrincipal][md=getPrincipalDatabagValues][cl=30114]#J2EE_GST_EPD#0####b4e72140030c11ddada100144f94dc48#Thread[ThreadPool.Worker5,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Debug##Java###null
    [EXCEPTION]
    #1#java.lang.Exception: LazyFetch: "USER.PRIVATE_DATASOURCE.un:index_service"-->"com.sap.security.core.usermanagement","description".
         at com.sap.security.core.imp.AbstractPrincipal.getPrincipalDatabagValues(AbstractPrincipal.java:1729)
         at com.sap.security.core.imp.AbstractPrincipal.getAttributeValueString(AbstractPrincipal.java:1782)
         at com.sap.security.core.imp.AbstractPrincipal.getDescription(AbstractPrincipal.java:667)
         at com.sap.security.core.imp.AbstractPrincipal.getAttribute(AbstractPrincipal.java:309)
         at com.sap.security.core.imp.User.getAttribute(User.java:1006)
         at com.sap.security.core.imp.UserWrapper.getAttribute(UserWrapper.java:321)
         at com.sapportals.portal.security.usermanagement.User50_Impl.getValuesForKey(User50_Impl.java:760)
         at com.sapportals.portal.security.usermanagement.User50_Impl.getDescription(User50_Impl.java:474)
         at sun.reflect.GeneratedMethodAccessor601.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sapportals.portal.security.usermanagement.WrappedUserInvocationHandler.callOtherMethod(ServiceUserFactoryImpl.java:172)
         at com.sapportals.portal.security.usermanagement.WrappedUserInvocationHandler.invoke(ServiceUserFactoryImpl.java:147)
         at $Proxy10.getDescription(Unknown Source)
         at com.sapportals.config.fwk.IConfigClientContext.<init>(IConfigClientContext.java:87)
         at com.sapportals.config.fwk.IConfigClientContext.createContext(IConfigClientContext.java:132)
         at com.sapportals.config.fwk.IConfigClientContext.createContext(IConfigClientContext.java:118)
         at com.sap.workflow.cfg.AbstractConfiguration.<init>(AbstractConfiguration.java:279)
         at com.sap.workflow.cfg.SchedulerConfiguration.<init>(SchedulerConfiguration.java:22)
         at com.sap.workflow.es.scheduler.TaskSchedulerDeadline.run(TaskSchedulerDeadline.java:63)
         at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:174)
         at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:108)
         at java.lang.Thread.run(Thread.java:534)
    any suggestions ?????

  • Crystal report PLD giving dump error during preview

    Hi,
    I have developed a Crystal report PLD for A/R Credit Memo (RIN1). It is working perfectly while running from Crystal report interface. After importing the same from Report and Layout Manager in SAP, while trying to view the preview it is giving dump error. Can anyone help me out in this regards.
    Thanks in advance.

    Hi,
    Check SAP note:
    1562837 - Previewing/printing some Crystal Reports layouts crashes
    B1
    Thanks & Regards,
    Nagarajan

  • MDG Material BS_MAT_OVP_03 application is fine in development but giving runtime errors when moved to quality

    Dear Experts,
    We are Facing a problem with BS_MAT_OVP_03, We have done some enhancements and it is working very much fine in development and when we move it to Quality we are getting runtime errors, they are not with the enhancements but with in standard code itself.
    "ASSERTION_FAILED" " ""CL_USMD_ACC_FLD_PROP_DATA=====CP" or "CL_USMD_ACC_FLD_PROP_DATA=====CM009" "VALIDATE_RETURNED_FLD_PROP"
    we are getting above runtime error, Please let us know the reason for issue, If some one have come across.
    Regards
    Sukumar

    Hi Sukumar,
    It's because of few generated structures could be in "Inactive" mode for your data model when you move to quality system.
    Refer each generated structure from SE11 and activate them individually..this can be a post processing activity everytime you move data model structures from one ECC to other ECC.
    Thanks
    Praveen

  • F-44 giving runtime error as  BCD_FIELD_OVERFLOW

    Dear All,
    I have checked end user system regarding the runtime error as  Runtime Errors         BCD_FIELD_OVERFLOW
    Exception              CX_SY_CONVERSION_OVERFLOW
    Date and Time          04.04.2011 11:44:22
    Actually user i has tried F-44 and mentioned Account and Additional selectios as None in F-44.
    finally user got ABAP runtime error as below .
    Runtime Errors         BCD_FIELD_OVERFLOW
    Exception              CX_SY_CONVERSION_OVERFLOW
    Date and Time          04.04.2011 11:44:22
    Short text
         A calculation field is defined too small.
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPMF05B" 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.
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
         caught in
        procedure "POSTAB_REBZG_COLLECT" "(FORM)", nor was it propagated by a RAISING
         clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        A value generated during processing is too large for the
        field "<POS>-PPIDX" of the program "SAPMF05B".

    How to correct the error
        It may be possible to divide the current process into
        smaller units, so that only smaller values occur.
        Otherwise, as a long-term solution, define the field "<POS>-PPIDX"
        larger.
        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:
        "BCD_FIELD_OVERFLOW" "CX_SY_CONVERSION_OVERFLOW"
        "SAPMF05B" or "MF05BF01_POSTAB_REBZG_COLLECT"
        "POSTAB_REBZG_COLLECT"
    System environment
        SAP-Release 700
        Application server... "PRDCIXI"
        Network address...... "10.54.145.32"
        Operating system..... "AIX"
        Release.............. "5.3"
        Hardware type........ "000184CAD400"
        Character length.... 16 Bits
        Pointer length....... 64 Bits
        Work process number.. 4
        Shortdump setting.... "full"
        Database server... "PRODORADB"
        Database type..... "ORACLE"
        Database name..... "IRP"
        Database user ID.. "SAPSR3"
    Client.............. 320
    User................ "SA_A054"
    Language key........ "E"
    Transaction......... "FB1K "
    Transactions ID..... "4D9953D749560108E10080000A369120"
    Program............. "SAPMF05B"
    Screen.............. "SAPMF05A 0131"
    Screen line......... 72

  • Class Inside MovieClip Giving Runtime Error

    Hey guys.
    I'm trying to place an instance of a movieclip (instance
    name: tehMovieClip) from the library within another movieclip
    (instance name: parentMovieClip) on the stage. tehMovieClip, the
    movieclip going inside another movieclip, belongs to a class called
    CollisonDetection (linkage properties, class:CollisonDetection,
    Base Class: flash.display.MovieClip). When I put tehMovieClip
    inside parentMovieClip, I get this runtime error:
    TypeError: Error #1009: Cannot access a property or method of
    a null object reference.
    If I just place tehMovieClip on the stage by itself, it works
    fine but I need it to be inside parentMovieClip. So what should I
    do?
    Just for your information, CollisonDetection extends the
    project's DocumentClass which extends MovieClip.
    Thanks in advanced!

    Thanks for that buddy.
    quote:
    Originally posted by:
    SwapnilVJ
    Is the movie clip your are placing linked from library to a
    class?
    The movieclip in question (the one I am placing inside
    another movieclip) is linked to a class.
    quote:
    Originally posted by:
    SwapnilVJ
    If yes. Is the Class linked to the movieclip have a
    Constructor method with parameters?
    Well this is my current constructor:
    public function CollisonDetection() {
    playerRefFromCollisonDetection.x = 600;
    Now that you've said that, I deleted that middle line and it
    seemed to work
    quote:
    Originally posted by:
    SwapnilVJ
    If Yes. you found the problem.
    And solution will be to update the class' constructor to have
    no parameters.
    Thanks buddy, but what if I need to have statements inside
    the constructor such as triggering methods/functions inside the
    class?

  • KCLJ giving runtime error

    Hi Experts,
    I am using KCLJ to transfer file data into SAP system through BDT Direct input. I am doing this in Incentive Commission Management system.
    I created a sender structure for Commission contract bundle and used this in KCLJ transaction.
    But when I am executing the KCLJ transaction I am getting a Runtime error. The Error says that the program could not execute because one of the statements could not be executed.
    The Sender structure program is automatically getting generated when i execute the transaction KCLJ with corresponding sender structure. So the program which got generated for this contains syntax errors.
    Have you ever experienced any such issues?
    Please let me know how to solve this issue?
    Thanks & Regards,
    Sreejith A P

    Hi ,
    Can you give me more details about the syntax error.
    Also let me know which release you are in?
    Regards,
    Singa

Maybe you are looking for