The ra_statistics command returns activity-related statistics that you can use to evaluate Mirror 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 that you know works, 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
Checking Mirror Replication Agent operations
Log in to the Mirror Replication Agent instance with the administrator login.
Verify that you are in Replicating state. If you are not, change the state to Admin. See “Check the Mirror Replication Agent status”.
Use the following command to return statistics for all of the Mirror Replication Agent components and the Java VM:
ra_statistics
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 Mirror Replication
Agent to process the transaction.
Compare the newly-returned statistics activity with the baseline. Check for differences and see the following table.
If... |
Then... |
|---|---|
The value returned for |
You are executing the transaction as the Replication Server 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. |
For more information about the ra_statistics command, see the Mirror Replication Agent Reference Manual.
