How To Fix CNV_DMC_HC006 - &1 - &2: Trigger is not active

CNV_DMC_HC006 - Overview

• Message type: E = Error

• Message class: CNV_DMC_HC -

• Message number: 006

• Message text: &1 - &2: Trigger is not active

What causes this issue?

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

System Response

How to fix this error?

In transaction LTRC, you can view the possible causes of the issue. On
the tabs <ZK>Table Overview</> and <ZK>Data Transfer Monitor</>, you can
choose the <ZK>View Errors</> pushbutton. On the tab <ZK>Application
Logs</>, you can also view the logs for the initial load and for the
replication process. The error message and logs can provide guidance for
resolving the issue, for example you can:
Use the expert function <ZK>View Trigger Source Code</> in transaction
LTRC to look for the trigger coding.
Create the trigger manually using the step <ZK>Create Database Triggers
</> (on the tab <ZK>Processing Steps</> in transaction LTRC). However,
note that if the table already had the status <ZK>In Replication</> and
the trigger did not exist for some time, it is possible that changes to
the source table were not captured and are therefore not replicated to
the target system.
Stop and start the table again.
If the trigger code is available and seems to be correct, you can reset
the <ZK>Failed</> flag for the table in order to resume the replication
process. You can reset the flag by using the expert function <ZK>Reset
Status for Triggers and Logging Tables</> in transaction LTRC.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CNV_DMC_HC006 - Details

• The SAP error message CNV_DMC_HC006 typically indicates that a specific trigger related to the Data Migration Cockpit (DMC) is not active. This error can occur during data migration processes when the system expects a certain trigger to be active but finds it inactive.
  
  Cause:
  
  Inactive Trigger: The most common cause of this error is that the database trigger required for the data migration process is not activated. Triggers are often used to automatically handle certain actions in the database, and if they are not active, the expected behavior will not occur.
  
  Configuration Issues: There may be issues with the configuration of the Data Migration Cockpit or the specific migration project you are working on.
  Authorization Issues: Sometimes, the user executing the migration may not have the necessary authorizations to activate or manage triggers.
  
  
  Solution:
  
  
  Activate the Trigger:
  
  Check the database for the specific trigger mentioned in the error message. You can do this by querying the database