Details For Running Compare Pair Page

Use the Details for Running Compare Pair page to view near-real-time information about a compare pair that is running.

The Compare Pair Details section of the page shows specific information about the compare pair as follows:

Field Description

Compare Pair Name

The name for the compare pair.

Source Table and Target Table

The names of the underlying source and target objects.

Run Information

Lists performance statistics based on each phase of a run: the sorting phase (for source and target), the initial comparison phase, and the confirmation phase. Note: sorting statistics are only available if the job profile specifies server-side sorting (row sorts are performed by Oracle GoldenGate Veridata, not by the database engines).

  • Start Time: The time that a run phase started.

  • Run Duration: The amount of time that it took to complete a run phase.

  • Rows Processed: The number of rows that were processed in a run phase.

  • Rows Per Second: The performance rate of a run phase, in terms of rows processed.

  • Bytes Processed: The overall volume of data, in bytes, that was processed in a run phase.

  • Bytes Per Second: The performance rate of a run phase, in terms of bytes processed.

Using the Charts

The charts on this page help you to determine what types of operations are causing the most out-of-sync conditions and which phases of processing are taking the most time to complete.

Overall Rows Compared Pie Chart

Plots the result from the Overall Rows Compared field according to the possible outcomes of the comparison: In-Sync or Out-Of-sync.

Operations Performed Per Comparison Phase

The Operations Performed Per Comparison Phase chart plots possible out-of-sync conditions against the different phases of processing that are taken to evaluate rows.The x axis plots the different comparison processing phases:

  • Initial Compare: This represents the initial phase of processing where the compare pair metadata is being processed and rows are being fetched, sorted, and initially evaluated.

  • Persistent OOS: This is a status of the confirmation step where the target values have not changed since the initial comparison step, and they still are not the same as those of the source.

  • In-Sync-After In-flight: This is a status of the confirmation step where the target values match the source values that were retrieved during the initial comparison, implying that the source values were applied to the target row by replication or another method.

  • Still Changing: This is a status of the confirmation step in which the target row values have changed after being out-of-sync in the initial comparison, but source and target values still do not match. In this case, it is assumed that replication or another mechanism applied the changes, but Oracle GoldenGate Veridata was unable to confirm that the rows were in-sync.

The y axis plots the number of out-of-sync conditions for each phase, labelled as the following:

  • Inserts: The source has a row, but the target does not.

  • Updates: The source row has a different value than that of the target.

  • Deletes: The target has a row, but the source does not.

Other Actions From Here

To update the statistics that are shown on this page, click Refresh Page. By default, statistics are refreshed every 30 seconds. You can change the refresh rate by setting the Poll/Refresh Interval parameter. See Setting General User Preferences.

To stop comparison, click Stop Compare Pair. The Details for Finished Compare Pair is displayed and it shows the processing status of the compare pair.

To view the results for a finished compare pair, go to the Details for Finished Compare Pair page.

Related Topics

"Working with Jobs" in Oracle GoldenGate Veridata User's Guide