Determine if the replication agent has applied all the transactions up to a particular point
For a parallel replication agent, the repadm utility "getstats" option displays the oldest uncommitted transaction log position below the last processed log position, as shown in the following output.
sid tid lognum logpos state seqno time error func 23 32 30 3300473 source 398228 2 0 ctReplGetNextChange
In this example, the log read thread has processed up to log 30 offset 3300473, and the oldest uncommitted transaction is at log 30 offset 3251827. If the oldest uncommitted transaction log position is zero, it means that the replication agent has committed all transactions up to the point of the last processed log position.
Use this information to determine if the replication agent has applied all the transactions up to a particular point in the transaction logs.
Notice
A repadm utility that does not support the newest version of the log read statistics structure will fail to read the log read thread statistics. The repadm utility will output the following error message, then exit.
"Error: Replication agent log read stat structure version (1) does not match repadm utility structure version (2)."
The solution is to use a version of the repadm utility that supports the new log read statistics structure.