Extraction job failing in source system

Former Member · ‎05-23-2012

Hi,

We have an extractor which extracts attributes for netwrok activity(0ACTIVITY_ATTR). This is a full data load as there are huge no of records we have split into multiple infopackages(by applying data selection).

Now the problem is some of the info packeges are failing due to the job cancelled in source system.

eg of job log:

19.05.2012 13:00:00 Job started

19.05.2012 13:00:00 Step 001 started (program SBIE0001, variant &0000000035667, user ID RFCUSR)

19.05.2012 13:00:00 DATASOURCE = 0ACTIVITY_ATTR

19.05.2012 13:00:00 *************************************************************************

19.05.2012 13:00:00 * Current Values for Selected Profile Parameters *

19.05.2012 13:00:00 *************************************************************************

19.05.2012 13:00:00 * abap/heap_area_nondia......... 2000683008 *

19.05.2012 13:00:00 * abap/heap_area_total.......... 2000683008 *

19.05.2012 13:00:00 * abap/heaplimit................ 40894464 *

19.05.2012 13:00:00 * zcsa/installed_languages...... 6EDGIJL *

19.05.2012 13:00:00 * zcsa/system_language.......... E *

19.05.2012 13:00:00 * ztta/max_memreq_MB............ 256 *

19.05.2012 13:00:00 * ztta/roll_area................ 6500352 *

19.05.2012 13:00:00 * ztta/roll_extension........... 2000683008 *

19.05.2012 13:00:00 *************************************************************************

19.05.2012 13:05:40 ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED

19.05.2012 13:05:40 Job cancelled

When i repaet the same infopackage it is able to extract data.

Why this is happening to only this extractor.

we have another data loads which extracts more no of records than this at a strech. why is this memory overflow issue is coming up only for this extractor ( even after splitting up the extraction based on data selection)?

Please help me understanding this.

Thanks,

Harish

former_member188080 · ‎05-25-2012

Hi,

1. check the data packet setting in RSCUSTV6

2. you can split the data and load it multiple times

3. check with basis which parameters and table it is getting stiuck and ask them to increase the size..they can check it now or when job is running

4. Normally these types of errors occurs in Dev /quality system where there is insufficient memory allocations..

Thanks and regards

Kiran

Former Member · ‎05-25-2012

Hi,

I have changed the data packet size at infopackage level to 200

Scheduler menu -> DataS. Default data transfer --> data packet size to 200

still some of my infopackages are fialed with the same error .

Please suggest

Br,

Harish

Former Member · ‎05-24-2012

Hi Harish,

We have faced the same issue several times when i was trying to extract the data from source system to BI. Please follow the below steps to avoid this issue in future...

1. Check the no.of bacj ground processes available

If back ground jobs are fie, then check whether there is any activity goinon in source system which is effecting your job with the help of BASIS Team.

2. Check the tRFC connection is fine or not with the help of BASIS Team

If the back gorund processes and tRFC connection is fine then there is no issue with the source system.

3. Reduce the packet size in Info Package Selection and run the job again.

The above three checks will let you know the reason for the failure and perform action accordingly as mentioned above.

Hope it will resolve your issue.....Please revert back with your responce......All the best..

Thanks,

Chandra.

Former Member · ‎05-24-2012

Use T-code RSCUSTV6 and see the pic to reduce packet size. Pls assign points if it is useful.

Thanks,

Raghavendra.Kolli

Former Member · ‎05-24-2012

Use T-code RSCUSTV6 and see the pic to reduce packet size. Pls assign points if it is useful.

Thanks,

Raghavendra.Kolli

Former Member · ‎05-23-2012

Hi harish,

This page allocation error can be solved by reducing the packet size in settings of infopackage.

It is due to memory issue at time of loading.

You can reduce packet size to prevent it from failing daily.

You can change packet size in display variant of infopackage. Goto Scheduler menu -> DataS. Default data transfer.

Here you can change the packet size.

Regards,

Harish.

Message was edited by: Harish Babu Tata

Former Member · ‎05-23-2012

Hi,

Check if suffiecient processes are availbale at time of running the IP.

Also Check with Basis regarding the TSV_TNEW_PAGE_ALLOC_FAILED Dump , it occurs due to memory issues.

Let us know your progress with tehe issue.

Best Regards,

Arpit

Former Member · ‎05-23-2012

Hi Harish,

Note - Take the help of basis people to solve this problem.

Recommended Memory Sizing

The following recommendations for memory sizing as of R/3 Release 3.0C are the result of the experience of software developers and consultants. All recommendations are based on the assumption that the swap space is at least 3-4 times as big as the main memory. WARNING: A lack of swap space can cause the operating system to crash. Since the extended memory is not mapped to a disk file like the roll and paging areas, more virtual memory and thus more swap space is required as of R/3 Release 3.0C than for previous Releases.

Problem Solving

Poor memory sizing and configuration causes performance problems. In the following, problem analysis is described for the four most critical problem areas:

Insufficient swap space
Extended memory exhausted
Roll area in memory exhausted
User context requires more memory

Insufficient Swap Space

To correct the sizing for swap space, proceed as follows:

From the main menu choose Tools ® Administration ® Monitoring ® Performance ® Operating system ® Activity. (Alternative: transaction code OS06.)

In the group Swap (fig. 3), check the value Actual swap-space. The recommended swap space is the largest of the following values:

3 to 4 times the size of the main memory
Allocated virtual memory + 600 MB
2 GB (the minimum size)

3. If the recommendation is not fulfilled, increase the swap space. Do not decrease the swap space.

Extended Memory Exhausted

To correct the sizing for extended memory, proceed as follows:

From the main menu choose Tools ® Administration ® Monitoring ® Performance ® Setup/Buffers ® Buffers. (Alternative: transaction code ST02.)
In the group SAP memory (fig. 4), check the row Extended Memory. The value Max. use increased by 20% should be less than the value In memory:
Max. use + 20% < In memory

3. If the recommendation is not fulfilled, adapt the following profile parameters to the values recommended in the section Recommended Memory Sizing:

ztta/roll_extension
em/initial_size_MB

4.If the profile parameters already fulfill the recommendations, contact the SAP Hotline.