How To Fix CNV_DMC_HC065 - &1 - &2: Average latency (&3) has exceeded warning threshold by &4

CNV_DMC_HC065 - Overview

• Message type: E = Error

• Message class: CNV_DMC_HC -

• Message number: 065

• Message text: &1 - &2: Average latency (&3) has exceeded warning threshold by &4

What causes this issue?

SAP Landscape Transformation Replication Server calculates the time
between the recording of a change in the source system and sending this
data to the target. The respective threshold has been exceeded.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Many different elements influence latency. It is always a good idea with
starting to monitor the latency values over some time. You can view
historical latency information in transaction LTRC. On the tab
<ZK>Expert Functions</>, choose <ZK>Display Replication Statistics</>.
If there are consistently high latency values, there may be issues with
the connections to the source or target systems, or issues within the
operations executed in these systems.
If you see different latency values (maybe aligned your business hours),
it is likely that the amount of changes in the source system is higher
than what SAP Landscape Transformation Replication Server can transfer
with one job. If this is the case, options for improving latency include
filtering the data, or specifying ranges for the logging table (for more
information, see <ZK>Performance Options</> in transaction LTRS).

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CNV_DMC_HC065 - Details

• The SAP error message CNV_DMC_HC065 indicates that the average latency for a data transfer process has exceeded a predefined warning threshold. This message is typically encountered during data migration or data transfer activities, particularly when using the SAP Data Migration Cockpit or similar tools.
  
  Cause:
  
  
  High Latency: The average latency of data transfer operations has surpassed the acceptable limit. This can occur due to various reasons, such as:
  
  Network issues causing delays in data transmission.
  Resource contention on the source or target systems (e.g., CPU, memory, or I/O bottlenecks).
  Inefficient data processing or transformation logic.
  Large volumes of data being processed at once, leading to slower performance.
  
  
  
  
  Configuration Issues: Incorrect configuration settings for the data transfer process can also lead to increased latency.
  
  
  
  Solution:
  
  
  Monitor System Performance: Check the performance metrics of both the source and target systems. Look for any resource bottlenecks (CPU, memory, disk I/O) that could be affecting performance.
  
  
  Network Analysis: Investigate the network connection between the