TSV_TNEW_PAGE_ALLOC_FAILED

[Former Member]

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)

[former_member189763 · Accepted solution]

This is issue comes when memory gets exhausted. Please advice your BI team to split the load and do the data loading in more than one run. As the number of records is large and can grow in future as well so extending memory can not be a feasible solution.

Regards

Dhiraj

[Former Member]

---

How to correct the error

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

Roll area...................... 2718352

Extended memory (EM)........... 2002743520

Assigned memory (HEAP)......... 17176773152

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

Paging area.................... 24576

Maximum address space.......... " "

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_PAGE_ALLOC_FAILED" " "

"CL_RSODSO_SEMANTIC_PACKETIZER=CP" or "CL_RSODSO_SEMANTIC_PACKETIZER=CM002"

"FETCH_PACKAGE"

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.

-

---

-

---

System environment

SAP-Release 700

Application server... "BI-PROD-APP1"

Network address...... "172.16.105.43"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "4x AMD64 Level"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 10

Shortdump setting.... "full"

Database server... "BI-PROD-DB1"

Database type..... "ORACLE"

Database name..... "BIP"

Database user ID.. "SAPSR3"

| Terminal................. " "

-

---

User and Transaction

Client.............. 300

User................ "DMORROW"

Language key........ "E"

Transaction......... " "

Transactions ID..... "568EC0DF03CDF17891ED002264FC02DA"

Program............. "CL_RSODSO_SEMANTIC_PACKETIZER=CP"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

-

---

-

---

Information on where terminated

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

in "FETCH_PACKAGE".

The main program was "RSBATCH_EXECUTE_PROZESS ".

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

of the (Include) program "CL_RSODSO_SEMANTIC_PACKETIZER=CM002".

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

Job Name....... "BIDTPR_21458_1"

Job Initiator.. "DMORROW"

Job Number..... 01590200

-

---

-

---

Source Code Extract

-

---

Line

SourceCde

-

---