"TSV_TNEW_PAGE_ALLOC_FAILED" errors

Our SAP system always gets the "TSV_TNEW_PAGE_ALLOC_FAILED" errors,
It has 16 GB physical memory and its em/initial_size_MB is 13.87 GB and its ztta/roll_extension isztta/roll_extension 2.79 GB.
I want to know where these errors come from :
(1)Our overall Extended Memory (em/initial_size_MB) is not large enough ?
(2)Or our overall Extended Memory is OK but ztta/roll_extension is too small ?
Please help me how to find out the root cause of this error.
Thank you very much.

is this dump for standard SAP or locally developed program? also check whether user ran report without any selection parameters? is this dump occurring frequently?
cheers,
-Sunil

Similar Messages

TSV_TNEW_PAGE_ALLOC_FAILED Error in Mass Update of Alternative Hierarchies

Hi Experts,
I am updating Cost Centers in the alternative nodes by calling a standard Program
PERFORM hierarchy_generate IN PROGRAM saplkkhi.
All these Entries are coming from a file having a Cost Center and respective hierarchies
under which it should be updated.
Suppose in a file a Cost Center was attached to one node and if it needds to be detached
in to another node within same common node i am using a Function Module K_HIERARCHY_UPDATE
to update the cost center under given node.For all these Process i have created a Z Function
Module.
A report is executed in background which calls the above FM and was supposed to display all
the Cost Centers and Hierarchies attached.
Unfortunately I am getting TSV_TNEW_PAGE_ALLOC_FAILED Error even when i am Processing the
Report in Background.
Please help me solving this Issue.
Regards
Manjari Patankar

As an addition to the answer from Siegfried.
Very often SAP application developers define internal buffering tables (in ABAP) to store some information for the fast access. Initialization of these tables are normally programmed in some function modules that are called in certain scenarios. However I have seen the cases where initialization was not intended at all. Developers motivated it with the fact that corresponding functions are not designed to call them in batch many times or with large data volumes.
If such kind of initialization does not happen, you are going to have memory issues.
I would proceed as follows:
1. Run your job in foreground
2. In SM50/SM66 monitor the memory consumption of the work process.
3. When it goes high, debug the work process from SM50/SM66.
4. Being in debugger, look at the memory areas and find out objects that occupy a lot of memory.
5. Display these objects (normally internal tables) in ABAP editor and use "where used list" to find the places where they are initialized.
6. Try to call initialization functions/subroutines in your coding after each data package and subsequent commit work and wait.

TSV_TNEW_PAGE_ALLOC_FAILED error while executing FAGLL03

Dear Experts,
We are on AIX, Oracle 10g and ECC 6.0
One of our FI consultant is trying to execute a report using the standard T-Code: FAGLL03 for a range of 1 year, but when she executes this she gets the following dump (runtime error)
TSV_TNEW_PAGE_ALLOC_FAILED
So on working on this error i found that we need to set few abap parameters, for which i have done the following parameter settings..
rsdb/ntab/ftabsize 41000
Previous Value: 30000
rsdb/ntab/entrycount 25000
Previous Value:20000
abap/buffersize 900000
Previous Value: 400000
rsdb/cua/buffersize 9000
Previous Value: 5000
zcsa/presentation_buffer_area 8388608
Previous Value:8388608
zcsa/table_buffer_area 41943040
Previous Value:41943040
rtbb/buffer_length 25000
Previous Value:20000
rsdb/obj/buffersize 25000
Previous Value: 4096
abap/heap_area_dia: 3000000000
Previous Value: 2000000000
abap/heap_area_nondia: 0
Previous Value: 2000000000
abap/heap_area_total: 5000000000
Previous Value: 2000000000
After doing these chnages and there was a problem restarting the server, and then i made changes to the abap/buffersize parameter from 900000 to 600000 and then 500000 but the server never restarted.
So finally i have copied the instance profile which was earlier backed up back into the profile folder and the restarted the server which is working fine now.
Now my question is can any one plese help with the best settings so that i can resolve the FI issue and restart my server without any problems.
Reward points for sure.
Awaiting for your quick reply
Thanks in Advance
Regards
Harry

Hi,
I suggest you to follow below SAP Notes:
#146289   Parameter recommendations for 64-bits SAP Kernel
#425207   SAP memory management, current parameter ranges
#153641   Swap Space requirement for R.3 64-bits kernel
you should have at least 20GB swap space configured, at least 8GB RAM configured
On heap parameter:
      abap/heap_area_nondia: 0
      Previous Value: 2000000000
why you configure zero ? please maintain at 2GB
abap/buffersize is a very sensitve parameter. simply increasing it will end up in system emergency mode with PXA shared memory dump.
if you are running windows, then please activate ZAMM.
If you are running AIX, i suggest you to look into SAP Note 789477.
cheers,
Vincent

TSV_TNEW_PAGE_ALLOC_FAILED Error

Dear Experts,
I have received multiple short dump Like "TSV_TNEW_PAGE_ALLOC_FAILED" in weekly twice
Server : Sun solaris/Oracle 10g- 64 Bit, 32GB Ram, SAP NetWeaver 2004s
one CI+DB and 3 APP servers.
When I checked Work process level it says
A Tue Aug 10 19:35:56 2010
A WP has reached abap/heaplimit = 40894464 bytes
A
A Tue Aug 10 19:41:14 2010
A *** ERROR => User XXXXXXX   reached avail. heapsize = 2045 MB: see ST22 [abstor.c     1779]
A *** ERROR => Increase abap/heap_area_total [abstor.c     1780]
A *** ERROR => heap memory WP0: 1936 MB [abstor.c     1784]
A *** ERROR => heap memory WP1: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP2: 109 MB [abstor.c     1784]
A *** ERROR => heap memory WP3: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP4: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP5: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP6: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP7: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP8: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP9: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP10: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP11: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP12: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP13: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP14: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP15: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP16: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP17: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP18: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP19: 0 MB [abstor.c     1784]
A *** ERROR => heap memory WP20: 0 MB [abstor.c     1784]
My Instance profile value is like
abap/heap_area_dia                          2145386496
abap/heap_area_nondia                       2145386496
abap/heap_area_total                        2145386496
abap/heaplimit                              40894464
em/initial_size_MB                          4092
Please let me know how to fix this issue, we are getting the same kind of dump for the last one year.. I have 32 GB, Can I increase the value to double the size of the above values. Already red the 425207 regarding this.
If i double the size of my above value, will my handle the load.. ?
Thanks
Malai

Dear Ananda,
yes, O I think so..
I am not sure what the user exactly doing, this the log from St22.
St22 -> error-> No more storage space available for extending an internal table.
It terminated at Line 78
Information on where terminated
    Termination occurred in the ABAP program "CL_RSBOLAP_QV_RESULT_SET======CP" -
     in "EXECUTE".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 78
    of the (Include) program "CL_RSBOLAP_QV_RESULT_SET======CM002".
Here I attached my code in line no 78
IF   o_r_query_view->n_s_rs_state_change-all = rs_c_true
        OR o_r_query_view->n_s_rs_state_change-text_rows = rs_c_true
        OR i_t_char_details IS NOT INITIAL.
        CALL METHOD get_texts
          CHANGING
            c_sx_axis = n_sx_rows.
      ENDIF.
      IF o_r_query_view->n_s_rs_state_change-all = rs_c_true.
1*   Use the texts from the text class
        p_th_text = cl_rsdm_read_master_data=>n_th_txt_n.
        GET REFERENCE OF p_th_text INTO n_r_text.
      ELSEIF o_r_query_view->n_s_rs_state_change-text_rows = rs_c_true
        OR o_r_query_view->n_s_rs_state_change-text_columns = rs_c_true
        OR i_t_char_details IS NOT INITIAL.
2*   Transfer the single texts (because the texts from the other axis might be missing otherwise)
        LOOP AT cl_rsdm_read_master_data=>n_th_txt_n INTO l_s_txt_n.
          INSERT l_s_txt_n INTO TABLE p_th_text.
          IF sy-subrc <> 0.
            MODIFY TABLE p_th_text FROM l_s_txt_n.
          ENDIF.
        ENDLOOP.
        GET REFERENCE OF p_th_text INTO n_r_text.
      ENDIF.
3* Rollup date and time
      o_r_query_view->n_r_olap->get_topicality_time( IMPORTING e_timestmp_min = l_min_time
                                              e_timestmp_max = l_max_time ).
When I double click line 77      I found that above on my system.
I am not sure This could be a Routine in internal tables or not..
Please advice.
Thanks
Malai

TSV_TNEW_PAGE_ALLOC_FAILED - error -Short Dump - Storage Problems

Dear Gurus,
I am new at SAP Basis, can you please help with the following;
One of our FI System Analyst is running a FI report that gives the followin error:
ABAP runtime errors    TSV_TNEW_PAGE_ALLOC_FAILED
       Occurred on     30.04.2008 at 11:11:14
>> Short dump has not been completely stored. It is too big.
Please help

Is the report a standart report or a custom one?
If custom, then the report might be using too much memory. You have to look into the report to optmize it.

TSV_TNEW_PAGE_ALLOC_FAILED error while loading the DATA using DTP

Hi,
While loading the data using DTP for 2 DSO's we are gettig the error
TSV_TNEW_PAGE_ALLOC_FAILED
can any one kindly help me out regarding the same.
Thank You,
Poornima.

Hi Soundarya,
Thanks a lot for the reply. But i found that its running fine in development, where as coming to quality its throwing an error. These happened for Two DSO's. In both the transformations i have identified that the Transformation names are different from Development and Quality..
There are no routines written for them and no select statements have been used
Can you please suggest me regarding the same.
Edited by: Poornima Gayatri on Mar 22, 2010 7:00 AM

TSV_TNEW_PAGE_ALLOC_FAILED error in FM CRM_TERRMAN_SINGLE_READ_BUFFER

Hi All,
I would just like to know if there is a SAP Note that can resolve the error TSV_TNEW_PAGE_ALLOC_FAILED that we are encountering in our system.
I have found one sap note 791726 which is for BBPCRM 4.0 but is not anymore applicable in our systems because it is now running with BBPCRM 5.0 with support pack 12.
I have also checked this note and i found out that the corrections within this note is not visible in our current system.
Can I still implement this sap note even if (technically) it is on a lower support pack? Or is there an OSS note similar to 791726 that is valid from version BBPCRM 5.0 with support pack 12.
Thank you in advance for all your support.
Regards,
Ranilo

As an addition to the answer from Siegfried.
Very often SAP application developers define internal buffering tables (in ABAP) to store some information for the fast access. Initialization of these tables are normally programmed in some function modules that are called in certain scenarios. However I have seen the cases where initialization was not intended at all. Developers motivated it with the fact that corresponding functions are not designed to call them in batch many times or with large data volumes.
If such kind of initialization does not happen, you are going to have memory issues.
I would proceed as follows:
1. Run your job in foreground
2. In SM50/SM66 monitor the memory consumption of the work process.
3. When it goes high, debug the work process from SM50/SM66.
4. Being in debugger, look at the memory areas and find out objects that occupy a lot of memory.
5. Display these objects (normally internal tables) in ABAP editor and use "where used list" to find the places where they are initialized.
6. Try to call initialization functions/subroutines in your coding after each data package and subsequent commit work and wait.

TSV_TNEW_PAGE_ALLOC_FAILED error while executing the report

Hi all,
. We are having an info cubeXFIAP_C12 (FIAP: Vendor Line Item Open).In which we have defined 10 Dimensions and 6 Line Item Dimensions. We have created a report on this with Key date as Input Variable Which gives me From Start to Till Date data. Also have an Variable on company code.
Then No of Records in my Cube is 45, 70,624.Compressed the Info Cube data .But No aggregates on it.
Now when I provide the key date as 30.06.2011 and Company code =XYZ.
I am unable to Execute the Report, It gives me a short Dump. Saying NO ROLL MEMORY.
Variables:
1. Key Date: Is a Customer Exit variable .If user Enters Data as 30.06.2011 ,It fetches data from u201C00000000u201D to u201C30.06.2011u201D.
2.Company code: Is a Manual Entry /Default variable.
I also have shot dump.Please find the error analysis of dump below:
The internal table "\FUNCTION-POOL=RRK0\FORM=MEGA_SORT_M\DATA=C_TSX_SORTK[2]-GT
ABIX[1]-GTABIX" 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: 4
Number of rows: 1503307
Allocated rows: 1503307
Newly requested rows: 2048 (in 1 blocks)
can any one help me .......
Regards
Laxman

Hi,
Just check following things
1http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCSTMM/BCCSTMM.pdf
2. See whether any back up process is happening and it has consumed the main memory.
3. Are you getting this error regularly
4. See any transport went and compression/aggregation got removed.
5. Check whether there are many dumps in ST22 same time when you execute report
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/4ab89e84-0d01-0010-cda2-82ddc3548c65?QuickLink=index&overridelayout=true
6. http://www.sap-press.de/download/dateien/1049/sappress_bw_performance_optimization_guide_080.pdf
7. Check whether Infoprovifder got removed from BIA
8. Query removed from BIA post transport
9. Run RSRT and regenerate the report.
Thanks and regards
Kiran

TSV_TNEW_PAGE_ALLOC_FAILED Error in VF04 tcode

Hi Guru's
When I am executing T-code VF04 (SDBILLDL) with Input value,I am getting dump of " TSV_TNEW_PAGE_ALLOC_FAILED alon with the short Text " No more storage space available for extending an internal table."
Is it has any SAP notes for solving this problem.???
Regards
P.Senthil Kumar

Hi Volker Binder,
We unable to inform basis people to extend memory space in our system without giving any proper notes..
i want to give detailed solution for this then only basis people extend the memory space..
is it has any sap notes for solving this issue..
Regards
P.Senthil Kumar

TSV_TNEW_PAGE_ALLOC_FAILED error in report

Hi Experts,
I am trying to run a report which will retrieve the Active BPs for a particular product Id in CRM environment.
I am trying to run the report on development in background mode.
It is being canceled out and TSV_TNEW_PAGE_ALLOC_FAILED is a DUMP I'm getting several times.
There is chance for selecting a large amount of data.
Please guide me how to resolve the issue.
Regards

Hi,
For background processing you need to got sm36 and schedule job. I think the problem occurs in function module. it means new page allocation is failed for the business partner. so it is retriving more than one page active Business partner for the product id.
thanks
Hemant

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.

BPC 7.5 NW - Error Object variable or With block variable not set ?

Hi, we have BPC 7.5 NW SP07.
I am getting an error "object variable or with block variable not set" while trying to submit data through an Input schedule
I went to the Excel Options --> Add-Ins --> COM Add-ins, disable and enable but not working.
I look in ST22 some errors:
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
TSV_TNEW_PAGE_ALLOC_FAILED
Error was initial in last days.
Any idea ?

Hi Vitoto,
The problem is not with BPC Excel, but with Memory. I think there is no sufficient memory available in your system.
Please check SAP Notes 20527 & 369726 for the dump that you are getting in ST22.
Regards,
Raghu

TSV_TNEW_PAGE_ALLOC_FAILED in source system

Hello all,
when executing rsa3 for datasource 0activity_attr and 0activity_text system dumps with the TSV_TNEW_PAGE_ALLOC_FAILED error, this also occurs when loading in background from BW. We have a identical system and on this system it does work.. We've already compared settings between the systems.
Already tried the following:
- Memory and table space settings are checked and optimized --> no result
- Tried rsa3 with minimum selection --> no result
- No relevant notes found (system is up to date with sp's)
- Searched sdn & service.sap.com
- Reactivated datasource from business content
When checking on database level, no errors occur, so it does not seem to be a table space error. Memory is extended and memory settings are checked (there is even more memory compared to the system where it does work...)
Anybody got an idea how to fix this issue?
Kind regards,
Immanuel

Hi Vikram,
extended & heap memory settings are checked and optimized by our basis team. The settings are even set better then on the system where the extration does work. Systems dumps on the following code:
221   LD_BLOCKING_INDEX_MIN = 1.
222   LD_BLOCKING_INDEX_MAX = GDC_BLOCK_FACTOR.
223   DO LD_BLOCKS TIMES.
224     REFRESH L_R_AUFPL_BLOCK.
225     APPEND LINES OF L_R_AUFPL_PART FROM LD_BLOCKING_INDEX_MIN
226                                      TO LD_BLOCKING_INDEX_MAX
227                  TO L_R_AUFPL_BLOCK.
228     IF ID_OBJTYPE = 'NV'.         "Network activity
229        SELECT (LT_AFVC_FIELDS)
230                   FROM AFVC
231             APPENDING CORRESPONDING FIELDS OF TABLE <fs_afvc>
232                   WHERE AUFPL IN L_R_AUFPL_BLOCK
233                   AND SUMNR = '0'
234                   AND (LR_WHERE-WHERE_TAB).
235      ELSEIF ID_OBJTYPE = 'NE'.    "Network activity element
236         SELECT (LT_AFVC_FIELDS)
237                   FROM AFVC
238             APPENDING CORRESPONDING FIELDS OF TABLE <fs_afvc>
239                   WHERE AUFPL IN L_R_AUFPL_BLOCK
240                   AND SUMNR <> '0'
241                   AND (LR_WHERE-WHERE_TAB).
242     ENDIF.
AFVC has nearly the same number of records in both systems ( > 9000000),
Kind regards,
Immanuel
Edited by: Immanuel Verdaasdonk on Mar 10, 2010 11:27 AM

TSV_TNEW_PAGE_ALLOC_FAILED Short Dump

Hi
I am scheduling a Setup tables job in background to fill setup table but i am getting a short dump with TSV_TNEW_PAGE_ALLOC_FAILED error
any ideas on how can i fix it
Thanks in advance

The error TSV_NEW_PAGE_ALLOC_FAILED means that more memory was requested by the system because the program needed to expand an internal table, but not is available. When Extended Memory is completely used up, the process will go into PRIV mode and it will start using Heap Memory in case of Windows or vice versa in case of Unix. Once this enters into PRIV mode, no other user will be able to use the corresponding work process. If there is enough memory for it to finish, You will not see the error.
Note: Internal table can store max of 2GB data.
Please refer the following SAP notes:
SAP Note 649327 Analysis of memory consumption.
SAP Note 20527 Runtime error TSV_TNEW_PAGE_ALLOC_FAILED
SAP Note 185185 Application: Analysis of memory bottlenecks
SAP Note 369726 TSV_TNEW_PAGE_ALLOC_FAILED
What can you do?
1) Process smaller chunks of data. (E.g. not all 50.000 records at once) is one option.
2) Create a memory snapshot right before the program dumps and analyze where the memory is consumed in order to understand if or where you can reduce memory consumption.

TSV_TNEW_PAGE_ALLOC_FAILED dump

HI ,
The user is getting the TSV_TNEW_PAGE_ALLOC_FAILED error while running a some job
The amount of storage space (in bytes) filled at termination
Roll area...................... 6221072
Extended memory (EM)........... 2002738624
Assigned memory (HEAP)......... 3000059984
Short area..................... " "
Paging area.................... 32768
Maximum address space.......... 4294967295
he is getting this error while executing when ever he runs that job

It is a z job of some archiving for PP_Order
For this user only we are getting this error for that perticular job.
The systme is ECC 6.0 Ehp6 oracle database .
SAP kernel....... 720
Memory consumption is
Roll.... 6221072
EM...... 2002738624
Heap.... 3000059984
Page.... 32768
MM Used. 4737199616
MM Free. 254668992
These are the current peremeters which were configured
abap/buffersize               2000000
em/initial_size_MB      40960http://
ztta/roll_extension      2000000000
ztta/roll_area                7000000
abap/heap_area_nondia         3000000000
in our system.
================
Category               Resource Shortage
Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time          05.08.2014 16:44:40
|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-POOL=SCD5\DATA=DATA_TAB_POS" 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: 1568                                                                               |
|    Number of rows: 424196                                                                        |
|    Allocated rows: 424196                                                                        |
|    Newly requested rows: 8 (in 1 blocks)                                                         |
|How to correct the error                                                                          |
|    The amount of storage space (in bytes) filled at termination time was:                        |
|                                                                                                  |
|    Roll area...................... 6221072                                                       |
|    Extended memory (EM)........... 2002738624                                                    |
|    Assigned memory (HEAP)......... 3000059984                                                    |
|    Short area..................... " "                                                           |
|    Paging area.................... 32768                                                         |
|    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

"TSV_TNEW_PAGE_ALLOC_FAILED" errors

Similar Messages

Maybe you are looking for