How To Fix CNV_IUUC_DB_CONN135 - 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: 135

• 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 do not 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_CONN135 - Other configurations use triggers with different settings ?

  The SAP error message CNV_IUUC_DB_CONN135 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 they have different settings (e.g., different trigger types, 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 database tables, they may have been set up with different parameters, leading to conflicts.
  
  Solution:
  
  Review SLT Configurations: Check all existing SLT configurations that are using the same database tables. Ensure that they are set up with consistent trigger settings.
  Adjust Trigger Settings: If you find conflicting settings, you may need to adjust the trigger settings in one or more of the configurations to ensure they match.
  Remove Conflicting Configurations: If possible, remove or deactivate any SLT configurations that are not needed or that are causing conflicts.
  Recreate Triggers: In some cases, it may be necessary to 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 trigger configurations for specific guidance on how to set up and manage triggers properly.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions for this specific error message.
  SLT Configuration Guide: Review the SLT configuration guide for best practices on setting up and managing database triggers.
  Database Documentation: Consult the documentation for your specific database (e.g., HANA, Oracle, SQL Server) for details on trigger management and configuration.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance, as they can provide more tailored guidance based on your specific system configuration and setup.