Ingesting Db2 for i Change Data into Snowflake with Cloud Mass Ingestion Databases

Back Next

Step 4: Configuring runtime options

On the

Schedule and Runtime Options

page of the database ingestion task wizard, you can configure some runtime options.

Under

Schema Drift Options

, specify the schema drift option to use for each of the supported types of DDL operations.

The types of supported DDL operations are:

Add Column

Modify Column

Drop Column

Rename Column

The following table describes the schema drift options that you can set for a DDL operation type:

Option	Description
Ignore	Do not replicate DDL changes that occur on the source database to the target. For Snowflake targets, this option is the default option for the Drop Column and Rename Column operation types
Replicate	Replicate the DDL operation to the target. For Snowflake targets, this option is the default option for the Add Column and Modify Column operation types. If you try to replicate a type of schema change that is not supported on the target, database ingestion jobs associated with the task will end with an error. Add Column operations that add a primary-key column are not supported and can cause unpredictable results. Modify Column operations that change the NULL or NOT NULL constraint for a column are not replicated to the target by design because changing the nullibility of a target column can cause problems when subsequent changes are applied. DDL operations are replicated to the target only after some data changes have been captured.
Stop Job	Stop the entire database ingestion job.
Stop Table	Stop processing the source table on which the DDL change occurred. When one or more of the tables are excluded from replication because of the Stop Table schema drift option, the job state changes to Running with Warning . The database ingestion job cannot retrieve the data changes that occurred on the source table after the job stopped processing it. Consequently, data loss might occur on the target. To avoid data loss, you will need to resynchronize the source and target objects that the job stopped processing. Use the Resume With Options Resync option.

Under

Advanced

, optionally edit the

Number of Rows in Output File

value to specify the maximum number of rows that the database ingestion task writes to an output data file for the Snowflake target.

Change data is flushed to the target either when this number of rows is reached or when the flush latency period expires and the job is not
in the middle of processing a transaction. The flush latency period is the time that the job waits for more change data before flushing data to the target. The latency period is internally set to 10 seconds and cannot be changed.

Valid values are 1 through 100000000. The default value is 100000 rows.

For Snowflake targets, the data is first stored in an internal stage area before being written to the target tables.

Under

Schedule

, the scheduling options are unavailable for incremental load tasks or combined initial and incremental load. Skip this field.

Under

Custom Properties

, you can specify custom properties that Informatica provides to meet your special requirements. Specify these properties only at the direction of Informatica Global Customer Support.

Click

Save

Configuring a database ingestion task

Download Guide

Watch

Comments

Cloud Mass Ingestion Homepage