Existing Compare Pairs
All of the source and target objects that you configure into compare pairs for any given group must be accessible from the data source connections that are associated with that group.
Note:
Before creating compare pairs, you must create a group to contain them.
Use the Compare Pair Configuration page to view, create, modify, and save compare pairs and their column mappings.
The Group Information section at the top of this page displays information about the group that you are working with.
The tabs on this page contain the tools that you need to work with compare pairs.
The Existing Compare Pairs tab is your start point. It displays any compare pairs that currently exist in the selected group. The columns in the Existing Compare Pairs list show details about those compare pairs.
To create compare pairs, use either of the Mapping methods:
You can use a combination of both mapping methods, if needed. Use the pattern method first, and then use the manual method for any objects that remain unmapped, or to make revisions such as to add row partitions.
Existing Compare Pair List Details
The following table describes each column in the Existing Compare Pairs list.
Name of the Column | Description |
---|---|
Compare Pair Name |
This is either the default name format of |
Column Mapping |
Links to the Column Mapping Configuration page, where you can create or edit the mappings between the source and target columns of a compare pair. |
Source Catalog (Some platforms) |
The source metadata catalog or database. |
Source Schema |
The owner of the source database objects that are to be compared. |
Target Catalog (Some platforms) |
The target metadata catalog or database. |
Target Schema |
The owner of the target database objects that are to be compared. |
Row Partition |
If any row partitions (subsets) are defined, there is a notification here. Otherwise, this field is blank. |
Profile |
If a run profile exists for a compare pair, it is shown here. Otherwise, this field is blank and the default profile will be used during comparisons. (A profile can be specified for an individual compare pair on the Manual Mapping tab.) |
Validation Status |
Shows whether or not the columns of the source and target objects are suitable for being compared, based on the results of any previous validation that was performed. |
Key Mapping Method |
Can be either System Generated or User Defined, depending on the method that was chosen to map the key columns for this compare pair. |
Column Mapping Method |
Can be either System Generated or User Defined, depending on the method that was chosen to map the non-key columns for this compare pair. |
To filter the Existing Compare Pair list:
Related Topics
Controlling Delta Processing
You can enable or disable delta processing for database compare pair from the Delta Processing tab and the Existing Compare Pairs tab of the Compare Pair Configuration page. In addition, you can use the Delta Processing Enabled check box on the Run Configuration page to toggle this feature.
From the Existing Compare Pairs tab, you can enable or disable delta processing for any or all compare pairs. Select their names in the Select column (or select Page to select all pairs on the current page), and then click Enable Delta Processing or Disable Delta Processing. When delta processing is enabled, a delta symbol appears next to the name of the affected compare pair.
How do I configure delta processing?
On the Column Mapping Configuration page, click the Delta Processing tab. By default, the options are automatically populated and the Enable Delta Processing check box is selected. You can disable the feature by deselecting the check box, which renders all other options inactive.
You can use the defaults or change any of the following:
-
the source or target columns for processing,
-
whether to use a source or target query
-
the source or target database query
After you have configured the delta processing for the compare pair, click Save to apply your changes.
For more information, see the "Using Delta Processing" section in Oracle GoldenGate Veridata User's Guide.
Deleting a Compare Pair
Use the Compare Pair Configuration page to delete compare pairs.
You must have the Administrator or Power User role to delete compare pairs.
To delete compare pairs:
-
Make the Existing Compare Pairs tab active.
-
(Optional) Expand Filters to filter the Existing Compare Pairs list as needed, and then click Apply Filter. You can filter by:
-
Compare Pairs with status
-
Validated means that the source and target columns are compatible and suitable for comparison.
-
Preliminary Validation Failed means that the compare pair has not been processed in a job yet, but a preliminary validation failed.
-
Runtime Validation Failed means that the compare pair failed the runtime validation when a job was started.
-
-
Compare Pair Like
The default name format is
source_table/file
=target_table/file
but a compare pair can have a user-defined name instead. The filter returns names containing the specified string. -
Source Table Name Like and Target Table Name Like
To determine the source and target table or file names if a user-defined name is shown, hover the mouse cursor over the name of the compare pair in the list. A hint appears showing the actual names.
-
Profile Name Like
There will be a profile name shown if one was specified to override the default profiles for jobs that contain this compare pair.
-
-
In the Select column, select the compare pairs that you want to delete, or select the Page check box to delete all of the compare pairs on the page. Use the page management tools to make selections on other list pages as needed.
-
Click Delete. You will be prompted to confirm your request.
Related Topics