Known Issues for Replication

Known issues and workarounds for Sybase Control Center for Replication.

Change Request Number	Description
687151	SCC for Replication 3.2.3 and older versions do not support RS 15.7 multipath replication.
687149	Sybase Control Center for Replication 3.2.3 may not have descriptions for some Replication Server 15.7 configuration parameters. Workaround: See the Replication Server 15.7 Reference Manual for information on the parameters with missing descriptions. The manual is available on the Product Documentation Web site at sybooks.sybase.com.
686837	A queue graph for intermediate Replication Server is missing in the Replication Path dashboard. When you open the Path dashboard, the ASE Replication Agent thread always displays zero. Workaround: Upgrade Adaptive Server Enterprise to 15.0.3 or later.
619404	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.
619385 618454	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.
619382 618772	Latency cannot be obtained for non-ASE replicate databases. Sybase 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 replicate databases. However, the default latency monitoring using rs_lastcommit does not, thus Sybase Control Center cannot access the rs_lastcommit table in non-Sybase 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 replicate databases, configure and use latency monitoring. See the Sybase Control Center Installation Guide for details.
616952	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 Replication Server connection is defined. If a primary connection definition is used for a replicate-only connection to a non-Sybase data target, the connection arrow between Replication Server and the non-Sybase data target may point in the wrong direction, from the target instead of to the target. Workaround: When creating the Replication Server connection definition to the non-Sybase replicate database, omit the with log transfer clause that is used for creating a primary connection definition.
616831	If an Adaptive Server cluster stops responding, the RepAgent thread status shown in replication is “Down.” You can register an Adaptive Server cluster and one of its nodes with SCC. If the registered node stops responding while SCC is monitoring replication in the Adaptive Server cluster, the statuses of both the RepAgent thread and of the node appear as “Down”—SCC does not automatically switch to another working node. Workaround: In the Perspective Resources view, select the Adaptive Server cluster and click the drop-down arrow that appears to the right of the name. Select Properties > Connection. Change the connection parameters to those of a working node in the Adaptive Server cluster, then click Apply.
616694 614419	Multiple error messages appear when a single Replication Server goes down. When a monitored Replication Server goes down, several error messages are recorded in the agent.log. The correct error message is reported by all monitored Replication Servers, making it appear that the error message may be coming from other Replication Servers. Workaround: None.
611190	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.
611023	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.
578836	Replication Server data collections fail if the replication access library stored procedures are removed from the Replication Server System Database (RSSD). Workaround: Unregister, then reregister the Replication Server with Sybase Control Center.
565911	When you open a Path dashboard, the RepAgent thread graph does not appear. Workaround: Replication Server is case-sensitive. The Adaptive Server name and the connection and route names must match, including case. If the case is different, unregister the Adaptive Server, then reregister it using the correct case.
563885	The “Launch Statistics Chart”option is missing when you right-click an Adaptive Server registered for replication. Workaround: None.
562600 562598	“Repeat once” and “Repeat indefinitely” options are not supported for 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 collection job option to Repeat until so that the job runs a specific number of times.
559160	Replication Server performance statistics collection does not support Replication Server 12.6 and 15.0. The monitor and counters interface in versions 12.6 and 15.0 differs from the interface in Replication Server 15.0.1 and later. Workaround: None.

Change Request Number

Description

687151

SCC for Replication 3.2.3 and older versions do not support RS 15.7 multipath replication.

687149

Sybase Control Center for Replication 3.2.3 may not have descriptions for some Replication Server 15.7 configuration parameters.

Workaround: See the Replication Server 15.7 Reference Manual for information on the parameters with missing descriptions. The manual is available on the Product Documentation Web site at sybooks.sybase.com.

686837

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

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

Workaround: Upgrade Adaptive Server Enterprise to 15.0.3 or later.

619404

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.

619385

618454

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.

619382

618772

Latency cannot be obtained for non-ASE replicate databases.

Sybase 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 replicate databases. However, the default latency monitoring using rs_lastcommit does not, thus Sybase Control Center cannot access the rs_lastcommit table in non-Sybase 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 replicate databases, configure and use latency monitoring. See the Sybase Control Center Installation Guide for details.

616952

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 Replication Server connection is defined. If a primary connection definition is used for a replicate-only connection to a non-Sybase data target, the connection arrow between Replication Server and the non-Sybase data target may point in the wrong direction, from the target instead of to the target.

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

616831

If an Adaptive Server cluster stops responding, the RepAgent thread status shown in replication is “Down.”

You can register an Adaptive Server cluster and one of its nodes with SCC. If the registered node stops responding while SCC is monitoring replication in the Adaptive Server cluster, the statuses of both the RepAgent thread and of the node appear as “Down”—SCC does not automatically switch to another working node.

Workaround:

In the Perspective Resources view, select the Adaptive Server cluster and click the drop-down arrow that appears to the right of the name.
Select Properties > Connection.
Change the connection parameters to those of a working node in the Adaptive Server cluster, then click Apply.

616694

614419

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

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

Workaround: None.

611190

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.

611023

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.

578836

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

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

565911

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

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

563885

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

Workaround: None.

562600

562598

“Repeat once” and “Repeat indefinitely” options are not supported for 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 collection job option to Repeat until so that the job runs a specific number of times.

559160

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

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

Workaround: None.