SAP Knowledge Base Article - Public

3484133 - Performance Problem in Replication Flows in SAP Datasphere


Replication Flow is slow or fails with generic error on SAP Datasphere where the target is a local table and Load Type is "Initial and Delta". Data volume may be relatively large or parallel partitions are running.

Following error messages or symptoms may occur during replication:

  • Run is stuck in Status: “Initial Running” / State: “Transferring Initial Load”
  • Run fails with runtime error: “Failed to write data to target. Connection reset”
  • Run reports message: "An error occurred. Replication runs are retrying. Error:"
  • Run fails with runtime error: Failed to write data to target due to database error. SAP DBTech JDBC: [616]: rejected by workload class configuration. This error can occur for any replication object when the workload class CPU or memory threshold limit of the HANA database is exceeded, or when the SQL statement has been waiting in the queue for more than 10 minutes. Please check HANA workload management settings to increase the workload thread limit and/or memory limit and/or priority. A possible solution could be, for example, adding more vCPU or memory capacity. Alternatively, you could consider pausing a few replication flows or their objects (considering their business importance) to reduce concurrency, until the HANA SQL error 616 disappears. 
  • Number of records replicated per hour drops significantly (from millions to a few hundred thousand records per hour)


SAP Datasphere


See the SAP Note 3489681 from DI development team for further insights and final deployment date.


replication flows, replicate, slowness, performance, cpu overload, initial running, memory, Transferring Initial Load, Failed to write data to target, Connection reset, slow, stalled, "HANA SQL error 616" , KBA , DS-DI-RF , Replication Flows , CA-DI-IS-RMS-CON , RMS connectivity , CA-DI-IS-RMS , Replication Management Service , Problem


SAP Datasphere all versions