This section describes the parameters that you can edit for a profile.

1. General: Controls output options. You can set the following output options:
   • Report In-sync rows to Report file: Prints all the in-sync rows to the veridata report.
   • Report In-sync after In-flight rows to Report file: Print the in-flight rows that becomes in-sync after the Confirm Out-of-Sync phase.
   • Out-of-Sync Output Format: From the dropdown, select a format for the out-of-sync file that is generated. The default value is Binary. If you select None, there is no output file generated.
   • Maximum size of each Out-of-Sync XML chunk (rows): You can set the maximum chunk size for the number of out-of-sync rows for the server-to-agent calls. Larger chunk size boosts perfomance by minimizing the server-to-agent calls, but utilizes more network bandwidth.
2. Sorting Method: Controls sorting method and memory management. Data is sorted to match keys (or a key specification) so that the correct source and target rows are compared.
   • Sort Data Using: Selecting the Server option gets and sorts the data on the server. Selecting the Database option uses the order by clause in the table, to sort the data during comparison.
   • Temporary Storage Directory for Source Data: Creates the sort file for the source data in the specified directory. Default location is the /tmp directory.
   • Temporary Storage Directory for Target Data Creates the sort file for the Target data in the specified directory. Default location is the /tmp directory.
3. Initial Compare: Controls parameters for the process that performs the initial compare step.
   • Output Out-of-Sync Record Details to Report File: Select this option to print all the out-of-sync records to an output report file.
   • Terminate when Maximum records Out-of-Sync: Set the number out-of-sync records after which the initial compare is stopped and records sent to Confirm Out-of-Sync phase. This parameter is valid only if you do not select the Perform Confirm Out-of-Sync Step parameter under the Confirm Out-of-Sync category.

     Note:

     If Terminate when Maximum COOS records out of sync number is not divisible by the batch size, then there are extra records in the report. The number of records in the report is always multiple of the batch size. For example, if the batch size is 10 and Terminate when Max COOS out of sync records is 15, and then the report will have 20 records.
   • Update Report file every (records): Enter the batch size after which the report file should be updated.
   • Update Report file every (seconds): Enter the time interval after which the report file should be updated.

     Note:

     Updating Report file every (seconds) takes precedence over Updating Report file every (records), when you set values for both the parameters.
   • 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.
   • Target Oracle Optimizer Hint: (Oracle) Specifies an Oracle hint that is passed to the agent on the target database when a comparison starts.
   • Max Concurrent Comparison Threads: Set the number of compare pairs to be run in parallel. The remaining compare pairs is set to waiting state.
   • Event Reporting
     • Generate Messages: Select the type of message to be generated in the report. Default is None.
     • Generate warning messages for Out-of-Sync rows after (differences): Set the number of out-of-sync records after which warning messages should be generated.
   • Agent (This is applicable only for C-Agents)
     • 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 Source (0 to use dynamic port list)
     • Use Static Listening Port for Agent during Row Hash on Target (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.

   • Non Stop Process
     • Source Process CPU Number: : This field designate a CPU for the process on the source system. The valid range is -1 (the default) to 16. When set to -1, the Oracle GoldenGate Manager process will attempt to start the processes in a round-robin fashion.
     • Source Process Priority: This field designate the priority at which the process will run on the source system.
     • Source process name starting with = Must start with dollar symbol, followed by two letters, and end with *: This value designate the name to use for the process on the source system. This name must start with a $ sign followed by two letters and end with an asterisk, for example $AA*.
     • Target Process CPU Number: This field designate a CPU for the process on the target system. The valid range is -1 (the default) to 16. When set to -1, the Oracle GoldenGate Manager process will attempt to start the processes in a round-robin fashion.
     • Target Process Priority: This field designate the priority at which the process will run on the target system.
     • Target process name starting with = Must start with dollar symbol followed by two letters, and end with *: This value designate the name to use for the process on the target system. This name must start with a $ sign followed by two letters and end with an asterisk, for example $AA*.
4. Confirm-Out-Of-Sync: Controls parameters for the process that performs the confirmation step.
   • Output Out-of-Sync Record Details to Report File: Enable this option to get the Out-of-Sync records in the compare-pair report file.
   • Terminate when Maximum records Out-of-Sync: Set the number of out-of-sync records, after which veridata should stop the (compare) job.
   • Update Report file every (records): Enter the batch size after which the report file should be updated.
   • Update Report file every (seconds): Enter the time interval after which the report file should be updated.

     Note:

     Updating Report file every (seconds) takes precedence over Updating Report file every (records), when you set values for both the parameters.
   • Source Oracle Optimizer Hint: Enter the source Oracle optimizer hint.
   • Target Oracle Optimizer Hint: Enter the target Oracle optimizer hint.
   • Run Concurrently With Initial Compare: Enable this parameter to run the Confirm Out-of-Sync and Initial Compare phase concurrently.
   • Delay Confirm-Out-of-Sync By (seconds): Enter the time interval by which you want to delay the Initial Compare and Confirm Out-of-Sync phases.
   • Confirm-Out-of-Sync Batch Size: Set the batch size to be processed in the Confirm Out-of-Sync phase.
   • Perform Confirm Out-of-Sync Step: Enable this parameter to perform the Confirm Out-of-Sync step. By default it is enabled.
5. Repair: Controls parameters for the repair process.
   • Repair
     • Repair Batch Size: Enter the batch size of the records to be repaired.
     • 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: Set the number of repair operations to be run concurrently.
     • Check changed values:
       • If you enable this parameter, and the non-key column records are updated post comparison, the changed out-of-sync records will not be repaired.
       • If you disable this parameter, and the non-key column records are updated post comparison, the changed out-of-sync records will also be repaired.
     • Terminate when Maximum Repair Warnings: Set the number of warnings after which the repair job should be stopped.
     • Run Repair Automatically after Compare: Enable this parameter to run repair automatically after comparison.
     • Repair SQL Path: Set the Repair SQLfile path inside veridata server.
   • Repair Reporting
     • Write Repair Success messages to Report: Enable this parameter to write the repair success messages to the report file.
   • Disable DB Triggers Session Based
     • 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.

The Sorting Method settings of the Profile Information page specify whether data sorting will be performed by the database or by Oracle GoldenGate Veridata Server. Specify this method in the Sort Data Using option on the Profile Information page.

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. Following is a list of the types of conditions that will produce differing sorted ordering of the rows:

• Character encoding conditions: Oracle GoldenGate Veridata compares character data as UTF-8 encoded bytes. To match server-side ordering, key columns that contain character data must contain only ASCII data or be encoded using UTF-8, and the database must use binary comparisons for character data (no comparisons that are case-insensitive or specific to a locale).

• Some datetime data types, such as Teradata TIME, may sort differently in the database and in Oracle GoldenGate Veridata Server.

• To make database ordering consistent with the ordering done by Oracle GoldenGate Veridata Server, the Oracle GoldenGate Veridata Agent may add ORDER BY clauses to the initial comparison SELECT statement that will make the database ignore indexes on the columns. An example is TIMESTAMP with TIMEZONE data, where Oracle GoldenGate Veridata orders the data by the string representation of the data rather than by the absolute time.

When Oracle GoldenGate Veridata Server performs the sort, the Oracle GoldenGate Veridata Agents return data in the natural order that is provided by each database, and then the data is sorted by two server sort processes, one to sort source rows and the other to sort target rows. Server-side sorting supports a maximum row length of 32768 bytes. This limit normally is not exceeded when the hash comparison method is used.

Specifies a location on the source disk or 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.

Choosing locations on different physical drives might speed up comparisons in some circumstances. You can specify multiple locations for each process, separating each one with a semicolon (for example /tmp/sort1; /tmp/sort2). All locations specified must already exist. The drives used should have sufficient free disk space. To calculate the approximate amount of space needed, use this formula:

1.5 * (Trows * (Tkey + 20)) * nTables

where:

Trows = the number of rows in table

Tkey = the average size of the table key, in bytes

nTables = the number of tables that are being compared