Known Issues for Replication

A SQL Anywhere^® error occurs in a 15.7 environment with no routes.

When no routes exist, the rs_helproute RSSD stored procedure does not return a result set. Currently, the Sybase Control Center for Replication functionality uses the result set to close the prepared statement. Since the result set is null, the prepared statement remains open, and eventually causes this error: SQL Anywhere Error -685: Resource governor for 'prepared statements' exceeded.

The default setting for SQL Anywhere is a maximum of 50 prepared statements opened at one time. After 50 SCC for Replication collections, this error occurs and the Replication collections fail.

Workaround: Since there are no routes, there is no workaround for this in a single 15.7 Replication Server environment. You can increase the maximum number of prepared statements, however, this only delays the problem from occurring.

The heat chart may not show correct status for Replication Server alert changes.

Workaround: Use the Alert Monitor to see the correct status. To open the Alert Monitor, select View > Open > Alert Monitor.

Resources of type Path MO appear in the Perspective Resources view.

A path MO resource is created when you click on a path name link in Replication Server Monitor > Paths.

Workaround: Path MO resources do not cause problems; you can ignore them or remove them from your perspective.

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

Administration Console options in the Sybase Control Center 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 Sybase 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 Replication Servers for each RepAgent.

Workaround: Open the Replication Server Monitor Connections tab for each controlling Replication Server. It displays the connection names for the Adaptive Server RepAgents. You can also login to Replication Server and use the admin who command to derive this information.

Sybase Control Center for Replication may not have descriptions for some 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 Product Documentation Web site at sybooks.sybase.com.

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.

619385

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

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.

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 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.

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.

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.

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.

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.

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

Workaround: None.

562600

The “Run the job: Once” and “Run the job: Repetitively” options (or “Repeat once” and “Repeat indefinitely”) 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 job option to Until (or Repeat until) and specify a date for the job to stop running.

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.