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

CNV_DMC_HC063 - Overview

• Message type: E = Error

• Message class: CNV_DMC_HC -

• Message number: 063

• Message text: &1 - &2: Minimum 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_HC063 - Details

• The SAP error message CNV_DMC_HC063 typically relates to data migration processes, particularly in the context of SAP Data Migration Cockpit (DMC) or SAP S/4HANA migrations. This specific error indicates that the minimum latency for a data transfer or processing task has exceeded a predefined warning threshold.
  
  Cause:
  
  Latency Issues: The error suggests that the time taken for data processing or transfer has exceeded the acceptable limits. This could be due to network issues, system performance bottlenecks, or inefficient data processing logic.
  Resource Constraints: Insufficient system resources (CPU, memory, I/O) can lead to delays in data processing.
  Configuration Settings: The thresholds for latency might be set too low for the current workload or data volume.
  Data Volume: Large volumes of data being processed simultaneously can lead to increased latency.
  
  
  Solution:
  
  Monitor System Performance: Use SAP monitoring tools to check system performance metrics (CPU, memory, disk I/O) during the data migration process. Identify any bottlenecks and address them.
  Optimize Data