TSV_TNEW_BLOCKS_NO_ROLL_MEMORY

[Former Member]

Hi Experts,

In BW Production system have one issue.

I have 3 Infospoke files which is taking the data from DSO to some .CSV File in G drive.But this is the first time i am getting this Runtime error

i have pasted the below runtime error in ST22.

Full points will be assigned.Appreciate your help.

********************************************************************************************************

Runtime Errors TSV_TNEW_BLOCKS_NO_ROLL_MEMORY

Date and Time 22.10.2011 17:46:05

-

---

-

---

Short text

No roll storage space of length 1398800 available for internal storage.

-

---

-

---

What happened?

Each transaction requires some main memory space to process

application data. If the operating system cannot provide any more

space, the transaction is terminated.

-

---

-

---

What can you do?

Try to find out (e.g. by targetted data selection) whether the

transaction will run with less main memory.

If there is a temporary bottleneck, execute the transaction again.

-

If the error persists, ask your system administrator to check the

following profile parameters:

o ztta/roll_area (1.000.000 - 15.000.000)

Classic roll area per user and internal mode

usual amount of roll area per user and internal mode

o ztta/roll_extension (10.000.000 - 500.000.000)

Amount of memory per user in extended memory (EM)

o abap/heap_area_total (100.000.000 - 1.500.000.000)

Amount of memory (malloc) for all users of an application

server. If several background processes are running on

one server, temporary bottlenecks may occur.

Of course, the amount of memory (in bytes) must also be

available on the machine (main memory or file system swap).

Caution:

The operating system must be set up so that there is also

enough memory for each process. Usually, the maximum address

space is too small.

Ask your hardware manufacturer or your competence center

about this.

In this case, consult your hardware vendor

abap/heap_area_dia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each dialog process.

Parameters for background processes:

abap/heap_area_nondia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each background process.

Other memory-relevant parameters are:

em/initial_size_MB: (35-1200)

Extended memory area from which all users of an

application server can satisfy their memory requirement.

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

-

---

-

---

Error analysis

The internal table "\CLASS=ZCL_IM_Z_DG8_ESTREAD_WEEKL\METHOD=IF_EX_OPENHUB_TRAN

SFORM~TRANSFORM\DATA=LT_EQUI" could not be enlarged further.

Memory location: "Session memory"

You attempted to extend the data structure for the management of the

memory blocks for table "\CLASS=ZCL_IM_Z_DG8_ESTREAD_WEEKL\METHOD=IF_EX_OPENHUB

TRANSFORM~TRANSFORM\DATA=LTEQUI". However, the 1398800 bytes required for

this were no longer available in the specified memory area.

The amount of memory requested is no longer available.

-

---

-

---

How to correct the error

Try to decide by analysis whether this request is

reasonable or whether there is a program error. You should pay

particular attention to the internal table entries listed below.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"TSV_TNEW_BLOCKS_NO_ROLL_MEMORY" " "

"ZCL_IM_Z_DG8_ESTREAD_WEEKL====CP" or "ZCL_IM_Z_DG8_ESTREAD_WEEKL====CM001"

"IF_EX_OPENHUB_TRANSFORM~TRANSFORM"

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.

-

---

-

---

Information on where terminated

Termination occurred in the ABAP program "ZCL_IM_Z_DG8_ESTREAD_WEEKL====CP" -

in "IF_EX_OPENHUB_TRANSFORM~TRANSFORM".

The main program was "RSBSPOKE2 ".

In the source code you have the termination point in line 230

of the (Include) program "ZCL_IM_Z_DG8_ESTREAD_WEEKL====CM001".

The program "ZCL_IM_Z_DG8_ESTREAD_WEEKL====CP" was started as a background job.

Job Name....... "BI_PROCESS_OPENHUB"

Job Initiator.. "ALEREMOTE"

Job Number..... 12490800

-

---

[Former Member]

Hi Experts,

In BW Production system have one issue.

I have 3 Infospoke files which is taking the data from DSO to some .CSV File in G drive.But this is the first time i am getting this Runtime error

i have pasted the below runtime error in ST22.

Full points will be assigned.Appreciate your help.

Runtime Errors TSV_TNEW_BLOCKS_NO_ROLL_MEMORY

Date and Time 22.10.2011 17:46:05

-

---

-

---

Short text

No roll storage space of length 1398800 available for internal storage.

-

---

-

---

What happened?

Each transaction requires some main memory space to process

application data. If the operating system cannot provide any more

space, the transaction is terminated.

-

---

-

---

What can you do?

Try to find out (e.g. by targetted data selection) whether the

transaction will run with less main memory.

If there is a temporary bottleneck, execute the transaction again.

-

If the error persists, ask your system administrator to check the

following profile parameters:

o ztta/roll_area (1.000.000 - 15.000.000)

Classic roll area per user and internal mode

usual amount of roll area per user and internal mode

o ztta/roll_extension (10.000.000 - 500.000.000)

Amount of memory per user in extended memory (EM)

o abap/heap_area_total (100.000.000 - 1.500.000.000)

Amount of memory (malloc) for all users of an application

server. If several background processes are running on

one server, temporary bottlenecks may occur.

Of course, the amount of memory (in bytes) must also be

available on the machine (main memory or file system swap).

Caution:

The operating system must be set up so that there is also

enough memory for each process. Usually, the maximum address

space is too small.

Ask your hardware manufacturer or your competence center

about this.

In this case, consult your hardware vendor

abap/heap_area_dia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each dialog process.

Parameters for background processes:

abap/heap_area_nondia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each background process.

Other memory-relevant parameters are:

em/initial_size_MB: (35-1200)

Extended memory area from which all users of an

application server can satisfy their memory requirement.

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

-

---

-

---

Error analysis

The internal table "\CLASS=ZCL_IM_Z_DG8_ESTREAD_WEEKL\METHOD=IF_EX_OPENHUB_TRAN

SFORM~TRANSFORM\DATA=LT_EQUI" could not be enlarged further.

Memory location: "Session memory"

You attempted to extend the data structure for the management of the

memory blocks for table "\CLASS=ZCL_IM_Z_DG8_ESTREAD_WEEKL\METHOD=IF_EX_OPENHUB

TRANSFORM~TRANSFORM\DATA=LTEQUI". However, the 1398800 bytes required for

this were no longer available in the specified memory area.

The amount of memory requested is no longer available.

-

---

-

---

How to correct the error

Try to decide by analysis whether this request is

reasonable or whether there is a program error. You should pay

particular attention to the internal table entries listed below.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"TSV_TNEW_BLOCKS_NO_ROLL_MEMORY" " "

"ZCL_IM_Z_DG8_ESTREAD_WEEKL====CP" or "ZCL_IM_Z_DG8_ESTREAD_WEEKL====CM001"

"IF_EX_OPENHUB_TRANSFORM~TRANSFORM"

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.

-

---

-

---

Information on where terminated

Termination occurred in the ABAP program "ZCL_IM_Z_DG8_ESTREAD_WEEKL====CP" -

in "IF_EX_OPENHUB_TRANSFORM~TRANSFORM".

The main program was "RSBSPOKE2 ".

In the source code you have the termination point in line 230

of the (Include) program "ZCL_IM_Z_DG8_ESTREAD_WEEKL====CM001".

The program "ZCL_IM_Z_DG8_ESTREAD_WEEKL====CP" was started as a background job.

Job Name....... "BI_PROCESS_OPENHUB"

Job Initiator.. "ALEREMOTE"

Job Number..... 12490800

-

---

[Former Member]

Hi Laxman,

This is memory related issue, so first of all I would suggest you to run the same infospoke at some other time and check whether it failed first time due to other processes running in the current server.

If this extraction is failing after multiple attempts then you need to contact to your basis team and they might change some parameters either related to background processes or roll memory area.

Regards,

Durgesh.

[Former Member]

Thanks for your speedy response.

In process chain,have 3 infospokes parallely and i executed one by one but still it is showing yellow colour and throwing the above dump in ST22.

I have informed to my bais team and they are help less.

As you said basis team will change some parameters and roll memory area.

can you please tell me what parameters and roll memory area need to change?

Please do the needful.

Thanks

Laxman

[Former Member]

Hi,

The dump TSV_TNEW_BLOCKS_NO_ROLL_MEMORY occurs when roll buffer has been exhausted. check the usage of roll buffer history in ST02 . If the roll buffer has been exhausted, you can increase the size with parameter rdisp/ROLL_MAXFS, but make sure you have sufficient disk space to handle the additional size of this buffer if it writes to disk.

Please refer the following SAP note:

SAP Note 185185 - Application: Analysis of memory bottlenecks

Hope this helps....

Thanks,

Nagarjuna

Edited by: Nagarjuna Reddy on Oct 24, 2011 5:06 AM

Edited by: Nagarjuna Reddy on Oct 24, 2011 5:09 AM