Introducing Replication with SAP Solution Manager's CDC Tool

Objective

After completing this lesson, you will be able to understand replication with SAP Solution Manager's CDC tool.

Cross-Database Comparison

The data transfer with SLT is robust, and data cannot be lost. Nevertheless, in rare cases where any inconsistencies have been identified, you can use the cross-database comparison (CDC) application that comes with the SAP Solution Manager. This allows you to compare the data consistency between source and target systems. The result of this comparison run can be used by SLT to solve the inconsistencies.

From the Repair Replication Tables dropdown, one option is selected: Resolve inconsistencies identified by CDC Application. A second screenshot shows the Resolve Inconsistencies Identified by CDC Application section , displaying fields for connection info, selection criteria, and runtime options.
  • If objects exist in the source system but not in the target system, the following occurs:

    The SAP Landscape Transformation Replication Server inserts the missing rows in the target system.

  • If objects exist in the target system but not in the source system, the following occurs:

    The SAP Landscape Transformation Replication Server removes the rows from the target system.

  • If objects exist in both systems, but there are differences concerning data, the following occurs:

    The SAP Landscape Transformation Replication Server adjusts the values.

The steps are as follows:

  1. In Expert Functions of transaction LTRC, select Resolve Inconsistencies Identified by CDC Application.
  2. Specify an RFC connection from the SLT system to the CDC system. The system uses this RFC connection to identify the relevant mass transfer IDs, tables, CDC instances, and CDC runs.
  3. Select the following:
    • Mass transfer ID
    • The table that you want to check. Note that you can only resolve inconsistencies for one table at a time.
    • The comparison instance
    • The comparison run

Any inconsistencies detected are solved by adding the respective records to the logging table. Therefore, they are picked up by the replication again. You can choose if SLT should check whether a record for the key values already exists in the logging table or if it should add it directly to the logging table.

Note

If you are adding records to the logging table without checking it beforehand, ensure that no changes are made to the source system table when this report is running.

For more information, see the following:

  • SAP Note 2761769 - What to check if the inconsistency between source table and target table is found – SLT
  • SAP Note 2602264 - Is there a way to check source and target consistency? – SLT
  • SAP Note 2277919 - How to check data consistency in replication between ECC and HANA when using SLT
  • SAP Note 2081759 - Monitoring of SLT systems in Solution Manager using the System Monitoring application
  • Cross Database Comparison - Guide - Solution Manager - Support Wiki (sap.com) CDC Configuration using LT Replication server – 1/2 blogs

Learning

SAP FacebookSAP YoutubeSAP LinkedIn