Skip to Content
0
Mar 18, 2015 at 01:05 PM

Data flows are getting started but not completing successfully while extracting/loading of the data

1023 Views

Hello People,

We are facing a abnormal behavior with the dataflows in the data services job.

Scenario:

We are extracting the data from CRM end in parallel. Please refer the build:

a. We have 5 main workflows flows i.e :

=> Main WF1 has 6 more sub Wf's in it, in which each sub Wf has 1/2 DF's associated in parallel.

=> Main WF2 has 21 DF's and 1 WFa->with a DF & a WFb. WFb has 1 DF in parallel.

=> Main WF3 has 1 DF in parallel.

=> Main WF4 has 3 DF in parallel.

=> Main WF5 has 1 WF & a DF in sequence.


b. Regularly the job works perfectly fine but, sometimes it gets stuck at the DF’s without any error logs.


c. Job doesn’t stuck at a specific dataflow or on a specific day, many a times it strucks at different DF’s.

d. Observations in the Monitor Log:

Dataflow---------------------- State----------------RowCnt------LT-------AT------

+DF1/ZABAPDF

PROCEED

234000

8.113 394.164

/DF1/Query

PROCEED

234000

8.159 394.242

-DF1/Query_2

PROCEED

234000

8.159 394.242

Where LT: Lapse Time and AT: Absolute time

If you check the monitor log, the State of the Dataflow DF1 remains PROCEED till the end, ideally it should complete.

In successful jobs, the status for DF1 is STOP . This DF takes approx. 2 min to execute.

The row count for DF1 extraction is 234204 but, it got stuck at 234000.

Then we terminate the job after sometime,but for surprise it gets executed successfully on next day.

e. As per analysis over all the failed jobs, same things were observed over the different data flows that got stuck during the execution.Logic related to the data flows is perfectly fine.

Observations in the Trace log:

DATAFLOW: Process to execute data flow <DF1> is started.

DATAFLOW: Data flow <DF1> is started.

ABAP: ABAP flow <ZABAPDF> is started.

ABAP: ABAP flow <ZABAPDF> is completed.

Cache statistics determined that data flow <DF1>

uses <0>caches with a total size of <0> bytes. This is less than(or equal to) the virtual memory <1609564160> bytes available for caches.

Statistics is switching the cache type to IN MEMORY.

DATAFLOW: Data flow <DF1> using IN MEMORY Cache.

DATAFLOW: <DF1> is completed successfully.

The highlighted text in the trace log is not appearing in the unsuccessful job but, it appears for the successful one.

Note: The cache type is pageable cache, DS ver is 3.2.


Please suggest.



Regards,

Santosh