Monitoring

For a landscape-wide, holistic view of every SLT replication process, which transaction do you open instead of the single-configuration cockpit?

You open the notification settings via transaction IUUC_REPL_EN directly instead of from the LTRC cockpit. What extra input does that path demand?

Email notifications are activated for an SLT configuration but no emails ever arrive. What upstream setup is most likely missing?

In the LTRC cockpit, when do you use the Load Statistics tab versus the Data Transfer Monitor tab?

Which SLT report gives you post-initial-load insert/update/delete counts and lets you watch replication latency?

SLT health checks fall into which two broad categories, and why does the split matter?

In the Settings for Connection Check tab, what is the default response-time threshold before a connection error fires, and when do you raise it?

When SLT resolves an inconsistency, how does it assign the new logging-table sequence number to avoid clashing with existing ones?

You set a configuration-level logging-table warning threshold, then also add a row for one table under Logging Table Entries (Table-Specific). Which value governs that table?

On the Email Recipients tab, does every recipient automatically receive all notification emails?

Under Job Settings, what does the default long-running-job option do, and what is its additional delay time?

What drives the check results that end up in an SLT notification email, and which configurations are covered?

Master Job Check versus Job Activity Check in SLT health checks — what's the difference?

Both the Table Status Check and the Trigger Check touch triggers. What is each actually checking?

In SLT's Latency Check, what exactly is being measured against the warning/error threshold?

Logging Table Check versus Latency Check — what does each flag against its threshold?

How do you run a health check on demand for one SLT configuration rather than waiting for the periodic job?

After running an SLT health check, where do you read the results, and what does a healthy system look like?

In the Data Transfer Monitor, a table's sequence number moves from 30 to 40. What does that signify, and which number means higher priority?

In transaction ODQMON on the SLT (source) system feeding SAP BW, what provider/subscriber pair identifies the queue?

Drilling into an ODQMON queue you see Extraction Mode 'Initial Data (Delta Init)'. What state is that queue in?

An ODQMON delta queue is stuck in an error state and data is piling up in the ODP system. If the target is unavailable so you can't stop the request the normal way, how do you stop the buildup?

In the SLT + SAP Data Services flow, how does the LAST TSN Confirmed column in the ODQMON queue tell you a target write actually succeeded?

SAP Data Services is down in an SLT→ODQMON→target flow. What keeps happening, and what is at risk while it's out?

The Cross-Database Comparison in SAP Solution Manager finds SLT source/target discrepancies. Is it just a read-only report?

When Cross-Database Comparison resolves inconsistencies, what are the three corrective actions SLT applies to the target?

For which tables can you actually resolve inconsistencies via Cross-Database Comparison?

During inconsistency resolution, what does the runtime option 'Do Not Update Logging Table if Record Key Exists' trade off?

You pick 'Update Logging Table without Performing Checks' to resolve inconsistencies faster. What must you absolutely not do while it runs?

When resolving an inconsistency, which target operations are allowed depends on the source. What's the rule?

What connection is a hard prerequisite for resolving Cross-Database Comparison inconsistencies, and what does it identify?