SAP Knowledge Base Article - Preview

2895688 - Trace logs do not follow each other in proper sequence - SAP Cloud Platform Integration for Data Services

Symptom

The trace logs in the View History do not follow each other in correct order. See the below example:

2020-01-25 18:01:10 (6060:1376) DATAFLOW:Data flow <<dataflow name>> is completed successfully.
2020-01-25 18:01:10 (6060:1376) DATAFLOW:Process to execute data flow <<dataflow name>> is completed.
2020-01-25 18:01:26 (1:1) DATAFLOW:READER: [BlockQueueReaderRunner] Batch '1' read data successful, ready for agent.
2020-01-25 18:01:30 (1:1) DATAFLOW:READER: [BlockQueueReaderRunner] Batch '1' read data successful, ready for agent.
2020-01-25 18:01:12 (340:5316) DATAFLOW:Process to execute data flow <<dataflow name>> is started.
2020-01-25 18:01:13 (340:5316) JOB:Initializing transcoder for datastore <<datastore name>> to transcode...


Read more...

Environment

SAP Cloud Platform Integration for Data Services 1.0.11.xx

Product

SAP Cloud Integration for data services 1.0

Keywords

LOD-HCI-DS, CPI, HCI, CPI-DS, logs, timestamp, order, sequence, View History, runtime , KBA , LOD-HCI-DS , HANA Cloud Integration for Data Services , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.