Skip to Content
0
Former Member
Sep 16, 2010 at 04:02 AM

TSV_TNEW_PAGE_ALLOC_FAILED

629 Views

Our BI consultant is trying to do BI loads in BIP system and gets short

dump "TSV_TNEW_PAGE_ALLOC_FAILED". Below are the BI Consultant process

discription. Below is the short dump. What is the solution to this

issue?

We are trying to reload the COPA cube with data from ECP and there are

approx 16 million records to load into our COPA cube.

I was able to successfully extract the records from ECP (it took about

3.5 hrs) but the next step in BW terminated with a dump ST22. It was

trying to extend a table space and did not have available space.

This is a onetime load then the daily deltas will be much smaller.

Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED

Date and Time 15.09.2010 02:56:48

-


-


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 "" 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: 968

Number of rows: 0

Allocated rows: 10

| Newly requested rows: 15594432 (in 974652 blocks)