cancel
Showing results for 
Search instead for 
Did you mean: 

Write Optimized DSO taking long time to load.

former_member190408
Participant
0 Kudos

Dear All,

We need your help in the below issue.

We have WO DSO which we are loading from Infoset . We added few fields in this DSO and moved it to production. Now in Production system this DSO is taking almost 20 hours to complete (no of records 58 Million) which earlier was taking only 1 hour. In Quality system the same DSO is taking only 1 hour (approx) for the same number of records.

In Production system we have checked the Background jobs and number of processes available. There is as such no deviation from the system point of view.

We have also checked the DTP settings in Quality and Production systems for the number of parallel process and the job class.

The total no of records that we get in this DSO are nearly 58 Million. The package size of DTP is 50,000. There is no routine in the transformation and all fields are directly mapped.

We have tried loading it by decreasing package size too. The strange thing to note in this is that, the first 50 to 60 Packets are getting loaded in only 10 to 15 mins and then the time goes on increasing for the rest of the packets. Most of the time is spent in below steps.

In Job log of this DTP we checked that most of time is spent in step "Overlapping check with archived data ". and in DTP Monitor the time is spent in Updating to DSO step.

We have also tried re-importing it to Production but still no success. So, request you to provide some inputs on this. This has become very critical as most of the other loads are dependent on this.

Accepted Solutions (0)

Answers (11)

Answers (11)

Former Member
0 Kudos

Hi Harjinder,

Check whether tablespace is not the issue?...Do you see enough space in DB02 to extract and load your 58 million records?

Regards

Former Member
0 Kudos

This message was moderated.

vikrant_mahajan
Discoverer
0 Kudos

This message was moderated.

Former Member
0 Kudos

Hello,

There is a SAP note with recommendations to load such volume of data.

Notice that as per recommendation you should not load more then 10 million records per request, once you do that the performance will start to decrease that is why the first 50 data packages are faster.

Please consider SAP note below for more information on this topic.

892513 Performance: Loading data, no of pkg,

Regards,

Christ

Former Member
0 Kudos

In RSBATCH, check how many Parallel Processing that u have for that particular DTP. Again this depends on No. of BGDs available in SM50 & SM51 while this DTP is running. Basically a W/o DSO allows parallel load, which saves time for data loading. In DTP check the symantic keys. If there are too many flagged, this will slow down the DTP run enormously.

Former Member
0 Kudos

Hi,

Just check if any check box is there in semantic Key in DTP.

Thanks

Mayank

Former Member
0 Kudos

Hi Harjinder,

If you have fond the solution to your problem can you please share your knowledge with me.

Thank you

former_member190408
Participant
0 Kudos

Hi ,

We have not found any solution yet. We have raised OSS message for this .

There is no such DSO under Infoset which stores Archived data. We have Master Data Info objects and 1 Write Optimized DSO under Infoset. Extraction from Infoset is very much fine. Time is spent while updating DSO.

Former Member
0 Kudos

hi,

you can try APD , create a base query Based on your infoset and process it in parallell process of std pkt size say 1000 , will execute faster and write to wo dso.

regards

satish

Former Member
0 Kudos

Hi Harjinder,

Please check the combination on which Infoset is built. For eg: if its built on the DSO, check if that DSO Contains archived data or not. Please let me know the objects on which infoset is built.

Regards,

Yash Parikh

Former Member
0 Kudos

Have you checked "Do not check uniqueness of data" setting?

Former Member
0 Kudos

I guess, its taking time for SID creation, you can observe the same processing time of steps under Package. The reason, when you repeat the load and first 50-60 packs went fast is that the SID already created for those packages data. So, check if its taking long time for the step "Conversion of Characteristic Values to SIDs' , if yes try to increase number ranges for required infoobjects.

Former Member
0 Kudos

Is there any archiving setup for that DSO? When you moved the transport, did you delete data? Can you check database object of the underlying tables and see if they are consistent?

former_member190408
Participant
0 Kudos

Hi Abhijeet,

Thanks for replying , there is not archiving step and yes data was deleted before moving.