Table of Contents

Search

  1. Preface
  2. Scripting Overview
  3. Tcl Scripting
  4. SQL Scripting

Tcl Script Execution

Tcl Script Execution

After you define Tcl scripts for a table in the Data Replication Console, the Tcl scripts run as part of the scheduled replication job during Apply processing or as part of the InitialSync job.
InitialSync does not support Apache Kafka or flat-file target types.
Tcl creates a single interpreter for each Apply task or InitialSync thread. For example, if you have four Apply task threads, Tcl uses four independent interpreters.
If you configured the replication job to use multiple subtask threads for an Apply task, Tcl creates a single interpreter for each subtask thread. You enable subtask threads by setting the apply.subtasks_enabled parameter to 1 on the
Runtime Settings
tab >
Advanced Settings
view.
For Teradata, Netezza,
PostgreSQL,
and Greenplum targets, Data Replication can use either a native load utility or the appropriate ODBC driver for initial materialization of target tables. For Microsoft SQL Server
and DB2
targets, InitialSync cannot use the native load utility with Tcl expressions that calculate column values for the target tables. For these targets, set the initial.enforce_odbc_load parameter to 1.

0 COMMENTS

We’d like to hear from you!