Troubleshooting

For creating and testing the DATABASE connections SLT uses to source/target, which transaction — and how does it differ from SM59?

Where do you go to improve SLT replication PERFORMANCE, versus where you trigger and monitor replication?

You get 'Cannot Create Logging Table /1CADMC/XXXX; Table Exists with Different Structure'. What does the XXXX (IDENT) part represent?

Resolving 'Cannot Create Logging Table; Table Exists with Different Structure' — the IDENT turns out to be obsolete. What is the fix?

The logging-table IDENT collision is NOT obsolete — the source table is actively replicating. How do you resolve it without disturbing that live replication?

In the logging-table IDENT fix, what is the number range object you adjust in SNRO, and why raise it rather than reuse the free number?

A source application table's structure was changed, but the change never reached the target and now the proxy table and target table disagree. What typically caused the propagation to fail?

Which SLT function reconciles a structural mismatch between the proxy table and the target table, and on which LTRC tab does it live?

You need to manually create or drop the SLT triggers and logging table. Which transaction do you use, and on which system must you run it?

A background replication job appears stuck. Which transaction shows the BG jobs overview and job logs for SLT?

You need to execute or display a standard SLT report (or write a custom one) during troubleshooting. Which transaction?

During SLT troubleshooting, when should you reach for SM21 rather than ST22?

In the LTRC Expert Functions tab, what class of actions are you generally there to perform during troubleshooting?

Why is changing write behavior to Array Modify a safe response to a duplicate-key error, rather than a data-loss risk?

Replication is failing and you can't tell if the problem is SLT logic, the RFC link, or the target DB. What ordered set of checks does the chapter's transaction toolkit suggest?

After an outage, SLT resumes an interrupted initial load and throws 'Cannot insert record in target system (duplicate key error)'. What is actually happening?

To clear the SLT duplicate-key error after a resumed load, which write behavior value do you set, and where?

Replicating table SFLIGHT from one source to two different targets, you hit 'Cannot Replicate Data from Table XXX, Different Trigger Option Exists'. What is the root cause?

Why does a mismatch in 'Allow Multiple Usage' between two SLT configurations break replication of a shared table to a second target?

SLT reports 'Table does not exist or unknown' for a table you just triggered for replication. What should you verify first?

For the 'Table does not exist or unknown' error, where do you look for the synonym information, and what determines which tab you use?

After a source/target outage, replication picks up automatically — but after a planned hostname change on the source, replication keeps failing with communication errors. What step was skipped?

Two engineers debate an SLT recovery after an unplanned source outage: one wants to reset and reload every table, the other says do nothing. Who is right?

You suspect the SLT replication problem is an ABAP short dump during the load. Which transaction do you open, and how does it differ from SM21?

Replication seems stalled and you suspect there aren't enough work processes. Which transaction shows DIA/BG/UPD process availability, and which one gives the server overview?

You want the health-check status of ALL configurations in an SLT system at a glance. Which transaction, and how is it different from LTRC?