ABAP Dump : TSV_TNEW_PAGE_ALLOC_FAILED in program SAPLCOM_PARTNER_OB

[Former Member]

Hi All,

I am getting the dump TSV_TNEW_PAGE_ALLOC_FAILED in program SAPLCOM_PARTNER_OB in LCOM_PARTNER_OB in line 165.

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.

The error is occuring in line

INSERT GS_CURRENT_PARTNERSET INTO TABLE GT_PARTNERSETS.

CT_PARTNER[] = GS_CURRENT_PARTNERSET-PARTNER[]. "#EC ENHOK

ENDIF.

The amount of storage space (in bytes) filled at termination time was:

Roll area...................... 6221152

Extended memory (EM)........... 3909511400

Assigned memory (HEAP)......... 2000692032

Short area..................... " "

Paging area.................... 417792

Maximum address space.......... 18446697117078316543

The dump is occuring in the standard program. Is there any note for this.

Kindly help.

Thanks,

[markus_doehr2 · Accepted solution]

> I am getting the dump TSV_TNEW_PAGE_ALLOC_FAILED in program SAPLCOM_PARTNER_OB in LCOM_PARTNER_OB in line 165.

> Extended memory (EM)........... 3909511400

> Assigned memory (HEAP)......... 2000692032

> The dump is occuring in the standard program. Is there any note for this.

Did you try a notes search?

This program is already using roughly 6 GB of RAM which seems quite a lot.

What transaction/process is triggering this error? It may be that a user just selects too much data.

Markus

[Former Member · Accepted solution]

I agree with Markus's comment.

Your program is definately using 6GB of memory already and that is already on the higher side.

Best solution recommended is that Data needs to be limited.

Increasing extended memory is also another solution but not a right one.

Further to avoid any memory bottlenecy you Basis admin should be bringing down value of parameter

ztta/roll_extension to may be 300~650 MB so that a single process should not use most of the extended memory.

P.S : You Basis admin can give actual value for above parameter based on available memory

Cheers !

Manish

[former_member197561]

Hi,

You can as well do a basic check for memory leak - execute the scenario several times and either take memory snapshots and compare with Memory Inspector or just look at transaction STAD and see how the memory usage is. If it is constantly growing, then you can suspect a memory leak. If there is memory leak then the tuning (increasing) of memory areas would only help temporarily.

Best Regards,

Sylvia

[former_member189546]

Hello,

Problem maybe on the application side ie CRM

What application are you using what t/s selection etc

Try to reduce your selection criteria

regards,

John Feely

[former_member184548]

Hello

Are you facing the problem for only one your one task. If your other programs are working fine then probably you need to look into the particulat program and the variant which you are trying to use,

It is not recommended to change the heap parameter size to get rid on single program

Thanks

Atul

[Former Member]

Hi ,

thanks for the reply. I tried searching the notes but i couldn't find one.

[markus_doehr2]

Ok.

But do you know what trigers that error? Username? Did you talk to the user?

The error means that you reached the system configured maximum memory for a transaction. This is not a SAP problem but a problem what is being selected.

Markus