Dump: Internal session terminated with a run time error TSV_TNEW_PAGE_ALLOC_FAILED (see ST22)

[Former Member]

Hi Experts,

I am geting  runtime error TSV_TNEW_PAGE_ALLOC_FAILED  in DEV system.

Short text

    No more storage space available for extending an internal table.

Information on where terminated

    Termination occurred in the ABAP program "******" -in "FILL_*****".

    The main program was "****** ".

    In the source code you have the termination point in line 2 of the (Include) program "Z*****".

    The program "Z*****" was started as a background job.

    Job Name....... "BIDTPR_45130_1"

    Job Initiator.. "BW-BATCH"

    Job Number..... 14032400

and the line number 21 contains the Select statement which is executed successfully for other loads.

Error analysis

    The internal table "{O:718*\CLASS=ZCL_ROYALTY_DATA_PROCESSING}\DATA=GT_GBL_REP_PROJ" 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: 442

    Number of rows: 17500540

    Allocated rows: 17500540

    Newly requested rows: 32 (in 1 blocks).

I have also deleted some files form server and after that loading one file at a time ,then also facing same issue in  step -DTP of the process Chain.

I have followed some discussion like but that was marked as not answered.

Please help me to resolved this issue.

Thanks ,

Tulika

[Former Member · Accepted solution]

Hi All,

Thanks for response.

I had solve the issue by following below links:-

• wiki.scn.sap.com/wiki/display/BI/There+is+a+TSV_TNEW_PAGE_ALLOC_FAILED+Dump+When+Using+Planning+Functions

• www.sap-perf.ca/trouble-shoot-sap-program-termination-on-memory-error/

It is a basis issue.

If any one face this issue just send a mail to your basis team "No more storage space available for Extending an internal table".

Thanks & Regards,

Tulika

[Former Member]

Hello Tulika,

When there are huge number of data records being pulled from source , then we wil lface the error

"TSV_TNEW_PAGE_ALLOC_FAILED".

Actions to be taken:

1. If the data load is delta, after deleting the red reuqest from target, go to change mode of DTP, Increase the number of processess on DTP level  from 1 to 2..(usually the no of processes will be 1). Save, Activate.

2. Trigger the load again.

3. If possible, the load can be splitted based on the selection parameters.

4, If you are facing the issue on BEx Level, then if it is the case where you have to display whole year data, then try to display the data monthly/quartley wise..in case, if it is not possible to filter in Fisc.Year Period in selection screen, you have to make changes in the query designer for 'Fisc.Year Period".

Thanks

Asha

[Former Member]

Hi,

Please try by changing the data packet size and load the data.

If it fails again, then change the data packet size again into low and retry the load.

Hope the load will success.

Thanks,

Phani.

[former_member182196]

Hi check this sap note this will help you  to resolve this issue.

See Note 928044

The reason is behind this issue is From BW Release 7.0 onwards the BW lock server is used in BW Integrated Planning and in Business Planning and Simulation. The BW lock server uses the shared objects memory area of an application server to store the lock table. You must ensure that the size of the lock table is not exceeded during system operation otherwise terminations such as the TSV_TNEW_PAGE_ALLOC_FAILED dump will occur.

[jaigupta]

Hi Tulika,

As the error points out, when running a DTP there might be some code in your transformtion whih is referring to ABAP class ZCL_ROYALTY_DATA_PROCESSING, in this class you have an internal table where you must be storing your data, the no of records that you are storing in the table would be exceeding the maximum limit allowed and hence you are recieving this error.

For resolving this issue you can refer any of the choices given by Vipin.

Regards,

Jai

[former_member229708]

Hi Tulika,

This Short Dump mainly comes because of Low memory in CPU.

Refer to following points also:

  - Number of records in your action. If it is huge, try to split in batches.

  - Check with your basis team about CPU utilization, when you are performing this activity.

Thanks & Regards,

Vipin

[RamanKorrapati]

Hi,

Actually what action you performed?

are you running nany bex report? if yes then better to run your report with small selections. seems like your target may have huge data.

Thanks