Define a replication request in Connect CDC Director - Connect_CDC - aws_mainframe_modernization_service - connect_cdc_mimix_share - Latest

The Replication Request Properties dialog is displayed.

Connect CDC now has an option where a load utility, Teradata Parallel Transporter (TPT), can now be used as an alternative to the standard apply method. This option will replicate captured data to csv files and then launch TPT jobs to load the data directly to a Teradata target. For additional usage details refer to Usage restrictions for TPT.

1. Select Use “Load Utility” where possible. By default, this checkbox is unselected.

2. Select the Load Utility tab. This tab only appears if you have selected Use “Load Utility” where possible.

3. The Load Utility dialog displays.

4. In the Apply error mode section, select the appropriate error mode you wish to apply for a specific request to the target database.

Skip file, continue with next—For a specific request, skip the file that had the error while applying data, and proceed to apply data from the next file.

Skip and Delete file, continue with next—For a specific request, skip the and delete file that that had the error while applying data, and proceed to apply data from the next file.

Shut down apply component—For a specific request, stop applying data to the target database. This is the default.

On the Common tab, enter a name for the request in Request Name and accept the defaults for the remaining options on all tabs.

The Replication tab is primarily for specifying how to handle errors and data collisions when applying the replicated data at the target. By default, transaction errors do not stop the replication processing, and data collisions are not resolved.

Click OK.

The model now displays the Replication request name under the Requests branch.

Validate and commit the model, as you did earlier. (See Validate the model and Commit the model.)