Introducing Troubleshooting

The notification console allows you to define the aspects you want to receive notifications about, for example, if a critical value, error, or warning occurs. You can also define thresholds for replication latency errors and warning conditions. You receive alerts as soon as an error condition occurs.

To find the root cause, go to transaction LTRC and check the following information:

• Table Overview
• Data Transfer Monitor
• Application Logs

First, identify whether the error occurred in the source system, the SLT server, or the target system. This indicates where you should look for the root cause. For example, you can perform the following checks:

• Check for any system or connection problems.
• Check for authorization or permission problems.
• Check if the necessary SLT jobs are running.
• Check for any errors or warnings in the application log.
• Check whether one or more tables are affected.
• Check whether all tables of one configuration are affected or all tables of all configurations are affected.
• Check trigger, logging table, migration object, target structure, and so on.

Identify whether the root cause is related to problems with the system’s environment or communication layer, or whether it is caused by a problem condition within the SLT functionality. If the problem is not directly related to SLT functionality, you must rely on classical system administration tools and expertise.

For most (identified) problems directly related to the SLT, the SAP Landscape Transformation Replication Server cockpit provides the following functions to correct the error:

Check for available SLT note corrections and apply them.

• The Expert Functions tab provides functions for deeper analysis, resetting of error flags, and health checks for 1:N configuration settings.

  Further health checks can be found in transaction LTRO.

• The Processing Steps tab provides functions to reset and correct problems with all preparatory-related steps.

  These functions are as follows:

  • Database triggers and logging table
  • Load and replication objects
  • Runtime module
  • Range calculation

For more information, see SAP Note 2529885.

If you cannot fix the problem, open an incident ticket with SAP.

Provide a detailed description of your problem. Be prepared to open the remote service connection to allow an SAP expert to log on to your systems for problem analysis.

The Processing Steps tab contains a collection of functions that you can use in preparation for data replication. You can execute all of these steps manually in the event of potential system failures or configuration errors.

The preparation steps are normally executed by the replication controller job automatically. However, you can use this activity to execute the steps if any issues have occurred. If you execute the Execute Preparatory Steps activity, the system only executes the steps that have not been completed successfully.

The preparatory steps consist of the following:

• Create Logging Tables
• Create Database Triggers
• Create Tables and Synonyms
• Define Load and Replication Object
• Generate Runtime Modules
• Start Range Calculation
• Unblock Initial Load when all preparation steps are executed

You can also execute the single steps, either for all tables of a configuration or a specified list of tables.

You can also delete the replication object definition or the generated runtime object.

In the last step, you can delete a table from the Table Overview tab, and delete all replication-relevant settings for this table.

On the Expert Functions tab, you can execute troubleshooting activities. You can, for example, reset the status for a table or change the connection settings to the target system. Each activity contains detailed documentation. To view the documentation for a function, select it and choose Documentation. To execute a function, select it and choose Execute.

Find more information about this topic in the Application Operation Guide.

In emergency cases, some functions can be executed directly on the source system using transaction IUUC_REMOTE.

To see the active triggers in the system, use the List Triggers in Display functions.

To delete the triggers or logging tables in the system, use the Delete Triggers or Delete Logging Tables in Expert functions.