Help Center/ Cloud Data Migration/ User Guide/ Creating a Job in a CDM Cluster/ Configuring CDM Destination Job Parameters/ To IBM Db2
Updated on 2026-07-29 GMT+08:00
View PDF
Share

To IBM Db2

Table 1 lists the destination job parameters when the destination link is an IBM Db2 link.

Table 1 Parameter description

Type

Parameter

Description

Example Value

Basic parameters

Schema/Tablespace

Name of the database to which data will be written. The schema can be automatically created. Click the icon next to the text box to select a schema or tablespace.

schema

Table Name

Name of the table to which data will be written. Click the icon next to the text box. The dialog box for selecting the table is displayed.

This parameter can be configured as a macro variable of date and time and a path name can contain multiple macro variables. When the macro variable of date and time works with a scheduled job, the incremental data can be synchronized periodically. For details, see Incremental Synchronization Using the Macro Variables of Date and Time.

NOTE:

If you have configured a macro variable of date and time and schedule a CDM job through DataArts Studio DataArts Factory, the system replaces the macro variable of date and time with (Planned start time of the data development job – Offset) rather than (Actual start time of the CDM job – Offset).

table

Clear Data Before Import
Whether to clear the data in the destination table before data import. The options are as follows:
  • Do not clear: The data in the destination table is not cleared before data import. The imported data is just added to the table.
  • Clear all data: All data is cleared from the destination table before data import.
  • Clear part of data: Part of the data in the destination table is cleared before data import. If you select Clear part of data, you must configure WHERE Clause to specify which part will be deleted.

Clear part of data

WHERE Clause

If Clear Data Before Import is set to Clear part of data, data in the destination table will be deleted based on the WHERE clause after the configuration is complete and before the import starts.

age > 18 and age <= 60

Advanced parameters

Prepare for Data Import

A custom SQL statement that is automatically executed before a migration job is executed

This function is often used for data cleanup, environment preparation, temporary operations, or other preparations.

create table

Complete Statement After Data Import

A custom SQL statement that is automatically executed after a migration job is executed

This function is often used for data cleanup, environment preparation, temporary operations, or other preparations.

drop table

Loader Threads

Number of threads started in each loader. A larger number allows more concurrent write operations.

NOTE:

This parameter is unavailable if Constraint Conflict Handling is set to replace into or on duplicate key update.

1