How To Fix CNV_IUUC_DB_CONN136 - Other configurations use triggers with different settings

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_IUUC_DB_CONN - db connection

• Message number: 136

• Message text: Other configurations use triggers with different settings

What causes this issue?

You want to replicate data from a source system, but there are other
configurations that use this source system. These configurations use
triggers that exclude fields from the replication process. The settings
for the triggers should be the same in all configurations that use the
same source system, but this is currently not the case.

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?

If you want to create the new trigger, you must delete the triggers for
the relevant tables and recreate them. This means that if you already
have a replication running, the replication must be stopped, and a new
replication (including an initial load of the relevant tables) must be
started. To avoid repeating the initial load, you can use the report
IUUC_REDEFINE_DB_TRIGGERS. In this report, you can specify the mass
transfer ID (MT_ID), leave field Lock Timeout Value unchanged, and then
specify the relevant tables in the Table Name field. This means that you
do not need to stop and restart the replication (including dropping and
recreating triggers, and reloading the relevant tables).

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_IUUC_DB_CONN136 - Other configurations use triggers with different settings ?

  The SAP error message CNV_IUUC_DB_CONN136 typically occurs during the execution of the SAP Landscape Transformation (SLT) replication process. This error indicates that there are conflicting trigger settings in the database configurations. Specifically, it suggests that other configurations are using triggers with different settings than those expected by the current configuration.
  Cause:
  
  Conflicting Trigger Settings: The error arises when there are multiple SLT configurations that are trying to use database triggers, but those triggers have different settings (e.g., different types of triggers, different tables, or different configurations).
  Database Configuration Issues: There may be inconsistencies in the database settings or configurations that are causing the triggers to behave differently.
  Multiple SLT Configurations: If there are multiple SLT configurations pointing to the same source table, they may have been set up with different trigger settings.
  
  Solution:
  
  Review SLT Configurations: Check all existing SLT configurations that are related to the source table. Ensure that they are using the same trigger settings.
  Synchronize Trigger Settings: If you find discrepancies, you may need to adjust the trigger settings in one or more configurations to ensure they match.
  Remove Conflicting Configurations: If possible, remove or deactivate any SLT configurations that are not needed or that conflict with the current configuration.
  Recreate Triggers: If necessary, you can drop and recreate the triggers to ensure they are set up correctly according to the desired configuration.
  Consult Documentation: Refer to the SAP documentation for SLT and database triggers to ensure that you are following best practices for configuration.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  SLT Documentation: Review the official SAP documentation for SLT to understand how triggers work and how to configure them properly.
  Database Logs: Look at the database logs for any additional error messages or warnings that may provide more context about the issue.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  By following these steps, you should be able to resolve the CNV_IUUC_DB_CONN136 error and ensure that your SLT configurations are set up correctly.