The ra_statistics command returns activity-related statistics that you can use to evaluate Replication Agent operations and performance. By comparing the statistics returned when you first run the command, to the statistics returned after you have successfully replicated something you know will work, you can analyze the differences in the statistics and troubleshoot where the problem lies. The statistics help you determine if the instance is:
Scanning the transaction log
Processing replicated transactions
Sending LTL to the Replication Server
To check Replication Agent operations
Log in to the Replication Agent instance with the administrator login.
Verify that you are in Replicating state. If you are not, change the state to Admin. See “Checking the Replication Agent status”.
Use the following command to get current Replication Agent activity statistics:
ra_statistics
This command returns statistics for all of the Replication Agent components and the Java VM.
Save the statistics returned to use as a baseline for comparison.
Perform activity against the object that is not being replicated.
For example, update a table that is not being replicated.
Repeat step 2.
Be sure to allow enough time for the Replication Agent to process the
transaction.
Compare the new returned statistics activity with the baseline.
Check for differences and see the table below.
If... |
Then... |
|---|---|
The value returned for |
You are executing the transaction as the Repserver maintenance user for this Replication Server connection. By default, these transactions are not sent to Replication Server. You must either connect to the primary database as a different user, or you can set the configuration value of filter_maint_userid to false. |
See the Sybase Replication Agent Reference Manual for more information about the ra_statistics command.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
