Overriding Run Options
Use the Run Options page to override the run settings configured in the job profile. By default, all parameters are set to Use Profile.
When a user has repair execution privileges, the options for controlling repair appear. These are the same options as the options in the Repair Category on the Profile Configuration page.
To change a run option:
Example 1-4 Parameter Details
-
General (No Comparisons Performed)
Select only one of these items for any given run, as they are mutually exclusive.
-
Review Previous Out-Of-Sync Results: Compares only those rows that were out-of-sync in the previous run, based on the information that is stored in the Out-of-Sync file. Oracle GoldenGate Veridata will compare these rows against their current state. The results identify which rows were brought back into synchronization by replication or another method. By default, this parameter is disabled. Check Value to enable it.
-
Generate Out-Of-Sync XML from Previous Run: Generates an OOSXML file based on the OOS file from the previous run. It generates XML for every row from the OOS file. You can use the XML from this file for your own purposes, such as to view the out-of-sync information in an XML editor. By default, this parameter is disabled. Check Value to enable it. When this parameter is enabled, Review Previous Out-Of-Sync Results is ignored.
-
-
Profile Setting Overrides
-
Max Concurrent Comparison Threads: Specifies the number of concurrent processing threads to use. You can use up to the same number of threads as there are processors on the server system.
-
Delay Confirm-Out-Of-Sync By (seconds): Delays the confirmation step by the specified number of seconds to account for replication lag. Delaying the confirmation step reduces the number of false out-of-sync results that occur because an updated source value was not replicated fast enough.
-
Perform Confirm-Out-Of-Sync Step: Controls whether or not the confirmation step is performed. By default, it is performed. Clear the check box under Value to skip the confirmation step and only perform the initial (row hash) comparison. You might skip the confirmation step if, for example, activity on the source tables is quiesced or if replication is not continuously updating the target table(s).
-
Out-Of-Sync Output Format: Controls how out-of-sync row information is written to the OOS file on disk. The default is binary format, which is compatible with the Oracle GoldenGate Veridata Web User Interface browser. To change the output option, select one of the following under Value:
-
To output only in XML, select XML.
-
To output in both binary and XML formats, select Both.
-
To suppress out-of-sync output, select None.
-
-
Maximum Size of Each Out-Of-Sync XML Chunk (Rows): Limits the number of out-of-sync rows that are written to an XML-based OOS report chunk. The OOS file is actually written as several files to prevent one file from becoming so large that it affects system resources. Using chunks enables periodic archiving or purging to remove aged files. The current file is closed when the specified number of rows is written, and a new file is opened.
-
-
Tracing
-
Trace Agent Rowhash: Turns on tracing for the initial comparison step.
-
Trace Agent COOS: Turns on tracing for the confirmation step.
-
Trace Server: Turns on tracing for Oracle GoldenGate Veridata Server. Select or enter a value to set the desired trace level. The higher the level, the more detailed the trace data.
By default, all tracing is off.
-
-
Repair
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.
-