Troubleshooting

A replication step failed hard. When do you look in ST22 versus SM21?

SLT reaches a source or target through two different kinds of connection. Which transaction manages each, SM59 or DBCO?

You want one view of whether every SLT configuration is healthy, not the detail of a single config. Which transaction?

You need to manually create or drop the replication triggers and logging table. Which transaction, and critically, in which system do you run it?

For a 'Cannot Create Logging Table ... different structure' error, how does the fix differ when the conflicting IDENT is obsolete versus still actively replicating?

What data does an SLT logging table actually store for its source application table?

When the same source application table is replicated to two different targets, how many logging tables and trigger sets does SLT maintain for it?

Starting replication fails with 'Cannot Create Logging Table /1CADMC/XXXX; Table Exists with Different Structure.' What does this indicate?

Which two tables assign and track the IDENT (sequence number) that names an SLT logging table, and in which system does each live?

Why does switching Write Behavior to Array Modify clear the duplicate-key error when the default insert-based behavior cannot?

An SAP Note tells you to run a specific SLT report program by name. Do you use the LTRC Expert Functions tab or SE38?

After a source upgrade the target table's structure no longer matches the source, even though SLT normally propagates structure changes. How do you resolve it?

To repair data inconsistencies after an outage, when do you use a partial (selective) load instead of a full re-initialization?

You need to tune replication throughput for a slow table. Is that done in LTRC or LTRS?

A replication load has stalled with no errors in the logs. Which transactions do you check, and in what order, to find a resource bottleneck?

After SLT auto-reconnects following an outage, the initial load fails with 'Cannot insert record in target system (duplicate key error).' What is happening and how do you fix it?

Replicating table SFLIGHT to a second target fails with 'Cannot Replicate Data from Table XXX, Different Trigger Option Exists.' What is the usual root cause?

Replication errors out with 'Table does not exist or unknown.' What objects should you check, and where?

After a planned source hostname change, replication stays in a communication-error state even though SLT is designed to auto-reconnect. What step was skipped?