Monitoring SLT Data Replication
After completing this lesson, you will be able to:
• Describe the monitoring dashboard
• Explain the concept of Mass Transfer IDs
• Leverage the IUUC Synchronization Cockpit
On the Jobs and Connections tab page, you get details about the status of the master job, the load jobs and the connection details of all the involved systems.
If the Master Job aborts (for example due to a restart of the LT Replication server), you can restart the master job by choosing the relevant pushbutton.
The Load Jobs status shows the total number of available batch tasks in the LT Replication Server and also the number of planned and currently running replication jobs for the current configuration. If there are no tables to be processed, the status might be green even though no replication jobs are running.
In the Jobs Connections, you can view the current connection status to the remote systems (source system and HANA System).
On the Triggers tab page, you can view all tables for which a trigger issue might exist. A trigger issue occurs if a trigger is dropped not using the LT Replication Server. Therefore LT replication server expects that a trigger is still active even though it was dropped.
When a new table is scheduled for replication there will be a warning message that the trigger is not yet created. Note that this message should disappear after a few seconds when the trigger is active.
The Incomplete Tables section in the Triggers tab page is empty if no trigger issues exist. This does not mean that no triggers are active, as it only displays tables for which trigger issues exist.
On the Statistics tab page, you can view the current status of all relevant tables of the selected configuration. You can view the Current Action and the Current Status.
For all tables started in replication mode, and the initial replication of all data is completed, a latency is calculated and also displayed here. The latency is the time difference between the change timestamp on the source system and the commit timestamp in the HANA system.
There are different latency figures calculated for each replicated table:
• Latency Med (all): Median of all latency figures
• Latency Med (24h): Median of the latency figures from the last 24 hours
• Latency Min (24h): Minimum latency within last 24 hours
• Latency Max (24h): Maximum latency within last 24 hours
• Last Replication: Laps of time since last replication
On the Settings tab page, the data entered when creating the configuration is displayed. If you switch to the Edit mode some properties can be changed.
The Number of Replay Jobs can be increased or decreased.
In the settings tab also the maximum number of jobs used for the Initial Load can be defined. The number of Initial Load Jobs defines how many replication jobs can be used for initial load.
Therefore this number cannot be higher than the total number of replay jobs. Its recommended to choose the number of Initial Load Jobs 1 number less then the number of total jobs, so that there is at least one job reserved for delta replication.
You can also switch the replication mode between Real Time replication and Scheduled replication.
All technical expert functions, monitor capabilities and job names use a so called Mass Transfer ID for selecting the relevant configuration.
Use transaction LTRC to open the cockpit overview
Give the mass transfer id and press execute button to see the table details.
On the application logs tab page, you can view the logs of executed definition and replication tasks.
You have to define a filter to view the logs.
SAP recommends to display only logs containing error messages. To do this, select Only Important Ones radio button in the filter definition dialog box.
Internal load / replication monitor is called from transaction MWBMON
Give the mass transfer id and execute
Here, below is the information about tabs-
Administration gives general information
Relevant Tables gives information about runtime objects
Steps – this tab is obsolete, do not execute any function here
Application logs – Log information
Runtime information – Runtime statistics of initial data load
Activities – not relevant
Expert Functions – Collection of expert functions
Runtime information is initialized for tables in delta replication
Give access plan/precalculation ID = 1
Here, the migration object is the name of loaded or replicated tables.
Portions indicate total number of portions
Run (number of running portions)
End (number of finished portions)
Err (no. of failed portions)
Total number of portions will increase depending on the load type.
Calculated records / records filtered: Number of calculation records to be transferred.
Final number only for 1,4 and 5
For 3 number will increase
Number of records read: Records read from source DB. After commit on HANA DB, number match to the loaded records.
Calculated MBytes: Calculate size of transferred data (number of records x table width)
Does not reflect the real DB size.
Start Time: Total runtime and detail runtime for individual steps
You can enter the detail view by double click on table name
In this screen, individual status of each load portion is displayed. Also the total runtime and also the runtime for each individual step (for example to read the data) is displayed here and also if any bottlenecks in data transfer.