Known Issues for Replication

Known issues and workarounds for SAP Control Center for Replication.

Change Request Number Description

SAP Replication Agent thread monitoring in SCC for Replication does not work in an SAP ASE 16.0 environment configured to use synchronous mode.

The SCC RepAgent Thread monitor cannot display controlling Replication Servers when it monitors an SAP ASE Replication Agent in synchronous mode.

Workaround: None.


No data is displayed for SAP Adaptive Server Enterprise RepAgent sender threads in the Replication Path Dashboard using alternate connections.

Workaround: Query the new SAP ASE MDA tables to get statistics for the new RepAgent senders. These are the new MDA tables:
  • monRepLogActivity
  • monRepScanners
  • monRepScannersTotalTime
  • monRepSenders

Administration Console options in the Properties dialog (Application > Administration > General Settings > Administration Console) let you set timeout and row count thresholds for data retrieval. These settings have no effect in SAP Control Center for Replication.

Workaround: None.


The Adaptive Server Monitor Replication Agent tab does not display the RepAgent thread sender connection names. However, it shows the list of the controlling SAP Replication Servers for each RepAgent.

Workaround: Open the Replication Server Monitor Connections tab for each controlling SAP Replication Server. The tab displays the connection names for the SAP ASE RepAgents. You can also log in to SAP Replication Server and use the admin who command to derive this information.

To access the Replication Server Monitor Connections tab:
  1. From the Perspective Resources view, select the controlling SAP Replication Server and click Resource > Monitor.
  2. Click Connections.

SAP Control Center for Replication may not have descriptions for some SAP Replication Server 15.7.1 configuration parameters.

Workaround: See the Replication Server 15.7.1 Reference Manual for information on the parameters with missing descriptions. The manual is available on the SAP Help Portal at


A queue graph for intermediate SAP Replication Server is missing in the Replication Path dashboard.

When you open the Path dashboard, the SAP ASE Replication Agent thread always displays zero.

Workaround: Upgrade SAP ASE to 15.0.3 or later.


Gaps may appear in the stacked columns of the latency monitoring history chart.

Only the latency monitoring collection start and end times are available when populating the latency monitoring history chart. If more than one rs_ticket is collected, only one time, that is, one column, is reported in the chart for both tickets. This appears as a gap in the stacked columns.

Workaround: None.


Latency cannot be obtained for non-ASE replicate databases.

SAP Control Center monitors latency in two different ways: by reading the rs_lastcommit table at the replicate database (the default) or, when configured, by reading the rs_ticket_history table at the replicate database. The rs_ticket_history table is used by latency monitoring, which provides the ability to configure connectivity information to non-Sybase/non-SAP replicate databases. However, the default latency monitoring using rs_lastcommit does not, thus SAP Control Center cannot access the rs_lastcommit table in non-Sybase/non-SAP replicate databases. Consequently, the Latency chart displays zero latency. This is also true for the Latency chart in the Path dashboard.

Workaround: To monitor latency to non-Sybase/non-SAP replicate databases, configure and use latency monitoring. See the SCC Installation Guide for details.


Status is not updated automatically when a latency monitoring process completes.

After a latency monitoring process completes, its status continues to show as “Running” in the Monitor > Paths view.

Workaround: To refresh the path status, click anywhere else in the pane to change the focus away from the path, then click the path again.


Connection arrows in the topology view depend on correctly defined connections.

The direction in which a connection arrow points in the topology depends on how the SAP Replication Server connection is defined. If a primary connection definition is used for a replicate-only connection to a non-Sybase/non-SAP data target, the connection arrow between SAP Replication Server and the non-Sybase/non-SAP data target may point in the wrong direction, from the target instead of to the target.

Workaround: When creating the SAP Replication Server connection definition to the non-Sybase/non-SAP replicate database, omit the with log transfer clause that is used for creating a primary connection definition.


Multiple error messages appear when a single SAP Replication Server goes down.

When a monitored SAP Replication Server goes down, several error messages are recorded in the SCC agent.log. The correct error message is reported by all monitored SAP Replication Servers, making it appear that the error message may be coming from other SAP Replication Servers.

Workaround: None.


When you configure Replication Agent parameters in the Quick Admin view while in the replicating state, the changes appear when you select “Show changes applied this session” even though they have not been successfully applied.

Workaround: None.


An empty value for the pdb_xlog_device parameter shows as invalid in the Quick Admin view for Replication Agent, even though an empty value is valid.

Workaround: None.


SAP Replication Server data collections fail if the replication access library stored procedures are removed from the SAP Replication Server System Database (RSSD).

Workaround: Unregister, then reregister the SAP Replication Server with SAP Control Center.


When you open a Path dashboard, the RepAgent thread graph does not appear.

Workaround: SAP Replication Server is case-sensitive. The SAP ASE name and the connection and route names must match, including case. If the case is different, unregister the SAP ASE, then reregister it using the correct case.


The “Launch Statistics Chart”option is missing when you right-click an SAP ASE registered for replication.

Workaround: None.


The “Run the job: Once” and “Run the job: Repetitively” options (or “Repeat once” and “Repeat indefinitely”) are not supported for SAP Replication Server data collection jobs.

If you select one of these options, the job is created, but SCC does not collect the statistics. Instead, it writes an error message to the SCC console and log file.

Workaround: Change the job option to Until (or Repeat until) and specify a date for the job to stop running.


SAP Replication Server performance statistics collection does not support SAP Replication Server 12.6 and 15.0.

The monitor and counters interface in versions 12.6 and 15.0 differs from the interface in SAP Replication Server 15.0.1 and later.

Workaround: None.