Delta load in SAP Datasphere replication flow fails

[popflorin]

Dear experts,

I am currently struggling with a delta load using the 0UC_SALES_STATS_02 extractor in SAP Datasphere Replication Flow configured with delta.

Long story short, we have everything related to the conectivity in place and we have created this RF to extract a full picture of sales statistics in a local table inside SAP Datasphere. We are using the EBW_DQ_SS transaction code to prepare our loads in the delta queue, however due to a very big pool of data(over 1B records), we have to run this job with filter on Posting Date to be just a part of each month (1-20; 21-29/30/31).

We have started the delta init with no data and from there with each slice of data scheduled in EBW_DQ_SS. Everything went smoothly for some cases, however for some particular cases(where is way too much data in one slice), we occur some errors: sometimes can be out-of-memory errors, othertimes can be "closed connection" (internal server error).

We are trying to trace the problem, but there are no hints on what actually is going wrong.

It is to mention that our DP Agent is set with only 8GB of physical memory.

We don't think there is a problem with the configuration of the SDI connection as we have managed to load about 700M records, but we got stuck at some point. 

Experts, please help us, if you have ever occured an error like this, to understand what we are doing wrong. Do we need to raise the resources for the DP agent? Is there any chance that the connection is configured wrong? 

Thank you and best regards,

Florin

[xiaoming_wu]

Hi Florin,

 Are you using replication flow in datasphere? As far as I know replication flow won't use DP agent.
You can try to run it again, check DP agent log for the extractor name, is there any record in the log? 
If DP agent is not used, you can raise a new question to sap datasphere. 

Best regards
Helen

[popflorin]

Hi @xiaoming_wu ,

Thank you for you response. Could you please explain me how the Replication Flow is connecting to the S/4 extractor without using the DP Agent? This issue is persisting and we really need to know what we are doing wrong..

Thank you and regards,

Florin

[xiaoming_wu]

I remove the tag for SDI, so SAP datasphere expert will help you with the replication flow related topic