Editing Profile Settings

General Settings

The General settings of the Edit Profile page control output options for the Out-of-Sync and Comparison reports.

Setting	Description
Out-Of-Sync Output Format	The default output for out-of-sync rows is in binary format that is compatible with Oracle GoldenGate Veridata Server's output format for display in the Veridata Web User Interface browser. To change the output option, deselect Use Default and then select one of the following under Value: XML: output in XML only Both: output in both binary and XML formats None: suppress out-of-sync output
Maximum Size of Each Out-Of-Sync Chunk (Rows)	Controls the number of out-of-sync rows that are written to each XML output file. Because the amount of XML output can be large, the XML report is written to different files, otherwise known as chunks, instead of to a single file.
Report in-sync rows to report file	Controls whether or not information about rows that are in-sync are written to the comparison report. Excluding these rows reduces the amount of output that is written to disk. By default, this information is omitted.
Report in-sync after in-flight rows to report file	Controls whether or not information is written to the comparison report about rows that were in-flight in the initial comparison but are now in-sync after the confirmation step. Excluding these rows reduces the amount of output that is written to disk. By default, this information is omitted.

Sorting Method Settings

The Sorting Method settings of the Edit Profile page specify whether data sorting will be performed by the database or by Oracle GoldenGate Veridata Server, and how the sorted data will be stored.

Setting	Description
Sort Data Using	By default, Oracle GoldenGate Veridata uses the database to sort data for comparison. This default is due to historical conditions that are no longer valid. Server-side sorting is the current recommended sorting method. Database sorting should only be considered when the ordering produced by the database is identical to the ordering produced by Oracle GoldenGate Veridata Server. More Note: The rest of the sort options on this page apply only if server-side sorting is being used.
Maximum Memory Usage (MB)	Sets the maximum amount of physical memory to be used by each Oracle GoldenGate Veridata Server sort process (source and target); therefore, twice the amount of memory specified will be used. The memory specified should be well below the actual physical memory of the system to prevent any possible use of virtual memory, which would significantly slow down processing.
Temporary Storage Directory for Source Data	Specifies a location on the source disk to use as temporary storage when there is not enough memory to process all of the data that is being sorted. If no locations are defined, the default is to use a directory under the Oracle GoldenGate Veridata Server home location. More
Temporary Storage Directory for Target Data	Specifies a location on the target disk to use as temporary storage when there is not enough memory to process all of the data that is being sorted. If no locations are defined, the default is to use a directory under the Oracle GoldenGate Veridata Server home location. More

Initial Compare Settings

The Initial Compare settings of the Edit Profile page set attributes for the initial (row hash) step of the comparison.

General

These settings control general settings that apply to both the initial and out-of-sync compare processes.

Setting	Description
Max Concurrent Comparison Threads	Sets the number of concurrent threads that the comparison process can use. This value should be less than, or equal to, the number of CPUs on the Oracle GoldenGate Veridata Server machine. Increasing the number of threads above the number of CPUs will not make the sort faster, and could even slow it down.
Terminate when Maximum Records Out-Of-Sync	Terminates the comparison when the specified number of out-of-sync rows is reached. Can be used to specify a threshold after which a full reload may be more appropriate than resynchronizing rows.
Output Out-Of-Sync Record Details to Report File	Outputs column-level details for out-of-sync rows to the report file, including actual and compressed values.
Update Report file Every (seconds)	Outputs intermediate statistics to the report file, including the number of rows processed so far and the number of out-of-sync rows. Select this option to specify an output interval in seconds.
Update Report file Every (records)	Outputs intermediate statistics to the report file, including the number of rows processed so far and the number of out-of-sync rows. Select this option to specify an output interval based on a specific number of records. Note: If both Update Report file Every (seconds) and Update Report file Every (records) are selected, only Update Report file Every (seconds) will be used.
Limit Number of Input Rows	Limits the number of rows to process from the table. Useful for estimating the amount of time that a comparison will take. Limit the number of rows, then run a comparison for them. Afterward use the results to calculate how long the full comparison would take. This parameter is also useful for testing and debugging so that the run completes in a shorter time than if the entire table was processed.
Source Oracle optimizer hint	(Oracle) Specifies an Oracle hint that is passed to the agent on the source database when a comparison starts. You can enter up to 256 characters. Note that only 20 characters is visible in the field; to ensure accurate entry of the hint, you can copy from a text file and paste into the field.
Target Oracle optimizer hint	(Oracle) Specifies an Oracle hint that is passed to the agent on the target database when a comparison starts. You can enter up to 256 characters. Note that only 20 characters is visible in the field; to ensure accurate entry of the hint, you can copy from a text file and paste into the field.

Event Reporting

These settings control whether, and how, messages are sent to the report whenever the initial comparison process finishes a task.

Setting	Description
Generate Messages	To generate only an informational message, whether or not rows are out-of-sync, select Info. To generate a warning message if rows are out-of-sync in this step, select Warning. To generate both types of messages, select Both, or to suppress all messages, select None.
Generate Warning Messages For Out-Of-Sync Rows After (differences)	Generates a warning message if the number of out-of-sync rows exceeds the specified value. If set, you should see a message in the comparison report similar to "Tables out-of-sync: srcTable, targTable, rows xx" if more than the specified number of rows are out of sync. If less than that number of rows is out of sync, you should see a message similar to "tables in sync: srcTable, targTable." To generate the warning message, you must set the Generate Messages parameter to something other than the default of None.

Setting

Description

Generate Messages

To generate only an informational message, whether or not rows are out-of-sync, select Info. To generate a warning message if rows are out-of-sync in this step, select Warning. To generate both types of messages, select Both, or to suppress all messages, select None.

Generate Warning Messages For Out-Of-Sync Rows After (differences)

Generates a warning message if the number of out-of-sync rows exceeds the specified value. If set, you should see a message in the comparison report similar to "Tables out-of-sync: srcTable, targTable, rows xx" if more than the specified number of rows are out of sync. If less than that number of rows is out of sync, you should see a message similar to "tables in sync: srcTable, targTable." To generate the warning message, you must set the Generate Messages parameter to something other than the default of None.

Agent

These settings control port usage for the Oracle GoldenGate Veridata Agent.

Setting	Description
Use Static Listening Port For Agent During Row Hash On Source (0 to use dynamic port list) Use Static Listening Port For Agent During Row Hash On Target (0 to use dynamic port list)	These settings are for debugging. At the default of 0, the Oracle GoldenGate Veridata Agent is started by the Oracle GoldenGate Veridata Manager during the initial comparison step. By specifying a port number instead, you can direct Oracle GoldenGate Veridata Server to interact with Veridata Agent through that port.

Setting

Description

Use Static Listening Port For Agent During Row Hash On Source (0 to use dynamic port list)

Use Static Listening Port For Agent During Row Hash On Target (0 to use dynamic port list)

These settings are for debugging. At the default of 0, the Oracle GoldenGate Veridata Agent is started by the Oracle GoldenGate Veridata Manager during the initial comparison step. By specifying a port number instead, you can direct Oracle GoldenGate Veridata Server to interact with Veridata Agent through that port.

NonStop Process

These settings control the process name, CPU, and priority assigned to the initial compare process on a NonStop system.

Setting	Description
Source Process Name Starting With Target Process Name Starting With	These two fields designate the name to use for the process on the source and target systems, respectively. This name must start with a $ sign followed by two letters and end with an asterisk, for example $AA*.
Source Process CPU Number Target Process CPU Number	These two fields designate a CPU for the process on the source and target systems, respectively. The valid range is -1 (the default) to 16. When set to -1, the Oracle GoldenGate Manager process will attempt to start the VERIAGT processes in a round-robin fashion.
Source Process Priority Target Process Priority	These two fields designate the priority at which the process will run on the source and target systems, respectively.

Setting

Description

Source Process Name Starting With

Target Process Name Starting With

These two fields designate the name to use for the process on the source and target systems, respectively. This name must start with a $ sign followed by two letters and end with an asterisk, for example $AA*.

Source Process CPU Number

Target Process CPU Number

These two fields designate a CPU for the process on the source and target systems, respectively. The valid range is -1 (the default) to 16. When set to -1, the Oracle GoldenGate Manager process will attempt to start the VERIAGT processes in a round-robin fashion.

Source Process Priority

Target Process Priority

These two fields designate the priority at which the process will run on the source and target systems, respectively.

Confirm-Out-Of-Sync Settings

The Confirm out-of-sync settings of the Edit Profile page control attributes for the confirmation step of the comparison.

General

These settings control general settings that apply to both the initial and out-of-sync compare processes.

Setting	Description
Perform Confirm Out-Of-Sync Step	When selected, the confirmation step is performed. Otherwise, this step is skipped. You might skip the confirmation step, for example, when the database is quiesced or if replication is not actively replicating data changes.
Run Concurrently With Initial Compare	When selected, the initial compare and confirmation processes run concurrently. To run them in sequence, deselect this box. Running them separately uses fewer system resources.
Delay Confirm-Out-Of-Sync By (seconds)	Specifies an anticipated replication lag threshold. The confirmation step will wait this amount of time before confirming rows as out-of-sync. This allows any in-flight changes in the replication stream to be posted first.
Terminate when Maximum Records Out-Of-Sync	Terminates the comparison when the specified number of out-of-sync rows is reached. Can be used to specify a threshold after which a full reload may be more appropriate than re-synchronizing rows.
Output Out-Of-Sync Record Details to Report File	Outputs column-level details for out-of-sync rows to the report file, including actual and compressed values.
Update Report file Every (seconds)	Outputs intermediate statistics to the report file, including the number of rows processed so far and the number of out-of-sync rows. Select this option to specify an output interval in seconds.
Update Report file Every (records)	Outputs intermediate statistics to the report file, including the number of rows processed so far and the number of out-of-sync rows. Select this option to specify an output interval based on a specific number of records. Note: If both Update Report file Every (seconds) and Update Report file Every (records) are selected, only Update Report file Every (seconds) will be used.
Source Oracle optimizer hint	(Oracle) Specifies an Oracle hint that is passed to the agent on the source database when a comparison starts. You can enter up to 256 characters. Note that only 20 characters is visible in the field; to ensure accurate entry of the hint, you can copy from a text file and paste into the field.
Target Oracle optimizer hint	(Oracle) Specifies an Oracle hint that is passed to the agent on the target database when a comparison starts. You can enter up to 256 characters. Note that only 20 characters is visible in the field; to ensure accurate entry of the hint, you can copy from a text file and paste into the field.
Confirm-Out-Of-Sync Batch Size	Specifies the number of Out-Of-Sync rows in a package. You can enter a number between 1 and 100; the default value is 10.

Event Reporting

These settings control whether, and how, messages are sent to the report whenever the initial comparison process finishes a task.

Setting	Description
Generate Messages	To generate only an informational message, whether or not rows are out-of-sync, select Info. To generate a warning message if rows are out-of-sync in this step, select Warning. To generate both types of messages, select Both, or to suppress all messages, select None.
Generate Warning Messages For Out-Of-Sync Rows After (differences)	Generates a warning message if the number of out-of-sync rows exceeds the specified value. If set, you should see a message in the comparison report similar to "Tables out-of-sync: srcTable, targTable, rows xx" if more than the specified number of rows are out of sync. If less than that number of rows is out of sync, you should see a message similar to "tables in sync: srcTable, targTable." To generate the warning message, you must set the Generate Messages parameter to something other than the default of None.

Setting

Description

Generate Messages

To generate only an informational message, whether or not rows are out-of-sync, select Info. To generate a warning message if rows are out-of-sync in this step, select Warning. To generate both types of messages, select Both, or to suppress all messages, select None.

Generate Warning Messages For Out-Of-Sync Rows After (differences)

Generates a warning message if the number of out-of-sync rows exceeds the specified value. If set, you should see a message in the comparison report similar to "Tables out-of-sync: srcTable, targTable, rows xx" if more than the specified number of rows are out of sync. If less than that number of rows is out of sync, you should see a message similar to "tables in sync: srcTable, targTable." To generate the warning message, you must set the Generate Messages parameter to something other than the default of None.

Agent

These settings control port usage for the Oracle GoldenGate Veridata Agent.

Settings	Description
Use Static Listening Port For Agent During Row Hash On Source (0 to use dynamic port list) Use Static Listening Port For Agent During Row Hash On Target (0 to use dynamic port list)	These settings are for debugging. At the default of 0, the Oracle GoldenGate Veridata Agent is started by the Oracle GoldenGate Veridata Manager during the initial comparison step. By specifying a port number instead, you can direct Oracle GoldenGate Veridata Server to interact with Veridata Agent through that port.

Settings

Description

Use Static Listening Port For Agent During Row Hash On Source (0 to use dynamic port list)

Use Static Listening Port For Agent During Row Hash On Target (0 to use dynamic port list)

These settings are for debugging. At the default of 0, the Oracle GoldenGate Veridata Agent is started by the Oracle GoldenGate Veridata Manager during the initial comparison step. By specifying a port number instead, you can direct Oracle GoldenGate Veridata Server to interact with Veridata Agent through that port.

NonStop Process

These settings control the process name, CPU, and priority assigned to the initial compare process on a NonStop system.

Setting	Description
Source Process Name Starting With Target Process Name Starting With	These two fields designate the name to use for the process on the source and target systems, respectively. This name must start with a $ sign followed by two letters and end with an asterisk, for example $AA*.
Source Process CPU Number Target Process CPU Number	These two fields designate a CPU for the process on the source and target systems, respectively. The valid range is -1 (the default) to 16. When set to -1, the Oracle GoldenGate Manager process will attempt to start the VERIAGT processes in a round-robin fashion.
Source Process Priority Target Process Priority	These two fields designate the priority at which the process will run on the source and target systems, respectively.

Setting

Description

Source Process Name Starting With

Target Process Name Starting With

These two fields designate the name to use for the process on the source and target systems, respectively. This name must start with a $ sign followed by two letters and end with an asterisk, for example $AA*.

Source Process CPU Number

Target Process CPU Number

These two fields designate a CPU for the process on the source and target systems, respectively. The valid range is -1 (the default) to 16. When set to -1, the Oracle GoldenGate Manager process will attempt to start the VERIAGT processes in a round-robin fashion.

Source Process Priority

Target Process Priority

These two fields designate the priority at which the process will run on the source and target systems, respectively.

Repair Settings

The Repair settings of the Edit Profile page control attributes for the repair process of out-of-sync rows. More

Repair

These settings control parameters in a repair job.

Setting	Description
Repair Batch Size	Specifies the number of repair operations in each batch transferred from the source agent to the target agent.
Repair Transaction Size	Specifies the number of repair operations included in the database transaction at the target. The special value "0" indicates that the transaction size should be the same as the repair batch size.
Number of Concurrent Repair Operations	Specifies the number of concurrent table pair repair operation allowed with a single repair job.
Check Changed Values	Indicates whether or not update operations should check whether or not column values have changed since the base comparison was run.
Terminate When Maximum Repair Warnings	Indicates the maximum number of repair warnings allowed on a single repair pair. A number less than or equal to zero indicates no limit.
Run Repair Automatically after Compare	Specifies that a repair operation will run automatically after a compare operation if any OOS rows are discovered. Defaults to False.

Repair Reporting

These settings control whether, and how, messages are sent to the report whenever the repair process finishes a task.

Setting	Description
Write Repair Success Messages to Report	By default, a message is written to the repair report file for each row in the repair job. This setting will suppress the message for successfully repaired rows. Error and warning messages are always written to the report..

Disable DB Triggers Session Based

These settings control port usage for the Oracle GoldenGate Veridata Agent.

Setting	Description
Disable DB Triggers Session Based	For databases that support disabling triggers (Oracle and Sybase), when you enable this setting, the Veridata Agent will issue the required commands to disable triggers while applying repair updates.